Re: can't remove project
Based on the error below, it looks like the deletes aren't cascading properly. You could probably log in to the database and blow away individual projects if you dug around and figured out how tables and foreign keys are linked up. This seems to be a bug, I'd file it in JIRA. Delete a project was just not tested enough before release, apparently. Wayne On 5/13/06, Brian E. Fox [EMAIL PROTECTED] wrote: Somehow I have a bunch of projects that got duplicated but I can't remove them. Here's the error, is there anything I can do other than blow away the db and start over? ognl.MethodFailedException: Method removeProject failed for object [EMAIL PROTECTED] [javax.jdo.JDOUserException: One or more instances could not be deleted NestedThrowables: javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM BUILDDEFINITION WHERE ID = ? NestedThrowables: SQL Exception: DELETE on table 'BUILDDEFINITION' caused a violation of foreign key constraint 'PROJECT_BUILP8_FK2' for key (86). The statement has been rolled back.]
Re: can't remove project
We had a problem similar to this as well and were able to delete them by shutting down Continuum and going into the build directory folder and deleting the projects from there, then they would remove from the GUI. FYI, Our problem occurred because I refreshed the page before the projects were all completely added, at least that's how I was able to re-create it. On 5/13/06, Wayne Fay [EMAIL PROTECTED] wrote: Based on the error below, it looks like the deletes aren't cascading properly. You could probably log in to the database and blow away individual projects if you dug around and figured out how tables and foreign keys are linked up. This seems to be a bug, I'd file it in JIRA. Delete a project was just not tested enough before release, apparently. Wayne On 5/13/06, Brian E. Fox [EMAIL PROTECTED] wrote: Somehow I have a bunch of projects that got duplicated but I can't remove them. Here's the error, is there anything I can do other than blow away the db and start over? ognl.MethodFailedException: Method removeProject failed for object [EMAIL PROTECTED] [javax.jdo.JDOUserException: One or more instances could not be deleted NestedThrowables: javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM BUILDDEFINITION WHERE ID = ? NestedThrowables: SQL Exception: DELETE on table 'BUILDDEFINITION' caused a violation of foreign key constraint 'PROJECT_BUILP8_FK2' for key (86). The statement has been rolled back.] -- Adam Altemus
Re: [m2] umlGraph
On 5/12/06, Wayne Fay [EMAIL PROTECTED] wrote: Didn't mean to include that looking cool line under my name... I know Prefuse is pure Java and thus crossplatform, not depending on Graphviz, etc. I'd personally just prefer a single image with my UML chart than a Java applet. prefuse seems to be first an set of APIs to control . I think Carlos used it to create a custom plugin (maven-grafo-plugin) to render the files. I don't see this plugin available somewhere so it must be one of Carlos private experiments :) It shouldn't be hard to modify the plugin or to write a new one to generate your pictures. So first, read that: http://prefuse.org/doc/manual/intro/ Then perhaps you can reuse the Display public method that returns a BufferedImage: public BufferedImage getOffscreenBuffer(); And here's a code example to save your image to PNG: http://javaalmanac.com/egs/javax.imageio/Graphic2File.html Good luck! Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : log4j.properties expendable and ignored
Look at http://jira.codehaus.org/browse/MSUREFIRE-108 But AFAIK it works with maven-surefire-plugin:2.1.3 but not with snapshot version. - Olivier -Message d'origine- De : Arik Kfir [mailto:[EMAIL PROTECTED] Envoyé : samedi 13 mai 2006 09:37 À : Maven Users List Objet : Re: log4j.properties expendable and ignored have you checked the issues for the surefire project, or the surefire-plugin? On 5/13/06, Simon Kitching [EMAIL PROTECTED] wrote: Hi, I've just gone through all the JIRA issues for SUREFIRE and can't see any such issue. If it is true that src classes come before test classes then I agree an issue should be raised. Ido, you could just add a test which does System.out.println( this.getClassLoader().getResource(log4j.properties).toString()); or similar to see which log4j properties file is seen first. Another possibility for the log4j.properties being ignored is that there is a log4j.xml file in the classpath somewhere. Config files in xml format are used in preference to ones in properties format. Regards, Simon On Sat, 2006-05-13 at 02:47 +0300, Arik Kfir wrote: I think there's a JIRA on the surefire plugin which gives precedence to the main classes over the test classes - hence the log4j.properties in src/main/resources is used before the src/test/resources's file is loaded. On 5/12/06, Ido M. Tamir [EMAIL PROTECTED] wrote: Hi, I am using maven 2.0.4 I have log4j.properties file in src/test/resources and src/main/resources. after compilation directory structure: -- test-classes | |-- hibernate.cfg.xml | |-- import.properties | |-- log4j.properties | `-- org The settings in this file are ignored in unit tests and other settings (assembly...). When I remove both files log4j doesn't even complain. The log level always seems to be info. This is also true for unit test run from eclipse (I use mvn eclipse:eclipse) This is independent of having commons-logging as a dependency or not. thank you very much for your suggestions ido -- --- 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] -- __ Cheers, Arik Kfir [EMAIL PROTECTED] Linux user, number 415067 - http://counter.li.org/ http://corleon.dnsalias.org This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] umlGraph
Well there you go! Perhaps I will have some time next week to look at this in more detail. Would certainly be a nice addition. Wayne On 5/13/06, jerome lacoste [EMAIL PROTECTED] wrote: On 5/12/06, Wayne Fay [EMAIL PROTECTED] wrote: Didn't mean to include that looking cool line under my name... I know Prefuse is pure Java and thus crossplatform, not depending on Graphviz, etc. I'd personally just prefer a single image with my UML chart than a Java applet. prefuse seems to be first an set of APIs to control . I think Carlos used it to create a custom plugin (maven-grafo-plugin) to render the files. I don't see this plugin available somewhere so it must be one of Carlos private experiments :) It shouldn't be hard to modify the plugin or to write a new one to generate your pictures. So first, read that: http://prefuse.org/doc/manual/intro/ Then perhaps you can reuse the Display public method that returns a BufferedImage: public BufferedImage getOffscreenBuffer(); And here's a code example to save your image to PNG: http://javaalmanac.com/egs/javax.imageio/Graphic2File.html Good luck! Jerome - 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: maven-eclipse-plugin
Hi Steven, this was my original question that eclipse:eclipse only generates project files for each of the modules but not for the parent project. So I guess this would be a really nice feature. Regards, Ingo Steven Coco schrieb: This is good news. But I think it's not as easy for me as for you!! Well it is really straight forward. I just have my maven 2.0 multi-modules project as a eclipse project. After I ran mvn eclipse:eclipse I imported the nested projects through the standard project import by pointing into my multi-modules project. In older Version you got an error because of nested project structure. Now you don't get one :-) When I run eclipse:eclipse on my parent POM that has 2 modules, Maven only generates project files for each of the modules -- the parent does not get a project generated. Unless that is not what you meant. Do you go ahead an create the parent eclipse project by hand? Of course, I just did that, and it does work. So this might be a nice improvement -- I'll have to go ahead and use it and see how it works out for me. Thanks, Steven. Regards, Ingo Jochen Wiedmann schrieb: On 5/12/06, Ingo D�ppe [EMAIL PROTECTED] wrote: The new upcoming Eclipse Version 3.2 (Callisto) does support nested projects. So there is no need for any workaround to get nested project structure into eclipse. I am interested in that feature. Perhaps others are as well. Could you please drop me a note, where it is documented? Regards, Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: log4j.properties expendable and ignored
On Saturday 13 May 2006 09:42, Olivier Lamy wrote: Look at http://jira.codehaus.org/browse/MSUREFIRE-108 But AFAIK it works with maven-surefire-plugin:2.1.3 but not with snapshot version. Thanks for all your replies. I forgot to include log4j in my classpath (duh). It now works as expected. thank you very much ido - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: log4j.properties expendable and ignored
LOL! :) On 5/13/06, Ido M. Tamir [EMAIL PROTECTED] wrote: On Saturday 13 May 2006 09:42, Olivier Lamy wrote: Look at http://jira.codehaus.org/browse/MSUREFIRE-108 But AFAIK it works with maven-surefire-plugin:2.1.3 but not with snapshot version. Thanks for all your replies. I forgot to include log4j in my classpath (duh). It now works as expected. thank you very much ido - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- __ Cheers, Arik Kfir [EMAIL PROTECTED] Linux user, number 415067 - http://counter.li.org/ http://corleon.dnsalias.org
RE: [m2.0.4] OutOfMemoryError
Thanks that would explain everything that I observed. Thanks for your help; the tests are working great now. -dh -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Friday, May 12, 2006 12:57 PM To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError I suspect that the change was caused by a recent change to the test plugin to fork by default (I believe the default changed from never to once). -Original Message- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Friday, May 12, 2006 07:10 To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError Bob, Thanks for the clarification. One thing I still don't understand is that when I first had trouble running my tests (getting out of memory errors), people in this mail list said to set MAVEN_OPTS and it did solve my problem. Now, I may have been executing the tests thru continuum or maven directly, I don't remember for sure. In any case, it solved the problem. I now find that running tests directly thru maven requires 'argLine' usage. Any thoughts? -dh -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Friday, May 12, 2006 6:53 AM To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError For everyone else following this thread, the reason you need to use the argLine rather than MAVEN_OPTS is that tests are forked so they run in their own JVM. Setting MAVEN_OPTS sets the heap limit for the JVM running Maven, but not the JVM running the tests. The argLine configuration sets additional arguments for the JVM that is running the tests. -Original Message- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 21:55 To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError Dan, I think you are right! I just added this to one of the failing projects and it works. For me maven is ignoring the MAVEN_OPTS setting. Using 'argLine' my memory usage is now reported to be 300MB where it was stuck just shy of 64MB. Thanks a bunch. -dh -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 4:47 PM To: users@maven.apache.org Cc: Kris Nuttycombe Subject: Re: [m2.0.4] OutOfMemoryError You can use the argLine configuration option for surefire plugin to add JVM args. Things like -ea to enable the assertions that you should be testing are also good things to put on that line. Dan On Thursday 11 May 2006 16:40, Kris Nuttycombe wrote: I have a related question to this: Is it possible to specify the memory footprint except using the MAVEN_OPTS environment variable? It would be useful to have this as an option for the surefire plugin, at least if the tests are running in a separate JVM. Kris Dave Hoffer wrote: For some of my projects that use a lot of memory when running unit tests I set MAVEN_OPTS to -Xmx1024m to get all the tests to not throw OutOfMemoryErrors. I now have a maven project that has a dependency on the prior component but I do get an OutOfMemoryError when I run the unit tests. I have tried to set -Xmx to larger values with no success, as it always fails. The poms are all but identical, why should one fail? Also, in the process viewer I see that when running the tests there are two java processes. One reports using about 90MB and the other about 64MB. Why are there two? These numbers are way lower than the max java heap size specified. Any ideas? -dh - 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] -- J. Daniel Kulp [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] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - 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,
How do I generate the changes.xml for the changes-maven-plugin ?
Hi , I'm using bugzilla as my issue management, how do I generate the changes.xml for the changes-maven-plugin ? Thank you kindly Malcolm DISCLAIMER: This message may contain information which is confidential, private or privileged in nature. If you are not the intended recipient, you may not peruse, use, disseminate, distribute or copy this message or file which is attached to this message. If you have received this message in error, please notify the sender immediately by e-mail, facsimile or telephone and thereafter return and/or destroy the original message. Any views of this communication are those of the sender except where the sender specifically states them to be those of Faritec (Holdings) Limited (Faritec) and/or any of its subsidiaries including (but not limited to) Faritec Enterprise Solutions (Proprietary) Limited, Faritec Strategic IT Services (Proprietary) Limited, Faritec Contracting (Proprietary) Limited, Ebis and/or any of its subsidiaries. Please note that the recipient must scan this e-mail and any attached files for viruses and the like. While we do everything possible to protect information from viruses, Faritec accepts no liability of whatever nature for any loss, liability, damage or expense resulting directly or indirectly from the access and/or downloading of any files which are attached to this e-mail message.
RE: log4j.properties expendable and ignored
Could you find out which log4j configuration file actually was used? Is it the one under main or the one under test? Andreas -Original Message- From: Ido M. Tamir [mailto:[EMAIL PROTECTED] Sent: Saturday, May 13, 2006 2:26 AM To: Maven Users List Subject: Re: log4j.properties expendable and ignored On Saturday 13 May 2006 09:42, Olivier Lamy wrote: Look at http://jira.codehaus.org/browse/MSUREFIRE-108 But AFAIK it works with maven-surefire-plugin:2.1.3 but not with snapshot version. Thanks for all your replies. I forgot to include log4j in my classpath (duh). It now works as expected. thank you very much ido - 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: Why does Maven 2 keep trying to download stuff that i put in my local repository
Well Maven usually tell you when there is a new plugin available and ask you if you want to install it but if you answer no, I guess you are never asked again. Also, you have to be sure you haven't declared which plugin version to use in your pom. On 5/12/06, Stefan Arentz [EMAIL PROTECTED] wrote: On 5/12/06, Kenney Westerhof [EMAIL PROTECTED] wrote: Have you checked your local repo? The pom should be there. It is :-) Thanks! I guess it is good practice to dump the local repository once in a while to get new versions of the plugins. S.
Re: Why does Maven 2 keep trying to download stuff that i put in my local repository
On Sat, 13 May 2006, Alexandre Poitras wrote: Well Maven usually tell you when there is a new plugin available and ask you if you want to install it but if you answer no, I guess you are never asked again. Also, you have to be sure you haven't declared which plugin version to use in your pom. I haven't seen Maven 2 ask me anything like that, yet. Maven 1 does, IIRC. :) Updating plugins is pretty easy in m2: just specify the '-cpu' argument (see mvn --help). -- Kenney On 5/12/06, Stefan Arentz [EMAIL PROTECTED] wrote: On 5/12/06, Kenney Westerhof [EMAIL PROTECTED] wrote: Have you checked your local repo? The pom should be there. It is :-) Thanks! I guess it is good practice to dump the local repository once in a while to get new versions of the plugins. S. -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] umlGraph
https://svn.apache.org/repos/asf/maven/sandbox/grafo the applet is one from the prefuse samples, the plugin just spits out xml. I have to check the project info reports plugin to see the code that lists the tree of dependencies On 5/13/06, Wayne Fay [EMAIL PROTECTED] wrote: Well there you go! Perhaps I will have some time next week to look at this in more detail. Would certainly be a nice addition. Wayne On 5/13/06, jerome lacoste [EMAIL PROTECTED] wrote: On 5/12/06, Wayne Fay [EMAIL PROTECTED] wrote: Didn't mean to include that looking cool line under my name... I know Prefuse is pure Java and thus crossplatform, not depending on Graphviz, etc. I'd personally just prefer a single image with my UML chart than a Java applet. prefuse seems to be first an set of APIs to control . I think Carlos used it to create a custom plugin (maven-grafo-plugin) to render the files. I don't see this plugin available somewhere so it must be one of Carlos private experiments :) It shouldn't be hard to modify the plugin or to write a new one to generate your pictures. So first, read that: http://prefuse.org/doc/manual/intro/ Then perhaps you can reuse the Display public method that returns a BufferedImage: public BufferedImage getOffscreenBuffer(); And here's a code example to save your image to PNG: http://javaalmanac.com/egs/javax.imageio/Graphic2File.html Good luck! Jerome - 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] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why does Maven 2 keep trying to download stuff that i put in my local repository
Really, it has happened to me couple of times but I don't know why it's not always the case. On 5/13/06, Kenney Westerhof [EMAIL PROTECTED] wrote: On Sat, 13 May 2006, Alexandre Poitras wrote: Well Maven usually tell you when there is a new plugin available and ask you if you want to install it but if you answer no, I guess you are never asked again. Also, you have to be sure you haven't declared which plugin version to use in your pom. I haven't seen Maven 2 ask me anything like that, yet. Maven 1 does, IIRC. :) Updating plugins is pretty easy in m2: just specify the '-cpu' argument (see mvn --help). -- Kenney On 5/12/06, Stefan Arentz [EMAIL PROTECTED] wrote: On 5/12/06, Kenney Westerhof [EMAIL PROTECTED] wrote: Have you checked your local repo? The pom should be there. It is :-) Thanks! I guess it is good practice to dump the local repository once in a while to get new versions of the plugins. S. -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Site plugin 2.0-SNAPSHOT , can not find the parent pom warning and some other things
Just stumbled over the relativePath element, which I assume will solve my
warning, a case of rtfm there...
On 12/05/06, Mikael Andersson [EMAIL PROTECTED] wrote:
Hi
When I try to run mvn site:site in a child module I get the following
warning message:
[WARNING] Unable to load parent project from repository: Could not find
the model file '/scratch/usr/workspace/rssgen/rssgen-core/../pom.xml'.
It is looking for the parent pom in the wrong place, to work for me it
would have to look here: ./rssgen/rssgen-core../rssgen-parent/pom.xml
My project structure is like this:
/rssgen/rssgen-parent
/rssgen/rssgen-core
/rssgen/rssgen-servlet
with group Id for all being uk.ac.ebi.es.rssgen , and the artifactId the
same as the top directory above.
Another question; is it possible to get the ${modules} navigation which I
have in the parent module in the child modules?
Currently I have the ${modules} in the child modules site.xml, but there
is nothing generated. Can I reference the parents ${modules} somehow?
Thanks
Micke
mule and maven2
Does anyone have some experience in using maven 2 along with the mule ESB? We are having difficulties to determine what are the right libs to put in WEB-INF/lib so transitive dependencies would come very useful. I hope someone is working on archetypes and a m2 plugin as mule is a nice target for one. Srgjan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-eclipse-plugin
Ingo Düppe wrote: Hi Steven, this was my original question that eclipse:eclipse only generates project files for each of the modules but not for the parent project. So I guess this would be a really nice feature. Regards, Ingo When you say parent project are you referring to a multi module project? What would the equivalent of it be under eclipse, I mean it's not a project with a java nature, what is it? Also if such a feature would need to be implemented I believe the only way to achieve something like that would be to make a multi module projects but with a flat hierarchy (as eclipse can't handle projects that are within projects but all projects are flatly in a workspace) and relative paths between them and people on the list have been against that kind of approach (but don't ask me why). Anyhow, once you generate the projects for the modules and import them in the workspace, do you need the parent project? Only possible use I see if some maven plugin manages to run some targets on the parent pom, otherwise I don't know. Anyone? Srgjan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mule and maven2
Sounds like a useful archetype/plugin. I have not used Mule ESB as yet but have done a bit of reading about it, and figure I'll check it out eventually. A nice M2 Archetype for Mule would certainly get me on track more quickly, when the time comes. If you have the ability and interest, I'd encourage you to create the archetype yourself and contribute it back. Wayne On 5/13/06, Srepfler Srgjan [EMAIL PROTECTED] wrote: Does anyone have some experience in using maven 2 along with the mule ESB? We are having difficulties to determine what are the right libs to put in WEB-INF/lib so transitive dependencies would come very useful. I hope someone is working on archetypes and a m2 plugin as mule is a nice target for one. Srgjan - 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]
[ANN] Maven Checkstyle Plugin 2.1
The Maven team is pleased to announce the release of the Maven Checkstyle Plugin, version 2.1 http://maven.apache.org/plugins/maven-checkstyle-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId version2.1/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12490styleName=TextprojectId=11127Create=Create * [MCHECKSTYLE-38] - checsktyle:check seems to fail on warning too * [MCHECKSTYLE-33] - Patch provides ability to control whether check MOJO violations cause build failure (inline with pmd:check) * [MCHECKSTYLE-34] - automatically detect linkXref and default to on * [MCHECKSTYLE-39] - use plugin testing harness and add test checkstyle plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven IDEA Plugin 2.0
The Maven team is pleased to announce the release of the Maven IDEA Plugin, version 2.0. http://maven.apache.org/plugins/maven-idea-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-idea-plugin/artifactId version2.0/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12295styleName=TextprojectId=11135Create=Create * [MIDEA-5] - using copyright plugin gets converted back differently to original, corrupting ipr * [MIDEA-6] - create separate :module, :project and :workspace goals * [MIDEA-11] - Attach source code and/or documentation to library jars * [MIDEA-14] - add support for ejb module configuration in iml * [MIDEA-15] - add support for war module configuration in iml * [MIDEA-16] - idea target only works after compilation * [MIDEA-21] - Running plugin multiple times causes multiple module entries in ipr * [MIDEA-27] - generated sources aren't added correctly to idea project path * [MIDEA-30] - Bad/missing settings for generated web app module * [MIDEA-31] - idea mojo doesn't work with dependency with classifier * [MIDEA-34] - Add resources to source folders instead of module libraries * [MIDEA-35] - Module Libraries and WebModule libraries to package should not have a name attribute * [MIDEA-42] - Maven IDEA Plugin does not respect dependency exclusions * [MIDEA-45] - Problems with exclude logic * [MIDEA-49] - WebModuleProperties reactor modules: adding with method 5 not compatible with /WEB-INF/classes * [MIDEA-50] - StringIndexOutOfBoundsException when adding a resource to the pom * [MIDEA-18] - Resource patterns should be configurable and have a better default (+patch) * [MIDEA-20] - Configurable excluded directories for less synchronizing * [MIDEA-23] - Add option to use full artifact names for library names * [MIDEA-25] - patch to add modules and libraries for web archives * [MIDEA-32] - Changed Xpp3Dom in favor of dom4j * [MIDEA-38] - Some improvements in generating iml-files for Intellij * [MIDEA-44] - Optional toggle switch to revert MIDEA-35 * [MIDEA-28] - Add an idea:clean goal * [MIDEA-41] - Source attachments are maintained when running idea:idea * [MIDEA-43] - Utilize plugin testing harness and create test cases for the Idea plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Assembly Plugin 2.1
The Maven team is pleased to announce the release of the Maven Assembly Plugin, version 2.1 http://maven.apache.org/plugins/maven-assembly-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.1/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12219styleName=TextprojectId=11126Create=Create * [MASSEMBLY-2] - TAR produces warning messages for over 100 cahrs in path name * [MASSEMBLY-5] - mvn assembly:assembly fails if there is no target directory already present * [MASSEMBLY-8] - Assembly plugin fails to resolve dependency when it tries to package the application * [MASSEMBLY-9] - assembly plugin with jar-with-dependency fails if there is no classes * [MASSEMBLY-11] - In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory * [MASSEMBLY-13] - assembly should automatically include generated artifacts for bin.xml (including all in a reactor) * [MASSEMBLY-20] - Assembly doesn't work with provided scope * [MASSEMBLY-29] - Possibility to aggrates sources from other modules * [MASSEMBLY-33] - document assembly descriptoir in more detail * [MASSEMBLY-37] - Assembly plugin should have the option not to repeat the build process every execution * [MASSEMBLY-40] - Evaluate project variables within assembly descriptors * [MASSEMBLY-43] - AbstractUnpackMojo#getDependencies() returns too much * [MASSEMBLY-46] - artifact classifier not used in outputFileNameMapping * [MASSEMBLY-49] - InvalidArtifactRTException is thrown when appendAssemblyId=false * [MASSEMBLY-51] - assembly:attached fails * [MASSEMBLY-52] - dependencySet is incorrect during multi-module builds * [MASSEMBLY-55] - Lost ability to attach artifact without classifier * [MASSEMBLY-64] - jar-with-dependencies has a last-one-copies-wins policy which can fail signed jars * [MASSEMBLY-65] - source repository on web site incorrect * [MASSEMBLY-70] - assembly:directory does not honor fileMode * [MASSEMBLY-74] - MANIFEST.MF is not used when specified in configuration. * [MASSEMBLY-82] - When creating a repository for assembly include transitive requirements * [MASSEMBLY-85] - Parent POMs are not pulled down into the assembled repository * [MASSEMBLY-89] - outputFileNameMapping broken * [MASSEMBLY-92] - Assembly plugin fails with fatal error if a particular fileset directory does not exist * [MASSEMBLY-98] - Assembly groupVersionAlignment excludes affects all other groupVersionAlignment * [MASSEMBLY-54] - Unable to filter files while creating assembly * [MASSEMBLY-56] - Refactor DirectoryMojo so it can be run either stand-alone or attached * [MASSEMBLY-57] - Add xsd to the set of modello outputs * [MASSEMBLY-59] - Patch to the assembly plug-in introduction APT document * [MASSEMBLY-60] - use DirectoryArchiver component instead of the internal DirectoryArchiver class in the plugin * [MASSEMBLY-61] - Should remove/deprecate AbstractUnpackAssembly's classifier field * [MASSEMBLY-68] - Need method to exclude all child dependencies when creating a jar * [MASSEMBLY-80] - Provide an option to write the artifact metadata to a repository * [MASSEMBLY-81] - Provide an option to use all dependencies in the creation of a repository * [MASSEMBLY-86] - Allow an easy way to exclude an artifact from groupId version alignment * [MASSEMBLY-62] - Ability to share DependencySets, FileSets, FileItems * [MASSEMBLY-71] - Allow an archive base directory that accepts variables * [MASSEMBLY-95] - Support unpacking of tar.gz, tgz, tar.bz2, and tbz2 archivers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Ann] Maven Javadoc Plugin 2.0
The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.0.
http://maven.apache.org/plugins/maven-javadoc-plugin/
You can run mvn -U to get the latest version of the plugin, or specify
the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.0/version
/plugin
Changes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12329styleName=TextprojectId=11138Create=Create
* [MJAVADOC-3] - plugin should honor proxy settings
* [MJAVADOC-8] - group parameter seems hard to use
* [MJAVADOC-25] - option -locale must be first on the command line.
* [MJAVADOC-28] - [EMAIL PROTECTED] foo} doesn't work when foo is a package
name
* [MJAVADOC-40] - javadoc:jar doesn't work if destDir was changed in
javadoc:javadoc
* [MJAVADOC-45] - Quoted argument text must escape apostrophes
* [MJAVADOC-47] - Javadoc plugin ignores destDir when used in reporting
section
* [MJAVADOC-49] - Embedded error: Exit code: 1 - javadoc: invalid flag:
-sourcePath
* [MJAVADOC-51] - Wrong source url on website
* [MJAVADOC-52] - locale error
* [MJAVADOC-53] - Default setting for bottom matter includes three years
for copyright info
* [MJAVADOC-55] - offline links not generated when offline
* [MJAVADOC-57] - empty target/site/apidocs/apidocs/index.html created
* [MJAVADOC-66] - Aggregated Javadoc does not use module-level dependencies
* [MJAVADOC-67] - JavaDoc plugin will not locate overview file.
* [MJAVADOC-69] - javadoc plugin install fails when running mvn
install from plugins dir
* [MJAVADOC-70] - {inceptionYear} is not evaluated when inceptionYear is
not specified in pom.
* [MJAVADOC-33] - Provide new javadoc:aggregate goal to perform javadoc
operation on project and subprojects.
* [MJAVADOC-42] - Ability to provide more complex data to bottom tag
(e.g. HTML code)
* [MJAVADOC-56] - excludePackageNames should accept wildars
* [MJAVADOC-46] - Allow -docletpath to be specified as an artifact
* [MJAVADOC-36] - Would like a way to get default javadoc behavior
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Ann] Maven WAR Plugin 2.0
The Maven team is pleased to announce the release of the Maven WAR Plugin, version 2.0. http://maven.apache.org/plugins/maven-war-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12160styleName=TextprojectId=11150Create=Create * [MWAR-1] - war:exploded removes content of .class files * [MWAR-3] - war:war launched from parent doesn't find module web.xml * [MWAR-5] - warSourceExcludes not working properly * [MWAR-6] - dependentWarExcludes and dependentWarIncludes do not support comma-separated patterns * [MWAR-7] - Referenced projects' artifacts naming scheme behaves differently when ran from reactor * [MWAR-20] - webXML/ tag doesn't work during aggregated build. * [MWAR-26] - Do not overwrite target unless source is modified * [MWAR-36] - filtering doesn't work on web resources not on the root of the webResource dir * [MWAR-11] - Add war:exploded and war:inplace goals * [MWAR-12] - Add resource filtering to war plugin * [MWAR-13] - War plugin needs better handling of multiple executions * [MWAR-19] - Make sure that there aren't two jars with the same artifactId and version * [MWAR-21] - Need a way to include limited set of webapp's dependencies * [MWAR-27] - It should be possible to exclude the META-INF/maven directory from produced WARs * [MWAR-8] - Merge contents of dependent wars into war being built * [MWAR-15] - Support separate generation of WAR's manifest.mf * [MWAR-24] - [PATCH] Add ability to specify context.xml file in plugin configuration * [MWAR-28] - test war plugin using plugin testing harness - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Ann] Maven JXR Plugin 2.0
The Maven team is pleased to announce the release of the Maven JXR Plugin, version 2.0. http://maven.apache.org/plugins/maven-jxr-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jxr-plugin/artifactId version2.0/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12480styleName=TextprojectId=11194Create=Create * [MJXR-3] - [JXR] botton doesn't include current year for license text * [MJXR-6] - Jxr breaks in projects with generated-sources directories * [MJXR-11] - long/complex destination directories for site cause a String index out of range error * [MJXR-2] - don't generated summary page and include both reports in menu like m1 * [MJXR-9] - JXR Plugin Documentation and How to use APT doc * [MJXR-1] - add an aggregate option - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven PMD Plugin 2.0
The Maven team is pleased to announce the release of the Maven PMD Plugin, version 2.0 http://maven.apache.org/plugins/maven-pmd-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.0/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12262styleName=TextprojectId=11140Create=Create * [MPMD-2] - pmd has problems with package-info.java. * [MPMD-15] - End line of violation displays as begin line * [MPMD-24] - Check goals fail in multi-module builds * [MPMD-25] - Character \ in Xref-Link in cpd report causes problems with some browsers * [MPMD-16] - Utilise the exclusion mechanism to allow arbitrary exclusions * [MPMD-18] - set linkXRef to true by default, and only link if JXR report is included to make it automatic * [MPMD-19] - Update PMD plugin docs * [MPMD-23] - Use PMD 3.6 * [MPMD-13] - Provide pmd:check (patch attached) * [MPMD-14] - create pmd:cpd-check goal * [MPMD-27] - Create test for pmd plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Cobertura Plugin 2.0
The Mojo team is pleased to announce the release of the Cobertura Plugin for Maven, version 2.0. http://mojo.codehaus.org/cobretura-maven-plugin You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.0/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12428styleName=TextprojectId=11226Create=Create * [MCOBERTURA-2] - Cobertura fails in multi-project * [MCOBERTURA-3] - [cobertura] doesn't recognise generated sources * [MCOBERTURA-6] - Cobertura doesn't check for project programming language * [MCOBERTURA-11] - Cobertura plugin forces ASM 2.1 on projects * [MCOBERTURA-12] - Cobertura runs tests twice * [MCOBERTURA-15] - cobertura-maven-plugin: Reports are not generated after a 'clean' * [MCOBERTURA-20] - Cobertura outputs to wrong directory in multi-project * [MCOBERTURA-30] - Error when setting the check parameter for cobertura:check * [MCOBERTURA-31] - Cobertura fails with empty source folders * [MCOBERTURA-10] - use standard configuration style for checks * [MCOBERTURA-17] - Cobertura Plugin (codehaus mojo) initial release * [MCOBERTURA-18] - cobertura-maven-plugin: Documentation enhancement * [MCOBERTURA-22] - Allow multiple output formats for Cobertura report * [MCOBERTURA-8] - [cobertura] add support for packageLineRate, packageBranchRate in checker * [MCOBERTURA-29] - Use the plugin testing harness and create tests for the cobertura plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Release Plugin 2.0 Beta 4
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0 Beta 4.
http://maven.apache.org/plugins/maven-release-plugin/
You can run mvn -U to get the latest version of the plugin, or specify
the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.0-beta-4/version
/plugin
Changes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12367styleName=TextprojectId=11144Create=Create
* [MRELEASE-4] - release plugin should ignore pom.xml from status check
* [MRELEASE-9] - default version for the release, but not the development
* [MRELEASE-20] - remove release.properties after successful release:perform
* [MRELEASE-24] - release.properties should be removed between (failed)
release runs
* [MRELEASE-25] - next dev version of pom gets release info
* [MRELEASE-27] - Insufficient information when SCM URL is wrong
* [MRELEASE-30] - release:prepare changes incorrectly tag pom scm if
tagbase not standard
* [MRELEASE-31] - Dependency management versions should only be updated
if they are SNAPSHOTs
* [MRELEASE-37] - Module dependancies with inherited versions are
updated to have versions
* [MRELEASE-43] - Release plug-in did not add the tag to the end of tagBase
* [MRELEASE-44] - release:perform doesn't work at all without
release.properties
* [MRELEASE-45] - release plugin removes xml comments and attributes
* [MRELEASE-48] - release:prepare fails when release.properties already
exists
* [MRELEASE-57] - ../tags doesn't work
* [MRELEASE-59] - Ability to pass user defined arguments into
release:perform
* [MRELEASE-60] - release plugin must rewrite scm connection + tag in
tagged pom for providers other than SVN
* [MRELEASE-63] - Error when trying release:prepare a second time
* [MRELEASE-64] - prerequisites are stripped on release:prepare
* [MRELEASE-66] - Source and Javadoc bundles should be optional
* [MRELEASE-70] - ${version} in dependencyManagement is replaced after
release:prepare
* [MRELEASE-71] - build.pluginMangement.plugin is growing after each
release:prepare
* [MRELEASE-75] - Release perform injects parent pom into child and
checks in for next development iteration
* [MRELEASE-80] - release:prepare incorrectly Runtime.exec's m2 instead
of mvn
* [MRELEASE-86] - release:prepare fails on checkin while using Clearcase
* [MRELEASE-90] - Exception if version is SNAPSHOT
* [MRELEASE-91] - Updating of dependencyManagement inconsistent with
updating of dependencies with regard to SNAPSHOTs
* [MRELEASE-93] - release:prepare loses POM prerequisite element
* [MRELEASE-95] - Exception if version has no minor number
* [MRELEASE-98] - re-architect as fully-tested components
* [MRELEASE-101] - tests contains jdk1.5 method (impossible to build it
without skipping test or using need jdk upgrade)
* [MRELEASE-105] - Top Matter Lost in POM
* [MRELEASE-77] - Adding a test only mode, where nothing is checked in
into SCM
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Site Plugin 2.0 Beta 5 Released
The Maven team is pleased to announce the release of the Maven Site
Plugin, version 2.0-beta-5.
http://maven.apache.org/plugins/maven-site-plugin/
You can run mvn -U to get the latest version of the plugin, or specify
the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.0-beta-5/version
/plugin
Changes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12541styleName=TextprojectId=11146Create=Create
* [MSITE-23] - problems with site:stage
* [MSITE-24] - Site deployment doesn't allow users in the group to write
files
* [MSITE-40] - don't generate doc file if it is unchanged
* [MSITE-44] - make site reactor aware
* [MSITE-48] - add reusable skin functionality and create skins default,
stylus and classic
* [MSITE-51] - add breadcrumbs
* [MSITE-58] - Ability to assign a report to choosen navigation menu
* [MSITE-65] - ${parentProject}\ in default site descriptor doesn't resolve
* [MSITE-71] - Plugin uses NON interpolated model values (e.g URL) due
to MavenProject.getParent returning non interpolated project
* [MSITE-72] - new non reactor populateModules SiteMojo code assumes
each POM declares its own URL
* [MSITE-73] - new site code fails to generate banner images in projects
other than site.xml owning project
* [MSITE-74] - Suport proxy
* [MSITE-86] - ${modules} macro placed in site.xml does work properly
* [MSITE-91] - src/site/site.xml hardcoded in AbstractSiteMojo.java
* [MSITE-97] - Site plugin doesn't copy images to target
* [MSITE-102] - SCM files in src/site directory cause 'mvn site' to fail
- need to exclude files
* [MSITE-104] - There is no way to specify the input encoding of site
documents
* [MSITE-108] - problem with nav generation (collapse = true) snapshot
used 20060315.092459-4.jar (same trouble doxia trunk)
* [MSITE-110] - Use reactor to find parent URL where possible patch
(patch also includes improved calculate relative path and better read
modules from filesystem POM functionality)
* [MSITE-111] - Invalid site-plugin_ja.properties
* [MSITE-113] - generated-site no longer working
* [MSITE-116] - When deploying an individual stage site it goes in the
wrong place
* [MSITE-128] - Site plugin does not properly handle filenames with more
than one period
* [MSITE-61] - deployment of site descriptor should populate any modules
items
* [MSITE-62] - make absolute paths relative where possible
* [MSITE-63] - replace interpolated values with decoration model directives
* [MSITE-94] - Add an image in an item from the site descriptor (m1 style)
* [MSITE-100] - Improve error message about duplicate files
* [MSITE-109] - Site plugin should convert .fml files when working from
xdocDirectory
* [MSITE-115] - Provide a default value for a staging directory
* [MSITE-127] - Welcome page should work with mvn site:run
* [MSITE-68] - Ability to view how the site would look without
generating the entire site
* [MSITE-98] - Allow files to be excluded from site generation
* [MSITE-99] - Spanish translation
* [MSITE-105] - No line number for Doxia barfs makes using APT to write
site documentation all but impossible
* [MSITE-80] - refactor site mojo into reusable components
* [MSITE-103] - finish refactoring of category summary pages and index
page report
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Ann] Maven Project Info Reports Plugin 2.0
The Maven team is pleased to announce the release of the Maven Project Info Reports Plugin, version 2.0. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.0/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12181styleName=TextprojectId=11142Create=Create * [MPIR-2] - Dependencies report throws NullPointerException when a transitive dependency has system scope * [MPIR-18] - Dependency report shows dependencies with scope test as required for compilation * [MPIR-21] - no a href generated for archive URL * [MPIR-22] - Source Repository is confused by certain URLs * [MPIR-29] - Invalid groupId in dependency pom fails dependencies report with an IAE * [MPIR-33] - ScmReport doesn't accept non-artifactId URLs * [MPIR-36] - Invalid project-info-report_ja.properties * [MPIR-39] - logic error in dependency resolution * [MPIR-40] - dependencies report no longer runs standalone * [MPIR-45] - Some french translations are missing * [MPIR-12] - Dutch (NL) translation for site and reports plugins * [MPIR-19] - Site plugin doesn't handle pom.xml in maven 1 version. * [MPIR-30] - The automatically generated documentation should identify the project's group id, artifact id, and maybe version * [MPIR-38] - sort Project Dependencies and Project Transitive Dependencies on groupId, then artifactId * [MPIR-41] - rearrange report * [MPIR-10] - Add Dependency Convergence (w/Ready for Release indicator) report. * [MPIR-11] - improved dependency report - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Resources Plugin 2.2
The Maven team is pleased to announce the release of the Maven Resources Plugin, version 2.2. http://maven.apache.org/plugins/maven-resources-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.2/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12486styleName=TextprojectId=11145Create=Create * [MRESOURCES-2] - No such file or directory when resource targetdirectory contains ../ and target/classes does not exist. * [MRESOURCES-15] - Resources plugin does not filter systemproperties properly * [MRESOURCES-17] - Filtering of property values containing backslashes for properties files does not escape them * [MRESOURCES-18] - System properties and cmdline params not filtered without filter file * [MRESOURCES-10] - Filtering should handle java.io.File values * [MRESOURCES-11] - Module doesn't depend on commons-io - remove dependency from pom * [MRESOURCES-14] - Move the description of the mojo from @description to the top of the class's comment block * [MRESOURCES-16] - test resources plugin using plugin testing harness - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Surefire Plugin 2.2
The Maven team is pleased to announce the release of the Maven Surefire Plugin, version 2.2. http://maven.apache.org/plugins/maven-surefire-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.2/version /plugin Changes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12440styleName=TextprojectId=10541Create=Create http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12207styleName=TextprojectId=11148Create=Create * [SUREFIRE-25] - surefire property droppings in fork mode * [SUREFIRE-30] - Wrong classpath separator * [SUREFIRE-33] - java.lang.ExceptionInInitializerError in TestCase constructor kills surefire without letting any log * [SUREFIRE-37] - System properties not working during forking [surefire-testng branch, patch attached] * [SUREFIRE-40] - memory leak in junit runner * [SUREFIRE-35] - refine use of assertion enablement * [MSUREFIRE-57] - Forking documentation improvement to help with class loader constrainst issues * [MSUREFIRE-59] - JUnitBattery dies when TestSuite has an anonymous inner class * [MSUREFIRE-62] - forkMode=pertest shows Results: line after every battery, not at the end. * [MSUREFIRE-63] - Surefire temporary files should be put in target rather than in the main project directory * [MSUREFIRE-65] - Surefire causes OOM * [MSUREFIRE-72] - [surefire-testng] SurefireReportMojo.executeReport() throws a java.lang.NumberFormatException * [MSUREFIRE-73] - systemClassLoader.getResource returns null * [MSUREFIRE-74] - IsolatedClassloader.getResources returns duplicated results * [MSUREFIRE-80] - systemProperties and NPE * [MSUREFIRE-86] - Surefire forking doesn't work on Java 1.3 * [MSUREFIRE-88] - Surefire fork fails under windows when command has several quotes * [MSUREFIRE-93] - maven-surefire-plugin:2.2-SNAPSHOT fails with invalid option -ea when forking to a JDK 1.4 * [MSUREFIRE-94] - settting System property basedir is evil. * [MSUREFIRE-95] - java.lang.NoClassDefFoundError: org/apache/maven/surefire/util/NestedCheckedException * [MSUREFIRE-96] - Sometimes xml report has no time atribute in testcase element * [MSUREFIRE-97] - TestNG tests are not executed if invoked by */*Test.java naming pattern * [MSUREFIRE-99] - TestNG tests that cause commons-logging to load fail * [MSUREFIRE-100] - IllegalAccessError with a dynamic proxy * [MSUREFIRE-101] - Surefire is giving classloader preferences to main sources before test sources * [MSUREFIRE-102] - Prevent XML parser problems by changing default forkMode and childDelegation settings * [MSUREFIRE-104] - classpath line is too long in fork mode * [MSUREFIRE-56] - The pertest option for forking mode should be renamed more appropriately * [MSUREFIRE-71] - System properties are not set * [MSUREFIRE-87] - Improve error stack trace when the error comes from the user's test code * [MSUREFIRE-106] - Disabling xml report generation * [MSUREFIRE-23] - Support TestNG - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Cobertura Plugin 2.0
The Mojo team is pleased to announce the release of the Clirr Plugin for Maven, version 2.0. http://mojo.codehaus.org/clirr-maven-plugin You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdclirr-maven-plugin/artifactId version2.0/version /plugin This is the first release of the plugin for Maven 2. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
