Hi,
I'm using maven 2.0.1 for AndroMDA's build (its a fairly large
multiproject build).
It appears that if I have a "version" property in my System properties,
it sometimes gets picked up and used for the version of my project when
creating the final name (during pom interpolation I'm assuming). I
then get an unresolved dependency error because of course the version is
not the one defined as the version in my pom.xml. Is this a know issue
and shouldn't information in the pom take precedence over System
properties? I'm assuming this call in DefaultMavenProjectBuilder is the
culprit (since this context is then passed to the
RegexBasedModelInterpolator for use in project interpolation) :
// TODO: Clean this up...we're using this to 'jump' the
interpolation step for model properties not expressed in XML.
// [BP] - Can this above comment be explained?
// We don't need all the project methods that are added over
those in the model, but we do need basedir
Map context = new HashMap( System.getProperties() );
I also have a similar issue with ${basedir}, the value that sometimes
gets picked up, is the value for the previous project (which of course
breaks the build), I resorted to using ${pom.basedir} which seems to fix
things. I've tried using "${pom.version}" instead of "${version}" to
fix my issue with the wrong version, however it doesn't help because it
looks like the DefaultModelInheritanceAssembler sets the final name as
"${artifactId}-${version}" (I put some debug in that code to see what
was being set). For now I've put a hack in one of my m2 plugins to
remove the "version" System property (not sure where its coming from
really) so that I can get past this, but of course this isn't the best
solution :)
Thanks,
Chad
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
