[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2516) build path' referenced libraries not included in war

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12422281#action_12422281 ] 

Rob Stryker commented on JBIDE-2516:
------------------------------------

build path is divorced from bundling because often times, one archive needs to compile against another project or some libraries that will already be on the classpath at runtime.  The project (build path) simply needs to have them available at compile time... not run time. 

WTP is what's responsible for the automatic deployment of referenced libraries when NOT using projcet archives. They have a UI, as well, to remove some things from automatic bundling.  But that is meant for WTP-style projcets (which seam projects are).   The export command uses the same WTP logic. 



> build path' referenced libraries not included in war
> ----------------------------------------------------
>
>                 Key: JBIDE-2516
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2516
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Archives
>    Affects Versions: 2.0.1
>         Environment: eclipse 3.3.2, jboss tool 2.0.1.GA (dunno why it's not listed above)
>            Reporter: arne anka
>            Assignee: Rob Stryker
>
> creating a war in archive view (why no entry in context menu? that view is not really intuitive) results in a war not deployable -- jboss complains over not being able to create smth.
> further research shows that libraries referenced in the build path (and _not_ physically located in WEB-INF/libs/) are _not_ included while creating the war.
> deploying the application from the jboss ide includes those libs, though -- but for productive use the app needs to be packed as war and thus include even libs only referenced ...
> a workaround might be to create a fileset by hand -- but because those libs are spread over several places it's a rather tedious task.

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