[ https://jira.codehaus.org/browse/MNG-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358406#comment-358406 ]
Paul Benedict commented on MNG-1683: ------------------------------------ Is adding a "zip" packaging really going to be part of 3.x? Or 4.0? > type zip for packaging ? > ------------------------ > > Key: MNG-1683 > URL: https://jira.codehaus.org/browse/MNG-1683 > Project: Maven > Issue Type: Improvement > Environment: not significant > Reporter: Olivier Lamy > Fix For: Issues to be reviewed for 3.x > > Attachments: archive+file-plugins.tar.bz2, maven-war-plugin.tar.gz, > maven-zip-plugin.tar.gz, MNG-1683.tar.gz, patch1, temp-test_version.zip > > > Hi, > I don't know if the artifact type zip exists (I think not after few test). > But I want to separate the html content and the webapp content (classes, > configuration files and so on). > The use case is to separate this different works (html designer and java > developpement) and production installation (one is to an http server and the > other is on an app server) in two artifacts with separate versionning. > But the <packaging>zip</packaging> is not recognized. > Then I would like to use it as an artifact with maven's features (snapshot, > pom, version, goals : install, deploy release and all others). > Add it to the webapp dependencies (needed only for developpment or unit > tests). > With this type of dependency the zip content could be unpacked to a directory > in the exploded webapp. (certainly need hack on the maven-war-plugin). > I have certainly the workaround to declare this as jar and using the assembly > plugin to generate a zip. > But I can't use install release deploy or something else to manage the > generated zip which is not an artifact. > Thanks for help or workaround. > - Olivier -- This message was sent by Atlassian JIRA (v6.1.6#6162)