Re: Enable Travis on Maven Scripting Plugin

[Hervé BOUTEMY]

Le samedi 5 janvier 2019, 08:10:51 CET Olivier Lamy a écrit :
> On Sat, 5 Jan 2019 at 12:39, Tibor Digana  wrote:
> > Manfred, did you see my comment on Slack?
> > Shortly, let's have dedicated machines just only for Maven project with
> > Infra support and one person from our team with Infra permissions just on
> > these machines. There are 6 Windows machine. So 4 Win/Ubuntu for us.
> > all: WDYT?
> 
> No way. Apache Infrastructure is a shared infrastructure. There are NO
> dedicated machine for any projects.
> The infra budget is shared between project. I'm pretty sure you will never
> convince infra of your idea...
> If you have time to waste maybe you can try but .. :)
+1

Enrico, you wrote
"I see the same setup in Zookeeper and Bookkeeper and github pr plugin works
like a charm (and I partecipated in setting it up)"

but you never gave any pointer, any demo of what Zookeeper and Bookkeeper do 
with PRs (or I overlooked the email: that may happen...)
can you show us, please?

Regards,

Hervé

> 
> > Cheers
> > Tibor
> > 
> > On Sat, Jan 5, 2019 at 12:11 AM Manfred Moser 
> > 
> > wrote:
> > > I agree with Tibor. I would rather not have to deal with two different
> > > CI
> > > systems...
> > > 
> > > Manfred
> > > 
> > > Tibor Digana wrote on 2019-01-04 14:00:
> > > > @Stephen Connolly 
> > > > After such a big investment, especially made on your side, in Jenkins
> > > > plugin you developed you do not want to support the GitHub PRs and you
> > > 
> > > just
> > > 
> > > > let be to go with TravisCI just like that? I do not think so!
> > > > T
> > > > 
> > > > 
> > > > On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly <
> > > > 
> > > > stephen.alan.conno...@gmail.com> wrote:
> > > >> +1 from me
> > > >> 
> > > >> On Fri 4 Jan 2019 at 18:21, Enrico Olivelli 
> > > 
> > > wrote:
> > > >> > Hi,
> > > >> > I would like to try out Travis on this small plugin:
> > > >> > https://github.com/apache/maven-scripting-plugin
> > > >> > 
> > > >> > I have pushed a minimal configuration file
> > > >> > I need to ask to Infra, but I need approval from the community and
> > > >> 
> > > >> PMCs...
> > > >> 
> > > >> > Can I proceed ?
> > > >> > 
> > > >> > Enrico
> > 
> > -
> > 
> > > >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > >> > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >> > 
> > > >> > --
> > > >> 
> > > >> Sent from my phone
> > > 
> > > -
> > > 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 provided dependency for child Questions

[Hervé BOUTEMY]

I think we need to have a sample project to be able to see the full tree, and 
not only the part on phoenix-core dependency

but I already have one fact to share: the issue happens not only on httpclient 
but also on junit:

[INFO] |  +- junit:junit:jar:4.12:compile
[INFO] |  |  \- org.hamcrest:hamcrest-core:jar:1.3:compile
...
[INFO] |  +- org.apache.httpcomponents:httpclient:jar:4.0.1:compile

perhaps this would be a corner case on test dependencies are impacted by 
provided scope

Regards,

Hervé

