Did I object something? :-)
--
Olivier
On 6 Mar 2015 21:19, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
We are CTR not RTC
If you object to the change, veto the commit
On 6 March 2015 at 07:44, Olivier Lamy ol...@apache.org wrote:
+1
I just find the change/discussion a bit
I'll respin, but I wonder why it failed to bite me.
On Fri, Mar 6, 2015 at 2:59 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi Benson,
first the link to the release is unfortunately wrong...the correct link is:
IMO this Java version bump should be reflected in a minor Maven version
bump as opposed to a maintenance release.
Gary
On Fri, Mar 6, 2015 at 12:09 AM, Anders Hammar and...@hammar.net wrote:
Ok, the consensus is to move forward to Java7. I updated the POM and
we're
in no rush so give it a
I created MNG-5780 to track the change
I let the issue open, because I hope that we won't have to revert the commit
after someone steps in with a strong reason not to upgrade
But in 48h, if nobody votes -1 woth a strong issue, I'll close the issue and
point to the (a little bit too quick at
Hi,
If we are going to release 3.3.0 very soon, like this week or the
next, there won't be any time to start using Java 7 features in the
3.3.0 release. Therefor I would prefer to go with Java 6 for 3.3.0 and
announce, in the 3.3.0 release notes, that the 3.3.x line is the last
line that will
I already have the full jdk7 port in a branch in github, so that assumption
does not hold :)
Kristian
2015-03-06 13:50 GMT+01:00 Dennis Lundberg denn...@apache.org:
Hi,
If we are going to release 3.3.0 very soon, like this week or the
next, there won't be any time to start using Java 7
Hi Benson,
I have attached the appropriate log files to the JIRA ticket...
Kind regards
Karl Heinz Marbaise
On 3/6/15 3:22 PM, Benson Margulies wrote:
I'll respin, but I wonder why it failed to bite me.
On Fri, Mar 6, 2015 at 2:59 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi Benson,
Hi,
I'm co-maintaining the Maven package in Debian and I'd like to mention
that the Ant bootstrap is also used in the build process. I'd be very
grateful if you could keep maintaining it, the Maven packaging is
already quite difficult (we are blocked on the 3.0.5- 3.1.1 upgrade)
and removing the
We are CTR not RTC
If you object to the change, veto the commit
On 6 March 2015 at 07:44, Olivier Lamy ol...@apache.org wrote:
+1
I just find the change/discussion a bit too fast.
You should wait longer than ~10h as the world has more timezone.
IMHO waiting for the answer from various
Hi,
It's a known wrong and misleading message, tracked as MNG-5477
Regards,
Hervé
- Mail original -
De: Karl Heinz Marbaise khmarba...@gmx.de
À: Maven Developers List dev@maven.apache.org
Envoyé: Vendredi 6 Mars 2015 09:32:01
Objet: Maven 3.0.5 Problem
Hi,
during the tests of maven
+1
On Thu, Mar 5, 2015 at 8:16 AM, Igor Fedorenko i...@ifedorenko.com wrote:
This is chicken-and-egg situation. We won't use java 7 features unless
the code targets java 7.
Try-with-resources and multi-exception catch are the too features I'd
like to start using throughout the code. Although
+1
--
Olivier
On 5 Mar 2015 09:10, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
We solved 15 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?
projectId=11137version=20457
There are still a couple of issues left in JIRA:
Hi Benson,
first the link to the release is unfortunately wrong...the correct link is:
https://repository.apache.org/content/repositories/maven-1146/org/apache/maven/archetype/maven-archetype/2.3/maven-archetype-2.3-source-release.zip
Checked SHA1 Ok...
Next step checking with Maven 2.2.1,
Hi,
here is my +1...
Kind regards
Karl Heinz Marbaise
On 3/4/15 10:56 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11714version=16117
There are still a couple of issues left in JIRA:
Hi,
here is my +1
Kind regards
Karl Heinz Marbaise
On 3/4/15 11:09 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 15 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137version=20457
There are still a couple of issues left in JIRA:
Ok, the consensus is to move forward to Java7. I updated the POM and we're
in no rush so give it a whirl and we can think about releasing next week if
the world doesn't blow up.
Please create a JIRA ticket for this to make things clear in the release
notes.
/Anders
On Mar 5, 2015, at
Hi,
during the tests of maven archetype release i found that using Maven
3.0.5 produced the following messages
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for
+1
--
Olivier
On 5 Mar 2015 08:56, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?
projectId=11714version=16117
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%
18 matches
Mail list logo