Re: Regarding timestamp in _remote.repositories

[Eric Lilja]

I didn't know that the datetime string in _remote.repositories was an
artifact of the behavior of a JDK class (or Properties.store(), more
specifically). Interesting. That also implies it is not processed by
anything. Thanks.

- Eric L

On Tue, Jun 6, 2023 at 6:30 PM Michael Osipov  wrote:

> Am 2023-06-06 um 14:14 schrieb Eric Lilja:
> > Hello everyone, the timestamp (e.g., #Tue Jun 06 01:59:04 CEST 2023) in
> the
> > _remote.repositories file, is that just for human consumption or is it
> > processed? If only as a courtesy for humans, can its generation be
> disabled
> > somehow?
>
> 5 seconds of Google: https://stackoverflow.com/q/6184335/696632
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Regarding timestamp in _remote.repositories

[Eric Lilja]

Hello everyone, the timestamp (e.g., #Tue Jun 06 01:59:04 CEST 2023) in the
_remote.repositories file, is that just for human consumption or is it
processed? If only as a courtesy for humans, can its generation be disabled
somehow?

Best regards,
Eric Lilja

Re: shading in surefire

[Eric Lilja]

Are the providers leaking byte-buddy today? I just had to add explicit byte
buddy to my pom-file, for Mockito to work.

- Eric L

On Thu, Mar 9, 2023 at 2:13 PM Slawomir Jaranowski 
wrote:

> To avoid leaking external libraries to classpath used under tests.
>
> But we should only use in providers and booter in plugins. We can use what
> we need without shading.
>
> To think about what methods are used in providers, maybe we can drop it
> anyway and use standard JDK api.
>
> czw., 9 mar 2023 o 13:58 Elliotte Rusty Harold 
> napisał(a):
>
> > I'm curious. Why do we shade various libraries like commons-lang and
> > maven-shared utils in surefire?
> >
> >
> >
> https://github.com/apache/maven-surefire/blob/master/surefire-shared-utils/pom.xml
> >
> > --
> > Elliotte Rusty Harold
> > elh...@ibiblio.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> Sławomir Jaranowski
>

Re: Test problem at head: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:unpack (unpack-classes) on project plexus-utils: Artifact has not been packaged yet.

[Eric Lilja]

Just curious, why is such an old version of maven-dependency-plugin used in
that build?

- Eric L

On Sat, Feb 25, 2023 at 2:46 PM Elliotte Rusty Harold 
wrote:

> On Sat, Feb 25, 2023 at 11:46 AM Guillaume Nodet 
> wrote:
> >
> > Which goal are you running ?
> > I think you need to run the package phase as hinted by the error.
> >
>
>
> mvn test
>
> also
>
> mvn compile; mvn test
> mvn clean test
> mvn package; mvn test
>
> All end with the same failure. This seems to be a regression in 4.0. I
> don't see this on the 3.9.x branch.
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Prepare maven-plugin-tools release 3.6.2

[Eric Lilja]

Now that's a good list of changes, thank you for doing that and I'm really
looking forward to this release!

- Eric L

On Fri, Oct 22, 2021 at 10:12 AM Michael Osipov  wrote:

> Am 2021-10-22 um 07:52 schrieb Tamás Cservenák:
> > Howdy,
> >
> > I just wanted a heads up, that 3.6.2 of maven-plugin-tools is about to
> > happen soon.
> > If anyone has something more to add, please push it now.
> >
> > Planned changes (already merged):
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20fixVersion%20%3D%203.6.2
>
> *Fantastic*
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven version 3.8.2

[Eric Lilja]

Thank you for testing a bit more, Dan, I can't see anything particular on
my end either, but I don't have access to any really huge builds at
the moment, since I'm on vacation

All in all, I do however feel comfortable to vote now: +1 (non-binding)

- Eric Lilja

On Tue, Aug 10, 2021 at 10:29 AM Dan Tran  wrote:

> Further testing and comparison with current builds,  there is no concrete
> evidence of performance degradation.
>
> here is my +1 ( none binding)
>
> Sorry about noise
>
> -D
>
> On Mon, Aug 9, 2021 at 5:13 PM Dan Tran  wrote:
>
> > Hello,
> >
> >  I am not able to dedicate the time to do bisecting this issue
> >
> > -D
> >
> > On Mon, Aug 9, 2021 at 3:03 AM Eric Lilja  wrote:
> >
> >> It's an impressive list of fixes and we are many that would like to see
> a
> >> 3.8.2 release appear. Question for me is if the particular change
> >> that appears to cause a general performance degradation on the scale of
> >> ten
> >> percent is worth it (if it indeed can be isolated to particular JIRA and
> >> not due to general performance creep). No word on the bisect? I find it
> a
> >> bit hard to give a verdict now...if the fix was for a problem that only
> >> affected a small number of users, but its solution makes everyone pay a
> >> performance decrease, it might not be worth it in its current form
> >>
> >> - Eric L
> >>
> >> On Mon, Aug 9, 2021 at 11:50 AM Arnaud Héritier 
> >> wrote:
> >>
> >> > +1
> >> > Tested on several projects with no issue
> >> > I agree that the performance is a bit degraded but nothing blocker
> >> compared
> >> > the value of the fixes introduced here.
> >> >
> >> > On Sun, Aug 8, 2021 at 10:53 PM Sylwester Lachiewicz <
> >> > slachiew...@gmail.com>
> >> > wrote:
> >> >
> >> > > +1
> >> > >
> >> > > niedz., 8 sie 2021, 21:32 użytkownik Robert Scholte <
> >> > rfscho...@apache.org>
> >> > > napisał:
> >> > >
> >> > > > +1
> >> > > > On 4-8-2021 22:02:18, Michael Osipov  wrote:
> >> > > > Hi,
> >> > > >
> >> > > > We solved 68 issues:
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12349965
> >> > > >
> >> > > > There are still a couple of issues left in JIRA:
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> >> > > >
> >> > > > Staging repo:
> >> > > > https://repository.apache.org/content/repositories/maven-1657/
> >> > > >
> >> > > > Dev dist directory:
> >> > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.2/
> >> > > >
> >> > > > Source release checksums:
> >> > > > apache-maven-3.8.2-src.zip sha512:
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> 228ae07dfd89f73cc7d0b10b60708db2730465dbe6022968bde6c5d7f0df9bcd7f460fe1d8012726a29f136486bdb63d1e1ba932e307380fe4c1f4db440407dd
> >> > > > apache-maven-3.8.2-src.tar.gz sha512:
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> 617377ad85ced7961f972610ed88535fd3f1ab18e104556d8a3adee7769515ee67ee3cbaff50afcffd74a443b471b806acb1ae92f91a259bc8ccaab56795baf6
> >> > > >
> >> > > > Binary release checksums:
> >> > > > apache-maven-3.8.2-bin.zip sha512:
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> 59ad2cbd6b7abde34ebedda94ce5631256373718e71b55202035bd1190d0144f071433f78b99e16f1204413b3eb888659e5039009e1ad0106f16332e3c62bced
> >> > > > apache-maven-3.8.2-bin.tar.gz sha512:
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> b0bf39460348b2d8eae1c861ced6c3e8a077b6e761fb3d4669be5de09490521a74db294cf031b0775b2dfcd57bd82246e42ce10904063ef8e3806222e686f222
> >> > > >
> >> > > > Draft for release notes:
> >> > > > https://github.com/apache/maven-site/pull/251
> >> > > >
> >> > > >
> >> > > > Guide to testing staged releases:
> >> > > >
> >> http://maven.apache.org/guides/development/guide-testing-releases.html
> >> > > >
> >> > > > Vote open for at least 72 hours.
> >> > > >
> >> > > > [ ] +1
> >> > > > [ ] +0
> >> > > > [ ] -1
> >> > > >
> >> > > >
> >> -
> >> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> >> > > >
> >> > > >
> >> > >
> >> >
> >> >
> >> > --
> >> > Arnaud Héritier
> >> > Twitter/GitHub/... : aheritier
> >> >
> >>
> >
>

Re: [VOTE] Release Apache Maven version 3.8.2

[Eric Lilja]

It's an impressive list of fixes and we are many that would like to see a
3.8.2 release appear. Question for me is if the particular change
that appears to cause a general performance degradation on the scale of ten
percent is worth it (if it indeed can be isolated to particular JIRA and
not due to general performance creep). No word on the bisect? I find it a
bit hard to give a verdict now...if the fix was for a problem that only
affected a small number of users, but its solution makes everyone pay a
performance decrease, it might not be worth it in its current form

- Eric L

On Mon, Aug 9, 2021 at 11:50 AM Arnaud Héritier  wrote:

> +1
> Tested on several projects with no issue
> I agree that the performance is a bit degraded but nothing blocker compared
> the value of the fixes introduced here.
>
> On Sun, Aug 8, 2021 at 10:53 PM Sylwester Lachiewicz <
> slachiew...@gmail.com>
> wrote:
>
> > +1
> >
> > niedz., 8 sie 2021, 21:32 użytkownik Robert Scholte <
> rfscho...@apache.org>
> > napisał:
> >
> > > +1
> > > On 4-8-2021 22:02:18, Michael Osipov  wrote:
> > > Hi,
> > >
> > > We solved 68 issues:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12349965
> > >
> > > There are still a couple of issues left in JIRA:
> > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-1657/
> > >
> > > Dev dist directory:
> > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.2/
> > >
> > > Source release checksums:
> > > apache-maven-3.8.2-src.zip sha512:
> > >
> > >
> >
> 228ae07dfd89f73cc7d0b10b60708db2730465dbe6022968bde6c5d7f0df9bcd7f460fe1d8012726a29f136486bdb63d1e1ba932e307380fe4c1f4db440407dd
> > > apache-maven-3.8.2-src.tar.gz sha512:
> > >
> > >
> >
> 617377ad85ced7961f972610ed88535fd3f1ab18e104556d8a3adee7769515ee67ee3cbaff50afcffd74a443b471b806acb1ae92f91a259bc8ccaab56795baf6
> > >
> > > Binary release checksums:
> > > apache-maven-3.8.2-bin.zip sha512:
> > >
> > >
> >
> 59ad2cbd6b7abde34ebedda94ce5631256373718e71b55202035bd1190d0144f071433f78b99e16f1204413b3eb888659e5039009e1ad0106f16332e3c62bced
> > > apache-maven-3.8.2-bin.tar.gz sha512:
> > >
> > >
> >
> b0bf39460348b2d8eae1c861ced6c3e8a077b6e761fb3d4669be5de09490521a74db294cf031b0775b2dfcd57bd82246e42ce10904063ef8e3806222e686f222
> > >
> > > Draft for release notes:
> > > https://github.com/apache/maven-site/pull/251
> > >
> > >
> > > Guide to testing staged releases:
> > > http://maven.apache.org/guides/development/guide-testing-releases.html
> > >
> > > Vote open for at least 72 hours.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
>
>
> --
> Arnaud Héritier
> Twitter/GitHub/... : aheritier
>

Re: Maven Assembly Plugin resolves extensions of dependencies -- is this intentional?

[Eric Lilja]

For what it's worth, I noticed the same thing a while back when setting up
an offline system for a particular project at work. I was stunned at some
of the artifacts being downloaded when invoking certain plugins. Thanks for
looking into this and trying to improve the situation.

- Eric L

On Thu, Mar 11, 2021 at 4:19 PM Tamás Cservenák  wrote:

> Howdy,
>
> just a quick question, I thought someone may enlighten me...
>
> Noticed, that Maven _resolves_ and _creates extension realms_ for things I
> did not opt to at all. Typical example is nexus-staging-maven-plugin, that
> maven 3.6.3 resolves at one moment in my build, despite not using it.
>
> So, what and why is maven-assembly-plugin doing this?
>
> ===
>
> Here is an example project:
> https://github.com/cstamas/mvn-md-bug
>
> Just add new dependency in POM, jackson for example that uses extensions in
> it's own build (copy paste into POM):
>
> 
>   com.fasterxml.jackson.core
>   jackson-databind
>   2.12.2
> 
>
> use vanilla maven 3.6.3 and run `mvn clean install -X`
>
> You will notice:
> - plugin lists 3 dependencies of project (OK), 1 will be filtered out
> (junit, test scope) OK
> - and then bunch of extensions are being resolved and created and added to
> maven (gitexe, gitsite, felix bundle plugin, and so on, up to
> nexus-staging-maven-plugin).
>
> Here is a "plain" console output of the build, that creates assembly of 2
> JARs:
> https://gist.github.com/cstamas/559b8083764ee7a9c9807551b73308f3
>
> Scroll to line 834 (where massembly begins) and just watch what it
> downloads...
>
> To me, it seems like assembly is doing much-much more than it should? Or am
> unaware why dependency build extensions need to be loaded?
>
> Note: the assembly ends up OK, it has 2 jar in it.
>
> Thanks
> T
>

Re: Unexpected dependency requirement when performing "package", but not "install"

[Eric Lilja]

I just wanted to mention that I saw that a pull request containing a fix
for this nuisance was made the same day I opened the ticket in Jira. This
is impressive and very much appreciated, so thank you for that! Hoping to
see this fix in the next milestone release of Surefire, then!

Have a great week!

- Eric L

On Thu, Oct 1, 2020 at 1:49 PM Eric Lilja  wrote:

> I opened https://issues.apache.org/jira/browse/SUREFIRE-1850
>
> Thanks!
>
> - Eric L
>
> On Wed, Sep 30, 2020 at 11:30 PM Eric Lilja  wrote:
>
>> Of course, I will do it when I get to the office tomorrow, thanks!
>>
>> - Eric L
>>
>> On Wed, Sep 30, 2020 at 5:51 PM Elliotte Rusty Harold 
>> wrote:
>>
>>> Looks like we don't need that. Can you file a bug in Jira?
>>>
>>> On Wed, Sep 30, 2020 at 11:12 AM Eric Lilja 
>>> wrote:
>>> >
>>> > Hello, I have to set up Maven on a system which is completely offline,
>>> > restricted to work on a few, select projects.
>>> >
>>> > During testing, everything initially looked good, I could perform "mvn
>>> > clean install" in all projects without issue, and could perform other
>>> > Maven-task as well, Intellij was happy, it could resolve all projects
>>> > fully, run all test cases etc, and did not complain about any missing
>>> > artifacts.
>>> >
>>> > However, then I noticed, almost by accident, that I couldn't do
>>> "package"
>>> > or "verify" (which was odd, since install works, which is a later
>>> phase!),
>>> > because then surefire (3.0.0-M5) would complain it was
>>> > missing org.apache.maven:maven-toolchain:jar:3.0-alpha-2 (or one of its
>>> > dependencies).
>>> >
>>> > Why Surefire would suddenly need that artifact (some old alpha from
>>> > 2009..), during package- or verify-phase feels weird to me since the
>>> later
>>> > phase, install, works, and install entails packaging and verification
>>> > (compile also works, btw)
>>> >
>>> > surefire-3.0.0-M3 also suffers from this issue...2.18.1 does not
>>> >
>>> > What's going on here? Is my analysis correct, that if I can do "mvn
>>> clean
>>> > install", then "mvn clean package" should not be an issue, since
>>> installs
>>> > entails packaging?
>>> >
>>> > For this exotic setup, we can easily work around this, obviously, but
>>> it
>>> > feels like a bug to me so I wanted to share it with you
>>> >
>>> > - Eric L
>>>
>>>
>>>
>>> --
>>> Elliotte Rusty Harold
>>> elh...@ibiblio.org
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>

Re: Unexpected dependency requirement when performing "package", but not "install"

[Eric Lilja]

I opened https://issues.apache.org/jira/browse/SUREFIRE-1850

Thanks!

- Eric L

On Wed, Sep 30, 2020 at 11:30 PM Eric Lilja  wrote:

> Of course, I will do it when I get to the office tomorrow, thanks!
>
> - Eric L
>
> On Wed, Sep 30, 2020 at 5:51 PM Elliotte Rusty Harold 
> wrote:
>
>> Looks like we don't need that. Can you file a bug in Jira?
>>
>> On Wed, Sep 30, 2020 at 11:12 AM Eric Lilja  wrote:
>> >
>> > Hello, I have to set up Maven on a system which is completely offline,
>> > restricted to work on a few, select projects.
>> >
>> > During testing, everything initially looked good, I could perform "mvn
>> > clean install" in all projects without issue, and could perform other
>> > Maven-task as well, Intellij was happy, it could resolve all projects
>> > fully, run all test cases etc, and did not complain about any missing
>> > artifacts.
>> >
>> > However, then I noticed, almost by accident, that I couldn't do
>> "package"
>> > or "verify" (which was odd, since install works, which is a later
>> phase!),
>> > because then surefire (3.0.0-M5) would complain it was
>> > missing org.apache.maven:maven-toolchain:jar:3.0-alpha-2 (or one of its
>> > dependencies).
>> >
>> > Why Surefire would suddenly need that artifact (some old alpha from
>> > 2009..), during package- or verify-phase feels weird to me since the
>> later
>> > phase, install, works, and install entails packaging and verification
>> > (compile also works, btw)
>> >
>> > surefire-3.0.0-M3 also suffers from this issue...2.18.1 does not
>> >
>> > What's going on here? Is my analysis correct, that if I can do "mvn
>> clean
>> > install", then "mvn clean package" should not be an issue, since
>> installs
>> > entails packaging?
>> >
>> > For this exotic setup, we can easily work around this, obviously, but it
>> > feels like a bug to me so I wanted to share it with you
>> >
>> > - Eric L
>>
>>
>>
>> --
>> Elliotte Rusty Harold
>> elh...@ibiblio.org
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>

Re: Unexpected dependency requirement when performing "package", but not "install"

[Eric Lilja]

Of course, I will do it when I get to the office tomorrow, thanks!

- Eric L

On Wed, Sep 30, 2020 at 5:51 PM Elliotte Rusty Harold 
wrote:

> Looks like we don't need that. Can you file a bug in Jira?
>
> On Wed, Sep 30, 2020 at 11:12 AM Eric Lilja  wrote:
> >
> > Hello, I have to set up Maven on a system which is completely offline,
> > restricted to work on a few, select projects.
> >
> > During testing, everything initially looked good, I could perform "mvn
> > clean install" in all projects without issue, and could perform other
> > Maven-task as well, Intellij was happy, it could resolve all projects
> > fully, run all test cases etc, and did not complain about any missing
> > artifacts.
> >
> > However, then I noticed, almost by accident, that I couldn't do "package"
> > or "verify" (which was odd, since install works, which is a later
> phase!),
> > because then surefire (3.0.0-M5) would complain it was
> > missing org.apache.maven:maven-toolchain:jar:3.0-alpha-2 (or one of its
> > dependencies).
> >
> > Why Surefire would suddenly need that artifact (some old alpha from
> > 2009..), during package- or verify-phase feels weird to me since the
> later
> > phase, install, works, and install entails packaging and verification
> > (compile also works, btw)
> >
> > surefire-3.0.0-M3 also suffers from this issue...2.18.1 does not
> >
> > What's going on here? Is my analysis correct, that if I can do "mvn clean
> > install", then "mvn clean package" should not be an issue, since installs
> > entails packaging?
> >
> > For this exotic setup, we can easily work around this, obviously, but it
> > feels like a bug to me so I wanted to share it with you
> >
> > - Eric L
>
>
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Unexpected dependency requirement when performing "package", but not "install"

[Eric Lilja]

Hello, I have to set up Maven on a system which is completely offline,
restricted to work on a few, select projects.

During testing, everything initially looked good, I could perform "mvn
clean install" in all projects without issue, and could perform other
Maven-task as well, Intellij was happy, it could resolve all projects
fully, run all test cases etc, and did not complain about any missing
artifacts.

However, then I noticed, almost by accident, that I couldn't do "package"
or "verify" (which was odd, since install works, which is a later phase!),
because then surefire (3.0.0-M5) would complain it was
missing org.apache.maven:maven-toolchain:jar:3.0-alpha-2 (or one of its
dependencies).

Why Surefire would suddenly need that artifact (some old alpha from
2009..), during package- or verify-phase feels weird to me since the later
phase, install, works, and install entails packaging and verification
(compile also works, btw)

surefire-3.0.0-M3 also suffers from this issue...2.18.1 does not

What's going on here? Is my analysis correct, that if I can do "mvn clean
install", then "mvn clean package" should not be an issue, since installs
entails packaging?

For this exotic setup, we can easily work around this, obviously, but it
feels like a bug to me so I wanted to share it with you

- Eric L

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.11.3

[Eric Lilja]

Again problems with "fix version" not being set properly..seems some of the
newer contributors do not have the same WoW with regards to it as the more
senior ones, but they should.

- Eric L

On Fri, Aug 7, 2020 at 9:39 AM Robert Scholte  wrote:

> Should MDEP-708 be moved or cloned? It must be part of
> https://issues.apache.org/jira/projects/MSHARED/versions/12348642
>
> Robert
> On 5-8-2020 18:31:51, Elliotte Rusty Harold  wrote:
> Hi,
>
> We solved 2 issues:
> * [MSHARED-932] Remove JMock dependency
> * [MDEP-708] dependency:analyze should recommend narrower scope
> where possible
>
> There are still five issues left in JIRA:
>
> https://issues.apache.org/jira/browse/MSHARED-916?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20maven-dependency-analyzer
>
>
> Staging repo:
>
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/
>
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/maven-dependency-analyzer-1.11.3-source-release.zip
>
> Source release checksum(s):
> maven-dependency-analyzer-1.11.3-source-release.zip sha512:
>
> 84a13538660dd877e6ab7b626778267b4ddf06581752235e8e4e282306a6c896e7d737795a81fd05a804e77fa685ddf4891b20c73561bbc741ab671b5ccf75b8
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-dependency-analyzer-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
>
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.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 Dependency Analyzer version 1.11.2

[Eric Lilja]

On Fri, Jul 24, 2020 at 12:06 AM Sylwester Lachiewicz 
wrote:

> +1
>
> in fact, in this release, based on commits, we have also fixed:
> MSHARED-879 Reproducible builds
> MSHARED-810 Support for Java 12
> MSHARED-792 Maven Dependency Analyzer ignores Java 8 type annotations on
> local variables
>
> All the above tasks was assigned to the next planned version 3.0, now all
> fix tags where corrected.


  Vote: +1 non-binding

Thanks for highlighting this, Sylwester. I think we have the same situation
in maven-site-plugin (and maybe elsewhere). Issues fixed without a fix
version. I usually look at the next version in Jira to see what issues are
already completed to make it into the next release and what other,
non-completed issues, also share the same fix version (I know some
components have several future versions, which may have their own
issues, like Maven itself, or surefire, but most do not is my experience).
I would like to track all changes in Jira, including dependency upgrades
and would like all pull requests to have corresponding jira issue with a
fix version so it's easy to track progress and see as complete as possible
release notes. Maybe the WoW around this needs to be aligned a bit more
among the developers in the Maven dev community.

- Eric L

Re: [VOTE] Release Apache Maven Assembly Plugin version 3.3.0

[Eric Lilja]

+1 non-binding

Nice to see a release of this plugin!

- Eric Lilja

On Thu, Apr 30, 2020 at 8:09 PM Karl Heinz Marbaise 
wrote:

> Hi,
>
> +1 from me
>
>
> Kind regards
> Karl Heinz Marbaise
> On 27.04.20 20:19, Robert Scholte wrote:
> > Hi,
> >
> > We solved 10 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12344774=Text
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317220%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1568/
> >
> https://repository.apache.org/content/repositories/maven-1568/org/apache/maven/plugins/maven-assembly-plugin/3.3.0/maven-assembly-plugin-3.3.0-source-release.zip
> >
> > Source release checksum(s):
> >
> maven-assembly-plugin-3.3.0-source-release.zip sha512: 
> d41ba25dd35dea5b1b690f6cb84e4e30c5466c0e6fb3d5d98305daf70cb1ba9468c0ba2181afb8fa5f6d41c735f4f1d9d462f58eb320df0c85d57dbefa70b15a
> >
> > Staging site:
> > https://maven.apache.org/plugins-archives/maven-assembly-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
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Proposal to deprecate Maven 3.0.x

[Eric Lilja]

Well, it's been supported for five years now, which was the threshold you
mentioned to be reasonable.

- Eric L

On Thu, Apr 16, 2020 at 11:29 AM Romain Manni-Bucau 
wrote:

> Hi Eric, point is that we can't deprecate 3.3 too IMHO.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le jeu. 16 avr. 2020 à 11:18, Eric Lilja  a écrit :
>
> > But the proposal was not to deprecate 3.5, but anything below (since 3.5
> > was when the resolver was introduced)?
> >
> > - Eric L
> >
> > On Thu, Apr 16, 2020 at 11:08 AM Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > wrote:
> >
> > > Hi Tibor, technically you are likely right but deprecating is not only
> > > technical, i'd say it is only 10% of the choice (even if it is what
> > > triggers the discussion).
> > > The biggest part for me is how it affects users.
> > > 3.5.x is only 3 years old so I think it is too early to deprecate it
> > (guess
> > > we should target at least 5 years of support) so I think 3.3 can't be
> > > deprecated today but maybe in 1 or 2 years.
> > > That said we can stop supporting 3.3 for new version of plugins and
> only
> > be
> > > reactive to backport a fix if needed (it is quite rare I think). This
> way
> > > we can move forward and not send a negative message for enterprises.
> > > In other words: we support >= 3.3 but plugin upgrades  can target only
> >
> > > 3.5.
> > >
> > > Wdyt?
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > <http://rmannibucau.wordpress.com> | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > <
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > >
> > >
> > >
> > > Le jeu. 16 avr. 2020 à 10:41, Tibor Digana  a
> > > écrit :
> > >
> > > > The Eclipse Aether looks like a strong argument.
> > > > If any user would open an issue to provide a fix on the top of
> Eclipse
> > > > Aether then we say 'no' already today in 3.7.0.
> > > > So the user has to switch to 3.5.0+ which would end up for him as the
> > > > same as deprecating 3.0.x - 3.3.x.
> > > > I know that it is a big extend, i understand that but this is
> > > > currently the outcome of my analysis.
> > > >
> > > > I don't know what you think about this view.
> > > >
> > > > On Thu, Apr 16, 2020 at 8:52 AM Hervé BOUTEMY  >
> > > > wrote:
> > > > >
> > > > > +1 to deprecate 3.0.x
> > > > >
> > > > > TLDR; no need to deprecate Eclipse Aether, which would mean
> > deprecating
> > > > also
> > > > > 3.1.x, 3.2.x and 3.3.x
> > > > >
> > > > > details:
> > > > > "deprecate everything before the maven-resolver import" would mean
> > > > deprecating
> > > > > up to 3.3.x [1]
> > > > >
> > > > > Given that maven-resolver has exactly the same API as Eclipse
> Aether
> > > (in
> > > > > org.eclipse.aether java package) but just a change in Maven
> > coordinates
> > > > (that
> > > > > are all filtered by Maven core class loading, then not really an
> > > issue),
> > > > I'm
> > > > > not convinced this is absolutely necessary to go to that extend
> > > > >
> > > > > what is really useful is to deprecate anything that is not in
> > > > > org.eclipse.aether Java package, because it is a nightmare in terms
> > of
> > > > Java
> > > > > code compatibility: this means deprecating 3.0.x only [2], given
> the
> > > > switch to
> > > > > Eclipse Aether has been done in 3.1.0 [3]
> > > > > And, for the record, the switch to Maven Artifact Resolver has been
> > > done
> > > > in
> >

Re: Proposal to deprecate Maven 3.0.x

[Eric Lilja]

But the proposal was not to deprecate 3.5, but anything below (since 3.5
was when the resolver was introduced)?

- Eric L

On Thu, Apr 16, 2020 at 11:08 AM Romain Manni-Bucau 
wrote:

> Hi Tibor, technically you are likely right but deprecating is not only
> technical, i'd say it is only 10% of the choice (even if it is what
> triggers the discussion).
> The biggest part for me is how it affects users.
> 3.5.x is only 3 years old so I think it is too early to deprecate it (guess
> we should target at least 5 years of support) so I think 3.3 can't be
> deprecated today but maybe in 1 or 2 years.
> That said we can stop supporting 3.3 for new version of plugins and only be
> reactive to backport a fix if needed (it is quite rare I think). This way
> we can move forward and not send a negative message for enterprises.
> In other words: we support >= 3.3 but plugin upgrades  can target only >
> 3.5.
>
> Wdyt?
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le jeu. 16 avr. 2020 à 10:41, Tibor Digana  a
> écrit :
>
> > The Eclipse Aether looks like a strong argument.
> > If any user would open an issue to provide a fix on the top of Eclipse
> > Aether then we say 'no' already today in 3.7.0.
> > So the user has to switch to 3.5.0+ which would end up for him as the
> > same as deprecating 3.0.x - 3.3.x.
> > I know that it is a big extend, i understand that but this is
> > currently the outcome of my analysis.
> >
> > I don't know what you think about this view.
> >
> > On Thu, Apr 16, 2020 at 8:52 AM Hervé BOUTEMY 
> > wrote:
> > >
> > > +1 to deprecate 3.0.x
> > >
> > > TLDR; no need to deprecate Eclipse Aether, which would mean deprecating
> > also
> > > 3.1.x, 3.2.x and 3.3.x
> > >
> > > details:
> > > "deprecate everything before the maven-resolver import" would mean
> > deprecating
> > > up to 3.3.x [1]
> > >
> > > Given that maven-resolver has exactly the same API as Eclipse Aether
> (in
> > > org.eclipse.aether java package) but just a change in Maven coordinates
> > (that
> > > are all filtered by Maven core class loading, then not really an
> issue),
> > I'm
> > > not convinced this is absolutely necessary to go to that extend
> > >
> > > what is really useful is to deprecate anything that is not in
> > > org.eclipse.aether Java package, because it is a nightmare in terms of
> > Java
> > > code compatibility: this means deprecating 3.0.x only [2], given the
> > switch to
> > > Eclipse Aether has been done in 3.1.0 [3]
> > > And, for the record, the switch to Maven Artifact Resolver has been
> done
> > in
> > > 3.5.0 [4]
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://maven.apache.org/ref/3.3.9/dependency-management.html
> > >
> > > [2] https://maven.apache.org/ref/3.0.5/dependency-management.html
> > >
> > > [3] https://maven.apache.org/ref/3.1.0/dependency-management.html
> > >
> > > [4]
> > https://maven.apache.org/ref/3.5.0-alpha-1/dependency-management.html
> > >
> > > Le jeudi 16 avril 2020, 00:22:20 CEST Manfred Moser a écrit :
> > > > +100
> > > >
> > > > I would deprecate everything before the maven-resolver import back to
> > the
> > > > project while you are at it. Not sure exact version but 3.1x would
> > > > definitely on that list as well. Maybe also 3.2x
> > > >
> > > > Manfred
> > > >
> > > > Tibor Digana wrote on 2020-04-15 13:39 (GMT -07:00):
> > > > > Some users still use Maven 3.0.5 and they require a support for
> > > > > compatibility reasons between nowadays Maven plugins and the Maven
> > > > > 3.0.x.
> > > > >
> > > > > We have a couple of reasons to deprecate this version (JSR-330,
> > > > > Components injection, Logger) and we have discussed this issue in
> > > > > https://github.com/apache/maven-surefire/pull/274
> > > > >
> > > > > Let's discuss it.
> > > > >
> > > > > Cheers
> > > > > Tibor17
> > > > >
> > > > >
> -
> > > > > 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
> > >
> > >
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> >
> >
> > --
> > Cheers
> > Tibor
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For 

