Re: Memory Leak?
You *will* want to make sure you're running the latest versions of most plugins, since a few leaks of this type have been fixed over the last year or so. surefire had one. Kristian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
JUnit test failures stop the build, but test errors do not
Hi, I've just joined a project which is using Maven for its builds. When running JUnit tests, the build fails if there is a build failure, but it does not fail if there is a test error. I'm new to maven so I'd like to know wether this is expected behaviour or not, and if there is a way to make it fail on test errors, too (I didn't find anything in the documentation). Thanks... Dirk -- Dirk Heinrichs | Tel: +49 (0)211 56623 316 Configuration Manager | Fax: +49 (0)211 56623 450 Capgemini Deutschland | Mail: dirk.heinri...@capgemini.com Wanheimerstraße 68 | Web: http://www.de.capgemini.com D-40468 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net Firma: Capgemini Deutschland GmbH Geschäftsführer: Dr. Michael Schulte (Sprecher) • Dr. Uwe Dumslaff • Burkhard Kehrbusch • Josef Ranner Aufsichtsratsvorsitzender: Antonio Schnieder Amtsgericht Berlin-Charlottenburg, HRB 98814 This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: JUnit test failures stop the build, but test errors do not
This is not the default behaviour, but can be set as a configuration option (not recommended under normal circumstances): http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore Are there any configuration settings for the surefire plugin in the project pom? Kind regards, Ben. On 14/05/12 16:55, Heinrichs, Dirk wrote: Hi, I've just joined a project which is using Maven for its builds. When running JUnit tests, the build fails if there is a build failure, but it does not fail if there is a test error. I'm new to maven so I'd like to know wether this is expected behaviour or not, and if there is a way to make it fail on test errors, too (I didn't find anything in the documentation). Thanks... Dirk -- Dirk Heinrichs | Tel: +49 (0)211 56623 316 Configuration Manager | Fax: +49 (0)211 56623 450 Capgemini Deutschland | Mail: dirk.heinri...@capgemini.com Wanheimerstraße 68 | Web: http://www.de.capgemini.com D-40468 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net Firma: Capgemini Deutschland GmbH Geschäftsführer: Dr. Michael Schulte (Sprecher) • Dr. Uwe Dumslaff • Burkhard Kehrbusch • Josef Ranner Aufsichtsratsvorsitzender: Antonio Schnieder Amtsgericht Berlin-Charlottenburg, HRB 98814 This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: JUnit test failures stop the build, but test errors do not
Firma: Capgemini Deutschland GmbH Geschäftsführer: Dr. Michael Schulte (Sprecher) • Dr. Uwe Dumslaff • Burkhard Kehrbusch • Josef Ranner Aufsichtsratsvorsitzender: Antonio Schnieder Amtsgericht Berlin-Charlottenburg, HRB 98814 This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. ---BeginMessage--- Am 14.05.2012 11:06, schrieb Ben Caradoc-Davies: This is not the default behaviour, but can be set as a configuration option (not recommended under normal circumstances): http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore There's no such setting in the projects POMs, so I tried running the build with an explicit -Dmaven.test.failure.ignore=false, but it didn't make a difference. Are there any configuration settings for the surefire plugin in the project pom? I didn't find any. Bye... Dirk -- ___ Dirk Heinrichs Capgemini | Düsseldorf Phone: +49 211 56623 316 - Mobile: +49 151 4025 2208 Fax: +49 211 56623 450 - e-mail: dirk.heinri...@capgemini.com www.de.capgemini.com Wanheimerstrasse 68, 40468 Düsseldorf, Germany People matter, results count. ___ signature.asc Description: OpenPGP digital signature ---End Message--- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: JUnit test failures stop the build, but test errors do not
You probably want to make sure you're running at least verision 2.11 of surefire. 2.12 is the latest. Kristian 2012/5/14 Heinrichs, Dirk dirk.heinri...@capgemini.com: Hi, I've just joined a project which is using Maven for its builds. When running JUnit tests, the build fails if there is a build failure, but it does not fail if there is a test error. I'm new to maven so I'd like to know wether this is expected behaviour or not, and if there is a way to make it fail on test errors, too (I didn't find anything in the documentation). Thanks... Dirk -- Dirk Heinrichs | Tel: +49 (0)211 56623 316 Configuration Manager | Fax: +49 (0)211 56623 450 Capgemini Deutschland | Mail: dirk.heinri...@capgemini.com Wanheimerstraße 68 | Web: http://www.de.capgemini.com D-40468 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net Firma: Capgemini Deutschland GmbH Geschäftsführer: Dr. Michael Schulte (Sprecher) • Dr. Uwe Dumslaff • Burkhard Kehrbusch • Josef Ranner Aufsichtsratsvorsitzender: Antonio Schnieder Amtsgericht Berlin-Charlottenburg, HRB 98814 This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: JUnit test failures stop the build, but test errors do not
Firma: Capgemini Deutschland GmbH Geschäftsführer: Dr. Michael Schulte (Sprecher) • Dr. Uwe Dumslaff • Burkhard Kehrbusch • Josef Ranner Aufsichtsratsvorsitzender: Antonio Schnieder Amtsgericht Berlin-Charlottenburg, HRB 98814 This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. ---BeginMessage--- Am 14.05.2012 11:51, schrieb Kristian Rosenvold: You probably want to make sure you're running at least verision 2.11 of surefire. 2.12 is the latest. It's 2.10 here. I guess updating surefire would make the very next build fail, right? Thanks a lot... Dirk -- ___ Dirk Heinrichs Capgemini | Düsseldorf Phone: +49 211 56623 316 - Mobile: +49 151 4025 2208 Fax: +49 211 56623 450 - e-mail: dirk.heinri...@capgemini.com www.de.capgemini.com Wanheimerstrasse 68, 40468 Düsseldorf, Germany People matter, results count. ___ signature.asc Description: OpenPGP digital signature ---End Message--- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Reg. accessing parent POM's property in child POM's version tag
I have a project structure like the below
School-parent
|
|
| services-parent
| | |
| | |-Services-core
| | |
| | |---pom.xml
| |
| |---pom.xml
|
|util-parent
| |
| |-common-util
| | |
| | |---pom.xml
| |
| |---pom.xml
|
|---pom.xml
(1) school-parent's POM looks like below
modelVersion4.0.0/modelVersion
groupIdroom/groupId
artifactIdSchool-parent/artifactId
version0.0.1-SNAPSHOT/version
packagingpom/packaging
properties
util-version0.0.1-SNAPSHOT/util-version
services-parent0.0.1-SNAPSHOT/services-parent
/properties
modules
moduleservices-parent/module
moduleutil-parent/module
/modules
(2) util-parent POM looks like
modelVersion4.0.0/modelVersion
parent
artifactIdSchool-parent/artifactId
groupIdroom/groupId
version0.0.1-SNAPSHOT/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdutil-parent/artifactId
packagingpom/packaging
version${util-version}/version
modules
modulecommon-util/module
/modules
(3) common-util POM looks like
modelVersion4.0.0/modelVersion
parent
artifactIdutil-parent/artifactId
groupIdroom/groupId
version${util-version}/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdcommon-util/artifactId
/project
(4) services - parent's POM looks like
modelVersion4.0.0/modelVersion
parent
artifactIdSchool-parent/artifactId
groupIdroom/groupId
version0.0.1-SNAPSHOT/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdservices-parent/artifactId
packagingpom/packaging
version${services-parent}/version
modules
moduleservices-core/module
/modules
(5) services-core's POM looks like
parent
artifactIdservices-parent/artifactId
groupIdroom/groupId
version${services-parent}/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdservices-core/artifactId
dependencies
dependency
groupIdroom/groupId
artifactIdcommon-util/artifactId
version${util-version}/version
/dependency
/dependencies
While running the root POM(No. 1), build success.
But while running services parent individually , I am getting an build error
saying it is not able to find common-util.
Is the way i am accessing property value(${...}), inside version tag having
any issue ?
Or
Any other issue ?
Please help me to solve this issue, or give some suggestion on how can i
overcome this problem.. ?
--
View this message in context:
http://maven.40175.n5.nabble.com/Reg-accessing-parent-POM-s-property-in-child-POM-s-version-tag-tp5708657.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: Problem downloading sources - The following files where skipped
I've had the same problem since maven did remeber that the sources were already downloaded. For me it was easily solved by execuring mvn clean, i.e mvn clean dependency:sources. -- View this message in context: http://maven.40175.n5.nabble.com/Problem-downloading-sources-The-following-files-where-skipped-tp127791p5708648.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] Mojo's Ship Maven Plugin 1.0-alpha-2 released
Hi, The Mojo team is pleased to announce the release of Mojo's Ship Maven Plugin version 1.0-alpha-2. Mojo's Ship Plugin is used when you have continuous deployment scripts that you want to integrate with your Apache Maven build. The plugin has the following goals. * ship:ship Resolves the shipVersion of the project artifacts and passes them to the ship scripts The plugin has support for the following kinds of ship scripts: * Bean Shell scripts * Groovy scripts * Simple Apache Maven Wagon scripts http://mojo.codehaus.org/ship-maven-plugin/ To use this version, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdship-maven-plugin/artifactId version1.0-alpha-2/version /plugin Release Notes - Mojo - Version ship-maven-plugin-1.0-alpha-2 ** Improvement * [MOJO-1845] - Define ship script file encoding ** New Feature * [MOJO-1843] - Don't fail by default when there is nothing to do * [MOJO-1844] - Allow ship scripts to be shared across modules Enjoy, The Mojo team. Apache, Apache Maven, and Maven are trademarks of The Apache Software Foundation. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Reg. accessing parent POM's property in child POM's version tag
Properties are not supported in the following XPath elements:
/project(/parent)?/(groupId/artifactId/version)
-Stephen
On 14 May 2012 13:42, RAJIV_S rajivbt...@gmail.com wrote:
I have a project structure like the below
School-parent
|
|
| services-parent
| | |
| | |-Services-core
| | |
| | |---pom.xml
| |
| |---pom.xml
|
|util-parent
| |
| |-common-util
| | |
| | |---pom.xml
| |
| |---pom.xml
|
|---pom.xml
(1) school-parent's POM looks like below
modelVersion4.0.0/modelVersion
groupIdroom/groupId
artifactIdSchool-parent/artifactId
version0.0.1-SNAPSHOT/version
packagingpom/packaging
properties
util-version0.0.1-SNAPSHOT/util-version
services-parent0.0.1-SNAPSHOT/services-parent
/properties
modules
moduleservices-parent/module
moduleutil-parent/module
/modules
(2) util-parent POM looks like
modelVersion4.0.0/modelVersion
parent
artifactIdSchool-parent/artifactId
groupIdroom/groupId
version0.0.1-SNAPSHOT/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdutil-parent/artifactId
packagingpom/packaging
version${util-version}/version
modules
modulecommon-util/module
/modules
(3) common-util POM looks like
modelVersion4.0.0/modelVersion
parent
artifactIdutil-parent/artifactId
groupIdroom/groupId
version${util-version}/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdcommon-util/artifactId
/project
(4) services - parent's POM looks like
modelVersion4.0.0/modelVersion
parent
artifactIdSchool-parent/artifactId
groupIdroom/groupId
version0.0.1-SNAPSHOT/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdservices-parent/artifactId
packagingpom/packaging
version${services-parent}/version
modules
moduleservices-core/module
/modules
(5) services-core's POM looks like
parent
artifactIdservices-parent/artifactId
groupIdroom/groupId
version${services-parent}/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdservices-core/artifactId
dependencies
dependency
groupIdroom/groupId
artifactIdcommon-util/artifactId
version${util-version}/version
/dependency
/dependencies
While running the root POM(No. 1), build success.
But while running services parent individually , I am getting an build error
saying it is not able to find common-util.
Is the way i am accessing property value(${...}), inside version tag having
any issue ?
Or
Any other issue ?
Please help me to solve this issue, or give some suggestion on how can i
overcome this problem.. ?
--
View this message in context:
http://maven.40175.n5.nabble.com/Reg-accessing-parent-POM-s-property-in-child-POM-s-version-tag-tp5708657.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Reg. accessing parent POM's property in child POM's version tag
What are you trying to accomplish? If you don't declare the version
element in a Maven project, Maven will use the version of the declared
parent as the version.
So, my suggestions is to have the versions hard-coded in the parent
section. The release plugin will update these when you release a
project, so you don't have to manage them manually.
/Anders
On Mon, May 14, 2012 at 2:42 PM, RAJIV_S rajivbt...@gmail.com wrote:
I have a project structure like the below
School-parent
|
|
| services-parent
| | |
| | |-Services-core
| | |
| | |---pom.xml
| |
| |---pom.xml
|
|util-parent
| |
| |-common-util
| | |
| | |---pom.xml
| |
| |---pom.xml
|
|---pom.xml
(1) school-parent's POM looks like below
modelVersion4.0.0/modelVersion
groupIdroom/groupId
artifactIdSchool-parent/artifactId
version0.0.1-SNAPSHOT/version
packagingpom/packaging
properties
util-version0.0.1-SNAPSHOT/util-version
services-parent0.0.1-SNAPSHOT/services-parent
/properties
modules
moduleservices-parent/module
moduleutil-parent/module
/modules
(2) util-parent POM looks like
modelVersion4.0.0/modelVersion
parent
artifactIdSchool-parent/artifactId
groupIdroom/groupId
version0.0.1-SNAPSHOT/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdutil-parent/artifactId
packagingpom/packaging
version${util-version}/version
modules
modulecommon-util/module
/modules
(3) common-util POM looks like
modelVersion4.0.0/modelVersion
parent
artifactIdutil-parent/artifactId
groupIdroom/groupId
version${util-version}/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdcommon-util/artifactId
/project
(4) services - parent's POM looks like
modelVersion4.0.0/modelVersion
parent
artifactIdSchool-parent/artifactId
groupIdroom/groupId
version0.0.1-SNAPSHOT/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdservices-parent/artifactId
packagingpom/packaging
version${services-parent}/version
modules
moduleservices-core/module
/modules
(5) services-core's POM looks like
parent
artifactIdservices-parent/artifactId
groupIdroom/groupId
version${services-parent}/version
relativePath..//relativePath
/parent
groupIdroom/groupId
artifactIdservices-core/artifactId
dependencies
dependency
groupIdroom/groupId
artifactIdcommon-util/artifactId
version${util-version}/version
/dependency
/dependencies
While running the root POM(No. 1), build success.
But while running services parent individually , I am getting an build error
saying it is not able to find common-util.
Is the way i am accessing property value(${...}), inside version tag having
any issue ?
Or
Any other issue ?
Please help me to solve this issue, or give some suggestion on how can i
overcome this problem.. ?
--
View this message in context:
http://maven.40175.n5.nabble.com/Reg-accessing-parent-POM-s-property-in-child-POM-s-version-tag-tp5708657.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Reg. accessing parent POM's property in child POM's version tag
version${project.version}/version
I thought based on the above example, any property value should be supported
in version tag using ${...}
Any, recommendtion/solution for my problem ,.. how can solve this issue ?
Plz explain a bit detail as i am new this maven..
Means , Nowhere i can't use dynamic values(custom decalred properrties) from
parent POM for *version tag* isn't ?
--
View this message in context:
http://maven.40175.n5.nabble.com/Reg-accessing-parent-POM-s-property-in-child-POM-s-version-tag-tp5708657p5708662.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: Reg. accessing parent POM's property in child POM's version tag
On 14 May 2012 14:26, RAJIV_S rajivbt...@gmail.com wrote:
version${project.version}/version
That is not a property but a reference to the pom.
I thought based on the above example, any property value should be supported
in version tag using ${...}
not in /project/version or /project/parent/version
Any, recommendtion/solution for my problem ,.. how can solve this issue ?
Plz explain a bit detail as i am new this maven..
Means , Nowhere i can't use dynamic values(custom decalred properrties) from
parent POM for *version tag* isn't ?
not quite true, but keep in mind that the release plugin will update
the hardcoded versions for you
--
View this message in context:
http://maven.40175.n5.nabble.com/Reg-accessing-parent-POM-s-property-in-child-POM-s-version-tag-tp5708657p5708662.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven-shade-plugin transform resource files
Hello I am working on jetty embedded application and use maven shade plugin. The problem is that I want to compress js, css, and html static files before shade plugin pack it to single jar. I wrote program that can do all I want in single directory. How to force plugin to pack treated by my program files?
Re: maven-shade-plugin transform resource files
Hi, Hello I am working on jetty embedded application and use maven shade plugin. The problem is that I want to compress js, css, and html static files before shade plugin pack it to single jar. I wrote program that can do all I want in single directory. How to force plugin to pack treated by my program files? That sounds like the wrong way cause you have a war archive which is the default to distribute into servlet engines like jetty etc. So why not using the war plugin ? You can js compressor plugins (yu...compressor exists, i can't remember the exact name)...and add the results to the war configuration... Ah found it: http://alchim.sourceforge.net/yuicompressor-maven-plugin/index.html Kind regards Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[Solved] Re: Memory Leak?
On 11 May 2012 15:56, Hilco Wijbenga hilco.wijbe...@gmail.com wrote: 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, Maven does not release memory before continuing on with the next module? Or would this be something that is specific to a particular plugin (in my case, it's undoubtedly the GWT Maven plugin)? I changed a number of things so I'm not sure exactly which one did the trick ... but I think we can make a good guess. :-) Oh, and this is all with Maven 3.0.3. I finally upgraded my system from 32bit to 64bit (GNU/Linux). I also went from the Sun JDK (1.6.0.32) to IcedTea (7.2.1). Finally, I upgraded the Maven Compiler plugin to 2.4. I believe it is mainly the first two changes that fixed things. Strangely enough, I can now run the full build with only 1GB (and I could probably use even less). I had 2GB before and that was still not enough... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Solved] Re: Memory Leak?
2012/5/14 Hilco Wijbenga hilco.wijbe...@gmail.com: On 11 May 2012 15:56, Hilco Wijbenga hilco.wijbe...@gmail.com wrote: 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, Maven does not release memory before continuing on with the next module? Or would this be something that is specific to a particular plugin (in my case, it's undoubtedly the GWT Maven plugin)? I changed a number of things so I'm not sure exactly which one did the trick ... but I think we can make a good guess. :-) Oh, and this is all with Maven 3.0.3. Cool and 3.0.4 ? I finally upgraded my system from 32bit to 64bit (GNU/Linux). I also went from the Sun JDK (1.6.0.32) to IcedTea (7.2.1). Finally, I upgraded the Maven Compiler plugin to 2.4. I believe it is mainly the first two changes that fixed things. Strangely enough, I can now run the full build with only 1GB (and I could probably use even less). I had 2GB before and that was still not enough... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com 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
[ANN] FileWeaver Maven Plugin 1.0 Released
I'd like to announce the release of FileWeaver 1.0. FileWeaver is a Maven plugin for assembling files from snippets. Multiple external files and literal segments can be combined, with token substitution. Why? I needed to append chunks of settings to a lengthy configuration file for testing, so that I didn't have to carry around two slightly different versions and keep them in sync. Homepage: http://mypage.iu.edu/~mwood/FileWeaver/index.html Coordinates: plugin groupIdedu.iu.ul.maven.plugins/groupId artifactIdfileweaver/artifactId version1.0/version /plugin -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgpacFSWVveLo.pgp Description: PGP signature
Re: maven-shade-plugin transform resource files
I use jetty embedded. War plugin is not applicable 2012/5/14 Karl Heinz Marbaise khmarba...@gmx.de Hi, Hello I am working on jetty embedded application and use maven shade plugin. The problem is that I want to compress js, css, and html static files before shade plugin pack it to single jar. I wrote program that can do all I want in single directory. How to force plugin to pack treated by my program files? That sounds like the wrong way cause you have a war archive which is the default to distribute into servlet engines like jetty etc. So why not using the war plugin ? You can js compressor plugins (yu...compressor exists, i can't remember the exact name)...and add the results to the war configuration... Ah found it: http://alchim.sourceforge.net/**yuicompressor-maven-plugin/**index.htmlhttp://alchim.sourceforge.net/yuicompressor-maven-plugin/index.html Kind regards Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Enforcer 1.1 Released
The Maven team is pleased to announce the release of the Maven Enforcer, version 1.1 This plugin provides various configurable validation rules for Maven builds. http://maven.apache.org/enforcer/ http://maven.apache.org/plugins/maven-enforcer-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.1/version /plugin Release Notes - Maven 2.x Enforcer Plugin - Version 1.1 ** Bug * [MENFORCER-98] - requirePluginVersions rule is not compatible with maven 3.0-beta-1 * [MENFORCER-114] - Typo in Require Plugin Versions Documentation * [MENFORCER-125] - requireProperty documentation's example for property.version uses wrong regex ** Improvement * [MENFORCER-118] - DependencyConvergence gets better if it doesn't fail on snapshots of same baseVersion ** New Feature * [MENFORCER-128] - Fail the build if a dependency is overwriten with an incompatible lower version (patch) Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
