[
https://issues.apache.org/jira/browse/GERONIMO-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507965
]
Sachin Patel commented on GERONIMO-3261:
----------------------------------------
The current packaging mechanism isn't technically incorrect. Geronimo itself
has a much more complex packaging mechanism, and thus some of the default maven
assembly mechnism wouldn't work for it. The current mechanism takes advantage
of moduleSet's in the assembly descriptor and thus it keeps the maintaince of
that file to a minium. Everything in the plugins directory will be
automatically be package for inclusion in the plugins directory and same goes
for the feature. If you moved the assembly as its own module, then you cannot
use moduleSet's and would have to use dependency sets which you'll have to
specifiy every single plugin and feature in the assembly's pom as a dependency
as well redefining which subset of those you want in the assembly descriptor.
> Modify pom.xml so that J2G automatically builds a deployable when the mvn
> install command is issued
> ---------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3261
> URL: https://issues.apache.org/jira/browse/GERONIMO-3261
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: J2G
> Reporter: Jason Warner
> Assignee: Jason Warner
> Priority: Minor
>
> J2G currently requires the use of the assembly:assembly command line argument
> to build the deployable. This should be changed to work similar to other
> parts of geronimo.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