Re: [VOTE] Release Apache Maven AntRun Plugin version 3.0.0

[Eric Lilja]

I was personally hoping to see the java 8 edition of ant used, as indicated
it would be in previous email threads on this list, but +1 from me
(non-binding)

A release is greatly appreciated!

- Eric L

On Sun, Apr 12, 2020 at 10:25 PM Sylwester Lachiewicz 
wrote:

> +1
> Tested with maven-archetypes, Maven ITs, resolver-ant-tasks
>
> BR
> Sylwester
>
> niedz., 12 kwi 2020 o 09:57 Hervé BOUTEMY 
> napisał(a):
>
> > Hi,
> >
> > We solved 22 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317121=12330278=Text
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1562/
> >
> >
> https://repository.apache.org/content/repositories/maven-1562/org/apache/maven/plugins/maven-antrun-plugin/3.0.0/maven-antrun-plugin-3.0.0-source-release.zip
> >
> > Source release checksum(s):
> > maven-antrun-plugin-3.0.0-source-release.zip sha512:
> >
> 27976fb318c8481013ba89f90eba118f25bad72704b642185b5bae2d796a3f57af7eddb7f665f1db402b2351d34b7487bb28d32e01e9c0180967f64be4836725
> >
> > Staging site:
> > https://maven.apache.org/plugins-archives/maven-antrun-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
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: [VOTE] Release Apache Maven Verifier version 1.7.1

[Eric Lilja]

Ah, I see, perfect, thanks for the clarification!

- Eric L

On Fri, Apr 3, 2020 at 11:43 PM Robert Scholte  wrote:

> yes it does, but not bound to a jira issue
> On 3-4-2020 22:10:54, Eric Lilja  wrote:
> Still no parent pom update that was mentioned to, unfortunately, be missing
> in the vote for 1.7.0?
>
> - Eric L
>
> On Fri, Apr 3, 2020 at 9:36 PM Robert Scholte wrote:
>
> > Hi,
> >
> > We solved 1 issue:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12347880=Text
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20component%20%3D%20maven-verifier%20%20AND%20resolution%20%3D%20Unresolved%20%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1559/
> >
> >
> https://repository.apache.org/content/repositories/maven-1559/org/apache/maven/shared/maven-verifier/1.7.1/maven-verifier-1.7.1-source-release.zip
> >
> > Source release checksum(s):
> >
> > maven-verifier-1.7.1-source-release.zip sha512:
> 84f7d634d0dada9d08506466cfb5a066c84fce696c33116ae6decbeaba609ef864e2d8e0bacb1f08e757dcda16c61a72ac8dbffd5a0b7ce4043204f1237c7ef1
> >
> > Staging site:
> > https://maven.apache.org/shared-archives/maven-verifier-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > NOTE: maven-verifier 1.7.0 was required to have maven wrapper support,
> but
> > it introduced a bug, hence this small release.
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
>

Re: [VOTE] Release Apache Maven Verifier version 1.7.1

[Eric Lilja]

Still no parent pom update that was mentioned to, unfortunately, be missing
in the vote for 1.7.0?

- Eric L

On Fri, Apr 3, 2020 at 9:36 PM Robert Scholte  wrote:

> Hi,
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12347880=Text
>
> There are still a couple of issues left in JIRA:
>
> issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20component%20%3D%20maven-verifier%20%20AND%20resolution%20%3D%20Unresolved%20%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1559/
>
> https://repository.apache.org/content/repositories/maven-1559/org/apache/maven/shared/maven-verifier/1.7.1/maven-verifier-1.7.1-source-release.zip
>
> Source release checksum(s):
>
> maven-verifier-1.7.1-source-release.zip sha512: 
> 84f7d634d0dada9d08506466cfb5a066c84fce696c33116ae6decbeaba609ef864e2d8e0bacb1f08e757dcda16c61a72ac8dbffd5a0b7ce4043204f1237c7ef1
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-verifier-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> NOTE: maven-verifier 1.7.0 was required to have maven wrapper support, but
> it introduced a bug, hence this small release.
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

Re: maven-antrun-plugin

[Eric Lilja]

Hi!

Any update on this? At least, in Jira, I cannot see any activity regarding
issues.

- Eric L

On Mon, Mar 2, 2020 at 12:30 AM Eric Lilja  wrote:

>
>
> On Sun, Mar 1, 2020 at 4:29 PM Enrico Olivelli 
> wrote:
>
>>
>>
>> Sorry I forgot, too much time passed :)
>>
>>
> No worries, Enrico! Thanks again for this initiative, we appreciate it to
> a grea degree!
>
> By the way, I checked the summary of maven-ant-plugin on Jira [1] and
> happened to notice that it was marked as not being maintained, in June last
> year. Considering the plans in this thread, that statement should be
> removed from the Jira page, I suppose, and some of the Jiras that were
> closed at around the same time should possibly be re-opened.
>
> - Eric L
>
> [1] https://issues.apache.org/jira/projects/MANT/summary
>
>

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

[Eric Lilja]

Hi, it was  MDEP-648, which was mentioned in the previous email thread
("Trying to release maven-dependency-plugin"), the thread which I referred
to in my previous reply.

- Eric L

On Sun, Mar 8, 2020 at 3:45 PM Hervé BOUTEMY  wrote:

