JDK 9 EA Build 174 & JDK 8u152 b04 are available on jdk.java.net

[Rory O'Donnell]

Hi Robert ,

*JDK 9 Early Access*  build 174  is available at : - jdk.java.net/9/

A summary of all the changes in this build are listed here 
.


Changes which were introduced since the last availability email that may 
be of interest :


 * b172 - JDK-8179014 : JFileChooser with Windows look and feel crashes
   on win 10
 * b173 - JDK-8180582 : the bind to rmiregistry is rejected by
   registryFilter even though registryFilter is set
 * b174 - JDK-8181702  : deprecate for removal the following tool
   modules:jdk.xml.bind and jdk.xml.ws

*JDK 9 Schedule Update*

 * The new GA date for JDK 9 is now set to 2017-09-21 [1]
 * We have updated the OpenJDK JDK 9 project page [2] with the new
   milestones and GA date.


*JDK 8u152 Early Access*  build 04 is available at : - jdk.java.net/8/ 



A summary of all the changes in this build are listed here 
.

Information and schedules specific to OpenJDK 8u152 release [3]

Rgds,Rory

[1] http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-June/005867.html
[2] http://openjdk.java.net/projects/jdk9/
[3] http://openjdk.java.net/projects/jdk8u/releases/8u152.html

--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

[GitHub] maven-plugins pull request #115: Upgrade to Plexus Archiver 3.5-SNAPSHOT

[snicoll]

GitHub user snicoll opened a pull request:

https://github.com/apache/maven-plugins/pull/115

Upgrade to Plexus Archiver 3.5-SNAPSHOT

See MASSEMBLY-854

Please note that this new release of plexus archiver requires Java7

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/snicoll/maven-plugins MASSEMBLY-854

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/115.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #115


commit eecf761b2edca2f91e52bf601db51bb86fb679d6
Author: Stephane Nicoll 
Date:   2017-06-16T12:34:03Z

Upgrade to Plexus Archiver 3.5-SNAPSHOT




---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: packaging type generating the current pom

[Robert Scholte]

On Fri, 16 Jun 2017 04:55:17 +0200, Olivier Lamy  wrote:


well not better as it looks not being possible

[ERROR] 'dependencyManagement.dependencies.dependency.classifier' for
org.eclipse.jetty:jetty-bom:pom:bom must be empty, imported POM cannot  
have

a classifier. @ line 40, column 21

WHY this restriction?


Only for a bom it could make sense to add a classifier, for all other poms  
it doesn't. I can imagine this is historical.
For Maven 5 the proposal is to make a pdt-file for every artifact, but  
that won't help you right now.


Robert



On 16 June 2017 at 11:40, Olivier Lamy  wrote:


Hi Robert
Sorry for late reply.
Well this doesn't work (see source here [1]) you can attach an artifact
with his own GAV.
And it's neither possible to change GAV of an attached artifact.

Caused by: java.lang.UnsupportedOperationException: Cannot change the
groupId for an attached artifact. It is derived from the main  
artifact.at

org.apache.maven.project.artifact.AttachedArtifact.
setGroupId(AttachedArtifact.java:110)

So at this stage the only solution I have is to attach an artifact with  
a

new classifier "bom"

Cheers
Olivier

[1] https://github.com/apache/maven/blob/eb6b212b567c287734a2dbbef3c113
fe650f1def/maven-core/src/main/java/org/apache/maven/project/
DefaultMavenProjectHelper.java#L101



On 9 June 2017 at 19:56, Robert Scholte  wrote:


Hi Olivier,

assuming this bom file is not used by the reactor, it should be  
possible

to possible to generate it in the root pom and attach it with its own
GA[1][2].
The javadoc content says this piece of code is deprecated, probably
because it introduces some magic where it is hard to determine where  
the
file is coming from. I think we should be able to allow this and in  
case of
pom.xml let Maven add some XML comment saying it was provided as part  
of

project GA(V)

Is this less hackish?

Robert


[1] https://maven.apache.org/ref/3.5.0/maven-core/apidocs/org/ap
ache/maven/project/MavenProject.html#addAttachedArtifact(org
.apache.maven.artifact.Artifact)

[2] https://maven.apache.org/ref/3.5.0/maven-core/apidocs/org/ap
ache/maven/project/DefaultMavenProjectHelper.html#attachArti
fact(org.apache.maven.project.MavenProject,%20org.apache.
maven.artifact.Artifact)


On Fri, 09 Jun 2017 08:35:11 +0200, Olivier Lamy 
wrote:

Hi,

Not sure how to do that in a non hackhish way.
My current goal: generate a bom style pom with all reactor projects in
dptMngt section.
As people are lazy to write dptMngt section in theirs poms they  
delegate

to
others with this pom.
So as I'm lazy too I don't want to write/maintain this pom neither so  
I

prefer using a plugin for that :-)
So I create a new packaging type bom and enable it on a pom.
The plugin simply generate a pom.xml file with all content and the
calculated dptMngt section.
The only way I found to replace the current pom is to use:
project.setFile(
the new pom file)

Any other way?

Cheers



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org





--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy






-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org