Le vendredi 4 janvier 2019, 20:59:09 CET Milan Das a écrit :
> Hello All,
> I have added provided dependency as below
> 
> 
> 
> org.apache.phoenix
> phoenix-core
> ${phoenix-provided.version}
> provided
> 
> 
> 
> 
> But when I am run (mvn dependency:tree) . I see some child libraries are
> converted to scope as compile as below ([INFO] |  +-
> org.apache.httpcomponents:httpclient:jar:4.0.1:compile). This is causing
> library conflicts. Wondering why maven is doing that ?
> 
> 
> [INFO] +- org.apache.phoenix:phoenix-core:jar:4.10.0-HBase-1.1:provided
> [INFO] |  +- org.apache.tephra:tephra-api:jar:0.9.0-incubating:provided
> [INFO] |  +- org.apache.tephra:tephra-core:jar:0.9.0-incubating:provided
> [INFO] |  |  +- com.google.code.gson:gson:jar:2.2.4:provided
> [INFO] |  |  +- com.google.inject:guice:jar:3.0:provided
> [INFO] |  |  |  +- javax.inject:javax.inject:jar:1:provided
> [INFO] |  |  |  \- aopalliance:aopalliance:jar:1.0:provided
> [INFO] |  |  +-
> com.google.inject.extensions:guice-assistedinject:jar:3.0:provided [INFO] |
>  |  +- org.apache.thrift:libthrift:jar:0.9.0:provided
> [INFO] |  |  +- it.unimi.dsi:fastutil:jar:6.5.6:provided
> [INFO] |  |  +- org.apache.twill:twill-common:jar:0.6.0-incubating:provided
> [INFO] |  |  +- org.apache.twill:twill-core:jar:0.6.0-incubating:provided
> [INFO] |  |  |  +- org.apache.twill:twill-api:jar:0.6.0-incubating:provided
> [INFO] |  |  |  \- org.ow2.asm:asm-all:jar:5.0.2:provided
> [INFO] |  |  +-
> org.apache.twill:twill-discovery-api:jar:0.6.0-incubating:provided [INFO] |
>  |  +- org.apache.twill:twill-discovery-core:jar:0.6.0-incubating:provided
> [INFO] |  |  \-
> org.apache.twill:twill-zookeeper:jar:0.6.0-incubating:provided [INFO] |  +-
> org.apache.tephra:tephra-hbase-compat-1.1:jar:0.9.0-incubating:provided
> [INFO] |  +- org.antlr:antlr-runtime:jar:3.5.2:provided
> [INFO] |  +- jline:jline:jar:2.11:provided
> [INFO] |  +- sqlline:sqlline:jar:1.2.0:provided
> [INFO] |  +- com.google.guava:guava:jar:13.0.1:provided
> [INFO] |  +- joda-time:joda-time:jar:1.6:compile
> [INFO] |  +-
> com.github.stephenc.findbugs:findbugs-annotations:jar:1.3.9-1:provided
> [INFO] |  +- com.github.stephenc.jcip:jcip-annotations:jar:1.0-1:provided
> [INFO] |  +- org.codehaus.jackson:jackson-core-asl:jar:1.9.2:provided
> [INFO] |  +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.2:provided
> [INFO] |  +- junit:junit:jar:4.12:compile
> [INFO] |  |  \- org.hamcrest:hamcrest-core:jar:1.3:compile
> [INFO] |  +- com.google.protobuf:protobuf-java:jar:2.5.0:provided
> [INFO] |  +- org.apache.httpcomponents:httpclient:jar:4.0.1:compile
> 
> 
> Thanks,
> Milan Das





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

Re: Enable Travis on Maven Scripting Plugin

[Olivier Lamy]

On Sat, 5 Jan 2019 at 12:39, Tibor Digana  wrote:

> Manfred, did you see my comment on Slack?
> Shortly, let's have dedicated machines just only for Maven project with
> Infra support and one person from our team with Infra permissions just on
> these machines. There are 6 Windows machine. So 4 Win/Ubuntu for us.
> all: WDYT?
>

No way. Apache Infrastructure is a shared infrastructure. There are NO
dedicated machine for any projects.
The infra budget is shared between project. I'm pretty sure you will never
convince infra of your idea...
If you have time to waste maybe you can try but .. :)


>
> Cheers
> Tibor
>
> On Sat, Jan 5, 2019 at 12:11 AM Manfred Moser 
> wrote:
>
> > I agree with Tibor. I would rather not have to deal with two different CI
> > systems...
> >
> > Manfred
> >
> > Tibor Digana wrote on 2019-01-04 14:00:
> >
> > > @Stephen Connolly 
> > > After such a big investment, especially made on your side, in Jenkins
> > > plugin you developed you do not want to support the GitHub PRs and you
> > just
> > > let be to go with TravisCI just like that? I do not think so!
> > > T
> > >
> > >
> > > On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly <
> > > stephen.alan.conno...@gmail.com> wrote:
> > >
> > >> +1 from me
> > >>
> > >> On Fri 4 Jan 2019 at 18:21, Enrico Olivelli 
> > wrote:
> > >>
> > >> > Hi,
> > >> > I would like to try out Travis on this small plugin:
> > >> > https://github.com/apache/maven-scripting-plugin
> > >> >
> > >> > I have pushed a minimal configuration file
> > >> > I need to ask to Infra, but I need approval from the community and
> > >> PMCs...
> > >> >
> > >> > Can I proceed ?
> > >> >
> > >> > Enrico
> > >> >
> > >> >
> -
> > >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > >> > For additional commands, e-mail: dev-h...@maven.apache.org
> > >> >
> > >> > --
> > >> Sent from my phone
> > >>
> > >
> >
> >
> > -
> > 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

