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

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

The idea is that the application can be made as a standards-compliant web 
application (war file) that can deployed in any standard application server 
(enterprise policy blah, blah..). It can also utilize any standard web 
technology and development tool (great advantage: there are lots of them). Yet, 
it deploys as easy as any main-method program, because it IS a main-method 
program that uses the application server as a library. 

thus: jetty is not used for testing, but for production. 

This is almost the same as an executable war, but not quite as the war file is 
a standard web app and we use a separate module bundles the appserver, a main 
method and the war file as a library. 

And the bug is this: appassebler correctly downloads all jar file dependencies 
to the target/appassembler/repo dir, but newer versions of appassembler 
mysteriously omits the war file dependency, even if it is declared the same way 
as the other dependencies. I wish that all dependencies (still) were treated 
the same way even if they have other maven classifiers and types than jar 
files. 

I'll look into creating an example in a few days. 
                
> 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