Re: [VOTE] Release Maven Project Info Reports Plugin version 3.0.1

2019-08-24 Thread Tibor Digana 
Hi Gabriel,

Let me paraphrase what you said " ... into master ... before I made changes
using PatternExcludesArtifactFilter based on the reviews ".
This means we are missing some commit in master.
In this case it does not make sense to test this project because the work
is incomplete.
We have to complete it first and then restart the release process.
That's better than doing new bug fix(es).

Cheers
Tibor17

On Sun, Aug 25, 2019 at 12:06 AM Gabriel Belingueres 
wrote:

> Hi Tibor:
>
> Please note I don't know if it's a plugin issue. Further tests shows that
> it works OK when configuring the plugin in the reporting section:
>
>   
> 
> 
>   org.apache.maven.plugins
>   maven-project-info-reports-plugin
>   3.0.1
>   
> 
>
> org.eclipse.m2e
> 
>   
> 
> 
>   
>
> *BUT* if I configure the plugin in BOTH the pluginManagement and reporting
> section, then it fails again.
> Sounds to me like some plugin resolution condition that causes the
> pluginManagementExcludes list parameter to not be set.
>
>
> El sáb., 24 de ago. de 2019 a la(s) 17:32, Tibor Digana (
> tibordig...@apache.org) escribió:
>
> > that's bad. We were too fast :-)
> > Although my build passed but in this case as I saw the commit I have to
> > give my -1, sorry!
> >
> > On Sat, Aug 24, 2019 at 9:41 PM Gabriel Belingueres <
> belingue...@gmail.com
> > >
> > wrote:
> >
> > > Hi:
> > >
> > > Regarding MPIR-375, I noted that the merge of the PR into master branch
> > > was done *before* I made changes using PatternExcludesArtifactFilter
> > based
> > > on the reviews.
> > >
> > > See https://github.com/apache/maven-project-info-reports-plugin/pull/7
> .
> > > The commit in master is:
> > >
> >
> https://github.com/apache/maven-project-info-reports-plugin/commit/82f4bf23b79fe87d2e414c70ab2058e8f1b4146b
> > >
> > > The patch should work anyway so I decided to test it with the
> > > maven-shared-utils library.
> > > I added this to the pom.xml file (in addition to adding the
> > > staged-releases profile to settings.xml with the staged repo):
> > >
> > > 
> > >   
> > > 
> > >   org.apache.maven.plugins
> > >   maven-project-info-reports-plugin
> > >   3.0.1
> > >   
> > > 
> > >
> > > org.eclipse.m2e
> > > 
> > >   
> > > 
> > >   
> > > 
> > >
> > > With version 3.0.1, running 'mvn -V -Pstaged-releases clean site >
> > > 3.0.1.log' throws an exception. (see 3.0.1.log attached file)
> > >
> > > However, when building 3.0.2-SNAPSHOT and installing in the local repo
> > > (please see that in git repo there are no new commits after the 3.0.1
> > > release), changing the version to 3.0.2-SNAPSHOT works as expected:
> > >
> > > mvn -V -Pstaged-releases clean site > 3.0.2-SNAPSHOT.log
> > >
> > > Does anyone else is having this problem? Or am I doing something wrong?
> > >
> > > Kind regards,
> > > Gabriel
> > >
> > > El vie., 23 de ago. de 2019 a la(s) 16:33, Michael Osipov (
> > > micha...@apache.org) escribió:
> > >
> > >> Hi,
> > >>
> > >> We solved 5 issues:
> > >>
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12344828
> > >>
> > >> There are still a couple of issues left in JIRA:
> > >> https://issues.apache.org/jira/projects/MPIR/issues
> > >>
> > >> Staging repo:
> > >> https://repository.apache.org/content/repositories/maven-1528/
> > >>
> > >>
> >
> https://repository.apache.org/content/repositories/maven-1528/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.1/maven-project-info-reports-plugin-3.0.1-source-release.zip
> > >>
> > >> Source release checksum(s):
> > >> maven-project-info-reports-plugin-3.0.1-source-release.zip
> > >> sha512:
> > >>
> > >>
> >
> 7145430a6999ed65a886ac503793f0aa9488b6853431c494c3dee6360c05f3db53fe46ff77bd41514002e8c320b0f4623d23b85d3a9373450c90bb713d3e50be
> > >>
> > >> Staging site:
> > >>
> > >>
> >
> https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/
> > >>
> > >> Guide to testing staged releases:
> > >>
> https://maven.apache.org/guides/development/guide-testing-releases.html
> > >>
> > >> Vote open for 72 hours.
> > >>
> > >> [ ] +1
> > >> [ ] +0
> > >> [ ] -1
> > >>
> > >> -
> > >> 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 Maven Project Info Reports Plugin version 3.0.1

