Not a bulletproof one (there's ${user.dir}, but that's only right 90% of
the time). In a multiproject scenario, you might be better off putting
the individual jars in as stubbed projects:
parent pom:
<module>jar-in-svn</module>
...
jar-in-svn/pom.xml: the POM from the repository, but add a copy file.jar
to target/artifactId-version.jar at the package phase.
Cheers,
Brett
On 5/07/2006 7:27 PM, Geoffrey De Smet wrote:
Brett Porter wrote:
Hi Ralph,
There are a couple of options for addressing this use case in Maven.
- include the JARs in SVN, and reference it as an additional
repository file://localhost/${basedir}/extra-jar-repo
When you declare such a repository in your parent pom, the child poms
don't use the parent's basedir, but their own basedir. Is there a
workaround for that problem?
--
Brett Porter <[EMAIL PROTECTED]>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]