maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <br...@apache.org>
Subject Re: [RANT] This Maven thing is killing us....
Date Wed, 05 Jul 2006 12:50:27 GMT
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 <brett@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message