You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Lester Ward <lw...@tagaudit.com> on 2003/05/23 15:50:23 UTC

RE: Newbie: How to configure 3rd party and internal dependencies in project.xml

> > So how do I configure my project.xml to use the 3rd party libraries
> > within Maven's repository?   and,.. 

> If your project is mavenised, you would then use maven 
> jar:deploy to put your artifacts into that repository.

If the lib isn't Mavenized, I usually do this after invoking its build
script (using velocity as an example):

<!-- A property that identifies your local code directory. -->
<property name="jakarta.root" value="<whereever your local source code
is>"/>

<!-- A property locating the output artifact of the library -->
<property name="velocity.output"
value="${jakarta.root}/jakarta-velocity/bin/velocity-1.3.jar"/>

<!-- Velocity builds using Ant, so execute its build process -->
<ant dir="${jakarta.root}/jakarta-velocity/build" inheritAll="false"/>

<!-- Copy the resulting jar file into the Maven directory, so other 
  projects use the one that got compiled instead of some other one. -->
<copy overwrite="true" file="${velocity.output}"
todir="${maven.repo.local}/velocity/jars"/>


Note that all of the tags used in this process happen to be Ant tags, one of
the nice things about Maven.


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


RE: Newbie: How to configure 3rd party and internal dependencies in project.xml

Posted by plim <pe...@correlationtech.com>.
Thanks brett and lester.
My 3rd party libs seems to be working finally, 
but my own libs are still giving me problems.
Guess I can't avoid maven-ising them as well.
pengster



-----Original Message-----
From: Lester Ward [mailto:lward@tagaudit.com] 
Sent: Friday, May 23, 2003 6:50 AM
To: 'Maven Users List'
Subject: RE: Newbie: How to configure 3rd party and internal
dependencies in project.xml


> > So how do I configure my project.xml to use the 3rd party libraries
> > within Maven's repository?   and,.. 

> If your project is mavenised, you would then use maven
> jar:deploy to put your artifacts into that repository.

If the lib isn't Mavenized, I usually do this after invoking its build
script (using velocity as an example):

<!-- A property that identifies your local code directory. --> <property
name="jakarta.root" value="<whereever your local source code
is>"/>

<!-- A property locating the output artifact of the library -->
<property name="velocity.output"
value="${jakarta.root}/jakarta-velocity/bin/velocity-1.3.jar"/>

<!-- Velocity builds using Ant, so execute its build process --> <ant
dir="${jakarta.root}/jakarta-velocity/build" inheritAll="false"/>

<!-- Copy the resulting jar file into the Maven directory, so other 
  projects use the one that got compiled instead of some other one. -->
<copy overwrite="true" file="${velocity.output}"
todir="${maven.repo.local}/velocity/jars"/>


Note that all of the tags used in this process happen to be Ant tags,
one of the nice things about Maven.


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


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