2019-08-24 Thread Gabriel Belingueres 
Hi Tibor:

Please note I don't know if it's a plugin issue. Further tests shows that
it works OK when configuring the plugin in the reporting section:

  


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.0.1
  


org.eclipse.m2e

  


  

*BUT* if I configure the plugin in BOTH the pluginManagement and reporting
section, then it fails again.
Sounds to me like some plugin resolution condition that causes the
pluginManagementExcludes list parameter to not be set.


El sáb., 24 de ago. de 2019 a la(s) 17:32, Tibor Digana (
tibordig...@apache.org) escribió:

> that's bad. We were too fast :-)
> Although my build passed but in this case as I saw the commit I have to
> give my -1, sorry!
>
> On Sat, Aug 24, 2019 at 9:41 PM Gabriel Belingueres  >
> wrote:
>
> > Hi:
> >
> > Regarding MPIR-375, I noted that the merge of the PR into master branch
> > was done *before* I made changes using PatternExcludesArtifactFilter
> based
> > on the reviews.
> >
> > See https://github.com/apache/maven-project-info-reports-plugin/pull/7.
> > The commit in master is:
> >
> https://github.com/apache/maven-project-info-reports-plugin/commit/82f4bf23b79fe87d2e414c70ab2058e8f1b4146b
> >
> > The patch should work anyway so I decided to test it with the
> > maven-shared-utils library.
> > I added this to the pom.xml file (in addition to adding the
> > staged-releases profile to settings.xml with the staged repo):
> >
> > 
> >   
> > 
> >   org.apache.maven.plugins
> >   maven-project-info-reports-plugin
> >   3.0.1
> >   
> > 
> >
> > org.eclipse.m2e
> > 
> >   
> > 
> >   
> > 
> >
> > With version 3.0.1, running 'mvn -V -Pstaged-releases clean site >
> > 3.0.1.log' throws an exception. (see 3.0.1.log attached file)
> >
> > However, when building 3.0.2-SNAPSHOT and installing in the local repo
> > (please see that in git repo there are no new commits after the 3.0.1
> > release), changing the version to 3.0.2-SNAPSHOT works as expected:
> >
> > mvn -V -Pstaged-releases clean site > 3.0.2-SNAPSHOT.log
> >
> > Does anyone else is having this problem? Or am I doing something wrong?
> >
> > Kind regards,
> > Gabriel
> >
> > El vie., 23 de ago. de 2019 a la(s) 16:33, Michael Osipov (
> > micha...@apache.org) escribió:
> >
> >> Hi,
> >>
> >> We solved 5 issues:
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12344828
> >>
> >> There are still a couple of issues left in JIRA:
> >> https://issues.apache.org/jira/projects/MPIR/issues
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-1528/
> >>
> >>
> https://repository.apache.org/content/repositories/maven-1528/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.1/maven-project-info-reports-plugin-3.0.1-source-release.zip
> >>
> >> Source release checksum(s):
> >> maven-project-info-reports-plugin-3.0.1-source-release.zip
> >> sha512:
> >>
> >>
> 7145430a6999ed65a886ac503793f0aa9488b6853431c494c3dee6360c05f3db53fe46ff77bd41514002e8c320b0f4623d23b85d3a9373450c90bb713d3e50be
> >>
> >> Staging site:
> >>
> >>
> https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/
> >>
> >> Guide to testing staged releases:
> >> https://maven.apache.org/guides/development/guide-testing-releases.html
> >>
> >> Vote open for 72 hours.
> >>
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1
> >>
> >> -
> >> 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
>

Guidance for Maven Core release

2019-08-24 Thread Enrico Olivelli 
Hello,
As I going to start the release procedure for Maven Core I have a bunch of
questions.
I see  that the procedure is slightly different from the procedure for
plugins ([1]), but actually the main differences are about the way we stage
the release artifacts and the finalization phase, the core of the processs
will be release:prepare and release:perform as usual.

So I will run "mvn:perform" and I will copy the artifacts to [4], that is
in a directory named 3.6.2 (I see that Karl used 3.6.0 last time for 3.6.1,
maybe it was a typo).
I will run manually the integration tests against the binary artifacts
generated and perform my self tests, if I have some problem can I drop the
get tag and the staged repository or should I ban "3.6.2" tag forever and
move immediately to 3.6.3 ?