Re: Enable Travis on Maven Scripting Plugin

[Stephen Connolly]

On Fri 4 Jan 2019 at 22:00, Tibor Digana  wrote:

> @Stephen Connolly 
>  After such a big investment, especially made on your side, in Jenkins
> plugin you developed you do not want to support the GitHub PRs and you just
> let be to go with TravisCI just like that? I do not think so!


I want to add GitHub support to ASF Jenkins too, but PR verification should
be layers. No harm in having one layer provided by Travis/Codeship/etc and
the second layer by Jenkins.

The other point is even if I add PR support to the ASF Jenkins, it’s not
going to be automatic build for non-committers (which is the group of PRs
that need the CI feedback most, and with least delay... ie before they walk
away) as we simply do not have throw-away infra for building PRs that could
contain bitcoin miners triggered by a unit test, etc.

Now if infra wants to set up a dedicated “safe space” for untrusted PRs to
be built... super... but until that happens, we’ll need something like
Travis to take that risk for us.


> T
>
>
> On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > +1 from me
> >
> > On Fri 4 Jan 2019 at 18:21, Enrico Olivelli  wrote:
> >
> > > Hi,
> > > I would like to try out Travis on this small plugin:
> > > https://github.com/apache/maven-scripting-plugin
> > >
> > > I have pushed a minimal configuration file
> > > I need to ask to Infra, but I need approval from the community and
> > PMCs...
> > >
> > > Can I proceed ?
> > >
> > > Enrico
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > > --
> > Sent from my phone
> >
>
-- 
Sent from my phone

Re: Enable Travis on Maven Scripting Plugin

[Tibor Digana]

Manfred, did you see my comment on Slack?
Shortly, let's have dedicated machines just only for Maven project with
Infra support and one person from our team with Infra permissions just on
these machines. There are 6 Windows machine. So 4 Win/Ubuntu for us.
all: WDYT?

Cheers
Tibor

On Sat, Jan 5, 2019 at 12:11 AM Manfred Moser 
wrote:

> I agree with Tibor. I would rather not have to deal with two different CI
> systems...
>
> Manfred
>
> Tibor Digana wrote on 2019-01-04 14:00:
>
> > @Stephen Connolly 
> > After such a big investment, especially made on your side, in Jenkins
> > plugin you developed you do not want to support the GitHub PRs and you
> just
> > let be to go with TravisCI just like that? I do not think so!
> > T
> >
> >
> > On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly <
> > stephen.alan.conno...@gmail.com> wrote:
> >
> >> +1 from me
> >>
> >> On Fri 4 Jan 2019 at 18:21, Enrico Olivelli 
> wrote:
> >>
> >> > Hi,
> >> > I would like to try out Travis on this small plugin:
> >> > https://github.com/apache/maven-scripting-plugin
> >> >
> >> > I have pushed a minimal configuration file
> >> > I need to ask to Infra, but I need approval from the community and
> >> PMCs...
> >> >
> >> > Can I proceed ?
> >> >
> >> > Enrico
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: dev-h...@maven.apache.org
> >> >
> >> > --
> >> Sent from my phone
> >>
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Enable Travis on Maven Scripting Plugin

[Manfred Moser]

I agree with Tibor. I would rather not have to deal with two different CI 
systems...

Manfred

Tibor Digana wrote on 2019-01-04 14:00:

> @Stephen Connolly 
> After such a big investment, especially made on your side, in Jenkins
> plugin you developed you do not want to support the GitHub PRs and you just
> let be to go with TravisCI just like that? I do not think so!
> T
> 
> 
> On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
> 
>> +1 from me
>>
>> On Fri 4 Jan 2019 at 18:21, Enrico Olivelli  wrote:
>>
>> > Hi,
>> > I would like to try out Travis on this small plugin:
>> > https://github.com/apache/maven-scripting-plugin
>> >
>> > I have pushed a minimal configuration file
>> > I need to ask to Infra, but I need approval from the community and
>> PMCs...
>> >
>> > Can I proceed ?
>> >
>> > Enrico
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>> > --
>> Sent from my phone
>>
> 


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

