RE: Multiproject build that needs to build one project only if on a particular os?

[KARR, DAVID]

> -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?

[Karl Heinz Marbaise]

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?

[Paul Benedict]

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?

[Karl Heinz Marbaise]

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?

[Bernd Eckenfels]

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?

[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: Why does my multiproject build revert to taking SNAPSHOT versions of dependencies when I want a specified version?

[Christopher Patti]

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?

[Christopher Patti]

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?

[Wayne Fay]

> 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?

[Christopher Patti]

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

Re: Multiproject build fails

[Greg Davidson]

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

[Arnaud HERITIER]

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

[Todd Nine]

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

[Todd Nine]

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: [m2] How to bypass unit testing durng multiproject build with Maven 2

[Thorsten Heit]

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

[mavenstart]

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

[Thorsten Heit]

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

[mavenstart]

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]

Maven 1 multiproject build

[Gabriel Page]

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 build question

[Roman Krutyakov]

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

[Roman Krutyakov]

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: Inherit version from parent project in multiproject build?

[Eric Redmond]

Children do inherit version from their parents (if the children do not set
the version element themselves).

Understand that there is a difference between a POM that aggregates other
projects, and a parent project. They are not necessarily related. A parent
POM is one that is explicitly pointed to by its children. They inherit their
parent's values. An aggregator (multimodule) POM, on the other hand, enacts
a common build over a set of modules (projects). But those modules do not
inherit from that POM (necessarily).

You'll still have the same issue with children inheriting from a version of
a parent POM. In order for a child to inherit from a different parent
version, then the child will have to explicitly point to the new parent
version, thus, negating your intent.

I remember talk of a plugin that could set versions by build, but I don't
know what came of it.

Eric

On 4/17/06, Sean McNamara <[EMAIL PROTECTED]> wrote:
>
>
> I've been trying to find an answer to this without much luck, but can't
> believe nobody else has tried to do this.  Apologies in advance if the
> answer is readily available... If so, my keywords must suck.
>
> I've got a M2 multproject setup that builds several artifacts.
>
> + parent
> -+ pom.xml
> -+ child1
> -+ child2
>
> We want to assign the same version to each artifact in the multiproject
> build, but it doesn't look like the version is actually an inheritable
> field.  This means each time we want to build a new version, we need to
> modify the POM for each child project, regardless of whether or not it
> changed.
>
> Is there some easy way to do this under Maven2?
>
> Thanks!
>
>
> *
>
> Note:  The information contained in this message and any attachment to it
> is privileged, confidential and protected from disclosure.  If the reader of
> this message is not the intended recipient, or an employee or agent
> responsible for delivering this message to the intended recipient, you are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited.  If you have received this
> communication in error, please notify the sender immediately by replying to
> the message, and please delete it  from your system. Thank you.  NYSE Group.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Inherit version from parent project in multiproject build?

[Sean McNamara]

I've been trying to find an answer to this without much luck, but can't
believe nobody else has tried to do this.  Apologies in advance if the
answer is readily available... If so, my keywords must suck.

I've got a M2 multproject setup that builds several artifacts.

+ parent
-+ pom.xml
-+ child1
-+ child2

We want to assign the same version to each artifact in the multiproject
build, but it doesn't look like the version is actually an inheritable
field.  This means each time we want to build a new version, we need to
modify the POM for each child project, regardless of whether or not it
changed.

Is there some easy way to do this under Maven2?

Thanks!

*

Note:  The information contained in this message and any attachment to it is 
privileged, confidential and protected from disclosure.  If the reader of this 
message is not the intended recipient, or an employee or agent responsible for 
delivering this message to the intended recipient, you are hereby notified that 
any dissemination, distribution or copying of this communication is strictly 
prohibited.  If you have received this communication in error, please notify 
the sender immediately by replying to the message, and please delete it  from 
your system. Thank you.  NYSE Group.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Inherit version from parent project in multiproject build?

[Ray Tsang]

'version' did inherit for me in the beginning until i used release
plugin.  using `mvn release:prepare` overwrote the original pom.xml
for both parent and chilren, and added in the version field to each. 
can this be avoided?

ray,

On 4/18/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On 4/17/06, Sean McNamara <[EMAIL PROTECTED]> wrote:
>
> > We want to assign the same version to each artifact in
> > the multiproject build, but it doesn't look like the
> > version is actually an inheritable field.
>
> Unless I misunderstand what you want to do, it's working fine for the
> Struts build... the only place the  is specified is in the
> struts-action-parent pom, and the rest inherit it.
>
> The parent pom with 
>http://svn.apache.org/repos/asf/struts/action/trunk/pom.xml
>
> And one of the child modules, without:
>http://svn.apache.org/repos/asf/struts/action/trunk/core/pom.xml
>
> (You still end up writing the version number everywhere, though, in
> the  tag.)
>
> If you still need help, post some snippets from your poms, or
> construct a simple example project that demonstrates the problem.
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Inherit version from parent project in multiproject build?