I see that Karl last time ([2]) sent a mail slightly different from the
template  [3] shall I use that email as template ?

How does website staging works for Maven Core ? I see no specific
instructions here in [6], I think the directory for Maven Core staging is
[7] (According to the component-reference-documentation-helper tool).
I have also found this script from Hervé, see [9], it runs the same
commands as in the "common" procedure

Release notes:
I can't find release notes for 3.6.0 and 3.6.1 on svn [8], have the sources
been moved to another location ? on some git repo ?

Should I prepare the release notes before then I cut the release and send
the VOTE, or can I create them during the finalization of the release ?
It will take time to write those notes, but I also think that writing the
release notes helps a lot in understanding the effective contents of the
release.


I have started a new build of master branch now, in order to perform a
final check up, see[5].

I am sorry if this list was so long but I feel it is a big responsibility
to cut a release of Maven core and I want to be sure I am understanding
clearly what I am doing.

Please do not push changes to master branch and let me drive all of the
commits until the release procedure is completed.

Best regards
Enrico Olivelli


[1] https://maven.apache.org/developers/release/maven-core-release.html
[2]
https://lists.apache.org/thread.html/249091304adb6366845ba115fb3d1d9d358682630ab4a51df0d4bf67@%3Cdev.maven.apache.org%3E
[3]
https://maven.apache.org/developers/release/maven-project-release-procedure.html
[4] https://dist.apache.org/repos/dist/dev/maven/maven-3/$VERSION. Then
once the vote passed, svn move to
https://dist.apache.org/repos/dist/release/maven/maven-3/3.6.2
[5] https://builds.apache.org/job/maven-box/job/maven/job/master/279/
[6]
https://maven.apache.org/developers/website/deploy-component-reference-documentation.html
[7] https://svn.apache.org/repos/asf/maven/website/components/ref/3-LATEST/
[8] https://svn.apache.org/repos/asf/maven/site/trunk/content/markdown/docs/
[9] https://github.com/apache/maven/blob/master/deploySite.sh
[10] https://maven.apache.org/docs/3.6.1/release-notes.html

Re: Releasing Maven 3.6.2

2019-08-24 Thread Enrico Olivelli 
Il sab 24 ago 2019, 12:16 Tibor Digana  ha scritto:

> Enrico, I know that Michael mentioned some test failure but I could not
> find it in MNG-6695 because the executions 1 and 2 were deleted by 3.
> So only Michael has the resources which belong to that error.
> Michael have you investigated the error, what is it, what cause?
>


Michael merged now MNG-6695.
I will start a couple of build from master on Jenkins in order to see if we
are stable.

I will start a new thread asking for suggestions about the release process


Enrico


T
>
> On Sat, Aug 24, 2019 at 12:08 PM Enrico Olivelli 
> wrote:
>
> > Il ven 23 ago 2019, 11:55 Enrico Olivelli  ha
> > scritto:
> >
> > >
> > > I see this test failing on current master, locally on my machine
> (MacOS),
> > > this is a show stopper...
> > > I will investigate as soon as possible, but today I can't
> > >
> >
> > The test doesn't fail on my fedora box, only on Mac, consistently.
> > We are not using Mac as reference platform (only linux and Windows)
> >
> > So maybe this is not a real problem.
> > Unfortunately thus week I won't have access to any Mac box so I won't be
> > able to reproduce the problem.
> >
> > I feel we can go to the release as soon as we commit the last enhancement
> >
> > Enrico
> >
> >
> >
> > > [ERROR] Tests run: 821, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed:
> > > 1,366.325 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> > >
> > > [ERROR]
> > > testitMNG6386UnicodeChars(org.apache.maven.it
> > .MavenITmng6386BaseUriPropertyTest)
> > > Time elapsed: 1.252 s  <<< FAILURE!
> > >
> > > junit.framework.AssertionFailedError
> > >
> > > at
> > > org.apache.maven.it
> >
> .MavenITmng6386BaseUriPropertyTest.testitMNG6386UnicodeChars(MavenITmng6386BaseUriPropertyTest.java:90)
> > >
> > >
> > >
> > > Enrico
> > >
> > > Il giorno ven 23 ago 2019 alle ore 09:49 Tibor Digana <
> > > tibordig...@apache.org> ha scritto:
> > >
> > >> Yeah Enrico, go for it. ;-)
> > >> Good luck!
> > >>
> > >> T
> > >>
> > >> On Fri, Aug 23, 2019 at 7:18 AM Enrico Olivelli 
> > >> wrote:
> > >>
> > >> > Il gio 22 ago 2019, 23:42 Hervé BOUTEMY  ha
> > >> > scritto:
> > >> >
> > >> > > We have 49 issues closed and nothing remaining open [1]
> > >> > >
> > >> > > Any objection to launch the release now?
> > >> > >
> > >> > > Any volunteer?
> > >> > >
> > >> >
> > >> > I would like to try. I can do it in the weekend.
> > >> > I have only released plugins, maybe I would need some guidance
> > >> >
> > >> > Okay?
> > >> >
> > >> > Enrico
> > >> >
> > >> >
> > >> >
> > >> > > Regards,
> > >> > >
> > >> > > Hervé
> > >> > >
> > >> > > [1] https://issues.apache.org/jira/projects/MNG/versions/12345234
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > -
> > >> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > >> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >> > >
> > >> > >
> > >> >
> > >>
> > >
> >
>

