You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Rune Flobakk <rf...@online.no> on 2008/09/04 12:31:39 UTC
maven-dependency-plugin 2.0 fails when running eclipse:eclipse
Hello,
On my project we have quite a large codebase separated in several Maven multimodule projects. In one of the parent poms I have configured to use maven-dependency-plugin to verify that we use dependencies appropriately, as described here:
http://maven.apache.org/plugins/maven-dependency-plugin/examples/failing-the-build-on-dependency-analysis-warnings.html
Snippet from our parent pom:
<build>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
</plugin>
</plugins>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.0</version>
<executions>
<execution>
<id>analyze</id>
<phase>verify</phase>
<goals>
<goal>analyze-only</goal>
</goals>
<configuration>
<failOnWarning>true</failOnWarning>
<ignoreNonCompile>true</ignoreNonCompile>
</configuration>
</execution>
</executions>
</plugin>
...
</pluginManagement>
</build>
When I run any lifecycle phase including verify (e.g. install, deploy) from that parent pom, every child module gets its dependency use checked, and the build fails on violations. All well!
But when I run eclipse:eclipse and specifies a "workspace" pom, which only lists modules from many different projects, some external to this project but still internal to the organization, for some reason Maven seems to do "something" with the maven-dependency-plugin execution config for that one multimodule project. The problem as I understand it, is that the projects involved in the "workspace" pom uses different versions of maven-dependency-plugin, and I see that Maven downloads both 2.0-alpha-4 and 2.0 when I run eclipse:eclipse.
The error message I get from Maven is this:
[INFO] ------------------------------------------------------------------------
[INFO] Building project-x
[INFO] task-segment: [eclipse:eclipse]
[INFO] ------------------------------------------------------------------------
[INFO] Preparing eclipse:eclipse
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] 'analyze-only' was specified in an execution, but not found in the plugin
[INFO] ------------------------------------------------------------------------
When building project-x on its own, everything is OK. So why does Maven get confused on which plugin version it should use when the project-x is included as one of many modules of a super-super-pom?
Sorry for a very verbose mail, I hope it's possible to understand the problem. Thanks in advance for any help :)
Regards,
Rune Flobakk
Re: Jboss ESB and Maven - success!!
Posted by Scott Ryan <sc...@theryansplace.com>.
http://repository.jboss.com/maven2
should have all the jboss stuff
Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 3:05 PM, Lam Hayward <Ha...@lac-bac.gc.ca>wrote:
> I created a brand new Java project from eclipse and all the maven
> directory from scratch. It works now!!
>
> It produced the .esb file.
>
> Thanks.
>
> In terms of jar dependency, a lot of the jboss esb jars can't be found
> in maven repo. Do you simply add them to your local repository? Or is
> there a repository out there I should reference?
>
> -----Original Message-----
> From: Lam Hayward [mailto:Hayward.Lam@lac-bac.gc.ca]
> Sent: September 4, 2008 4:47 PM
> To: Maven Users List
> Subject: RE: Jboss ESB and Maven
>
> Only one <packaging> element is in the pom.xml. That should be ok.
>
> The error shows "esb" is a very strange.
>
> -----Original Message-----
> From: sryan737@gmail.com [mailto:sryan737@gmail.com] On Behalf Of Scott
> Ryan
> Sent: September 4, 2008 4:36 PM
> To: Maven Users List
> Subject: Re: Jboss ESB and Maven
>
> Are you sure the packaging is jboss-esb rather than just esb as the
> error message states? I got the same error you did when i changed my
> packaging to just esb. Make sure you only have one packaging entry.
>
>
> Scott Ryan
> President/CTO
> Soaring Eagle L.L.C.
> Highlands Ranch, Co. 80129
> (303) 263-3044
> scott@theryansplace.com
> www.soaringeagleco.com
>
>
> On Thu, Sep 4, 2008 at 2:23 PM, Lam Hayward
> <Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
> > scott@theryansplace.com
> > www.soaringeagleco.com
> >
> >
> > On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward
> > <Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Jboss ESB and Maven - success!!
Posted by Lam Hayward <Ha...@lac-bac.gc.ca>.
I created a brand new Java project from eclipse and all the maven
directory from scratch. It works now!!
It produced the .esb file.
Thanks.
In terms of jar dependency, a lot of the jboss esb jars can't be found
in maven repo. Do you simply add them to your local repository? Or is
there a repository out there I should reference?
-----Original Message-----
From: Lam Hayward [mailto:Hayward.Lam@lac-bac.gc.ca]
Sent: September 4, 2008 4:47 PM
To: Maven Users List
Subject: RE: Jboss ESB and Maven
Only one <packaging> element is in the pom.xml. That should be ok.
The error shows "esb" is a very strange.
-----Original Message-----
From: sryan737@gmail.com [mailto:sryan737@gmail.com] On Behalf Of Scott
Ryan
Sent: September 4, 2008 4:36 PM
To: Maven Users List
Subject: Re: Jboss ESB and Maven
Are you sure the packaging is jboss-esb rather than just esb as the
error message states? I got the same error you did when i changed my
packaging to just esb. Make sure you only have one packaging entry.
Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 2:23 PM, Lam Hayward
<Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
> scott@theryansplace.com
> www.soaringeagleco.com
>
>
> On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward
> <Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Jboss ESB and Maven
Posted by Lam Hayward <Ha...@lac-bac.gc.ca>.
Only one <packaging> element is in the pom.xml. That should be ok.
The error shows "esb" is a very strange.
-----Original Message-----
From: sryan737@gmail.com [mailto:sryan737@gmail.com] On Behalf Of Scott
Ryan
Sent: September 4, 2008 4:36 PM
To: Maven Users List
Subject: Re: Jboss ESB and Maven
Are you sure the packaging is jboss-esb rather than just esb as the
error message states? I got the same error you did when i changed my
packaging to just esb. Make sure you only have one packaging entry.
Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 2:23 PM, Lam Hayward
<Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
> scott@theryansplace.com
> www.soaringeagleco.com
>
>
> On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward
> <Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jboss ESB and Maven
Posted by Scott Ryan <sc...@theryansplace.com>.
Are you sure the packaging is jboss-esb rather than just esb as the error
message states? I got the same error you did when i changed my packaging to
just esb. Make sure you only have one packaging entry.
Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 2:23 PM, Lam Hayward <Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
> scott@theryansplace.com
> www.soaringeagleco.com
>
>
> On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward
> <Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Jboss ESB and Maven
Posted by Scott Ryan <sc...@theryansplace.com>.
try changing the packaging to war and see if you get a warning about
web.xml when you do mvn install.
Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 3:04 PM, Scott Ryan <sc...@theryansplace.com> wrote:
> 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
> scott@theryansplace.com
> www.soaringeagleco.com
>
>
> On Thu, Sep 4, 2008 at 2:45 PM, Lam Hayward <Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
>> scott@theryansplace.com
>> www.soaringeagleco.com
>>
>>
>> On Thu, Sep 4, 2008 at 2:23 PM, Lam Hayward
>> <Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
>> > scott@theryansplace.com
>> > www.soaringeagleco.com
>> >
>> >
>> > On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward
>> > <Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: users-help@maven.apache.org
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
Re: Jboss ESB and Maven
Posted by Scott Ryan <sc...@theryansplace.com>.
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
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 2:45 PM, Lam Hayward <Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
> scott@theryansplace.com
> www.soaringeagleco.com
>
>
> On Thu, Sep 4, 2008 at 2:23 PM, Lam Hayward
> <Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
> > scott@theryansplace.com
> > www.soaringeagleco.com
> >
> >
> > On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward
> > <Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Jboss ESB and Maven
Posted by Lam Hayward <Ha...@lac-bac.gc.ca>.
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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 2:23 PM, Lam Hayward
<Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
> scott@theryansplace.com
> www.soaringeagleco.com
>
>
> On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward
> <Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jboss ESB and Maven
Posted by Scott Ryan <sc...@theryansplace.com>.
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
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 2:23 PM, Lam Hayward <Ha...@lac-bac.gc.ca>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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
> scott@theryansplace.com
> www.soaringeagleco.com
>
>
> On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward
> <Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Jboss ESB and Maven
Posted by Lam Hayward <Ha...@lac-bac.gc.ca>.
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: sryan737@gmail.com [mailto:sryan737@gmail.com] 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
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward
<Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jboss ESB and Maven
Posted by Scott Ryan <sc...@theryansplace.com>.
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
scott@theryansplace.com
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 1:07 PM, Lam Hayward <Ha...@lac-bac.gc.ca>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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Jboss ESB and Maven
Posted by Lam Hayward <Ha...@lac-bac.gc.ca>.
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-dependency-plugin 2.0 fails when running eclipse:eclipse
Posted by Rune Flobakk <rf...@online.no>.
Thank you for your reply, Brian!
Yes, that is what I figured as well. The workspace consists of several
projects which does not share the same parent pom (only in the context
of running eclipse:eclipse). So I don't want to be forced to upgrade the
version of the plugin in projects which I decide to include in my
"workspace" pom, when they are really independent projects. It seems a
bit odd that there are som kind of "validating" of the configured
execution goal for the plugin when explicitly running eclipse:eclipse,
since eclipse:eclipse does not actually execute that goal. I have read
that eclipse:eclipse also triggers the generate-resources phase, but
maven-dependency-plugin is bound to the verify phase, much later in the
lifecycle.
Anyway, we worked around the problem by specifying the execution of
dependency:analyze-only in its own profile which is activated by Hudson.
So the dependency check happens on our CI server, but cannot be
triggered in the build by default, since it interferes with the
eclipse:eclipse goal, and people are individually maintaining their own
workspace POMs depending on what artifacts they would like linked up in
Eclipse.
- Rune
Brian E. Fox skrev:
> Maven will use the first version of a plugin it sees, so somewhere in
> your workspace you have an old version of the dependency plugin and when
> running the other projects, it is still using this old version.
>
> -----Original Message-----
> From: Rune Flobakk [mailto:rflobakk@online.no]
> Sent: Thursday, September 04, 2008 6:32 AM
> To: users@maven.apache.org
> Subject: maven-dependency-plugin 2.0 fails when running eclipse:eclipse
>
> Hello,
>
> On my project we have quite a large codebase separated in several Maven
> multimodule projects. In one of the parent poms I have configured to use
> maven-dependency-plugin to verify that we use dependencies
> appropriately, as described here:
> http://maven.apache.org/plugins/maven-dependency-plugin/examples/failing
> -the-build-on-dependency-analysis-warnings.html
>
> Snippet from our parent pom:
> <build>
> ...
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> </plugin>
> </plugins>
> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <version>2.0</version>
> <executions>
> <execution>
> <id>analyze</id>
> <phase>verify</phase>
> <goals>
> <goal>analyze-only</goal>
> </goals>
> <configuration>
> <failOnWarning>true</failOnWarning>
> <ignoreNonCompile>true</ignoreNonCompile>
> </configuration>
> </execution>
> </executions>
> </plugin>
> ...
> </pluginManagement>
> </build>
>
> When I run any lifecycle phase including verify (e.g. install, deploy)
> from that parent pom, every child module gets its dependency use
> checked, and the build fails on violations. All well!
>
> But when I run eclipse:eclipse and specifies a "workspace" pom, which
> only lists modules from many different projects, some external to this
> project but still internal to the organization, for some reason Maven
> seems to do "something" with the maven-dependency-plugin execution
> config for that one multimodule project. The problem as I understand it,
> is that the projects involved in the "workspace" pom uses different
> versions of maven-dependency-plugin, and I see that Maven downloads both
> 2.0-alpha-4 and 2.0 when I run eclipse:eclipse.
>
> The error message I get from Maven is this:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building project-x
> [INFO] task-segment: [eclipse:eclipse]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing eclipse:eclipse
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] 'analyze-only' was specified in an execution, but not found in
> the plugin [INFO]
> ------------------------------------------------------------------------
>
> When building project-x on its own, everything is OK. So why does Maven
> get confused on which plugin version it should use when the project-x is
> included as one of many modules of a super-super-pom?
>
> Sorry for a very verbose mail, I hope it's possible to understand the
> problem. Thanks in advance for any help :)
>
> Regards,
> Rune Flobakk
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: maven-dependency-plugin 2.0 fails when running eclipse:eclipse
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Maven will use the first version of a plugin it sees, so somewhere in
your workspace you have an old version of the dependency plugin and when
running the other projects, it is still using this old version.
-----Original Message-----
From: Rune Flobakk [mailto:rflobakk@online.no]
Sent: Thursday, September 04, 2008 6:32 AM
To: users@maven.apache.org
Subject: maven-dependency-plugin 2.0 fails when running eclipse:eclipse
Hello,
On my project we have quite a large codebase separated in several Maven
multimodule projects. In one of the parent poms I have configured to use
maven-dependency-plugin to verify that we use dependencies
appropriately, as described here:
http://maven.apache.org/plugins/maven-dependency-plugin/examples/failing
-the-build-on-dependency-analysis-warnings.html
Snippet from our parent pom:
<build>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
</plugin>
</plugins>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.0</version>
<executions>
<execution>
<id>analyze</id>
<phase>verify</phase>
<goals>
<goal>analyze-only</goal>
</goals>
<configuration>
<failOnWarning>true</failOnWarning>
<ignoreNonCompile>true</ignoreNonCompile>
</configuration>
</execution>
</executions>
</plugin>
...
</pluginManagement>
</build>
When I run any lifecycle phase including verify (e.g. install, deploy)
from that parent pom, every child module gets its dependency use
checked, and the build fails on violations. All well!
But when I run eclipse:eclipse and specifies a "workspace" pom, which
only lists modules from many different projects, some external to this
project but still internal to the organization, for some reason Maven
seems to do "something" with the maven-dependency-plugin execution
config for that one multimodule project. The problem as I understand it,
is that the projects involved in the "workspace" pom uses different
versions of maven-dependency-plugin, and I see that Maven downloads both
2.0-alpha-4 and 2.0 when I run eclipse:eclipse.
The error message I get from Maven is this:
[INFO]
------------------------------------------------------------------------
[INFO] Building project-x
[INFO] task-segment: [eclipse:eclipse]
[INFO]
------------------------------------------------------------------------
[INFO] Preparing eclipse:eclipse
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] 'analyze-only' was specified in an execution, but not found in
the plugin [INFO]
------------------------------------------------------------------------
When building project-x on its own, everything is OK. So why does Maven
get confused on which plugin version it should use when the project-x is
included as one of many modules of a super-super-pom?
Sorry for a very verbose mail, I hope it's possible to understand the
problem. Thanks in advance for any help :)
Regards,
Rune Flobakk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org