Am 2014-02-22 00:58, schrieb Dennis Lundberg:
Hi,
If anyone wants to add something to the next release of the Checkstyle
plugin, now would be a good time to do it, as I intend to make a
release next week. If you need more time to squeeze something in, just
let me know.
Dennis,
I have now
I've staged 2.5 of the maven-release component. However, the
documentation staging process is failing.
mvn -Preporting site site:stage
does not write into the ~/maven-sites directory where the scm plugin expects it.
Could some kind soul either checkout the tag and patch this up and
stage
I think the parts about which JRE to depend upon deserves its own
document, because it is something that affects our users much more
that which version numbers we use. The same goes for which version of
Maven Core a plugin/component can require. That being said, your
proposal is a great starting
Hi,
maven-release is a component that provides the maven-release-manager
and the maven-release-plugin.
This release integrates version 1.9 of Maven SCM, which addresses a
number of problems with git.
We resolved 10 issues:
** Bug
* [MRELEASE-166] - release:prepare should always check for
+1 - binding.
On Sun, Feb 23, 2014 at 9:49 AM, Benson Margulies bimargul...@gmail.com wrote:
Hi,
maven-release is a component that provides the maven-release-manager
and the maven-release-plugin.
This release integrates version 1.9 of Maven SCM, which addresses a
number of problems with
Never mind, I found the shell script left behind by the last person
who did this. I
On Sun, Feb 23, 2014 at 7:38 AM, Benson Margulies bimargul...@gmail.com wrote:
I've staged 2.5 of the maven-release component. However, the
documentation staging process is failing.
mvn -Preporting site
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/34
SUREFIRE [1048] Surefire does not use the total amount of threads specif...
...ied by threadCount
This is optimization of thread counts limited to the real number of
parallel JUnit
I guess we need to clear up what I mean by a maintenance line...
We *can/may* cut releases on maintenance / security line... Does not mean
we *will* more that for non-security/maintenance lines there is ZERO
possibility of us cutting a release...
On Sunday, 23 February 2014, Dennis Lundberg
I didn't yet tested it. Is it supposed to support git 1.9? I had some some
feedback that it didn't work but for now I didn't investigate. I'm not sure if
something was reported about it. —
Sent from Mailbox for iPhone
On Sun, Feb 23, 2014 at 3:50 PM, Benson Margulies bimargul...@gmail.com
Maven scm 1.9 does not necessarily correspond to git 1.9. You would need to
look at those release notes.
On February 23, 2014 10:56:04 AM EST, Arnaud Héritier aherit...@gmail.com
wrote:
I didn't yet tested it. Is it supposed to support git 1.9? I had some
some feedback that it didn't work but
I propose to make releases of our parent stack that are suitable for
components and plugins that are making the leap to Java 1.6 and Maven
3 as their base requirements.
What do people think is the right approach in terms of what stays on
trunk and what goes on a branch, and whether to do anything
Keep in mind that maven 3.0-3.1.x are still java 1.5 and we haven't put a
version policy in place.
Personally speaking I'm fine with plugins requiring java 1.6 and maven
3.2.1 as a minimum, but I'd rather see 3.3.x get some legs first and I
suspect we'll have a few 3.2.x releases as we have EOL'd
I would have expected our first step would be to set source and target
to 1.6, and move the Maven core dependencies to 3.0.x. I don't see why
the fact that the core was compiled with target=1.5 would have any
impact here.
I'd like to avoid a disorganized process of individual plugins and
For this thread, I'd be content to get a plan for how to manage the
poms to reflect the EOL of 2.x. The actual content of those poms can
argued over by committing an initial proposal.
On Sun, Feb 23, 2014 at 1:50 PM, Benson Margulies bimargul...@gmail.com wrote:
I would have expected our first
Well let's get the maven dep up to at least 3.0.4.
Let's give users an announce that we are moving to only checking java 1.5
compat via animal sniffer and that we will be building plugins with 1.6 or
1.7
On Sunday, 23 February 2014, Benson Margulies bimargul...@gmail.com wrote:
For this
Stephen, can I possibly get you to respond to the the questions about branches
(or not) and version numbers for the POM's?
On February 23, 2014 2:00:24 PM EST, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Well let's get the maven dep up to at least 3.0.4.
Let's give users an
Am 2014-02-23 19:06, schrieb Benson Margulies:
I propose to make releases of our parent stack that are suitable for
components and plugins that are making the leap to Java 1.6 and Maven
3 as their base requirements.
What do people think is the right approach in terms of what stays on
trunk and
On Sunday, 23 February 2014, Michael Osipov micha...@apache.org wrote:
Am 2014-02-23 19:06, schrieb Benson Margulies:
I propose to make releases of our parent stack that are suitable for
components and plugins that are making the leap to Java 1.6 and Maven
3 as their base requirements.
Am 2014-02-01 11:20, schrieb Hervé BOUTEMY:
after m-scm-publish-p 1.0 is released, I intend to release ASF parent pom
Then every Maven parent poms
please have a look at these if you want to be sure your favorite plugin
version + configuration, or you position, is correct
Hervé,
did you check
On 24 Feb 2014, at 5:12, Benson Margulies wrote:
Maven scm 1.9 does not necessarily correspond to git 1.9. You would need to
look at those release notes.
Git 1.8.x changed the output of the human readable 'git status', scm 1.9 ( and
quite a few versions earlier ) switched to using the git
Am 2014-02-23 21:20, schrieb Stephen Connolly:
On Sunday, 23 February 2014, Michael Osipov micha...@apache.org wrote:
Am 2014-02-23 19:06, schrieb Benson Margulies:
I propose to make releases of our parent stack that are suitable for
components and plugins that are making the leap to Java
Hi folks,
did anyone already check
http://maven.apache.org/docs/3.2.1/release-notes.html?
The link See complete release notes for all versions links to
http://maven.apache.org/ and is missing a period. Release notes not
available.
http://maven.apache.org/ref/3.2.1/ is a 404.
I forgot:
System Requirements: JDK 1.5 or above
Depends on the Mavn version.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I'm still on ASF parent: Maven parent POMs will be later
Regards,
Hervé
Le dimanche 23 février 2014 21:25:35 Michael Osipov a écrit :
Am 2014-02-01 11:20, schrieb Hervé BOUTEMY:
after m-scm-publish-p 1.0 is released, I intend to release ASF parent pom
Then every Maven parent poms
I haven't announced it yet because trying to make all the pertinent changes to
the site is tedious. Take a look at the end of the day.
On Feb 23, 2014, at 12:52 PM, Michael Osipov micha...@apache.org wrote:
Hi folks,
did anyone already check
So, my 'maven 3' parent project comes after this, in case anyone wonders.
On Sun, Feb 23, 2014 at 3:55 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
I'm still on ASF parent: Maven parent POMs will be later
Regards,
Hervé
Le dimanche 23 février 2014 21:25:35 Michael Osipov a écrit :
Am
I think that Michael might be over-reading my intentions. I am not
trying to start a short-term avalanche of moving components to require
3.0.5. My idea is:
1. We release parents that set up the 3.0.5 dependencies. Call that version Q.
2. Any maintainer who feels inclined to release a
On Feb 23, 2014, at 12:38 PM, Michael Osipov micha...@apache.org wrote:
Just had a hard time to find this information on the (front) page.
I think a mere: 2014-02-18 End of Life EoL notes, announce is not enough. I
would have expected something like this on the front page:
Looking for
On 24 Feb 2014, at 2:48 am, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
I guess we need to clear up what I mean by a maintenance line...
We *can/may* cut releases on maintenance / security line... Does not mean
we *will* more that for non-security/maintenance lines there is ZERO
MGso in your instance why does'nt maven-scm-publish to ~/maven-sites ??
Date: Sun, 23 Feb 2014 09:52:12 -0500
Subject: Re: Maven-release-plugin and scm site publication: need help
From: bimargul...@gmail.com
To: dev@maven.apache.org
Never mind, I found the shell script left behind by
I just published the site with the ref docs and the updated release notes. I
don't know how long it takes to sync but you can check anything in SVN. I'll
leave them there until the morning, if you want to make any changes feel free.
If there are no issues I'll send out the announcement in the
If you look at the current parent poms, they generally set up so that
site:stage writes to ~/maven-sites/..., so that, later, the scm
publish plugin can read it from there.
On Sun, Feb 23, 2014 at 8:58 PM, Martin Gainty mgai...@hotmail.com wrote:
MGso in your instance why does'nt
Le 23 févr. 2014 21:20, Stephen Connolly stephen.alan.conno...@gmail.com
a écrit :
On Sunday, 23 February 2014, Michael Osipov micha...@apache.org wrote:
Am 2014-02-23 19:06, schrieb Benson Margulies:
I propose to make releases of our parent stack that are suitable for
components and
+1 (possibly set the deps to 3.0.4 instead, and not 3.0.5)
I don't think we need to branch the parent poms. That will just create
unnecessary complexity. As you pointed out, plugins can continue to use the
Q-1 version of the parent if the want to go with 2.x-compat (and
add/override plugin
I had a look at the Download page and the JDK requirements incorrectly
states 1.5. It should be 1.6 for Maven 3.2.x.
/Anders
On Mon, Feb 24, 2014 at 5:53 AM, Jason van Zyl ja...@takari.io wrote:
I just published the site with the ref docs and the updated release notes.
I don't know how long
35 matches
Mail list logo
