Here's a little further information I've been able to glean. If I look at
the ivy.xml files that have been generated in the dedicated Ivy cache for
the source Maven repository, I see that they are referring to the source and
javadoc artifacts--even though those artifacts are not there for the
trans
Here's an excerpt from a pom of a dependency I'm using:
javax.enterprise
cdi-api
org.jboss.weld
weld-api
org.jboss.weld
weld-spi
You'll notice there aren't any versions defined here, so maven is going to use
Dear all,
Thank you for your input to my question. It seems to me that
ivy:buildlist will not generate a different build order dependant on the
configuration and having read the comment from Mitch
Also, I would dispute one assumption you make in response to Alex:
"however, why should I hav
Jumping in late to the party here...
Our versioning pattern is major.minor.revision, which is populated using two
variables major.minor are set at a release level (and can be calculated to a
branch in Subversion), and revision matches the last-changed revision of the
particular module.
Works well
