On 11 May 2012 22:47, Anders Hammar wrote:
> This is not uncommon for large multi-module builds. You need to
> increase the memory available for Maven, such as the heap depending on
> the error you're getting.
> Do this by setting the MAVEN_OPTS env variable.
I know, it is already getting 2GB. I
This is not uncommon for large multi-module builds. You need to
increase the memory available for Maven, such as the heap depending on
the error you're getting.
Do this by setting the MAVEN_OPTS env variable.
My experience is that this is mainly due to the plugins being used in
the build, not Mave
Hi all,
I have noticed that in a fairly large reactor build the build dies
close to the end (about 10 modules to go out of around 90). It simply
runs out of memory. Restarting it with -rf allows it to finish without
issues. There is a limit to how much memory I can give Maven... :-)
So apparently
Just make sure you done deploy this "extra" aggregating pom, or make
sure you use a different artifactId. I strongly suggest not deploying
it as it would be your private special build purposes agg pom. Thus,
don't make it a parent pom.
/Anders
On Fri, May 11, 2012 at 10:30 PM, KARR, DAVID wrote:
> -Original Message-
> From: GALLAGHER, RON
> Sent: Friday, May 11, 2012 11:58 AM
> To: Maven Users List
> Subject: RE: Some questions about customizing the build on the Maven
> command line
>
> David,
>
> Why not just create a new pom file at level1, rather than modifying an
> existing o
David,
Why not just create a new pom file at level1, rather than modifying an existing
one?
Something like this in pom-david-karr.xml:
level2
level2/level3
Then, you just use the -f command line argument to get Maven to use a different
POM file.
mvn -f pom-david-karr.xml
Hi,
The Maven team is pleased to announce the release of the Maven Remote
Resources Plugin, version 1.3
This plugin is used to retrieve JARs of resources from remote
repositories, process those resources, and incorporate them into JARs
you build with Maven. A very common use-case is the need to p
> -Original Message-
> From: Wayne Fay [mailto:wayne...@gmail.com]
> Sent: Friday, May 11, 2012 7:31 AM
> To: Maven Users List
> Subject: Re: Some questions about customizing the build on the Maven
> command line
>
> >> Why can't you simply make level2 a child (module) of level1, and the
>
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.3
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps: prepare
and perform.
http://maven.apache.org/plugins/maven-rel
>> Why can't you simply make level2 a child (module) of level1, and the
>> same for level3 under level2? Why are you making things harder than it
>> needs to be?
>
> Because I can't change the poms.
Then you probably can't make this work. This is a silly and arbitrary
restriction. How would you ma
10 matches
Mail list logo