+1
Regards,
Hervé
Le mercredi 24 septembre 2014 15:23:12 Mirko Friedenhagen a écrit :
Hi,
we solved 9 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212version=20
323
* [MCHANGES-343] Update maven-reporting-impl to 2.3
* [MCHANGES-342] Removed dependency
My +1, would be great to geht 2.10 with this patch.
Regards
Mirko
--
Sent from my mobile
On Sep 26, 2014 11:09 PM, Michael Osipov micha...@apache.org wrote:
Am 2014-09-26 um 21:28 schrieb Robert Scholte:
Hi Michael,
I'm missing action on the wise words from Hervé.
Are you planning to add
I have created
http://jira.codehaus.org/browse/MSHARED-350
http://jira.codehaus.org/browse/PLXUTILS-165
to deal with this. I'm convinced there is only one right thing (tm) to
do, so I will do that :)
Kristian
2014-09-26 22:26 GMT+02:00 Kristian Rosenvold kristian.rosenv...@gmail.com:
I now
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=20644
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MJAVADOC%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
Staging
Hi,
checked sha1 Ok. Site looks Ok.
Tested with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.1, 3.2.2, 3.2.3
mvn -Prun-its clean verify
without any issue...
So +1 from me.
Kind regards
Karl-Heinz Marbaise
On 9/27/14 4:34 PM, Michael Osipov wrote:
Hi,
We solved 3 issues:
We moved core to 1.6 some time ago. Time to move everything else as well ?
Kristian (Who's ready to say 1.7 but we stop by 1.6 first :)
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
+1
On Sep 27, 2014, at 1:23 PM, Kristian Rosenvold kristian.rosenv...@zenior.no
wrote:
We moved core to 1.6 some time ago. Time to move everything else as well ?
Kristian (Who's ready to say 1.7 but we stop by 1.6 first :)
We moved core to 1.6 some time ago. Time to move everything else as well ?
Kristian (Who's ready to say 1.7 but we stop by 1.6 first :)
I would favor the move to Java 1.7 if we make strong use of NIO2 for file
operations. A lot of pain should go away.
Michael
Agree. 1.7 makes more sense at this point.
On September 27, 2014 1:41:31 PM EDT, Michael Osipov 1983-01...@gmx.net wrote:
We moved core to 1.6 some time ago. Time to move everything else as
well ?
Kristian (Who's ready to say 1.7 but we stop by 1.6 first :)
I would favor the move to Java
Let's use the [discuss] thread constructively then; do we call a
[VOTE] to move *everything* to 1.7 ? I think we are ready to move to
1.6 without actually having a vote, so if you for some reason oppose
the move to 1.6 please say so in the discuss thread or I will simply
conclude that we move
Hi Kristian,
On 9/27/14 7:23 PM, Kristian Rosenvold wrote:
We moved core to 1.6 some time ago.
As far as i know starting with Maven 3.2.1...was the first one...
Time to move everything else as well ?
We have at the moment a large number of plugins which have minimum Maven
2.2.1 (JDK
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/36
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
1.6 is fine by me. Working actively with a customer using IBM's JDK 1.6,
which is still supported by IBM, will make me vote -1 on a move to 1.7
currently.
/Anders
On Sat, Sep 27, 2014 at 8:01 PM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
Hi Kristian,
On 9/27/14 7:23 PM, Kristian Rosenvold
Karl; I think you are mixing concerns somewhat -making things a little
more complex than they need to be.
I would propose that most people using 2.2.1 are not doing so due to
the java version, but simply because they have not ported their build
to 3.X due to a bag of different constraints, java
Michael; we are heavily into jdk7 file-system related features, most
of which is covered by feature detection/jdk detection. Plexus
requires 1.7 to build but still supports 1.5. I'll split a bottle of
champagne the day we can drop 1.5/1.6 support from plexus and various
utility projects with
Hi Kristian,
Karl; I think you are mixing concerns somewhat -making things a little
more complex than they need to be.
I think it is not that simple...
I would propose that most people using 2.2.1 are not doing so due to
the java version,
but simply because they have not ported their
Yeah Karl, I think you're right :) Things aren't always that easy so
we tend to err in favor of being conservative, which I think is ok.
Personally I think all java versions 1.8 are a drag right now. So I
think we call a straight vote for 1.6 for everything. Although not
very ambitious, it moves
The vote has passed:
+1 binding by Hervé, Karl-Heinz and Robert
+1 non-binding by me :-)
I will proceed tomorrow with releasing.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
Hi,
I wonder if this does what we want to achieve: forcing projects using
maven-shared-utils to be executed with at least Maven 2.2.1.
Right now it is just the preferred version, no problem if the project
itself redefines it to 2.0.9 for instance.
Is that a problem or should we say [2.2.1,)
On 28 Sep 2014, at 7:27, Kristian Rosenvold wrote:
But I think coupling java version - maven version like you're doing
is basically flawed; for most users this is not about java versions.
With this - I think further promotion and support of the
maven-toolchains-plugin might be handy. The JVM
20 matches
Mail list logo
