I have <extensions>true</extensions> . My issues is a jboss-spring artifact gets generated. But when my EAR is deployed to Jboss, the artifact is not picked up when the EAR starts up. Only if the artifact is named with a .spring extension does my EAR start correctly.
How to i force the plugin to spit out .spring extensions like it use to ? thanks for your help On Thu, Feb 28, 2008 at 2:05 AM, nicolas de loof <[EMAIL PROTECTED]> wrote: > I applied a patch provided by jboss developpers to support ESB packaging > (MOJO-841) > @see > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112005&postdays=0&postorder=asc&start=10 > . > > This patch defines custom ArtifactHandlers for all jboss artifact types > including "jboss-spring". > > It seems the plugin must be declared in the POM with > <extensions>true</extensions> so that those ArtifactHandlers get registered. > > Nico. > > > > > 2008/2/27, christopher justin <[EMAIL PROTECTED]>: > > > The latest 2.0 SNAPSHOT produces artifacts with a .jboss-spring > > extension now which JBoss does not recognize on my EAR deployments. This > > appears to have been changed (within the last 30 days) from producing > > .spring artifacts which Jboss recognizes inside the EAR. I have had to > > resort back to a previous 2.0 SNAOPSHOT i had laying around. > > > > How do I get past this issue? Why is it producing .jboss-spring > > extensions now? > > > > I am using JBoss 4.2.1 with the jboss-spring-jdk5-2.5.deployer > > > > thanks for any insight. > > > > > > chris > > >