> you did not answer to the important part: what benefit do you expect from
> these? are you stuck by a bug?
>
> Le dimanche 8 mars 2020, 13:14:31 CET Eric Lilja a écrit :
> > It's not too late, all it takes is will, and it was feedbacked by another
> > person in the previous thread regarding the upcoming release of this
> > plugin, but his mail didn't receive a response.
> >
> > - Eric L
> >
> > On Sun, Mar 8, 2020 at 9:21 AM Hervé BOUTEMY 
> wrote:
> > > what benefit do you expect from these?
> > > are you stuck by a bug?
> > >
> > > Notice: too late for this release, this is a vote thread
> > > the feedback eventually useful here is "blocking issue found while
> ...",
> > > then
> > > the release manager can look if this is critical for any user or just
> an
> > > edge
> > > case, and choose to finish the release or cancel it
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le samedi 7 mars 2020, 19:33:47 CET Eric Lilja a écrit :
> > > > It would be very nice to release maven-artifact-transfer first (both
> > >
> > > 0.12.1
> > >
> > > > and 0.13.0 look ready in Jira, with one and two issues closed
> > >
> > > respectively,
> > >
> > > > so I would go for 0.13.0 to get all ready fixes out), and integrate
> into
> > > > this release. Please consider doing that!
> > > >
> > > > - Eric L
> > > >
> > > > On Sat, Mar 7, 2020 at 12:56 PM Karl Heinz Marbaise <
> khmarba...@gmx.de>
> > > >
> > > > wrote:
> > > > > We solved 23 issues:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227;
> > >
> > > > > version=12343772
> > >
> > > > > There are still a couple of issues left in JIRA:
> > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDEP%20AND%20re
> > >
> > >
> solution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> > >
> > > > > %2C%20updated%20DESC
> > > > >
> > > > > Staging repo:
> > > > > https://repository.apache.org/content/repositories/maven-1555
> > >
> > >
> https://repository.apache.org/content/repositories/maven-1555/org/apache/m
> > >
> > >
> aven/plugins/maven-dependency-plugin/3.1.2/maven-dependency-plugin-3.1.2-s
> > >
> > > > > ource-release.zip
> > > > >
> > > > > Source release checksum(s):
> > >
> > > > > [NAME-OF]-source-release.zip sha512:
> > >
> e06c1696842682e599c2b7e6a24c58ac0c01ae0d5bf57fcc7269a7fd11092143c598fa82f9
> > >
> > > > > 08ee181d905cb949f44515e14b7b899e5df1aa184d68d2d308f83f
> > >
> > > > > Staging site:
> > >
> https://maven.apache.org/plugins-archives/maven-dependency-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
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Another Release for Maven Dependency Plugin WAS [VOTE] Release Apache Maven Dependency Plugin version 3.1.2

[Eric Lilja]

Fair enough! The reason the plugin hadn't been released in such a long time
was what made me worried about not including fixes that seemed pretty much
good-to-go and that users had asked for, in case the slow release cycle
would to continue. Thanks for doing the release, Karl, and thanks for
sharing upcoming plans for this plugin and artifact-transfer! Looking
forward to it!

- Eric L

On Sun, Mar 8, 2020 at 1:33 PM Karl Heinz Marbaise 
wrote:

> Hi,
>
> the Apache Maven Dependency Plugin hasn't been released for a very long
> time (approx. a year) so I will finish the release first (except someone
> finds a blocking issue) and afterwards I really appreciate to work on
> another release with upgraded parts for maven-artifact-transfer
> apart from that in artifact-transfer there should be done several
> updates first and only a single release will be done for 0.13.0... and
> afterwards making a release of it ...and then integrate that into
> maven-dependency-plugin and make another release of maven dependency
> plugin.
>
>
> Kind regards
> Karl Heinz Marbaise
>
> On 07.03.20 19:33, Eric Lilja wrote:
> > It would be very nice to release maven-artifact-transfer first (both
> > 0.12.1 and 0.13.0 look ready in Jira, with one and two issues closed
> > respectively, so I would go for 0.13.0 to get all ready fixes out), and
> > integrate into this release. Please consider doing that!
> >
> > - Eric L
>

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

[Eric Lilja]

It's not too late, all it takes is will, and it was feedbacked by another
person in the previous thread regarding the upcoming release of this
plugin, but his mail didn't receive a response.

- Eric L

On Sun, Mar 8, 2020 at 9:21 AM Hervé BOUTEMY  wrote:

> what benefit do you expect from these?
> are you stuck by a bug?
>
> Notice: too late for this release, this is a vote thread
> the feedback eventually useful here is "blocking issue found while ...",
> then
> the release manager can look if this is critical for any user or just an
> edge
> case, and choose to finish the release or cancel it
>
> Regards,
>
> Hervé
>
> Le samedi 7 mars 2020, 19:33:47 CET Eric Lilja a écrit :
> > It would be very nice to release maven-artifact-transfer first (both
> 0.12.1
> > and 0.13.0 look ready in Jira, with one and two issues closed
> respectively,
> > so I would go for 0.13.0 to get all ready fixes out), and integrate into
> > this release. Please consider doing that!
> >
> > - Eric L
> >
> > On Sat, Mar 7, 2020 at 12:56 PM Karl Heinz Marbaise 
> >
> > wrote:
> > > We solved 23 issues:
> > >
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227;
> > > version=12343772
> > >
> > > There are still a couple of issues left in JIRA:
> > >
> > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDEP%20AND%20re
> > >
> solution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> > > %2C%20updated%20DESC
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-1555
> > >
> > >
> > >
> https://repository.apache.org/content/repositories/maven-1555/org/apache/m
> > >
> aven/plugins/maven-dependency-plugin/3.1.2/maven-dependency-plugin-3.1.2-s
> > > ource-release.zip
> > >
> > > Source release checksum(s):
> > > [NAME-OF]-source-release.zip sha512:
> > >
> > >
> e06c1696842682e599c2b7e6a24c58ac0c01ae0d5bf57fcc7269a7fd11092143c598fa82f9
> > > 08ee181d905cb949f44515e14b7b899e5df1aa184d68d2d308f83f
> > >
> > > Staging site:
> > >
> https://maven.apache.org/plugins-archives/maven-dependency-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 Dependency Plugin version 3.1.2

[Eric Lilja]

It would be very nice to release maven-artifact-transfer first (both 0.12.1
and 0.13.0 look ready in Jira, with one and two issues closed respectively,
so I would go for 0.13.0 to get all ready fixes out), and integrate into
this release. Please consider doing that!

- Eric L

On Sat, Mar 7, 2020 at 12:56 PM Karl Heinz Marbaise 
wrote:

> We solved 23 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12343772
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDEP%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1555
>
>
> https://repository.apache.org/content/repositories/maven-1555/org/apache/maven/plugins/maven-dependency-plugin/3.1.2/maven-dependency-plugin-3.1.2-source-release.zip
>
> Source release checksum(s):
> [NAME-OF]-source-release.zip sha512:
>
> e06c1696842682e599c2b7e6a24c58ac0c01ae0d5bf57fcc7269a7fd11092143c598fa82f908ee181d905cb949f44515e14b7b899e5df1aa184d68d2d308f83f
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-dependency-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: Maven version support

[Eric Lilja]

Seems to me that fixes are never back-ported, meaning only the latest
version of Maven is really supported. That being said, care also seems to
be taken to not make changes in plugins which break older versions of
Maven. I think you ask an important question, because trying to keep
plugins working on older versions of Maven possibly means not being able to
solve things in a way one would like to. Older versions limit choices. So
that is a cost. I don't know how many users there who insist on keeping an
older version of Maven itself but want the latest plugins..I wouldn't mind
personally if the Maven project more aggressively lifted the floor if that
means better implementations due to more freedom.

- Eric L

On Fri, Mar 6, 2020 at 2:04 PM Elliotte Rusty Harold 
wrote:

> We're coming up on the ten year anniversary of Maven 3.0.
>
> Maven 3.2.5 was, I think, the first to support Java 6.
>
> 3.3.9 is five years old.
>
> Some of our documentation still references Maven 2 and Maven 3 as if
> the difference matters. It does, but we can mostly just assume Maven
> 3, I think, and ignore Maven 2.
>
> Is it time to stop worrying about Maven 3.0 for plugin support? If so,
> what's the minimum version we should support? 3.1.0? 3.3.9? 3.5.0?
>
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: maven-antrun-plugin

[Eric Lilja]

On Sun, Mar 1, 2020 at 4:29 PM Enrico Olivelli  wrote:

>
>
> Sorry I forgot, too much time passed :)
>
>
No worries, Enrico! Thanks again for this initiative, we appreciate it to a
grea degree!

By the way, I checked the summary of maven-ant-plugin on Jira [1] and
happened to notice that it was marked as not being maintained, in June last
year. Considering the plans in this thread, that statement should be
removed from the Jira page, I suppose, and some of the Jiras that were
closed at around the same time should possibly be re-opened.

- Eric L

[1] https://issues.apache.org/jira/projects/MANT/summary

Re: maven-antrun-plugin

[Eric Lilja]

No no, not at all, if you see my first reply in this thread, I am
personally in favor of moving to latest Ant for this plugin, even if it
requires Java 8!

- Eric L

On Sun, Mar 1, 2020 at 4:19 PM Enrico Olivelli  wrote:

> Il Dom 1 Mar 2020, 16:04 Eric Lilja  ha scritto:
>
> > Oh, so ant has already been bumped to 1.9.14 (released March 2019), which
> > is the highest version of Ant not requiring java 8?
> >
>
> For other plugins, like checkstyle, we are following the main dependency,
> so if ant moved to java8 I am fine with moving to java 8 this plugin as
> well
>
> Do you have a strong reason for keeping java7?
>
> Enrico
>
>
> > - Eric L
> >
> > On Sun, Mar 1, 2020 at 3:35 PM Elliotte Rusty Harold  >
> > wrote:
> >
> > > Deps look good except for org.apache.ant which is as high as it can go
> > > without requiring Java 8.
> > >
> > > --
> > > Elliotte Rusty Harold
> > > elh...@ibiblio.org
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
>

Re: maven-antrun-plugin

[Eric Lilja]

Oh, so ant has already been bumped to 1.9.14 (released March 2019), which
is the highest version of Ant not requiring java 8?

- Eric L

On Sun, Mar 1, 2020 at 3:35 PM Elliotte Rusty Harold 
wrote:

> Deps look good except for org.apache.ant which is as high as it can go
> without requiring Java 8.
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: maven-antrun-plugin

[Eric Lilja]

  Thanks for doing this, Enrico! It would be absolutely lovely to see the
plugin uplifted to Maven 3 requirement, as the other plugins have, along
with other parent/dependency updates, as you mentioned. Also hoping to see
ant itself bumped to 1.10.7!

Thanks again!

- Eric L

On Sun, Mar 1, 2020 at 2:25 PM Enrico Olivelli  wrote:

> Shivaji
> Sorry for late reply.
> I have some troubles with my local env.
>
> I will start working on it as soon as possible.
>
> We have to check:
> - pending blocker  tickets in JIRA
> - pending pull requests
> - upgrading dependencies and parent poms
> - build ok on builds.apache.org
>
> Then we are good to go.
> Personally I am not familiar with this plugin but if the build is already
> stable and we do not have showstoppers the release procedure is quite
> straightforward
>
> Please help me with the checklist above
> I hope we can cut a release within a couple of week.
>
> And other help is very appreciated
> If any other committer that is used to use and work with this plugin wants
> to pick this release up then it is worth to think about driving the release
>
> Cheers
>
> Il Gio 27 Feb 2020, 21:57 Shivaji Thanneeru 
> ha scritto:
>
> > Enrico Olivelli
> >
> > Can you please release new version of maven-antrun plugin?
> >
> > Thanks,
> >
> > Shivaji Thanneeru
> > 610-314-9159
> >
> >
> >
> > On Fri, Dec 20, 2019 at 11:45 AM Shivaji Thanneeru <
> > shivaji.thanne...@gmail.com> wrote:
> >
> >> Ok, no problem.
> >>
> >> On Fri, Dec 20, 2019 at 11:44 AM Enrico Olivelli 
> >> wrote:
> >>
> >>> Shivaji,
> >>> Unfortunately I don't have time these days, I hope any other committer
> >>> can volunteer
> >>>
> >>> If no one volunteers I can pick this up, but in January
> >>>
> >>> Enrico
> >>>
> >>> Il ven 20 dic 2019, 17:12 Shivaji Thanneeru <
> shivaji.thanne...@gmail.com>
> >>> ha scritto:
> >>>
>  Hi,
>  MANTRUN-221 resolves a bug introduced by MANTRUN-178, where it
>  incorrectly
>  assumes that mavenProject.getProperties() will contain all properties
>  present in the session.  The PR is merged to master after it is
>  approved.
>  Please release the new version of maven-antrun-plugin as soon as
>  possible.
> 
>  Thanks,
> 
>  Shivaji Thanneeru
>  610-314-9159
> 
>  --
> >> Thanks,
> >>
> >> Shivaji Thanneeru
> >> 610-314-9159
> >>
> >>
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

Ah, yes, I do remember the changed indentation of the tag element in the
past, put I don't recall seeing that lately. Have to check tomorrow when I
get to the office.

Bernd: Which version of the maven-release-plugin did you use?

- Eric L

On Tue, Feb 4, 2020 at 8:30 PM Bernd Eckenfels 
wrote:

> Hm, for me it keeps the line breaks, it does however change the intention
> for the tag element. I thought this was configurable, but can't find it at
> the moment.
>
> Anyway this is an open (and rejected) issue:
> https://issues.apache.org/jira/browse/MRELEASE-1008
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> ____
> Von: Eric Lilja 
> Gesendet: Tuesday, February 4, 2020 3:21:51 PM
> An: Maven Developers List 
> Betreff: Prevent maven-release-plugin from reformatting attributes on
> project element
>
> Hi, we noticed that maven-release-plugin changes formatting of the project
> element, it writes the element as a single line, removing existing line
> breaks on attributes. Is it possible to make it preserve original
> formatting?
>
> We're using maven-release-plugin version 3.0.0-M1
>
> - Eric L
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

Sure! Today I did a release in a single module project. The unwanted diff
was that the release plugin changed


http://maven.apache.org/POM/4.0.0; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>

to


http://maven.apache.org/POM/4.0.0; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>

So it discarded our formatting (which had a linebreak after the
xmlns:xsi-attribute and aligned xsi:schemaLocation-attribute, column-wise,
with the xmlns-attribute, in case formatting is lost in the email) and put
all attributes on the same line as its containing element (element
"project", in this case).

I don't know if it happens only for this element or not, in our pom-files,
that is usually the only element that has so many attributes that our
formatter line splits it.

We're trying to make sure formatting is always correct in our code-base, to
get rid of unwanted noise in git diffs to make reviews smaller, that's why
this is a slight nuisance to us.

The release was done on Linux machine. All files have unix-style line
breaks, indentation is four spaces.

- Eric L

On Tue, Feb 4, 2020 at 6:47 PM Hervé BOUTEMY  wrote:

> can you provide an example of reformatting, please?
>
> in every case I saw until now, there is no reformatting, so I suppose
> you're
> in a case I did not expect
>
> Regards,
>
> Hervé
>
> Le mardi 4 février 2020, 16:24:54 CET Eric Lilja a écrit :
> > > I see.
> > > I am not aware of any such feature.
> > > If you have some tool that pretty prints XML according to your
> > > comporate rules you could invoke it in completionGoals [1]
> >
> > That could be a workaround for now. Thanks!
> >
> > - Eric L
> >
> > > Enrico
> > >
> > > [1]
> > >
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.ht
> > > ml#completionGoals
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

>
> I see.
> I am not aware of any such feature.
> If you have some tool that pretty prints XML according to your
> comporate rules you could invoke it in completionGoals [1]
>

That could be a workaround for now. Thanks!

- Eric L


>
> Enrico
>
> [1]
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#completionGoals
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

I didn't say the generated xml was invalid. It's a nuisance for us since
the formatting conflicts with our corporate settings, so we are seeing
unwelcome noise git diffs after releases.

- Eric L

On Tue, Feb 4, 2020 at 4:08 PM Enrico Olivelli  wrote:

> Eric
> What's your use case?
> As far as it creates a valid XML with the same meaning this should not be a
> problem
>
> Enrico
>
> Il Mar 4 Feb 2020, 15:22 Eric Lilja  ha scritto:
>
> > Hi, we noticed that maven-release-plugin changes formatting of the
> project
> > element, it writes the element as a single line, removing existing line
> > breaks on attributes. Is it possible to make it preserve original
> > formatting?
> >
> > We're using maven-release-plugin version 3.0.0-M1
> >
> > - Eric L
> >
>

Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

Hi, we noticed that maven-release-plugin changes formatting of the project
element, it writes the element as a single line, removing existing line
breaks on attributes. Is it possible to make it preserve original
formatting?

We're using maven-release-plugin version 3.0.0-M1

- Eric L

Re: [MCHECKSTYLE] release for upstream checkstyle

[Eric Lilja]

Which version of Checkstyle will be used for the release? 8.28?

- Eric L

On Wed, Jan 15, 2020 at 9:43 AM Enrico Olivelli  wrote:

> This is red
>
> https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/master/
>
> We need it blue :-)
>
> Enrico
>
> Il giorno mer 15 gen 2020 alle ore 07:46 Enrico Olivelli <
> eolive...@gmail.com> ha scritto:
>
> > Okay
> >
> > If No one objects I will prepare for a release.
> >
> > Currently ASF CI is not very healthy, as soon as I am confident I will
> run
> > the procedure
> >
> >
> > Enrico
> >
> >
> >
> > Il dom 12 gen 2020, 08:35 Enrico Olivelli  ha
> > scritto:
> >
> >> Ben
> >> It is a good idea.
> >>
> >> Any volunteer?
> >>
> >> Enrico
> >>
> >> Il ven 10 gen 2020, 18:46 Benjamin Marwell  ha
> >> scritto:
> >>
> >>> Hi everyone,
> >>>
> >>> since the classloader issue is resolved in the master branch, I'd like
> >>> to suggest a release before merging the violation class PR.
> >>>
> >>> The sooner the better (for the checkstyle team anyway).
> >>>
> >>> Thanks,
> >>> Ben
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: dev-h...@maven.apache.org
> >>>
> >>>
>

Re: Maven Enforcer Release-3.0.0-M3

[Eric Lilja]