Re: [VOTE] Release Maven Project Info Reports Plugin version 3.0.1

2019-08-24 Thread Tibor Digana 
that's bad. We were too fast :-)
Although my build passed but in this case as I saw the commit I have to
give my -1, sorry!

On Sat, Aug 24, 2019 at 9:41 PM Gabriel Belingueres 
wrote:

> Hi:
>
> Regarding MPIR-375, I noted that the merge of the PR into master branch
> was done *before* I made changes using PatternExcludesArtifactFilter based
> on the reviews.
>
> See https://github.com/apache/maven-project-info-reports-plugin/pull/7.
> The commit in master is:
> https://github.com/apache/maven-project-info-reports-plugin/commit/82f4bf23b79fe87d2e414c70ab2058e8f1b4146b
>
> The patch should work anyway so I decided to test it with the
> maven-shared-utils library.
> I added this to the pom.xml file (in addition to adding the
> staged-releases profile to settings.xml with the staged repo):
>
> 
>   
> 
>   org.apache.maven.plugins
>   maven-project-info-reports-plugin
>   3.0.1
>   
> 
>
> org.eclipse.m2e
> 
>   
> 
>   
> 
>
> With version 3.0.1, running 'mvn -V -Pstaged-releases clean site >
> 3.0.1.log' throws an exception. (see 3.0.1.log attached file)
>
> However, when building 3.0.2-SNAPSHOT and installing in the local repo
> (please see that in git repo there are no new commits after the 3.0.1
> release), changing the version to 3.0.2-SNAPSHOT works as expected:
>
> mvn -V -Pstaged-releases clean site > 3.0.2-SNAPSHOT.log
>
> Does anyone else is having this problem? Or am I doing something wrong?
>
> Kind regards,
> Gabriel
>
> El vie., 23 de ago. de 2019 a la(s) 16:33, Michael Osipov (
> micha...@apache.org) escribió:
>
>> Hi,
>>
>> We solved 5 issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12344828
>>
>> There are still a couple of issues left in JIRA:
>> https://issues.apache.org/jira/projects/MPIR/issues
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-1528/
>>
>> https://repository.apache.org/content/repositories/maven-1528/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.1/maven-project-info-reports-plugin-3.0.1-source-release.zip
>>
>> Source release checksum(s):
>> maven-project-info-reports-plugin-3.0.1-source-release.zip
>> sha512:
>>
>> 7145430a6999ed65a886ac503793f0aa9488b6853431c494c3dee6360c05f3db53fe46ff77bd41514002e8c320b0f4623d23b85d3a9373450c90bb713d3e50be
>>
>> Staging site:
>>
>> https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/
>>
>> Guide to testing staged releases:
>> https://maven.apache.org/guides/development/guide-testing-releases.html
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>> -
>> 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] Retire Maven OSGi

2019-08-24 Thread Hervé BOUTEMY 
+1

Regards,

Hervé