[Wendy Smoak]

On 4/17/06, Sean McNamara <[EMAIL PROTECTED]> wrote:

> We want to assign the same version to each artifact in
> the multiproject build, but it doesn't look like the
> version is actually an inheritable field.

Unless I misunderstand what you want to do, it's working fine for the
Struts build... the only place the  is specified is in the
struts-action-parent pom, and the rest inherit it.

The parent pom with 
   http://svn.apache.org/repos/asf/struts/action/trunk/pom.xml

And one of the child modules, without:
   http://svn.apache.org/repos/asf/struts/action/trunk/core/pom.xml

(You still end up writing the version number everywhere, though, in
the  tag.)

If you still need help, post some snippets from your poms, or
construct a simple example project that demonstrates the problem.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Inherit version from parent project in multiproject build?

[Sean McNamara]

I've been trying to find an answer to this without
much luck, but can't believe nobody else has tried to
do this.  Apologies in advance if the answer is
readily available... If so, my keywords must suck.

I've got a M2 multproject setup that builds several
artifacts.

+ parent
-+ pom.xml
-+ child1
-+ child2

We want to assign the same version to each artifact in
the multiproject build, but it doesn't look like the
version is actually an inheritable field.  This means
each time we want to build a new version, we need to
modify the POM for each child project, regardless of
whether or not it changed.

Is there some easy way to do this under Maven2?

Thanks!

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

M1 multiproject Build Order still wrong

[Osborne, Matthew]

Okay I got my previous issue fixed only to run straight into another.
Not sure exactly how the multiproject plugin determines the proper build
order for a given project, but for mine it is not being determined
correctly (It is trying to build a module first that has a dependency on
another that is not yet built, thus hosing the whole process).  Is there
a way to manually override the auto-generated project build order, as I
can't find anything in documentation on this and a google search turned
up nothing also.  Thanks


Matt Osborne


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m1.1-b-2] how can I initialize a variable/prop just once and share with subprojects in multiproject build?

[Dion Gillard]

Yep, that works well. Since you want it to be available to all
projects, the system properties are one way to do it.

On 1/17/06, Max Cooper <[EMAIL PROTECTED]> wrote:
> Well, I am not sure this is a good answer, but I found something that
> works -- save it in the systemScope:
>
> 
>value="${systemScope.getProperty('my.svnRevision')}"/>
>   
> Getting revision...
> 
> 
> 
> ${systemScope.setProperty('my.svnRevision', svnRevision)}
>   
> 
>
> Comments are still welcome. :-)
>
> -Max
>
> On Mon, 2006-01-16 at 15:14 -0800, Max Cooper wrote:
> > I want to initialize a variable or property just once at the beginning
> > of a multiproject build and then be able to access that value in any of
> > the subprojects. Ideally, running a subproject build on it's own would
> > also initialize the value.
> >
> > For instance, so far I have something like this in my shared,
> > common/maven.xml file:
> >
> > 
> >   
> > Getting revision...
> > 
> > 
> >   
> > 
> >
> > This doesn't work -- "Getting revision..." is echoed for each subproject
> > build, which means that svnRevision isn't set in the context of each of
> > the individual builds. I don't actually think this code should work (it
> > makes sense that each subproject *would* have it's own independent
> > instance of the svnRevision variable) -- I am just looking for tips
> > about what I might change to get it to work. I just don't know where I
> > can "stash" the value so that it will be available in the subproject
> > builds.
> >
> > Thanks,
> > -Max
> >
> >
> > -
> > 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]
>
>


--
http://www.multitask.com.au/people/dion/
"In order to succeed, your desire for success should be greater than
your fear of failure." - Bill Cosby

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m1.1-b-2] how can I initialize a variable/prop just once and share with subprojects in multiproject build?

[Max Cooper]

Well, I am not sure this is a good answer, but I found something that
works -- save it in the systemScope:


  
  
Getting revision...



${systemScope.setProperty('my.svnRevision', svnRevision)} 
  


Comments are still welcome. :-)

-Max

On Mon, 2006-01-16 at 15:14 -0800, Max Cooper wrote:
> I want to initialize a variable or property just once at the beginning
> of a multiproject build and then be able to access that value in any of
> the subprojects. Ideally, running a subproject build on it's own would
> also initialize the value.
> 
> For instance, so far I have something like this in my shared,
> common/maven.xml file:
> 
> 
>   
> Getting revision...
> 
> 
>   
> 
> 
> This doesn't work -- "Getting revision..." is echoed for each subproject
> build, which means that svnRevision isn't set in the context of each of
> the individual builds. I don't actually think this code should work (it
> makes sense that each subproject *would* have it's own independent
> instance of the svnRevision variable) -- I am just looking for tips
> about what I might change to get it to work. I just don't know where I
> can "stash" the value so that it will be available in the subproject
> builds.
> 
> Thanks,
> -Max
> 
> 
> -
> 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]