I guess the reasoning goes something like this: "I am a plugin developer,
and I want to release a number of changes, a sub-set of which are "breaking
changes". Since all my changes are not ready at the same time and I want to
avoid releasing several major versions close to each other (assuming
semantic versioning is used), I use milestones, to lead up to next major".

- Eric L

On Tue, Nov 12, 2019 at 1:38 PM Enrico Olivelli  wrote:

> Il mar 12 nov 2019, 13:01 Elliotte Rusty Harold  ha
> scritto:
>
> > I'm a little nervous about this is being messages to and being
> > understood by developers. How stable is a milestone release? If it's
> > not stable, they shouldn't be seeing as abroad an adoption as they
> > are. If it is stable, then why not give it a full release as 3.0.0.
> > (or whatever) and add more in 3.1.0, 3.2.0, etc.?
> >
>
> I totally agree with this point.
> Personally I don't like milestones as we are doing with plugins, it is very
> confusing for users.
> If the plugin is good to be used in 'production' (in every day work) than
> we should not call it -Mx.
> If we know it has problems but some user needs it we can call it 'beta'.
>
> Enrico
>
>
>
>
>
>
> > On Tue, Nov 12, 2019 at 6:51 AM Tibor Digana 
> > wrote:
> > >
> > > Hi Elliotte,
> > >
> > > I am also using milestones in Surefire, as you may have noticed,
> because
> > > the complete work is too big and for one release.
> > > As for instance, milestones are fantastic for the major versions like
> in
> > > 3.0.0 because it is the only chance when you can break some backwards
> > > compatibility in plugin configuration.
> > > That's our case. For instance the system properties for config
> parameters
> > > of plugins share the same because they do not have prefixes. So i put
> the
> > > prefix in the system property and that's what i break, a little. It was
> > > just an example, but this is the principle that i understand and we
> > > untilize it in the milestones.
> > >
> > > T
> > >
> > > On Mon, Nov 11, 2019 at 7:55 PM Elliotte Rusty Harold <
> > elh...@ibiblio.org>
> > > wrote:
> > >
> > > > What is the significance of the M2/M3 classifier in the version
> > > > string? It's not obvious to me whether this is a release version or
> > > > not.
> > > >
> > > > Is there a reason not to call this simply 3.0.0 or 3.0.1?
> > > >
> > > > On Mon, Nov 11, 2019 at 1:50 PM Karl Heinz Marbaise <
> khmarba...@gmx.de
> > >
> > > > wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I've seen there are a lot of fixes in the meantime in the current
> > state
> > > > > so I would like to cut a release and the end of the week.
> > > > >
> > > > > So if someone has any objections please raise your hand.
> > > > >
> > > > > Kind regards
> > > > > Karl Heinz Marbaise
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > >
> > > >
> > > >
> > > > --
> > > > Elliotte Rusty Harold
> > > > elh...@ibiblio.org
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >
> > > >
> >
> >
> >
> > --
> > Elliotte Rusty Harold
> > elh...@ibiblio.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: [jira] [Updated] (MSHARED-841) Upgrade Commons Collections to 4.2

[Eric Lilja]

On 2019-10-19 23:55, Sylwester Lachiewicz wrote:

I always read the release notes very carefully and I don't mind seeing 
individual JIRA's per upgrade, even if does increase the length of the 
release notes. I guess others only want to see features and possibly bug 
fixes. Personally I like details. And if there is one JIRA per upgrade, 
it maps better to the git log because I don't think people are bumping 
unrelated dependencies in the same commit, right?


However, my question is why version 4.2 was selected. 4.4 is out, is 
there something broken in versions > 4.2?


- Eric L


Yes Robert, thank you for the suggestions - more changes of this type will
be combined.
Sylwester

sob., 19 paź 2019 o 22:32 Robert Scholte  napisał(a):


Maybe it is me, be I don't think having a separate jira issue for every
updated dependency adds value.
It makes the release notes unnecessary long (in a time where people
already are bad readers).
As a user I expect dependency updates to be part of every release.
1 Jira item would be good enough for me, where you sum up all dependency
changes.
Different commits can refer to the same Jira if you want.

Robert

On Sat, 19 Oct 2019 22:15:00 +0200, Sylwester Lachiewicz (Jira)
 wrote:


  [


https://issues.apache.org/jira/browse/MSHARED-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel


]

Sylwester Lachiewicz updated MSHARED-841:
-
 Fix Version/s: maven-shared-jar-3.0.0


Upgrade Commons Collections to 4.2
--

 Key: MSHARED-841
 URL: https://issues.apache.org/jira/browse/MSHARED-841
 Project: Maven Shared Components
  Issue Type: Dependency upgrade
  Components: maven-shared-jar
Reporter: Sylwester Lachiewicz
Priority: Minor
 Fix For: maven-shared-jar-3.0.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)




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

Re: when will the maven jira be ok

[Eric Lilja]

On 2019-08-22 04:39,  wrote:

Works fine for me, are you logged in?

https://issues.apache.org/jira/projects/MNG/summary

- Eric L


when will the maven jira be ok?
it has been down for several days.




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

Re: Problems with checkstyle tests on Windows (Was [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0)

[Eric Lilja]

Ah, thanks Vladimir, that's even better. I was not 100% sure it would be
possible to retain complete control over resulting line endings for those
files, regardless of user git settings of stuff like autocrlf = true and
whatnot, but it seems there is, that's great news. Thanks!

- Eric L

On Thu, Jul 18, 2019 at 2:00 PM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:

> Eric>In that case, we should generate the test files (to
> Eric>avoid git interfering), one with linux-style EOLs and one with
> Eric>Windows-style EOLs and test with both.
>
> You'd better have those files under Git control, and you could just specify
> .gitattributes so the LF file is always LF, and CRLF file is always CRLF.
>
> That is way simpler than generation of the file(s), and it is way easier to
> understand by humans
>
> Vladimir
>

Re: Problems with checkstyle tests on Windows (Was [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0)

[Eric Lilja]

Hi Enrico!

If I remember correctly, a number of weeks ago I tried using Checkstyle
8.21 with maven-checkstyle-plugin (I had simply cloned the
maven-checkstyle-plugin repository) and it did solve the problem with the
test case discussed in this thread. However, as I recall there was another,
unrelated, test that started failing with Checkstyle 8.21, which I did not
investigate. I haven't tried Checkstyle 8.22, which has been released since.

Additionally, we could be a bit more ambitious in the
file-should-end-with-newline-test, if we also want to verify it's indeed
platform-agnostic now. In that case, we should generate the test files (to
avoid git interfering), one with linux-style EOLs and one with
Windows-style EOLs and test with both.

I might give it a go to uplift Checkstyle to 8.22 and possibly expand the
test as outlined above if you think it sounds like a reasonable proposition

- Eric L

On Wed, Jul 17, 2019 at 1:32 PM Enrico Olivelli  wrote:

> Il mer 17 lug 2019, 13:28 Eric Lilja  ha scritto:
>
> > I believe, if we instead upgrade to Checkstyle 8.21 or later, we don't
> need
> > to do any of those alternative approaches.
> >
> > https://github.com/checkstyle/checkstyle/issues/4073
>
>
> Eric
> I think it is the best idea
> Do you have cycles to give it a try?
>
> Enrico
>
>
>
> >
> > - Eric L
> >
> >
> > On Wed, Jul 17, 2019 at 1:20 PM Vladimir Sitnikov <
> > sitnikov.vladi...@gmail.com> wrote:
> >
> > > Robert>A clone from Git succeeds, but the sources.zip fails.
> > > Robert>The files in the zip are generated on a unix system, so all EOLs
> > in
> > > text files are LF
> > > Robert>...
> > > Robert>The fix: add a setup.groovy to the IT and rewrite the java files
> > > with OS specific EOLs
> > >
> > > Alternative approaches:
> > > A) Provide both Linux (LF) and Windows (CRLF) source distributions
> (e.g.
> > > *.zip and *.tgz).
> > > B) Specify "lineSeparator" explicitly. Then you could have both CRLF
> and
> > LF
> > > files at the same time and verify if those work
> > > C) Generate file at the build stage. If you generate it into target/
> > > directory, then you could generate the file with appropriate for the
> > > platform enconding
> > > D) Ensure the file is always in LF or CRLF by adding a relevant
> > > .gitattributes entry
> > >
> > > Vladimir
> > >
> >
>

Re: Problems with checkstyle tests on Windows (Was [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0)

[Eric Lilja]

I believe, if we instead upgrade to Checkstyle 8.21 or later, we don't need
to do any of those alternative approaches.

https://github.com/checkstyle/checkstyle/issues/4073

- Eric L


On Wed, Jul 17, 2019 at 1:20 PM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:

> Robert>A clone from Git succeeds, but the sources.zip fails.
> Robert>The files in the zip are generated on a unix system, so all EOLs in
> text files are LF
> Robert>...
> Robert>The fix: add a setup.groovy to the IT and rewrite the java files
> with OS specific EOLs
>
> Alternative approaches:
> A) Provide both Linux (LF) and Windows (CRLF) source distributions (e.g.
> *.zip and *.tgz).
> B) Specify "lineSeparator" explicitly. Then you could have both CRLF and LF
> files at the same time and verify if those work
> C) Generate file at the build stage. If you generate it into target/
> directory, then you could generate the file with appropriate for the
> platform enconding
> D) Ensure the file is always in LF or CRLF by adding a relevant
> .gitattributes entry
>
> Vladimir
>

maven-assembly-plugin 3.1.2 release?

[Eric Lilja]

Hi! When could we see a release of maven-assembly-plugin 3.1.2? In Jira,
eight issues are associated with version 3.1.2, and they are all resolved.
We're keen to see 3.1.2 released, as it contains important dependency
upgrades, like MASSEMBLY-910 [1]

Best regards,
Eric L

[1] https://issues.apache.org/jira/browse/MASSEMBLY-910

Re: [VOTE] Release Maven Site Plugin version 3.8.1

[Eric Lilja]

+1 (non-binding)

- Eric Lilja

On Thu, Jul 4, 2019 at 10:04 PM Michael Osipov  wrote:

> Am 2019-07-03 um 23:54 schrieb Graham Leggett:
> > On 01 Jul 2019, at 23:10, Michael Osipov  wrote:
> >
> >> We solved 11 issues:
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
> >>
> >> There are still a couple of issues left in JIRA:
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-1520/
> >>
> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
> >>
> >> Source release checksum(s):
> >> maven-site-plugin-3.8.1-source-release.zip
> >> sha512:
> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
> >>
> >> Staging site:
> >> https://maven.apache.org/plugins-archives/maven-site-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
> >
> > Like last time, +1 on Java8.
> >
> > One test failed, however this test also fails in maven-site-plugin
> v3.7.1, so this is not a regression:
> >
> > [INFO] Building: effective-site/pom.xml
> > [INFO] run post-build script verify.groovy
> > [INFO]   effective-site/pom.xml ...
> FAILED (6.0 s)
> > [INFO]   The post-build script did not succeed. assert new File(
> basedir, 'effective-site.xml' ).exists()
> > | |   |
> > | |   false
> > |
>  
> /home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site
> >
>  
> /home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site/effective-site.xml
>
> Can you share why this one fails for you, but not for me on three
> different operating systems? I'd like to fix this.
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: proposal for maven-archetype to switch to dom4j 2.1.1 (and Java 8)

[Eric Lilja]

+1, people on old versions of Java can remain on the old version of the
plugin. No one who is in a project where an old version of Java is still in
use (< 8) expect to have everything else in their eco-system (3PPs, maven
plugins etc) at bleeding edge versions. I guess many such projects are many
versions behind on even supported releases...particularly regarding Maven
plugins.

- Eric L

On Mon, Jun 3, 2019 at 7:23 PM Mickael Istria  wrote:

> People who don't want to update are the ones who have to pay the effort,
> not the project that tries to ship a security fix.
> The simplest past forward is the one provided by Tony. Customers who don't
> want to use it can remain on previous version of the archetype plugins.
> Other proposals to fix it are just more time-consuming without providing
> value to Maven project.
>

