[ANN] Maven Clean Plugin 2.3 and Shared File Management 1.2.1 released
The Maven team is pleased to announce the release of the Maven Clean Plugin, version 2.3 This plugin is used to delete artifacts to provide a clean build. http://maven.apache.org/plugins/maven-clean-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-clean-plugin/artifactId version2.3/version /plugin Release Notes - Maven 2.x Clean Plugin - Version 2.3 ** Sub-task * [MCLEAN-35] - Upgrade plexus-utils to a new version ** Bug * [MCLEAN-28] - maven-clean-plugin doesn't delete directories with symlinks in them * [MCLEAN-29] - Maven clean plugin doesn't filter resources from exclude list * [MCLEAN-31] - Always resolve relative path against the project's base directory * [MCLEAN-34] - NPE when forcing delete of directory * [MCLEAN-36] - filesets with an absolute path directory are ignored when !project.isExecutionRoot() ** Improvement * [MCLEAN-37] - Make verbose mode default to Maven's global debug mode ** New Feature * [MCLEAN-33] - Cannot Supress Default clean while still cleaning Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Dependency Plugin 2.1 and Maven Dependency Analyzer 1.1 released
The Maven team is pleased to announce the release of the Maven Dependency Plugin, version 2.1 This plugin is used to copy and unpack artifacts and dependencies. It also provides visualization and optimization tools for your project dependencies. http://maven.apache.org/plugins/maven-dependency-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.1/version /plugin Release Notes - Maven 2.x Dependency Plugin - Version 2.1 ** Bug * [MDEP-150] - Indeterministic artifact ordering can cause bogus warnings * [MDEP-180] - Copy-dependencies useRepositoryLayout doesn't match with maven layout * [MDEP-181] - useRepositoryLayout does not create proper repository layout * [MDEP-183] - Unpack goal cannot unpack sar files. ** Improvement * [MDEP-148] - Use Set.contains() rather than manual iteration to check for containment of class in artifact * [MDEP-151] - Use File(URI) for converting from URI to File * [MDEP-157] - Unpack xxxto yyy space ** New Feature * [MDEP-178] - Create a goal to download single artifact transitively Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven surefir report problem
I executed mvn test
[INFO] Surefire report directory
org.apache.maven.surefire.booter.SurefireExecutionException:
DoubleArrayQueueTest (wrong name: a/b/c/DoubleArrayQueueTest; nested
exception is java.lang.NoClassDefFoundError: DoubleArrayQueueTest (wrong
name:a/b/c/DoubleArrayQueueTest)
java.lang.NoClassDefFoundError: DoubleArrayQueueTest (wrong name: )
at java.lang.ClassLoader.defineClass1(Native Method)
In pom.xml
testClassesDirectory${TOPDIR}/a/b/c/test/testClassesDirectory
testSourceDirectory${TOPDIR}/${JAVA_CLASSES_SRC}/a/b/c/test/testSourc
eDirectory
Why this error
Am I wrong some where ?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
YAPII
Hi,
there are two subtle differences between Maven 2.x and 3.x regarding POM
interpolation I would like to discuss.
a) Ordering of Interpolation Sources
According to section 6.1 of the POM spec for Maven 3.x, the precedence
of interpolation sources is:
1. Maven Props
2. System Props
3. POM Props
4. Environment Props
In particular, system properties dominate POM values, i.e. mvn package
-Dproject.version=0.1 will override the project version as given in the
POM. This is different compared to Maven 2.x where model values can't be
overriden by system properties.
As far as I understand 3.x, the reasoning for the above ordering is that
POM Props include both reflective data from the model and the values
from the properties section (which, I agree, should be dominated by
system props).
IMHO, there should be no way to override model values to ensure a
reliable degree of independence from the environment. Hence I suggest
the handle model values and the properties section as independent
interpolation sources, i.e.
1. Maven Props (e.g. basedir)
2. Model Values
3. System Props
4. properties section
5. Environment Props
b) Resolution of Expressions
Consider this POM snippet:
properties
project.propA/project.prop
propB/prop
fooC/foo
/properties
name${project.prop} - ${prop} - ${foo}/name
If there was a Maven certified developer, a nice question for his exam
could be What is the effective value of the name element?.
Well, in Maven 2.x it's B - B - C. In Maven 3.x, it's A - B - C.
The first B in the Maven 2.x answer results from the interpolator
stripping the project.|pom. prefix from project.prop when querying
the properties section.
IMHO, here is Maven 3.x making a nicer job. Nice here means more
intuitive and more consistent. With consistent I refer to the behavior
of the PluginParameterExpressionEvaluator that does not strip any
prefixes from expressions when resolving them from the properties
section.
If we agree that the current Maven 2.x way to handle an expression that
is prefixed with project.|pom. but doesn't match a model value is odd,
can we change/fix this behavior for Maven 2.1.x and even Maven 2.0.x?
Benjamin
P.S.: For those that sill wonder what YAPII means: Yet Another POM
Interpolation Issue. Sorry, but I was in strange mood.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven surefir report problem
i dont think surefire understands test source directory outside of its
project, regard less how you configure it.
-D
On Sat, Jan 10, 2009 at 5:24 AM, Kumari, Shailja
shailja.kum...@deshaw.com wrote:
I executed mvn test
[INFO] Surefire report directory
org.apache.maven.surefire.booter.SurefireExecutionException:
DoubleArrayQueueTest (wrong name: a/b/c/DoubleArrayQueueTest; nested
exception is java.lang.NoClassDefFoundError: DoubleArrayQueueTest (wrong
name:a/b/c/DoubleArrayQueueTest)
java.lang.NoClassDefFoundError: DoubleArrayQueueTest (wrong name: )
at java.lang.ClassLoader.defineClass1(Native Method)
In pom.xml
testClassesDirectory${TOPDIR}/a/b/c/test/testClassesDirectory
testSourceDirectory${TOPDIR}/${JAVA_CLASSES_SRC}/a/b/c/test/testSourc
eDirectory
Why this error
Am I wrong some where ?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Stylus Skin version 1.1
Vincent Siveton wrote: Hi Dennis, 2009/1/7 Dennis Lundberg denn...@apache.org: Is it really a chicken and egg issue? I think so. Imagine this use case: 0. clean repo 1. svn co tag/maven-stylus-skin-1.1 with the site.xml using 1.1 2. mvn -o site will fail: no download of maven-stylus-skin artifact. Yes, if building the site is part of the release then we have a problem. But if it's not, then you should be able to do the release first and build the site afterwards. I think it depends on what is done during the release process. If the release process consists of packaging a jar and deploying it to a repo. Will the version number in the site.xml file be resolved? Or will it be resolved when the site of the artifact is built? At present we don't build/deploy the site at release time, so it should be possible to set the skin version in site.xml to the upcoming artifact version. Not a SNAPSHOT version though. In this case we would set it to 1.1. I could always fix the tag and redeploy the staging site. That would be good. Cheers, Vincent Vincent Siveton wrote: Hi, We need to make a release with no snapshot, and I don't think we can do what's you propose. It is an chicken and egg issue... similar to with the maven-plugin-plugin [1]. I think we could live with it. Cheers, Vincent [1] https://svn.apache.org/repos/asf/maven/plugin-tools/tags/maven-plugin-tools-2.4.3/maven-plugin-plugin/pom.xml 2009/1/7 Dennis Lundberg denn...@apache.org: That's because https://svn.apache.org/repos/asf/maven/skins/trunk/maven-stylus-skin/src/site/site.xml is still using the 1.0.1 version of the skin. It should be using 1.1. I don't know if it's possible to change the version of the skin in site.xml to the version-to-be-released prior to the release itself. But if that work's it should be the preferred way to do it. Brian E. Fox wrote: Actually the stylus skin below doesn't have the privacy policy, which is weird cause it's working for m.a.o -Original Message- From: Vincent Siveton [mailto:vincent.sive...@gmail.com] Sent: Wednesday, January 07, 2009 11:06 AM To: Maven Developers List Subject: [VOTE] Release Maven Stylus Skin version 1.1 Hi, We solved 1 issue, to comply with the board resolution about Privacy policy page. http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430styleNa me=Htmlversion=14872 There are no issue left in JIRA. Staging repo: http://people.apache.org/~vsiveton/staging-repo/ Staging site (need to sync): http://maven.apache.org/skins/maven-stylus-skin-1.1 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Vincent - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: How do I add all the jars in a directory in junit test exeicution classpath
Thanks Wendy for the response.. I'll follow it in users list.. Regards, Mandar Nimbkar Patni Computer Systems Ltd SDF VII, Unit 20, SEEPZ, Andheri (E) Mumbai 400096. Tel : 91 22 28291454 x5844 Fax : 91 22 28280911 Link: 601 7141 -Original Message- From: Wendy Smoak [mailto:wsm...@gmail.com] Sent: Friday, January 09, 2009 8:07 PM To: Maven Developers List Subject: Re: How do I add all the jars in a directory in junit test exeicution classpath On Fri, Jan 9, 2009 at 6:48 AM, Nimbkar, Mandar mandar.nimb...@patni.com wrote: I have few junit test cases to be executed using Maven build. ... I replied on the users list and copied you. Please follow up on that list instead; this one is for discussing the development of Maven itself. Thanks! -- Wendy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netad...@patni.com and delete this mail. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
