Hello, this is my first post to this list. Usually, I can find any
information I need to use Maven. But, nowadays, because my company is
migrating from Ant to Maven and we have a lot of specific targets, I need to
appeal to this mailing list.
So, we are doing the migration following the steps below:
1. Put projects in Maven layout
2. Split some projects in "many modules project"
3. Migrate Ant tasks.

Doing theses steps we have some doubts.

Our environment: We have a set of internal projects that work more like libs
to other real projects. So, we desire to add these internal libs as maven
managed dependencies, we´ve even created an internal remote repository to
deploy them. Right now, these libs have only classes, but to us, in a
logical view, they must contain all artifacts related to them - like JSPs,
pictures, and so forth.

First: We have more than one project that share the same web application
structure. In other words, all web artefacts for those projects - including
jsp - are in the same directory/eclipse project, without modules. My
question is: how can I separate web application part in modules and later
take only a single war with all artifacts? How can can separate these
projects and keep taking my whole webapp?

Second: I have some ant´s targets that create jars for java web start
clients. These jars have classes that are part of the dependencies - for
example, from commons-beans. Using Ant, I put these classes in jws's jar
using a zipfileset:

<zipfileset id="jar.commons-beans" src="${libs}/commons-beans.jar">
   <include name="org/apache/..." />
   ...
</zipfileset>

Of course, I manage the dependency manually, so, I could reference it in
"src" attribute. Using maven, how can I do it? I am already using the antrun
plugin, but I don't know how to reference a dependency jar inside pom.xml.
Do you have any suggestions? Maybe I can use maven-webstart plugin, but how
do I filter classes inside a dependency?

ps.: sorry my poor English.

--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
http://blastemica.blogspot.com

Reply via email to