[ http://jira.codehaus.org/browse/MNG-2152?page=all ]
Brett Porter closed MNG-2152.
-----------------------------
Assignee: Brett Porter
Resolution: Won't Fix
Fix Version/s: (was: 2.0.5)
it depends on what you are using to produce the SAR.
Many Maven plugins already support configuration to disable it (see the guides
page, regarding configuring archive plugins). If it is a plugin, then it needs
to be filed against the plugin, not Maven. Thanks.
> pom.xml and pom.properties in JAR file causes JBOSS SARDeployer to fail.
> ------------------------------------------------------------------------
>
> Key: MNG-2152
> URL: http://jira.codehaus.org/browse/MNG-2152
> Project: Maven 2
> Issue Type: Bug
> Components: POM, Plugin API
> Affects Versions: 2.0.1
> Environment: Windows, JBOSS-4.0.1sp1
> Reporter: Walt Barrow
> Assigned To: Brett Porter
> Attachments: ESS-PD-1.1-DEV.sar
>
>
> I am creating a JAR file which is then packaged into JBOSS MBean Service
> Archives (SARs). When the JAR file is created it contains the following
> files:
> META-INF\maven\SJL\WorkflowManagerMBean\pom.xml
> META-INF\maven\SJL\WorkflowManagerMBean\pom.properties
> The JAR file is then embedded into a SAR file which is nothing more than a
> JAR file with a ".sar" extension plus a special jboss-service.xml file.
> When I try to deploy the SAR to JBOSS, it fails because it cannot resolve the
> classloader for the classes in the JAR file. When I remove the pom.xml file
> from the embedded JAR file, then the SAR file deploys properly.
> Is this a known issue? Is there any way to surpress the inclusion of the
> pom.xml file in the target JAR file?
> Perhaps there should be a mechanism to surpress such information should the
> need arise.
> Thank you!
--
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
