Re: [VOTE] Retired Maven Artifact Resolution API (Maven2)

[Sylwester Lachiewicz]

+1

W dniu sob., 11.05.2019 o 01:30 Tibor Digana 
napisał(a):

> +1
>
> On Wed, May 8, 2019 at 8:25 PM Robert Scholte 
> wrote:
>
> > Hi,
> >
> > The Apache Maven project consist of about 100 (sub)projects. Due to the
> > small number of volunteers and the huge amount of code to maintain we're
> > missing enough space to make real progress on all these projects,
> including
> > our ambitious ideas for the next major version(s) of Maven itself.
> > To be able to gain more focus we need to criticize the current
> subprojects
> > and decide if it is worth maintaining.
> >
> > The Maven Artifact Resolution API (maven-artifact-resolver) is a shared
> > component that could be used to easily resolve Maven project
> dependencies.
> > The last (and only) released version is 1.0 in September 2009.(
> > https://maven.apache.org/shared/maven-artifact-resolver/ [
> > https://maven.apache.org/shared/maven-artifact-resolver/] ).
> > This library should not be confused with Artifact Resolver
> > (maven-resolver), previously known as Aether. As you can see the naming
> > will cause confusion.
> > The library that aims the same goal for Artifact Resolver is another
> > shared component called maven-artifact-transfer (which by now is not just
> > the transfer part or Artifact Resolver, but a bridge for both Sonatype
> > Aether as used in Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+.
> > This way Maven plugins and extensions can be compatible with any Maven 3
> > release)
> >
> > I therefore propose that we retire the maven-artifact-resolver.
> >
> > I don't think it makes sense to do a final release. Instead we should
> > update the documentation and the freeze the codebase.
> >
> > The process for retiring a plugin is described here:
> > https://maven.apache.org/developers/retirement-plan-plugins.html [
> > https://maven.apache.org/developers/retirement-plan-plugins.html]
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Yes, it's about time
> > [ ] -1 No, because...
>

Re: [VOTE] Retired Maven Artifact Resolution API (Maven2)

[Tibor Digana]

+1

On Wed, May 8, 2019 at 8:25 PM Robert Scholte  wrote:

> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
> our ambitious ideas for the next major version(s) of Maven itself.
> To be able to gain more focus we need to criticize the current subprojects
> and decide if it is worth maintaining.
>
> The Maven Artifact Resolution API (maven-artifact-resolver) is a shared
> component that could be used to easily resolve Maven project dependencies.
> The last (and only) released version is 1.0 in September 2009.(
> https://maven.apache.org/shared/maven-artifact-resolver/ [
> https://maven.apache.org/shared/maven-artifact-resolver/] ).
> This library should not be confused with Artifact Resolver
> (maven-resolver), previously known as Aether. As you can see the naming
> will cause confusion.
> The library that aims the same goal for Artifact Resolver is another
> shared component called maven-artifact-transfer (which by now is not just
> the transfer part or Artifact Resolver, but a bridge for both Sonatype
> Aether as used in Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+.
> This way Maven plugins and extensions can be compatible with any Maven 3
> release)
>
> I therefore propose that we retire the maven-artifact-resolver.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and the freeze the codebase.
>
> The process for retiring a plugin is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html [
> https://maven.apache.org/developers/retirement-plan-plugins.html]
>
> The vote is open for 72 hours.
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...

Re: JDK 13 - Early Access build 20 is available

[Rory O'Donnell]

Hi Robert,

I expect the best place to bring this up is on the 
net.java.openjdk.nio-dev mailing list ?


Rgds,Rory

On 10/05/2019 09:36, Robert Scholte wrote:

Hi Rory,

 I noticed the following change:
- Add new FileSystems.newFileSystem methods (JDK-8218875)

Based on the method signature it looks like something we discussed on 
the mailinglist and during FOSDEM.
In short we'd like to control the basedir of a FileSystem, which is 
now controlled by the System property user.dir and which has been made 
immutable recently.

The new methods seems to only accept a regular file.
I'm wondering if our request (if implemented) could cause confusion 
with the current signatures.


thanks,
Robert


On Fri, 10 May 2019 10:19:35 +0200, Rory O'Donnell 
 wrote:



Hi Robert ,


  *OpenJDK builds *- JDK 13 - Early Access build 20 is
  available at http://jdk.java.net/13/

  * These early-access , open-source builds are provided under the
  o GNU General Public License, version 2, with the Classpath
Exception .
  * Changes in this build


  * Release notes [1]


  *Significant changes since the last availability email*

  * build 20
  o Removal of T-Systems Deutsche Telekom Root CA 2
certificate (JDK-8222137)
  o Add new FileSystems.newFileSystem methods (JDK-8218875)
  o Enhance auto vectorization for x86 (JDK-8222074)
  o Remove CollectorPolicy and its subclasses (JDK-8198505)
  o Drop support for pre JDK 1.4 SocketImpl implementations
(JDK-8216978)
  * build 19
  o add support for generating method handles from a variable
symbol (JDK-8222744)
  o mark new VM option AllowRedefinitionToAddOrDeleteMethods
as deprecated (JDK-8222934)
  * build 18
  o Improve String::equals warmup characteristics (JDK-8215017)
  o [Containers] Improve systemd slice memory limit support
(JDK-8217338)


Bug fixes for issues reported by Open Source Projects

  * build 20
  o assert(Compile::current()->live_nodes() <
Compile::current()->max_node_limit()) failed: Live Node
limit exceeded limit (JDK-8219520)
  o C2: MemNode::can_see_stored_value() ignores casts which
carry control dependency (JDK-8219902)
  o New fix of the deadlock in sun.security.ssl.SSLSocketImpl
(JDK-8219991)


  JEP updates since last email

  * JEP 350: Dynamic CDS Archives
  istargeted for JDK 13.
  * JEP 351: ZGC: Uncommit Unused Memory
 istargeted for JDK 13
  * JEP 353: Reimplement the Legacy Socket API
 moved to Candidate
  * JEP 354: Switch Expressions 
moved to Candidate.


  OpenJDK Committers’ Workshop, 1–2 August 2019 [2]

Rgds,Rory

[1] http://jdk.java.net/13/release-notes
[2]
https://mail.openjdk.java.net/pipermail/announce/2019-April/000269.html

-- 
Rgds, Rory O'Donnell

Quality Engineering Manager
Oracle EMEA, Dublin, Ireland





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

Re: Tagging Maven Checkstyle plugin

[Enrico Olivelli]

Il giorno ven 10 mag 2019 alle ore 14:53 Eric Lilja 
ha scritto:

> Great news! Which version of Checkstyle will be default, 8.20? Hoping for
> 8.20!
>

Actually we have 8.19
https://github.com/apache/maven-checkstyle-plugin/blob/6abad1cb750244899c6e3b45a7a8bb49fba954db/pom.xml#L71

Feel free to send a PR

Enrico


>
> - Eric L
>
> On Fri, May 10, 2019 at 2:42 PM Tibor Digana 
> wrote:
>
> > Thx for your effort.
> > Good job with everything you have done in Maven.
> >
> > On Fri, May 10, 2019 at 2:23 PM Enrico Olivelli 
> > wrote:
> >
> > > Hi all,
> > > I am going to cut a release of Maven Checkstyle Plugin during this
> > weekend.
> > >
> > > There are major changes, I will release 3.1.0 version:
> > > - drop support for Java 7 (Checkstyle 8 needs java 8)
> > > - drop support for Checkstyle  < 8.x (We have migrated to the new
> > > Checkstyle API)
> > > - do not resolve anymore project depedencies (This seems deprecated
> from
> > > Checkstyle perspective)
> > >
> > > Most of these works have been done with guys from Checkstyle project
> and
> > > this is great because our plugin is mostly a wrapper around Checkstyle
> > and
> > > it is good that we work together.
> > >
> > > Unfortunately Checkstyle 8 has major breking changes and checkstyle
> > > configuration files taht worked on CS 6 do not work any more (I had to
> > > change a bunch of ITs) but this is expected
> > > and this is very appreciated from CS community because now they are
> free
> > to
> > > move forward
> > > with the project.
> > >
> > > Enrico
> > >
> >
>

Re: Tagging Maven Checkstyle plugin

[Eric Lilja]

Great news! Which version of Checkstyle will be default, 8.20? Hoping for
8.20!

- Eric L

On Fri, May 10, 2019 at 2:42 PM Tibor Digana  wrote:

> Thx for your effort.
> Good job with everything you have done in Maven.
>
> On Fri, May 10, 2019 at 2:23 PM Enrico Olivelli 
> wrote:
>
> > Hi all,
> > I am going to cut a release of Maven Checkstyle Plugin during this
> weekend.
> >
> > There are major changes, I will release 3.1.0 version:
> > - drop support for Java 7 (Checkstyle 8 needs java 8)
> > - drop support for Checkstyle  < 8.x (We have migrated to the new
> > Checkstyle API)
> > - do not resolve anymore project depedencies (This seems deprecated from
> > Checkstyle perspective)
> >
> > Most of these works have been done with guys from Checkstyle project and
> > this is great because our plugin is mostly a wrapper around Checkstyle
> and
> > it is good that we work together.
> >
> > Unfortunately Checkstyle 8 has major breking changes and checkstyle
> > configuration files taht worked on CS 6 do not work any more (I had to
> > change a bunch of ITs) but this is expected
> > and this is very appreciated from CS community because now they are free
> to
> > move forward
> > with the project.
> >
> > Enrico
> >
>

Re: Tagging Maven Checkstyle plugin

[Tibor Digana]

Thx for your effort.
Good job with everything you have done in Maven.

On Fri, May 10, 2019 at 2:23 PM Enrico Olivelli  wrote:

> Hi all,
> I am going to cut a release of Maven Checkstyle Plugin during this weekend.
>
> There are major changes, I will release 3.1.0 version:
> - drop support for Java 7 (Checkstyle 8 needs java 8)
> - drop support for Checkstyle  < 8.x (We have migrated to the new
> Checkstyle API)
> - do not resolve anymore project depedencies (This seems deprecated from
> Checkstyle perspective)
>
> Most of these works have been done with guys from Checkstyle project and
> this is great because our plugin is mostly a wrapper around Checkstyle and
> it is good that we work together.
>
> Unfortunately Checkstyle 8 has major breking changes and checkstyle
> configuration files taht worked on CS 6 do not work any more (I had to
> change a bunch of ITs) but this is expected
> and this is very appreciated from CS community because now they are free to
> move forward
> with the project.
>
> Enrico
>

Tagging Maven Checkstyle plugin

[Enrico Olivelli]

Hi all,
I am going to cut a release of Maven Checkstyle Plugin during this weekend.

There are major changes, I will release 3.1.0 version:
- drop support for Java 7 (Checkstyle 8 needs java 8)
- drop support for Checkstyle  < 8.x (We have migrated to the new
Checkstyle API)
- do not resolve anymore project depedencies (This seems deprecated from
Checkstyle perspective)

Most of these works have been done with guys from Checkstyle project and
this is great because our plugin is mostly a wrapper around Checkstyle and
it is good that we work together.

Unfortunately Checkstyle 8 has major breking changes and checkstyle
configuration files taht worked on CS 6 do not work any more (I had to
change a bunch of ITs) but this is expected
and this is very appreciated from CS community because now they are free to
move forward
with the project.

Enrico

Re: [VOTE] Release Apache Maven JAR Plugin version 3.1.2

[Robert Scholte]

+1

On Wed, 08 May 2019 22:22:24 +0200, Karl Heinz Marbaise  
 wrote:



Hi,

We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12344629

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC


Staging repo:
https://repository.apache.org/content/repositories/maven-1502/
https://repository.apache.org/content/repositories/maven-1502/org/apache/maven/plugins/maven-jar-plugin/3.1.2/maven-jar-plugin-3.1.2-source-release.zip

Source release checksum(s):
maven-jar-plugin-3.1.2-source-release.zip sha1:
cb3abae243455afbca49cc1b9f156235411223e2
maven-jar-plugin-3.1.2-source-release.zip sha512:
aff5baf3c218ab79e1f15b59f3c7e6c0c0b5344b13cf62d1aef03be34a8f90b75ceb51c7d8a28f1916becdcc48ec869b426bcb71365de364a93b981050d1fd70

Staging site:
https://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

Kind regards
Karl Heinz Marbaise

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


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

Re: [VOTE] Release Apache Maven JAR Plugin version 3.1.2

[Eric Lilja]

+1 (non-binding)

On Fri, May 10, 2019 at 8:54 AM Karl Heinz Marbaise 
wrote:

> Hi,
> +1 from me.
>
> Kind regards
> Karl Heinz Marbaise
> On 08.05.19 22:22, Karl Heinz Marbaise wrote:
> > Hi,
> >
> > We solved 2 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12344629
> >
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
> >
> >
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1502/
> >
> https://repository.apache.org/content/repositories/maven-1502/org/apache/maven/plugins/maven-jar-plugin/3.1.2/maven-jar-plugin-3.1.2-source-release.zip
> >
> >
> > Source release checksum(s):
> > maven-jar-plugin-3.1.2-source-release.zip sha1:
> > cb3abae243455afbca49cc1b9f156235411223e2
> > maven-jar-plugin-3.1.2-source-release.zip sha512:
> >
> aff5baf3c218ab79e1f15b59f3c7e6c0c0b5344b13cf62d1aef03be34a8f90b75ceb51c7d8a28f1916becdcc48ec869b426bcb71365de364a93b981050d1fd70
> >
> >
> > Staging site:
> > https://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: JDK 13 - Early Access build 20 is available

[Robert Scholte]

Hi Rory,

 I noticed the following change:
- Add new FileSystems.newFileSystem methods (JDK-8218875)

Based on the method signature it looks like something we discussed on the  
mailinglist and during FOSDEM.
In short we'd like to control the basedir of a FileSystem, which is now  
controlled by the System property user.dir and which has been made  
immutable recently.

The new methods seems to only accept a regular file.
I'm wondering if our request (if implemented) could cause confusion with  
the current signatures.


thanks,
Robert


On Fri, 10 May 2019 10:19:35 +0200, Rory O'Donnell  
 wrote:




Hi Robert ,OpenJDK builds  - JDK 13 - Early Access build 20 is available  
at http://jdk.java.net/13/

These early-access , open-source builds are provided under the
GNU General Public License, version 2, with the Classpath Exception.
Changes in this buildRelease notes [1]Significant changes since the last  
availability email

build 20
Removal of T-Systems Deutsche Telekom Root CA 2 certificate (JDK-8222137)
Add new FileSystems.newFileSystem methods (JDK-8218875)
Enhance auto vectorization for x86 (JDK-8222074)
Remove CollectorPolicy and its subclasses (JDK-8198505)
Drop support for pre JDK 1.4 SocketImpl implementations (JDK-8216978)
build 19add support for generating method handles from a variable symbol  
(JDK-8222744)
mark new VM option AllowRedefinitionToAddOrDeleteMethods as deprecated  
(JDK-8222934)

build 18Improve String::equals warmup characteristics (JDK-8215017)
[Containers] Improve systemd slice memory limit support (JDK-8217338)
Bug fixes for issues reported by Open Source Projects build 20 
assert(Compile::current()->live_nodes() <  
Compile::current()->max_node_limit()) failed: Live Node limit exceeded  
limit (JDK-8219520)
C2: MemNode::can_see_stored_value() ignores casts which carry control  
dependency (JDK-8219902)

New fix of the deadlock in sun.security.ssl.SSLSocketImpl (JDK-8219991)
JEP updates since last email
JEP 350: Dynamic CDS Archives  is targeted for JDK 13.
JEP 351: ZGC: Uncommit Unused Memory is targeted for JDK 13
JEP 353: Reimplement the Legacy Socket API moved to Candidate
JEP 354: Switch Expressions moved to Candidate.
OpenJDK Committers’ Workshop, 1–2 August 2019 [2]


Rgds,Rory
[1] http://jdk.java.net/13/release-notes
[2]  
https://mail.openjdk.java.net/pipermail/announce/2019-April/000269.html

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

JDK 13 - Early Access build 20 is available

[Rory O'Donnell]

Hi Robert ,


 *OpenJDK builds *- JDK 13 - Early Access build 20 is available at
 http://jdk.java.net/13/

 * These early-access , open-source builds are provided under the
 o GNU General Public License, version 2, with the Classpath
   Exception .
 * Changes in this build
   

 * Release notes [1]


 *Significant changes since the last availability email*

 * build 20
 o Removal of T-Systems Deutsche Telekom Root CA 2 certificate
   (JDK-8222137)
 o Add new FileSystems.newFileSystem methods (JDK-8218875)
 o Enhance auto vectorization for x86 (JDK-8222074)
 o Remove CollectorPolicy and its subclasses (JDK-8198505)
 o Drop support for pre JDK 1.4 SocketImpl implementations
   (JDK-8216978)
 * build 19
 o add support for generating method handles from a variable symbol
   (JDK-8222744)
 o mark new VM option AllowRedefinitionToAddOrDeleteMethods as
   deprecated (JDK-8222934)
 * build 18
 o Improve String::equals warmup characteristics (JDK-8215017)
 o [Containers] Improve systemd slice memory limit support
   (JDK-8217338)


   Bug fixes for issues reported by Open Source Projects

 * build 20
 o assert(Compile::current()->live_nodes() <
   Compile::current()->max_node_limit()) failed: Live Node limit
   exceeded limit (JDK-8219520)
 o C2: MemNode::can_see_stored_value() ignores casts which carry
   control dependency (JDK-8219902)
 o New fix of the deadlock in sun.security.ssl.SSLSocketImpl
   (JDK-8219991)


 JEP updates since last email

 * JEP 350: Dynamic CDS Archives  
   istargeted for JDK 13.
 * JEP 351: ZGC: Uncommit Unused Memory
    istargeted for JDK 13
 * JEP 353: Reimplement the Legacy Socket API
    moved to Candidate
 * JEP 354: Switch Expressions  moved
   to Candidate.


 OpenJDK Committers’ Workshop, 1–2 August 2019 [2]

Rgds,Rory

[1] http://jdk.java.net/13/release-notes
[2] https://mail.openjdk.java.net/pipermail/announce/2019-April/000269.html

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