Le vendredi 23 août 2019, 15:17:23 CEST Robert Scholte a écrit :
> Hi,
> 
> The Apache Maven project consist of about 90 (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.
> 
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
> 
> I therefore propose that we retire the maven-osgi library.
> 
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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...
> 
> -
> 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 Maven Project Info Reports Plugin version 3.0.1

2019-08-24 Thread Gabriel Belingueres 
Hi:

Regarding MPIR-375, I noted that the merge of the PR into master branch was
done *before* I made changes using PatternExcludesArtifactFilter based on
the reviews.

See https://github.com/apache/maven-project-info-reports-plugin/pull/7.
The commit in master is:
https://github.com/apache/maven-project-info-reports-plugin/commit/82f4bf23b79fe87d2e414c70ab2058e8f1b4146b

The patch should work anyway so I decided to test it with the
maven-shared-utils library.
I added this to the pom.xml file (in addition to adding the staged-releases
profile to settings.xml with the staged repo):


  

  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.0.1
  


org.eclipse.m2e

  

  


With version 3.0.1, running 'mvn -V -Pstaged-releases clean site >
3.0.1.log' throws an exception. (see 3.0.1.log attached file)

However, when building 3.0.2-SNAPSHOT and installing in the local repo
(please see that in git repo there are no new commits after the 3.0.1
release), changing the version to 3.0.2-SNAPSHOT works as expected:

mvn -V -Pstaged-releases clean site > 3.0.2-SNAPSHOT.log

Does anyone else is having this problem? Or am I doing something wrong?

Kind regards,
Gabriel

El vie., 23 de ago. de 2019 a la(s) 16:33, Michael Osipov (
micha...@apache.org) escribió:

> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12344828
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MPIR/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1528/
>
> https://repository.apache.org/content/repositories/maven-1528/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.1/maven-project-info-reports-plugin-3.0.1-source-release.zip
>
> Source release checksum(s):
> maven-project-info-reports-plugin-3.0.1-source-release.zip
> sha512:
>
> 7145430a6999ed65a886ac503793f0aa9488b6853431c494c3dee6360c05f3db53fe46ff77bd41514002e8c320b0f4623d23b85d3a9373450c90bb713d3e50be
>
> Staging site:
>
> https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> 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

JDK 13 is now in the Release Candidate Phase & JDK 14 build 11 is available.

2019-08-24 Thread Rory O'Donnell 

Hi Robert ,

*JDK 13 is now in the Release Candidate Phase
*

Per the JDK 13 schedule [1], we are now in the Release Candidate phase.
The stabilization repository, jdk/jdk13, is open for P1 bug fixes per 
the JDK Release Process (JEP 3) [2].

All changes require approval via the Fix-Request Process [3].

For more details, see Mark Reinhold's email to jdk-dev mailing list [4]

 * Milestone Schedule:
 o GAC - Aug 22, 2019
 o GAR - Sept 5, 2019
 o GA - Sept 17, 2019

**OpenJDK 14 *EA build 11 is now available at **http://jdk.java.net/14**
*

 * These early access, open source builds are provided under the GNU
   General Public License, version 2, with the Classpath Exception
   .
 * Release Notes
 o http://jdk.java.net/14/release-notes
 * JEPs targeted to JDK 14
 o JEP 352  - Non-Volatile Mapped
   Byte Buffers
 * Significant changes since the last availability email:
 o Build 10
 + 8226374: Restrict TLS signature schemes and named groups
 + 8227439: Turn off AOT by default
 o Build 11
 + 8224974: Implement JEP 352
 * Changes in this build
   


*jpackage EA - **Build 1 (2019/8/20) *

 * This is an early access build of JEP 343: Packaging Tool
   , aimed at testing a prototype
   implementation of jpackage, which is a new tool for packaging
   self-contained Java applications along with a Java Runtime Environment.
 * Build 1 (2019/8/20) is now available http://jdk.java.net/jpackage/
 * Please send feedback via e-mail to core-libs-...@openjdk.java.net
   

Regards,
Rory

[1] https://openjdk.java.net/projects/jdk/13/#Schedule
[2] https://openjdk.java.net/jeps/3
[3] https://openjdk.java.net/jeps/3#Fix-Request-Process
[4] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-August/003250.html

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

Re: Releasing Maven 3.6.2

2019-08-24 Thread Tibor Digana 
Enrico, I know that Michael mentioned some test failure but I could not
find it in MNG-6695 because the executions 1 and 2 were deleted by 3.
So only Michael has the resources which belong to that error.
Michael have you investigated the error, what is it, what cause?
T

On Sat, Aug 24, 2019 at 12:08 PM Enrico Olivelli 
wrote:

> Il ven 23 ago 2019, 11:55 Enrico Olivelli  ha
> scritto:
>
> >
> > I see this test failing on current master, locally on my machine (MacOS),
> > this is a show stopper...
> > I will investigate as soon as possible, but today I can't
> >
>
> The test doesn't fail on my fedora box, only on Mac, consistently.
> We are not using Mac as reference platform (only linux and Windows)
>
> So maybe this is not a real problem.
> Unfortunately thus week I won't have access to any Mac box so I won't be
> able to reproduce the problem.
>
> I feel we can go to the release as soon as we commit the last enhancement
>
> Enrico
>
>
>
> > [ERROR] Tests run: 821, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> > 1,366.325 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> >
> > [ERROR]
> > testitMNG6386UnicodeChars(org.apache.maven.it
> .MavenITmng6386BaseUriPropertyTest)
> > Time elapsed: 1.252 s  <<< FAILURE!
> >
> > junit.framework.AssertionFailedError
> >
> > at
> > org.apache.maven.it
> .MavenITmng6386BaseUriPropertyTest.testitMNG6386UnicodeChars(MavenITmng6386BaseUriPropertyTest.java:90)
> >
> >
> >
> > Enrico
> >
> > Il giorno ven 23 ago 2019 alle ore 09:49 Tibor Digana <
> > tibordig...@apache.org> ha scritto:
> >
> >> Yeah Enrico, go for it. ;-)
> >> Good luck!
> >>
> >> T
> >>
> >> On Fri, Aug 23, 2019 at 7:18 AM Enrico Olivelli 
> >> wrote:
> >>
> >> > Il gio 22 ago 2019, 23:42 Hervé BOUTEMY  ha
> >> > scritto:
> >> >
> >> > > We have 49 issues closed and nothing remaining open [1]
> >> > >
> >> > > Any objection to launch the release now?
> >> > >
> >> > > Any volunteer?
> >> > >
> >> >
> >> > I would like to try. I can do it in the weekend.
> >> > I have only released plugins, maybe I would need some guidance
> >> >
> >> > Okay?
> >> >
> >> > Enrico
> >> >
> >> >
> >> >
> >> > > Regards,
> >> > >
> >> > > Hervé
> >> > >
> >> > > [1] https://issues.apache.org/jira/projects/MNG/versions/12345234
> >> > >
> >> > >
> >> > >
> >> > >
> -
> >> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> > > For additional commands, e-mail: dev-h...@maven.apache.org
> >> > >
> >> > >
> >> >
> >>
> >
>