[m1.1-b-2] how can I initialize a variable/prop just once and share with subprojects in multiproject build?

[Max Cooper]

I want to initialize a variable or property just once at the beginning
of a multiproject build and then be able to access that value in any of
the subprojects. Ideally, running a subproject build on it's own would
also initialize the value.

For instance, so far I have something like this in my shared,
common/maven.xml file:


  
Getting revision...


  


This doesn't work -- "Getting revision..." is echoed for each subproject
build, which means that svnRevision isn't set in the context of each of
the individual builds. I don't actually think this code should work (it
makes sense that each subproject *would* have it's own independent
instance of the svnRevision variable) -- I am just looking for tips
about what I might change to get it to work. I just don't know where I
can "stash" the value so that it will be available in the subproject
builds.

Thanks,
-Max


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Run script/goal whether multiproject build fails or not

[Patrick Villacorta]

Hi,

Is there a way to run a goal/script in Maven 1 that will run at the end 
of a multiproject build, whether the build is succussful or not? (ex. 
build fails in 3rd module of a 5 module project) I'm trying to make a 
goal that will write a report everytime a build is attempted.


Thanks,
Patrick

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiproject build

[stéphane bouchet]

Hi,
i am in the same configuration, but even if i have all my projects depending  on 
my utility project, it is not built in the first place ?


So when i do a "multiproject:install", my utility project is not on the top list 
and the build fails


Using maven 1.0.2 and multiproject 1.4.1.

Thanks



Per Abich a écrit :

Just put a dependency in your project.xml so that all project depend
on your utility project. That should do the trick. Currently, there is
no other way of orderig the build process.

Per

2005/8/3, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:


Hi,

 I have a Maven multiproject set up. One of my project is a utility
kind of project which is used by my other modules/projects.

During the build, can i set up a order in which the projects will be built
(or) can i set dependency between my projects so that my utility project
will get built first ?

newbie
gurubaran.



*
This message and any attachments (the "message") are confidential
and intended solely for the addressee(s). Any unauthorised use or
dissemination is prohibited.E-mails are susceptible to alteration.
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates
shall be liable for the message if altered, changed or falsified.
*


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiproject build

[Per Abich]

Just put a dependency in your project.xml so that all project depend
on your utility project. That should do the trick. Currently, there is
no other way of orderig the build process.

Per

2005/8/3, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Hi,
> 
>   I have a Maven multiproject set up. One of my project is a utility
> kind of project which is used by my other modules/projects.
> 
> During the build, can i set up a order in which the projects will be built
> (or) can i set dependency between my projects so that my utility project
> will get built first ?
> 
> newbie
> gurubaran.
> 
> 
> 
> *
> This message and any attachments (the "message") are confidential
> and intended solely for the addressee(s). Any unauthorised use or
> dissemination is prohibited.E-mails are susceptible to alteration.
> Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates
> shall be liable for the message if altered, changed or falsified.
> *
> 
> 
> -
> 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]

Multiproject build

[gurubaran . kanagaraj]

Hi,

  I have a Maven multiproject set up. One of my project is a utility
kind of project which is used by my other modules/projects.

During the build, can i set up a order in which the projects will be built
(or) can i set dependency between my projects so that my utility project
will get built first ?

newbie
gurubaran.



*
This message and any attachments (the "message") are confidential
and intended solely for the addressee(s). Any unauthorised use or
dissemination is prohibited.E-mails are susceptible to alteration.
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates
shall be liable for the message if altered, changed or falsified.
*


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: a practical multiproject build

[Durham David R Jr Contr 805 CSPTS/SCE]

> Remember that maven always uses the version in the local repository.
> So if module B depends on 1.0-SNAPSHOT of module A, and you change
> something to module A, then you need to call jar:install on module A.
> Otherwise module B will not see the changes.

Yeah, that's what multiproject does: call the artifact:install in order
of dependencies.  Here's the thing, if you're working online, it will
always try to get the module A SNAPSHOT dependency that module B needs
from the remote repository first, then fail over to the local repository
because it's a SNAPSHOT.  See what I mean?


- Dave

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: a practical multiproject build

[Wim Deblauwe]

You can have SNAPSHOT in your , we use it like that.

with 1-0-SNAPSHOT:
jar:install -> puts myjar-1.0-SNAPSHOT.jar in the local repository
jar:install-snapshot -> puts myjar-SNAPSHOT.jar in the local repository

