+1
On 15 September 2014 01:51, Hervé BOUTEMY wrote:
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=18319
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status
Thought I'd give this a shot on one our maven projects:
java version "1.9.0-ea"
Java(TM) SE Runtime Environment (build 1.9.0-ea-b30)
Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b30, mixed mode)
This was just running maven with JAVA_HOME set to the JDK9 directory (
on OSX ):
[ERROR] Fai
True, but IIRC we got a lot of serious complaints after deleting tags in
Git when trying to push a new Maven Distribution (I think svn is less
critical due to its different approach).
Although I prefer single digit incremental versions over version gaps, I
have agree that it is just a number.
I believe it's not the first time someone delete a tag because of a
cancelled release.
--
Olivier
On Sep 16, 2014 6:40 AM, "Robert Scholte" wrote:
> Ouch?!
>
> Op Mon, 15 Sep 2014 03:44:29 +0200 schreef :
>
> Repository: maven-wagon
>> Updated Tags: refs/tags/wagon-2.7 [deleted] b00132663
>>
>
There will still be a copy around, get hold of the original and push it
back up. Hooks should be setup to prevent tag deletion...
On Tue, Sep 16, 2014 at 8:40 AM, Robert Scholte
wrote:
> Ouch?!
>
> Op Mon, 15 Sep 2014 03:44:29 +0200 schreef :
>
> Repository: maven-wagon
>> Updated Tags: refs/
work done:
http://people.apache.org/~hboutemy/codehaus/summary.html
after author stats for each component, there is the shortlog for patches
applied
now we need to prepare attribution thread, to let a maximum of contributors
express their desire to give their contribution to ASF.
Any proposal f
Ouch?!
Op Mon, 15 Sep 2014 03:44:29 +0200 schreef :
Repository: maven-wagon
Updated Tags: refs/tags/wagon-2.7 [deleted] b00132663
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: de
Hi,
The main focus for this release is Java 8 compatibility.
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138&styleName=Html&version=19448
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=1113
+1
Regards,
Hervé
Le dimanche 14 septembre 2014 20:19:44 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/browse/MSHARED/fixforversion/19225
>
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MSHARED%20AND%20resolut
> ion%20%3D%20Unresolved%20AND%20c
Thanks for the feedback Guys, if you have a contact at Guava that would
be great ?
Rgds,Rory
On 15/09/2014 12:51, Stuart McCulloch wrote:
Just to clarify, Sisu has _never_ used any Guava APIs directly, the use of
Guava comes from its use of Guice.
In Guice 3.0 Guava was shaded in under an in
Just to clarify, Sisu has _never_ used any Guava APIs directly, the use of
Guava comes from its use of Guice.
In Guice 3.0 Guava was shaded in under an internal package, since then Guava is
now an external dependency:
https://github.com/google/guice/commit/3236b100a95b739577dfcd117c246
I was not suggesting changing guava, which I agree, is not our problem.
I was suggesting using more recent version of guava in maven, which only
we can do.
--
Regards,
Igor
On 2014-09-15, 7:42, Kristian Rosenvold wrote:
Guava is a general purpose library that contains quite a bunch of
stuff. It
Guava is a general purpose library that contains quite a bunch of
stuff. It seems like the report we're looking at is simply a byte code
scan of our "lib" folder looking for undesirables.
sun.misc.Unsafe is cookie jar of cool stuff that certain features of
guava use. I doubt that /we/ actually use
We can move to the newer version of guava. This was one of the reasons I
updated to the latest sisu, I was told it did not depend on any internal
guava apis any more. Of course, somebody will have to check what guava
version is compatible with JDK 9 before we upgrade.
--
Regards,
Igor
On 2014-09
So if I read your report correctly, our code uses guava, which
contains references to sun.misc.Unsafe. Actually it's sisu that uses
guava, not maven core itself.
Not too much we can do about that, other than consider throwing guava
out of sisu. As long as we're on a sub-1.8 minimum language le
Hi,
here is my +1.
Kind regards
Karl-Heinz Marbaise
On 9/14/14 8:19 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 3 issues:
http://jira.codehaus.org/browse/MSHARED/fixforversion/19225
http://jira.codehaus.org/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20com
Hi Stephen,
One more time, hope this is ok.
Rgds,Rory
JDK Internal API Usage Report for apache-maven-3.2.3
The OpenJDK Quality Outreach campaign has run a compatibility report to
identify usage of JDK-internal APIs. Usage of these JDK-internal APIs
could pose compatibility issues, as the J
Chris, See
http://maven.apache.org/developers/conventions/git.html.
I didn't know it existed until yesterday.
On Mon, Sep 15, 2014 at 1:26 AM, Chris Graham wrote:
> So, if the scm stuff is in git, my original question still remains
> unanswered.
>
> What are the process steps needed to go thr
Ok, here is the text. Rgds,Rory
JDK Internal API Usage Report for apache-maven-3.2.3
The OpenJDK Quality Outreach campaign has run a compatibility report to
identify usage of JDK-internal APIs. Usage of these JDK-internal APIs
could pose compatibility issues, as the Java team explained in 19
I think the mailing list stripped the attachment
On Monday, 15 September 2014, Rory O'Donnell Oracle, Dublin Ireland <
rory.odonn...@oracle.com> wrote:
> Hi Robert,Kristian,
>
> As part of the preparations for JDK 9, Oracle's engineers have been
> analyzing open source projects like yours to unde
Hi Robert,Kristian,
As part of the preparations for JDK 9, Oracle's engineers have been
analyzing open source projects like yours to understand usage.
One area of concern involves identifying compatibility problems, such as
reliance on JDK-internal APIs.
Our engineers have already prepared gu
21 matches
Mail list logo