Re: Enable Travis on Maven Scripting Plugin

[Enrico Olivelli]

Thanks
I am asking INFRA to enable Travis, let's see how it works
https://issues.apache.org/jira/browse/INFRA-17554

Enrico

Il giorno ven 4 gen 2019 alle ore 23:00 Tibor Digana
 ha scritto:
>
> @Stephen Connolly 
>  After such a big investment, especially made on your side, in Jenkins
> plugin you developed you do not want to support the GitHub PRs and you just
> let be to go with TravisCI just like that? I do not think so!
> T
>
>
> On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > +1 from me
> >
> > On Fri 4 Jan 2019 at 18:21, Enrico Olivelli  wrote:
> >
> > > Hi,
> > > I would like to try out Travis on this small plugin:
> > > https://github.com/apache/maven-scripting-plugin
> > >
> > > I have pushed a minimal configuration file
> > > I need to ask to Infra, but I need approval from the community and
> > PMCs...
> > >
> > > Can I proceed ?
> > >
> > > Enrico
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > > --
> > Sent from my phone
> >

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

Re: Enable Travis on Maven Scripting Plugin

[Tibor Digana]

@Stephen Connolly 
 After such a big investment, especially made on your side, in Jenkins
plugin you developed you do not want to support the GitHub PRs and you just
let be to go with TravisCI just like that? I do not think so!
T


On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> +1 from me
>
> On Fri 4 Jan 2019 at 18:21, Enrico Olivelli  wrote:
>
> > Hi,
> > I would like to try out Travis on this small plugin:
> > https://github.com/apache/maven-scripting-plugin
> >
> > I have pushed a minimal configuration file
> > I need to ask to Infra, but I need approval from the community and
> PMCs...
> >
> > Can I proceed ?
> >
> > Enrico
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> > --
> Sent from my phone
>

Maven provided dependency for child Questions

[Milan Das]

Hello All,
I have added provided dependency as below



org.apache.phoenix
phoenix-core
${phoenix-provided.version}
provided




But when I am run (mvn dependency:tree) . I see some child libraries are 
converted to scope as compile as below ([INFO] |  +- 
org.apache.httpcomponents:httpclient:jar:4.0.1:compile). This is causing 
library conflicts. Wondering why maven is doing that ?


[INFO] +- org.apache.phoenix:phoenix-core:jar:4.10.0-HBase-1.1:provided
[INFO] |  +- org.apache.tephra:tephra-api:jar:0.9.0-incubating:provided
[INFO] |  +- org.apache.tephra:tephra-core:jar:0.9.0-incubating:provided
[INFO] |  |  +- com.google.code.gson:gson:jar:2.2.4:provided
[INFO] |  |  +- com.google.inject:guice:jar:3.0:provided
[INFO] |  |  |  +- javax.inject:javax.inject:jar:1:provided
[INFO] |  |  |  \- aopalliance:aopalliance:jar:1.0:provided
[INFO] |  |  +- 
com.google.inject.extensions:guice-assistedinject:jar:3.0:provided
[INFO] |  |  +- org.apache.thrift:libthrift:jar:0.9.0:provided
[INFO] |  |  +- it.unimi.dsi:fastutil:jar:6.5.6:provided
[INFO] |  |  +- org.apache.twill:twill-common:jar:0.6.0-incubating:provided
[INFO] |  |  +- org.apache.twill:twill-core:jar:0.6.0-incubating:provided
[INFO] |  |  |  +- org.apache.twill:twill-api:jar:0.6.0-incubating:provided
[INFO] |  |  |  \- org.ow2.asm:asm-all:jar:5.0.2:provided
[INFO] |  |  +- 
org.apache.twill:twill-discovery-api:jar:0.6.0-incubating:provided
[INFO] |  |  +- 
org.apache.twill:twill-discovery-core:jar:0.6.0-incubating:provided
[INFO] |  |  \- org.apache.twill:twill-zookeeper:jar:0.6.0-incubating:provided
[INFO] |  +- 
org.apache.tephra:tephra-hbase-compat-1.1:jar:0.9.0-incubating:provided
[INFO] |  +- org.antlr:antlr-runtime:jar:3.5.2:provided
[INFO] |  +- jline:jline:jar:2.11:provided
[INFO] |  +- sqlline:sqlline:jar:1.2.0:provided
[INFO] |  +- com.google.guava:guava:jar:13.0.1:provided
[INFO] |  +- joda-time:joda-time:jar:1.6:compile
[INFO] |  +- 
com.github.stephenc.findbugs:findbugs-annotations:jar:1.3.9-1:provided
[INFO] |  +- com.github.stephenc.jcip:jcip-annotations:jar:1.0-1:provided
[INFO] |  +- org.codehaus.jackson:jackson-core-asl:jar:1.9.2:provided
[INFO] |  +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.2:provided
[INFO] |  +- junit:junit:jar:4.12:compile
[INFO] |  |  \- org.hamcrest:hamcrest-core:jar:1.3:compile
[INFO] |  +- com.google.protobuf:protobuf-java:jar:2.5.0:provided
[INFO] |  +- org.apache.httpcomponents:httpclient:jar:4.0.1:compile