with 1.0:
jar:install -> puts myjar-1.0.jar in the local repository
jar:install-snapshot -> puts myjar-SNAPSHOT.jar in the local repository

If your project depends on a version that has SNAPSHOT in it (so
either 1.0-SNAPSHOT and SNAPSHOT work), it will be checked for every
build if it has not changed in the remote or local repository.

Remember that maven always uses the version in the local repository.
So if module B depends on 1.0-SNAPSHOT of module A, and you change
something to module A, then you need to call jar:install on module A.
Otherwise module B will not see the changes.

hth,

Wim




On 4/14/05, Durham David R Jr Contr 805 CSPTS/SCE
<[EMAIL PROTECTED]> wrote:
> > SNAPSHOT makes a lot of sense in a multiproject context.
> >
> > From what I understand, you should never set the version to SNAPSHOT
> > in your  tag. you should rather use something along the
> > line of
> > artifact:install-snapshot (local repo)
> > artifact:deploy-snapshot (global repo)
> > which will tag your current "release" as SNAPSHOT.
> 
> Yeah, I thought the same thing about install-snapshot, but according to:
> 
> http://maven.apache.org/using/bestpractices.html#Project_Development_Cyc
> le
> 
> You should also change the currentVersion to nextVersion-SNAPSHOT.
> 
> > your SNAPSHOTdependencies will then be resolved.
> 
> Actually, SNAPSHOT dependencies do get resolved, however, maven will
> first try to get the SNAPSHOT from the repository (makes sense outside
> of the multiproject context), even though it exists locally.  Would be
> nice if it grabbed locally first since it's a multiproject.
> 
> - Dave
> 
> -
> 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: a practical multiproject build

[Durham David R Jr Contr 805 CSPTS/SCE]

> SNAPSHOT makes a lot of sense in a multiproject context.
> 
> From what I understand, you should never set the version to SNAPSHOT
> in your  tag. you should rather use something along the 
> line of
> artifact:install-snapshot (local repo)
> artifact:deploy-snapshot (global repo)
> which will tag your current "release" as SNAPSHOT.

Yeah, I thought the same thing about install-snapshot, but according to:

http://maven.apache.org/using/bestpractices.html#Project_Development_Cyc
le

You should also change the currentVersion to nextVersion-SNAPSHOT.

> your SNAPSHOTdependencies will then be resolved.

Actually, SNAPSHOT dependencies do get resolved, however, maven will
first try to get the SNAPSHOT from the repository (makes sense outside
of the multiproject context), even though it exists locally.  Would be
nice if it grabbed locally first since it's a multiproject.


- Dave

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: a practical multiproject build

[Patrick Roumanoff]

> Right, part of my problem is that I don't understand exactly how the
> SNAPSHOT stuff works.  Perhaps SNAPSHOTs don't make as much sense in a
> "multiproject" context at least as far the modules are concerned.  I
> replaced SNAPSHOT with an actual version number within the different
> modules' project.xml files and the build works smoothly now.

Hi,

SNAPSHOT makes a lot of sense in a multiproject context.

>From what I understand, you should never set the version to SNAPSHOT
in your  tag. you should rather use something along the line
of
artifact:install-snapshot (local repo)
artifact:deploy-snapshot (global repo)
which will tag your current "release" as SNAPSHOT.

your SNAPSHOTdependencies will then be resolved.

cheers,

Patrick


NOTICE
This e-mail and any attachments are confidential and may contain copyright 
material of Macquarie Bank or third parties. If you are not the intended 
recipient of this email you should not read, print, re-transmit, store or act 
in reliance on this e-mail or any attachments, and should destroy all copies of 
them. Macquarie Bank does not guarantee the integrity of any emails or any 
attached files. The views or opinions expressed are the author's own and may 
not reflect the views or opinions of Macquarie Bank.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: a practical multiproject build

[Durham David R Jr Contr 805 CSPTS/SCE]

> You can filter the subprojects on which you want to call a goal by
> adding the following on the root maven.xml :
> 
> 
>  basedir="${basedir}"
> includes="*/project.xml"
> postProcessing="false"
> goals="myGoal"
> ignoreFailures="false" />
> 

Yeah, I can do this by manipulating the maven.multiproject.excludes and
maven.multiproject.includes properties.

> In your case the subprojects should have the same version number. So 
> I think that you can set the version (SNAPSHOT) on the root POM
> (project.xml) and remove it from subprojects. I hope it will 
> resolve your problem...

Right, part of my problem is that I don't understand exactly how the
SNAPSHOT stuff works.  Perhaps SNAPSHOTs don't make as much sense in a
"multiproject" context at least as far the modules are concerned.  I
replaced SNAPSHOT with an actual version number within the different
modules' project.xml files and the build works smoothly now.

Thanks,

Dave

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: a practical multiproject build

[Simon BRANDHOF]

Hello,

