[
http://jira.codehaus.org/browse/MJBOSSPACK-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208105#action_208105
]
Brent N Atkinson commented on MJBOSSPACK-35:
--------------------------------------------
I could not disagree more.
When developing a full-fledged j2ee application with wars, ejbs, and true JCA
connectors (not just JDBC adapters) you often want to package the dependencies
at the ear level to ensure proper class-loading and to limit size.
The dependency tree gives you the flexibility to bundle it how you like. It
also allows proper dependency management. The fact that wars bundle *and*
depend on the libraries is at least unconventional and at worst incorrect in
the current Maven dependency resolution scheme. It only works because wars are
often end-of-the-line artifacts so the inaccurate information isn't used
downstream.
I have multiple ear projects that bundle sars just like any other artifact. For
sar dependencies that will be bundled by the application packaging (the ear) I
declare them as provided which prevents the dependencies from being used
transitively.
Modeling this after the war plugin is probably not the best decision. The
warpath plugin was made specifically to make up for the mess that the war
plugin made of the dependency tree (and the artifacts themselves). If there is
functionality added to do this, I'd ask that it be an option and disabled by
default.
> EAR projects shouldn't pack SAR dependencies
> ---------------------------------------------
>
> Key: MJBOSSPACK-35
> URL: http://jira.codehaus.org/browse/MJBOSSPACK-35
> Project: Maven 2.x JBoss Packaging Plugin
> Issue Type: Bug
> Components: sar
> Affects Versions: 2.1
> Environment: Vista, maven 3.0 alpha 6,
> jboss-packaging-maven-plugin-2.1.1
> Reporter: Fred Bricon
>
> I believe that, when packing an EAR which depends on a SAR module, the SAR
> dependencies shouldn't be included in the EAR package. It should behave like
> WAR modules. Currently, when adding a SAR to an EAR, I need to manually
> exclude its dependencies from the EAR.
> I don't pretend to be an expert at SAR (I just started to develop one), so I
> can be wrong.
> I don't know if the same behavior should apply to the other jboss packagings,
> but think about it.
> regards,
> Fred Bricon
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
