Hervé BOUTEMY schrieb:
Ok the archives arn't build right, the libs arn't copied into the new
archives....
I'm using the following lines:
<artifact:dependencies pomRefId="maven.project"
filesetId="dependency.fileset" useScope="runtime"/>
<copy todir="${war.dir}/WEB-INF/lib">
<!--<fileset dir="${lib.dir}">
<include name="richfaces-impl*.jar" />
<include name="richfaces-ui*.jar" />
<include name="oscache*.jar" />
<include name="commons-digester.jar" />
<include name="commons-beanutils.jar" />
<include name="jsf-facelets.jar" />
<include name="jboss-seam-*.jar" />
<exclude name="jboss-seam-gen.jar" />
</fileset>-->
<fileset refid="dependency.fileset"/>
<mapper classpathref="maven-ant-tasks.classpath"
classname="org.apache.maven.artifact.ant.VersionMapper"
from="${dependency.versions}" to="flatten" />
</copy>
notice that the fileset which is commented was the initial ant script,
which copied the libs from the local ./lib folder ...
Am I missing something, or is the code simply wrong..?
Think this would be the last problem!
Thanks,
Greets
yes, with pomRefId, it should work better:
<artifact:dependencies pomRefId="maven" filesetId="dependency.fileset"
useScope="runtime"/>
Le lundi 05 mai 2008, roman schoenbichler a écrit :
Ok sry.. how should it work with an empty artifact:dependencies.... So
now he can resolve the dependencies... hope the rest will work..
Greets
Hey again!
Thanks for your reply, this basicly looks like what I need.. but
unfortunately the ant script isn't working. Maybe my Ant knowledge
isn't enough, but I think the documentation got a bit short on this.
Anyway.. my ant file includes
<path id="maven-ant-tasks.classpath"
path="lib/maven-ant-tasks-2.0.9.jar" />
<typedef resource="org/apache/maven/artifact/ant/antlib.xml"
uri="urn:maven-artifact-ant" classpathref="maven-ant-tasks.classpath" />
<artifact:pom id="maven" file="pom.xml" />
and
<artifact:dependencies filesetId="dependency.fileset"
useScope="runtime"/>
to which I now refere when copying the libs to the .ear file.
But now ant fails during compilation because it simply can't resolve
any imports pointing to the libs included by maven (the pom).
Hm... I would realy appreciate some help!
Greets
Hi Roman,
If I understand what you're trying to do, I'd say it's the same as
the "Declaring Dependencies" section of the documentation:
http://maven.apache.org/ant-tasks.html
look at "For example, to populate WEB-INF/lib with your dependencies
you could use the following:"
If the doc is not clear, don't hesitate to propose other words to
explain the case and open a Jira issue: it's written with best
efforts, we need review and help to improve it. Source is here:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/ant-tasks.apt
regards,
Hervé
Le samedi 03 mai 2008, roman schoenbichler a écrit :
Hey Guys!
I'm currently working with seam. They have a project generation script.
This sets up a project, including a build.xml file. The Problem with
this script is, that it copies all libs in the generated project which
is not nice at all.
So I started using maven-ant-tasks.
The problem is, that I wasn't able to figure out how I can copy the
needed lib files to the generated .ear project from my local
repository.
The generated script uses:
<fileset id="lib" dir="${lib.dir}">
<include name="*.jar" />
</fileset>
with lib.dir pointing to ./lib, which of corse is not very usefull
since
my libs are in the .m2 repository.
The description on the website isn't very clear about such functions.
I hope you can help me on that,
Greets
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