Re: Releasing Maven 3.6.2

2019-08-24 Thread Enrico Olivelli 
Il ven 23 ago 2019, 11:55 Enrico Olivelli  ha scritto:

>
> I see this test failing on current master, locally on my machine (MacOS),
> this is a show stopper...
> I will investigate as soon as possible, but today I can't
>

The test doesn't fail on my fedora box, only on Mac, consistently.
We are not using Mac as reference platform (only linux and Windows)

So maybe this is not a real problem.
Unfortunately thus week I won't have access to any Mac box so I won't be
able to reproduce the problem.

I feel we can go to the release as soon as we commit the last enhancement

Enrico



> [ERROR] Tests run: 821, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 1,366.325 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
>
> [ERROR]
> testitMNG6386UnicodeChars(org.apache.maven.it.MavenITmng6386BaseUriPropertyTest)
> Time elapsed: 1.252 s  <<< FAILURE!
>
> junit.framework.AssertionFailedError
>
> at
> org.apache.maven.it.MavenITmng6386BaseUriPropertyTest.testitMNG6386UnicodeChars(MavenITmng6386BaseUriPropertyTest.java:90)
>
>
>
> Enrico
>
> Il giorno ven 23 ago 2019 alle ore 09:49 Tibor Digana <
> tibordig...@apache.org> ha scritto:
>
>> Yeah Enrico, go for it. ;-)
>> Good luck!
>>
>> T
>>
>> On Fri, Aug 23, 2019 at 7:18 AM Enrico Olivelli 
>> wrote:
>>
>> > Il gio 22 ago 2019, 23:42 Hervé BOUTEMY  ha
>> > scritto:
>> >
>> > > We have 49 issues closed and nothing remaining open [1]
>> > >
>> > > Any objection to launch the release now?
>> > >
>> > > Any volunteer?
>> > >
>> >
>> > I would like to try. I can do it in the weekend.
>> > I have only released plugins, maybe I would need some guidance
>> >
>> > Okay?
>> >
>> > Enrico
>> >
>> >
>> >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > > [1] https://issues.apache.org/jira/projects/MNG/versions/12345234
>> > >
>> > >
>> > >
>> > > -
>> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > > For additional commands, e-mail: dev-h...@maven.apache.org
>> > >
>> > >
>> >
>>
>

Re: [VOTE] Retire Maven OSGi

2019-08-24 Thread Stephane Nicoll 
+1

On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte  wrote:

> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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...
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>