You can filter the subprojects on which you want to call a goal by
adding the following on the root maven.xml :


 
 

For your example, you should have :


 
 

In your case the subprojects should have the same version number. So I
think that you can set the version (SNAPSHOT) on the root POM
(project.xml) and remove it from subprojects. I hope it will resolve
your problem...

Simon

For the problem
On Apr 11, 2005 12:10 PM, Bahaa Nasrallah <[EMAIL PROTECTED]> wrote:
> I have exactly the smae problem, can anybody who knows how to solve
> this problem reply?
> 
> thanks,
> Bahaa
> 
> On Apr 8, 2005 8:17 PM, Durham David R Jr Contr 805 CSPTS/SCE
> <[EMAIL PROTECTED]> wrote:
> > I've been working with multiproject for a couple of days, so while I'm
> > not exactly an expert, I feel reasonably confident with the following
> > questions.
> >
> > Basically, I'd like to end up with 1 step to deploying only changes to a
> > web application.  Here's my directory structure:
> >
> > /project
> >/application
> >project.xml
> >...
> >/webClient
> >project.xml
> >...
> >project.xml
> >  ...
> >
> > As I understand it, I need to run multiproject:something from the
> > /project directory, to "build" the multiproject.  Then, I'd like to run
> > jboss:deploy-exploded-warfile from the /webClient directory.  How can I
> > bundle all of this into one goal within /project/maven.xml?  Something
> > like:
> >
> > The other thing I'm wondering is how manage the dependencies as
> > SNAPSHOTs.  For instance, since /webClient depends on /application, I'm
> > guessing that I should have something like this in
> > /webClient/project.xml:
> >
> >
> >project
> >application
> >SNAPSHOT
> >jar
> >
> >true
> >
> >
> >
> > And in /application/project.xml:
> >
> >SNAPSHOT
> >
> > Additionally, /webClient/project.xml has:
> >
> >SNAPSHOT
> >
> > Then, when I cut a release, I would replace SNAPSHOT with whatever
> > version I'm releasing.
> >
> > Since I'll be actively developing both modules at once, they should be
> > SNAPSHOTs right?  Currently, I'm having difficulty getting multiproject
> > to handle SNAPSHOT dependencies.  It always tries to get the dependency
> > from the remote repository despite the fact that the project SNAPSHOT is
> > part of the multiproject.
> >
> > Does this make sense?
> >
> > Thanks,
> >
> > Dave
> >
> > -
> > 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]
> 
> 


-- 
Simon BRANDHOF
Hortis - La rencontre de l'Agilité et de l'Open-source
www.xp-suisse.org
www.hortis.ch

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: a practical multiproject build

[Bahaa Nasrallah]

I have exactly the smae problem, can anybody who knows how to solve
this problem reply?

thanks,
Bahaa

On Apr 8, 2005 8:17 PM, Durham David R Jr Contr 805 CSPTS/SCE
<[EMAIL PROTECTED]> wrote:
> I've been working with multiproject for a couple of days, so while I'm
> not exactly an expert, I feel reasonably confident with the following
> questions.
> 
> Basically, I'd like to end up with 1 step to deploying only changes to a
> web application.  Here's my directory structure:
> 
> /project
>/application
>project.xml
>...
>/webClient
>project.xml
>...
>project.xml
>  ...
> 
> As I understand it, I need to run multiproject:something from the
> /project directory, to "build" the multiproject.  Then, I'd like to run
> jboss:deploy-exploded-warfile from the /webClient directory.  How can I
> bundle all of this into one goal within /project/maven.xml?  Something
> like:
> 
> The other thing I'm wondering is how manage the dependencies as
> SNAPSHOTs.  For instance, since /webClient depends on /application, I'm
> guessing that I should have something like this in
> /webClient/project.xml:
> 
>
>project
>application
>SNAPSHOT
>jar
>
>true
>
>
> 
> And in /application/project.xml:
> 
>SNAPSHOT
> 
> Additionally, /webClient/project.xml has:
> 
>SNAPSHOT
> 
> Then, when I cut a release, I would replace SNAPSHOT with whatever
> version I'm releasing.
> 
> Since I'll be actively developing both modules at once, they should be
> SNAPSHOTs right?  Currently, I'm having difficulty getting multiproject
> to handle SNAPSHOT dependencies.  It always tries to get the dependency
> from the remote repository despite the fact that the project SNAPSHOT is
> part of the multiproject.
> 
> Does this make sense?
> 
> Thanks,
> 
> Dave
> 
> -
> 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]

a practical multiproject build

[Durham David R Jr Contr 805 CSPTS/SCE]

I've been working with multiproject for a couple of days, so while I'm
not exactly an expert, I feel reasonably confident with the following
questions.

Basically, I'd like to end up with 1 step to deploying only changes to a
web application.  Here's my directory structure:

