RE: Multiproject build that needs to build one project only if on a particular os?
> -Original Message- > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] > Sent: Tuesday, August 16, 2016 12:59 PM > To: Maven Users List > Subject: Re: Multiproject build that needs to build one project only if > on a particular os? > > Hi, > > You should take a look to profiles which might solve your problem... > > http://maven.apache.org/guides/introduction/introduction-to- > profiles.html > > But you might can give an example what can not be built on Windows in > particular in a Java project? Or do you make a OSGi build? A docker image for Linux. > On 16/08/16 21:47, KARR, DAVID wrote: > > I have a multiproject build with three modules, not counting the top- > level. > > I can build this on either Windows or Linux, but if I'm building on > > Windows, one of the subprojects should not be built. > > I vaguely remember seeing ways to set architecture properties and > > check for those, but I can't find info on that right now. How do I > set this up? > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multiproject build that needs to build one project only if on a particular os?
Hi, activtion of modules via profile is a bad idea... http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/ Kind regards Karl Heinz Marbaise On 16/08/16 21:54, Bernd Eckenfels wrote: This describes how to control modules with profiles and how to activate profiles based on os family: http://books.sonatype.com/mvnref-book/reference/profiles-sect-activation.html Gruss Bernd Am Tue, 16 Aug 2016 19:47:38 + schrieb "KARR, DAVID" : I have a multiproject build with three modules, not counting the top-level. I can build this on either Windows or Linux, but if I'm building on Windows, one of the subprojects should not be built. I vaguely remember seeing ways to set architecture properties and check for those, but I can't find info on that right now. How do I set this up? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multiproject build that needs to build one project only if on a particular os?
In addition, you can use the --pl option (requires Maven 3.2.1+) to exclude the child module of your choice. This example excludes child module "foo": mvn --pl !foo Cheers, Paul On Tue, Aug 16, 2016 at 2:54 PM, Bernd Eckenfels wrote: > This describes how to control modules with profiles and how to activate > profiles based on os family: > > > http://books.sonatype.com/mvnref-book/reference/ > profiles-sect-activation.html > > Gruss > Bernd > > Am Tue, 16 Aug 2016 19:47:38 +0000 > schrieb "KARR, DAVID" : > > > I have a multiproject build with three modules, not counting the > > top-level. I can build this on either Windows or Linux, but if I'm > > building on Windows, one of the subprojects should not be built. I > > vaguely remember seeing ways to set architecture properties and check > > for those, but I can't find info on that right now. How do I set > > this up? > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Multiproject build that needs to build one project only if on a particular os?
Hi, You should take a look to profiles which might solve your problem... http://maven.apache.org/guides/introduction/introduction-to-profiles.html But you might can give an example what can not be built on Windows in particular in a Java project? Or do you make a OSGi build? Kind regards Karl Heinz Marbaise On 16/08/16 21:47, KARR, DAVID wrote: I have a multiproject build with three modules, not counting the top-level. I can build this on either Windows or Linux, but if I'm building on Windows, one of the subprojects should not be built. I vaguely remember seeing ways to set architecture properties and check for those, but I can't find info on that right now. How do I set this up? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multiproject build that needs to build one project only if on a particular os?
This describes how to control modules with profiles and how to activate profiles based on os family: http://books.sonatype.com/mvnref-book/reference/profiles-sect-activation.html Gruss Bernd Am Tue, 16 Aug 2016 19:47:38 + schrieb "KARR, DAVID" : > I have a multiproject build with three modules, not counting the > top-level. I can build this on either Windows or Linux, but if I'm > building on Windows, one of the subprojects should not be built. I > vaguely remember seeing ways to set architecture properties and check > for those, but I can't find info on that right now. How do I set > this up? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Multiproject build that needs to build one project only if on a particular os?
I have a multiproject build with three modules, not counting the top-level. I can build this on either Windows or Linux, but if I'm building on Windows, one of the subprojects should not be built. I vaguely remember seeing ways to set architecture properties and check for those, but I can't find info on that right now. How do I set this up? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to generate javadocs for only some projects in a multiproject?
Only some jars contains API meant to be used by customers. No
point in having Javadoc for internal code, that will be confusing
for the customer.
For our internal use we are using Eclipse and having "projects
dependencies" in the .classpath file instead of JAR dependencies
so all javadoc will be available form the java source code in a
IDE.
Anyway the exclude can do but since we have so many packages to
exclude it is not really a good solution.
Thanks
Lucas
On 04/08/2011 04:01 PM, Anders Hammar wrote:
Although you can't exclude projects you should be
able to what you want by excluding packages.
In any case, the problems you are running into is mostly because
you're trying to do something isn't the Maven main road. :-) Why
isn't a javadoc jar for each artifact good enough? That's how
your IDE wants it in any case.
/Anders
On Fri, Apr 8, 2011 at 15:47, Lucas
Persson <lucas.pers...@oracle.com>
wrote:
Hi
Yes but the two things have to happen at the same time :-)
yes javadoc:aggregate-jar will produce a single jar of
javadoc but I can not see that I can exclude or include
projects.
It seem to take all projects the the multiproject defines.
/Lucas
On 04/08/2011 02:29 PM, Anders Hammar wrote:
I think you're asking two
different things here:
1. You only want a javadoc for some projects.
2. You want a single aggrgated javadoc jar
For #2, would the aggregate-jar goal of the javadoc
plugin work?
/Anders
On Fri, Apr 8, 2011 at
13:36, Lucas Persson <lucas.pers...@oracle.com>
wrote:
Hi
I want to generate and release the javadoc
(e.g. the javadoc.jar should be a release
artefacts just like any other JAR)
But only some projects contains public java
code that javadoc should be generated for.
And if I have for instance 4 projects for
which I want to generate javadoc I only want
one javadoc.jar in the end with the complete
source tree.
I really thought that I found the solution to
this in
http://stackoverflow.com/questions/4947215/maven-3-generate-javadoc-for-defined-artifacts
but the bug reported in http://jira.codehaus.org/browse/MDEP-291
seem to hinder it.
I really do not want to have some relative
path from the 'javadoc project' to the
projects where the source are in.
I have also played around with different
combination on
like this in the multiproject
org.apache.maven.plugins
maven-javadoc-plugin
false
false
org.apache.maven.plugins
maven-javadoc-plugin
true
And in those subproject that I really want
javadoc for added:
org.apache.maven.plugins
Re: How to generate javadocs for only some projects in a multiproject?
Although you can't exclude projects you should be able to what you want by excluding packages. In any case, the problems you are running into is mostly because you're trying to do something isn't the Maven main road. :-) Why isn't a javadoc jar for each artifact good enough? That's how your IDE wants it in any case. /Anders On Fri, Apr 8, 2011 at 15:47, Lucas Persson wrote: > Hi > > Yes but the two things have to happen at the same time :-) > > yes javadoc:aggregate-jar will produce a single jar of javadoc but I can > not see that I can exclude or include projects. > It seem to take all projects the the multiproject defines. > /Lucas > > On 04/08/2011 02:29 PM, Anders Hammar wrote: > > I think you're asking two different things here: > 1. You only want a javadoc for some projects. > 2. You want a single aggrgated javadoc jar > > For #2, would the aggregate-jar goal of the javadoc plugin work? > > /Anders > On Fri, Apr 8, 2011 at 13:36, Lucas Persson wrote: > >> Hi >> >> I want to generate and release the javadoc (e.g. the javadoc.jar should be >> a release artefacts just like any other JAR) >> But only some projects contains public java code that javadoc should be >> generated for. >> And if I have for instance 4 projects for which I want to generate javadoc >> I only want one javadoc.jar in the end with the complete source tree. >> >> I really thought that I found the solution to this in >> >> http://stackoverflow.com/questions/4947215/maven-3-generate-javadoc-for-defined-artifacts >> but the bug reported in http://jira.codehaus.org/browse/MDEP-291 seem to >> hinder it. >> >> I really do not want to have some relative path from the 'javadoc project' >> to the projects where the source are in. >> >> >> I have also played around with different combination on >> like this in the multiproject >> >> >> >> org.apache.maven.plugins >> maven-javadoc-plugin >> false >> >> false >> >> >> >> >> >> >> org.apache.maven.plugins >> maven-javadoc-plugin >> >> true >> >> >> >> >> And in those subproject that I really want javadoc for added: >> >> org.apache.maven.plugins >> maven-javadoc-plugin >> >> false >> >> >> >> >> >> So I then tried to use >includePackageNames> but that does not exists. >> Only but then I need to exclude like hundred of >> package names, sigh. >> >> /Lucas >> >> >> >> -- >> [image: Oracle] <http://www.oracle.com> >> Lucas Persson | Principal Member of Technical Staff >> Phone: +4684773644 | | | Mobile: +46730946656 >> Oracle Communications Platform >> ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm >> >> Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746 >> [image: Green Oracle] <http://www.oracle.com/commitment> Oracle is >> committed to developing practices and products that help protect the >> environment >> > > > -- > [image: Oracle] <http://www.oracle.com> > Lucas Persson | Principal Member of Technical Staff > Phone: +4684773644 | | | Mobile: +46730946656 > Oracle Communications Platform > ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm > > Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746 > [image: Green Oracle] <http://www.oracle.com/commitment> Oracle is > committed to developing practices and products that help protect the > environment >
Re: How to generate javadocs for only some projects in a multiproject?
Hi Yes but the two things have to happen at the same time :-) yes javadoc:aggregate-jar will produce a single jar of javadoc but I can not see that I can exclude or include projects. It seem to take all projects the the multiproject defines. /Lucas On 04/08/2011 02:29 PM, Anders Hammar wrote: I think you're asking two different things here: 1. You only want a javadoc for some projects. 2. You want a single aggrgated javadoc jar For #2, would the aggregate-jar goal of the javadoc plugin work? /Anders On Fri, Apr 8, 2011 at 13:36, Lucas Persson <lucas.pers...@oracle.com> wrote: Hi I want to generate and release the javadoc (e.g. the javadoc.jar should be a release artefacts just like any other JAR) But only some projects contains public java code that javadoc should be generated for. And if I have for instance 4 projects for which I want to generate javadoc I only want one javadoc.jar in the end with the complete source tree. I really thought that I found the solution to this in http://stackoverflow.com/questions/4947215/maven-3-generate-javadoc-for-defined-artifacts but the bug reported in http://jira.codehaus.org/browse/MDEP-291 seem to hinder it. I really do not want to have some relative path from the 'javadoc project' to the projects where the source are in. I have also played around with different combination on like this in the multiproject org.apache.maven.plugins maven-javadoc-plugin false false org.apache.maven.plugins maven-javadoc-plugin true And in those subproject that I really want javadoc for added: org.apache.maven.plugins maven-javadoc-plugin false So I then tried to use >includePackageNames> but that does not exists. Only but then I need to exclude like hundred of package names, sigh. /Lucas -- Lucas Persson | Principal Member of Technical Staff Phone: +4684773644 | | | Mobile: +46730946656 Oracle Communications Platform ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746 Oracle is committed to developing practices and products that help protect the environment -- Lucas Persson | Principal Member of Technical Staff Phone: +4684773644 | | | Mobile: +46730946656 Oracle Communications Platform ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746 Oracle is committed to developing practices and products that help protect the environment
Re: How to generate javadocs for only some projects in a multiproject?
I think you're asking two different things here: 1. You only want a javadoc for some projects. 2. You want a single aggrgated javadoc jar For #2, would the aggregate-jar goal of the javadoc plugin work? /Anders On Fri, Apr 8, 2011 at 13:36, Lucas Persson wrote: > Hi > > I want to generate and release the javadoc (e.g. the javadoc.jar should be > a release artefacts just like any other JAR) > But only some projects contains public java code that javadoc should be > generated for. > And if I have for instance 4 projects for which I want to generate javadoc > I only want one javadoc.jar in the end with the complete source tree. > > I really thought that I found the solution to this in > > http://stackoverflow.com/questions/4947215/maven-3-generate-javadoc-for-defined-artifacts > but the bug reported in http://jira.codehaus.org/browse/MDEP-291 seem to > hinder it. > > I really do not want to have some relative path from the 'javadoc project' > to the projects where the source are in. > > > I have also played around with different combination on > like this in the multiproject > > > > org.apache.maven.plugins > maven-javadoc-plugin > false > > false > > > > > > > org.apache.maven.plugins > maven-javadoc-plugin > > true > > > > > And in those subproject that I really want javadoc for added: > > org.apache.maven.plugins > maven-javadoc-plugin > > false > > > > > > So I then tried to use >includePackageNames> but that does not exists. > Only but then I need to exclude like hundred of > package names, sigh. > > /Lucas > > > > -- > [image: Oracle] <http://www.oracle.com> > Lucas Persson | Principal Member of Technical Staff > Phone: +4684773644 | | | Mobile: +46730946656 > Oracle Communications Platform > ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm > > Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746 > [image: Green Oracle] <http://www.oracle.com/commitment> Oracle is > committed to developing practices and products that help protect the > environment >
How to generate javadocs for only some projects in a multiproject?
Hi I want to generate and release the javadoc (e.g. the javadoc.jar should be a release artefacts just like any other JAR) But only some projects contains public java code that javadoc should be generated for. And if I have for instance 4 projects for which I want to generate javadoc I only want one javadoc.jar in the end with the complete source tree. I really thought that I found the solution to this in http://stackoverflow.com/questions/4947215/maven-3-generate-javadoc-for-defined-artifacts but the bug reported in http://jira.codehaus.org/browse/MDEP-291 seem to hinder it. I really do not want to have some relative path from the 'javadoc project' to the projects where the source are in. I have also played around with different combination on like this in the multiproject org.apache.maven.plugins maven-javadoc-plugin false false org.apache.maven.plugins maven-javadoc-plugin true And in those subproject that I really want javadoc for added: org.apache.maven.plugins maven-javadoc-plugin false So I then tried to use >includePackageNames> but that does not exists. Only but then I need to exclude like hundred of package names, sigh. /Lucas -- Lucas Persson | Principal Member of Technical Staff Phone: +4684773644 | | | Mobile: +46730946656 Oracle Communications Platform ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746 Oracle is committed to developing practices and products that help protect the environment
Re: Where I have to put third party libraries in a multiproject layout?.
take a look at appassembler-maven-plugin, it create jsw bundle nicely -Dan On Mon, Aug 2, 2010 at 12:38 PM, ale_s wrote: > > Hello, where I have to put third party libraries in a multiproject layout?. > I'm using the library "java wrapper" to run as a service apalicacion. This > library comes with a configuration file and other files but I do not know > where they go. > Also when I run the assembly phase I want to copy the configuration files > "java wrapper" in a configuration folder. > > How I can do this? > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Where-I-have-to-put-third-party-libraries-in-a-multiproject-layout-tp2262165p2262165.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Where I have to put third party libraries in a multiproject layout?.
Hello, where I have to put third party libraries in a multiproject layout?. I'm using the library "java wrapper" to run as a service apalicacion. This library comes with a configuration file and other files but I do not know where they go. Also when I run the assembly phase I want to copy the configuration files "java wrapper" in a configuration folder. How I can do this? -- View this message in context: http://maven.40175.n5.nabble.com/Where-I-have-to-put-third-party-libraries-in-a-multiproject-layout-tp2262165p2262165.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does my multiproject build revert to taking SNAPSHOT versions of dependencies when I want a specified version?
On Mon, Jan 5, 2009 at 2:52 PM, Christopher Patti wrote:
> On Thu, Jan 1, 2009 at 2:59 AM, Wayne Fay wrote:
>
>> > Why does it all of a sudden switch from the version I want (R2_5_653H1)
>> to
>> > SNAPSHOT here?
>>
>> Bugs have been filed in Jira against various Maven2 versions involving
>> the dotted notation of properties. Specifically, it seems like
>> anything before the final dot is sometimes ignored, so
>> this.is.a.property.version is evaluated as simply version which is
>> usually project.version.
>>
>> I'd replace your dots with underlines and see if you have different
>> results. I moved away from dots entirely the first time this bug hit
>> me a while back. I can't give you a specific Jira to look at/follow
>> but I'm sure you could find it/one of them (I feel like there are a
>> couple).
>>
>> Wayne
>>
>
> Thanks, this is a good point and might also help explain some other
> problems we've had.
>
> This will very likely cause my novice Maven 2 skills to show, but I can't
> just change:
> ---
>
> Squid
> dbawrappers
> ${build.version}
>
> ---
> to:
> ---
>
> Squid
> dbawrappers
> ${build_version}
>
> ---
>
> Can I? Won't that break the desired "If no version is specified, use
> SNAPSHOT' behavior I'm trying to override for versioned builds?
>
> Thanks,
> -Chris
>
Aha! If I use use ${version} that seems to fix the problem! Thanks so much!
-Chris
--
Christopher Patti - Release Engineer - E-Mail: cpa...@broad.mit.edu
Y! feoh AIM: chrisfeohpatti GTalk/Jabber: cpa...@gmail.com
Phone - Work: 617-324-2820 Cell: 617-710-1806 Home: 617-764-5887
Re: Why does my multiproject build revert to taking SNAPSHOT versions of dependencies when I want a specified version?
On Thu, Jan 1, 2009 at 2:59 AM, Wayne Fay wrote:
> > Why does it all of a sudden switch from the version I want (R2_5_653H1)
> to
> > SNAPSHOT here?
>
> Bugs have been filed in Jira against various Maven2 versions involving
> the dotted notation of properties. Specifically, it seems like
> anything before the final dot is sometimes ignored, so
> this.is.a.property.version is evaluated as simply version which is
> usually project.version.
>
> I'd replace your dots with underlines and see if you have different
> results. I moved away from dots entirely the first time this bug hit
> me a while back. I can't give you a specific Jira to look at/follow
> but I'm sure you could find it/one of them (I feel like there are a
> couple).
>
> Wayne
>
Thanks, this is a good point and might also help explain some other problems
we've had.
This will very likely cause my novice Maven 2 skills to show, but I can't
just change:
---
Squid
dbawrappers
${build.version}
---
to:
---
Squid
dbawrappers
${build_version}
---
Can I? Won't that break the desired "If no version is specified, use
SNAPSHOT' behavior I'm trying to override for versioned builds?
Thanks,
-Chris
--
Christopher Patti - Release Engineer - E-Mail: cpa...@broad.mit.edu
Y! feoh AIM: chrisfeohpatti GTalk/Jabber: cpa...@gmail.com
Phone - Work: 617-324-2820 Cell: 617-710-1806 Home: 617-764-5887
Re: Why does my multiproject build revert to taking SNAPSHOT versions of dependencies when I want a specified version?
> Why does it all of a sudden switch from the version I want (R2_5_653H1) to > SNAPSHOT here? Bugs have been filed in Jira against various Maven2 versions involving the dotted notation of properties. Specifically, it seems like anything before the final dot is sometimes ignored, so this.is.a.property.version is evaluated as simply version which is usually project.version. I'd replace your dots with underlines and see if you have different results. I moved away from dots entirely the first time this bug hit me a while back. I can't give you a specific Jira to look at/follow but I'm sure you could find it/one of them (I feel like there are a couple). Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Why does my multiproject build revert to taking SNAPSHOT versions of dependencies when I want a specified version?
Folks;
I've run into this problem before, and have never been able to explain it.
We have a number of dependent sub-projects, and whenever I try to do a build
from one of the sub-projects, somewhere down the dependency chain it
switches away from the version I'm specifying with -Dbuild.version and back
to SNAPSHOT, causing the build to fail.
Here's some sample output:
1:17pm prodi...@node179 /prodinfolocal/buildareas/squid/R2_5_653/salmon >
mvn -PPROD -Dsquid.version=R2_5_653H1 -Dbuild.version=R2_5_653H1
-Dproject.version=R2_5_653H1 -Dmaven.test.skip=true install
[INFO] Scanning for projects...
[INFO]
[INFO] Building Squid Salmon UI
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://prodinfosvn.broad.mit.edu:8000/m2-repository/Squid/SquidEntities/1.0-SNAPSHOT/SquidEntities-1.0-SNAPSHOT.pom
Downloading:
http://prodinfosvn.broad.mit.edu:8000/m2-repository/Squid/dbawrappers/1.0-SNAPSHOT/dbawrappers-1.0-SNAPSHOT.pom
Downloading:
http://prodinfosvn.broad.mit.edu:8000/m2-repository/jadm/jadm/1.0-SNAPSHOT/jadm-1.0-SNAPSHOT.pom
Downloading:
http://prodinfosvn.broad.mit.edu:8000/m2-repository/Squid/SquidEntities/1.0-SNAPSHOT/SquidEntities-1.0-SNAPSHOT.jar
Downloading:
http://prodinfosvn.broad.mit.edu:8000/m2-repository/jadm/jadm/1.0-SNAPSHOT/jadm-1.0-SNAPSHOT.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) Squid:SquidEntities:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=Squid -DartifactId=SquidEntities
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=Squid -DartifactId=SquidEntities
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
Path to dependency:
1) Squid:salmon:jar:R2_5_653H1
2) Squid:common:jar:R2_5_653H1
3) Squid:SquidEntities:jar:1.0-SNAPSHOT
2) jadm:jadm:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=jadm -DartifactId=jadm
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=jadm -DartifactId=jadm
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
Path to dependency:
1) Squid:salmon:jar:R2_5_653H1
2) bettalims:bettalims:jar:R2_5_653H1
3) jadm:jadm:jar:1.0-SNAPSHOT
--
2 required artifacts are missing.
for artifact:
Squid:salmon:jar:R2_5_653H1
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
codehaus (http://repository.codehaus.org/),
sourceforge (http://repository.codehaus.org/),
internal (http://prodinfosvn.broad.mit.edu:8000/m2-repository)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Wed Dec 31 13:18:22 EST 2008
[INFO] Final Memory: 17M/244M
[INFO]
9.185u 0.508s 0:05.51 175.6%0+0k 0+0io 1pf+0w
1:18pm prodi...@node179 /prodinfolocal/buildareas/squid/R2_5_653/salmon >
--
Why does it all of a sudden switch from the version I want (R2_5_653H1) to
SNAPSHOT here?
Hers's the way the dependency is specified in this (salmon) subproject's
POM:
Squid
common
${build.version}
and here's the dependency to the failing SquidEntities in the common POM:
---
Squid
SquidEntities
${project.version}
I'd appreciate any clues, as I'm out of ideas.
Thanks!
-Chris
--
Christopher Patti - Release Engineer - E-Mail: cpa...@broad.mit.edu
Y! feoh AIM: chrisfeohpatti GTalk/Jabber: cpa...@gmail.com
Phone - Work: 617-324-2820 Cell: 617-710-1806 Home: 617-764-5887
Multiproject site merge
Hello all, I've been battling with this for a while, with no satisfaction :-p Maybe you guys can help? I have a multi-module project layout with a parent pom that contains the build and reporting instructions, a subproject per artifact, and a subproject for the main site. parent |- pom.xml |- subA [...] |- subAexample ||- pom.xml (without any site instructions) ||- src | |- site | |- apt | ||- subAexample.apt | |- resources | |- images ||- ... |- subB [...] |- siteProj |- src |- site |- site.xml |- apt |- index.apt (main site index) |- ... The goal was to have parts of the site documentation distributed in the subprojects and then have them all merged into the main site. For example, a sub-project is a developer guide, which comes with source (structured like other subprojects), an apt and a few images (for the guide). The desired outcome after say local staging would be: htdocs |- index.html |- ... (css, etc) |- subAexample |- subAexample.html |- images |- ... 1) Is this goal at all possible? I currently have all site related files under the siteProj, but it would really be interesting to split them up, 2) I can't even get the apt in subAexample to generate... - What's the minimal requirements for the site plugin to go through the file structure and generate apt, fml, etc? - Is a site.xml a requirement? Can more than one site.xml be merged? Thanks for any hints or advice. w
Cannot find the tag library descriptor for "http://java.sun.com/jsp/jstl/core"multiproject
Hi I have a multiproject web-application with 5 modules. Each web-module have jsp-page and works fine, showing no errrors. However, In my parent project I get this message: Cannot find the tag library descriptor for "http://java.sun.com/jsp/jstl/core"; The error points to the jsp pages in the modules. My parent project is a POM project. I can run install, package, deploy from the parent project without compilation errors. So the code works fine. But the validator in Eclipse returns the error. Running Eclipse Ganymede 3.4.1 Regards Johan - http://www.procensor.se http://www.mobilepost.se http://www.resultreporter.com http://www.butiksbelysning.se -- View this message in context: http://www.nabble.com/Cannot-find-the-tag-library-descriptor-for-%22http%3A--java.sun.com-jsp-jstl-core%22multiproject-tp20030388p20030388.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Versions in a Multiproject
aha I remember now
if you have the parent also the parent folder then the default value
of project/parent/relativePath which is ../pom.XML will kick in
if you move the parent and don't set relative path then it won't find
the newer version of the patent that you have locally
Sent from my iPod
On 24 Aug 2008, at 16:05, Stephen Connolly <[EMAIL PROTECTED]
> wrote:
ok, here is one "solution"
the current behaviour is that if you have the parent in the reactor
(possibly only if it is also the parent folder) then maven ignores
the version.
what I would do is separate the parent from aggregation
so the project you use as parent does not have any child modules
this might be enough to solve your issues. if not, I would then take
a look at the version-maven-plugin and its update-parent goal
Sent from my iPod
On 20 Aug 2008, at 01:39, mfs <[EMAIL PROTECTED]> wrote:
Has anyone been able to figure out an alternate solution where
doesnt need to
specify the "${pom.parent.version}" in every
pom ? and be
able to inherit/refer the parent pom, so that we can specify the pom
version(s) in a multi-module project at one place, and hence make the
branching easy..
Petr Ferschmann wrote:
Hello,
The solution is not that simple. The problem with inherited
version is
if you enter only the subproject (and run mvn command there), the
newest
version (I think) of parent pom.xml is always used.
So if you checkout older version, it can make problems.
So we used different approach, we specify in every pom.xml the
parent
version. For project version we use
${pom.parent.version}.
The only working solution is using the maven release plugin (it
increases version when releasing new version).
Without that I was not able to use simple way for version handling.
How others handle that?
Petr
Maria Odea Ching píše v Pá 15. 06. 2007 v 16:43 +0800:
You can do that by not specifying the element in your
child
pom. The child pom would automatically inherit its parent's version
which you specified in the block.
See
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project%20Inheritance
-Deng
Jens Hohl wrote:
Good Morning,
Can someone point me to infos how i can set the version in a
Multiproject ?
In my parent pom file the Tag contains e.g
1.0-SNAPSHOT.
How can I refer to that value in my child POMs ? What's best way
to do
that ?
Regards,
Jens
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Petr Ferschmann
SoftEU s.r.o.
---
Bolevecká 6
301 00 Plzen
Czech Republic
---
Phone: +420 373 731 284
+420 373 729 300
Fax: +420 373 729 301
Cell: +420 775 638 008
E-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Versions-in-a-Multiproject-tp11135002p19061164.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
Re: Versions in a Multiproject
ok, here is one "solution"
the current behaviour is that if you have the parent in the reactor
(possibly only if it is also the parent folder) then maven ignores the
version.
what I would do is separate the parent from aggregation
so the project you use as parent does not have any child modules
this might be enough to solve your issues. if not, I would then take a
look at the version-maven-plugin and its update-parent goal
Sent from my iPod
On 20 Aug 2008, at 01:39, mfs <[EMAIL PROTECTED]> wrote:
Has anyone been able to figure out an alternate solution where
doesnt need to
specify the "${pom.parent.version}" in every
pom ? and be
able to inherit/refer the parent pom, so that we can specify the pom
version(s) in a multi-module project at one place, and hence make the
branching easy..
Petr Ferschmann wrote:
Hello,
The solution is not that simple. The problem with inherited version
is
if you enter only the subproject (and run mvn command there), the
newest
version (I think) of parent pom.xml is always used.
So if you checkout older version, it can make problems.
So we used different approach, we specify in every pom.xml the parent
version. For project version we use
${pom.parent.version}.
The only working solution is using the maven release plugin (it
increases version when releasing new version).
Without that I was not able to use simple way for version handling.
How others handle that?
Petr
Maria Odea Ching píše v Pá 15. 06. 2007 v 16:43 +0800:
You can do that by not specifying the element in your
child
pom. The child pom would automatically inherit its parent's version
which you specified in the block.
See
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project%20Inheritance
-Deng
Jens Hohl wrote:
Good Morning,
Can someone point me to infos how i can set the version in a
Multiproject ?
In my parent pom file the Tag contains e.g
1.0-SNAPSHOT.
How can I refer to that value in my child POMs ? What's best way
to do
that ?
Regards,
Jens
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Petr Ferschmann
SoftEU s.r.o.
---
Bolevecká 6
301 00 Plzen
Czech Republic
---
Phone: +420 373 731 284
+420 373 729 300
Fax: +420 373 729 301
Cell: +420 775 638 008
E-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Versions-in-a-Multiproject-tp11135002p19061164.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
Re: Versions in a Multiproject
Has anyone been able to figure out an alternate solution where doesnt need to
specify the "${pom.parent.version}" in every pom ? and be
able to inherit/refer the parent pom, so that we can specify the pom
version(s) in a multi-module project at one place, and hence make the
branching easy..
Petr Ferschmann wrote:
>
> Hello,
>
> The solution is not that simple. The problem with inherited version is
> if you enter only the subproject (and run mvn command there), the newest
> version (I think) of parent pom.xml is always used.
> So if you checkout older version, it can make problems.
>
> So we used different approach, we specify in every pom.xml the parent
> version. For project version we use
> ${pom.parent.version}.
>
> The only working solution is using the maven release plugin (it
> increases version when releasing new version).
> Without that I was not able to use simple way for version handling.
>
> How others handle that?
>
> Petr
>
>
> Maria Odea Ching píše v Pá 15. 06. 2007 v 16:43 +0800:
>
>> You can do that by not specifying the element in your child
>> pom. The child pom would automatically inherit its parent's version
>> which you specified in the block.
>>
>> See
>> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project%20Inheritance
>>
>> -Deng
>>
>> Jens Hohl wrote:
>> > Good Morning,
>> >
>> >
>> >
>> >
>> >
>> > Can someone point me to infos how i can set the version in a
>> > Multiproject ?
>> >
>> > In my parent pom file the Tag contains e.g
>> > 1.0-SNAPSHOT.
>> >
>> > How can I refer to that value in my child POMs ? What's best way to do
>> > that ?
>> >
>> >
>> >
>> > Regards,
>> >
>> > Jens
>> >
>> >
>> >
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
> Petr Ferschmann
>
>
> SoftEU s.r.o.
> ---
> Bolevecká 6
> 301 00 Plzen
> Czech Republic
> ---
> Phone: +420 373 731 284
>+420 373 729 300
> Fax: +420 373 729 301
> Cell: +420 775 638 008
> E-mail: [EMAIL PROTECTED]
>
>
--
View this message in context:
http://www.nabble.com/Versions-in-a-Multiproject-tp11135002p19061164.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven eclipse:eclipse plugin: multiproject parent of the parent modules generated incorrectly
Hello. Problem is with the maven eclipse:eclipse plugin. To make it simpler, I have following modules structure: Parent A -> extends -> Parent B Parent B defines modules: B.m1 and B.m2 Parent A defines modules: A.m3 and A.m4 Using flat layout, if that matters, so B, m1, m2, A, m3, m4 are in the same workspace folder, to make things easier. Now, when generating .classpath for modules in B, the .classpath files are correct -> module m1 reference eclipse project of the m2 (if it does depend of course). Contrary, generated .classpath for A is incorrect. If the module A.m3 depends on B.m1, then .classpath will contain reference to the B.m1 jar, but not eclipse project. That's because module B.m1 is not explicitly specified in A modules (which it shouldn't). In other words, mvn eclipse:eclipse fails to look up deeper than one parent. Any help is appreciated. Trying to get rid of those m2eclipse plugins (which are horribly slow). cvl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assemblies, filtering, and multiproject builds - a question.
On Mon, Jun 23, 2008 at 1:22 PM, Bracewell, Robert <[EMAIL PROTECTED]> wrote: > I have never got filtering working with filesets > The Maven documentation states filtering only works on > > So switching to solved my issues > Most interesting. Would that explain the behavior of the assembly working *perfectly* including filtering when I build it using 'mvn assembly:assembly' in the sub-project's directory, as opposed to being built as a part of the multiproject build? Thanks for the tip, I'll give it a shot in any case. -Chris -- Christopher Patti - Release Engineer - E-Mail: [EMAIL PROTECTED] Y! feoh AIM: chrisfeohpatti GTalk/Jabber: [EMAIL PROTECTED] Phone - Work: 617-324-2820 Cell: 617-710-1806 Home: 617-764-5887
RE: Assemblies, filtering, and multiproject builds - a question.
I have never got filtering working with filesets
The Maven documentation states filtering only works on
So switching to solved my issues
--
Robert
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Christopher Patti
Sent: 20 June 2008 22:46
To: users@maven.apache.org
Subject: Assemblies, filtering, and multiproject builds - a question.
Folks;
I have a project in a multiproject build that wants to generate a bunch
of
scripts. We're using the assembly plugin to do this, and in the
sub-project
build's pom.xml we have the following:
--
maven-assembly-plugin
src/main/assembly/assembly.xml
make-assembly
package
attached
---
Here's the assembly.xml file:
---
${artifactId}
tar.gz
src/main/scripts
0555
true
lib
0444
--
As you can see we've turned filtering on as we tar up the scripts.
Herein
lies the rub.
If I 'mvn install' in the sub-project's directory, I get the desired
.tar.gz
file created in 'target' and everything looks great.
---
cm65c-2a0:~/src/sandbox/cpatti-sequence-fixscripts/sequence/fobjectClien
t/target/unpacked-fobjectClient
cpatti$ more runJava
#!/bin/sh -f
exec java -cp lib/fobjectClient-1.0-SNAPSHOT.jar "$@"
*But* when I allow the multiproject build to run the sub-project build
as
part of its normal sequence of events, filtering fails to happen at all!
--
/fobjectClient cpatti$ more runJava
#!/bin/sh -f
exec java -cp lib/${project.build.finalName}.jar "$@"
cm65c-2a0:~/src/sandbox/cpatti-sequence-fixscripts/sequence/fobjectClien
t/target/fobjectClient
cpatti$
--
Needless to say, this isn't the desired behavior. Is there some way to
have
my cake and eat it too?
Thanks in advance for any clues!
-Chris
--
Christopher Patti - Release Engineer - E-Mail: [EMAIL PROTECTED]
Y! feoh AIM: chrisfeohpatti GTalk/Jabber: [EMAIL PROTECTED]
Phone - Work: 617-324-2820 Cell: 617-710-1806 Home: 617-764-5887
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Assemblies, filtering, and multiproject builds - a question.
Folks;
I have a project in a multiproject build that wants to generate a bunch of
scripts. We're using the assembly plugin to do this, and in the sub-project
build's pom.xml we have the following:
--
maven-assembly-plugin
src/main/assembly/assembly.xml
make-assembly
package
attached
---
Here's the assembly.xml file:
---
${artifactId}
tar.gz
src/main/scripts
0555
true
lib
0444
--
As you can see we've turned filtering on as we tar up the scripts. Herein
lies the rub.
If I 'mvn install' in the sub-project's directory, I get the desired .tar.gz
file created in 'target' and everything looks great.
---
cm65c-2a0:~/src/sandbox/cpatti-sequence-fixscripts/sequence/fobjectClient/target/unpacked-fobjectClient
cpatti$ more runJava
#!/bin/sh -f
exec java -cp lib/fobjectClient-1.0-SNAPSHOT.jar "$@"
*But* when I allow the multiproject build to run the sub-project build as
part of its normal sequence of events, filtering fails to happen at all!
--
/fobjectClient cpatti$ more runJava
#!/bin/sh -f
exec java -cp lib/${project.build.finalName}.jar "$@"
cm65c-2a0:~/src/sandbox/cpatti-sequence-fixscripts/sequence/fobjectClient/target/fobjectClient
cpatti$
--
Needless to say, this isn't the desired behavior. Is there some way to have
my cake and eat it too?
Thanks in advance for any clues!
-Chris
--
Christopher Patti - Release Engineer - E-Mail: [EMAIL PROTECTED]
Y! feoh AIM: chrisfeohpatti GTalk/Jabber: [EMAIL PROTECTED]
Phone - Work: 617-324-2820 Cell: 617-710-1806 Home: 617-764-5887
Assemblies, filtering, and multiproject builds - a question.
Folks;
I have a project in a multiproject build that wants to generate a bunch of
scripts. We're using the assembly plugin to do this, and in the sub-project
build's pom.xml we have the following:
--
maven-assembly-plugin
src/main/assembly/assembly.xml
make-assembly
package
attached
---
Here's the assembly.xml file:
---
${artifactId}
tar.gz
src/main/scripts
0555
true
lib
0444
--
As you can see we've turned filtering on as we tar up the scripts. Herein
lies the rub.
If I 'mvn install' in the sub-project's directory, I get the desired .tar.gz
file created in 'target' and everything looks great.
---
cm65c-2a0:~/src/sandbox/cpatti-sequence-fixscripts/sequence/fobjectClient/target/unpacked-fobjectClient
cpatti$ more runJava
#!/bin/sh -f
exec java -cp lib/fobjectClient-1.0-SNAPSHOT.jar "$@"
*But* when I allow the multiproject build to run the sub-project build as
part of its normal sequence of events, filtering fails to happen at all!
--
/fobjectClient cpatti$ more runJava
#!/bin/sh -f
exec java -cp lib/${project.build.finalName}.jar "$@"
cm65c-2a0:~/src/sandbox/cpatti-sequence-fixscripts/sequence/fobjectClient/target/fobjectClient
cpatti$
--
Needless to say, this isn't the desired behavior. Is there some way to have
my cake and eat it too?
Thanks in advance for any clues!
-Chris
--
Christopher Patti - Release Engineer - E-Mail: [EMAIL PROTECTED]
Y! feoh AIM: chrisfeohpatti GTalk/Jabber: [EMAIL PROTECTED]
Phone - Work: 617-324-2820 Cell: 617-710-1806 Home: 617-764-5887
maven multiproject
Hi,Does the multiproject site works with maven 2.0.9,is there a separate plugin for it?It used to create separate sites for every subproject before,does it still do that.Kindly let me know. Thanks, Kalyana krishnan
Use of AntRun causes clean to fail for multiproject?
So I've whittled my way down to a very simple multiproject that exhibits the same failure I'm seeing on a larger-scale project. Attached is the example. http://www.nabble.com/file/p14017171/test.zip test.zip Here's the summary. The project consists of project 'test' with modules 'test-a' and test-b'. 'test-a' depends on 'test-b'. If you run "mvn clean" on the root POM, the clean succeeds. If you run "mvn clean -Pbuild-failure" it fails. It appears that by attaching the antrun plugin to the clean phase causes it to interfere with local dependency resolution for sibling projects. So the big question, where should I report the bug in JIRA, since I'm not sure which plugin the bug is in. -- View this message in context: http://www.nabble.com/Use-of-AntRun-causes-clean-to-fail-for-multiproject--tf4894370s177.html#a14017171 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject build fails
Try adding this to the maven-release-plugin clean install On 9/5/07, Todd Nine <[EMAIL PROTECTED]> wrote: > > Hi all, > I have a multi project build in the standard directory structure. I'm > using subversion, and all my submodules will be built with the same > version > as the parent. I can perform a prepare successfully, however when I > perform > the release, the modules aren't built in the correct order based on their > dependencies, and the release fails. I'm able to perform a 'mvn clean > install', and they are built in the correct order, so it doesn't appear to > be an issue with the way I have defined my. I've included my prompts, I > can't seem to find anything wrong with my commands. > > > mvn clean release:clean release:prepare (from parent pom.xml working > directory) > > ### omitting clean > [INFO] Checking dependencies and plugins for snapshots ... > What is the release version for "Master Build Module for Parent"? ( > com.purdueefcu.statements:parent) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "dataaccess"? ( > com.purdueefcu.statements:dataaccess) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "common"? ( > com.purdueefcu.statements:common) > 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "parser"? ( > com.purdueefcu.statements:parser) > 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "processor"? ( > com.purdueefcu.statements:processor) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "mdb"? (com.purdueefcu.statements:mdb) > 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "overlays"? ( > com.purdueefcu.statements:overlays) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "reader"? ( > com.purdueefcu.statements:reader) > 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "writer"? ( > com.purdueefcu.statements:writer) > 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "statments ear"? ( > com.purdueefcu.statements:statements-app) 1.0.0-beta-2: : 1.0.0-beta-1 > What is SCM release tag or label for "Master Build Module for Parent"? ( > com.purdueefcu.statements:parent) parent-1.0.0-beta-1: : > What is the new development version for "Master Build Module for Parent"? > ( > com.purdueefcu.statements:parent) 1.0.0-beta-3-SNAPSHOT: : 1.0.0- > beta-2-SNAPSHOT > > ### omitting junit test output ### > > [INFO] Executing: svn --non-interactive commit --file > c:\DOCUME~1\tnine\LOCALS~1\Temp\maven-scm-2128849133.commit --targets > c:\DOCUME~1\tnin > e\LOCALS~1\Temp\maven-scm-8191-targets > [INFO] Working directory: c:\development\pefcu\statements\trunk > [INFO] Release preparation complete. > [INFO] > [INFO] > [INFO] > > [INFO] Reactor Summary: > [INFO] > > [INFO] Master Build Module for Parent SUCCESS [2: > 14.438s] > [INFO] dataaccess SUCCESS [ > 0.016s] > [INFO] common SUCCESS [ > 0.000s] > [INFO] parser SUCCESS [ > 0.000s] > [INFO] processor . SUCCESS [ > 0.109s] > [INFO] mdb ... SUCCESS [ > 0.063s] > [INFO] overlays .. SUCCESS [ > 0.000s] > [INFO] reader SUCCESS [ > 0.156s] > [INFO] writer SUCCESS [ > 0.015s] > [INFO] statments ear . SUCCESS [ > 0.125s] > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 2 minutes 24 seconds > [INFO] Finished at: Wed Sep 05 09:40:07 EDT 2007 > [INFO] Final Memory: 9M/32M > [INFO] > > > > > Next command > > mvn clean release:perform (from parent pom.xml working directory) > > ### omitting clean output > [INFO] Executing: svn --non-interactive checkout > > http://sourceforge.purdueefcu.com/svn/repos/statements/tags/parent-1.0.0-beta-1checkout > [INFO] Working directory: c:\development\pefcu\statements\trunk\target > [INFO] Executing goals 'deploy site-deploy'... > [INFO] Executing: mvn deploy site-deploy --no-plugin-updates -P > pefcu-profile -DperformRelease=true > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Master Build Module for Parent > [INFO] dataaccess > [INFO] common > [INFO] parser > [INFO] processor > [INFO] mdb > [INFO] overlays >
Re: Multiproject build fails
Did you specify a version for the release plugin ? On 06/09/07, Todd Nine <[EMAIL PROTECTED]> wrote: > ping > > On 9/5/07, Todd Nine <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > I have a multi project build in the standard directory structure. I'm > > using subversion, and all my submodules will be built with the same version > > as the parent. I can perform a prepare successfully, however when I perform > > the release, the modules aren't built in the correct order based on their > > dependencies, and the release fails. I'm able to perform a 'mvn clean > > install', and they are built in the correct order, so it doesn't appear to > > be an issue with the way I have defined my. I've included my prompts, I > > can't seem to find anything wrong with my commands. > > > > > > mvn clean release:clean release:prepare (from parent pom.xml working > > directory) > > > > ### omitting clean > > [INFO] Checking dependencies and plugins for snapshots ... > > What is the release version for "Master Build Module for Parent"? ( > > com.purdueefcu.statements:parent) 1.0.0-beta-2: : 1.0.0-beta-1 > > What is the release version for "dataaccess"? ( > > com.purdueefcu.statements:dataaccess) 1.0.0-beta-2: : 1.0.0-beta-1 > > What is the release version for "common"? ( > > com.purdueefcu.statements:common) 1.0.0-beta-2: : 1.0.0-beta-1 > > What is the release version for "parser"? ( > > com.purdueefcu.statements:parser) 1.0.0-beta-2: : 1.0.0-beta-1 > > What is the release version for "processor"? ( > > com.purdueefcu.statements:processor) 1.0.0-beta-2: : 1.0.0-beta-1 > > What is the release version for "mdb"? (com.purdueefcu.statements:mdb) > > 1.0.0-beta-2: : 1.0.0-beta-1 > > What is the release version for "overlays"? ( > > com.purdueefcu.statements:overlays) 1.0.0-beta-2: : 1.0.0-beta-1 > > What is the release version for "reader"? ( > > com.purdueefcu.statements:reader) 1.0.0-beta-2: : 1.0.0-beta-1 > > What is the release version for "writer"? ( > > com.purdueefcu.statements:writer) 1.0.0-beta-2: : 1.0.0-beta-1 > > What is the release version for "statments ear"? ( > > com.purdueefcu.statements:statements-app) 1.0.0-beta-2: : 1.0.0-beta-1 > > What is SCM release tag or label for "Master Build Module for Parent"? ( > > com.purdueefcu.statements:parent) parent-1.0.0-beta-1: : > > What is the new development version for "Master Build Module for Parent"? > > (com.purdueefcu.statements:parent) 1.0.0-beta-3-SNAPSHOT: : 1.0.0- > > beta-2-SNAPSHOT > > > > ### omitting junit test output ### > > > > [INFO] Executing: svn --non-interactive commit --file > > c:\DOCUME~1\tnine\LOCALS~1\Temp\maven-scm-2128849133.commit --targets > > c:\DOCUME~1\tnin > > e\LOCALS~1\Temp\maven-scm-8191-targets > > [INFO] Working directory: c:\development\pefcu\statements\trunk > > [INFO] Release preparation complete. > > [INFO] > > [INFO] > > [INFO] > > > > [INFO] Reactor Summary: > > [INFO] > > > > [INFO] Master Build Module for Parent SUCCESS [2: > > 14.438s] > > [INFO] dataaccess SUCCESS [ > > 0.016s] > > [INFO] common SUCCESS [ > > 0.000s] > > [INFO] parser SUCCESS [ > > 0.000s] > > [INFO] processor . SUCCESS [ > > 0.109s] > > [INFO] mdb ... SUCCESS [ > > 0.063s] > > [INFO] overlays .. SUCCESS [ > > 0.000s] > > [INFO] reader SUCCESS [ > > 0.156s] > > [INFO] writer SUCCESS [ > > 0.015s] > > [INFO] statments ear . SUCCESS [ > > 0.125s] > > [INFO] > > > > [INFO] > > > > [INFO] BUILD SUCCESSFUL > > [INFO] > > > > [INFO] Total time: 2 minutes 24 seconds > > [INFO] Finished at: Wed Sep 05 09:40:07 EDT 2007 > > [INFO] Final Memory: 9M/32M > > [INFO] > > > > > > > > > > Next command > > > > mvn clean release:perform (from parent pom.xml working directory) > > > > ### omitting clean output > > [INFO] Executing: svn --non-interactive checkout > > http://sourceforge.purdueefcu.com/svn/repos/statements/tags/parent-1.0.0-beta-1 > > checkout > > [INFO] Working directory: c:\development\pefcu\statements\trunk\target > > [INFO] Executing goals 'deploy site-deploy'... > > [INFO] Executing: mvn deploy site-deploy --no-plugin-updates -P > > pefcu-profile -DperformRelease=true > > [I
Re: Multiproject build fails
ping On 9/5/07, Todd Nine <[EMAIL PROTECTED]> wrote: > > Hi all, > I have a multi project build in the standard directory structure. I'm > using subversion, and all my submodules will be built with the same version > as the parent. I can perform a prepare successfully, however when I perform > the release, the modules aren't built in the correct order based on their > dependencies, and the release fails. I'm able to perform a 'mvn clean > install', and they are built in the correct order, so it doesn't appear to > be an issue with the way I have defined my. I've included my prompts, I > can't seem to find anything wrong with my commands. > > > mvn clean release:clean release:prepare (from parent pom.xml working > directory) > > ### omitting clean > [INFO] Checking dependencies and plugins for snapshots ... > What is the release version for "Master Build Module for Parent"? ( > com.purdueefcu.statements:parent) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "dataaccess"? ( > com.purdueefcu.statements:dataaccess) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "common"? ( > com.purdueefcu.statements:common) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "parser"? ( > com.purdueefcu.statements:parser) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "processor"? ( > com.purdueefcu.statements:processor) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "mdb"? (com.purdueefcu.statements:mdb) > 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "overlays"? ( > com.purdueefcu.statements:overlays) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "reader"? ( > com.purdueefcu.statements:reader) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "writer"? ( > com.purdueefcu.statements:writer) 1.0.0-beta-2: : 1.0.0-beta-1 > What is the release version for "statments ear"? ( > com.purdueefcu.statements:statements-app) 1.0.0-beta-2: : 1.0.0-beta-1 > What is SCM release tag or label for "Master Build Module for Parent"? ( > com.purdueefcu.statements:parent) parent-1.0.0-beta-1: : > What is the new development version for "Master Build Module for Parent"? > (com.purdueefcu.statements:parent) 1.0.0-beta-3-SNAPSHOT: : 1.0.0- > beta-2-SNAPSHOT > > ### omitting junit test output ### > > [INFO] Executing: svn --non-interactive commit --file > c:\DOCUME~1\tnine\LOCALS~1\Temp\maven-scm-2128849133.commit --targets > c:\DOCUME~1\tnin > e\LOCALS~1\Temp\maven-scm-8191-targets > [INFO] Working directory: c:\development\pefcu\statements\trunk > [INFO] Release preparation complete. > [INFO] > [INFO] > [INFO] > > [INFO] Reactor Summary: > [INFO] > > [INFO] Master Build Module for Parent SUCCESS [2: > 14.438s] > [INFO] dataaccess SUCCESS [ > 0.016s] > [INFO] common SUCCESS [ > 0.000s] > [INFO] parser SUCCESS [ > 0.000s] > [INFO] processor . SUCCESS [ > 0.109s] > [INFO] mdb ... SUCCESS [ > 0.063s] > [INFO] overlays .. SUCCESS [ > 0.000s] > [INFO] reader SUCCESS [ > 0.156s] > [INFO] writer SUCCESS [ > 0.015s] > [INFO] statments ear . SUCCESS [ > 0.125s] > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 2 minutes 24 seconds > [INFO] Finished at: Wed Sep 05 09:40:07 EDT 2007 > [INFO] Final Memory: 9M/32M > [INFO] > > > > > Next command > > mvn clean release:perform (from parent pom.xml working directory) > > ### omitting clean output > [INFO] Executing: svn --non-interactive checkout > http://sourceforge.purdueefcu.com/svn/repos/statements/tags/parent-1.0.0-beta-1 > checkout > [INFO] Working directory: c:\development\pefcu\statements\trunk\target > [INFO] Executing goals 'deploy site-deploy'... > [INFO] Executing: mvn deploy site-deploy --no-plugin-updates -P > pefcu-profile -DperformRelease=true > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Master Build Module for Parent > [INFO] dataaccess > [INFO] common > [INFO] parser > [INFO] processor > [INFO] mdb > [INFO] overlays > [INFO] reader > [INFO] writer > [INFO] statments ea
Multiproject build fails
Hi all, I have a multi project build in the standard directory structure. I'm using subversion, and all my submodules will be built with the same version as the parent. I can perform a prepare successfully, however when I perform the release, the modules aren't built in the correct order based on their dependencies, and the release fails. I'm able to perform a 'mvn clean install', and they are built in the correct order, so it doesn't appear to be an issue with the way I have defined my. I've included my prompts, I can't seem to find anything wrong with my commands. mvn clean release:clean release:prepare (from parent pom.xml working directory) ### omitting clean [INFO] Checking dependencies and plugins for snapshots ... What is the release version for "Master Build Module for Parent"? ( com.purdueefcu.statements:parent) 1.0.0-beta-2: : 1.0.0-beta-1 What is the release version for "dataaccess"? ( com.purdueefcu.statements:dataaccess) 1.0.0-beta-2: : 1.0.0-beta-1 What is the release version for "common"? (com.purdueefcu.statements:common) 1.0.0-beta-2: : 1.0.0-beta-1 What is the release version for "parser"? (com.purdueefcu.statements:parser) 1.0.0-beta-2: : 1.0.0-beta-1 What is the release version for "processor"? ( com.purdueefcu.statements:processor) 1.0.0-beta-2: : 1.0.0-beta-1 What is the release version for "mdb"? (com.purdueefcu.statements:mdb) 1.0.0-beta-2: : 1.0.0-beta-1 What is the release version for "overlays"? ( com.purdueefcu.statements:overlays) 1.0.0-beta-2: : 1.0.0-beta-1 What is the release version for "reader"? (com.purdueefcu.statements:reader) 1.0.0-beta-2: : 1.0.0-beta-1 What is the release version for "writer"? (com.purdueefcu.statements:writer) 1.0.0-beta-2: : 1.0.0-beta-1 What is the release version for "statments ear"? ( com.purdueefcu.statements:statements-app) 1.0.0-beta-2: : 1.0.0-beta-1 What is SCM release tag or label for "Master Build Module for Parent"? ( com.purdueefcu.statements:parent) parent-1.0.0-beta-1: : What is the new development version for "Master Build Module for Parent"? ( com.purdueefcu.statements:parent) 1.0.0-beta-3-SNAPSHOT: : 1.0.0- beta-2-SNAPSHOT ### omitting junit test output ### [INFO] Executing: svn --non-interactive commit --file c:\DOCUME~1\tnine\LOCALS~1\Temp\maven-scm-2128849133.commit --targets c:\DOCUME~1\tnin e\LOCALS~1\Temp\maven-scm-8191-targets [INFO] Working directory: c:\development\pefcu\statements\trunk [INFO] Release preparation complete. [INFO] [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] Master Build Module for Parent SUCCESS [2: 14.438s] [INFO] dataaccess SUCCESS [ 0.016s] [INFO] common SUCCESS [ 0.000s] [INFO] parser SUCCESS [ 0.000s] [INFO] processor . SUCCESS [ 0.109s] [INFO] mdb ... SUCCESS [ 0.063s] [INFO] overlays .. SUCCESS [ 0.000s] [INFO] reader SUCCESS [ 0.156s] [INFO] writer SUCCESS [ 0.015s] [INFO] statments ear . SUCCESS [ 0.125s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 2 minutes 24 seconds [INFO] Finished at: Wed Sep 05 09:40:07 EDT 2007 [INFO] Final Memory: 9M/32M [INFO] Next command mvn clean release:perform (from parent pom.xml working directory) ### omitting clean output [INFO] Executing: svn --non-interactive checkout http://sourceforge.purdueefcu.com/svn/repos/statements/tags/parent-1.0.0-beta-1checkout [INFO] Working directory: c:\development\pefcu\statements\trunk\target [INFO] Executing goals 'deploy site-deploy'... [INFO] Executing: mvn deploy site-deploy --no-plugin-updates -P pefcu-profile -DperformRelease=true [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Master Build Module for Parent [INFO] dataaccess [INFO] common [INFO] parser [INFO] processor [INFO] mdb [INFO] overlays [INFO] reader [INFO] writer [INFO] statments ear [INFO] [INFO] Building Master Build Module for Parent [INFO]task-segment: [deploy, site-deploy] [INFO] [INF
Re: [maven 1.1] StackOverflowError error for in multiproject plugin ???
I was defining some properties with similar names that creates a recursive
conflict in latests Jexl :
> maven.eclipse.classpath.include = ${
maven.eclipse.classpath.include.append}
renaming my properties with non-conflicting names solves my issue.
Thanks.
2007/7/18, Lukas Theussl <[EMAIL PROTECTED]>:
Two more jira's that might be helpful:
http://jira.codehaus.org/browse/MAVEN-1745
http://jira.codehaus.org/browse/MAVEN-1830
-Lukas
Lukas Theussl wrote:
> Probably because of this:
>
> http://jira.codehaus.org/browse/MAVEN-1749
>
> check your properties...
>
> HTH,
> -Lukas
>
>
> nicolas de loof wrote:
>
>> Hello,
>>
>> I'm working on an old project that used maven 1.0.1 and try to upgrade
to
>> 1.1.
>> When I run the multiproject:install goal, I get a
>> java.lang.StackOverflowError:
>>at java.lang.String.(String.java:208)
>>at java.lang.StringBuffer.toString(StringBuffer.java:586)
>>
>> This is cause by a in multiproject plugin.jelly (???)
>> " Gathering project list "
>> When I remove this in the plugin jelly script (in cache dir), my
>> build works as expected (I get other errors, but not related to
this...)
>>
>> What did I miss ? I get same error with jrockit 5.0, 6.0 and Sun jdk 6.
>>
>> Nico.
>>
>> Here is the full stacktrace :
>>
>> Errors stack :
>>
>>>> Unable to obtain goal [multiproject:install]
>>
>>
>> Fichier... file:/D:/platina/maven/cache/maven-multiproject-plugin-1.5.1
>> /plugin.jelly
>> ╚lement... ant:echo
>> Ligne. 54
>> Colonne... 17
>>
>>>> java.lang.reflect.InvocationTargetException
>>>>
>>
>> Exception stack traces :
>> org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal
>> [multiproject:install]
>>at org.apache.maven.werkz.Goal.fire(Goal.java:698)
>>at org.apache.maven.werkz.Goal.attain(Goal.java:623)
>>at org.apache.maven.plugin.PluginManager.attainGoals(
>> PluginManager.java:712)
>>at
>> org.apache.maven.MavenSession.attainGoals(MavenSession.java:265)
>>at org.apache.maven.cli.App.doMain(App.java:307)
>>at org.apache.maven.cli.App.main(App.java:217)
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at sun.reflect.NativeMethodAccessorImpl.invoke(
>> NativeMethodAccessorImpl.java:39)
>>at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:25)
>>at java.lang.reflect.Method.invoke(Method.java:585)
>>at com.werken.forehead.Forehead.run(Forehead.java:551)
>>at com.werken.forehead.Forehead.main(Forehead.java:581)
>> Caused by: org.apache.commons.jelly.JellyTagException:
>> file:/D:/platina/maven/cache/maven-multiproject-plugin-1.5.1/plug
>> in.jelly:54:17: null
>>at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java
:178)
>>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java
:250)
>>at org.apache.commons.jelly.impl.ScriptBlock.run(
ScriptBlock.java
>> :95)
>>at org.apache.commons.jelly.TagSupport.invokeBody(
TagSupport.java
>> :186)
>>at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:42)
>>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java
:250)
>>at org.apache.commons.jelly.impl.ScriptBlock.run(
ScriptBlock.java
>> :95)
>>at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(
>> MavenGoalTag.java:83)
>>at
>>
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction
>>
>> (MavenGoalTag.java:116)
>>at org.apache.maven.werkz.Goal.fire(Goal.java:691)
>>at org.apache.maven.werkz.Goal.attain(Goal.java:623)
>>at org.apache.maven.werkz.Goal.attainPrecursors(Goal.java:526)
>>at org.apache.maven.werkz.Goal.attain(Goal.java:621)
>>at
>> org.apache.maven.werkz.WerkzProject.attainGoal(WerkzProject.java
>> :209)
>>at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(
>> MavenAttainGoalTag.java:115)
>>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java
:250)
>>at org.apache.commons.jelly.impl.ScriptBlock.run(
ScriptBlock.java
>> :95)
>>at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(
>> MavenGoalTag.java:83)
>>at
>>
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction
>>
>> (MavenGoalTag.java:116)
>>a
Re: [maven 1.1] StackOverflowError error for in multiproject plugin ???
Two more jira's that might be helpful: http://jira.codehaus.org/browse/MAVEN-1745 http://jira.codehaus.org/browse/MAVEN-1830 -Lukas Lukas Theussl wrote: Probably because of this: http://jira.codehaus.org/browse/MAVEN-1749 check your properties... HTH, -Lukas nicolas de loof wrote: Hello, I'm working on an old project that used maven 1.0.1 and try to upgrade to 1.1. When I run the multiproject:install goal, I get a java.lang.StackOverflowError: at java.lang.String.(String.java:208) at java.lang.StringBuffer.toString(StringBuffer.java:586) This is cause by a in multiproject plugin.jelly (???) " Gathering project list " When I remove this in the plugin jelly script (in cache dir), my build works as expected (I get other errors, but not related to this...) What did I miss ? I get same error with jrockit 5.0, 6.0 and Sun jdk 6. Nico. Here is the full stacktrace : Errors stack : Unable to obtain goal [multiproject:install] Fichier... file:/D:/platina/maven/cache/maven-multiproject-plugin-1.5.1 /plugin.jelly ╚lement... ant:echo Ligne. 54 Colonne... 17 java.lang.reflect.InvocationTargetException Exception stack traces : org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [multiproject:install] at org.apache.maven.werkz.Goal.fire(Goal.java:698) at org.apache.maven.werkz.Goal.attain(Goal.java:623) at org.apache.maven.plugin.PluginManager.attainGoals( PluginManager.java:712) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:265) at org.apache.maven.cli.App.doMain(App.java:307) at org.apache.maven.cli.App.main(App.java:217) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: org.apache.commons.jelly.JellyTagException: file:/D:/platina/maven/cache/maven-multiproject-plugin-1.5.1/plug in.jelly:54:17: null at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:178) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java :186) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:42) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:83) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:116) at org.apache.maven.werkz.Goal.fire(Goal.java:691) at org.apache.maven.werkz.Goal.attain(Goal.java:623) at org.apache.maven.werkz.Goal.attainPrecursors(Goal.java:526) at org.apache.maven.werkz.Goal.attain(Goal.java:621) at org.apache.maven.werkz.WerkzProject.attainGoal(WerkzProject.java :209) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag( MavenAttainGoalTag.java:115) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:83) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:116) at org.apache.maven.werkz.Goal.fire(Goal.java:691) at org.apache.maven.werkz.Goal.attain(Goal.java:623) at org.apache.maven.plugin.PluginManager.attainGoals( PluginManager.java:712) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:265) at org.apache.maven.cli.App.doMain(App.java:307) at org.apache.maven.cli.App.main(App.java:217) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag
Re: [maven 1.1] StackOverflowError error for in multiproject plugin ???
Probably because of this: http://jira.codehaus.org/browse/MAVEN-1749 check your properties... HTH, -Lukas nicolas de loof wrote: Hello, I'm working on an old project that used maven 1.0.1 and try to upgrade to 1.1. When I run the multiproject:install goal, I get a java.lang.StackOverflowError: at java.lang.String.(String.java:208) at java.lang.StringBuffer.toString(StringBuffer.java:586) This is cause by a in multiproject plugin.jelly (???) " Gathering project list " When I remove this in the plugin jelly script (in cache dir), my build works as expected (I get other errors, but not related to this...) What did I miss ? I get same error with jrockit 5.0, 6.0 and Sun jdk 6. Nico. Here is the full stacktrace : Errors stack : Unable to obtain goal [multiproject:install] Fichier... file:/D:/platina/maven/cache/maven-multiproject-plugin-1.5.1 /plugin.jelly ╚lement... ant:echo Ligne. 54 Colonne... 17 java.lang.reflect.InvocationTargetException Exception stack traces : org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [multiproject:install] at org.apache.maven.werkz.Goal.fire(Goal.java:698) at org.apache.maven.werkz.Goal.attain(Goal.java:623) at org.apache.maven.plugin.PluginManager.attainGoals( PluginManager.java:712) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:265) at org.apache.maven.cli.App.doMain(App.java:307) at org.apache.maven.cli.App.main(App.java:217) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: org.apache.commons.jelly.JellyTagException: file:/D:/platina/maven/cache/maven-multiproject-plugin-1.5.1/plug in.jelly:54:17: null at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:178) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java :186) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:42) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:83) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:116) at org.apache.maven.werkz.Goal.fire(Goal.java:691) at org.apache.maven.werkz.Goal.attain(Goal.java:623) at org.apache.maven.werkz.Goal.attainPrecursors(Goal.java:526) at org.apache.maven.werkz.Goal.attain(Goal.java:621) at org.apache.maven.werkz.WerkzProject.attainGoal(WerkzProject.java :209) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag( MavenAttainGoalTag.java:115) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:83) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:116) at org.apache.maven.werkz.Goal.fire(Goal.java:691) at org.apache.maven.werkz.Goal.attain(Goal.java:623) at org.apache.maven.plugin.PluginManager.attainGoals( PluginManager.java:712) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:265) at org.apache.maven.cli.App.doMain(App.java:307) at org.apache.maven.cli.App.main(App.java:217) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:172) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java
[maven 1.1] StackOverflowError error for in multiproject plugin ???
Hello, I'm working on an old project that used maven 1.0.1 and try to upgrade to 1.1. When I run the multiproject:install goal, I get a java.lang.StackOverflowError: at java.lang.String.(String.java:208) at java.lang.StringBuffer.toString(StringBuffer.java:586) This is cause by a in multiproject plugin.jelly (???) " Gathering project list " When I remove this in the plugin jelly script (in cache dir), my build works as expected (I get other errors, but not related to this...) What did I miss ? I get same error with jrockit 5.0, 6.0 and Sun jdk 6. Nico. Here is the full stacktrace : Errors stack : Unable to obtain goal [multiproject:install] Fichier... file:/D:/platina/maven/cache/maven-multiproject-plugin-1.5.1 /plugin.jelly ╚lement... ant:echo Ligne. 54 Colonne... 17 java.lang.reflect.InvocationTargetException Exception stack traces : org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [multiproject:install] at org.apache.maven.werkz.Goal.fire(Goal.java:698) at org.apache.maven.werkz.Goal.attain(Goal.java:623) at org.apache.maven.plugin.PluginManager.attainGoals( PluginManager.java:712) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:265) at org.apache.maven.cli.App.doMain(App.java:307) at org.apache.maven.cli.App.main(App.java:217) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: org.apache.commons.jelly.JellyTagException: file:/D:/platina/maven/cache/maven-multiproject-plugin-1.5.1/plug in.jelly:54:17: null at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:178) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java :186) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:42) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:83) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:116) at org.apache.maven.werkz.Goal.fire(Goal.java:691) at org.apache.maven.werkz.Goal.attain(Goal.java:623) at org.apache.maven.werkz.Goal.attainPrecursors(Goal.java:526) at org.apache.maven.werkz.Goal.attain(Goal.java:621) at org.apache.maven.werkz.WerkzProject.attainGoal(WerkzProject.java :209) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag( MavenAttainGoalTag.java:115) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:83) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:116) at org.apache.maven.werkz.Goal.fire(Goal.java:691) at org.apache.maven.werkz.Goal.attain(Goal.java:623) at org.apache.maven.plugin.PluginManager.attainGoals( PluginManager.java:712) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:265) at org.apache.maven.cli.App.doMain(App.java:307) at org.apache.maven.cli.App.main(App.java:217) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:172) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java :186) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.jav
AW: Re: [m2] Deploy on Multiproject
Hello, At first i need to deploy three Ear files. Later I would like to deploy them directly on an Test Server. - Jens -Ursprüngliche Nachricht- Von: news [mailto:[EMAIL PROTECTED] Im Auftrag von ossi petz Gesendet: Dienstag, 3. Juli 2007 10:31 An: users@maven.apache.org Betreff: Re: [m2] Deploy on Multiproject Jens Hohl schrieb: > i have an Multi project with lots of artefacts. What's the best solution > deploying all Artefacts ? > what do you need to deploy (standalone apps, webapps, ...?) and where do you want it do deploy? and are there variants of the same deployment? best way is using maven to do it ;-) - 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]
Re: [m2] Deploy on Multiproject
The deploy goals work in the reactor to deploy all artifacts in a multi module project. Unless you have some specific requirements this should be fine. Andy On 2 Jul 2007, at 13:17, Jens Hohl wrote: Hello, i have an Multi project with lots of artefacts. What's the best solution deploying all Artefacts ? - Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Deploy on Multiproject
Jens Hohl schrieb: i have an Multi project with lots of artefacts. What's the best solution deploying all Artefacts ? what do you need to deploy (standalone apps, webapps, ...?) and where do you want it do deploy? and are there variants of the same deployment? best way is using maven to do it ;-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Deploy on Multiproject
Hello, i have an Multi project with lots of artefacts. What's the best solution deploying all Artefacts ? - Jens
Re: Versions in a Multiproject
Hello,
The solution is not that simple. The problem with inherited version is
if you enter only the subproject (and run mvn command there), the newest
version (I think) of parent pom.xml is always used.
So if you checkout older version, it can make problems.
So we used different approach, we specify in every pom.xml the parent
version. For project version we use
${pom.parent.version}.
The only working solution is using the maven release plugin (it
increases version when releasing new version).
Without that I was not able to use simple way for version handling.
How others handle that?
Petr
Maria Odea Ching píše v Pá 15. 06. 2007 v 16:43 +0800:
> You can do that by not specifying the element in your child
> pom. The child pom would automatically inherit its parent's version
> which you specified in the block.
>
> See
> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project%20Inheritance
>
> -Deng
>
> Jens Hohl wrote:
> > Good Morning,
> >
> >
> >
> >
> >
> > Can someone point me to infos how i can set the version in a
> > Multiproject ?
> >
> > In my parent pom file the Tag contains e.g
> > 1.0-SNAPSHOT.
> >
> > How can I refer to that value in my child POMs ? What's best way to do
> > that ?
> >
> >
> >
> > Regards,
> >
> > Jens
> >
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Petr Ferschmann
SoftEU s.r.o.
---
Bolevecká 6
301 00 Plzen
Czech Republic
---
Phone: +420 373 731 284
+420 373 729 300
Fax: +420 373 729 301
Cell: +420 775 638 008
E-mail: [EMAIL PROTECTED]
Re: Versions in a Multiproject
You can do that by not specifying the element in your child pom. The child pom would automatically inherit its parent's version which you specified in the block. See http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project%20Inheritance -Deng Jens Hohl wrote: Good Morning, Can someone point me to infos how i can set the version in a Multiproject ? In my parent pom file the Tag contains e.g 1.0-SNAPSHOT. How can I refer to that value in my child POMs ? What's best way to do that ? Regards, Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Versions in a Multiproject
Good Morning, Can someone point me to infos how i can set the version in a Multiproject ? In my parent pom file the Tag contains e.g 1.0-SNAPSHOT. How can I refer to that value in my child POMs ? What's best way to do that ? Regards, Jens
AW: How configure to Multiproject Site references
Hello, ist me (mac) from other mail Adress: Actually I have some problems to get this really working. I tried mvn site:run which results that the 'master' Website Is available through localhost. But I have same problems To reference to the sub-projects. In my site.xml I link via relative path like this: http://maven.apache.org/images/apache-maven-project.png http://maven.apache.org/ http://maven.apache.org/images/maven-small.gif -- The generated Site links like this to the Subprojekts: Project1 All result in a 404 Error. Anyone can help me, may I need some complete other solution for that ? Actually I think how to structure this to deploy on a Webserver ... Regards, Jens -Ursprüngliche Nachricht- Von: vgpande [mailto:[EMAIL PROTECTED] Gesendet: Montag, 21. Mai 2007 16:31 An: users@maven.apache.org Betreff: Re: How configure to Multiproject Site references Hi when you run the "mvn site" for Maven2 at the application root level, the command is executed to generate the site at application root level. James Abley-2 wrote: > > On 20/05/07, Mac Systems <[EMAIL PROTECTED]> wrote: >> Hello, >> >> actually i wonder how to generate an Site for an Multiproject ? >> >> The (Master) Project Site will be generated for all my Modules but i do >> not know >> how to link to each module's site ? >> >> >> Project: >> >> pom.xml >> | >> | >> >Module A >> pom.xml >> -> target/site/index.html >> >Module B >> pom.xml >> -> target/site/index.html >> >Module C >> pom.xml >> -> target/site/index.html >> >> >> regards, >> Jens Hohl >> > > I've used the element in each module's pom. > > ../../Module A/target/site/ > > It works fine for builds locally. > > Cheers, > > James > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/How-configure-to-Multiproject-Site-references-tf3787163s177.html#a10719982 Sent from the Maven - Users mailing list archive at Nabble.com. - 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]
Re: How configure to Multiproject Site references
Hi when you run the "mvn site" for Maven2 at the application root level, the command is executed to generate the site at application root level. James Abley-2 wrote: > > On 20/05/07, Mac Systems <[EMAIL PROTECTED]> wrote: >> Hello, >> >> actually i wonder how to generate an Site for an Multiproject ? >> >> The (Master) Project Site will be generated for all my Modules but i do >> not know >> how to link to each module's site ? >> >> >> Project: >> >> pom.xml >> | >> | >> >Module A >> pom.xml >> -> target/site/index.html >> >Module B >> pom.xml >> -> target/site/index.html >> >Module C >> pom.xml >> -> target/site/index.html >> >> >> regards, >> Jens Hohl >> > > I've used the element in each module's pom. > > ../../Module A/target/site/ > > It works fine for builds locally. > > Cheers, > > James > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/How-configure-to-Multiproject-Site-references-tf3787163s177.html#a10719982 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How configure to Multiproject Site references
On 20/05/07, Mac Systems <[EMAIL PROTECTED]> wrote: Hello, actually i wonder how to generate an Site for an Multiproject ? The (Master) Project Site will be generated for all my Modules but i do not know how to link to each module's site ? Project: pom.xml | | >Module A pom.xml -> target/site/index.html >Module B pom.xml -> target/site/index.html >Module C pom.xml -> target/site/index.html regards, Jens Hohl I've used the element in each module's pom. ../../Module A/target/site/ It works fine for builds locally. Cheers, James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How configure to Multiproject Site references
Hello, actually i wonder how to generate an Site for an Multiproject ? The (Master) Project Site will be generated for all my Modules but i do not know how to link to each module's site ? Project: pom.xml | | >Module A pom.xml -> target/site/index.html >Module B pom.xml -> target/site/index.html >Module C pom.xml -> target/site/index.html regards, Jens Hohl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: generating site for multiproject
Hi Marco, You could use the stage goal mvn site:stage -DstagingDirectory=C:\fullsite http://maven.apache.org/plugins/maven-site-plugin/howto.html Cheers, Vincent 2007/5/18, Marco Mistroni <[EMAIL PROTECTED]>: hi all, how can i generate only one site for my multiproject? i want to avoid to put 'hardcoded' references to point to sites of my subprojects, i was wondering if maven could do an 'all in one' site.. any help? thanks in advance and regards marco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
generating site for multiproject
hi all, how can i generate only one site for my multiproject? i want to avoid to put 'hardcoded' references to point to sites of my subprojects, i was wondering if maven could do an 'all in one' site.. any help? thanks in advance and regards marco
running webapp (war) in a multiproject environment
Hi,
I'm trying to run a maven build war file using one of the container plugins
(cargo, tomcat or jetty). While this works fine in single project setup, I
don't know how to get it properly work in multi project setup, if I have
dependencies from the war module to at least on other child project. The
multiproject setup I'm using is similar to the following (pom file are below):
parent (pom) / child1 (jar)
/ child2 (war)
where the child2 module depends on the module child1.
Building and packaging all modules from the top-level project works fine, but
starting the webapp (child2.war) is not possible. Running a "mvn tomcat:run"
from inside of module "child2" results in the following error:
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'tomcat'.
[INFO]
[INFO] Building Unnamed - example:child2:war:1.0-SNAPSHOT
[INFO]task-segment: [tomcat:run]
[INFO]
[INFO] Preparing tomcat:run
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) example:child1:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=example -DartifactId=child1 \
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) example:child2:war:1.0-SNAPSHOT
2) example:child1:jar:1.0-SNAPSHOT
--
1 required artifact is missing.
for artifact:
example:child2:war:1.0-SNAPSHOT
As far I understand maven, this error is comprehensible, because when running
maven from inside of the child module, maven doesn't know how to build the
child1 dependency. So I would think, that running "mvn tomcat:run" from inside
of the top-level module would be more appropriate. But this isn't possible,
too, because the top-level module doesn't know anything about the
maven-tomcat-plugin. For sure, I can solve this problem, by running a "mvn
install" first, go into the child2 module and run a "mvn tomcat:run". This
seems to me a little bit too complicated.
So I wonder if there something wrong with my project setup or if there is
better way to run the webapp using maven?
Carsten
===
top-level module
4.0.0
example
parent
pom
1.0-SNAPSHOT
child1
child2
${project.version}
child1
--
example
parent
1.0-SNAPSHOT
4.0.0
example
child1
jar
child2
--
example
parent
1.0-SNAPSHOT
4.0.0
example
child2
war
org.codehaus.mojo
tomcat-maven-plugin
org.codehaus.cargo
cargo-maven2-plugin
tomcat5x
/opt/apache-tomcat-5.5.17
example
child1
${example.version}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M1] multiproject basedir not changing in subprojects?
In theory that is the case. How is defined your build part in your POM ? What is your version of maven and its plugins ? Arnaud On 20/04/07, matthewadams <[EMAIL PROTECTED]> wrote: Hi all, I've got some unit tests in a subproject of a multiproject that run fine when building from the subproject's basedir, but when the subproject is built as part of the multiproject build (that is, maven is launched in the parent directory), the basedir is that of the parent directory, and my unit tests fail to find the resources they need to test (some xml files). How does Maven 1 handle setting the basedir property in subprojects during a multiproject build? It seems inutitive that the basedir property should be set appropriately for each subproject, but that's not happening. TIA, Matthew -- View this message in context: http://www.nabble.com/-M1--multiproject-basedir-not-changing-in-subprojects--tf3620470s177.html#a10109703 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M1] multiproject basedir not changing in subprojects?
Hi all, I've got some unit tests in a subproject of a multiproject that run fine when building from the subproject's basedir, but when the subproject is built as part of the multiproject build (that is, maven is launched in the parent directory), the basedir is that of the parent directory, and my unit tests fail to find the resources they need to test (some xml files). How does Maven 1 handle setting the basedir property in subprojects during a multiproject build? It seems inutitive that the basedir property should be set appropriately for each subproject, but that's not happening. TIA, Matthew -- View this message in context: http://www.nabble.com/-M1--multiproject-basedir-not-changing-in-subprojects--tf3620470s177.html#a10109703 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] exec-maven-plugin in a multiproject
Hi all,
I am using Maven 2.0.6 with the exec-maven-plugin 1.1-beta-1.
My project has a structure similar to this:
root
+child1
+child2
In child2 I am using the java goal and in child1 I am using the exec goal.
When I am building child2 alone everything works fine.
When I am building the root I am getting the error below.
If I remove the exec-maven-plugin from child1 then every works fine
again. Something from the first instance (child1) interferes with the
second instance (child2).
Please help,
Adrian.
Here is the error:
[INFO] Preparing exec:java
[WARNING] Removing: java from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [exec:java {execution: default}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
---
constituent[0]:
file:/C:/PROGRA~1/Java/MAVEN-~1.6/bin/../lib/maven-core-2.0.6-ub
er.jar
constituent[1]:
file:/C:/DOCUME~1/pm/M2639C~1/REPOSI~1/org/myproject/build/extensio
ns/myproject-build-extensions/1.0-alpha-1/myproject-build-extensions-1.0-alpha-1.jar
[AH] NOTE: this artifact is produced by some other child under the root.
[AH] NOTE: I have other children which use it, but without using the
exec-maven-plugin, and it doesn't interfere.
---
java.lang.NullPointerException
at
org.apache.maven.usability.MojoExecutionExceptionDiagnoser.diagnose(M
ojoExecutionExceptionDiagnoser.java:64)
at
org.apache.maven.usability.diagnostics.ErrorDiagnostics.diagnose(Erro
rDiagnostics.java:84)
at
org.apache.maven.DefaultMaven.logDiagnostics(DefaultMaven.java:711)
at org.apache.maven.DefaultMaven.logError(DefaultMaven.java:656)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:131)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiproject Subversion Layout
tnine wrote on Thursday, March 15, 2007 5:53 PM: > Hi Jörg, > Thanks for your reply. I have a couple of questions about > your layout. > > 1. You have two "parent" poms. One in a sub directory for > performing a > release, and another at the top level to link all modules together for > dependency resolution, is this correct? Yes. But we call the one in the parent directory builder POM, since it is not part of the release - it's even never released at all. It is simply a POM to combine several modules ... nothing more. The "real" parent POM is the one that is referenced with group and artifact id in the individual modules. > 2. You say your ".links/trunk" points to the trunk of every > sub project. > How do I get that into subversion? I don't quite understand > how to do that. See the described structure from below. The myrepo/.link/trunk directory contains a "svn:externals" property with links to the trunk of the individual (sub)modules e.g. = %< === parent-pom myrepo/parent-pom/trunk project-A myrepo/project-A/trunk project-B myrepo/project-B/trunk = %< === So if you checkout myrepo/.link/trunk subversion will automatically checkout the external references also and you end up with the subdirectories parent-pom, project-A and project-B. - Jörg > > Thanks, > Todd > > > Jörg Schaible wrote: >> >> Hi Todd, >> >> Todd Nine wrote on Friday, March 02, 2007 5:22 PM: >> >>> Hi all, >>> I'm created a multi project build using subversion for source >>> control. I've used CVS in the past, so I'm a bit confused as to >>> how I need to layout the repository for a multiproject release in >>> subversion. Here are the two options as I see them, which one >>> should I use to perform a release from the parent pom? >>> >>> Option 1 (I think this is correct) >>> >>> >>> myrepo + >>> +branches >>> +tags >>> +trunk >>> +--pom.xml(parent) >>> +-- proj A (component) >>> +-- proj B (component) >>> >>> Option 2 (I'm not sure how the parent pom would tag the whole >>> release this way) >>> >>> >>> myrepo + >>> +pom.xml >>> +Proj A(component) >>> +--branches >>> +--tags >>> +--trunk >>> +Proj B (component, same structure as proj A) >> >> IMHO it simply depends on your release cycle. If the components from >> proj A+B share the same version I'd go with option 1. If they have an >> independent release cylce, we use a modified option 2: >> >> myrepo >> + .links (2) >> + trunk >> + pom.xml >> + parent-pom (1) >> + trunk >> + pom.xml >> + project-A >> + trunk >> + pom.xml >> + project-B >> + trunk >> + pom.xml >> >> 1) The parent POM of the project has an own release cycle. Every >> component's POM will use it as parent (referenced simply with group >> and artifact id, we're not using the relPath). For a release you'll >> have to release the parent POM first. >> >> 2) This is a construction to enable easy check outs of a specific >> branch of the project i.e. normally the trunk. A subversion user >> checks out myrepo/.links/trunk to get the head revision of all >> sources. The trick is, that that directory contains external links >> to the trunks of all other modules of this project (parent-pom, >> project-A, project-B). The pom.xml in this directory is never >> released, it contains simply a modules section for the three modules >> to enable a multi module build. With this construct you're able to >> setup easily branches e.g.: >> >> myrepo >> + .links >> + branch-2.x >> + pom.xml >> >> The external links in "myrepo/.links/branch-2.x" will point to the >> individual branches of the module. And this is really convenient, if >> branch 2.x does not mean that every subproject has an own branch (you >> might be able to use a released version - therefore no need to build >> the component that has no changes in the branch). >> >> This setup works quite well for us. >> >> - Jörg >> >> > - >> 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]
RE: Multiproject Subversion Layout
Hi Jörg, Thanks for your reply. I have a couple of questions about your layout. 1. You have two "parent" poms. One in a sub directory for performing a release, and another at the top level to link all modules together for dependency resolution, is this correct? 2. You say your ".links/trunk" points to the trunk of every sub project. How do I get that into subversion? I don't quite understand how to do that. Thanks, Todd Jörg Schaible wrote: > > Hi Todd, > > Todd Nine wrote on Friday, March 02, 2007 5:22 PM: > >> Hi all, >> I'm created a multi project build using subversion for source >> control. I've used CVS in the past, so I'm a bit confused as to how I >> need to layout the repository for a multiproject release in >> subversion. Here are the two options as I see them, which one should >> I use to perform a release from the parent pom? >> >> Option 1 (I think this is correct) >> >> >> myrepo + >> +branches >> +tags >> +trunk >> +--pom.xml(parent) >> +-- proj A (component) >> +-- proj B (component) >> >> Option 2 (I'm not sure how the parent pom would tag the whole >> release this way) >> >> >> myrepo + >> +pom.xml >> +Proj A(component) >> +--branches >> +--tags >> +--trunk >> +Proj B (component, same structure as proj A) > > IMHO it simply depends on your release cycle. If the components from proj > A+B share the same version I'd go with option 1. If they have an > independent release cylce, we use a modified option 2: > > myrepo > + .links (2) > + trunk > + pom.xml > + parent-pom (1) > + trunk > + pom.xml > + project-A > + trunk > + pom.xml > + project-B > + trunk > + pom.xml > > 1) The parent POM of the project has an own release cycle. Every > component's POM will use it as parent (referenced simply with group and > artifact id, we're not using the relPath). For a release you'll have to > release the parent POM first. > > 2) This is a construction to enable easy check outs of a specific branch > of the project i.e. normally the trunk. A subversion user checks out > myrepo/.links/trunk to get the head revision of all sources. The trick is, > that that directory contains external links to the trunks of all other > modules of this project (parent-pom, project-A, project-B). The pom.xml in > this directory is never released, it contains simply a modules section for > the three modules to enable a multi module build. With this construct > you're able to setup easily branches e.g.: > > myrepo > + .links > + branch-2.x > + pom.xml > > The external links in "myrepo/.links/branch-2.x" will point to the > individual branches of the module. And this is really convenient, if > branch 2.x does not mean that every subproject has an own branch (you > might be able to use a released version - therefore no need to build the > component that has no changes in the branch). > > This setup works quite well for us. > > - Jörg > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Multiproject-Subversion-Layout-tf3334487s177.html#a9498748 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] How to bypass unit testing durng multiproject build with Maven 2
Hi, > So I did mvn -Dmaven.test.skip=true package, it still compiled and ran the > JUNIT testing... Strange. What exactly does your command line look like? Do you have a special configuration entry for tests in your POM? > I also did mvn package compile, JUNIT is still running... "package" implies "compile", i.e. it isn't necessary to add both commands to the command line > Maybe this is the purpose for a multiproject build to make sure that all > the > projects get compiled and tested, but how about the deployment, what if I > want to skip the deployment part defined in the POM.xml? still puzzled. Deployment occurs only if you tell Maven to do this, i.e. "mvn deploy" etc. BTW, perhaps the following may be of some help: http://maven.apache.org/plugins/maven-surefire-plugin/examples/skipping-test.html HTH Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] How to bypass unit testing durng multiproject build with Maven 2
Thanks a lot, Thorsten So I did mvn -Dmaven.test.skip=true package, it still compiled and ran the JUNIT testing... I also did mvn package compile, JUNIT is still running... Maybe this is the purpose for a multiproject build to make sure that all the projects get compiled and tested, but how about the deployment, what if I want to skip the deployment part defined in the POM.xml? still puzzled. Thanks, ms -- View this message in context: http://www.nabble.com/How-to-bypass-unit-testing-durng-multiproject-build-with-Maven-2-tf3374096s177.html#a9398426 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to bypass unit testing durng multiproject build with Maven 2
Hi, > I think I can use "mvn package" to do a multiproject build with Maven 2, > my > question is - how do I do a quick build with "mvn package" by bypassing > the > junit testing. http://maven.apache.org/general.html#skip-test Is that what you're looking for? Cheers Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to bypass unit testing durng multiproject build with Maven 2
Hello Maven gurus, I think I can use "mvn package" to do a multiproject build with Maven 2, my question is - how do I do a quick build with "mvn package" by bypassing the junit testing. Thanks, MavenStarter -- View this message in context: http://www.nabble.com/How-to-bypass-unit-testing-durng-multiproject-build-with-Maven-2-tf3374096s177.html#a9389406 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiproject Subversion Layout
Hi Todd, Todd Nine wrote on Friday, March 02, 2007 5:22 PM: > Hi all, > I'm created a multi project build using subversion for source > control. I've used CVS in the past, so I'm a bit confused as to how I > need to layout the repository for a multiproject release in > subversion. Here are the two options as I see them, which one should > I use to perform a release from the parent pom? > > Option 1 (I think this is correct) > > > myrepo + > +branches > +tags > +trunk > +--pom.xml(parent) > +-- proj A (component) > +-- proj B (component) > > Option 2 (I'm not sure how the parent pom would tag the whole > release this way) > > > myrepo + > +pom.xml > +Proj A(component) > +--branches > +--tags > +--trunk > +Proj B (component, same structure as proj A) IMHO it simply depends on your release cycle. If the components from proj A+B share the same version I'd go with option 1. If they have an independent release cylce, we use a modified option 2: myrepo + .links (2) + trunk + pom.xml + parent-pom (1) + trunk + pom.xml + project-A + trunk + pom.xml + project-B + trunk + pom.xml 1) The parent POM of the project has an own release cycle. Every component's POM will use it as parent (referenced simply with group and artifact id, we're not using the relPath). For a release you'll have to release the parent POM first. 2) This is a construction to enable easy check outs of a specific branch of the project i.e. normally the trunk. A subversion user checks out myrepo/.links/trunk to get the head revision of all sources. The trick is, that that directory contains external links to the trunks of all other modules of this project (parent-pom, project-A, project-B). The pom.xml in this directory is never released, it contains simply a modules section for the three modules to enable a multi module build. With this construct you're able to setup easily branches e.g.: myrepo + .links + branch-2.x + pom.xml The external links in "myrepo/.links/branch-2.x" will point to the individual branches of the module. And this is really convenient, if branch 2.x does not mean that every subproject has an own branch (you might be able to use a released version - therefore no need to build the component that has no changes in the branch). This setup works quite well for us. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Releasing a multiproject
I've put together a group of projects as a multiproject (so the parent pom.xml references the others as modules). They all build just fine as snapshots. I'm now trying to do a release:prepare on the group as a whole (running from the parent pom directory). There are interdependencies within the group, and the prepare goal seems to set the versions correctly. However, once the goal has changed all the pom.xml file, it attempts to do a package goal for the group of projects, and this fails because it can't find the release version of the dependent jar (which is being released as part of this operation). My understanding was that running mvn package on a multiproject would use the targets of each of those projects to find dependencies if there were interdependencies, but it doesn't seem to work that way. Is something going wrong here, or am I expecting it to do something it's not supposed to do? ..David..
Multiproject Subversion Layout
Hi all, I'm created a multi project build using subversion for source control. I've used CVS in the past, so I'm a bit confused as to how I need to layout the repository for a multiproject release in subversion. Here are the two options as I see them, which one should I use to perform a release from the parent pom? Option 1 (I think this is correct) myrepo + +branches +tags +trunk +--pom.xml(parent) +-- proj A (component) +-- proj B (component) Option 2 (I'm not sure how the parent pom would tag the whole release this way) myrepo + +pom.xml +Proj A(component) +--branches +--tags +--trunk +Proj B (component, same structure as proj A) Thanks, Todd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject in eclipse VS subversion client
Thanks! Subversive-JavaHL solved all the problems thus far. INHO this should really be documented on the mvn eclipse:eclipse plugin website. nicolas de loof schreef: I had to configure subversive (Preferences/Team/SVN) to use JavaHL svn client to get project detected as beeing shared. 2007/1/3, Geoffrey De Smet <[EMAIL PROTECTED]>: Subversive 1.1.0-RC? (not 1.0.x) works in some of my test workspaces - but not in all. The sequence of the actions taken seems to affect when it works or not - most of the time team/share is not available (and when it is it could end up corrupting the local copy). Anyone know the proper sequence? nicolas de loof schreef: > I've registered an issue for this in subclipse. Such configuration make my > Eclipse hang ! > > I'm using subversive plugin from polarion in Eclipse 3.2, that supports > nested projects. This plugin has been approved as an eclipse project ( > http://www.eclipse.org/proposals/subversive/) so will become the defualt > SVN > plugin for next eclipse builds. > > After checkout, you can "import exisitng project into workspace" for the > modules. To import all modules in one click, you have to temporary delete > the main ".project" file so that eclipse will search sub-directories. > > Nico. > > 2007/1/3, Geoffrey De Smet <[EMAIL PROTECTED]>: >> >> In Eclipse, I 've have a multiproject open like this: >> >> myproj-> simple project >> myproj/myproj-api -> java project >> myproj/myproj-gui -> java project >> >> Which subversion plugin for eclipse can handle this? >> I've tried both Subclipse and Subversion: >> - Subclipse: seems to get confused about file locations >> - Subversion: won't even allow me to enable my subprojects as team >> synchronized. >> >> Has anyone accomplished combining a svn plugin for eclipse with a >> non-flat mutliproject? >> >> Thanks for any and all help, >> Geoffrey De Smet >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject in eclipse VS subversion client
I had to configure subversive (Preferences/Team/SVN) to use JavaHL svn client to get project detected as beeing shared. 2007/1/3, Geoffrey De Smet <[EMAIL PROTECTED]>: Subversive 1.1.0-RC? (not 1.0.x) works in some of my test workspaces - but not in all. The sequence of the actions taken seems to affect when it works or not - most of the time team/share is not available (and when it is it could end up corrupting the local copy). Anyone know the proper sequence? nicolas de loof schreef: > I've registered an issue for this in subclipse. Such configuration make my > Eclipse hang ! > > I'm using subversive plugin from polarion in Eclipse 3.2, that supports > nested projects. This plugin has been approved as an eclipse project ( > http://www.eclipse.org/proposals/subversive/) so will become the defualt > SVN > plugin for next eclipse builds. > > After checkout, you can "import exisitng project into workspace" for the > modules. To import all modules in one click, you have to temporary delete > the main ".project" file so that eclipse will search sub-directories. > > Nico. > > 2007/1/3, Geoffrey De Smet <[EMAIL PROTECTED]>: >> >> In Eclipse, I 've have a multiproject open like this: >> >> myproj-> simple project >> myproj/myproj-api -> java project >> myproj/myproj-gui -> java project >> >> Which subversion plugin for eclipse can handle this? >> I've tried both Subclipse and Subversion: >> - Subclipse: seems to get confused about file locations >> - Subversion: won't even allow me to enable my subprojects as team >> synchronized. >> >> Has anyone accomplished combining a svn plugin for eclipse with a >> non-flat mutliproject? >> >> Thanks for any and all help, >> Geoffrey De Smet >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject in eclipse VS subversion client
Subversive 1.1.0-RC? (not 1.0.x) works in some of my test workspaces - but not in all. The sequence of the actions taken seems to affect when it works or not - most of the time team/share is not available (and when it is it could end up corrupting the local copy). Anyone know the proper sequence? nicolas de loof schreef: I've registered an issue for this in subclipse. Such configuration make my Eclipse hang ! I'm using subversive plugin from polarion in Eclipse 3.2, that supports nested projects. This plugin has been approved as an eclipse project ( http://www.eclipse.org/proposals/subversive/) so will become the defualt SVN plugin for next eclipse builds. After checkout, you can "import exisitng project into workspace" for the modules. To import all modules in one click, you have to temporary delete the main ".project" file so that eclipse will search sub-directories. Nico. 2007/1/3, Geoffrey De Smet <[EMAIL PROTECTED]>: In Eclipse, I 've have a multiproject open like this: myproj-> simple project myproj/myproj-api -> java project myproj/myproj-gui -> java project Which subversion plugin for eclipse can handle this? I've tried both Subclipse and Subversion: - Subclipse: seems to get confused about file locations - Subversion: won't even allow me to enable my subprojects as team synchronized. Has anyone accomplished combining a svn plugin for eclipse with a non-flat mutliproject? Thanks for any and all help, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiproject in eclipse VS subversion client
Hi,
Perso, I only record modules (java project) in eclipse and not the root.
The content of myproj which is pom packaging (contains only pom, src/site/*
and not sources) can be managed with cli.
--
Olivier
-Message d'origine-
De : news [mailto:[EMAIL PROTECTED] De la part de Geoffrey De Smet
Envoyé : mercredi 3 janvier 2007 11:09
À : users@maven.apache.org
Objet : Multiproject in eclipse VS subversion client
In Eclipse, I 've have a multiproject open like this:
myproj-> simple project
myproj/myproj-api -> java project
myproj/myproj-gui -> java project
Which subversion plugin for eclipse can handle this?
I've tried both Subclipse and Subversion:
- Subclipse: seems to get confused about file locations
- Subversion: won't even allow me to enable my subprojects as team synchronized.
Has anyone accomplished combining a svn plugin for eclipse with a non-flat
mutliproject?
Thanks for any and all help,
Geoffrey De Smet
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, any attachments and the information contained therein ("this
message") are confidential and intended solely for the use of the addressee(s).
If you have received this message in error please send it back to the sender
and delete it. Unauthorized publication, use, dissemination or disclosure of
this message, either in whole or in part is strictly prohibited.
**
Ce message électronique et tous les fichiers joints ainsi que les informations
contenues dans ce message ( ci après "le message" ), sont confidentiels et
destinés exclusivement à l'usage de la personne à laquelle ils sont adressés.
Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur
et de le détruire. Toutes diffusion, publication, totale ou partielle ou
divulgation sous quelque forme que se soit non expressément autorisées de ce
message, sont interdites.
**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject in eclipse VS subversion client
I've registered an issue for this in subclipse. Such configuration make my Eclipse hang ! I'm using subversive plugin from polarion in Eclipse 3.2, that supports nested projects. This plugin has been approved as an eclipse project ( http://www.eclipse.org/proposals/subversive/) so will become the defualt SVN plugin for next eclipse builds. After checkout, you can "import exisitng project into workspace" for the modules. To import all modules in one click, you have to temporary delete the main ".project" file so that eclipse will search sub-directories. Nico. 2007/1/3, Geoffrey De Smet <[EMAIL PROTECTED]>: In Eclipse, I 've have a multiproject open like this: myproj-> simple project myproj/myproj-api -> java project myproj/myproj-gui -> java project Which subversion plugin for eclipse can handle this? I've tried both Subclipse and Subversion: - Subclipse: seems to get confused about file locations - Subversion: won't even allow me to enable my subprojects as team synchronized. Has anyone accomplished combining a svn plugin for eclipse with a non-flat mutliproject? Thanks for any and all help, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiproject in eclipse VS subversion client
In Eclipse, I 've have a multiproject open like this: myproj-> simple project myproj/myproj-api -> java project myproj/myproj-gui -> java project Which subversion plugin for eclipse can handle this? I've tried both Subclipse and Subversion: - Subclipse: seems to get confused about file locations - Subversion: won't even allow me to enable my subprojects as team synchronized. Has anyone accomplished combining a svn plugin for eclipse with a non-flat mutliproject? Thanks for any and all help, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse .classpath generation in a multiproject with eclipse:eclipse
On 11/23/06, AndreasWuest <[EMAIL PROTECTED]> wrote: i have seen the guide, but it did not really convice me. so this guide tells me that i need at least two eclipse instances. one that only servers as a cvs client, and one which is used as java ide. i can't see the disadvantage of having a .project and a .classpath created in the parent, with properly set src and output folders. correct me if i am wrong, but the only disadvantage would be the fact, that it might be complicated to collect all the data and create the correct paths, or do i miss something ? once the src and output folders are set correctly everything is supposed to work fine, no need for two eclipse instances and inconvenient importing actions. You don't need two eclipse instances. The problem as Thomas Recloux points out is that each module has a different classpath. The parent "project" in eclipse should not be an aggregation of all module classpaths. It should just be a simple project with no java/classpath details in it at all. The problem is that eclipse does not support projects whose folder structure lives within an already mounted project. In Eclipse 3.2 this restriction has been lifted slightly. With the snapshot build of the eclipse:eclipse plugin you can get correct .project and .classpath created for your entire maven project tree. You then need to open the navigator view and delete the parent project's ".project" file, File -> Import -> General -> Existing projects into Workspace -> Select root directory = your project root, and then select all the project you want to import. If you forget to delete the parent project's ".project" file then the list of projects will be empty. The above setup means you can use one CVS checkout of your parent root, load the parent and all modules in eclipse and use CVS correctly at any of the mounted projects. If you are using subversion I believe there is an outstanding bug with subclipse that causes projects within projects to consume 100% CPU. The Nabble archives have plenty of discussions on this. See http://www.nabble.com/forum/ViewPost.jtp?post=5862059&framed=y&skin=177 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse .classpath generation in a multiproject with eclipse:eclipse
i have seen the guide, but it did not really convice me. so this guide tells me that i need at least two eclipse instances. one that only servers as a cvs client, and one which is used as java ide. You can't use an other cvs client for the root pom ? i can't see the disadvantage of having a .project and a .classpath created in the parent, with properly set src and output folders. correct me if i am wrong, but the only disadvantage would be the fact, that it might be complicated to collect all the data and create the correct paths, or do i miss something ? once the src and output folders are set correctly everything is supposed to work fine, no need for two eclipse instances and inconvenient importing actions. The first response I can give is that the classpath is not the same for your three modules. -- Thomas Recloux a.k.a Karmelitre http://karmelitre.tartachuc.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse .classpath generation in a multiproject with eclipse:eclipse
i have seen the guide, but it did not really convice me. so this guide tells me that i need at least two eclipse instances. one that only servers as a cvs client, and one which is used as java ide. i can't see the disadvantage of having a .project and a .classpath created in the parent, with properly set src and output folders. correct me if i am wrong, but the only disadvantage would be the fact, that it might be complicated to collect all the data and create the correct paths, or do i miss something ? once the src and output folders are set correctly everything is supposed to work fine, no need for two eclipse instances and inconvenient importing actions. The maven eclipse plugin creates eclipse .project and .classpath files for each maven project ( : pom.xml file). You should read this guide : http://maven.apache.org/guides/mini/guide-ide-eclipse.html 2006/11/22, AndreasWuest <[EMAIL PROTECTED]>: hello, i have a question concerning the usage of eclipse in a multiproject build. i have a project that has the following structure : + project + ear + ejb + web The project contains a pom.xml with the defined modules: ear ejb web each of the modules contains a pom.xml of its own, well the usual stuff. in the standalone version (without eclipse) everything works fine. the problem occurs when i import that project into eclipse and try to compile the project. after creating the .classpath and .project files with mvn eclipse:eclipse from the project directory i have a .classpath and a .project file in each of my module directories, not in my project directory ! however eclipse ignores the created files in the modules directories, it expects one file to be created in the project directory (root of the project). so is there a way to tell the plugin to create a proper classpath and project file for the root directory (the parent). the file .classpath content is supposed to look something like : . basically i need for the source files of each module a specific output directory (usually the classes in the target directory). so what is needed is a kind of merged .classpath file in my project directory that contains the individual .classpath file information from the mdules, so the eclipse ide can compile the java classes and put them into the correct (module) output folders. i can provide a testcase on request. thanks in advance, andy - 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]
Re: eclipse .classpath generation in a multiproject with eclipse:eclipse
The maven eclipse plugin creates eclipse .project and .classpath files for each maven project ( : pom.xml file). You should read this guide : http://maven.apache.org/guides/mini/guide-ide-eclipse.html 2006/11/22, AndreasWuest <[EMAIL PROTECTED]>: hello, i have a question concerning the usage of eclipse in a multiproject build. i have a project that has the following structure : + project + ear + ejb + web The project contains a pom.xml with the defined modules: ear ejb web each of the modules contains a pom.xml of its own, well the usual stuff. in the standalone version (without eclipse) everything works fine. the problem occurs when i import that project into eclipse and try to compile the project. after creating the .classpath and .project files with mvn eclipse:eclipse from the project directory i have a .classpath and a .project file in each of my module directories, not in my project directory ! however eclipse ignores the created files in the modules directories, it expects one file to be created in the project directory (root of the project). so is there a way to tell the plugin to create a proper classpath and project file for the root directory (the parent). the file .classpath content is supposed to look something like : . basically i need for the source files of each module a specific output directory (usually the classes in the target directory). so what is needed is a kind of merged .classpath file in my project directory that contains the individual .classpath file information from the mdules, so the eclipse ide can compile the java classes and put them into the correct (module) output folders. i can provide a testcase on request. thanks in advance, andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thomas Recloux a.k.a Karmelitre http://karmelitre.tartachuc.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
eclipse .classpath generation in a multiproject with eclipse:eclipse
hello, i have a question concerning the usage of eclipse in a multiproject build. i have a project that has the following structure : + project + ear + ejb + web The project contains a pom.xml with the defined modules: ear ejb web each of the modules contains a pom.xml of its own, well the usual stuff. in the standalone version (without eclipse) everything works fine. the problem occurs when i import that project into eclipse and try to compile the project. after creating the .classpath and .project files with mvn eclipse:eclipse from the project directory i have a .classpath and a .project file in each of my module directories, not in my project directory ! however eclipse ignores the created files in the modules directories, it expects one file to be created in the project directory (root of the project). so is there a way to tell the plugin to create a proper classpath and project file for the root directory (the parent). the file .classpath content is supposed to look something like : path="ear/src/main/java"/> path="ejb/src/main/java"/> path="ejb/target/generated-sources/xdoclet"/> path="web/src/main/java"/> . path="org.eclipse.jdt.launching.JRE_CONTAINER"/> basically i need for the source files of each module a specific output directory (usually the classes in the target directory). so what is needed is a kind of merged .classpath file in my project directory that contains the individual .classpath file information from the mdules, so the eclipse ide can compile the java classes and put them into the correct (module) output folders. i can provide a testcase on request. thanks in advance, andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] multiproject that contains a mojo sub-project and sub-projects that rely on that mojo for build
Should I be able to have a multi-project that has a Mojo as one sub-project and then have other sub-projects that use that Mojo in their build? I can't seem to get it to work. the top-level build fails complaining about the plugin not being installed and not downloadable Thanks, Matthew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Multiproject execution directory
Hello! I've tried googling for this, but with no success so far. When running multi-project/multi-module/sub-module builds, does maven2 use the execution directory of the aggregating project for /all/ projects? If so, is it possible to make sure each sub-projects is being run in its own root? I use a flat (eclipse-like) project structure: project1/ project2/ aggregating_project/ and ../project1 ../project2 in the aggregating_project pom.xml. I know, "you shouldn't depend on the execution directory" etc, but this time I really need it. Cheers Daniel -- __ [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven multiproject, test inheritance
Cheers for the reply Philippe.
Cool, didn't know you could do that. I am guessing that you need to run the
maven jar:test-jar goal to create the test jar? (The generates an error for
me?)
My original idea was to create a brand new sub project that would handle all
unit tests, so it could share resources (DB connections, parsed XML files
etc...) more easily. Would it make sense to use this approach?
Or would this create more hassle than its worth?
Robert
Philippe Faes wrote:
>
> Rob,
>
> You can make the test classes of one project visible in the test phase
> of another project:
>
>
> com.example
> someArtifact
> 0.1.1-SNAPSHOT
> test-jar
> test
>
>
> greets,
> Philippe
>
> On Mon, 2006-10-09 at 06:10 -0700, RobertK wrote:
>> Hi,
>>
>> first off, using maven 1.0.2 multiproject to build, test and deploy about
>> 8
>> sub-projects. Everything working there smoothly (got to love Maven! :) )
>>
>> Now my question, many of my projects repeat the same unit test or data,
>> so
>> the whole project suffers from the annoying / untidy symptom of "copy and
>> paste". So what I am wondering, is there an easier (cleaner) way to do
>> it?
>>
>> Example, I have 43 Tester.java classes for testing various different
>> packages. Each one of them has the following code,
>>
>> public Tester(String a_name)
>> {
>> super(a_name);
>> }
>>
>> /**
>> * Run all tests in this package.
>> *
>> * @param args
>> */
>> public static void main(String[] args)
>> {
>> junit.textui.TestRunner.run(suite());
>> }
>>
>>
>> I mean, there must be a better way? There are over 500 unit tests in the
>> projects, so having one giant test suite is out of the question. Need
>> some
>> sort of strategy to make common utility classes available to multiple
>> project and allow some form of inheritance from a base class.
>>
>> I have some ideas, but really looking for alternatives, see if any one
>> can
>> think of a better way. So does any one have any suggestions?
>>
>> Cheers,
>> Rob
> --
> ir. Philippe Faes
> Ghent University - Department ELIS
> Sint-Pietersnieuwstraat 41 -- B-9000 Gent
> Tel:+32 9 264 95 25 - Fax:+32 9 264 35 94
> http://www.elis.UGent.be/~pfaes
> ON5DEU -- LPIC1 -- gpg-key:173720B6
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Maven-multiproject%2C-test-inheritance-tf2409917.html#a6719634
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven multiproject, test inheritance
Rob,
You can make the test classes of one project visible in the test phase
of another project:
com.example
someArtifact
0.1.1-SNAPSHOT
test-jar
test
greets,
Philippe
On Mon, 2006-10-09 at 06:10 -0700, RobertK wrote:
> Hi,
>
> first off, using maven 1.0.2 multiproject to build, test and deploy about 8
> sub-projects. Everything working there smoothly (got to love Maven! :) )
>
> Now my question, many of my projects repeat the same unit test or data, so
> the whole project suffers from the annoying / untidy symptom of "copy and
> paste". So what I am wondering, is there an easier (cleaner) way to do it?
>
> Example, I have 43 Tester.java classes for testing various different
> packages. Each one of them has the following code,
>
> public Tester(String a_name)
> {
> super(a_name);
> }
>
> /**
> * Run all tests in this package.
> *
> * @param args
> */
> public static void main(String[] args)
> {
> junit.textui.TestRunner.run(suite());
> }
>
>
> I mean, there must be a better way? There are over 500 unit tests in the
> projects, so having one giant test suite is out of the question. Need some
> sort of strategy to make common utility classes available to multiple
> project and allow some form of inheritance from a base class.
>
> I have some ideas, but really looking for alternatives, see if any one can
> think of a better way. So does any one have any suggestions?
>
> Cheers,
> Rob
--
ir. Philippe Faes
Ghent University - Department ELIS
Sint-Pietersnieuwstraat 41 -- B-9000 Gent
Tel:+32 9 264 95 25 - Fax:+32 9 264 35 94
http://www.elis.UGent.be/~pfaes
ON5DEU -- LPIC1 -- gpg-key:173720B6
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven multiproject, test inheritance
Hi,
first off, using maven 1.0.2 multiproject to build, test and deploy about 8
sub-projects. Everything working there smoothly (got to love Maven! :) )
Now my question, many of my projects repeat the same unit test or data, so
the whole project suffers from the annoying / untidy symptom of "copy and
paste". So what I am wondering, is there an easier (cleaner) way to do it?
Example, I have 43 Tester.java classes for testing various different
packages. Each one of them has the following code,
public Tester(String a_name)
{
super(a_name);
}
/**
* Run all tests in this package.
*
* @param args
*/
public static void main(String[] args)
{
junit.textui.TestRunner.run(suite());
}
I mean, there must be a better way? There are over 500 unit tests in the
projects, so having one giant test suite is out of the question. Need some
sort of strategy to make common utility classes available to multiple
project and allow some form of inheritance from a base class.
I have some ideas, but really looking for alternatives, see if any one can
think of a better way. So does any one have any suggestions?
Cheers,
Rob
--
View this message in context:
http://www.nabble.com/Maven-multiproject%2C-test-inheritance-tf2409917.html#a6717273
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Multiproject run V/S Individual run
hi all i am using maven 2.0.4 i used multiproject environment ,in this one project is dependent on other like wise .,these project work fine if i run all together from parent pom but when i run any one project it go for downloading the dependency of dependent project i am unable to understand why this is happening because that dependency is present in my local repository Regards Neeraj
Re: Multiproject Rector
It's based on dependencies specified by the projects. On 9/30/06, Neeraj Bisht <[EMAIL PROTECTED]> wrote: hi all i am unable to get answer of my Question regarding maven 1.0.2 i want to know that while building the multiple project through reactor in maven 1.0.2 , is build on the bases of dependency based on each othere or its build in the sorted order Regards Neeraj -- http://www.multitask.com.au/people/dion/ Rule of Acquisition #91: Hear all, trust nothing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject Rector
Only one way to find out: try it out. I'm going to guess dependency but the bigger question might be why you are even using 1.0.2? On 9/30/06, Neeraj Bisht <[EMAIL PROTECTED]> wrote: hi all i am unable to get answer of my Question regarding maven 1.0.2 i want to know that while building the multiple project through reactor in maven 1.0.2 , is build on the bases of dependency based on each othere or its build in the sorted order Regards Neeraj - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiproject Rector
hi all i am unable to get answer of my Question regarding maven 1.0.2 i want to know that while building the multiple project through reactor in maven 1.0.2 , is build on the bases of dependency based on each othere or its build in the sorted order Regards Neeraj
Re: Uploading multiproject to central repo: Packaging cannot be POM when creating an upload bundle.
We 'll wait with pushing Spring-richclient to Ibiblio till http://jira.codehaus.org/browse/MREPOSITORY-3 is fixed. (Anyone else is free to push it up there though) With kind regards, Geoffrey De Smet Geoffrey De Smet wrote: We 'd like to get spring-richclient 0.2.1 (build with m2) on the central repo. We have it deployed in our repo: http://spring-rich-c.sourceforge.net/maven2repository/org/springframework/richclient/ and we have the source here: https://svn.sourceforge.net/svnroot/spring-rich-c/tags/spring-richclient-0.2.1/ So I followed "Guide to uploading artifacts to Ibiblio" from http://maven.apache.org/guides/mini/guide-ibiblio-upload.html but as soon as I did mvn source:jar javadoc:jar repository:bundle-create I got this error: Packaging cannot be POM when creating an upload bundle. which is probably related to this bug: http://jira.codehaus.org/browse/MREPOSITORY-3 so what's the easiest way to get spring-richclient on the central repo? - ask for a sync from our repo? is that possible? - mess around with manually doing each module (which are a lot...) and do the parent pom's also manually? - Just wait till MREPOSITORY-3 is fixed and then do it (even it's just a snapshot)? - Will Archiva help in this in any way in the future? Thanks for any and all help. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
multiproject amazing
hi all i am using the multiroject and each project is dependent on each other while runing the multiproject goal the build started in shorted oder ,but in maven site i come to know that thr build will take place on the bases of dependency but in my case it is not working can any one help me where i am wrong or which property i am forget to specify Regards Neeraj
Uploading multiproject to central repo: Packaging cannot be POM when creating an upload bundle.
We 'd like to get spring-richclient 0.2.1 (build with m2) on the central repo. We have it deployed in our repo: http://spring-rich-c.sourceforge.net/maven2repository/org/springframework/richclient/ and we have the source here: https://svn.sourceforge.net/svnroot/spring-rich-c/tags/spring-richclient-0.2.1/ So I followed "Guide to uploading artifacts to Ibiblio" from http://maven.apache.org/guides/mini/guide-ibiblio-upload.html but as soon as I did mvn source:jar javadoc:jar repository:bundle-create I got this error: Packaging cannot be POM when creating an upload bundle. which is probably related to this bug: http://jira.codehaus.org/browse/MREPOSITORY-3 so what's the easiest way to get spring-richclient on the central repo? - ask for a sync from our repo? is that possible? - mess around with manually doing each module (which are a lot...) and do the parent pom's also manually? - Just wait till MREPOSITORY-3 is fixed and then do it (even it's just a snapshot)? - Will Archiva help in this in any way in the future? Thanks for any and all help. -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Propose structure for multiproject
1. Yes, you will have fun configuring the complete paths in every pom. 2. You will need to use filesets with includes/excludes to specify which files to use for each test, and include that in the poms specified in #1. This is going to be complicated and troublesome for you. It is far better (and easier!) to reorganize the project to "fit" Maven than to force Maven to fit your project, imho. Wayne On 9/20/06, Neeraj Bisht <[EMAIL PROTECTED]> wrote: Hello all, Please help to get out of the following confusions: I am having many projects which may be dependent on each other or not.But we need to make one ear having all the archives file made of all projects. In one project, we can have one jar,jar+war,jar+war+har,or some other application specific archives like if har not supported by other applciation servers. These all projects are different cvs modules in the following structure but with no maven files(also we can't place file there) and test contains the testcases for all sub projects(object/services/UI) of one project/CVS module. Following is the structure: Project1 src objects(har) java resource services(jar) java resource UI(war) java resource webapps test So two problems: 1)Is it possible that we place our maven scripts somewhere at our system and projects are somewhere else, Can maven build all subprojects,make war,har,jar etc from that location and then package all of them to make ear? 2)Now i want ot run the testcases after building the project,not after making war/har/jar.I know if we place test in subproject thjen before making any archive it will run the testcases but ours is different case.Our testcases are in Main project not in different subprojects,so how can we achieve it? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: multiproject structure
Hi, What you need is a project with modules... Create a pom.xml file with pom packaging (pom) in this file, place tag with contains all the module (your sub-project). Regards, Sylvain Deschênes On 9/21/06, Neeraj Bisht <[EMAIL PROTECTED]> wrote: Hello all, Please help to get out of the following confusions: I am having many projects which may be dependent on each other or not.Butwe need to make one ear having all the archives file made of all projects. In one project, we can have one jar,jar+war,jar+war+har,or some other application specific archives like if har not supported by other applciation servers. These all projects are different cvs modules in the following structure but with no maven files(also we can't place file there) and test contains the testcases for all sub projects(object/services/UI) of one project/CVS module. Following is the structure: Project1 src objects(har) java resource services(jar) java resource UI(war) java resource webapps test So two problems: 1)Is it possible that we place our maven scripts somewhere at our system and projects are somewhere else, Can maven build all subprojects,make war,har,jar etc from that location and then package all of them to make ear? 2)Now i want ot run the testcases after building the project,not after making war/har/jar.I know if we place test in subproject thjen before making any archive it will run the testcases but ours is different case.Our testcases are in Main project not in different subprojects,so how can we achieve it? Regards Neeraj
multiproject structure
Hello all, Please help to get out of the following confusions: I am having many projects which may be dependent on each other or not.But we need to make one ear having all the archives file made of all projects. In one project, we can have one jar,jar+war,jar+war+har,or some other application specific archives like if har not supported by other applciation servers. These all projects are different cvs modules in the following structure but with no maven files(also we can't place file there) and test contains the testcases for all sub projects(object/services/UI) of one project/CVS module. Following is the structure: Project1 src objects(har) java resource services(jar) java resource UI(war) java resource webapps test So two problems: 1)Is it possible that we place our maven scripts somewhere at our system and projects are somewhere else, Can maven build all subprojects,make war,har,jar etc from that location and then package all of them to make ear? 2)Now i want ot run the testcases after building the project,not after making war/har/jar.I know if we place test in subproject thjen before making any archive it will run the testcases but ours is different case.Our testcases are in Main project not in different subprojects,so how can we achieve it? Regards Neeraj
Propose structure for multiproject
Hello all, Please help to get out of the following confusions: I am having many projects which may be dependent on each other or not.But we need to make one ear having all the archives file made of all projects. In one project, we can have one jar,jar+war,jar+war+har,or some other application specific archives like if har not supported by other applciation servers. These all projects are different cvs modules in the following structure but with no maven files(also we can't place file there) and test contains the testcases for all sub projects(object/services/UI) of one project/CVS module. Following is the structure: Project1 src objects(har) java resource services(jar) java resource UI(war) java resource webapps test So two problems: 1)Is it possible that we place our maven scripts somewhere at our system and projects are somewhere else, Can maven build all subprojects,make war,har,jar etc from that location and then package all of them to make ear? 2)Now i want ot run the testcases after building the project,not after making war/har/jar.I know if we place test in subproject thjen before making any archive it will run the testcases but ours is different case.Our testcases are in Main project not in different subprojects,so how can we achieve it?
Re: multiproject plugin
You should use the multiproject:deploy goal for that. HTH, -Lukas neeraj daffodil wrote: hi all i am building multiproject through maven 1.0.2 with the help of maven:recator by defining the following in maven.xml it is working well but what happen that the all four goals are running for each module but i only want that the specific module will run for each type of project for that i define the maven.multiproject.type=(war,jar,ear) as i required in our module but i am not geeting theresult as my need due ,all four gaol are running for each module , i am not able to get that it is its feature or there is somthing which i am lacking in my project.properties to define any one can help me where i am wrong Regards Neeraj - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
multiproject plugin
hi all i am building multiproject through maven 1.0.2 with the help of maven:recator by defining the following in maven.xml it is working well but what happen that the all four goals are running for each module but i only want that the specific module will run for each type of project for that i define the maven.multiproject.type=(war,jar,ear) as i required in our module but i am not geeting theresult as my need due ,all four gaol are running for each module , i am not able to get that it is its feature or there is somthing which i am lacking in my project.properties to define any one can help me where i am wrong Regards Neeraj
Re: DocCheck using multiproject?
Hi Mick,
You might have already moved on to m2, but for the record...
On 9/9/05, Mick Knutson <[EMAIL PROTECTED]> wrote:
I am trying to run DocCheck on all my subprojects using
multiproject:doccheck, but I can't seem to get it to recognize my source
files in each subproject. Anyone help?
I'm using doccheck with multiproject fine.
It might have something to do with this:
http://maven.apache.org/maven-1.x/plugins/multiproject/faq.html#resources-not-included-in-artifacts
You might need to add ${basedir} to your project.xml sourceDirectory
entry like this:
${basedir}/src/main/java
Best regards,
-- Shinobu
--
Shinobu Kawai <[EMAIL PROTECTED]>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven 1 multiproject build
Hi I have a continuum build that is executing multiproject:install on a Maven 1 project. Continuum reports the builds to be successful even when they fail. Is this a known issue? Thanks Gabriel Communications on or through ioko's computer systems may be monitored or recorded to secure effective system operation and for other lawful purposes. Unless otherwise agreed expressly in writing, this communication is to be treated as confidential and the information in it may not be used or disclosed except for the purpose for which it has been sent. If you have reason to believe that you are not the intended recipient of this communication, please contact the sender immediately. No employee is authorised to conclude any binding agreement on behalf of ioko with another party by e-mail without prior express written confirmation. ioko365 Ltd. VAT reg 656 2443 31. Reg no 3048367. All rights reserved.
Re: [M2] Multiproject and ${user.dir} (was: [jira] Closed: (MNG-1570) Testing from a parent POM fails ...)
I'm having this problem as well... modules all build fine on their own, but I can't reference a module relative path properly when starting a reactor build from the parent. - Brill Pappin On 11/24/05, Brett Porter <[EMAIL PROTECTED]> wrote: On 11/23/05, Jörg Schaible <[EMAIL PROTECTED]> wrote: > > Maven 2.x is not currently > > forking, so relative paths are correctly relative to user.dir. > > Any plans for it? This seems quite essential. For our company this is a show-stopper and as David Jackman explained in his posting it is also essential if you have JNI bindings. I won't be able to convert the project for the swt component of pico/nano too. Someone took a stab at implementing it and then seems to have disappeared from the list, so we're hoping to pick it up soon. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 multiproject build question
Hello, I have project tree -core -addons -site1 -site1-i18n -site2 -site2-i18n -parent site1 and site2 requires both core and addons, site3 requires only core. Im writing plugin for customizing build of my projects - i need full rebuild for addons and core when im making "mvn package" for site1 or site2. Now im trying to use for this MavenEmbedder, but it is not good way. Could anyone advice me better solution? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2 multiproject build question
Hello, I have project tree -core -addons -site1 -site1-i18n -site2 -site2-i18n -site3 -site3-i18n -parent site1 and site2 requires both core and addons, site3 requires only core. i need to have possibility performing full build for any webapp, ie for example invoke build chain core->addons->site1-i18n->site1 also i need to rebuild all dependendencies from my project tree every time im building webapp. is it possible with only maven configuration or it requires making my own plugin for invoking this chain? another question - if i dont have "core" in local repository how i can tell maven to build it? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject: Merge Javadoc's into parents site?
Maria Odea Ching wrote: > The aggregate parameter specifies that all the generated javadocs of the > different modules will Thanks for the hint, Odea. Indeed, that seems to work. For the record, I had to force using the latest version of the javadoc plugin by adding a 2.0. Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject: Merge Javadoc's into parents site?
Hi Jochen, You can integrate javadoc into the site by putting this in your parent pom: ... maven-javadoc-plugin true The aggregate parameter specifies that all the generated javadocs of the different modules will be compiled into one javadoc report. Thanks, Odea Jochen Wiedmann wrote: Hi, I have a project (Apache XML-RPC) with three subprojects (common, client, server), each of which are building a jar file. The site is created by the parent project. Now I'd like to integrate the Javadoc's into the site. But how to do that? Regards, Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiproject: Merge Javadoc's into parents site?
Hi, I have a project (Apache XML-RPC) with three subprojects (common, client, server), each of which are building a jar file. The site is created by the parent project. Now I'd like to integrate the Javadoc's into the site. But how to do that? Regards, Jochen -- Whenever you find yourself on the side of the majority, it is time to pause and reflect. (Mark Twain) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
