Re: svn commit: r1576206 - /maven/pom/trunk/maven/pom.xml
I'm going to release maven parent POM in a few days please everybody check that everything they want in this version is ok Regards, Hervé Le mardi 11 mars 2014 07:36:20 hbout...@apache.org a écrit : Author: hboutemy Date: Tue Mar 11 07:36:19 2014 New Revision: 1576206 URL: http://svn.apache.org/r1576206 Log: use released ASF parent 14 Modified: maven/pom/trunk/maven/pom.xml Modified: maven/pom/trunk/maven/pom.xml URL: http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?rev=1576206r1=1 576205r2=1576206view=diff === === --- maven/pom/trunk/maven/pom.xml (original) +++ maven/pom/trunk/maven/pom.xml Tue Mar 11 07:36:19 2014 @@ -26,7 +26,7 @@ under the License. parent groupIdorg.apache/groupId artifactIdapache/artifactId -version14-SNAPSHOT/version +version14/version relativePath../asf/pom.xml/relativePath /parent - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
+1 from me I have verified that the problems Karl Heinz had with th ITs were fixed by specifying the correct version in the POM of the IT. So the error was not in the main plugin code, but rather in the configuration of the IT. On Sat, Mar 8, 2014 at 11:49 PM, Dennis Lundberg denn...@apache.org wrote: Hi, We solved 15 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=19723 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1010/ https://repository.apache.org/content/repositories/maven-1010/org/apache/maven/plugins/maven-checkstyle-plugin/2.12/maven-checkstyle-plugin-2.12-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.12-source-release.zip sha1: 1d2c6435e214daa9bedce6d32871a8b7ac3f Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote is open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: JDK 8 Build 126 JDK 7 Update 60 build 04 are available on java.net
Hi Robert, Thanks for the update! Rgds,Rory On 10/03/2014 21:07, Robert Scholte wrote: Hi Rory, today I've released Maven Filtering 1.2, which doesn't suffer from https://bugs.openjdk.java.net/browse/JDK-8015656 anymore. Next step will be upgrading the projects which depend on Maven Filtering. regards, Robert Op Sun, 02 Feb 2014 17:07:26 +0100 schreef Robert Scholte rfscho...@apache.org: Hi Rory, I can confirm that JDK-8031572 is now fixed. I found at least one project which suffers from https://bugs.openjdk.java.net/browse/JDK-8015656, which I could fix with https://jira.codehaus.org/browse/MSHARED-319 (maven-filtering). According to http://mvnrepository.com/artifact/org.apache.maven.shared/maven-filtering/1.0 http://mvnrepository.com/artifact/org.apache.maven.shared/maven-filtering/1.1 this artifact is mainly used by a small amount of maven-plugins, so the change of behavior of the JDK shouldn't have a huge impact. We can plan a release for this component, so plugins only have to upgrade their dependency. best regards, Robert Scholte Op Fri, 31 Jan 2014 10:15:26 +0100 schreef Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com: Hi Robert,Kristian, JDK 8 Build b126 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b04 Early Access Build is also available for download https://jdk7.java.net/download.html test. Please log all show stopper issues as soon as possible. Thanks for your support, Rory - 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 -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [gsoc] Is there a Maven opportunity for Google Summer of Code students?
On Mon, Mar 10, 2014 at 7:06 PM, Jason van Zyl ja...@takari.io wrote: Is there a candidate? Why don't you ask them what they are interested in, if there is one. Or do you have to come up with a project to attract someone? yes, I got in touch with a student interested in GSoC. It's hard for somebody very new to the project to find something that is reasonable to do, and big enough for a summer project. We were looking at the most voted issues in jira and pretty much all of them require a new pom model. On Mar 10, 2014, at 1:49 PM, Carlos Sanchez car...@apache.org wrote: On Mon, Mar 10, 2014 at 2:45 PM, Benson Margulies bimargul...@gmail.com wrote: Realistically, look to plugins more than the core, if you ask me. There's the new not-quite-consumer-pom which might have a subtask. Or pick any of the common plugins and see what's out here. I thought about that, but for GSoC it needs to be something at the ASF, and not Codehaus And is there any new feature big enough to make it as a summer project? would need to be almost a new plugin On Mon, Mar 10, 2014 at 9:42 AM, Carlos Sanchez car...@apache.org wrote: There's a student interesting on doing the GSoC with the Maven project so I was trying to figure out a meaningful project, not to small, not too large, focusing on the top voted issues in jira. But most of them are related to POM and profiles new features/improvements which are not clearly defined/agreed on yet. Anyone has other suggestions? Cheers - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham
Re: svn commit: r1576206 - /maven/pom/trunk/maven/pom.xml
The current maven-release-plugin? On Tue, Mar 11, 2014 at 3:38 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I'm going to release maven parent POM in a few days please everybody check that everything they want in this version is ok Regards, Hervé Le mardi 11 mars 2014 07:36:20 hbout...@apache.org a écrit : Author: hboutemy Date: Tue Mar 11 07:36:19 2014 New Revision: 1576206 URL: http://svn.apache.org/r1576206 Log: use released ASF parent 14 Modified: maven/pom/trunk/maven/pom.xml Modified: maven/pom/trunk/maven/pom.xml URL: http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?rev=1576206r1=1 576205r2=1576206view=diff === === --- maven/pom/trunk/maven/pom.xml (original) +++ maven/pom/trunk/maven/pom.xml Tue Mar 11 07:36:19 2014 @@ -26,7 +26,7 @@ under the License. parent groupIdorg.apache/groupId artifactIdapache/artifactId -version14-SNAPSHOT/version +version14/version relativePath../asf/pom.xml/relativePath /parent - 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: MRELEASE-431
Hi Robert,
+1 - given my current experimental implementation, I am convinced that
declaring the VersionPolicy as component is the way to go, so I can
even inject whatever I need in order to implement my policy to
increase versions :)
Thanks,
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
On Mon, Mar 10, 2014 at 7:09 PM, Robert Scholte rfscho...@apache.org wrote:
Hi Simone,
I still have to find a solution for the VersionParseException which can be
thrown with the current implementation of DefaultVersionInfo. I probably
have to add it to both methods of VersionPolicy
Your custom implementation will look something like:
@Component( role = VersionPolicy.class, hint = tripodi )
public class TripodiVersionPolicy implements VersionPolicy {
// your stuff
}
The plugin will get parameters like projectVersionPolicyId and/or
dependencyVersionPolicyId.
At least, that's my idea right now to split it up per type. This way
implementations can stay as clean as possible.
Robert
Op Mon, 10 Mar 2014 14:17:43 +0100 schreef Simone Tripodi
simonetrip...@apache.org:
Hi again Robert,
new APIs look reasonable and easily extensible to me, thanks for putting
effort on that!
I maybe missed something but I didn't notice how they are integrated in
the
core module...
TIA all the best!
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
On Sat, Mar 8, 2014 at 3:17 PM, Robert Scholte rfscho...@apache.org
wrote:
Hi Simone,
I've added a new module for Maven release policies including my idea of
how the API should look like.
Although one of my suggestions to specify this as an implementation in
the
plugin configuration, I now prefer to use it as a component. Downside is
that you can't use a pojo, you'll need to add Plexus annotations and
generate the descriptor. However, now you can inject other components
a.k.a
requirements. Since this might become quite complicated, injection is
probably the preferred way.
I probably need more info in the PolicyRequest to support the current
behavior, but this is just a start.
This should be a good start for you too. Let me know if this will work
with your requirements.
best,
Robert
Op Fri, 28 Feb 2014 17:06:05 +0100 schreef Simone Tripodi
simonetrip...@apache.org:
Hi Rob! :)
indeed it has been a very long while, so sorry for that :(
OK I understand your PoV, count on me if you want to co-operate - I need
that feature as well in order to make the release-plugin able to
generate
that version using a tool, but without exposing such APIs that allow me
plugging different versioning systems, I cannot do it :)
Many thanks in advance and have a nice weekend!
All the best!
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
On Fri, Feb 28, 2014 at 4:17 PM, Robert Scholte rfscho...@apache.org
wrote:
Hi Simone,
It's been a while, so I'll need to have another look at this.
At first glance I'm not yet happy with the suggested API.
I'd need to make some time so come with a final solution.
Robert
Op Fri, 28 Feb 2014 14:56:35 +0100 schreef Simone Tripodi
simonetrip...@apache.org:
Hi all mates,
I am in a phase where I could get benefit of that feature as well
(and,
since I am still in the committer list, I can provide some help here)
so I
would like to push it :P
@Robert: before merging the contribution we received in JIRA, I'd
kindly
ask if you had a better idea if new API has to be in
the maven-release-manager or in a separate module.
Many thanks in advance, all the best!
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
-
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
-
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: Convert everything to Git
Hi all,
Wondering, wouldn't maven-release be a good next candidate for a Git
migration?
I'm currently working locally with the maven-release github mirror, but
just had to checkout svn trunk to have a look at MRELEASE-431's robert's
current proposal (yes, I could've also git svn'ed it).
Cheers
2014-02-20 23:13 GMT+01:00 Fred Cooke fred.co...@gmail.com:
+extension
+groupIdorg.apache.maven.wagon/groupId
+artifactIdwagon-ssh-external/artifactId
+version${extension.version.wagon}/version
+/extension
It was SSH settings that were not being respected. Things like ports and
ssh hosts vs DNS lookups, etc.
There were other issues with multi-module-parents vs ONLY-parents vs
aggregator poms. MRELEASE-814
https://jira.codehaus.org/browse/MRELEASE-812
https://jira.codehaus.org/browse/MRELEASE-815
Other issues were m-site-p in terms of variables and inheritance and
uploads, which work OK for general generation.
IIRC the results of these bugs was that I had a lot of unwanted duplication
of config that I couldn't inherit because it got mal-processed. Nothing
worse, but duplication is evil and makes baby Jesus and other equally
ordinary small children cry.
Then there are things that are just generally broken and don't affect git
worse than other SCMs
!-- scmCommentPrefixReleasing ${project.artifactId}
version ${project.version} /scmCommentPrefix -- !-- Space trimmed and
version snapshot, yuck. --
But I'm OT now.
Fred.
On Fri, Feb 21, 2014 at 10:58 AM, Mark Derricutt m...@talios.com wrote:
On 21 Feb 2014, at 10:27, Jason van Zyl wrote:
I only release core and that works fine which begs the question: do we
want to normalize our repository structure to simplify the tooling
requirements. What exactly doesn't work? Trying to release a single
thing
out of a repository containing many things?
A stock m-r-p config will break using the latest releases of git ( due to
depending on an old version of the -scm- artefacts ) which I've mentioned
before, and I believe there are commits awaiting release to resolve this.
m-r-p also _really_ likes to release from the root directory of a
repository, so doing independent releases from sub directories/modules is
difficult ( there is a setting which lets this work, but that's just
unpleasant ) - but due to git's tagging/branching being repository wide
just releasing an individual module really is unpleasant.
Basically, if modules have a constant release cadence/version numbering
scheme, they can release together in a single repo, otherwise they should
be separate. This however I don't see as a problem with git tooling in
maven - just good practise.
Mark
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor ! nbsp;!
Re: maven-assembly-plugin / Maven default folder layout
Hi Michael, You forgot: src/site. No, cause it's already part of the default folder layout. Kind Regards Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Apache Maven PMD Plugin version 3.1
Hi, We solved 10 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140styleName=Htmlversion=19131 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11140status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1011/ https://repository.apache.org/content/repositories/maven-1011/org/apache/maven/plugins/maven-pmd-plugin/3.1/maven-pmd-plugin-3.1-source-release.zip Source release checksum(s): maven-pmd-plugin-3.1-source-release.zip sha1: 1a9d25aaf8db9e9e5cdecc5ca34757e22661f246 Staging site: http://maven.apache.org/plugins-archives/maven-pmd-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote is open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven PMD Plugin version 3.1
+1, but why not upgrade to 5.1 (MPMD-182) first? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin / Maven default folder layout
Hi, On 3/9/14 9:02 PM, Karl Heinz Marbaise wrote: So based on the discussion could we go with the following: /src/main * are files required during compile time (production) /src/test * are files required during test time (unit testing; based on naming schema we could also have integration tests here) /src/it * are files required during integration tests (primarily for plugins) /src/assembly * for assembly descriptors and appropriate filter property files. The /src/it/ should be added to the default folder layout page. What i missed: What is about src/main/config ? I would suggest to remove it from the default folder layout, cause i can't remember a case where it is used ? Someone else? Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
Hi Dennis, +1 from me I have verified that the problems Karl Heinz had with th ITs were fixed by specifying the correct version in the POM of the IT. So the error was not in the main plugin code, but rather in the configuration of the IT. Yes i can give now the +1 cause it's not really in the code of the pluginas you wrote... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Convert everything to Git
no problem for me on this one
if someone creates a new git repository, it would be nice to create a Maven
root git repository with submodules definition to every actual git module
Regards,
Hervé
Le mardi 11 mars 2014 16:34:26 Baptiste Mathus a écrit :
Hi all,
Wondering, wouldn't maven-release be a good next candidate for a Git
migration?
I'm currently working locally with the maven-release github mirror, but
just had to checkout svn trunk to have a look at MRELEASE-431's robert's
current proposal (yes, I could've also git svn'ed it).
Cheers
2014-02-20 23:13 GMT+01:00 Fred Cooke fred.co...@gmail.com:
+extension
+groupIdorg.apache.maven.wagon/groupId
+artifactIdwagon-ssh-external/artifactId
+version${extension.version.wagon}/version
+/extension
It was SSH settings that were not being respected. Things like ports and
ssh hosts vs DNS lookups, etc.
There were other issues with multi-module-parents vs ONLY-parents vs
aggregator poms. MRELEASE-814
https://jira.codehaus.org/browse/MRELEASE-812
https://jira.codehaus.org/browse/MRELEASE-815
Other issues were m-site-p in terms of variables and inheritance and
uploads, which work OK for general generation.
IIRC the results of these bugs was that I had a lot of unwanted
duplication
of config that I couldn't inherit because it got mal-processed. Nothing
worse, but duplication is evil and makes baby Jesus and other equally
ordinary small children cry.
Then there are things that are just generally broken and don't affect git
worse than other SCMs
!-- scmCommentPrefixReleasing ${project.artifactId}
version ${project.version} /scmCommentPrefix -- !-- Space trimmed and
version snapshot, yuck. --
But I'm OT now.
Fred.
On Fri, Feb 21, 2014 at 10:58 AM, Mark Derricutt m...@talios.com wrote:
On 21 Feb 2014, at 10:27, Jason van Zyl wrote:
I only release core and that works fine which begs the question: do we
want to normalize our repository structure to simplify the tooling
requirements. What exactly doesn't work? Trying to release a single
thing
out of a repository containing many things?
A stock m-r-p config will break using the latest releases of git ( due
to
depending on an old version of the -scm- artefacts ) which I've
mentioned
before, and I believe there are commits awaiting release to resolve
this.
m-r-p also _really_ likes to release from the root directory of a
repository, so doing independent releases from sub directories/modules
is
difficult ( there is a setting which lets this work, but that's just
unpleasant ) - but due to git's tagging/branching being repository wide
just releasing an individual module really is unpleasant.
Basically, if modules have a constant release cadence/version numbering
scheme, they can release together in a single repo, otherwise they
should
be separate. This however I don't see as a problem with git tooling in
maven - just good practise.
Mark
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor ! nbsp;!
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Maven 3.1.1 dependency downloading issues
Hi, I found that Maven 3.1.1 will try downloading the artifacts in parallel. 02:04:47 Downloading: http://mycentral/content/repositories/central/javax/inject/javax.inject/1/javax.inject-1.pom 02:04:47 Downloaded: http://mycentral/content/repositories/central/javax/inject/javax.inject/1/javax.inject-1.pom (612 B at 28.5 KB/sec) 02:04:47 [DEBUG] Using connector WagonRepositoryConnector with priority 0.0 for http://mycentral/content/repositories/plugins 02:04:47 Downloading: http://mycentral/content/repositories/plugins/javax/inject/javax.inject/1/javax.inject-1.pom 02:04:47 [DEBUG] Skipped remote update check for javax.inject:javax.inject:pom:1, already updated during this session. 02:04:47 Downloading: http://repository.jboss.org/maven2/javax/inject/javax.inject/1/javax.inject-1.pom This cause the issue, actually the first try already downloaded the pom, but Maven still trying other repository in paralle. In our CI server we cannot access repository.jboss.org. that cause the system hang until it's timeout. My questions are, l Can we configure the threads number for parallel downloading. l Why Maven 3.1.1 will try to download artifacts from repository.jboss.org, we did not define in our settings.xml and pom. Can we remove those external repositories? Thanks in advance, James
Javadoc plugin include/exclude
I just create an IT for sourceFileExcludes, and it fails. And I debugged into it; the code dilligently scans the source directories, but then does not use the resulting list files in the invocation of javadoc. It just fires up javadoc on the entire src/main/java directory. Are any of the other contributors to the javadoc plugin in a position to offer any illumination here? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1576206 - /maven/pom/trunk/maven/pom.xml
already done in http://svn.apache.org/r1575724[1] Regards, Hervé Le mardi 11 mars 2014 06:17:34 Benson Margulies a écrit : The current maven-release-plugin? On Tue, Mar 11, 2014 at 3:38 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I'm going to release maven parent POM in a few days please everybody check that everything they want in this version is ok Regards, Hervé Le mardi 11 mars 2014 07:36:20 hbout...@apache.org a écrit : Author: hboutemy Date: Tue Mar 11 07:36:19 2014 New Revision: 1576206 URL: http://svn.apache.org/r1576206 Log: use released ASF parent 14 Modified: maven/pom/trunk/maven/pom.xml Modified: maven/pom/trunk/maven/pom.xml URL: http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?rev=1576206r1 =1 576205r2=1576206view=diff === == == === --- maven/pom/trunk/maven/pom.xml (original) +++ maven/pom/trunk/maven/pom.xml Tue Mar 11 07:36:19 2014 @@ -26,7 +26,7 @@ under the License. parent groupIdorg.apache/groupId artifactIdapache/artifactId -version14-SNAPSHOT/version +version14/version relativePath../asf/pom.xml/relativePath /parent - 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 [1] http://svn.apache.org/r1575724
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12
+1 On 9 March 2014 09:49, Dennis Lundberg denn...@apache.org wrote: Hi, We solved 15 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=19723 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1010/ https://repository.apache.org/content/repositories/maven-1010/org/apache/maven/plugins/maven-checkstyle-plugin/2.12/maven-checkstyle-plugin-2.12-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.12-source-release.zip sha1: 1d2c6435e214daa9bedce6d32871a8b7ac3f Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote is open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Maven PMD Plugin version 3.1
I want this release to be Java 5 compatible. PMD 5.1 requires Java 6, even though it is not mentioned in their release notes. -- Dennis Lundberg Den 11 mar 2014 21:46 skrev Michael Osipov micha...@apache.org: +1, but why not upgrade to 5.1 (MPMD-182) first? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