/project
/application
project.xml
...
/webClient
project.xml
...
project.xml
  ...


As I understand it, I need to run multiproject:something from the
/project directory, to "build" the multiproject.  Then, I'd like to run
jboss:deploy-exploded-warfile from the /webClient directory.  How can I
bundle all of this into one goal within /project/maven.xml?  Something
like:

The other thing I'm wondering is how manage the dependencies as
SNAPSHOTs.  For instance, since /webClient depends on /application, I'm
guessing that I should have something like this in
/webClient/project.xml:


project
application
SNAPSHOT
jar

true





And in /application/project.xml:

SNAPSHOT


Additionally, /webClient/project.xml has:

SNAPSHOT

Then, when I cut a release, I would replace SNAPSHOT with whatever
version I'm releasing.

Since I'll be actively developing both modules at once, they should be
SNAPSHOTs right?  Currently, I'm having difficulty getting multiproject
to handle SNAPSHOT dependencies.  It always tries to get the dependency
from the remote repository despite the fact that the project SNAPSHOT is
part of the multiproject.

Does this make sense?


Thanks,


Dave








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Multiproject build failure

[Carlos Sanchez]

Hi,

Look for a incorrect dependency. Try moving away project folders until it
works.

Regards

Carlos Sanchez
A Coruña, Spain

Oness Project
http://oness.sourceforge.net
 

> -Original Message-
> From: STRAYER, JON (SBCSI) [mailto:[EMAIL PROTECTED] 
> Sent: Friday, July 02, 2004 3:56 PM
> To: 'Maven Users List'
> Subject: Multiproject build failure
> 
> I'm in the process of splitting a project up into several 
> subprojects.  I've been running the multiproject build for 
> weeks without problems.  I just changed the subprojects so 
> they extend the main project.  Each subproject builds fine, 
> but now when I run multiproject I get this error message:
> 
> multiproject:projects-init:
> [echo] Gathering project list
> Starting the reactor...
> 
> BUILD FAILED
> File..
> /home/wfausers/wfaoper/.maven/cache/maven-multiproject-plugin-
> 1.3.1/plugin.j
> elly
> Element... maven:reactor
> Line.. 63
> Column 9
> A cycle has been detected from the initial goal 
> [wfa-billing:core] Total time: 21 seconds Finished at: Fri 
> Jul 02 08:11:35 CDT 2004
> 
> How can I go about finding the cycle it's complaining about?
> 
> -
> 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 build failure

[Brett Porter]

if maven -X doesn't show enough debugging info, you might just need to
trace back. It's usually easy to find - a pregoal/prereq on a goal
that does the same on the original.

On Fri, 2 Jul 2004 09:56:01 -0400 , STRAYER, JON (SBCSI) <[EMAIL PROTECTED]> wrote:
> I'm in the process of splitting a project up into several subprojects.  I've
> been running the multiproject build for weeks without problems.  I just
> changed the subprojects so they extend the main project.  Each subproject
> builds fine, but now when I run multiproject I get this error message:
> 
> multiproject:projects-init:
> [echo] Gathering project list
> Starting the reactor...
> 
> BUILD FAILED
> File..
> /home/wfausers/wfaoper/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.j
> elly
> Element... maven:reactor
> Line.. 63
> Column 9
> A cycle has been detected from the initial goal [wfa-billing:core]
> Total time: 21 seconds
> Finished at: Fri Jul 02 08:11:35 CDT 2004
> 
> How can I go about finding the cycle it's complaining about?
> 
> -
> 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]

Multiproject build failure

[STRAYER, JON (SBCSI)]

I'm in the process of splitting a project up into several subprojects.  I've
been running the multiproject build for weeks without problems.  I just
changed the subprojects so they extend the main project.  Each subproject
builds fine, but now when I run multiproject I get this error message:

multiproject:projects-init:
[echo] Gathering project list
Starting the reactor...

BUILD FAILED
File..
/home/wfausers/wfaoper/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.j
elly
Element... maven:reactor
Line.. 63
Column 9
A cycle has been detected from the initial goal [wfa-billing:core]
Total time: 21 seconds
Finished at: Fri Jul 02 08:11:35 CDT 2004

How can I go about finding the cycle it's complaining about?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Réf. : Plugins ready for use within the multiproject build.

[Niclas Hedhman]

On Tuesday 27 April 2004 20:02, [EMAIL PROTECTED] wrote:
> You meen that your plugin are subproject ?

Yes.

> Define in project.properties :
> maven.multiproject.type = plugin

I have done that. 

I have also tried to do;

  

  
  
in the plug-in's maven.xml.

I am coming to the conclusion that there is some kind of bug involved here, 
and that the Plugins can not be constructed in the same pass as they are 
used.

Niclas

