On Friday, December 02, 2011 10:15:22 AM David Jencks wrote: > On Dec 2, 2011, at 2:39 AM, Jeremy Hughes wrote: > > On 2 December 2011 03:49, David Jencks <[email protected]> wrote: > >> released - contains version properties for dependencies at the oldest > >> released version we expect the project bundle to work against> > > would we have to do this using a set of maintained properties files? > > Where would this go - in the parent pom, the top level module pom or > > the bundle pom. There's a file her > > http://svn.apache.org/repos/asf/aries/trunk/aries_release_versions.txt > > which is supposed to reflect the latest versions - although I think a > > maven plugin could be written and teased into figuring out the latest. > > I think the versions need to be maintained in each (leaf) pom for artifacts > we release. Otherwise there's no good way to release single artifacts. > > There's the versions-maven-plugin > http://mojo.codehaus.org/versions-maven-plugin/ that helps with updating > versions but I don't know if it is smart enough to work with version > properties in a profile. If the plugin doesn't work, if we use a > consistent version naming scheme its easy enough to use an IDE's > search-and-replace to update properties.
We could also try an import scoped dependency of some sort. Basically, have a pom someplace that defines an dependencyManagement thing that lists ALL the Aries jars and their current SNAPSHOT version and another one that lists ALL of the latest releases (which means it would need to be part of each release). A profile could selectively depend on the one that is needed. Pretty much would remove all the version numbers from everywhere. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
