Task #98 (closed)
Rework pom.xml, classpath.xml, and maven.xml (with groovy) to use version.properties
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-Beta3 |
| Component: | Deployment | Version: | 3.0-M1 |
| Keywords: | build, ant, maven | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
There's really no need to re-generate classpath.xml and friends just to update a jar version. Pom.xml can be reworked to accept versions from some external location (the classpath maintainer will have to do some hoop jumping) but after that, the version numbers in classpath.xml et al (which are always the last path element before the jar
<project>/<component>/<version>/<component>-<version>.jar
can be rewritten in the form:
${<project>.<component>.version}
or similar.
Change History (2)
comment:1 Changed 16 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 16 years ago by jmoore
- Milestone changed from Unscheduled to 3.0-Beta3
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Completed with ivy