Thanks,
Milan Das

Re: Enable Travis on Maven Scripting Plugin

[Stephen Connolly]

+1 from me

On Fri 4 Jan 2019 at 18:21, Enrico Olivelli  wrote:

> Hi,
> I would like to try out Travis on this small plugin:
> https://github.com/apache/maven-scripting-plugin
>
> I have pushed a minimal configuration file
> I need to ask to Infra, but I need approval from the community and PMCs...
>
> Can I proceed ?
>
> Enrico
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

Enable Travis on Maven Scripting Plugin

[Enrico Olivelli]

Hi,
I would like to try out Travis on this small plugin:
https://github.com/apache/maven-scripting-plugin

I have pushed a minimal configuration file
I need to ask to Infra, but I need approval from the community and PMCs...

Can I proceed ?

Enrico

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

Re: JDK 12 Early Access build 26 & JDK 13 Early Access builds available

[Rory O'Donnell]

Hi Michael,

This issue is already logged, I'll let you know the JBS ID once it gets

into the JBS system.

Rgds,Rory

On 04/01/2019 10:28, Michael Osipov wrote:

Hi Rory,

can you take a look at 
https://issues.apache.org/jira/browse/MJAVADOC-561. We assume there is 
a bug in Java 11's javadoc(1) not reading the modules in element-list 
properly thus links are broken in output.


Michael

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


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


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

Re: JDK 12 Early Access build 26 & JDK 13 Early Access builds available

[Michael Osipov]

Hi Rory,

can you take a look at 
https://issues.apache.org/jira/browse/MJAVADOC-561. We assume there is a 
bug in Java 11's javadoc(1) not reading the modules in element-list 
properly thus links are broken in output.


Michael

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

JDK 12 Early Access build 26 & JDK 13 Early Access builds available

[Rory O'Donnell]

Hi Robert ,

Happy New Year!

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


 * These early-access, open-source builds are provided under the GNU
   General Public License, version 2, with the Classpath Exception
   .
 * Changes since last email
 o Distrust TLS server certificates anchored by Symantec Root CAs
   (JDK-8207258 )
 o Customizing the generation of a PKCS12 keystore (JDK-8076190
   )
 o Compact Number Formatting Support (JDK-8177552
   )

*OpenJDK builds *- JDK 13 - Early Access build 2 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 build
   


*jpackage EA builds*

 * 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.
 * Please send feedback via e-mail to core-libs-...@openjdk.java.net
   

*Quality Outreach report for December 2018*

 * The report for December 2018 is available here
   


Rgds,Rory

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

Re: [VOTE] Release Maven Wagon version 3.3.1

[Michael Osipov]

Am 2019-01-03 um 14:28 schrieb Michael Osipov:

Hi,

We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12344772 



There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved 



Staging repo:
https://repository.apache.org/content/repositories/maven-1483/
https://repository.apache.org/content/repositories/maven-1483/org/apache/maven/wagon/wagon/3.3.1/wagon-3.3.1-source-release.zip 



Source release checksum(s):
wagon-3.3.1-source-release.zip
sha512: 
398d8d028cbaff4fdc6380a105af8c2111915931db9c46f404e96c6de82b713995f3842ffd32b61e1a0b6c4249973af69a6256c160babf2d3acf7cff5417a649 



Staging site:
https://maven.apache.org/wagon-archives/wagon-LATEST/

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

Vote open for 72 hours.


+1 from me

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