Re: Building selected projects with nested aggregators

[spoots]

Bingo!

I can't believe I never tried that, but it works perfectly. Thank you :)



--
View this message in context: 
http://maven.40175.n5.nabble.com/Building-selected-projects-with-nested-aggregators-tp5753572p5753574.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: Building selected projects with nested aggregators

[Andreas Gudian]

Hi,

just use the directory notation. The following will build the module
in module-dir/sub-module-dir
and all the modules in the reactor that depend on it:

mvn test -pl module-dir/sub-module-dir -amd

Andreas

Am Freitag, 12. April 2013 schrieb spoots :

> Hi,
>
> I've got a project structure where I have an aggregator project and all of
> it's modules are also aggregator projects (i.e. projects that exist just to
> specify sub-modules). Picture something like what's shown in the "POM best
> practices" section of the Maven reference:
> 
>
> Now pretend that project "streaming-client" has a dependency on project
> "client-web". If I do a build of "big-system", Maven will put "client-web"
> ahead of "streaming-client" in the reactor order which is dandy - it seems
> to walk the whole project tree and resolve the dependencies just fine.
>
> But how can I specify, from the top level, to build "client-web" and all
> it's dependents if I change just that one project? Using the "-pl" option
> from within "big-system" seems to only recognise project names that are
> directly included in that reactor (e.g. "server-side" and "client-side").
> Is
> there some kind of qualifier that lets me specify a project which is nested
> within another aggregator project?
>
> Thanks,
> Keith
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Building-selected-projects-with-nested-aggregators-tp5753572.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
>
>

Building selected projects with nested aggregators

[spoots]

Hi,

I've got a project structure where I have an aggregator project and all of
it's modules are also aggregator projects (i.e. projects that exist just to
specify sub-modules). Picture something like what's shown in the "POM best
practices" section of the Maven reference:
 

Now pretend that project "streaming-client" has a dependency on project
"client-web". If I do a build of "big-system", Maven will put "client-web"
ahead of "streaming-client" in the reactor order which is dandy - it seems
to walk the whole project tree and resolve the dependencies just fine.

But how can I specify, from the top level, to build "client-web" and all
it's dependents if I change just that one project? Using the "-pl" option
from within "big-system" seems to only recognise project names that are
directly included in that reactor (e.g. "server-side" and "client-side"). Is
there some kind of qualifier that lets me specify a project which is nested
within another aggregator project?

Thanks,
Keith



--
View this message in context: 
http://maven.40175.n5.nabble.com/Building-selected-projects-with-nested-aggregators-tp5753572.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: [ANN] Maven Compiler Plugin 3.1 Released

[Wayne Fay]

> I'm not sure it could be a clue but it happens for some (I haven't
> verified all) WAR modules.

What code are you compiling in a WAR module? Best practice says to move the
Java code to a Jar module. Are you precompiling jsps with jspc or ...?

Is this a project you can share via Github? Or can you make a sample that
(consistently) exhibits the behavior, and share just that part?

Wayne

Re: What happened to Polyglot Maven?

[vra5107]

Jason 

I am trying to pitch maven to the folks who are still using Ant + Ivy and
have created a dependency mess. One of the points I want to mention is
polyglot because of fewer number of lines of code. Is your update from Aug
2012 still valid ? as in, polyglot not abandoned ?


Thanks
Venkat



--
View this message in context: 
http://maven.40175.n5.nabble.com/What-happened-to-Polyglot-Maven-tp5715529p5753558.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

[ANN] Maven surefire Plugin 2.14.1 Released

[Kristian Rosenvold]

The Maven team is pleased to announce the release of the Maven
Surefire Plugin, version 2.14.1

This version contains mostly minor bugfixes.

This is the last version that will include any java 1.3 & 1.4 support.
Future versions will be 1.5+ only.

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-surefire-plugin
  2.14.1


Release Notes - Maven Surefire - Version 2.14.1

** Bug
* [SUREFIRE-967] - ArrayIndexOutOfBounds in SmartStackTraceParser
* [SUREFIRE-970] - Elapsed time of skipped tests in surefire
report XML file shows huge number
* [SUREFIRE-971] - Configuration attributes groups/excludedGroups
don't work when running a single test.
* [SUREFIRE-972] - Bizarre NoClassDefFoundError in failsafe
* [SUREFIRE-975] - TEST-*.xml in system encoding with utf-8 header
* [SUREFIRE-979] - Wrong classloader used in SmartStackTraceParser
when test-class fails to instantiate
* [SUREFIRE-980] - Surefire NPEs if you don't spec any tests to
include/exclude
* [SUREFIRE-981] - Surefire hangs if forked test name ends with
carriage return


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Shared Utils 0.4 Released

[Kristian Rosenvold]

The Maven team is pleased to announce the release of
maven-shared-utils, version 0.4

This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.

It is not a 100% API compatible replacement though but a replacement
:
lots of methods got cleaned up, generics got added and we dropped a
lot of unused code. Although all
the classes are in different packages from plexus-utils, if the method
is present it will have the same
semantics, facilitating easy conversion.

http://maven.apache.org/shared/maven-shared-utils/

You should specify the version in your project's plugin configuration:


   org.apache.maven.shared
   maven-shared-utils0.4


Release Notes - Maven Shared Components - Version maven-shared-utils-0.4

** Bug
* [MSHARED-282] - StringIndexOutOfBoundsException in m-s-u
XMLEncode if carriage-return is the last character

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-license-plugin NPE

[Stephen Connolly]

On 11 April 2013 11:36, Olivier Lamy  wrote:

> This mojo is maintained here
> http://code.google.com/p/maven-license-plugin/
> So use this place for any questions.
>

While you are over there can you also point out that they are not supposed
to call themselves maven-___-plugin as that causes confusion on behalf of
users (and is not a naming format that we consider part of the allowed
usage) they should use a format that makes it clear that it is a plugin for
Apache Maven but by somebody other than the ASF, e.g. -maven-plugin
would be fine

See http://jira.codehaus.org/browse/MPLUGIN-185


> Maybe you can try this one too
> http://mojo.codehaus.org/license-maven-plugin/
>
> 2013/4/11 David Hoffer :
> > I have a multi-module build I'm running the license:format goal on.  It
> > works fine for several modules then fails with NPE on the
> deployment-parent
> > module which is a pom type module (we have several like that), any ideas
> > why it would fail on this one?
> >
> > I tried versions 1.9.0 and 1.10.b1 and get the same error.
> >
> > [ERROR] Failed to execute goal
> > com.mycila.maven-license-plugin:maven-license-plu
> > gin:1.10.b1:format (default-cli) on project deployment-parent: Execution
> > default
> > -cli of goal
> > com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format
> >  failed. NullPointerException -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> > goal c
> > om.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format
> > (default-cli)
> >  on project deployment-parent: Execution default-cli of goal
> > com.mycila.maven-li
> > cense-plugin:maven-license-plugin:1.10.b1:format failed.
> > at
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> > .java:225)
> > at
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> > .java:153)
> > at
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> > .java:145)
> > at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
> > ct(LifecycleModuleBuilder.java:84)
> > at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
> > ct(LifecycleModuleBuilder.java:59)
> > at
> > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
> > ild(LifecycleStarter.java:183)
> > at
> > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
> > eStarter.java:161)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > java:57)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> > sorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:601)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
> > cher.java:290)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
> > a:230)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
> > uncher.java:409)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
> > 352)
> > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> > default-c
> > li of goal
> > com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format f
> > ailed.
> > at
> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
> > BuildPluginManager.java:110)
> > at
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> > .java:209)
> > ... 19 more
> > Caused by: java.lang.NullPointerException
> > at
> > com.google.code.mojo.license.header.HeaderParser.hasHeader(HeaderPars
> > er.java:142)
> > at
> > com.google.code.mojo.license.header.HeaderParser.(HeaderParser.
> > java:63)
> > at
> > com.google.code.mojo.license.document.Document.parseHeader(Document.j
> > ava:125)
> > at
> > com.google.code.mojo.license.LicenseFormatMojo$1.onHeaderNotFound(Lic
> > enseFormatMojo.java:55)
> > at
> > com.google.code.mojo.license.AbstractLicenseMojo$1.run(AbstractLicens
> > eMojo.java:265)
> > at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47
> > 1)
> > at
> > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> > at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47
> > 1)
> >

Re: maven-license-plugin NPE

[Olivier Lamy]

This mojo is maintained here http://code.google.com/p/maven-license-plugin/
So use this place for any questions.

Maybe you can try this one too http://mojo.codehaus.org/license-maven-plugin/

2013/4/11 David Hoffer :
> I have a multi-module build I'm running the license:format goal on.  It
> works fine for several modules then fails with NPE on the deployment-parent
> module which is a pom type module (we have several like that), any ideas
> why it would fail on this one?
>
> I tried versions 1.9.0 and 1.10.b1 and get the same error.
>
> [ERROR] Failed to execute goal
> com.mycila.maven-license-plugin:maven-license-plu
> gin:1.10.b1:format (default-cli) on project deployment-parent: Execution
> default
> -cli of goal
> com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format
>  failed. NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal c
> om.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format
> (default-cli)
>  on project deployment-parent: Execution default-cli of goal
> com.mycila.maven-li
> cense-plugin:maven-license-plugin:1.10.b1:format failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> .java:225)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> .java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> .java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
> ct(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
> ct(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
> ild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
> eStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
> cher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
> a:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
> uncher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
> 352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-c
> li of goal
> com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format f
> ailed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
> BuildPluginManager.java:110)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> .java:209)
> ... 19 more
> Caused by: java.lang.NullPointerException
> at
> com.google.code.mojo.license.header.HeaderParser.hasHeader(HeaderPars
> er.java:142)
> at
> com.google.code.mojo.license.header.HeaderParser.(HeaderParser.
> java:63)
> at
> com.google.code.mojo.license.document.Document.parseHeader(Document.j
> ava:125)
> at
> com.google.code.mojo.license.LicenseFormatMojo$1.onHeaderNotFound(Lic
> enseFormatMojo.java:55)
> at
> com.google.code.mojo.license.AbstractLicenseMojo$1.run(AbstractLicens
> eMojo.java:265)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47
> 1)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47
> 1)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
> java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:615)
> at java.lang.Thread.run(Thread.java:722)



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [ANN] Maven Compiler Plugin 3.1 Released

[Stanimir Stamenkov]

Mon, 8 Apr 2013 20:15:15 +1000, /Olivier Lamy/:


Release Notes - Apache Maven 2.x Compiler Plugin - Version 3.1

** Bug
 * [MCOMPILER-187] - incremental stuff detect changes even if
nothing has changed means too much compilation


I'm not sure it is the same, but it seems I'm still observing 
instance of this.  I perform `mvn clean compile`, then immediately 
`mvn compile` after it and I still see:


[INFO] Changes detected - recompiling the module!

It doesn't appear for all modules I've tried with, though.  I'm not 
sure it could be a clue but it happens for some (I haven't verified 
all) WAR modules.


--
Stanimir

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org