On Thu, 28 Mar 2019 at 03:14, Enrico Olivelli wrote:
> Il mer 27 mar 2019, 18:10 Tibor Digana ha
> scritto:
>
> > Enrico, what i maintenance release for you, 2.22.2-M1?
> >
>
> 2.22.2 without suffix
>
+1
@Tibor if you are too busy maybe Enrico can cut the release if he has time.
>
>
> Enrico
+1
notice that the fix in Maven core should be marked with MNG-6506 like the IT:
MNG-6543 is just a duplicate Jira entry
Regards,
Hervé
Le mardi 26 mars 2019, 21:08:24 CET Sylwester Lachiewicz a écrit :
> I'd like to merge MNG-6543 Upgrade Plexus Classwords to 2.6.0 to fix the
> problem with
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12343484
There are still a couple of issues left in JIRA:
On Wed, Mar 27, 2019 at 6:14 PM Enrico Olivelli wrote:
> Il mer 27 mar 2019, 18:10 Tibor Digana ha
> scritto:
>
> > Enrico, what i maintenance release for you, 2.22.2-M1?
> >
>
> 2.22.2 without suffix
>
>
This.
Il mer 27 mar 2019, 18:10 Tibor Digana ha scritto:
> Enrico, what i maintenance release for you, 2.22.2-M1?
>
2.22.2 without suffix
Enrico
>
>
>
>
> On Wed, Mar 27, 2019 at 6:07 PM Enrico Olivelli
> wrote:
>
> > Stephane
> > thank you so much.
> > I think we will be able to cut a
Enrico, what i maintenance release for you, 2.22.2-M1?
On Wed, Mar 27, 2019 at 6:07 PM Enrico Olivelli wrote:
> Stephane
> thank you so much.
> I think we will be able to cut a maintenaince release soon with your
> branch.
>
> Maybe you can join us in chat with
Stephane
thank you so much.
I think we will be able to cut a maintenaince release soon with your branch.
Maybe you can join us in chat with https://s.apache.org/slack-invite
#maven channel
Enrico
Il giorno mer 27 mar 2019 alle ore 15:45 Tibor Digana
ha scritto:
>
> Stephane, What exists in
Stephane, What exists in our agreement are two issues (SUREFIRE-1546 and
SUREFIRE-1614), you will have them but no multiple releases (not effective
in the perspectives of out spare time).
We need people like you who will support us in 3.0.0-M4. This is the main
goal.
The issues SUREFIRE-1546 and
This confused me too, and there are a lot of outdated docs on various
web sites that make this worse. However, that said,
1. The most current version of Aether is now the Apache Maven resolver.
2. Package name (org.eclipse) was retained when Aether was migrated
from the Eclipse Project for
Great! Thanks for your answer. I didn't imagine there's another repository
for this.
Looks like many of them are pulled in when I pull "maven-resolver-provider"
and ASF license has been applied though the package name still starts with
"org.eclipse".
While I still love to hear more information
Il mer 27 mar 2019, 08:25 Jungtaek Lim ha scritto:
> Hi devs, I'm Jungtaek Lim, PMC member of Apache Storm.
>
> Maybe it's a question for user, but mostly regarding license and migration
> status of maven-artifact so sending here. Please kindly guide me if Maven
> community think it would be
Hi devs, I'm Jungtaek Lim, PMC member of Apache Storm.
Maybe it's a question for user, but mostly regarding license and migration
status of maven-artifact so sending here. Please kindly guide me if Maven
community think it would be better to go through user mailing list.
Apache Storm leverages
On Tue, Mar 26, 2019 at 12:26 PM Tibor Digana
wrote:
> Stephane,
>
> >> I wanted to make sure that the JUnit5 story was functional
>
> I really don't like politics.
What's that supposed to mean? If you want to quote something, please quote
the full sentence. The full sentence is *"I wanted to
13 matches
Mail list logo
