maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard van Nieuwenhoven (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling
Date Fri, 26 Oct 2007 16:07:52 GMT


Richard van Nieuwenhoven commented on MECLIPSE-333:

as far as i know one should not make a dependency between war's. Does the war plugin handle
such things at all?

When i need such a requirement i use a system like tobago uses. a jar resource that will be
extracted in the dependent war resource .

As far as i know WTP has no other way to split the WebContent into to directories or even
in two modules/projects.

The classes of a dependent jar will never be exploded in the WEB-INF/classes directory. WTP
will package your dependent jar into WEB-INF/lib, as it should! and as maven does!
WTP will also do the hot deployment of your changed classes during debugging so no need of
copying classes. When it can't update them just do a republish.


> WTP-2.0 support with howto apt, refactoring and  contextroot handling
> ---------------------------------------------------------------------
>                 Key: MECLIPSE-333
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: multiproject, WTP support
>    Affects Versions: 2.5
>            Reporter: Richard van Nieuwenhoven
>            Assignee: Brian Fox
>         Attachments: maven-eclipse-plugin_only_new.tar.gz, wtp-2.0-and-more-2.5-SNAPSHOT.patch
> This patch contains:
> - WTP.2.0 support for ear and war's (includes MECLIPSE-264)
> - context root handling very much improved
>       (war takes configuration from the ear, if available)
> - refactoring (constant usage, foreign plug-in access centralized)
> - a detailed description how we use maven-2 with WTP in multi module projects
> - testing code included
> the patch is attached, together with a tar with all the new files.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message