-- 
+-//---+
|   http://www.bali.ac |
|  http://niclas.hedhman.org   |
+--//--+

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Réf. : Plugins ready for use within the multiproject build.

[Nicolas . CHALUMEAU]

You meen that your plugin are subproject ?

Define in project.properties :
maven.multiproject.type = plugin

Nicolas,





Niclas Hedhman <[EMAIL PROTECTED]>
27/04/2004 13:55
Veuillez répondre à "Maven Users List"

 
Pour :  "'Maven Users List'" <[EMAIL PROTECTED]>
cc : 
    Objet : Plugins ready for use within the multiproject build.



Hi,
What do I need to do to have my own Plugins created/installed, _during_ 
the 
same multiproject build where they are used??


Cheers
Niclas
-- 
+-//---+
|   http://www.bali.ac |
|  http://niclas.hedhman.org   |
+--//--+

-
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]

Plugins ready for use within the multiproject build.

[Niclas Hedhman]

Hi,
What do I need to do to have my own Plugins created/installed, _during_ the 
same multiproject build where they are used??


Cheers
Niclas
-- 
+-//---+
|   http://www.bali.ac |
|  http://niclas.hedhman.org   |
+--//--+

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: multiproject build with inherited POMs

[Jason Horne]

Thanks... I actually just pulled the latest version of Maven from CVS and all is now 
well.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 17, 2003 11:39 PM
To: Maven Users List
Subject: RE: multiproject build with inherited POMs


Jason,

if you're on beta 10, your  will need ${basedir}/../project.xml 
and not just ../project.xml


"Jason Horne" <[EMAIL PROTECTED]> wrote on 18/09/2003 04:01:13 AM:

> I think Maven switches it automatically.  The original line from the 
> sub-POM had a forward-slash, i.e.:
> 
>   ../project.xml
> 
> I changed it to a backslash, i.e.:
> 
>   ..\project.xml
> 
> In both cases, the error message had a backslash.
> 
> Jason

--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: multiproject build with inherited POMs

[dion]

Jason,

if you're on beta 10, your  will need ${basedir}/../project.xml 
and not just ../project.xml


"Jason Horne" <[EMAIL PROTECTED]> wrote on 18/09/2003 04:01:13 AM:

> I think Maven switches it automatically.  The original line from the
> sub-POM had a forward-slash, i.e.:
> 
>   ../project.xml
> 
> I changed it to a backslash, i.e.:
> 
>   ..\project.xml
> 
> In both cases, the error message had a backslash.
> 
> Jason

--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: multiproject build with inherited POMs

[Brett Porter]

What Maven version (beta-10 or CVS)? What Multiproject version (the one that
came with beta-10 or release 1.0 or the one in CVS)?

I'm guessing its beta-10, which means you need to add ${basedir}/ to the
front of the path. That's fixed in CVS.
As for the multiproject plugin - use version 1.0 released on the site, not
the one in beta-10.

- Brett

