Re: including project local jars as a dependency

2005-10-29 Thread Hervé BOUTEMY
I had the same need and found that system scope could do the job. For example, I replaced following lines in project.properties : maven.jar.activation=${basedir}/lib/activation.jar with following lines in pom.xml : dependency groupIdjavax.activation/groupId

Re: including project local jars as a dependency

2005-10-29 Thread Brill Pappin
what is the lib relative to in your example? - Brill On 10/29/05, Hervé BOUTEMY [EMAIL PROTECTED] wrote: I had the same need and found that system scope could do the job. For example, I replaced following lines in project.properties : maven.jar.activation=${basedir}/lib/activation.jar

Eclipse plugin broken? Was: Re: including project local jars as a dependency

2005-10-29 Thread Brill Pappin
I just tried the system scope as suggested, however when running the eclipse:eclipse goal, it sets the file path to: classpathentry kind=var path=M2_REPO/main/libs/ireasoning-snmp-v3.jar/ which is clearly incorrect as the M2_REPO var points at the local repository... is this something broken in

including project local jars as a dependency

2005-10-28 Thread Brill Pappin
In Maven 1 I used to be able to include project local jars and include them in the dependency list with an override property. This is important to be able to do it so that a build can include private jars where a repository is *not* an option (I have several such cases). How do I do that in m2?