You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jerome Lacoste (JIRA)" <ji...@codehaus.org> on 2005/06/21 18:59:52 UTC

[jira] Commented: (MPWAR-41) Ability to merge other war files as dependencies

    [ http://jira.codehaus.org/browse/MPWAR-41?page=comments#action_41800 ] 

Jerome Lacoste commented on MPWAR-41:
-------------------------------------

If you change this issue into: "allow to unpack dependencies in a specific place of the war file", then I would vote for it.

I.e. you specify a dependency like this:

  <dependency>
    <id>myWebstartApp</id>
    <version>1.3</version>
    <type>zip</type>
    <properties>
      <war.target.path>apps</war.target.path>
      <war.unzip>true</war.unzip>
    </properties>
  </dependency>

It's more general and would solve my issue of adding artifacts that are bundled in zip files (*) (e.g. as a result of creating a webapp using jnlp).

(*) that's the only clean&simple way I've found in order to make the resulting numerous signed jars of a particular jnlp module available as a single artifact.

> Ability to merge other war files as dependencies
> ------------------------------------------------
>
>          Key: MPWAR-41
>          URL: http://jira.codehaus.org/browse/MPWAR-41
>      Project: maven-war-plugin
>         Type: New Feature
>     Versions: 1.6
>     Reporter: Grégory Joseph (old account)
>  Attachments: maven-war-includewar.patch
>
>
> In a project I'm working on, we need to be able to separate parts of our web applications, to be able to build different versions, with or without certain features.
> Since some of these "parts" use jsp's, have specific dependencies, etc... we can't just build them as jars.
> I've made the attached patch in order to be able to specify a dependency of type war and have it included in my "master" war. 
> Note that for this to work, the dependent war should not have a web.xml, for instance. As it is, it simply unwar's the dependency in the main build directory. It might be desired to actually run this *before* copying the resources from the master project, so that at least they don't get overwritten by the dependencies'. 
> Currently, the META-INF content and the web.xml are excluded from the unwar task, maybe more excludes should be added?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org