Hi,
I would like know how to go about this scenario.
I would like to create an exploded war with the following differences to
what the standard war plugin created
* instead of placing all compiled classes from src/main/java into
WEB-INF/classes/com/comp/etc I would like them to
be compiled into a jar and put in the WEB-INF/lib.
* I would like to assign certain resource not to be put in the above
described jar, and some to be put into the jar. e.g., some
properties files need not be changed except bij the developer, but log4j
files for instance could be changed by the deployer.
Any idea's on how to automate this process?
Regards,
Wouter

Hi,

can't you just create an extra jar project for the java sources and resources you don't
want to end in WEB-INF/classes and declare it as a dependency.

Hope this helps
-Tim

Wouter de Vaal schrieb:
Hi,

I would like know how to go about this scenario.
I would like to create an exploded war with the following differences to
what the standard war plugin created
* instead of placing all compiled classes from src/main/java into
WEB-INF/classes/com/comp/etc I would like them to
be compiled into a jar and put in the WEB-INF/lib.
* I would like to assign certain resource not to be put in the above
described jar, and some to be put into the jar. e.g., some
properties files need not be changed except bij the developer, but log4j
files for instance could be changed by the deployer.

Any idea's on how to automate this process?

Regards,
Wouter

To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org

Thanks for you suggestions.

Simply put, create an extra pom? I would like to keep all code within the
same eclipse project because of testability.

Wouter

5/11/06, Tim Kettler <tim.kettler (AT) udo (DOT) eduwrote:
--
Hi,

can't you just create an extra jar project for the java sources and
resources you don't
want to end in WEB-INF/classes and declare it as a dependency.

Hope this helps
-Tim

Wouter de Vaal schrieb:
Hi,

I would like know how to go about this scenario.
I would like to create an exploded war with the following differences to
what the standard war plugin created
* instead of placing all compiled classes from src/main/java into
WEB-INF/classes/com/comp/etc I would like them to
be compiled into a jar and put in the WEB-INF/lib.
* I would like to assign certain resource not to be put in the above
described jar, and some to be put into the jar. e.g., some
properties files need not be changed except bij the developer, but log4j
files for instance could be changed by the deployer.

Any idea's on how to automate this process?

Regards,
Wouter
>
>
>

To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
--

Yesterday i tried to generate the files needed for Eclipse
(.project, .classpath) with eclipse:eclise for a multi-project. It created
for every module a separate pair of files.

Is there a possibility to create only one Eclipse configuration for the master
project? With that we could have NE Eclipse project with source directories
for every module.

Regards
-chris

Am Donnerstag, 11. Mai 2006 10:16 schrieb Wouter de Vaal:
Thanks for you suggestions.

Simply put, create an extra pom? I would like to keep all code within the
same eclipse project because of testability.

Wouter

5/11/06, Tim Kettler <tim.kettler (AT) udo (DOT) eduwrote:
Hi,

can't you just create an extra jar project for the java sources and
resources you don't
want to end in WEB-INF/classes and declare it as a dependency.

Hope this helps
-Tim

Wouter de Vaal schrieb:
Hi,

I would like know how to go about this scenario.
I would like to create an exploded war with the following differences
to what the standard war plugin created
* instead of placing all compiled classes from src/main/java into
WEB-INF/classes/com/comp/etc I would like them to
be compiled into a jar and put in the WEB-INF/lib.
* I would like to assign certain resource not to be put in the above
described jar, and some to be put into the jar. e.g., some
properties files need not be changed except bij the developer, but
log4j files for instance could be changed by the deployer.

Any idea's on how to automate this process?

Regards,
Wouter

To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org

Diese E-Mail wurde auf Viren ueberprueft.
mailsweeper (AT) it2media (DOT) de

To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org