> -Original Message-
> From: Jason Horne [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, 18 September 2003 4:01 AM
> To: Maven Users List
> Subject: RE: multiproject build with inherited POMs
> 
> 
> I think Maven switches it automatically.  The original line 
> from the sub-POM had a forward-slash, i.e.:
> 
>   ../project.xml
> 
> I changed it to a backslash, i.e.:
> 
>   ..\project.xml
> 
> In both cases, the error message had a backslash.
> 
> Jason
> 
> -Original Message-
> From: khote [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, September 17, 2003 1:51 PM
> To: Maven Users List
> Subject: Re: multiproject build with inherited POMs
> 
> 
> it's worth a shot to turn the slash around.  ../project.xml 
> ${basedir}/../project.xml works on my windows machines.
> 
> - Original Message - 
> From: "Jason Horne" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, September 17, 2003 10:47 AM
> Subject: multiproject build with inherited POMs
> 
> 
> I'm getting a "can't find ..\project.xml" when trying to use 
> multiproject to build Maven plugins with POMs that inherit 
> from the root POM.  This is the structure reflected in the 
> plugins-build directory in the CVS tree.  As a sanity check, 
> I pulled src/plugins-build/* and src/plugins-build/war/* from 
> CVS and got the same error.  It occurs no matter which goal I 
> specify; I've tried "multiproject:site" and 
> "multiproject:artifact" among others.
> 
> Perhaps it isn't evaluating the ".." in relationship to the 
> working directory of the subproject, and thus isn't finding 
> the root POM?  Or, am I doing something wrong?
> 
> Here's the text of the error:
> 
> C:\Java\plugins2>maven multiproject:site
> 
> multiproject:site:
> multiproject:create-nav:
> [mkdir] Created dir: C:\Java\plugins2\target\generated-xdocs
> Starting the reactor...
> 
> BUILD FAILED
> File.. file:/C:/Documents and 
> Settings/jahorn/.maven/plugins/maven-multiproject-plugin-1.0-SNAPSHOT/
> Element... maven:reactor
> Line.. 84
> Column 7
> ..\project.xml (The system cannot find the file specified) 
> Total time:  3 seconds
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

RE: multiproject build with inherited POMs

[Jason Horne]

I think Maven switches it automatically.  The original line from the sub-POM had a 
forward-slash, i.e.:

  ../project.xml

I changed it to a backslash, i.e.:

  ..\project.xml

In both cases, the error message had a backslash.

Jason

-Original Message-
From: khote [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 17, 2003 1:51 PM
To: Maven Users List
Subject: Re: multiproject build with inherited POMs


it's worth a shot to turn the slash around.  ../project.xml ${basedir}/../project.xml 
works on my windows machines.

- Original Message - 
From: "Jason Horne" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 10:47 AM
Subject: multiproject build with inherited POMs


I'm getting a "can't find ..\project.xml" when trying to use multiproject to build 
Maven plugins with POMs that inherit from the root POM.  This is the structure 
reflected in the plugins-build directory in the CVS tree.  As a sanity check, I pulled 
src/plugins-build/* and src/plugins-build/war/* from CVS and got the same error.  It 
occurs no matter which goal I specify; I've tried "multiproject:site" and 
"multiproject:artifact" among others.

Perhaps it isn't evaluating the ".." in relationship to the working directory of the 
subproject, and thus isn't finding the root POM?  Or, am I doing something wrong?

Here's the text of the error:

C:\Java\plugins2>maven multiproject:site

multiproject:site:
multiproject:create-nav:
[mkdir] Created dir: C:\Java\plugins2\target\generated-xdocs
Starting the reactor...

BUILD FAILED
File.. file:/C:/Documents and 
Settings/jahorn/.maven/plugins/maven-multiproject-plugin-1.0-SNAPSHOT/
Element... maven:reactor
Line.. 84
Column 7
..\project.xml (The system cannot find the file specified) Total time:  3 seconds

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: multiproject build with inherited POMs

[khote]

it's worth a shot to turn the slash around.  ../project.xml
${basedir}/../project.xml works on my windows machines.

- Original Message - 
From: "Jason Horne" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 10:47 AM
Subject: multiproject build with inherited POMs


I'm getting a "can't find ..\project.xml" when trying to use multiproject to
build Maven plugins with POMs that inherit from the root POM.  This is the
structure reflected in the plugins-build directory in the CVS tree.  As a
sanity check, I pulled src/plugins-build/* and src/plugins-build/war/* from
CVS and got the same error.  It occurs no matter which goal I specify; I've
tried "multiproject:site" and "multiproject:artifact" among others.

Perhaps it isn't evaluating the ".." in relationship to the working
directory of the subproject, and thus isn't finding the root POM?  Or, am I
doing something wrong?

Here's the text of the error:

C:\Java\plugins2>maven multiproject:site

multiproject:site:
multiproject:create-nav:
[mkdir] Created dir: C:\Java\plugins2\target\generated-xdocs
Starting the reactor...

BUILD FAILED
File.. file:/C:/Documents and
Settings/jahorn/.maven/plugins/maven-multiproject-plugin-1.0-SNAPSHOT/
Element... maven:reactor
Line.. 84
Column 7
..\project.xml (The system cannot find the file specified)
Total time:  3 seconds

-- 
Jason Horne
Application Architecture Team/MIS/ISD
SAS Institute Inc.

-
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]

multiproject build with inherited POMs

[Jason Horne]

I'm getting a "can't find ..\project.xml" when trying to use multiproject to build 
Maven plugins with POMs that inherit from the root POM.  This is the structure 
reflected in the plugins-build directory in the CVS tree.  As a sanity check, I pulled 
src/plugins-build/* and src/plugins-build/war/* from CVS and got the same error.  It 
occurs no matter which goal I specify; I've tried "multiproject:site" and 
"multiproject:artifact" among others.

Perhaps it isn't evaluating the ".." in relationship to the working directory of the 
subproject, and thus isn't finding the root POM?  Or, am I doing something wrong?

Here's the text of the error:

C:\Java\plugins2>maven multiproject:site

multiproject:site:
multiproject:create-nav:
[mkdir] Created dir: C:\Java\plugins2\target\generated-xdocs
Starting the reactor...

BUILD FAILED
File.. file:/C:/Documents and 
Settings/jahorn/.maven/plugins/maven-multiproject-plugin-1.0-SNAPSHOT/
Element... maven:reactor
Line.. 84
Column 7
..\project.xml (The system cannot find the file specified)
Total time:  3 seconds

-- 
Jason Horne
Application Architecture Team/MIS/ISD
SAS Institute Inc. 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]