[ 
https://jira.codehaus.org/browse/MAPPASM-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296280#comment-296280
 ] 

Eirik Maus commented on MAPPASM-158:
------------------------------------

It's not a bug, but a weird idea that turned out to work better than expected. 

Appassembler (and assembly-plugin) makes it really easy to make stand-alone 
applications in archives that can be downloaded, unzipped and run anywhere with 
only a few commands (3, to be exact). This can be done, even if the application 
expose its user interface through http. All you need is to bundle some 
http-library stuff and some web-library stuff that can provide user interaction 
help. This is similar to using swing libraries to expose a swing user interface 
(okay, they are bundled in the jdk now, but initially they weren't). The main 
method starts jetty (5 - 10 lines of code), locates the war file in the 
classpath (10 lines of code) and tells jetty to load the war file. voila! Just 
as easy as opening a main JWindow. 

                
> war file dependencies not included since version 1.0-alpha-2
> ------------------------------------------------------------
>
>                 Key: MAPPASM-158
>                 URL: https://jira.codehaus.org/browse/MAPPASM-158
>             Project: Mojo AppAssembler Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>         Environment: linux and windows, jdks 6 and 7. maven 3. 
>            Reporter: Eirik Maus
>
> Tried to update maven and plugins on and old project that uses appassembler 
> and assembly-plugin to create a bundle containing jetty.jar some other stuff 
> and a war-file with the web-app I want to run through jetty. I cannot make 
> any other version of appassembler than 1.0-alpha-2 include the war file in 
> the assembly, even if it is declared with scope 'runtime'. 
> It seems like after 1.0-alpha-2, only jar files are included. If this is a 
> deliberate feature, I want a switch to allow the inclusion of the war file 
> again. 
> In order to reproduce:
> # create a multi-module maven project. 
> # create a war module inside that project. 
> # create a "normal" module inside that project that uses appassembler and has 
> dependency to the war module with dependency type:'war' and scope:'runtime' 
> (and also some other jar dependencies). 
> # run 'mvn clean install' on the whole thing and note that the war file is 
> not present under the target/appassembler directory unless the appassembler 
> version is set to 1.0-alpha-2. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to