Hi,
I don't like the way the jboss plugin works. ATM, it assumes the EAR and
the jboss packaging is done in the same project. I think they are 2
separate activities that should be done in 2 separate projects. Why?
Because packaging something in JBoss can mean packaging several modules:
An EAR module, an EJB-JAR one, a WAR one, etc. and this won't work in a
single project.
Proposal:
* Add a <jboss.bundle> property for dependencies. Example:
<dependencies>
<dependency>
<groupId>everest</groupId>
<artifactId>registration</artifactId>
<version>1.0-SNAPSHOT</version>
<type>ear</type>
<properties>
<jboss.bundle>true</jboss.bundle>
</properties>
</dependency>
</dependencies>
* Keep only a jboss:package goal (remove the jboss:package-ear, etc) as
they are no longer needed. The modules to package are now listed in the
dependencies list
If no one has any objection, I'll implement this in the coming 1-2 days.
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
