Are you sure esb does not appear anywhere else in your pom or any parent pom?
Scott Ryan President/CTO Soaring Eagle L.L.C. Highlands Ranch, Co. 80129 (303) 263-3044 [EMAIL PROTECTED] www.soaringeagleco.com On Thu, Sep 4, 2008 at 2:45 PM, Lam Hayward <[EMAIL PROTECTED]>wrote: > I have exactly the same <packaging> and <plugin> as yours. > > <modelVersion>4.0.0</modelVersion> > <groupId>myCompany</groupId> > <artifactId>myEsb</artifactId> > <packaging>jboss-esb</packaging> > <version>1.0-SNAPSHOT</version> > <name>myEsb</name> > > I use jboss-esb for packaging. > > The codehause plugin jar was downloaded to my local repository. > Everything seems to be there. > > Even if I run "mvn compile", I get the same error. > > $ mvn compile > [INFO] Scanning for projects... > [INFO] > ------------------------------------------------------------------------ > [INFO] Building esb > [INFO] task-segment: [compile] > [INFO] > ------------------------------------------------------------------------ > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Cannot find lifecycle mapping for packaging: 'esb'. > Component descriptor cannot be found in the component repository: > org.apache.mav > en.lifecycle.mapping.LifecycleMappingesb. > [INFO] > ------------------------------------------------------------------------ > [INFO] For more information, run Maven with the -e switch > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: < 1 second > [INFO] Finished at: Thu Sep 04 16:44:04 EDT 2008 > [INFO] Final Memory: 2M/4M > [INFO] > ------------------------------------------------------------------------ > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott > Ryan > Sent: September 4, 2008 4:33 PM > To: Maven Users List > Subject: Re: Jboss ESB and Maven > > Here are some relevant sections of my pom > > <packaging>jboss-esb</packaging> > > <build> > <resources> > <resource> > <directory>src/main/resources</directory> > <filtering>true</filtering> > </resource> > </resources> > <plugins> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>jboss-packaging-maven-plugin</artifactId> > <extensions>true</extensions> > </plugin> > </plugins> > </build> > > > > Scott Ryan > President/CTO > Soaring Eagle L.L.C. > Highlands Ranch, Co. 80129 > (303) 263-3044 > [EMAIL PROTECTED] > www.soaringeagleco.com > > > On Thu, Sep 4, 2008 at 2:23 PM, Lam Hayward > <[EMAIL PROTECTED]>wrote: > > > I figured the directory structure would be similar to regular maven > > project. So, I have the following: > > > > src/main/java > > src/main/resources > > src/test/java > > src/test/resources > > > > I followed your suggestion to move the deployment.xml and > > jboss-esb.xml to src/main/resources/META-INF directory. > > > > In the pom.xml file, I specified <packaging>jboss-esb</packaging> and > > > > <build> > > <plugins> > > .... > > <plugin> > > <groupId>org.codehaus.mojo</groupId> > > <artifactId>jboss-packaging-maven-plugin</artifactId> > > > > <!-- Enable packaging types and lifecycle bindings. --> > > <extensions>true</extensions> > > </plugin> > > .... > > </plugins> > > </build> > > > > When I run "mvn install", it complains: > > > > $ mvn install > > [INFO] Scanning for projects... > > [INFO] > > ---------------------------------------------------------------------- > > -- > > [INFO] Building esb > > [INFO] task-segment: [install] > > [INFO] > > ---------------------------------------------------------------------- > > -- > > [INFO] > > ---------------------------------------------------------------------- > > -- > > [ERROR] BUILD ERROR > > [INFO] > > ---------------------------------------------------------------------- > > -- [INFO] Cannot find lifecycle mapping for packaging: 'esb'. > > Component descriptor cannot be found in the component repository: > > org.apache.mav > > en.lifecycle.mapping.LifecycleMappingesb. > > [INFO] > > ---------------------------------------------------------------------- > > -- [INFO] For more information, run Maven with the -e switch [INFO] > > ---------------------------------------------------------------------- > > -- > > [INFO] Total time: < 1 second > > [INFO] Finished at: Thu Sep 04 16:16:44 EDT 2008 [INFO] Final Memory: > > 2M/4M [INFO] > > ---------------------------------------------------------------------- > > -- > > > > It didn't seem to compile the code. The target directory has empty > "lib" > > directory and empty "META-INF" directory. > > > > Is there something missing? > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > Scott Ryan > > Sent: September 4, 2008 3:50 PM > > To: Maven Users List > > Subject: Re: Jboss ESB and Maven > > > > We have used the plugin with great success and can send you our layout > > > but basically use the standard maven 2 structure as follows > > > > src/main/java > > src/main/resources > > > > put the jbm-queue-service.xml file in the resources directory and the > > following files in the resource/META-INF directory > > > > deployment.xml > > jboss-esb.xml > > > > Let me know if i can help in any way. > > > > Scott Ryan > > President/CTO > > Soaring Eagle L.L.C. > > Highlands Ranch, Co. 80129 > > (303) 263-3044 > > [EMAIL PROTECTED] > > www.soaringeagleco.com > > > > > > On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward > > <[EMAIL PROTECTED]>wrote: > > > > > I have a Jboss ESB example project with ant build script to convert > > > to > > > > > maven. Maven usually prefers certain directory structure. There is a > > > > plugin for jboss esb packaging. Is there somewhere I can find the > > > directory structure and pom.xml? > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