Re: Problems with checkstyle tests on Windows (Was [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0)

[Eric Lilja]

Yeah, sounds like a good idea to take full control of the line breaks in
files, if they should be used to test line-break related features, since
git might convert them on certain platforms if configured to do so (I tend
to use Cygwin's git so I personally get unix-style line breaks). Looking
forward to the next release of this plugin, thanks for your work on this
and other things in the Maven ecosystem!

- Eric L

On Mon, May 27, 2019 at 10:35 PM Enrico Olivelli 
wrote:

> Il lun 27 mag 2019, 22:27 Eric Lilja  ha scritto:
>
> > I mean that we don't need to convert any line breaks in any files in
> > maven-checkstyle-plugin for the ITs to work, if we use checkstyle 8.21.
> > However, we could extend the tests for "file-ends-with-newline" to
> > explicitly cover all valid combinations of
> > system-line-break/file-line-break. Like if my system line break is
> > windows-style and the file ends with unix-style line break, the test
> should
> > pass, and vice versa. This to let the tests actually showcase (and test,
> > obviously) how the feature actually works from 8.21 onwards (look at the
> > bugifx I linked previously:
> > https://github.com/checkstyle/checkstyle/issues/4073)
> >
>
> This is the work, gently carried on by 2 guys from Checkstyle community.
>
> https://github.com/apache/maven-checkstyle-plugin/pull/16
>
> The idea is to convert a bunch of files to linux EOL. IIUC git is able to
> convert EOL automatically on windows, so having a clear convention for all
> of the files helps keeping an uniform way of dealing with this problem.
>
> The integration test about MCHECKSTYLE-54 has been changed in a way that
> now it is testing only the issue and not other stuff (like incidentally was
> checking for EOLs due to the usage of the default checkstyle rules)
>
> Thank you for continuing this discussion for the health of the project
>
> Enrico
>
>
>
>
> > - Eric L
> >
> > On Mon, May 27, 2019 at 10:17 PM Eric Lilja 
> wrote:
> >
> > > Hi Enrico! Just out of curiosity, what do you mean by " We are also
> > fixing
> > > EOL in the checkstyle plugin code base"? No change in the plugin is
> > > required with regards to EOLs to make tests pass, simply bump to
> version
> > > 8.21 of checkstyle itself (but there were two other errors, seemingly
> not
> > > related to EOL characters). Cheers!
> > >
> > > - Eric L
> > >
> > > On Mon, May 27, 2019 at 8:37 PM Enrico Olivelli 
> > > wrote:
> > >
> > >> Eric
> > >> Thank you
> > >>
> > >> We are also fixing EOL in the checkstyle plugin code base
> > >>
> > >> Enrico
> > >>
> > >>
> > >>
> > >> Il lun 27 mag 2019, 11:34 Eric Lilja  ha
> scritto:
> > >>
> > >> > Just to inform you that this problem has been resolved in version
> 8.21
> > >> of
> > >> > checkstyle, which was just released, and I've confirmed the fix
> works
> > by
> > >> > running the ITs on the checkstyle-plugin (checked out master on
> > Cygwin).
> > >> > There are two other failures, though (was one failure with 8.20 if I
> > >> recall
> > >> > correctly, apart from the EOL issue still present in that version).
> > >> >
> > >> > https://github.com/checkstyle/checkstyle/issues/4073
> > >> >
> > >> > - Eric L
> > >> >
> > >> > On Thu, May 16, 2019 at 1:33 AM Tibor Digana <
> tibordig...@apache.org>
> > >> > wrote:
> > >> >
> > >> > > Enrico, I checked the Checkstyle rules again (default value =
> > system)
> > >> and
> > >> > > Robert is right, please adjust the IT sources on the fly.
> > >> > > Not sure why INFRA or Jenkins sets the Windows EOL to LF.
> > >> > > Therefore we could not find this issue in version 3.0.0 (Jan 04)
> > >> because
> > >> > > the IT was created on Jan 17 and we run it on local Windows the
> > first
> > >> > time.
> > >> > >
> > >> > > The library is fine. I used several old versions of the plugin
> > having
> > >> > > identical results.
> > >> > > Few links:
> > >> > >
> > >> > >
> > http://checkstyle.sourceforge.net/config_misc.html#NewlineAtEndOfFile
> > >> > > 
> > >> > > http://checkstyle.sour

Re: Problems with checkstyle tests on Windows (Was [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0)

[Eric Lilja]

I mean that we don't need to convert any line breaks in any files in
maven-checkstyle-plugin for the ITs to work, if we use checkstyle 8.21.
However, we could extend the tests for "file-ends-with-newline" to
explicitly cover all valid combinations of
system-line-break/file-line-break. Like if my system line break is
windows-style and the file ends with unix-style line break, the test should
pass, and vice versa. This to let the tests actually showcase (and test,
obviously) how the feature actually works from 8.21 onwards (look at the
bugifx I linked previously:
https://github.com/checkstyle/checkstyle/issues/4073)

- Eric L

On Mon, May 27, 2019 at 10:17 PM Eric Lilja  wrote:

> Hi Enrico! Just out of curiosity, what do you mean by " We are also fixing
> EOL in the checkstyle plugin code base"? No change in the plugin is
> required with regards to EOLs to make tests pass, simply bump to version
> 8.21 of checkstyle itself (but there were two other errors, seemingly not
> related to EOL characters). Cheers!
>
> - Eric L
>
> On Mon, May 27, 2019 at 8:37 PM Enrico Olivelli 
> wrote:
>
>> Eric
>> Thank you
>>
>> We are also fixing EOL in the checkstyle plugin code base
>>
>> Enrico
>>
>>
>>
>> Il lun 27 mag 2019, 11:34 Eric Lilja  ha scritto:
>>
>> > Just to inform you that this problem has been resolved in version 8.21
>> of
>> > checkstyle, which was just released, and I've confirmed the fix works by
>> > running the ITs on the checkstyle-plugin (checked out master on Cygwin).
>> > There are two other failures, though (was one failure with 8.20 if I
>> recall
>> > correctly, apart from the EOL issue still present in that version).
>> >
>> > https://github.com/checkstyle/checkstyle/issues/4073
>> >
>> > - Eric L
>> >
>> > On Thu, May 16, 2019 at 1:33 AM Tibor Digana 
>> > wrote:
>> >
>> > > Enrico, I checked the Checkstyle rules again (default value = system)
>> and
>> > > Robert is right, please adjust the IT sources on the fly.
>> > > Not sure why INFRA or Jenkins sets the Windows EOL to LF.
>> > > Therefore we could not find this issue in version 3.0.0 (Jan 04)
>> because
>> > > the IT was created on Jan 17 and we run it on local Windows the first
>> > time.
>> > >
>> > > The library is fine. I used several old versions of the plugin having
>> > > identical results.
>> > > Few links:
>> > >
>> > > http://checkstyle.sourceforge.net/config_misc.html#NewlineAtEndOfFile
>> > > 
>> > > http://checkstyle.sourceforge.net/google_style.html
>> > >
>> > >
>> >
>> https://github.com/checkstyle/checkstyle/blob/master/src/main/resources/sun_checks.xml
>> > >
>> > >
>> >
>> https://github.com/checkstyle/checkstyle/blob/master/src/main/resources/google_checks.xml
>> > >
>> > > I expected platform independence because my company used
>> sun_checks.xml
>> > on
>> > > Windows with Unix EOL in Git/IDE without this problem.
>> > > The company improved sun_checks.xml long time ago, so I realized that
>> > later
>> > > that it is slightly different XML and different experience. Sorry.
>> > > Cheers
>> > > Tibor17
>> > >
>> > >
>> > > On Tue, May 14, 2019 at 2:11 PM Enrico Olivelli 
>> > > wrote:
>> > >
>> > > > I will get a windows box and try to reproduce.
>> > > > It is weird that on ASF Jenkins the build is passing even on windows
>> > > >
>> > > > Enrico
>> > > >
>> > > > -- Forwarded message -
>> > > > Da: Enrico Olivelli 
>> > > > Date: mar 14 mag 2019, 13:58
>> > > > Subject: Re: [VOTE] Release Apache Maven Checkstyle Plugin version
>> > 3.1.0
>> > > > To: Maven Developers List 
>> > > >
>> > > >
>> > > > Eric and Tibor,
>> > > > Thank you so much for your effort in testing Maven Checkstyle
>> Plugin.
>> > > >
>> > > > This is the "official" VOTE thread, here we have to decide if the
>> > staged
>> > > > artifacts are good to be released or not.
>> > > >
>> > > > Feel free to cast a -1 if you think that the staged artifacts are
>> not
>> > > > "stable" or there is any showstopper problem for the rele

Re: Problems with checkstyle tests on Windows (Was [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0)

[Eric Lilja]

Hi Enrico! Just out of curiosity, what do you mean by " We are also fixing
EOL in the checkstyle plugin code base"? No change in the plugin is
required with regards to EOLs to make tests pass, simply bump to version
8.21 of checkstyle itself (but there were two other errors, seemingly not
related to EOL characters). Cheers!

- Eric L

On Mon, May 27, 2019 at 8:37 PM Enrico Olivelli  wrote:

> Eric
> Thank you
>
> We are also fixing EOL in the checkstyle plugin code base
>
> Enrico
>
>
>
> Il lun 27 mag 2019, 11:34 Eric Lilja  ha scritto:
>
> > Just to inform you that this problem has been resolved in version 8.21 of
> > checkstyle, which was just released, and I've confirmed the fix works by
> > running the ITs on the checkstyle-plugin (checked out master on Cygwin).
> > There are two other failures, though (was one failure with 8.20 if I
> recall
> > correctly, apart from the EOL issue still present in that version).
> >
> > https://github.com/checkstyle/checkstyle/issues/4073
> >
> > - Eric L
> >
> > On Thu, May 16, 2019 at 1:33 AM Tibor Digana 
> > wrote:
> >
> > > Enrico, I checked the Checkstyle rules again (default value = system)
> and
> > > Robert is right, please adjust the IT sources on the fly.
> > > Not sure why INFRA or Jenkins sets the Windows EOL to LF.
> > > Therefore we could not find this issue in version 3.0.0 (Jan 04)
> because
> > > the IT was created on Jan 17 and we run it on local Windows the first
> > time.
> > >
> > > The library is fine. I used several old versions of the plugin having
> > > identical results.
> > > Few links:
> > >
> > > http://checkstyle.sourceforge.net/config_misc.html#NewlineAtEndOfFile
> > > 
> > > http://checkstyle.sourceforge.net/google_style.html
> > >
> > >
> >
> https://github.com/checkstyle/checkstyle/blob/master/src/main/resources/sun_checks.xml
> > >
> > >
> >
> https://github.com/checkstyle/checkstyle/blob/master/src/main/resources/google_checks.xml
> > >
> > > I expected platform independence because my company used sun_checks.xml
> > on
> > > Windows with Unix EOL in Git/IDE without this problem.
> > > The company improved sun_checks.xml long time ago, so I realized that
> > later
> > > that it is slightly different XML and different experience. Sorry.
> > > Cheers
> > > Tibor17
> > >
> > >
> > > On Tue, May 14, 2019 at 2:11 PM Enrico Olivelli 
> > > wrote:
> > >
> > > > I will get a windows box and try to reproduce.
> > > > It is weird that on ASF Jenkins the build is passing even on windows
> > > >
> > > > Enrico
> > > >
> > > > -- Forwarded message -
> > > > Da: Enrico Olivelli 
> > > > Date: mar 14 mag 2019, 13:58
> > > > Subject: Re: [VOTE] Release Apache Maven Checkstyle Plugin version
> > 3.1.0
> > > > To: Maven Developers List 
> > > >
> > > >
> > > > Eric and Tibor,
> > > > Thank you so much for your effort in testing Maven Checkstyle Plugin.
> > > >
> > > > This is the "official" VOTE thread, here we have to decide if the
> > staged
> > > > artifacts are good to be released or not.
> > > >
> > > > Feel free to cast a -1 if you think that the staged artifacts are not
> > > > "stable" or there is any showstopper problem for the release.
> > > >
> > > > Let's move this discussion to a separate thread, something like
> > > "Validation
> > > > failures in Windows over current checkstyle plugin master branch")
> > > >
> > > > Enrico
> > > >
> > > >
> > > >
> > > >
> > > > Il giorno mar 14 mag 2019 alle ore 13:51 Eric Lilja <
> > > mindcoo...@gmail.com>
> > > > ha scritto:
> > > >
> > > > > Tried overriding line.separator when running using
> > > -Dline.separator="\n",
> > > > > but then the builds fails (early) in maven-plugin-plugin:
> > > > > [ERROR] Failed to execute goal
> > > > > org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> > > > > (default-descriptor) on project maven-checkstyle-plugin: Execution
> > > > > default-descriptor of goal
> > > > > org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed:
>

Re: Problems with checkstyle tests on Windows (Was [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0)

[Eric Lilja]

Just to inform you that this problem has been resolved in version 8.21 of
checkstyle, which was just released, and I've confirmed the fix works by
running the ITs on the checkstyle-plugin (checked out master on Cygwin).
There are two other failures, though (was one failure with 8.20 if I recall
correctly, apart from the EOL issue still present in that version).

https://github.com/checkstyle/checkstyle/issues/4073

- Eric L

On Thu, May 16, 2019 at 1:33 AM Tibor Digana  wrote:

> Enrico, I checked the Checkstyle rules again (default value = system) and
> Robert is right, please adjust the IT sources on the fly.
> Not sure why INFRA or Jenkins sets the Windows EOL to LF.
> Therefore we could not find this issue in version 3.0.0 (Jan 04) because
> the IT was created on Jan 17 and we run it on local Windows the first time.
>
> The library is fine. I used several old versions of the plugin having
> identical results.
> Few links:
>
> http://checkstyle.sourceforge.net/config_misc.html#NewlineAtEndOfFile
> 
> http://checkstyle.sourceforge.net/google_style.html
>
> https://github.com/checkstyle/checkstyle/blob/master/src/main/resources/sun_checks.xml
>
> https://github.com/checkstyle/checkstyle/blob/master/src/main/resources/google_checks.xml
>
> I expected platform independence because my company used sun_checks.xml on
> Windows with Unix EOL in Git/IDE without this problem.
> The company improved sun_checks.xml long time ago, so I realized that later
> that it is slightly different XML and different experience. Sorry.
> Cheers
> Tibor17
>
>
> On Tue, May 14, 2019 at 2:11 PM Enrico Olivelli 
> wrote:
>
> > I will get a windows box and try to reproduce.
> > It is weird that on ASF Jenkins the build is passing even on windows
> >
> > Enrico
> >
> > -- Forwarded message -
> > Da: Enrico Olivelli 
> > Date: mar 14 mag 2019, 13:58
> > Subject: Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0
> > To: Maven Developers List 
> >
> >
> > Eric and Tibor,
> > Thank you so much for your effort in testing Maven Checkstyle Plugin.
> >
> > This is the "official" VOTE thread, here we have to decide if the staged
> > artifacts are good to be released or not.
> >
> > Feel free to cast a -1 if you think that the staged artifacts are not
> > "stable" or there is any showstopper problem for the release.
> >
> > Let's move this discussion to a separate thread, something like
> "Validation
> > failures in Windows over current checkstyle plugin master branch")
> >
> > Enrico
> >
> >
> >
> >
> > Il giorno mar 14 mag 2019 alle ore 13:51 Eric Lilja <
> mindcoo...@gmail.com>
> > ha scritto:
> >
> > > Tried overriding line.separator when running using
> -Dline.separator="\n",
> > > but then the builds fails (early) in maven-plugin-plugin:
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> > > (default-descriptor) on project maven-checkstyle-plugin: Execution
> > > default-descriptor of goal
> > > org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed:
> > > Requested line separator is invalid. -> [Help 1]
> > > [ERROR]
> > > [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> > -e
> > > switch.
> > > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > > [ERROR]
> > > [ERROR] For more information about the errors and possible solutions,
> > > please read the following articles:
> > > [ERROR] [Help 1]
> > >
> >
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> > >
> > > Tried upgrading maven-plugin-plugin to 3.6.0 (lots of stuff
> > > upgradeable...), but same error
> > >
> > > I also happened to notice this (probably unrelated, but wanted to bring
> > it
> > > to attention anyway so it can be fixed) warning:
> > > [INFO] java-annotations mojo extractor found 4 mojo descriptors.
> > > [WARNING]
> > >
> > > Unexpected situation: destinationDirectory not defined in
> > > maven-plugin-help.properties during help mojo source generation but
> > > expected during XML descriptor generation.
> > > [WARNING] Please check helpmojo goal version used in previous build
> > phase.
> > > [WARNING] If you just upgraded to plugin-tools >= 3.2 you must run a
> > clean
> > > build at least once.
> > > [WARNING] Trying defau

Re: [VOTE] Release Apache Maven WAR Plugin version 3.2.3

[Eric Lilja]

+1 (non-binding), thanks for doing the release!

- Eric Lilja

On 2019-05-23 19:55, Karl Heinz Marbaise wrote:

Hi,

We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12343424 



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



Staging repo:
https://repository.apache.org/content/repositories/maven-1505/
https://repository.apache.org/content/repositories/maven-1505/org/apache/maven/plugins/maven-war-plugin/3.2.3/maven-war-plugin-3.2.3-source-release.zip 



Source release checksum(s):
maven-war-plugin-3.2.3-source-release.zip
sha1:803bac9ea7942b84d3dd602b30b4dd58cc03a521
maven-war-plugin-3.2.3-source-release.zip sha512:
b72b7c9e4770df7dd933bef05a343cc90314f28eb5b385aa21febbadeabcf25a3e619af44c5e9d0367193e63d9ccba3c0a79775e17032272a75032489496970c 



Staging site:
https://maven.apache.org/plugins-archives/maven-war-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

maven-war-plugin 3.2.3 on vote soon?

[Eric Lilja]

Hi, in Jira there are five issues assigned to version 3.2.3, and they 
are all closed. When can we see a new release? It would be nice to get 
plexus-archiver fix out for this plugin as well! Not sure about status 
for maven-assembly-plugin and maven-javadoc-plugin, if the latest 
versions of those plugins also suffer from the bug in plexus-archiver 
(well, really in plexus-io I suppose, via plexus-archiver)


- Eric L


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

Re: [VOTE] Release Apache Maven Source Plugin version 3.1.0

[Eric Lilja]

+1 (non-binding) - nice to see this under vote!

- Eric Lilja

On Wed, May 15, 2019 at 9:58 PM Karl Heinz Marbaise 
wrote:

> Hi,
>
> We solved 11 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924=12336941
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSOURCES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1504
>
>
> https://repository.apache.org/content/repositories/maven-1504/org/apache/maven/plugins/maven-source-plugin/3.1.0/maven-source-plugin-3.1.0-source-release.zip
>
> Source release checksum(s):
> maven-source-plugin-3.1.0-source-release.zip sha1:
> 525e119423432ad850edcb308c2c15f20fd2dcbe
>
> maven-source-plugin-3.1.0-source-release.zip sha512:
>
> 9714d8e44c0e1e298190cf280694608502b3110c4077742189edc72136e733a025727092363774e51b9329df9fdd7b098795da2d3c1735c3bf926fce8d7b774b
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-source-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: Problems with checkstyle tests on Windows (Was [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0)

[Eric Lilja]

Since git settings may influence line separators when cloning and
Checkstyle seems to want read line separator to match System.lineSeparator,
maybe the test need to take full control back (from git) over the two files
in the test, to have a fully deterministic test input files.

- Eric L

On Tue, May 14, 2019 at 4:18 PM Eric Lilja  wrote:

> Hi, I edited the wrong files before when I changed line breaks (edited
> copies under target folder, silly me!). I changed the line separators to
> Windows-style for the two files under MCHECKSTYLE-54 (Mcheckstyle54.java
> and package.info) and the integration tests passes (expect for that other
> failure, MCHECKSTYLE-70-multi-sourcefolder\pom.xml, when bumping Checkstyle
> version to 8.20 I mentioned previously).
>
> Maybe your Windows node on Jenkins has git set-up to checkout files as
> \r\n, and that's why it works there (assuming the job is indeed cloning).
>
> A question I now get in my mind how that Checkstyle feature should handle
> the fact there is more than one type of line break (unfortunately) out
> there, depending on OS...
>
> - Eric L
>
>
> On Tue, May 14, 2019 at 3:08 PM Tibor Digana 
> wrote:
>
>> I wrote both files again, see the attachments (windows and Unix EOL).
>> To be faster, I am running the command *mvn checkstyle:check* from the
>> (IT target) path on my system
>> c:\vcs\github\maven-checkstyle-plugin\target\it\MCHECKSTYLE-54\src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\
>>
>> No idea why the linux EOL file fails on Windows system.
>>
>> Cheers
>> Tibor
>>
>>
>> On Tue, May 14, 2019 at 2:11 PM Enrico Olivelli 
>> wrote:
>>
>>> I will get a windows box and try to reproduce.
>>> It is weird that on ASF Jenkins the build is passing even on windows
>>>
>>> Enrico
>>>
>>> -- Forwarded message -
>>> Da: Enrico Olivelli 
>>> Date: mar 14 mag 2019, 13:58
>>> Subject: Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0
>>> To: Maven Developers List 
>>>
>>>
>>> Eric and Tibor,
>>> Thank you so much for your effort in testing Maven Checkstyle Plugin.
>>>
>>> This is the "official" VOTE thread, here we have to decide if the staged
>>> artifacts are good to be released or not.
>>>
>>> Feel free to cast a -1 if you think that the staged artifacts are not
>>> "stable" or there is any showstopper problem for the release.
>>>
>>> Let's move this discussion to a separate thread, something like
>>> "Validation
>>> failures in Windows over current checkstyle plugin master branch")
>>>
>>> Enrico
>>>
>>>
>>>
>>>
>>> Il giorno mar 14 mag 2019 alle ore 13:51 Eric Lilja <
>>> mindcoo...@gmail.com>
>>> ha scritto:
>>>
>>> > Tried overriding line.separator when running using
>>> -Dline.separator="\n",
>>> > but then the builds fails (early) in maven-plugin-plugin:
>>> > [ERROR] Failed to execute goal
>>> > org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
>>> > (default-descriptor) on project maven-checkstyle-plugin: Execution
>>> > default-descriptor of goal
>>> > org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed:
>>> > Requested line separator is invalid. -> [Help 1]
>>> > [ERROR]
>>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>>> the -e
>>> > switch.
>>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> > [ERROR]
>>> > [ERROR] For more information about the errors and possible solutions,
>>> > please read the following articles:
>>> > [ERROR] [Help 1]
>>> >
>>> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
>>> >
>>> > Tried upgrading maven-plugin-plugin to 3.6.0 (lots of stuff
>>> > upgradeable...), but same error
>>> >
>>> > I also happened to notice this (probably unrelated, but wanted to
>>> bring it
>>> > to attention anyway so it can be fixed) warning:
>>> > [INFO] java-annotations mojo extractor found 4 mojo descriptors.
>>> > [WARNING]
>>> >
>>> > Unexpected situation: destinationDirectory not defined in
>>> > maven-plugin-help.properties during help mojo source generation but
>>> > expected during XML descriptor generation.
>>

Re: Problems with checkstyle tests on Windows (Was [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0)

[Eric Lilja]

Hi, I edited the wrong files before when I changed line breaks (edited
copies under target folder, silly me!). I changed the line separators to
Windows-style for the two files under MCHECKSTYLE-54 (Mcheckstyle54.java
and package.info) and the integration tests passes (expect for that other
failure, MCHECKSTYLE-70-multi-sourcefolder\pom.xml, when bumping Checkstyle
version to 8.20 I mentioned previously).

Maybe your Windows node on Jenkins has git set-up to checkout files as
\r\n, and that's why it works there (assuming the job is indeed cloning).

A question I now get in my mind how that Checkstyle feature should handle
the fact there is more than one type of line break (unfortunately) out
there, depending on OS...

- Eric L


On Tue, May 14, 2019 at 3:08 PM Tibor Digana  wrote:

> I wrote both files again, see the attachments (windows and Unix EOL).
> To be faster, I am running the command *mvn checkstyle:check* from the (IT
> target) path on my system
> c:\vcs\github\maven-checkstyle-plugin\target\it\MCHECKSTYLE-54\src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\
>
> No idea why the linux EOL file fails on Windows system.
>
> Cheers
> Tibor
>
>
> On Tue, May 14, 2019 at 2:11 PM Enrico Olivelli 
> wrote:
>
>> I will get a windows box and try to reproduce.
>> It is weird that on ASF Jenkins the build is passing even on windows
>>
>> Enrico
>>
>> -- Forwarded message -
>> Da: Enrico Olivelli 
>> Date: mar 14 mag 2019, 13:58
>> Subject: Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0
>> To: Maven Developers List 
>>
>>
>> Eric and Tibor,
>> Thank you so much for your effort in testing Maven Checkstyle Plugin.
>>
>> This is the "official" VOTE thread, here we have to decide if the staged
>> artifacts are good to be released or not.
>>
>> Feel free to cast a -1 if you think that the staged artifacts are not
>> "stable" or there is any showstopper problem for the release.
>>
>> Let's move this discussion to a separate thread, something like
>> "Validation
>> failures in Windows over current checkstyle plugin master branch")
>>
>> Enrico
>>
>>
>>
>>
>> Il giorno mar 14 mag 2019 alle ore 13:51 Eric Lilja > >
>> ha scritto:
>>
>> > Tried overriding line.separator when running using
>> -Dline.separator="\n",
>> > but then the builds fails (early) in maven-plugin-plugin:
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
>> > (default-descriptor) on project maven-checkstyle-plugin: Execution
>> > default-descriptor of goal
>> > org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed:
>> > Requested line separator is invalid. -> [Help 1]
>> > [ERROR]
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e
>> > switch.
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> > [ERROR]
>> > [ERROR] For more information about the errors and possible solutions,
>> > please read the following articles:
>> > [ERROR] [Help 1]
>> >
>> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
>> >
>> > Tried upgrading maven-plugin-plugin to 3.6.0 (lots of stuff
>> > upgradeable...), but same error
>> >
>> > I also happened to notice this (probably unrelated, but wanted to bring
>> it
>> > to attention anyway so it can be fixed) warning:
>> > [INFO] java-annotations mojo extractor found 4 mojo descriptors.
>> > [WARNING]
>> >
>> > Unexpected situation: destinationDirectory not defined in
>> > maven-plugin-help.properties during help mojo source generation but
>> > expected during XML descriptor generation.
>> > [WARNING] Please check helpmojo goal version used in previous build
>> phase.
>> > [WARNING] If you just upgraded to plugin-tools >= 3.2 you must run a
>> clean
>> > build at least once.
>> > [WARNING] Trying default location: target\generated-sources\plugin
>> >
>> > - Eric L
>> >
>> > On Tue, May 14, 2019 at 11:04 AM Eric Lilja 
>> wrote:
>> >
>> > > I tried bumping checkstyle to 8.20, plus a few of the plexus
>> > dependencies,
>> > > but that just brought an additional failure... (to
>> > > MCHECKSTYLE-70-multi-sourcefolder\pom.xml)  :-)
>> > >
>> > > I suppose the problem might be that the files has l

Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0

[Eric Lilja]

Tried overriding line.separator when running using -Dline.separator="\n",
but then the builds fails (early) in maven-plugin-plugin:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
(default-descriptor) on project maven-checkstyle-plugin: Execution
default-descriptor of goal
org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed:
Requested line separator is invalid. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException

Tried upgrading maven-plugin-plugin to 3.6.0 (lots of stuff
upgradeable...), but same error

I also happened to notice this (probably unrelated, but wanted to bring it
to attention anyway so it can be fixed) warning:
[INFO] java-annotations mojo extractor found 4 mojo descriptors.
[WARNING]

Unexpected situation: destinationDirectory not defined in
maven-plugin-help.properties during help mojo source generation but
expected during XML descriptor generation.
[WARNING] Please check helpmojo goal version used in previous build phase.
[WARNING] If you just upgraded to plugin-tools >= 3.2 you must run a clean
build at least once.
[WARNING] Trying default location: target\generated-sources\plugin

- Eric L

On Tue, May 14, 2019 at 11:04 AM Eric Lilja  wrote:

> I tried bumping checkstyle to 8.20, plus a few of the plexus dependencies,
> but that just brought an additional failure... (to
> MCHECKSTYLE-70-multi-sourcefolder\pom.xml)  :-)
>
> I suppose the problem might be that the files has linux-style line breaks
> (this is desired for me, I don't want to convert to windows-style line
> breaks locally), but the test think I should have windows-style line
> separators. It seems these files are generated by the tests because I tried
> changing them to Windows style line breaks for re-running just to see if
> that would work, but those changes were overwritten)
>
> - Eric L
>
> On Tue, May 14, 2019 at 10:38 AM Eric Lilja  wrote:
>
>> I also see a failure for MCHECKSTYLE-54 on Windows. (Sorry, I didn't try
>> the source zip, just cloned master)
>>
>> I tested on one of our corporate laptops:
>> Windows 10
>> Cygwin 64-bit (I use it to clone the repo and use Maven)
>> Maven 3.6.0
>> Java 8 update 202
>>
>> The build log says:
>> [INFO] There are 2 errors reported by Checkstyle 8.19 with sun_checks.xml
>> ruleset.
>> [ERROR]
>> src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\Mcheckstyle54.java:[1]
>> (misc) NewlineAtEndOfFile: File does not end with a newline.
>> [ERROR]
>> src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\package-info.java:[1]
>> (misc) NewlineAtEndOfFile: File does not end with a newline.
>>
>> These two files end with unix-style line breaks (as expected with my
>> setup).
>>
>> - Eric L
>>
>>
>> On Tue, May 14, 2019 at 8:10 AM Enrico Olivelli 
>> wrote:
>>
>>> Il lun 13 mag 2019, 23:48 Tibor Digana  ha
>>> scritto:
>>>
>>> > Robert, I did *not* use the source zip.
>>> >
>>>
>>> IMHO we should vote on the staged zip
>>>
>>>
>>> > git clone https://gitbox.apache.org/repos/asf/maven-checkstyle-plugin
>>> > Oracle jdk 1.8.0u212, Maven 3.3.9, Windows 10
>>> >
>>>
>>> This is what CI does and tests are passing.
>>>
>>> Do you have some global git configuration?
>>>
>>> Enrico
>>>
>>> >
>>> > I see there is a new line, but the checkstyle does not care if you put
>>> one
>>> > or two lines.
>>> > No idea why.
>>> >
>>> > Even if you go to the target and run it from the folder
>>> > c:\vcs\github\maven-checkstyle-plugin\target\it\MCHECKSTYLE-54\
>>> > it's the same as if you run the project root - mvn verify -P
>>> > run-its,quality-checks
>>> >
>>> >
>>> > *mvn -nsu checkstyle:check*
>>> >
>>> > [INFO] --- maven-checkstyle-plugin:3.1.1-SNAPSHOT:check (default-cli) @
>>> > mcheckstyle-54 ---
>>> > [INFO] There are 2 errors reported by Checkstyle 8.19 with
>>> sun_checks.xml
>>> > ruleset.
>>> > [ERROR]
>>> >
>>> >
>>> src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\Mcheckstyle54.java:[1]
>>> >

Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0

[Eric Lilja]

I tried bumping checkstyle to 8.20, plus a few of the plexus dependencies,
but that just brought an additional failure... (to
MCHECKSTYLE-70-multi-sourcefolder\pom.xml)  :-)

I suppose the problem might be that the files has linux-style line breaks
(this is desired for me, I don't want to convert to windows-style line
breaks locally), but the test think I should have windows-style line
separators. It seems these files are generated by the tests because I tried
changing them to Windows style line breaks for re-running just to see if
that would work, but those changes were overwritten)

- Eric L

On Tue, May 14, 2019 at 10:38 AM Eric Lilja  wrote:

> I also see a failure for MCHECKSTYLE-54 on Windows. (Sorry, I didn't try
> the source zip, just cloned master)
>
> I tested on one of our corporate laptops:
> Windows 10
> Cygwin 64-bit (I use it to clone the repo and use Maven)
> Maven 3.6.0
> Java 8 update 202
>
> The build log says:
> [INFO] There are 2 errors reported by Checkstyle 8.19 with sun_checks.xml
> ruleset.
> [ERROR]
> src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\Mcheckstyle54.java:[1]
> (misc) NewlineAtEndOfFile: File does not end with a newline.
> [ERROR]
> src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\package-info.java:[1]
> (misc) NewlineAtEndOfFile: File does not end with a newline.
>
> These two files end with unix-style line breaks (as expected with my
> setup).
>
> - Eric L
>
>
> On Tue, May 14, 2019 at 8:10 AM Enrico Olivelli 
> wrote:
>
>> Il lun 13 mag 2019, 23:48 Tibor Digana  ha
>> scritto:
>>
>> > Robert, I did *not* use the source zip.
>> >
>>
>> IMHO we should vote on the staged zip
>>
>>
>> > git clone https://gitbox.apache.org/repos/asf/maven-checkstyle-plugin
>> > Oracle jdk 1.8.0u212, Maven 3.3.9, Windows 10
>> >
>>
>> This is what CI does and tests are passing.
>>
>> Do you have some global git configuration?
>>
>> Enrico
>>
>> >
>> > I see there is a new line, but the checkstyle does not care if you put
>> one
>> > or two lines.
>> > No idea why.
>> >
>> > Even if you go to the target and run it from the folder
>> > c:\vcs\github\maven-checkstyle-plugin\target\it\MCHECKSTYLE-54\
>> > it's the same as if you run the project root - mvn verify -P
>> > run-its,quality-checks
>> >
>> >
>> > *mvn -nsu checkstyle:check*
>> >
>> > [INFO] --- maven-checkstyle-plugin:3.1.1-SNAPSHOT:check (default-cli) @
>> > mcheckstyle-54 ---
>> > [INFO] There are 2 errors reported by Checkstyle 8.19 with
>> sun_checks.xml
>> > ruleset.
>> > [ERROR]
>> >
>> >
>> src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\Mcheckstyle54.java:[1]
>> > (misc) NewlineAtEndOfFile: File does not end with a newline.
>> > [ERROR]
>> >
>> >
>> src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\package-info.java:[1]
>> > (misc) NewlineAtEndOfFile: File does not end with a newline.
>> > [INFO]
>> > 
>> > [INFO] BUILD FAILURE
>> > [INFO]
>> > 
>> > [INFO] Total time: 3.450 s
>> > [INFO] Finished at: 2019-05-13T23:42:55+02:00
>> > [INFO] Final Memory: 12M/193M
>> > [INFO]
>> > 
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1-SNAPSHOT:check
>> > (default-cli) on project mcheckstyle-54: You have 2 Checkstyle
>> violations.
>> > -> [Help 1]
>> > [ERROR]
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e
>> > switch.
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> > [ERROR]
>> > [ERROR] For more information about the errors and possible solutions,
>> > please read the following articles:
>> > [ERROR] [Help 1]
>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>> >
>> >
>> > On Mon, May 13, 2019 at 10:29 PM Robert Scholte 
>> > wrote:
>> >
>> > > This can happen when source-release.zip was created on a different OS
>> > > compared to the verifying OS.
>> > >
>> > > With Git it will switch to the line endings of the operating system,
>> but
>> &

Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.0

[Eric Lilja]

I also see a failure for MCHECKSTYLE-54 on Windows. (Sorry, I didn't try
the source zip, just cloned master)

I tested on one of our corporate laptops:
Windows 10
Cygwin 64-bit (I use it to clone the repo and use Maven)
Maven 3.6.0
Java 8 update 202

The build log says:
[INFO] There are 2 errors reported by Checkstyle 8.19 with sun_checks.xml
ruleset.
[ERROR]
src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\Mcheckstyle54.java:[1]
(misc) NewlineAtEndOfFile: File does not end with a newline.
[ERROR]
src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\package-info.java:[1]
(misc) NewlineAtEndOfFile: File does not end with a newline.

These two files end with unix-style line breaks (as expected with my setup).

- Eric L


On Tue, May 14, 2019 at 8:10 AM Enrico Olivelli  wrote:

> Il lun 13 mag 2019, 23:48 Tibor Digana  ha
> scritto:
>
> > Robert, I did *not* use the source zip.
> >
>
> IMHO we should vote on the staged zip
>
>
> > git clone https://gitbox.apache.org/repos/asf/maven-checkstyle-plugin
> > Oracle jdk 1.8.0u212, Maven 3.3.9, Windows 10
> >
>
> This is what CI does and tests are passing.
>
> Do you have some global git configuration?
>
> Enrico
>
> >
> > I see there is a new line, but the checkstyle does not care if you put
> one
> > or two lines.
> > No idea why.
> >
> > Even if you go to the target and run it from the folder
> > c:\vcs\github\maven-checkstyle-plugin\target\it\MCHECKSTYLE-54\
> > it's the same as if you run the project root - mvn verify -P
> > run-its,quality-checks
> >
> >
> > *mvn -nsu checkstyle:check*
> >
> > [INFO] --- maven-checkstyle-plugin:3.1.1-SNAPSHOT:check (default-cli) @
> > mcheckstyle-54 ---
> > [INFO] There are 2 errors reported by Checkstyle 8.19 with sun_checks.xml
> > ruleset.
> > [ERROR]
> >
> >
> src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\Mcheckstyle54.java:[1]
> > (misc) NewlineAtEndOfFile: File does not end with a newline.
> > [ERROR]
> >
> >
> src\main\java\org\apache\maven\plugins\checkstyle\mcheckstyle54\package-info.java:[1]
> > (misc) NewlineAtEndOfFile: File does not end with a newline.
> > [INFO]
> > 
> > [INFO] BUILD FAILURE
> > [INFO]
> > 
> > [INFO] Total time: 3.450 s
> > [INFO] Finished at: 2019-05-13T23:42:55+02:00
> > [INFO] Final Memory: 12M/193M
> > [INFO]
> > 
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1-SNAPSHOT:check
> > (default-cli) on project mcheckstyle-54: You have 2 Checkstyle
> violations.
> > -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> >
> >
> > On Mon, May 13, 2019 at 10:29 PM Robert Scholte 
> > wrote:
> >
> > > This can happen when source-release.zip was created on a different OS
> > > compared to the verifying OS.
> > >
> > > With Git it will switch to the line endings of the operating system,
> but
> > > with a zip that's not possible.
> > >
> > > I'd say not blocking, but the IT needs to be fixed to handle these
> > > situations.
> > >
> > > Robert
> > >
> > >
> > > On Mon, 13 May 2019 21:55:27 +0200, Enrico Olivelli <
> eolive...@gmail.com
> > >
> > >
> > > wrote:
> > >
> > > > Tibor
> > > > It is strage all its are passing on CI.
> > > > Are you sure you have correcly unpacked the package?
> > > >
> > > >
> > > > Il lun 13 mag 2019, 21:23 Tibor Digana  ha
> > > > scritto:
> > > >
> > > >> checked the sha512 of src zip, ok
> > > >> checked the build, failed (mvn verify -P run-its,quality-checks)
> > > >>
> > > >
> > > > What is 'quality-checks' profile? I have never heard about it
> > > >
> > > > Enrico
> > > >
> > > >
> > > >> [INFO] Building: MCHECKSTYLE-54\pom.xml
> > > >> [INFO]   MCHECKSTYLE-54\pom.xml ...
> > > >> FAILED
> > > >> (5.3 s)
> > > >>
> > > >> *Mcheckstyle54.java:[1] (misc) NewlineAtEndOfFile: File does not end
> > > >> with a
> > > >> newline.*
> > > >>
> > > >> but I checkted this file and it ends with a new line. Is it bug in
> the
> > > >> Checkstyle dependency?
> > > >>
> > > >> [INFO] BUILD FAILURE
> > > >> [ERROR] Failed to execute goal
> > > >> org.apache.maven.plugins:maven-pmd-plugin:3.8:cpd-check (cpd-check)
> on
> > > >> project maven-checkstyle-plugin: You have 1 CPD duplication.
> > > >>
> > > >> There are exactly the same methods. That's why CPD fails, see
> > > >> CheckstyleViolationCheckMojo L813
> > > >> AbstractCheckstyleReportL581
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>

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: [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=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: Regarding MJAR-259 and MSOURCES-119

[Eric Lilja]

Hi, and thanks for the answers! We (and many others I'm sure) are happy to
see new releases as soon as possible, of course :-)

Anders: Thanks for the workaround, I implemented it in our corporate pom
for maven-jar-plugin and maven-source-plugin, plus maven-javadoc-plugin.
Then I wiped out .m2/repository and built the corporate parent and then one
of our smaller projects (which had been changed to use the new parent
version). I could see it downloaded version 4.1.0 of plexus-archiver, along
with 3.3, 3.4, 3.5, 3.6.0, and 3.7.0 (it was  simple mvn clean install,
which also builds a source-jar and javadocs).

However, when I do: dependency:resolve-plugins, I get:
[INFO]
org.apache.maven.plugins:maven-jar-plugin:maven-plugin:3.1.1:runtime
[INFO]   org.apache.maven.plugins:maven-jar-plugin:jar:3.1.1
[INFO]   org.apache.maven:maven-plugin-api:jar:3.0
[INFO]   org.apache.maven:maven-model:jar:3.0
[INFO]   org.sonatype.sisu:sisu-inject-plexus:jar:1.4.2
[INFO]   org.sonatype.sisu:sisu-inject-bean:jar:1.4.2
[INFO]   org.sonatype.sisu:sisu-guice:jar:noaop:2.1.7
[INFO]   org.apache.maven:maven-core:jar:3.0
[INFO]   org.apache.maven:maven-settings:jar:3.0
[INFO]   org.apache.maven:maven-settings-builder:jar:3.0
[INFO]   org.apache.maven:maven-repository-metadata:jar:3.0
[INFO]   org.apache.maven:maven-model-builder:jar:3.0
[INFO]   org.apache.maven:maven-aether-provider:jar:3.0
[INFO]   org.sonatype.aether:aether-impl:jar:1.7
[INFO]   org.sonatype.aether:aether-spi:jar:1.7
[INFO]   org.sonatype.aether:aether-api:jar:1.7
[INFO]   org.sonatype.aether:aether-util:jar:1.7
[INFO]   org.codehaus.plexus:plexus-interpolation:jar:1.14
[INFO]   org.codehaus.plexus:plexus-classworlds:jar:2.2.3
[INFO]   org.codehaus.plexus:plexus-component-annotations:jar:1.7.1
[INFO]   org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3
[INFO]   org.sonatype.plexus:plexus-cipher:jar:1.4
[INFO]   org.apache.maven:maven-artifact:jar:3.0
[INFO]   org.apache.maven:maven-archiver:jar:3.3.0
[INFO]   org.apache.maven.shared:maven-shared-utils:jar:3.2.1
[INFO]   commons-io:commons-io:jar:2.5
[INFO]   org.codehaus.plexus:plexus-archiver:jar:3.7.0 <--
[INFO]   org.codehaus.plexus:plexus-io:jar:3.1.0
[INFO]   org.apache.commons:commons-compress:jar:1.18
[INFO]   org.iq80.snappy:snappy:jar:0.4
[INFO]   org.tukaani:xz:jar:1.8
[INFO]   org.codehaus.plexus:plexus-utils:jar:3.1.0

Here's it still listing 3.7.0 of plexus-archiver, did it not work or does
dependency:resolve-plugins fail to pick up version overrides? Same behavior
for maven-source-plugin and maven-javadoc-plugin, both list their original
dependencies in dependency:resolve-plugins

(Unrelated question: Is the order of dependencies random in the above list
or is it classpath order? If it's random, it would be better if it was
sorted, so it's easy for the human eye to scan for a particular dependency)

- Eric L

On Tue, May 7, 2019 at 9:16 PM Anders Hammar  wrote:

> Checking m-jar-p, what is needed is an upgrade of plexus-archiver to
> version 4.0.0+ as it includes an upgraded dependency to plexus-io v3.1.1.
> See [1].
> If you include m-jar-p in the pluginManagement section of your corporate
> parent-POM, you could bump this on the existing maven-jar-plugin v3.1.1
> like this:
> 
> org.apache.maven.plugins
> maven-jar-plugin
> 3.1.1
> 
> 
> org.codehaus.plexus
> plexus-archiver
> 4.1.0
> 
> 
> 
>
> [1]
>
> https://github.com/codehaus-plexus/plexus-archiver/blob/master/ReleaseNotes.md#plexus-archiver-400
>
> /Anders
>
> On Tue, May 7, 2019 at 8:07 PM Eric Lilja  wrote:
>
> > Hi, in my organization we're seeing big increases in build time using
> newer
> > versions of maven-jar-plugin and maven-sources-plugin, because those
> > plugins are affected by a bug in plexus-io.
> >
> > The issue in plexus-io has been fixed since some time:  [1] and I
> believe a
> > release has been made of relevant plexus components containing the fix
> (but
> > I might be wrong about that).
> >
> > However, both MJAR-259 [2] and MSOURCES-119 [3] are still open. When can
> we
> > expect new releases of these two plugins (and other plugins/components
> > affected by the same issue)? Is something block the release or no one
> > simply got around to it yet?
> >
> > We're trying to stay current and modern in our little eco-system at work,
> > but this issue is holding us back on older versions of aforementioned
> > plugins.
> >
> > Thanks fo

Regarding MJAR-259 and MSOURCES-119

[Eric Lilja]

Hi, in my organization we're seeing big increases in build time using 
newer versions of maven-jar-plugin and maven-sources-plugin, because 
those plugins are affected by a bug in plexus-io it seems.


The issue in plexus-io has been fixed since some time:  [1] and I 
believe a release has been made of relevant plexus components containing 
the fix (but I might be wrong about that).


However, both MJAR-259 [2] and MSOURCES-119 [3] are still open. When can 
we expect new releases of these two plugins (and other 
plugins/components affected by the same issue)? Is something block the 
release or no one simply got around to it yet?


We're trying to stay current and modern in our little eco-system at 
work, but this issue is holding us back on older versions of 
aforementioned plugins.


Thanks for your time!

- Eric L

[1] https://github.com/codehaus-plexus/plexus-io/pull/17
[2] https://issues.apache.org/jira/browse/MJAR-259
[3] https://issues.apache.org/jira/browse/MSOURCES-119

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

Regarding MJAR-259 and MSOURCES-119

[Eric Lilja]

Hi, in my organization we're seeing big increases in build time using newer
versions of maven-jar-plugin and maven-sources-plugin, because those
plugins are affected by a bug in plexus-io.

The issue in plexus-io has been fixed since some time:  [1] and I believe a
release has been made of relevant plexus components containing the fix (but
I might be wrong about that).

However, both MJAR-259 [2] and MSOURCES-119 [3] are still open. When can we
expect new releases of these two plugins (and other plugins/components
affected by the same issue)? Is something block the release or no one
simply got around to it yet?

We're trying to stay current and modern in our little eco-system at work,
but this issue is holding us back on older versions of aforementioned
plugins.

Thanks for your time!

- Eric L

[1] https://github.com/codehaus-plexus/plexus-io/pull/17
[2] https://issues.apache.org/jira/browse/MJAR-259
[3] https://issues.apache.org/jira/browse/MSOURCES-119

Re: New release of ant-maven-plugin

[Eric Lilja]

I would not mind at all seeing latest 1.10.x of Ant being used instead (I
believe 1.10.6 is being voted on at the moment), and the plugin requiring
Java 8. I am also happy to hear that the checkstyle plugin didn't get stuck
on some older, Java 7-compatible release of Checkstyle, but is able to
follow the latest versions! I think that's good!

- Eric L

On Sat, May 4, 2019 at 8:57 PM Enrico Olivelli  wrote:

> Il sab 4 mag 2019, 19:46 Eric Lilja  ha scritto:
>
> > That's great news, Sylwester! Since it will be version 3.0 (as you say),
> > I'm assuming the plugin will be changed to require Maven 3.x and Java 7
> > (and update to latest Maven parents), as that is a target for official
> > Maven plugins versioned 3 and higher? And why can't we use ant version
> > 1.10.x, does it require Java 8?
> >
>
> FYI we are doing the same for checkstyle plugin. Checkstyle now requires
> java8 and so the new version of the plugin will adapt to its core
> dependency
>
>
> Enrico
>
>
>
> > Looking forward to the release!
> >
> > - Eric L
> >
> > On Fri, May 3, 2019 at 9:48 PM Sylwester Lachiewicz <
> slachiew...@gmail.com
> > >
> > wrote:
> >
> > > I have also updated Ant to 1.9.14 and I think we can already prepare a
> > vote
> > > for the 3.0 release.
> > > Sylwester
> > >
> > > niedz., 14 kwi 2019 o 22:35 Sebastian Laskawiec 
> > > napisał(a):
> > >
> > > > Hey Robert,
> > > >
> > > > Thank you for the heads up!
> > > >
> > > > I'm talking about this one:
> > > > org.apache.maven.plugins
> > > > maven-antrun-plugin
> > > > 1.8
> > > >
> > > > The one, that can run Ant scripts within a Maven project.
> > > >
> > > > Thanks,
> > > > Sebastian
> > > >
> > > > On Sat, Apr 13, 2019 at 11:50 AM Robert Scholte <
> rfscho...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi Sebastian,
> > > > >
> > > > > be careful with your naming, because my first response would have
> > been
> > > > > 'no'.
> > > > >
> > > > > You're talking about ant-maven-plugin, whereas we maintain 2
> related
> > > > > plugins: maven-ant-plugin and maven-antrun-plugin.
> > > > >
> > > > > The first one can generate Ant scripts based on a Maven project.
> This
> > > > > project hasn't been touched for quite some time and it probably
> > doesn't
> > > > > make sense to maintain this plugin any longer.
> > > > >
> > > > > The latter on the other hand does make sense, however in general it
> > is
> > > a
> > > > > sign that you're doing a task that should be transformed to a
> > dedicated
> > > > > Maven plugin.
> > > > >
> > > > > So all we need is somebody to step up as the release manager.
> > > > > Might be a good project for a Maven committer who has never done a
> > > > > release
> > > > > before.
> > > > >
> > > > > Robert
> > > > >
> > > > > On Thu, 11 Apr 2019 09:28:02 +0200, Sebastian Laskawiec
> > > > >  wrote:
> > > > >
> > > > > > Hey,
> > > > > >
> > > > > > My name is Sebastian Łaskawiec and I'm a part of Keycloak
> > Engineering
> > > > > > Team
> > > > > > [1].
> > > > > >
> > > > > > Recently I hit a problem with resolving user properties that
> seems
> > to
> > > > be
> > > > > > fixed in Maven. I would love to give it a go but it seems we
> didn't
> > > > have
> > > > > > any release for a very long time [2]. Could you please tell me,
> do
> > > you
> > > > > > plan
> > > > > > to release a new version any time soon?
> > > > > >
> > > > > > On a side note, I already reached Hervé Boutemy, who asked me to
> > > write
> > > > to
> > > > > > this email list and ask for release. Thank you for the hint,
> Hervé!
> > > > > >
> > > > > > Thanks,
> > > > > > Sebastian Łaskawiec
> > > > > > Senior Software Engineer @ Red Hat
> > > > > > Keycloak Engineering Team
> > > > > >
> > > > > > [1] https://www.keycloak.org/
> > > > > > [2] https://github.com/apache/maven-antrun-plugin/releases
> > > > >
> > > >
> > >
> >
>

Re: New release of ant-maven-plugin

[Eric Lilja]

That's great news, Sylwester! Since it will be version 3.0 (as you say),
I'm assuming the plugin will be changed to require Maven 3.x and Java 7
(and update to latest Maven parents), as that is a target for official
Maven plugins versioned 3 and higher? And why can't we use ant version
1.10.x, does it require Java 8?

Looking forward to the release!

- Eric L

On Fri, May 3, 2019 at 9:48 PM Sylwester Lachiewicz 
wrote:

> I have also updated Ant to 1.9.14 and I think we can already prepare a vote
> for the 3.0 release.
> Sylwester
>
> niedz., 14 kwi 2019 o 22:35 Sebastian Laskawiec 
> napisał(a):
>
> > Hey Robert,
> >
> > Thank you for the heads up!
> >
> > I'm talking about this one:
> > org.apache.maven.plugins
> > maven-antrun-plugin
> > 1.8
> >
> > The one, that can run Ant scripts within a Maven project.
> >
> > Thanks,
> > Sebastian
> >
> > On Sat, Apr 13, 2019 at 11:50 AM Robert Scholte 
> > wrote:
> >
> > > Hi Sebastian,
> > >
> > > be careful with your naming, because my first response would have been
> > > 'no'.
> > >
> > > You're talking about ant-maven-plugin, whereas we maintain 2 related
> > > plugins: maven-ant-plugin and maven-antrun-plugin.
> > >
> > > The first one can generate Ant scripts based on a Maven project. This
> > > project hasn't been touched for quite some time and it probably doesn't
> > > make sense to maintain this plugin any longer.
> > >
> > > The latter on the other hand does make sense, however in general it is
> a
> > > sign that you're doing a task that should be transformed to a dedicated
> > > Maven plugin.
> > >
> > > So all we need is somebody to step up as the release manager.
> > > Might be a good project for a Maven committer who has never done a
> > > release
> > > before.
> > >
> > > Robert
> > >
> > > On Thu, 11 Apr 2019 09:28:02 +0200, Sebastian Laskawiec
> > >  wrote:
> > >
> > > > Hey,
> > > >
> > > > My name is Sebastian Łaskawiec and I'm a part of Keycloak Engineering
> > > > Team
> > > > [1].
> > > >
> > > > Recently I hit a problem with resolving user properties that seems to
> > be
> > > > fixed in Maven. I would love to give it a go but it seems we didn't
> > have
> > > > any release for a very long time [2]. Could you please tell me, do
> you
> > > > plan
> > > > to release a new version any time soon?
> > > >
> > > > On a side note, I already reached Hervé Boutemy, who asked me to
> write
> > to
> > > > this email list and ask for release. Thank you for the hint, Hervé!
> > > >
> > > > Thanks,
> > > > Sebastian Łaskawiec
> > > > Senior Software Engineer @ Red Hat
> > > > Keycloak Engineering Team
> > > >
> > > > [1] https://www.keycloak.org/
> > > > [2] https://github.com/apache/maven-antrun-plugin/releases
> > >
> >
>

Re: New release of ant-maven-plugin

[Eric Lilja]

In my organization, we would be very happy to see newer, more modernized
releases of maven-ant-plugin. So a big thumbs up for that!

- Eric L

On Sat, Apr 13, 2019 at 11:50 AM Robert Scholte 
wrote:

> Hi Sebastian,
>
> be careful with your naming, because my first response would have been
> 'no'.
>
> You're talking about ant-maven-plugin, whereas we maintain 2 related
> plugins: maven-ant-plugin and maven-antrun-plugin.
>
> The first one can generate Ant scripts based on a Maven project. This
> project hasn't been touched for quite some time and it probably doesn't
> make sense to maintain this plugin any longer.
>
> The latter on the other hand does make sense, however in general it is a
> sign that you're doing a task that should be transformed to a dedicated
> Maven plugin.
>
> So all we need is somebody to step up as the release manager.
> Might be a good project for a Maven committer who has never done a
> release
> before.
>
> Robert
>
> On Thu, 11 Apr 2019 09:28:02 +0200, Sebastian Laskawiec
>  wrote:
>
> > Hey,
> >
> > My name is Sebastian Łaskawiec and I'm a part of Keycloak Engineering
> > Team
> > [1].
> >
> > Recently I hit a problem with resolving user properties that seems to be
> > fixed in Maven. I would love to give it a go but it seems we didn't have
> > any release for a very long time [2]. Could you please tell me, do you
> > plan
> > to release a new version any time soon?
> >
> > On a side note, I already reached Hervé Boutemy, who asked me to write to
> > this email list and ask for release. Thank you for the hint, Hervé!
> >
> > Thanks,
> > Sebastian Łaskawiec
> > Senior Software Engineer @ Red Hat
> > Keycloak Engineering Team
> >
> > [1] https://www.keycloak.org/
> > [2] https://github.com/apache/maven-antrun-plugin/releases
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Version 3.6.1

[Eric Lilja]

+1 (non-binding), tested with Java 8 on Windows 10 and Linux, both 
personal projects and at work


- Eric L

On 2019-04-04 21:55, Karl Heinz Marbaise wrote:

Hi,

We have solved 42 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12338966 



There are issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC 



Staging repo:
https://repository.apache.org/content/repositories/maven-1496

The distributable binaries and sources can be found here:
https://repository.apache.org/content/repositories/maven-1496/org/apache/maven/apache-maven/3.6.1/ 



Specifically the zip, tarball and source archives can be found here:

https://repository.apache.org/content/repositories/maven-1496/org/apache/maven/apache-maven/3.6.1/apache-maven-3.6.1-bin.zip 

https://repository.apache.org/content/repositories/maven-1496/org/apache/maven/apache-maven/3.6.1/apache-maven-3.6.1-bin.tar.gz 



https://repository.apache.org/content/repositories/maven-1496/org/apache/maven/apache-maven/3.6.1/apache-maven-3.6.1-src.zip 

https://repository.apache.org/content/repositories/maven-1496/org/apache/maven/apache-maven/3.6.1/apache-maven-3.6.1-src.tar.gz 



The release artifacts are staged for distribution in:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.0

Source release checksum(s):
apache-maven-3.6.1-src.tar.gz

  sha1: 4e87c962ed505a0158085f99d92a0ade8c7fd197
sha512:
11a31022cffa0518584703fffd9fce998332ac5f6c2a50db3b590e90f3bdd1508d9e0cb5ba89a699ef6536b237bcc96166cfde3d45bce6346fa21b05b4d12bf8 



apache-maven-3.6.1-src.zip:

  sha1: ec0618f981f9367f133a29fbfcaa8e073cb8ac85
sha512:
b92d8ed72585c4e05debe4d15eb9ae5dd72e814b6413bcba78d01282c9eccc38e79755654e0d0b4e5a650f0226c116a4a4faad731918a465ad424a2a81582a67 



Git tag:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555 



Staging site:
https://maven.apache.org/components/ref/3-LATEST/

Vote open for 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 Surefire Plugin version 3.0.0-M3

[Eric Lilja]

+1 (non-binding) Tested with personal projects and larger projects at work

- Eric Lilja

On Fri, Dec 21, 2018 at 2:49 PM Tibor Digana  wrote:

> Thx Enrico, Christian for testing.
> This is not an ideal time for the release since it's Christmas season.
> I hope we will get some PMC members and common users in this Vote as well.
>
> Cheers
> Tibor
>
> On Fri, Dec 21, 2018 at 1:16 PM Enrico Olivelli 
> wrote:
>
> > +1 (non binding)
> > built from source, all its are passing on my Linux
> >
> > Enrico
> >
> > Il giorno gio 20 dic 2018 alle ore 11:35 Christian Stein
> >  ha scritto:
> > >
> > > +1
> > >
> > > Cheers,
> > > Christian
> > >
> > > Simple project using Surefire 3.0.0-M3:
> > >
> >
> https://github.com/junit-team/junit5-samples/commit/a8660d636058a52fc68f7a9d6a5a11b42ee44303
> > > Result: https://travis-ci.org/junit-team/junit5-samples/jobs/470432909
> > >
> > > On Thu, Dec 20, 2018 at 10:48 AM Tibor Digana 
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > We solved 6 issues:
> > > >
> > > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12342872
> > > >
> > > > There are still a couple of issues left in JIRA:
> > > >
> > > >
> >
> https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
> > > >
> > > > Staging repo:
> > > > https://repository.apache.org/content/repositories/maven-1479
> > > >
> > > >
> >
> https://repository.apache.org/content/repositories/maven-1479/org/apache/maven/surefire/surefire/3.0.0-M3/surefire-3.0.0-M3-source-release.zip
> > > >
> > > > Source release checksum(s):
> > > > surefire-3.0.0-M3-source-release.zip sha1:
> > > > 4d1187b9c1f1922d13ac25d4538f30225ea8e27a
> > > > surefire-3.0.0-M3-source-release.zip sha512:
> > > >
> > > >
> >
> c13d24c10ec59278113f862702538770fccf1f816a7803dc7adaaa9f90ab0a76bad0d83526cd4ce80d3891e9364f4079020b70478dede0e330f98f8f79afae54
> > > >
> > > > Staging site:
> > > > http://maven.apache.org/surefire-archives/surefire-LATEST/
> > > >
> > > > Guide to testing staged releases:
> > > >
> http://maven.apache.org/guides/development/guide-testing-releases.html
> > > >
> > > > Vote open for 72 hours.
> > > >
> > > > [ ] +1
> > > > [ ] +0
> > > > [ ] -1
> > > >
> > > > Cheers
> > > > Tibor
> > > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M2

[Eric Lilja]

Hi, Tibor, yes I saw the milestone roadmap, that's why I am excited for 
M2 (which I tested both on private projects and at work), since it 
brings us closer to M3, which introduces changes which will be 
beneficial for Pax Exam (communicating with child processes through 
sockets).
The problems with Pax Exam and surefire (for surefire version greater 
than 2.18.1), has varied over the versions (of surefire since 2.18.1). 
Before tests would often crash, now things work better but you often get 
this 30s timeout at the end. That's why we stayed with 2.18.1 in our 
organization.


Great work on M2, looking forward to see it release and even more 
excited about M3!


I didn't mean to hijack the vote email thread, and this will be last 
message on this thread about this topic. I was just excited about M2 
since it brings us a lot closer to M3, which I am even more excited 
about for the reason described above, and I wanted to share that excitement.


Great work!

- Eric L

On 2018-12-08 19:40, Tibor Digana wrote:

@Eric Lilja
You use Pax. I guess you are refering to the problem with standard input
and standard output stream. The plugin says that the stream is corrupted.
Am I right?

Did you see the documentation here in this Vote? See the roadmap on the
front page
http://maven.apache.org/surefire-archives/surefire-LATEST/maven-surefire-plugin/index.html

This is long standing problem but it can be changed in new major version.
But I still think that Pax and Felix could provide some kind of abstraction
layer of these streams in testing purposes.

Cheers
Tibor





On Sat, Dec 8, 2018 at 7:20 PM Eric Lilja  wrote:


+1 (non-binding)

M2 is looking good on my projects, and I can't wait for the upcoming M3
after M2, which I believe will solve the long-standing problems running
Pax Exam tests (in the organization I work in we use 2.18.1 of surefire
for Pax-Exam tests particularly, as no version of Surefire higher than
that works well with it)

- Eric L

On 2018-12-05 23:26, Tibor Digana wrote:

Hi,

We solved 15 issues:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344396

There are still a couple of issues left in JIRA:


https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1472/


https://repository.apache.org/service/local/repositories/maven-1472/content/org/apache/maven/surefire/surefire/3.0.0-M2/surefire-3.0.0-M2-source-release.zip

Source release checksum(s):
surefire-3.0.0-M2-source-release.zip sha1:
421f6fda2367d128007b84b213690db348a8b2c6
surefire-3.0.0-M2-source-release.zip sha512:


ed02ac46eec7f632180e00487f65901420908ea5afc0e507350c2fa529a6278f73f32f915bcd1dee0bcdffbf391d045b9f3cfe557003d02af9e2dc91ddb31212

Staging site:
http://maven.apache.org/surefire-archives/surefire-LATEST/

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

Vote open for 72 hours.

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

BR
Tibor



-
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 Surefire Plugin version 3.0.0-M2

[Eric Lilja]

+1 (non-binding)

M2 is looking good on my projects, and I can't wait for the upcoming M3 
after M2, which I believe will solve the long-standing problems running 
Pax Exam tests (in the organization I work in we use 2.18.1 of surefire 
for Pax-Exam tests particularly, as no version of Surefire higher than 
that works well with it)


- Eric L

On 2018-12-05 23:26, Tibor Digana wrote:

Hi,

We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344396

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1472/
https://repository.apache.org/service/local/repositories/maven-1472/content/org/apache/maven/surefire/surefire/3.0.0-M2/surefire-3.0.0-M2-source-release.zip

Source release checksum(s):
surefire-3.0.0-M2-source-release.zip sha1:
421f6fda2367d128007b84b213690db348a8b2c6
surefire-3.0.0-M2-source-release.zip sha512:
ed02ac46eec7f632180e00487f65901420908ea5afc0e507350c2fa529a6278f73f32f915bcd1dee0bcdffbf391d045b9f3cfe557003d02af9e2dc91ddb31212

Staging site:
http://maven.apache.org/surefire-archives/surefire-LATEST/

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

Vote open for 72 hours.

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

BR
Tibor




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

Re: [maven-enforcer] 05/05: Code improvement.

[Eric Lilja]

>
>
> > +private boolean isVersion( String version )
> > +{
> > +return StringUtils.isNotEmpty( version ) &&
> > !StringUtils.isWhitespace( version );
> > +}
>

Maybe use StringUtils.isNotBlank() instead?

- Eric L

Re: [VOTE] Release Apache Maven Jarsigner Plugin version 3.0.0

[Eric Lilja]

Aha, indeed, I missed that part. Sorry for the noise!

- EL

On 2018-11-03 22:26, Tibor Digana wrote:

It was a component [1] but now it is a plugin [2].

[1]: https://github.com/apache/maven-jarsigner
[2]: https://github.com/apache/maven-jarsigner-plugin


On Sat, Nov 3, 2018 at 6:32 PM Eric Lilja  wrote:


If one just reads the list, it's hard to understand why this is voted on
again after this announcement [1] (but I can see it didn't make it to
Maven central). Seems some off-list communication have taken place here...

[1]

https://mail-archives.apache.org/mod_mbox/maven-dev/201810.mbox/%3Cop.zrrhydlkkdkhrr%40desktop-2khsk44.dynamic.ziggo.nl%3E

- Eric L

On 2018-11-03 13:58, Sylwester Lachiewicz wrote:

+1

sob., 3.11.2018, 13:45: Tibor Digana 

napisał(a):

+1

On Sat, Nov 3, 2018 at 11:32 AM Robert Scholte 
wrote:


Hi,

We solved 8 issues:



https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317528=12330856=Text

There are still a couple of issues left in JIRA:



https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317528%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-maven-1465/



https://repository.apache.org/content/repositories/maven-1465/org/apache/maven/plugins/maven-jarsigner-plugin/3.0.0/maven-jarsigner-plugin-3.0.0-source-release.zip

Source release checksum(s):
maven-jarsigner-plugin-3.0.0-source-release.zip sha512:



d02b69c2190a5d2360e317bb17393134b4d78a86aec66732a5534baa069afed6a6c4314697238b74badc53ed5beb88fdf6a811474923a30bb554a9b3404d5588

Staging site:


https://maven.apache.org/plugins-archives/maven-jarsigner-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

-
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





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

Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M1 - TAKE 2

[Eric Lilja]

+1 (non-binding)

When testing on my personal projects, I did see one JUnit test failure 
on some very old code, a test which didn't have any problems on surefire 
2.18.1-2.22.1. I examined the test and came to the conclusion that is 
was misbehaved as it tried to treat a classpath resource as a file 
system resource. I re-wrote the test and now it works on both both 
3.0.0-M1 and older versions. But I guess others will see similar 
failures if they have poorly written code like I had in that testcase.


I tested using a clean .m2 and ran a script which builds all my projects 
in dependency order. I noticed the process took a lot longer than usual 
after adding the staging repo, but I solved that by adding the default 
plugin repo as well.


By the way, there were five issues closed, not four, which is not a bad 
thing, just a tiny error in the vote email text :)


- Eric Lilja

On 2018-11-04 11:48, Tibor Digana wrote:

Hi,

We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12342871

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1466/
https://repository.apache.org/content/repositories/maven-1466/org/apache/maven/surefire/surefire/3.0.0-M1/surefire-3.0.0-M1-source-release.zip

Source release checksum(s):
surefire-3.0.0-M1-source-release.zip sha512:
2817639681b8597a58c38dbb5616c481c263f04b722f6fafcbc3f33c17f5d4b165572c38a83789ed80097047601505b339df015617603f754319dfadf3089b94
surefire-3.0.0-M1-source-release.zip sha1:
72830b8d82bd068ab7da5eaeb4da8a66b8ea600d

Staging site:
http://maven.apache.org/surefire-archives/surefire-LATEST/

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

Vote open for 72 hours.

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

Cheers
Tibor




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

Re: [VOTE] Release Apache Maven Jarsigner Plugin version 3.0.0

[Eric Lilja]

If one just reads the list, it's hard to understand why this is voted on 
again after this announcement [1] (but I can see it didn't make it to 
Maven central). Seems some off-list communication have taken place here...


[1] 
https://mail-archives.apache.org/mod_mbox/maven-dev/201810.mbox/%3Cop.zrrhydlkkdkhrr%40desktop-2khsk44.dynamic.ziggo.nl%3E


- Eric L

On 2018-11-03 13:58, Sylwester Lachiewicz wrote:

+1

sob., 3.11.2018, 13:45: Tibor Digana  napisał(a):


+1

On Sat, Nov 3, 2018 at 11:32 AM Robert Scholte 
wrote:


Hi,

We solved 8 issues:



https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317528=12330856=Text

There are still a couple of issues left in JIRA:



https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317528%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-maven-1465/



https://repository.apache.org/content/repositories/maven-1465/org/apache/maven/plugins/maven-jarsigner-plugin/3.0.0/maven-jarsigner-plugin-3.0.0-source-release.zip

Source release checksum(s):
maven-jarsigner-plugin-3.0.0-source-release.zip sha512:



d02b69c2190a5d2360e317bb17393134b4d78a86aec66732a5534baa069afed6a6c4314697238b74badc53ed5beb88fdf6a811474923a30bb554a9b3404d5588

Staging site:
https://maven.apache.org/plugins-archives/maven-jarsigner-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

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

[Eric Lilja]

On 2018-10-27 11:35, Karl Heinz Marbaise wrote:

Hi,

I will enhance the VOTE period for another 72 h.


Oh, no, even more delays, I was hoping to see the official release 72h 
after original vote was opened (which would have been late tonight, 
CET). :-(
My vote is +1 (non-binding). Tested with personal projects at home and 
also with bigger projects at work, both on personal workstation and on 
Jenkins


- Eric Lilja



Reasons:

 1. Not enough VOTE's from PMC's
 2. I would like to see more feedback from community.


Kind regards
Karl Heinz Marbaise
On 24/10/18 21:50, Karl Heinz Marbaise wrote:

Hi,

We have solved 26 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12338966 



There are issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC 



Staging repo:
https://repository.apache.org/content/repositories/maven-1459

The distributable binaries and sources can be found here:
https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/ 



Specifically the zip, tarball and source archives can be found here:

https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-bin.zip 

https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-bin.tar.gz 



https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-src.zip 

https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-src.tar.gz 



The release artifacts are staged for distribution in:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.4

Source release checksum(s):
apache-maven-3.6.0-src.tar.gz

   sha1: 255d8057b7f014222e96137001d4f4aa05d4a7cb
sha512: 
5b4b5ca569d5476f9d6a2b8080927f58da9ca10a04c593df3d8c012e60fdcf7dcf70c4bc5db0d068b3a36785ede62a55fd1778b22ecadcf787485681ddc758a8 



apache-maven-3.6.0-src.zip:

   sha1: 6149f259489acf36e2c04ec0dd713f99336b3346
sha512: 
c5794a6723d8d0fc8ff447b42e5a8c13524a44f8508a305d463f811c8039c7e9166d709077c8373d3cf980ce24feaebb2431cb50fb274933ab3bc2a90355 



Git tag:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=97c98ec64a1fdfee7767ce5ffb20918da4f719f3 



Staging site:
https://maven.apache.org/components/ref/3-LATEST/

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 Apache Maven 3.6.0

[Eric Lilja]

+1 (non-binding), tested with my personal projects and bigger projects 
at work (and at work both on personal workstations and certain Jenkins 
installations).


Very much looking forward to the release!

- Eric Lilja

On 2018-10-24 21:50, Karl Heinz Marbaise wrote:

Hi,

We have solved 26 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12338966 



There are issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC 



Staging repo:
https://repository.apache.org/content/repositories/maven-1459

The distributable binaries and sources can be found here:
https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/ 



Specifically the zip, tarball and source archives can be found here:

https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-bin.zip 

https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-bin.tar.gz 



https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-src.zip 

https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-src.tar.gz 



The release artifacts are staged for distribution in:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.4

Source release checksum(s):
apache-maven-3.6.0-src.tar.gz

  sha1: 255d8057b7f014222e96137001d4f4aa05d4a7cb
sha512: 
5b4b5ca569d5476f9d6a2b8080927f58da9ca10a04c593df3d8c012e60fdcf7dcf70c4bc5db0d068b3a36785ede62a55fd1778b22ecadcf787485681ddc758a8


apache-maven-3.6.0-src.zip:

  sha1: 6149f259489acf36e2c04ec0dd713f99336b3346
sha512: 
c5794a6723d8d0fc8ff447b42e5a8c13524a44f8508a305d463f811c8039c7e9166d709077c8373d3cf980ce24feaebb2431cb50fb274933ab3bc2a90355


Git tag:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=97c98ec64a1fdfee7767ce5ffb20918da4f719f3 



Staging site:
https://maven.apache.org/components/ref/3-LATEST/

Vote open for 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 Install Plugin version 3.0.0-M1

[Eric Lilja]

>
>
>
> > 2. Both projects (install, deploy) have several warnings
>
> Can you be more accurate? Where ?
>


I just went to link describing the fixes issues in your email,
https://issues.apache.org/jira/projects/MINSTALL/versions/12334343, and I
can see JIRA saying there are 20 warnings. Warnings indicate when the
status of a JIRA issue doesn't reflect related development activity. For
example: an issue marked complete that has an open pull request should be
marked as still being in progress.

I think it's easier to trust the list of changes during time to vote, if
there are no warnings and no still on-going issues according to JIRA. The
ongoing issue should either be completed or moved to next target version.

- Eric L


>
>
>

Re: [VOTE] Release Apache Maven Install Plugin version 3.0.0-M1

[Eric Lilja]

solve versions should have been "solved issues"

On Mon, Sep 24, 2018 at 9:29 AM Eric Lilja  wrote:

>
>
> On Sun, Sep 23, 2018 at 7:44 PM Karl Heinz Marbaise 
> wrote:
>
>> Hi,
>>
>> We solved 32 issues:
>> https://issues.apache.org/jira/projects/MINSTALL/versions/12334343
>>
>
>  Hi and thank you for doing the releases of both maven-deploy-plugin and
> maven-install-plugin, it's exciting! However, when I follow the links to
> JIRA to see the solve versions, a few things look weird:
> 1. Seems you need to be logged in to actually see the list of solved
> issues, which is inconvenient and unncessarily secretive.
> 2. Both projects (install, deploy) have several warnings
> 3. Both projects have an issue still in TODO.
>
> Seems some JIRA managemenet is in order  here...
>
> - Eric L
>
>
>

Re: [VOTE] Release Apache Maven Install Plugin version 3.0.0-M1

[Eric Lilja]

On Sun, Sep 23, 2018 at 7:44 PM Karl Heinz Marbaise 
wrote:

> Hi,
>
> We solved 32 issues:
> https://issues.apache.org/jira/projects/MINSTALL/versions/12334343
>

 Hi and thank you for doing the releases of both maven-deploy-plugin and
maven-install-plugin, it's exciting! However, when I follow the links to
JIRA to see the solve versions, a few things look weird:
1. Seems you need to be logged in to actually see the list of solved
issues, which is inconvenient and unncessarily secretive.
2. Both projects (install, deploy) have several warnings
3. Both projects have an issue still in TODO.

Seems some JIRA managemenet is in order  here...

- Eric L

Re: core master branch freeze

[Eric Lilja]

On 2018-06-17 21:18, Stephen Connolly wrote:

y'all good now... 3.5.4 cut... vote will follow once the other bits sync



Yay! I cannot wait to see the vote email! Awesome work by everyone 
involved, exciting!


- Eric L

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

Re: [VOTE] Release Apache Maven WAR Plugin version 3.2.1

[Eric Lilja]

How's the release of plexus-interpolation going? We're looking forward to a
new release of maven-war-plugin!

- EL

On Sun, May 13, 2018 at 10:16 AM Karl Heinz Marbaise 
wrote:

> Hi Gabriel,
>
> I have added an issue for the upgrade of plexus-interpolation (MWAR-417)
> which is related to MWAR-303 and I will do a release of
> plexus-interpolation within the next daysafterwards I can make an
> other release of Maven WAR Plugin if this helps...
>
>
> Kind regards
> Karl Heinz Marbaise
> On 10/05/18 03:21, Gabriel Belingueres wrote:
> > any chance of adding MWAR-303 to the release? fix is already submitted.
> >
> > El mié., 9 de may. de 2018 20:14, Olivier Lamy 
> escribió:
> >
> >> +1
> >>
> >> On Thu, 10 May 2018 at 04:17, Karl Heinz Marbaise 
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> We solved 5 issues:
> >>>
> >>>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12341729
> >>>
> >>> There are still a couple of issues left in JIRA:
> >>>
> >>>
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MWAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
> >>>
> >>> Staging repo:
> >>> https://repository.apache.org/content/repositories/maven-1423/
> >>>
> >>>
> >>>
> >>
> https://repository.apache.org/content/repositories/maven-1423/org/apache/maven/plugins/maven-war-plugin/3.2.1/maven-war-plugin-3.2.1-source-release.zip
> >>>
> >>> Source release checksum(s):
> >>> maven-war-plugin-3.2.1-source-release.zip sha1:
> >>> 94317def832e4b767808dbed6b9463c75a99227c
> >>>
> >>> Staging site:
> >>> https://maven.apache.org/plugins-archives/maven-war-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
> >>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20.1

[Eric Lilja]

On 2018-03-06 14:27, Tibor Digana wrote:



Hi Herve,

Can you send me a zip of the test which failed
*surefire-its/target/Surefire1177TestngParallelSuitesIT_shouldRunTwoSuitesInParallel*
?
It is a parallelism in TestNG. I will discuss it with the guys in TestNG
team on GitHub.
Thx.
Tibor




Congratulations on the release, looking forward to trying it! For us who 
only read this mailing list, how was the issue mentioned above resolved 
(parallelism in TestNG)?


- EL

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

Re: [ANN] First call to round up issues for 3.5.1

[Eric Lilja]

Is https://issues.apache.org/jira/browse/MNG-6025 being included in 
3.5.1? I sure hope so!


- Eric L

On 2017-05-01 22:15, Hervé BOUTEMY wrote:

great!
I'll mark it for 3.5.1

Regards,

Hervé

Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit :

@Hervé, I want to second MNG-6223

Robert

On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly

 wrote:

I'd like people to take this next week to consider what issues we want to
pull in scope for 3.5.1.

If you are a committer, just add the issues to Fix Version of
3.5.1-candidate, ideally adding a comment at the same time with your
reasoning.

If once we have a seconding committer, they can just comment seconding
and
move the Fix Version to 3.5.1.

I'm going to suggest a 1 week period of open scoping. After that point in
time, my intent is to be more strict and apply "release manager risk
management" on any new issues being targeted for 3.5.1. Similarly, if
issues targeted for 3.5.1 are not making sufficient progress they will be
dropped... but for now... it's open season!

Get triaging!

-Stephen

-
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




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

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

[Eric Lilja]

Indeed, I would not expect to having my provided manifest modified at all.

On 2015-06-07 18:57, Igor Fedorenko wrote:

If I provide custom jar manifest, I expect the manifest to be used
as-is, without anything added, removed or reordered. Just my 2 kopecks.




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