Jar instead of classes dir in War

Hello Wouter,
You can also make eclipse projects depend on one and another. This makes
seperation of concerns, and other boundaries a lot easier to manage.
There are several places where you can configure such dependencies for
eclipse projects: J2EE Module Dependencies, Project References, Java
Build Path -Projects.
Also, you can add the project to the classpath of Tomcat (or any other
server you deploy the project to) by modifying the launcher's classpath
settings.

Play with these settings a little and you'll probably get it working,
because I don't know exactly how it should be done.

Matthijs

Wouter de Vaal wrote:
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
>>
>>
>