Hi,
You can use a j2ee project with all your dependencies, and you create
child projects that extend of j2ee project.
j2ee project :
<project>
...
<dependencies>
<!-- j2ee dependencies -->
...
</dependencies>
...
</project>
child projects:
<project>
<extend>j2eeProject.xml</extend>
...
<dependencies>
<!-- Your dependencies -->
...
</dependencies>
</project>
Emmanuel
-----Message d'origine-----
De: Michal Maczka <[EMAIL PROTECTED]>
A: "'Turbine Maven Users List'" <[EMAIL PROTECTED]>
Date: 12/11/02
Objet: RE: Ear plugin - how can I set dependency
>unfortunately, you can't. There are various known issues with
dependencies.
>http://www.mail-archive.com/turbine-maven-dev@;jakarta.apache.org/msg046
46.h
tml
>I didn't get a response from anyone so don't know when this will be
>adressed.
Hi Nathan!
I read your previous post (thanks for a link!)
>Hi,
>I'm looking into improving the dependency code to cope with non-jar
artifacts - e.g. war, ejb, told etc. Also multiple artifacts within a
>dependency.
>For clarity: I understand a dependency to be a collection of artifacts.
A
dependency equates to a single subdirectory within the repository >e.g.
struts.
>I think two things are missing from the current dependency structure.
>1) Dependencies should work for file types other than jar.
>2) A dependency should be able to consist of more than 1 file. e.g. a
dependency on struts version 1.0.2 would be to a jar file and 4 tld
>files.
If I can add my 2 cents.
It think that it will be nice to go even further.
E.G. Usually J2EE application requires a lot of different APIs EJB, JTA,
JNDI, JAXP, Servlets etc.
It would be nice to have a single dependency descriptor for a bunch of
folders in repository
For example if I will write:
<dependency>
<id>j2ee</id>
...
<dependency>
and voila: JTA, JNDI and other APIS are already included in my list of
dependencies.
It would nice if one has a possibility of defining such shortcuts by
itself.
I am not saying that this is the best and the smartest example but just
an
illustration of the idea.
I will study it more deeply and try to give you a feedback.
But I think that those things are needed badly and there is no way to
make
plugins to cooperate with one another without
such facility. For example it will be much easier to write Cactus plugin
if
war, ear, ejb, appserver plugins were already
tightly integrated.
Michal
--
To unsubscribe, e-mail:
<mailto:turbine-maven-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:turbine-maven-user-help@;jakarta.apache.org>
__________________________________________________
Modem offert : 150,92 euros rembours�s sur le Pack eXtense de Wanadoo !
Haut d�bit � partir de 30 euros/mois : http://www.ifrance.com/_reloc/w
__________________________________________________
Modem offert : 150,92 euros rembours�s sur le Pack eXtense de Wanadoo !
Haut d�bit � partir de 30 euros/mois : http://www.ifrance.com/_reloc/w
--
To unsubscribe, e-mail: <mailto:turbine-maven-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-maven-user-help@;jakarta.apache.org>
