Hi David,
David Weintraub wrote at Donnerstag, 25. Juni 2009 17:34:
1/ A POM is not a programming language, but a project description. It is
pointless to define the properties section in the top of the file in the
hope that Maven sees the values first before you use them. You can
call mvn
1/ A POM is not a programming language, but a project description. It is
pointless to define the properties section in the top of the file in the
hope that Maven sees the values first before you use them. You can
call mvn help:effective-pom to see what Maven actually uses for the
project
Well, could you give us at least an excerpt of your pom?
I'm guessing you want to use some jar and didn't acknowledge the local maven
repository existence, but I might be wrong.
In fact you seem to be trying to directory use some given jar that's been
produced by another projet.
But this is all
The base directory's POM.xml:
project
modelVersion4.0.0/modelVersion
properties
base.version2.1.2-SNAPSHOT/base.version
/properties
groupIdcom.solbright/groupId
version${base.version}/version
artifactIdbase/artifactId
packagingpom/packaging
namebase/name
Hi David,
[sorting the mail]
Another question: I build the base.jar file, and the other two
projects depend upon that file. I've setup the POMs to show this
dependency: Everything builds, but when I run analyze:dependency, it
tells me it is missing base.jar
[snip]
The base directory's
I have a project (it's actually a sub-project of another project, so
it will get interesting).
We build three items: base.jar, base-ui.jar, and base-hib.har. These
each are in their own sub-directory, and I can treat them like
projects. I was able to get the whole thing working. However, the
