[RESULT] [VOTE] Retire Maven OSGi

[Robert Scholte]

Hi,

The vote has passed with the following result:

+1: Tamás Cservenák, Anders Hammar, Tibor Digana, Karl Heinz Marbaise,  
Michael Osipov, Arnaud Héritier, Enrico Olivelli, Stephane Nicoll,  
Francois Papon, Hervé BOUTEMY


PMC quorum: reached

Special thanks to Dirk Mahler for collecting a list of projects still  
using the library.
I considered doing a final release anyway because of the provided  
information, but after having a view on the list of commits on the project  
and concluded it is still not worth it.


I will continue with the steps required to retire this library.

On Fri, 23 Aug 2019 15:17:23 +0200, 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


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

Re: Guidance for Maven Core release

[Karl Heinz Marbaise]

Hi Enrico,

On 27.08.19 18:53, Enrico Olivelli wrote:

I have created the tag so the master is ready for new commits.
I am testing the staged artifacts, It will take time.


Can you send the staged artifacts URL's so I can test too ?

Kind regards
Karl Heinz Marbaise


I will send the VOTE email as soon as I am ready.

Enrico

Il giorno dom 25 ago 2019 alle ore 20:27 Enrico Olivelli
mailto:eolive...@gmail.com>> ha scritto:

Thank you guys for your support.
I apologize, something came up, I can't start the procedure until
(hopefully) Wednesday.

I will start as soon as possible.
Please tag me if you are committing something to master branch

Cheers
Enrico

Il giorno dom 25 ago 2019 alle ore 12:53 Karl Heinz Marbaise
mailto:khmarba...@gmx.de>> ha scritto:

Hi Enrico,

On 24.08.19 23:55, Enrico Olivelli wrote:
 > 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.

No need to apologize cause based on the list you are asking you
show how
serious you are taking this ...

No problem..

As Hervé already stated go for it...

Kind regards
Karl Heinz Marbaise

 >
 > 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
 > 

Re: Guidance for Maven Core release

[Enrico Olivelli]

I have created the tag so the master is ready for new commits.
I am testing the staged artifacts, It will take time.
I will send the VOTE email as soon as I am ready.

Enrico

Il giorno dom 25 ago 2019 alle ore 20:27 Enrico Olivelli <
eolive...@gmail.com> ha scritto:

> Thank you guys for your support.
> I apologize, something came up, I can't start the procedure until
> (hopefully) Wednesday.
>
> I will start as soon as possible.
> Please tag me if you are committing something to master branch
>
> Cheers
> Enrico
>
> Il giorno dom 25 ago 2019 alle ore 12:53 Karl Heinz Marbaise <
> khmarba...@gmx.de> ha scritto:
>
>> Hi Enrico,
>>
>> On 24.08.19 23:55, Enrico Olivelli wrote:
>> > 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.
>>
>> No need to apologize cause based on the list you are asking you show how
>> serious you are taking this ...
>>
>> No problem..
>>
>> As Hervé already stated go for it...
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>> >
>> > 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: The URL appending issue and Maven Central

[Hervé BOUTEMY]

yes, if someone at Apache wants to use the new attributes in an Apache 
release, Apache Nexus Repository Manager has to be upgraded like OSSRH was

Regards,

Hervé

Le lundi 26 août 2019, 17:10:56 CEST Mirko Friedenhagen a écrit :
> Hello,
> 
> just a question: according to NEXUS-19912[1] I see the issue was fixed in
> release 2.14.4 of Nexus. Looking at https://repository.apache.org/
>  2.14.12-0 is still used. Should INFRA
> update this as well to avoid the same issue?
> 
> 
> Best Regards
> Mirko
> 
> [1] https://issues.sonatype.org/browse/NEXUS-19912
> 
> > Am 09.07.2019 um 08:16 schrieb Hervé BOUTEMY :
> > 
> > you have created MVNCENTRAL-4841 [1] issue 2 months ago: this is where to
> > ping for updates
> > 
> > Regards,
> > 
> > Hervé
> > 
> > [1] https://issues.sonatype.org/browse/MVNCENTRAL-4841
> > > 
> > Le lundi 8 juillet 2019, 12:23:57 CEST Mark Raynsford a écrit :
> >> Hello!
> >> 
> >> This is still a problem:
> >>  https://issues.apache.org/jira/browse/MNG-5951
> >>  https://issues.apache.org/jira/browse/MNG-6059
> >> 
> >> The problem isn't that the behaviour hasn't been fixed, but instead
> >> that the POM files that use the new attributes can't be deployed to
> >> Maven Central. I reported the issue to Sonatype, but it's been eight
> >> months [0] and nothing has been done about it. I think it might be case
> >> of the Sonatype people waiting to see what the Maven people will do, and
> >> the Maven people waiting to see what the Sonatype people will do. :)
> >> 
> >> I wonder if, instead, we could just turn off this URL appending
> >> behaviour with a property? Ideally the property would be specified in
> >> the POM file and the model would stay entirely backwards compatible.
> >> If you don't set the property to true, you get the old url-mangling
> >> behaviour.
> >> 
> >> 
> >> 
> >>  
> >> 
> >> true
> >> 
> >> 
> >>  ...
> >> 
> >> I'm *still* in the situation where I can either add the attributes to
> >> my projects and get correct metadata but be unable to publish to
> >> Central, or avoid using the attributes and get wildly incorrect
> >> metadata but be able to publish to Central. Both choices are
> >> pretty much unacceptable. Free to publish garbage, or prevented from
> >> publishing non-garbage!
> >> 
> >> I'd like to see some movement on this... What do I need to do to get
> >> this sorted out?
> >> 
> >> [0] https://blog.io7m.com/2018/11/23/lurking-between-releases.xhtml
> > 
> > -
> > 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: [maven-resolver] PR#39 PathRecordingDependencyVisitor to handle 3 cycles

[Tibor Digana]

I am currently preparing Surefire PR#240 (SUREFIRE-1658) for Enrico because
he comes back from vacations on Wednesday and he will perform review.
In your PR, Tomo, I planned to "play" with your code in my own IDE on my
PC. But I am not glad when I ask my ASF colleagues and they do not reply
except Michael-o.
So the PR#39 listed the requests for reviewers. I know there are vacations
but some email should be sent with a brief feedback, and that's enough.

Tomo, I will get back to your PR this week.
Cheers
Tibor17

On Tue, Aug 27, 2019 at 3:59 PM Tomo Suzuki 
wrote:

> Hi @bentmann ,
>
> Tibor17 suggested your review on this PR
> https://github.com/apache/maven-resolver/pull/39 of mine. I appreciate if
> you can take a look at it.
>
> --
> Regards,
> Tomo
>

[maven-resolver] PR#39 PathRecordingDependencyVisitor to handle 3 cycles

[Tomo Suzuki]

Hi @bentmann ,

Tibor17 suggested your review on this PR
https://github.com/apache/maven-resolver/pull/39 of mine. I appreciate if
you can take a look at it.

-- 
Regards,
Tomo