Re: Maven 3.9,0 plan

2023-01-30 Thread Dan Tran
run into this issue

"Unable to parse maven.config file options: Unrecognized maven.config file
entries: [ -e --fail-fast -Djavax.xml.accessExternalSchema=all
-Daether.connector.resumeDownloads=false]"

The workaround is to break it into multiple lines

-D



On Mon, Jan 30, 2023 at 2:43 PM Tamás Cservenák  wrote:

> Howdy,
>
> commented on issue, but FTR:
> - the refd issue MCOMPILER-481 related IT fails when run with Maven 3.9.x
> (passes OK with Maven 3.8.7)
> - the compilation (what IT is testing) passes OK
> - the failure is in UT run (surefire)
>
> Maven 3.8.x uses surefire 2.x, while 3.9.x uses surefire 3.0.0-M8... to me,
> this seems like a surefire 3.0.0-M8 issue...
>
> I see no other relation to Maven core here.
>
> Thanks
> T
>
> On Mon, Jan 30, 2023 at 10:23 PM Jorge Solórzano  wrote:
>
> > Hi, what about the issue (regression) with
> > https://issues.apache.org/jira/browse/MCOMPILER-481?
> >
> > Regards,
> >
> > On Mon, Jan 30, 2023 at 4:24 PM Tamás Cservenák 
> > wrote:
> > >
> > > Howdy,
> > >
> > > FYI Maven 3.9.0 is good to go.
> > >
> > >
> > > T
> > >
> > > On Thu, Jan 26, 2023 at 10:46 PM Tamás Cservenák 
> > > wrote:
> > >
> > > > Howdy,
> > > >
> > > > 3.9.0 on hold for a bit more, an issue (and related PR) just popped
> in:
> > > > https://issues.apache.org/jira/browse/MNG-7672
> > > >
> > > > Thanks
> > > > T
> > > >
> > > > On Thu, Jan 26, 2023 at 7:49 PM Tamás Cservenák  >
> > > > wrote:
> > > >
> > > >> Howdy
> > > >>
> > > >> Tomorrow is 27th :) Staging is part of release (release + vote +
> final
> > > >> promotion to Central), so hopefully tomorrow will be staged
> > > >>
> > > >> T
> > > >>
> > > >> On Thu, Jan 26, 2023, 19:28 Delany 
> > wrote:
> > > >>
> > > >>> Hi Tamas,
> > > >>> Will you create a staging for 3.9.0?
> > > >>> I don't see anything at
> > > >>>
> > > >>>
> >
> https://repository.apache.org/content/repositories/staging/org/apache/maven/maven/
> > > >>> Delany
> > > >>>
> > > >>> On Thu, 19 Jan 2023 at 11:03, Tamás Cservenák  >
> > > >>> wrote:
> > > >>>
> > > >>> > Howdy,
> > > >>> >
> > > >>> > The 3.9.0 changelist:
> > > >>> >
> > > >>> >
> > > >>>
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0
> > > >>> >
> > > >>> > It received today one more PR (
> > > >>> > https://issues.apache.org/jira/browse/MNG-7630), but the plan
> I'd
> > > >>> like to
> > > >>> > propose is following:
> > > >>> >
> > > >>> > - Keep the "3.9.0 window" open until the end of next week (27th
> Jan
> > > >>> 2023).
> > > >>> > - On 27th (or a bit after) do the 3.9.0 release
> > > >>> >
> > > >>> > So, please anyone able to, test 3.9.0-SNAPSHOT if you can.
> > > >>> >
> > > >>> > Aside of detailed changelog above, here is a high level list (to
> be
> > > >>> > reworked for site) here:
> > > >>> >
> > > >>> >
> > > >>>
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Notes+for+Maven+3.9.x+users
> > > >>> >
> > > >>> >
> > > >>>
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Notes+For+Maven+3.9.x+Plugin+Developers
> > > >>> >
> > > >>> > Have fun
> > > >>> > T
> > > >>> >
> > > >>>
> > > >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>


Re: [ANN] Apache Maven 3.8.6 released

2022-06-11 Thread Dan Tran
Thanks for releasing this needed release

looks like it is slow to appear at maven central? [1]

-D

[1] https://repo1.maven.org/maven2/org/apache/maven/apache-maven/



On Sat, Jun 11, 2022 at 8:48 AM Michael Osipov  wrote:

> The Apache Maven team is pleased to announce the release of the Apache
> Maven 3.8.6
>
> Apache Maven is a software project management and comprehension tool.
> Based on the concept
> of a project object model (POM), Maven can manage a project's build,
> reporting and documentation
> from a central piece of information.
>
> Maven 3.8.6 is available via https://maven.apache.org/download.cgi
>
> The core release is independent of plugin releases. Further releases of
> plugins will be made
> separately.
>
> If you have any questions, please consult:
>
> - the web site: https://maven.apache.org/
> - the maven-user mailing list: https://maven.apache.org/mailing-lists.html
> - the reference documentation: https://maven.apache.org/ref/3.8.6/
>
>
> Release Notes - Maven - Version 3.8.6
>
> ** Bug
>  * [MNG-7432] - [REGRESSION] Resolver session contains
> non-MavenWorkspaceReader
>  * [MNG-7433] - [REGRESSION] Multiple maven instances working on
> same source tree can lock each other
>  * [MNG-7441] - Update Version of (optional) Logback to Address
> CVE-2021-42550
>  * [MNG-7448] - Don't ignore bin/ otherwise bin/ in apache-maven
> module cannot be readded
>  * [MNG-7455] - [REGRESSION] IllegalStateException in SessionScope
> during guice injection in multithreaded build
>  * [MNG-7459] - Revert MNG-7347 (SessionScoped beans should be
> singletons for a given session)
>  * [MNG-7467] - [REGRESSION] Compilation failure with relocated
> transitive dependency
>  * [MNG-7487] - Fix deadlock during forked lifecycle executions
>  * [MNG-7493] - [REGRESSION] Resolving dependencies between
> submodules fails
>
> ** New Feature
>  * [MNG-7486] - Create a multiline message helper for boxed log
> messages
>
> ** Improvement
>  * [MNG-7445] - to refactor some useless code
>  * [MNG-7476] - Display a warning when an aggregator mojo is locking
> other mojo executions
>
> ** Task
>  * [MNG-7466] - Align Assembly Descriptor NS versions
>
> ** Dependency upgrade
>  * [MNG-7488] - Upgrade SLF4J to 1.7.36
>  * [MNG-7489] - Upgrade JUnit to 4.13.2
>  * [MNG-7490] - Upgrade Plexus Utils to 3.3.1
>
>
> For more information read
> https://maven.apache.org/docs/3.8.6/release-notes.html
>
> Enjoy!
>
> - The Maven Team
>
> -
> 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.6

2022-06-07 Thread Dan Tran
+1 (non-binding) works well with my large internal product build

Thank you for pushing this new version out

-Dan

On Mon, Jun 6, 2022 at 11:30 PM Romain Manni-Bucau 
wrote:

> +1, works well on tested projects and toolings
>
> 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 lun. 6 juin 2022 à 19:18, Michael Osipov  a écrit
> :
>
> > Hi,
> >
> > We solved 16 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12351556
> >
> > There are still hundreds of issues left in JIRA:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1759/
> >
> > Dev dist directory:
> > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.6/
> >
> > Source release checksums:
> > apache-maven-3.8.6-src.zip sha512:
> >
> >
> cfa8b7e5f965d4da8d0e098889b98fccf3eec70ac500c452a5257ca9f8b5e75d200ba51d89c0be6e06072255b71d8a0c0f21ee3e3d4ba6152ea72007b497344a
> > apache-maven-3.8.6-src.tar.gz sha512:
> >
> >
> 03366d0d34bba79ce6f0d5e88390e360fbf2f61c273bc18885a21a6d4dcdf5eca14fe4d902735e4fcb03db32327be086e3927d259c519aa790f42142cfcb
> >
> > Binary release checksums:
> > apache-maven-3.8.6-bin.zip sha512:
> >
> >
> f92dbd90060c5fd422349f844ea904a0918c9c9392f3277543ce2bfb0aab941950bb4174d9b6e2ea84cd48d2940111b83ffcc2e3acf5a5b2004277105fd22be9
> > apache-maven-3.8.6-bin.tar.gz sha512:
> >
> >
> f790857f3b1f90ae8d16281f902c689e4f136ebe584aba45e4b1fa66c80cba826d3e0e52fdd04ed44b4c66f6d3fe3584a057c26dfcac544a60b301e6d0f91c26
> >
> > Draft for release notes:
> > https://github.com/apache/maven-site/pull/303
> >
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open until 2021-06-12T12:00Z
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>


Re: Upcoming Maven 3.8.6

2022-05-31 Thread Dan Tran
Hi,

possible to have 3.8.6-SNAPSHOT upload to https://repository.apache.org ?

Thanks

-D

On Mon, May 30, 2022 at 12:35 PM Michael Osipov  wrote:

> Folks,
>
> Maven 3.8.6 is complete, no more open issues. Thank you gnodet@!
>
> I'll leave people this business week to work/discuss on potential issues
> for 3.8.x. My plan is to start the release around 2022-06-06.
>
> Michael
>
> -
> 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-M6

2022-04-03 Thread Dan Tran
+1 tested with a large build running both unit and integration tests in
production using 3.0.0-M6-SNAPSHOT (not easy for us to pickup staging)

-D

On Sat, Apr 2, 2022 at 2:07 PM Sylwester Lachiewicz 
wrote:

> +1
>
> czw., 31 mar 2022, 14:35 użytkownik Tibor Digana 
> napisał:
>
> > Hi,
> >
> > We solved 111 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344613
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1731/
> >
> >
> https://repository.apache.org/content/repositories/maven-1731/org/apache/maven/surefire/surefire/3.0.0-M6/surefire-3.0.0-M6-source-release.zip
> >
> > Source release checksum(s):
> > surefire-3.0.0-M6-source-release.zip   sha512:
> >
> >
> 2ad963a52445100438c68ecc2d2eb3c3e2191a33494b255969d9ec37f1a418012b8cd71567201a87839f10a47a01d6b304a625a53d90237637755b06234f4bc7
> >
> > 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
> >
>


Re: Quick test at maven-surefire-3.0-M6-SNAPSHOT

2022-03-08 Thread Dan Tran
found this matched JIRA https://issues.apache.org/jira/browse/SUREFIRE-2033

-D

On Mon, Mar 7, 2022 at 10:39 PM Dan Tran  wrote:

> From the console log,  looks like junit4 provider got picked up first and
> lock-in?
>
> -D
>
> On Mon, Mar 7, 2022 at 9:56 PM Dan Tran  wrote:
>
>>
>> Hi
>>
>> My surefire 3.0.0-M4 classpath contains both junit4 and junit5 providers,
>> and surefire beautifully run both junit4 and junit test classes
>>
>> with  3.0-M6-SNAPSHOT,  surefire ignores all junit 5 test class
>>
>> [INFO] --- maven-surefire-plugin:3.0.0-M6-SNAPSHOT:test (default-test) @
>> xxxt ---
>> [INFO] Surefire report directory:
>> C:\x\ppdm\y\z\xxx\target\surefire-reports
>> [INFO] Using auto detected provider
>> org.apache.maven.surefire.junit4.JUnit4Provider
>> [INFO]
>> [INFO] ---
>> [INFO]  T E S T S
>> [INFO] ---
>> [INFO]
>> [INFO] Results:
>> [INFO]
>> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>> [INFO]
>>
>> is it a known issue?
>>
>> thanks
>>
>> -D
>>
>


Re: Quick test at maven-surefire-3.0-M6-SNAPSHOT

2022-03-07 Thread Dan Tran
>From the console log,  looks like junit4 provider got picked up first and
lock-in?

-D

On Mon, Mar 7, 2022 at 9:56 PM Dan Tran  wrote:

>
> Hi
>
> My surefire 3.0.0-M4 classpath contains both junit4 and junit5 providers,
> and surefire beautifully run both junit4 and junit test classes
>
> with  3.0-M6-SNAPSHOT,  surefire ignores all junit 5 test class
>
> [INFO] --- maven-surefire-plugin:3.0.0-M6-SNAPSHOT:test (default-test) @
> xxxt ---
> [INFO] Surefire report directory: C:\x\ppdm\y\z\xxx\target\surefire-reports
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junit4.JUnit4Provider
> [INFO]
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> is it a known issue?
>
> thanks
>
> -D
>


Quick test at maven-sure-3.0-M6-SNAPSHOT

2022-03-07 Thread Dan Tran
Hi

My surefire classpath contains both junit4 and junit5 providers, and
surefire beautifully run both junit4 and junit test classes

with  3.0-M6-SNAPSHOT,  surefire ignores all junit 5 test class

[INFO] --- maven-surefire-plugin:3.0.0-M6-SNAPSHOT:test (default-test) @
xxxt ---
[INFO] Surefire report directory: C:\x\ppdm\y\z\xxx\target\surefire-reports
[INFO] Using auto detected provider
org.apache.maven.surefire.junit4.JUnit4Provider
[INFO]
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]

is it a known issue?

thanks

-D


Re: [VOTE] Release Apache Maven version 3.8.5

2022-03-06 Thread Dan Tran
+1 (none-binding)

Tested with a large multi modules build running a number of times to verify
concurrency issues

Many thanks to the Maven team

-D

On Sun, Mar 6, 2022 at 12:38 AM Michael Osipov  wrote:

> Yes, have a look at MNG-7335 and MNG-7156
>
> Am 2022-03-06 um 05:30 schrieb Dan Tran:
> > Hello
> >
> > In maven 3.8.4,  Maven team reverted a number of fixes (which caused
> > regressions) related to concurrency issues.  does 3.8.5 add back the
> fixes?
> >
> > The release notes mention a couple of parallel build related fixes, but i
> > am not sure if they do address all the fixes before the revert
> >
> > Thanks
> >
> > -D
> >
> > On Sat, Mar 5, 2022 at 8:47 AM Michael Osipov 
> wrote:
> >
> >> Hi,
> >>
> >> We solved 27 issues:
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12351105
> >>
> >> There are still hundreds of issues left in JIRA:
> >>
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-1724/
> >>
> >> Dev dist directory:
> >> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.5/
> >>
> >> Source release checksums:
> >> apache-maven-3.8.5-src.zip sha512:
> >>
> >>
> 7edb6864834a81c11cf9d22a8110abc3f5f96360bdbc4bc33ec0c98dc389dd9fc71465253a87729dbe7b8a011b2ec38afa0e011172657c3a97ef96fb6f40292b
> >> apache-maven-3.8.5-src.tar.gz sha512:
> >>
> >>
> 1aa1b2dcba794b7e4cbc8e2ff9baf64283fb3883ae93efff26fe259578504b60a8b68404a074f4741922e462fa696cbbe71f9d74e4e6316ed0e389d25667
> >>
> >> Binary release checksums:
> >> apache-maven-3.8.5-bin.zip sha512:
> >>
> >>
> f9f838b4adaf23db0204a6cafa52bf1125bd2d649fd676843fd05e82866b596ec19c4f3de60d5e3ff17f10a63d96c141311ff9bc2bfa816eade7a5cbff2bd925
> >> apache-maven-3.8.5-bin.tar.gz sha512:
> >>
> >>
> 89ab8ece99292476447ef6a6800d9842bbb60787b9b8a45c103aa61d2f205a971d8c3ddfb8b03e514455b4173602bd015e82958c0b3ddc1728a57126f773c743
> >>
> >> Draft for release notes:
> >> https://github.com/apache/maven-site/pull/292
> >>
> >>
> >> Guide to testing staged releases:
> >> http://maven.apache.org/guides/development/guide-testing-releases.html
> >>
> >> Vote open until 2021-03-13T12:00Z
> >>
> >> [ ] +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 version 3.8.5

2022-03-05 Thread Dan Tran
Hello

In maven 3.8.4,  Maven team reverted a number of fixes (which caused
regressions) related to concurrency issues.  does 3.8.5 add back the fixes?

The release notes mention a couple of parallel build related fixes, but i
am not sure if they do address all the fixes before the revert

Thanks

-D

On Sat, Mar 5, 2022 at 8:47 AM Michael Osipov  wrote:

> Hi,
>
> We solved 27 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12351105
>
> There are still hundreds of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1724/
>
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.5/
>
> Source release checksums:
> apache-maven-3.8.5-src.zip sha512:
>
> 7edb6864834a81c11cf9d22a8110abc3f5f96360bdbc4bc33ec0c98dc389dd9fc71465253a87729dbe7b8a011b2ec38afa0e011172657c3a97ef96fb6f40292b
> apache-maven-3.8.5-src.tar.gz sha512:
>
> 1aa1b2dcba794b7e4cbc8e2ff9baf64283fb3883ae93efff26fe259578504b60a8b68404a074f4741922e462fa696cbbe71f9d74e4e6316ed0e389d25667
>
> Binary release checksums:
> apache-maven-3.8.5-bin.zip sha512:
>
> f9f838b4adaf23db0204a6cafa52bf1125bd2d649fd676843fd05e82866b596ec19c4f3de60d5e3ff17f10a63d96c141311ff9bc2bfa816eade7a5cbff2bd925
> apache-maven-3.8.5-bin.tar.gz sha512:
>
> 89ab8ece99292476447ef6a6800d9842bbb60787b9b8a45c103aa61d2f205a971d8c3ddfb8b03e514455b4173602bd015e82958c0b3ddc1728a57126f773c743
>
> Draft for release notes:
> https://github.com/apache/maven-site/pull/292
>
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open until 2021-03-13T12:00Z
>
> [ ] +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 Wrapper version 3.1.0

2021-12-13 Thread Dan Tran
Hi

Could you deploy a snapshot?  my company repository manager does not proxy
staging repos.

Can build from tag, generate the wrapper files, and run mvnw on some other
host, it will fail if I use the staging RC, but I can pull
maven-wrapper.jar from snapshot

Thanks

-D

On Mon, Dec 13, 2021 at 1:12 PM Manfred Moser 
wrote:

> Awesome. Thank you Herve.
>
> + 100
>
> Hervé BOUTEMY wrote on 2021-12-13 13:09 (GMT -08:00):
>
> > Hi,
> >
> > We solved 18 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12350068=Text
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1679/
> >
> https://repository.apache.org/content/repositories/maven-1679/org/apache/maven/wrapper/maven-wrapper-parent/3.1.0/maven-wrapper-parent-3.1.0-source-release.zip
> >
> > Source release checksum(s):
> > maven-wrapper-parent-3.1.0-source-release.zip sha512:
> >
> 9b7362c956cd24e21b46b290e154893ae35fd38431b6fe80f035cd17a97806e9221c71ac14975692f2a948ad25489f5b9d9bbb72441f9ab5eb541da0a86bdef9
> >
> > Staging site:
> > https://maven.apache.org/wrapper-archives/wrapper-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: reviewing Maven Wrapper before releasing

2021-12-09 Thread Dan Tran
awesome. Thanks

On Thu, Dec 9, 2021 at 12:43 AM Hervé BOUTEMY  wrote:

> this is the fix in https://issues.apache.org/jira/browse/MWRAPPER-18
>
> with wrapper 0.5.6, there was a fixed Maven version hard coded in maven-
> wrapper.jar and inconsistent local installation directory name (see Jira
> issue
> for detailed description)
>
> with MWRAPPER-18, from the distributionUrl in maven-wrapper.properties, it
> replaces the repository prefix: see the commit
>
> Regards,
>
> Hervé
>
> Le jeudi 9 décembre 2021, 09:19:09 CET Dan Tran a écrit :
> > That works,  but how does it figure out the maven version to compute the
> > full URL to download?
> >
> > Thanks
> >
> > -D
> >
> > On Wed, Dec 8, 2021 at 11:10 PM Hervé BOUTEMY 
> wrote:
> > > there is MVNW_REPOURL system property
> > > https://maven.apache.org/wrapper/#Using_a_Maven_Repository_Manager
> > >
> > > with a fix done in https://issues.apache.org/jira/browse/MWRAPPER-18
> > > (showing concrete usage output)
> > >
> > > Is it what you expected?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le jeudi 9 décembre 2021, 00:59:41 CET Dan Tran a écrit :
> > > > sorry for hi-jack this thread.  is it possible to configure mvnw to
> use
> > > > a
> > > > new location of  distributionUrl  on the fly? (without touching
> > > > maven-wrapper.properties)
> > > >
> > > > Thanks
> > > >
> > > > -D
> > > >
> > > > On Wed, Dec 8, 2021 at 11:31 AM Slawomir Jaranowski <
> > >
> > > s.jaranow...@gmail.com>
> > >
> > > > wrote:
> > > > > In current project configuration it is a bug rather ... We can use
> a
> > > > > wrapper with java 5 but we can't install it because the plugin
> > > > > requires
> > > > > java 8 ...
> > > > >
> > > > > śr., 8 gru 2021 o 20:18 Xeno Amess 
> napisał(a):
> > > > > > +1 for forcing more people quit java 5,6,7, as even 17 is out.
> > > > > > 8 is the minimum version normal people can accept,others be
> zombies
> > >
> > > who
> > >
> > > > > do
> > > > >
> > > > > > not need to be maintained IMO. They can use original wrapper
> plugin
> > > > >
> > > > > anyway.
> > > > >
> > > > > > If we do not force them when beginning,it is harder to add the
> > > > > > liminition
> > > > > > later.
> > > > > >
> > > > > > XenoAmess
> > > > > > 
> > > > > > From: Slawomir Jaranowski 
> > > > > > Sent: Thursday, December 9, 2021 3:11:42 AM
> > > > > > To: Maven Developers List 
> > > > > > Subject: Re: reviewing Maven Wrapper before releasing
> > > > > >
> > > > > > I created issues with the proposition of improvement:
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/MWRAPPER-31
> > > > > > https://issues.apache.org/jira/browse/MWRAPPER-32
> > > > > > https://issues.apache.org/jira/browse/MWRAPPER-33
> > > > > >
> > > > > > please assign a version to fix ... if it is applicable.
> > > > > >
> > > > > > śr., 8 gru 2021 o 19:47 Hervé BOUTEMY 
> > > > >
> > > > > napisał(a):
> > > > > > > because it's as it was imported:
> > > > > > >
> https://github.com/takari/maven-wrapper/blob/master/pom.xml#L21
> > > > > > > I refactored but kept everything as equivalent as possible
> > > > > > >
> > > > > > > we can update the value if it has an interest, with associated
> > > > > > > Jira
> > > > >
> > > > > issue
> > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Hervé
> > > > > > >
> > > > > > > Le mercredi 8 décembre 2021, 19:14:55 CET Slawomir Jaranowski a
> > >
> > > écrit
> > >
> > > > > > > > Next question:
> > > > > > > >  - why use java 5 in maven-wrapper module .. it is not
> possible
> > > > > > > >  build
> >

Re: reviewing Maven Wrapper before releasing

2021-12-09 Thread Dan Tran
That works,  but how does it figure out the maven version to compute the
full URL to download?

Thanks

-D

On Wed, Dec 8, 2021 at 11:10 PM Hervé BOUTEMY  wrote:

> there is MVNW_REPOURL system property
> https://maven.apache.org/wrapper/#Using_a_Maven_Repository_Manager
>
> with a fix done in https://issues.apache.org/jira/browse/MWRAPPER-18
> (showing concrete usage output)
>
> Is it what you expected?
>
> Regards,
>
> Hervé
>
> Le jeudi 9 décembre 2021, 00:59:41 CET Dan Tran a écrit :
> > sorry for hi-jack this thread.  is it possible to configure mvnw to use a
> > new location of  distributionUrl  on the fly? (without touching
> > maven-wrapper.properties)
> >
> > Thanks
> >
> > -D
> >
> > On Wed, Dec 8, 2021 at 11:31 AM Slawomir Jaranowski <
> s.jaranow...@gmail.com>
> > wrote:
> > > In current project configuration it is a bug rather ... We can use a
> > > wrapper with java 5 but we can't install it because the plugin requires
> > > java 8 ...
> > >
> > > śr., 8 gru 2021 o 20:18 Xeno Amess  napisał(a):
> > > > +1 for forcing more people quit java 5,6,7, as even 17 is out.
> > > > 8 is the minimum version normal people can accept,others be zombies
> who
> > >
> > > do
> > >
> > > > not need to be maintained IMO. They can use original wrapper plugin
> > >
> > > anyway.
> > >
> > > > If we do not force them when beginning,it is harder to add the
> > > > liminition
> > > > later.
> > > >
> > > > XenoAmess
> > > > 
> > > > From: Slawomir Jaranowski 
> > > > Sent: Thursday, December 9, 2021 3:11:42 AM
> > > > To: Maven Developers List 
> > > > Subject: Re: reviewing Maven Wrapper before releasing
> > > >
> > > > I created issues with the proposition of improvement:
> > > >
> > > > https://issues.apache.org/jira/browse/MWRAPPER-31
> > > > https://issues.apache.org/jira/browse/MWRAPPER-32
> > > > https://issues.apache.org/jira/browse/MWRAPPER-33
> > > >
> > > > please assign a version to fix ... if it is applicable.
> > > >
> > > > śr., 8 gru 2021 o 19:47 Hervé BOUTEMY 
> > >
> > > napisał(a):
> > > > > because it's as it was imported:
> > > > > https://github.com/takari/maven-wrapper/blob/master/pom.xml#L21
> > > > > I refactored but kept everything as equivalent as possible
> > > > >
> > > > > we can update the value if it has an interest, with associated Jira
> > >
> > > issue
> > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > Le mercredi 8 décembre 2021, 19:14:55 CET Slawomir Jaranowski a
> écrit
> :
> > > > > > Next question:
> > > > > >  - why use java 5 in maven-wrapper module .. it is not possible
> > > > > >  build
> > > > >
> > > > > with
> > > > >
> > > > > > java > 8 [1]
> > > > > >
> > > > > > [1]
> > >
> > >
> https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-wrapper/job/
> > > ma>
> > > > > > ster/
> > > > > > śr., 8 gru 2021 o 19:05 Hervé BOUTEMY 
> > > > >
> > > > > napisał(a):
> > > > > > > Le mercredi 8 décembre 2021, 15:52:46 CET Robert Scholte a
> écrit :
> > > > > > > > With mvn verify -Prun-its all ITs fail on my system. This
> should
> > > >
> > > > work
> > > >
> > > > > > > > out-of-the-box, so I'll need to investigate the issue.
> > > > > > > >
> > > > > > > > And I'm pretty sure we can remove the cli package: you can't
> > > > > > > > pass
> > > > >
> > > > > System
> > > > >
> > > > > > > > properties to Maven, only arguments. And they should be
> passed
> > > > > > > > as
> > > >
> > > > is
> > > >
> > > > > to
> > > > >
> > > > > > > > mvn.
> > > > > > >
> > > > > > > I must admit I don't know: I suppose that if the code is here
> from
> > > >
> > > > the
&

Re: reviewing Maven Wrapper before releasing

2021-12-08 Thread Dan Tran
sorry for hi-jack this thread.  is it possible to configure mvnw to use a
new location of  distributionUrl  on the fly? (without touching
maven-wrapper.properties)

Thanks

-D

On Wed, Dec 8, 2021 at 11:31 AM Slawomir Jaranowski 
wrote:

> In current project configuration it is a bug rather ... We can use a
> wrapper with java 5 but we can't install it because the plugin requires
> java 8 ...
>
> śr., 8 gru 2021 o 20:18 Xeno Amess  napisał(a):
>
> > +1 for forcing more people quit java 5,6,7, as even 17 is out.
> > 8 is the minimum version normal people can accept,others be zombies who
> do
> > not need to be maintained IMO. They can use original wrapper plugin
> anyway.
> > If we do not force them when beginning,it is harder to add the liminition
> > later.
> >
> > XenoAmess
> > 
> > From: Slawomir Jaranowski 
> > Sent: Thursday, December 9, 2021 3:11:42 AM
> > To: Maven Developers List 
> > Subject: Re: reviewing Maven Wrapper before releasing
> >
> > I created issues with the proposition of improvement:
> >
> > https://issues.apache.org/jira/browse/MWRAPPER-31
> > https://issues.apache.org/jira/browse/MWRAPPER-32
> > https://issues.apache.org/jira/browse/MWRAPPER-33
> >
> > please assign a version to fix ... if it is applicable.
> >
> > śr., 8 gru 2021 o 19:47 Hervé BOUTEMY 
> napisał(a):
> >
> > > because it's as it was imported:
> > > https://github.com/takari/maven-wrapper/blob/master/pom.xml#L21
> > > I refactored but kept everything as equivalent as possible
> > >
> > > we can update the value if it has an interest, with associated Jira
> issue
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mercredi 8 décembre 2021, 19:14:55 CET Slawomir Jaranowski a écrit :
> > > > Next question:
> > > >
> > > >  - why use java 5 in maven-wrapper module .. it is not possible build
> > > with
> > > > java > 8 [1]
> > > >
> > > > [1]
> > > >
> > >
> >
> https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-wrapper/job/ma
> > > > ster/
> > > > śr., 8 gru 2021 o 19:05 Hervé BOUTEMY 
> > > napisał(a):
> > > > > Le mercredi 8 décembre 2021, 15:52:46 CET Robert Scholte a écrit :
> > > > > > With mvn verify -Prun-its all ITs fail on my system. This should
> > work
> > > > > > out-of-the-box, so I'll need to investigate the issue.
> > > > > >
> > > > > > And I'm pretty sure we can remove the cli package: you can't pass
> > > System
> > > > > > properties to Maven, only arguments. And they should be passed as
> > is
> > > to
> > > > > > mvn.
> > > > >
> > > > > I must admit I don't know: I suppose that if the code is here from
> > the
> > > > > beginning, it's for some use, it's just me who did not imagine the
> > use
> > > > > case
> > > > >
> > > > > if everybody is confident that it's never used, no problem to
> remove
> > it
> > > > >
> > > > > > IT's should confirm that.
> > > > > >
> > > > > > Robert
> > > > > >
> > > > > > -- Origineel bericht --
> > > > > > Van: "Jason van Zyl" 
> > > > > > Aan: "Maven Developers List" 
> > > > > > Verzonden: 7-12-2021 14:55:32
> > > > > > Onderwerp: Re: reviewing Maven Wrapper before releasing
> > > > > >
> > > > > > >Everything builds and it generates the wrapper for a project in
> a
> > > way
> > > > >
> > > > > will
> > > > >
> > > > > > >be familiar to existing users. The switch for current users
> > should,
> > > > > > >hopefully, be painless and transparent.
> > > > > > >
> > > > > > >Nice work Robert and Hervé. I put a notice on the GitHub page
> for
> > > the
> > > > > > >Takari version about the impending release at Apache, and
> provided
> > > > > > >pointers to the new Git repository and JIRA project.
> > > > > > >
> > > > > > >jvz
> > > > > > >
> > > > > > >>  On Dec 6, 2021, at 6:07 PM, Hervé BOUTEMY <
> > herve.bout...@free.fr
> > > >
> > > > >
> > > > > wrote:
> > > > > > >>  Hi,
> > > > > > >>
> > > > > > >>  Maven Wrapper has been donated to Apache Maven, imported to
> > > > > > >>
> > > > > > >>https://github.com/apache/maven-wrapper
> > > > > > >>
> > > > > > >>  Documentation published to https://maven.apache.org/wrapper/
> > > > >
> > > > > > >>  Here is the list of fixes from previous 0.5.6 release:
> > > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721;
> > > > >
> > > > > > >>version=12350068>>
> > > > > > >>
> > > > > > >>  Please test and review so we can do a release soon
> > > > > > >>
> > > > > > >>  Regards,
> > > > > > >>
> > > > > > >>  Hervé
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > 
> > > > > > >>  -
> > > > > > >>  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: 

Re: [VOTE] Release Apache Maven version 3.8.4

2021-11-15 Thread Dan Tran
I have a concern about the reverting of a couple of Jira fixes.  is the
real fix also in this release and will arrive later?

Thanks

-D

On Mon, Nov 15, 2021 at 9:53 AM Tibor Digana  wrote:

> +1
> Cheers
> Tibor17
>
> On Sun, Nov 14, 2021 at 2:28 PM Michael Osipov 
> wrote:
>
> > Hi,
> >
> > We solved 5 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350685
> >
> > 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-1669/
> >
> > Dev dist directory:
> > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.4/
> >
> > Source release checksums:
> > apache-maven-3.8.4-src.zip sha512:
> >
> >
> 2f57dd7476ee1831867930dbe33ebe669b8fc0a9863586093a4eb2188745c5ddc2710beea1bf076263923ce38a487ef92d570bc752c77d0e0f1e3416b65bc785
> > apache-maven-3.8.4-src.tar.gz sha512:
> >
> >
> ea4b5f2b29be45d22e716099d0ef87367c78766aade094e8d7f295fe3b2c98cba2bf0f214d3ed55e2c17d2f74c82352cf9dc83fa47ddc97a8d2b847315500431
> >
> > Binary release checksums:
> > apache-maven-3.8.4-bin.zip sha512:
> >
> >
> bcd1e99548ac8a5b9ec159ee16c23d29d6799696c92140d583d25eb323433aadcc0b47c45b0b6bd9dbcf344bbba38b56dd056a9c49ae714cfc22dc06bb4a4230
> > apache-maven-3.8.4-bin.tar.gz sha512:
> >
> >
> a9b2d825eacf2e771ed5d6b0e01398589ac1bfa4171f36154d1b5787879605507802f699da6f7cfc80732a5282fd31b28e4cd6052338cbef0fa1358b48a5e3c8
> >
> > Draft for release notes:
> > https://github.com/apache/maven-site/pull/274
> >
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open until 2021-11-19T18:00Z
> >
> > [ ] +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 version 3.8.2

2021-08-11 Thread Dan Tran
sounds to me, it impacts any plugin creating a class loader? such jaxws?

-D

On Wed, Aug 11, 2021 at 4:20 AM Olivier Lamy  wrote:

> On Wed, 11 Aug 2021 at 21:16, Michael Osipov  wrote:
>
> > Merci Olivier for testing.
> > Would you say that the change in Maven just revealed this bug in that
> > particular plugin?
> >
>
> Yes we can say that :)
> I just hope no other plugins do something similar
>
>
>
> > Am 2021-08-11 um 06:03 schrieb Olivier Lamy:
> > > did the bisect and found this
> > >
> > > *➜  **maven-core* *git:(**42c99b45e**)* git bisect good
> > >
> > > 76d5f0d942f52650d3bdf775b6af42d23d69066b is the first bad commit
> > >
> > > commit 76d5f0d942f52650d3bdf775b6af42d23d69066b
> > >
> > > Author: Falko Modler 
> > >
> > > Date:   Fri Jun 25 19:28:40 2021 +0200
> > >
> > >
> > >  [MNG-6843] Parallel build fails due to missing JAR artifacts in
> > > compilePath
> > >
> > >
> > >
> > >  Signed-off-by: rfscholte 
> > >
> > >  (cherry picked from commit
> 73e00ed85df84ba0c557dd020740812b2453f2d3)
> > >
> > >
> > >
> > >  This closes #482
> > >
> > >
> > >   .../org/apache/maven/project/MavenProject.java | 67 
> > > --
> > >
> > >   1 file changed, 36 insertions(+), 31 deletions(-)
> > >
> > >
> > >
> > > There is a simple fix in the mentioned plugin (and btw the fix is
> needed
> > :)
> > > )
> > > So if a mojo creates a new Thread and tries to get some values from
> > > MavenProject the result might change (because of this new threadLocal
> > > field).
> > >
> > > not changing my vote but it's still a change and possible failure
> > >
> > >
> > > On Wed, 11 Aug 2021 at 11:29, Olivier Lamy  wrote:
> > >
> > >> interesting this code change in the plugin fix the issue with the
> staged
> > >> 3.8.2
> > >>
> > >>
> >
> https://github.com/jetty-project/h2spec-maven-plugin/commit/a752521d12c59347a0995d01160332af28e3f092
> > >>
> > >> looking at commits log not sure if we touched something related to
> > thread
> > >> context classloader?
> > >>
> > >> On Wed, 11 Aug 2021 at 09:11, Olivier Lamy  wrote:
> > >>
> > >>> found some breaking change.
> > >>> this plugin is not working anymore:
> > >>> https://github.com/jetty-project/h2spec-maven-plugin
> > >>> mvn verify
> > >>> got ClassNotFoundException
> > >>>
> > >>> On Wed, 11 Aug 2021 at 03:50, Falko Modler  wrote:
> > >>>
> >  I checked it briefly with Quarkus (almost 1k modules) and I couldn't
> >  really see a difference.
> > 
> >  Cheers,
> >  Falko
> > 
> > 
> -
> >  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >  For additional commands, e-mail: dev-h...@maven.apache.org
> > 
> > 
> > >>>
> > >>> --
> > >>> Olivier Lamy
> > >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> > >>>
> > >>
> > >>
> > >> --
> > >> Olivier Lamy
> > >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> > >>
> > >
> > >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>


Re: [VOTE] Release Apache Maven version 3.8.2

2021-08-10 Thread Dan Tran
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

2021-08-09 Thread Dan Tran
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

2021-08-05 Thread Dan Tran
tested with my company internal build with 300+ modules.  the build time
increase by 10%. Not sure if anyone sees the same. but I am happy to take
it due to the fix at the classpath concurrency issue.

Thanks for pushing this out

-D

On Thu, Aug 5, 2021 at 1:23 PM Tamás Cservenák  wrote:

> +1
>
> T
>
> On Wed, Aug 4, 2021 at 10:02 PM 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
> >
> >
>


Re: Upcoming Maven 3.8.2

2021-07-22 Thread Dan Tran
looking forward to the release.  please ensure to have the latest snapshot
deployed.

Thank you for the awesome work.

-D

On Thu, Jul 22, 2021 at 11:37 AM Arnaud Héritier 
wrote:

> Awesome work.
> Well done team
>
> On Sat, Jul 3, 2021 at 4:31 PM Michael Osipov  wrote:
>
> > Folks,
> >
> > I have ported approx. 50 non-invasive issues back to maven-3.8.x branch
> > and it is in a very good shape.
> > There are only two issues open (one blocker):
> > * https://issues.apache.org/jira/browse/MNG-7161
> > * https://issues.apache.org/jira/browse/MNG-7034
> > (https://github.com/apache/maven/pull/484)
> >
> > I kindly asked gnodet@ for help to resolve them.
> >
> > Do you see any other issues either from 4.0.0-alpha-1 or others which
> > need to be addressed in 3.8.2?
> >
> > M
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> Arnaud Héritier
> Twitter/Skype : aheritier
>


Re: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath

2021-07-11 Thread Dan Tran
Thanks, will hook it up with our internal build

On Sun, Jul 11, 2021 at 6:59 PM Olivier Lamy  wrote:

> done
>
> On Sun, 11 Jul 2021 at 07:44, Dan Tran  wrote:
>
> > possible to push the latest snapshot to
> >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-maven
> > ?
> >
> > Thanks
> >
> > -D
> >
> > On Sat, Jul 10, 2021 at 2:33 PM Dan Tran  wrote:
> >
> > > Thanks,  I will test out the latest 3.8
> > >
> > > -D
> > >
> > > On Sat, Jul 10, 2021 at 12:29 PM Falko Modler 
> wrote:
> > >
> > >> Done already: https://github.com/apache/maven/pull/482
> > >>
> > >> Cheers,
> > >> Falko
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > >> For additional commands, e-mail: dev-h...@maven.apache.org
> > >>
> > >>
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>


Re: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath

2021-07-10 Thread Dan Tran
possible to push the latest snapshot to
https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-maven
?

Thanks

-D

On Sat, Jul 10, 2021 at 2:33 PM Dan Tran  wrote:

> Thanks,  I will test out the latest 3.8
>
> -D
>
> On Sat, Jul 10, 2021 at 12:29 PM Falko Modler  wrote:
>
>> Done already: https://github.com/apache/maven/pull/482
>>
>> Cheers,
>> Falko
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>


Re: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath

2021-07-10 Thread Dan Tran
Thanks,  I will test out the latest 3.8

-D

On Sat, Jul 10, 2021 at 12:29 PM Falko Modler  wrote:

> Done already: https://github.com/apache/maven/pull/482
>
> Cheers,
> Falko
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath

2021-07-10 Thread Dan Tran
I think this is the one   https://github.com/apache/maven/pull/413

-D

On Sat, Jul 10, 2021 at 2:56 AM Michael Osipov  wrote:

> Am 2021-07-10 um 00:52 schrieb Dan Tran:
> > ah sorry, the proposed PR merged into master.  Can we back port it to
> 3.8?
>
> Which PR exactly?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath

2021-07-09 Thread Dan Tran
ah sorry, the proposed PR merged into master.  Can we back port it to 3.8?

-D

On Fri, Jul 9, 2021 at 3:47 PM Dan Tran  wrote:

> ping again :-) to keep discussion going :-)
>
> -D
>
> On Tue, May 18, 2021 at 6:20 AM Guillaume Nodet  wrote:
>
>> Maybe not that many people are using parallel builds...
>> Imho, the PR should be merged.  I've created
>> https://issues.apache.org/jira/browse/MNG-7157 to provide a better API
>> and deprecate the getArtifacts() method which is flawed (see discussion on
>> the PR https://github.com/apache/maven/pull/413#issuecomment-841720517).
>>
>> Le mar. 4 mai 2021 à 15:15, Michael Osipov  a écrit
>> :
>>
>> > Am 2021-05-03 um 22:15 schrieb Falko Modler:
>> > > Earlier today Michael Osipov added this note to the ticket:
>> > >
>> > > I confirm that this still happens on Maven master with Resolver
>> > > 1.7.0-SNAPSHOT. This isn't Resolver related because no dependency
>> > > resolution happens in the build.
>> >
>> > I am still confused why only a few suffer from this. Is this related to
>> > dependency inheritance?
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>> >
>>
>> --
>> 
>> Guillaume Nodet
>>
>


Re: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath

2021-07-09 Thread Dan Tran
ping again :-) to keep discussion going :-)

-D

On Tue, May 18, 2021 at 6:20 AM Guillaume Nodet  wrote:

> Maybe not that many people are using parallel builds...
> Imho, the PR should be merged.  I've created
> https://issues.apache.org/jira/browse/MNG-7157 to provide a better API
> and deprecate the getArtifacts() method which is flawed (see discussion on
> the PR https://github.com/apache/maven/pull/413#issuecomment-841720517).
>
> Le mar. 4 mai 2021 à 15:15, Michael Osipov  a écrit :
>
> > Am 2021-05-03 um 22:15 schrieb Falko Modler:
> > > Earlier today Michael Osipov added this note to the ticket:
> > >
> > > I confirm that this still happens on Maven master with Resolver
> > > 1.7.0-SNAPSHOT. This isn't Resolver related because no dependency
> > > resolution happens in the build.
> >
> > I am still confused why only a few suffer from this. Is this related to
> > dependency inheritance?
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> 
> Guillaume Nodet
>


Re: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath

2021-05-02 Thread Dan Tran
we are in pain with this issue :-)

-D

On Sun, Jan 24, 2021 at 2:56 PM Tibor Digana  wrote:

> Hi Falco,
>
> This is not the first time I have been talking about these principles in
> our team.
> Seven years ago and then in 2019. But sorry I cannot force the people to do
> it and they have to start by themself. We have to do it together.
> All I can do is to provide some training and elaborate a problem but I am
> convinced that we will meet again after the next seven years if we
> don't understand the JMM. Thus we should prevent from redoing the same bad
> and understand the process on how to make the code better in the early
> beginning.
>
> Cheers
> Tibor17
>
>
> On Sun, Jan 24, 2021 at 10:51 PM Falko Modler  wrote:
>
> > Hi Tibor,
> >
> > thanks for this very elaborate answer and I always appreciate your
> > feedback, but to me it kind of misses the point a bit...?
> >
> > > may not necessarily have to do with concurrent access.
> > But it does in this special case. Please see the issue and the linked
> > explanations.
> >
> > > The solution with ThreadLocal would eat too much memory.
> > Is that so? Are you sure about this? How much is "too much"?
> > Are there any predefined profiling tests I can run?
> >
> > I mean: yes, it is a workaround and immutable core classes that are
> > _designed_ for concurrent access would be much better,
> > but who is going to do such a massive refactoring (without breaking
> > Maven extensions that are today mutating MavenProject etc.)?
> >
> > TBH, this is one of the, IMHO, critical bugs that should have been fixed
> > before Maven 4.
> >
> > Cheers,
> > Falko
> >
> > Am 21.01.2021 um 02:13 schrieb Tibor Digana:
> > > I commented on one issue regarding the NULL JAR file in Artifact a few
> > days
> > > ago.
> > > The thing that some data is "missing" in some large object structures
> in
> > > the environment with multiple threads may not necessarily have to do
> with
> > > concurrent access.
> > > There may not be any writes to MavenProject or MavenSession causing
> > > "missed" data, and the answer why this happens is Memory Model.
> > >
> > > It's the fact that non-concurrent or non-immutable objects may lose
> some
> > > references very easily!
> > > This has all to do with JMM and not the happens-before relationship.
> > >
> > > Suppose that we have thread T1 creating ArrayList and adding elements
> > into
> > > this collection.
> > > artifacts = new ArrayList();
> > > artifacts.add(new DefaultArtifact(...));
> > >
> > > Suppose thread T2 reads the artifacts from the collection right after
> > > "artifacts.add()".
> > > Artifact a = artifacts.get(0);
> > >
> > > In practice the following happens:
> > > artifacts.size() returns 1
> > > but artifacts.get(0) returns NULL
> > >
> > > Let;s explain why it happens.
> > > The implementation of ArrayList is not native. It is a pure Java
> > > implementation which has two variables inside:
> > > + count:int
> > > + array:Object[]
> > > These two variables always appear in a critical section and they do not
> > > have proper treatments in ArrayList.
> > > Technically, the things are complicated on the CPU level and more
> > > complicated than happens-before theorems.
> > > T1 contains pointers and data in CPU registers or CPU cache. No Thread
> > has
> > > a direct access to a stack of another Thread, and of course it does not
> > > operate on main memory.
> > > The CPU uses memory barriers (assembler instructions) and a cache to
> > > operate with RAM and memory coherency.
> > > These instructions are used via Java keywords: final, volatile and
> > > synchronized.
> > > T2 may not see all elements completely from the ArrayList because there
> > are
> > > no safety mechanisms in the implementation of ArrayList to make this
> > happen.
> > > Thus the T2 may see the values in the Java variable "count" *but it may
> > not
> > > see the values in* "array", or vice versa.
> > >
> > > The results are NPE, or missing JAR artifacts or the issues with Maven
> > > Resolver, as we can see in https://github.com/apache/maven/pull/310
> > >
> > > The solution with ThreadLocal would eat too much memory.
> > > Reimplementing the POJO classes in Maven and making them t

Re: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath

2021-01-16 Thread Dan Tran
we are facing the same issue at work (300+ modules), classpath
empty randomly empty

Love to see some resolution, will help to test it

Thanks

-D

On Fri, Jan 15, 2021 at 1:51 PM Falko Modler  wrote:

> Hi everyone,
>
> I'd like to raise awareness for the MavenProject concurrency problem
> that is causing MNG-6843 "Parallel build fails due to missing JAR
> artifacts in compilePath" [1] and probably others [2] [3] [4].
>
> Almost a month ago, I created a ThreadLocal-based fix for this [5]
> (after another, older cloning-based approach had raised some concerns by
> Robert Scholte [6]).
>
> Michael Osipov was the only one so far having a look (thanks!) and he
> suggested that more Maven team members should review this.
>
> So, before I take a stab at the not so trivial integration test that
> Michael proposed [7], I'd like to get an approval for the general
> aproach (or a declination in case someone has a better idea).
>
> Thanks for your attention and feedback!
>
> Cheers,
>
> Falko
>
>
> [1] https://issues.apache.org/jira/browse/MNG-6843
>
> [2] https://issues.apache.org/jira/browse/MNG-4996
>
> [3] https://issues.apache.org/jira/browse/MNG-5750
>
> [4] https://issues.apache.org/jira/browse/MNG-5960
>
> [5] https://github.com/apache/maven/pull/413
>
> [6] https://github.com/apache/maven/pull/310#issuecomment-571317501
>
> [7] https://github.com/apache/maven/pull/413#issuecomment-754661032
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Release Maven Resolver version 1.6.1

2020-10-05 Thread Dan Tran
+1 none-binding

However, I still see random compilation failure at my multiple thread
build. I am hoping the latest maven-resolver would make it go away :-)

Thanks

-D

On Sun, Oct 4, 2020 at 3:16 PM Hervé BOUTEMY  wrote:

> +1
>
> this time, I could reproduce the build, done with JDK 8 on Windows
>
> Regards,
>
> Hervé
>
> Le vendredi 2 octobre 2020, 20:32:20 CEST Michael Osipov a écrit :
> > Hi,
> >
> > We solved 25 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628
> > rsion=12348853
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissue
> > s
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1607/
> >
> https://repository.apache.org/content/repositories/maven-1607/org/apache/mav
> > en/resolver/maven-resolver/1.6.1/maven-resolver-1.6.1-source-release.zip
> >
> > Source release checksum(s):
> > maven-resolver-1.6.1-source-release.zip
> >
> ab45c772e9af4061977feb4fb48e3ae9ddd8cbebe41ada40f2a762504e96fd4c0fd4a939ab70
> > 7667d9888caf92ab9fa354abe0624031c7049b7a2cb133421ddd
> >
> > Staging site:
> > https://maven.apache.org/resolver-archives/resolver-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Note: This Resolver offers salvation from a 13.5 years old feature
> > request: MNG-2802
> > Yes, you can have now concurrent-safe access to your local Maven
> > repository synchronized with Redis.
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Release Maven Resolver version 1.6.0

2020-09-26 Thread Dan Tran
without  -Daether.checksums.algorithms=SHA1,MD5,  very slow

-D

On Sat, Sep 26, 2020 at 3:11 PM Michael Osipov  wrote:

> Awesome, what about with the fix, but with the default list of hashing
> algos (SHA-512, SHA-256, SHA-1, MD5) in place?
>
> Am 2020-09-27 um 00:07 schrieb Dan Tran:
> > it works using the provided commitID +
> >-Daether.checksums.algorithms=SHA1,MD5
> >
> > -D
> >
> > On Sat, Sep 26, 2020 at 2:25 PM Michael Osipov 
> wrote:
> >
> >> Gosh, I assumed so. Every SHA family is horrible in terms of
> >> performance. This is going to be a huge problem for the community, I
> >> would prefer Blake2 or Blake3 for this.
> >>
> >> Anyway, I think this is the root cause, actually the fix:
> >>
> >>
> https://github.com/apache/maven-resolver/commit/a9e0ca8307e532fc30591a47d7d96e27fa647465
> >>
> >> Can you please try with the property set
> >> (-Daether.checksums.algorithms=SHA1,MD5)?
> >>
> >> Thrilled to see your results. If this works, please remove the property
> >> and see whether the patch along with SHA-2 on URLs changes the
> >> performance as well.
> >>
> >> Michael
> >>
> >> Am 2020-09-26 um 21:45 schrieb Dan Tran:
> >>> I am able to pin down the problematic commit:
> >>>
> >>
> https://github.com/apache/maven-resolver/commit/8e8a4f1944a0589397e36a5dd049ec765424e863
> >>>
> >>> Adding -Daether.checksums.algorithms=SHA1,MD5  to maven command line
> does
> >>> not help
> >>>
> >>> Sorry about the delay
> >>>
> >>> -D
> >>>
> >>> On Wed, Sep 16, 2020 at 1:57 AM Michael Osipov 
> >> wrote:
> >>>
> >>>> Your logging config is sound, so appearently nothing is wrong.
> >>>> You see no trace because DefaultSyncContextFactory is empty and there
> is
> >>>> nothing to trace. Something else is the cause.
> >>>>
> >>>> Can you git bisect 1.4.2 and 1.6.0 to find the offending commit?
> >>>> Otherwise I have no idea and we are searching the needle in the
> >> haystack.
> >>>>
> >>>> The only commits which come to my mind are:
> >>>> *
> >>>>
> >>>>
> >>
> https://github.com/apache/maven-resolver/commit/8e8a4f1944a0589397e36a5dd049ec765424e863?w=1
> >>>>
> >>>> You can disable/restore this one by using:
> >>>> -Daether.checksums.algorithms=SHA1,MD5 (previous behavior)
> >>>>
> >>>> *
> >>>>
> >>>>
> >>
> https://github.com/apache/maven-resolver/commit/3c2a5141c9d393a45bdee873e6aa2c9c275b7b58?w=1
> >>>>
> >>>> But still this wouldn't make any sense.
> >>>>
> >>>> Looking forward for some findings.
> >>>>
> >>>> Am 2020-09-15 um 22:45 schrieb Dan Tran:
> >>>>> this is my log config
> >>>>>
> >>>>> org.slf4j.simpleLogger.defaultLogLevel=info
> >>>>> org.slf4j.simpleLogger.showDateTime=true
> >>>>> org.slf4j.simpleLogger.showThreadName=true
> >>>>> org.slf4j.simpleLogger.showShortLogName=true
> >>>>> org.slf4j.simpleLogger.showLogName=false
> >>>>> org.slf4j.simpleLogger.logFile=System.out
> >>>>> org.slf4j.simpleLogger.cacheOutputStream=true
> >>>>> org.slf4j.simpleLogger.levelInBrackets=true
> >>>>> org.slf4j.simpleLogger.log.Sisu=info
> >>>>> org.slf4j.simpleLogger.warnLevelString=WARNING
> >>>>>
> >>>>> # MNG-6181: mvn -X also prints all debug logging from HttpClient
> >>>>> # Be aware that the shaded packages are used
> >>>>> # org.apache.http -> org.apache.maven.wagon.providers.http.httpclient
> >>>>>
> >>>>
> >>
> org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=off
> >>>>>
> >>>>
> >>
> org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off
> >>>>>
> >>>>> org.slf4j.simpleLogger.log.org.eclipse.aether.synccontext=trace
> >>>>>
> >>>>>
> >>>>> no sign of [TRACE]
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Tue, Sep 15, 2020 at 1:30 PM D

Re: [VOTE] Release Maven Resolver version 1.6.0

2020-09-26 Thread Dan Tran
it works using the provided commitID +
  -Daether.checksums.algorithms=SHA1,MD5

-D

On Sat, Sep 26, 2020 at 2:25 PM Michael Osipov  wrote:

> Gosh, I assumed so. Every SHA family is horrible in terms of
> performance. This is going to be a huge problem for the community, I
> would prefer Blake2 or Blake3 for this.
>
> Anyway, I think this is the root cause, actually the fix:
>
> https://github.com/apache/maven-resolver/commit/a9e0ca8307e532fc30591a47d7d96e27fa647465
>
> Can you please try with the property set
> (-Daether.checksums.algorithms=SHA1,MD5)?
>
> Thrilled to see your results. If this works, please remove the property
> and see whether the patch along with SHA-2 on URLs changes the
> performance as well.
>
> Michael
>
> Am 2020-09-26 um 21:45 schrieb Dan Tran:
> > I am able to pin down the problematic commit:
> >
> https://github.com/apache/maven-resolver/commit/8e8a4f1944a0589397e36a5dd049ec765424e863
> >
> > Adding -Daether.checksums.algorithms=SHA1,MD5  to maven command line does
> > not help
> >
> > Sorry about the delay
> >
> > -D
> >
> > On Wed, Sep 16, 2020 at 1:57 AM Michael Osipov 
> wrote:
> >
> >> Your logging config is sound, so appearently nothing is wrong.
> >> You see no trace because DefaultSyncContextFactory is empty and there is
> >> nothing to trace. Something else is the cause.
> >>
> >> Can you git bisect 1.4.2 and 1.6.0 to find the offending commit?
> >> Otherwise I have no idea and we are searching the needle in the
> haystack.
> >>
> >> The only commits which come to my mind are:
> >> *
> >>
> >>
> https://github.com/apache/maven-resolver/commit/8e8a4f1944a0589397e36a5dd049ec765424e863?w=1
> >>
> >> You can disable/restore this one by using:
> >> -Daether.checksums.algorithms=SHA1,MD5 (previous behavior)
> >>
> >> *
> >>
> >>
> https://github.com/apache/maven-resolver/commit/3c2a5141c9d393a45bdee873e6aa2c9c275b7b58?w=1
> >>
> >> But still this wouldn't make any sense.
> >>
> >> Looking forward for some findings.
> >>
> >> Am 2020-09-15 um 22:45 schrieb Dan Tran:
> >>> this is my log config
> >>>
> >>> org.slf4j.simpleLogger.defaultLogLevel=info
> >>> org.slf4j.simpleLogger.showDateTime=true
> >>> org.slf4j.simpleLogger.showThreadName=true
> >>> org.slf4j.simpleLogger.showShortLogName=true
> >>> org.slf4j.simpleLogger.showLogName=false
> >>> org.slf4j.simpleLogger.logFile=System.out
> >>> org.slf4j.simpleLogger.cacheOutputStream=true
> >>> org.slf4j.simpleLogger.levelInBrackets=true
> >>> org.slf4j.simpleLogger.log.Sisu=info
> >>> org.slf4j.simpleLogger.warnLevelString=WARNING
> >>>
> >>> # MNG-6181: mvn -X also prints all debug logging from HttpClient
> >>> # Be aware that the shaded packages are used
> >>> # org.apache.http -> org.apache.maven.wagon.providers.http.httpclient
> >>>
> >>
> org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=off
> >>>
> >>
> org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off
> >>>
> >>> org.slf4j.simpleLogger.log.org.eclipse.aether.synccontext=trace
> >>>
> >>>
> >>> no sign of [TRACE]
> >>>
> >>>
> >>>
> >>> On Tue, Sep 15, 2020 at 1:30 PM Dan Tran  wrote:
> >>>
> >>>> Maven 3.7.0 with Resolver 1.4.2   -  no issue
> >>>>
> >>>> Maven 3.7.0 with Resolver 1.6.0  + trace.  I cant get any indication
> >>>> about
> >>>>
> >>>> 4626 [main] [TRACE] GlobalSyncContextFactory$GlobalSyncContext -
> >> Acquiring global...
> >>>> 35318 [main] [TRACE] GlobalSyncContextFactory$GlobalSyncContext -
> >> Releasing global...
> >>>>
> >>>>
> >>>> Very strange
> >>>>
> >>>> -D
> >>>>
> >>>> On Tue, Sep 15, 2020 at 4:37 AM Michael Osipov 
> >>>> wrote:
> >>>>
> >>>>> There is no new feature active in 1.6.0 in this regard.
> >>>>> Here is the diff:
> >>>>>
> >>>>>
> >>
> https://github.com/apache/maven-resolver/compare/maven-resolver-1.4.2...maven-resolver-1.6.0?w=1
> >>>>>
> >>>>> Since I do not have access to your project, ca

Re: [VOTE] Release Maven Resolver version 1.6.0

2020-09-26 Thread Dan Tran
I am able to pin down the problematic commit:
https://github.com/apache/maven-resolver/commit/8e8a4f1944a0589397e36a5dd049ec765424e863

Adding -Daether.checksums.algorithms=SHA1,MD5  to maven command line does
not help

Sorry about the delay

-D

On Wed, Sep 16, 2020 at 1:57 AM Michael Osipov  wrote:

> Your logging config is sound, so appearently nothing is wrong.
> You see no trace because DefaultSyncContextFactory is empty and there is
> nothing to trace. Something else is the cause.
>
> Can you git bisect 1.4.2 and 1.6.0 to find the offending commit?
> Otherwise I have no idea and we are searching the needle in the haystack.
>
> The only commits which come to my mind are:
> *
>
> https://github.com/apache/maven-resolver/commit/8e8a4f1944a0589397e36a5dd049ec765424e863?w=1
>
> You can disable/restore this one by using:
> -Daether.checksums.algorithms=SHA1,MD5 (previous behavior)
>
> *
>
> https://github.com/apache/maven-resolver/commit/3c2a5141c9d393a45bdee873e6aa2c9c275b7b58?w=1
>
> But still this wouldn't make any sense.
>
> Looking forward for some findings.
>
> Am 2020-09-15 um 22:45 schrieb Dan Tran:
> > this is my log config
> >
> > org.slf4j.simpleLogger.defaultLogLevel=info
> > org.slf4j.simpleLogger.showDateTime=true
> > org.slf4j.simpleLogger.showThreadName=true
> > org.slf4j.simpleLogger.showShortLogName=true
> > org.slf4j.simpleLogger.showLogName=false
> > org.slf4j.simpleLogger.logFile=System.out
> > org.slf4j.simpleLogger.cacheOutputStream=true
> > org.slf4j.simpleLogger.levelInBrackets=true
> > org.slf4j.simpleLogger.log.Sisu=info
> > org.slf4j.simpleLogger.warnLevelString=WARNING
> >
> > # MNG-6181: mvn -X also prints all debug logging from HttpClient
> > # Be aware that the shaded packages are used
> > # org.apache.http -> org.apache.maven.wagon.providers.http.httpclient
> >
> org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=off
> >
> org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off
> >
> > org.slf4j.simpleLogger.log.org.eclipse.aether.synccontext=trace
> >
> >
> > no sign of [TRACE]
> >
> >
> >
> > On Tue, Sep 15, 2020 at 1:30 PM Dan Tran  wrote:
> >
> >> Maven 3.7.0 with Resolver 1.4.2   -  no issue
> >>
> >> Maven 3.7.0 with Resolver 1.6.0  + trace.  I cant get any indication
> >> about
> >>
> >> 4626 [main] [TRACE] GlobalSyncContextFactory$GlobalSyncContext -
> Acquiring global...
> >> 35318 [main] [TRACE] GlobalSyncContextFactory$GlobalSyncContext -
> Releasing global...
> >>
> >>
> >> Very strange
> >>
> >> -D
> >>
> >> On Tue, Sep 15, 2020 at 4:37 AM Michael Osipov 
> >> wrote:
> >>
> >>> There is no new feature active in 1.6.0 in this regard.
> >>> Here is the diff:
> >>>
> >>>
> https://github.com/apache/maven-resolver/compare/maven-resolver-1.4.2...maven-resolver-1.6.0?w=1
> >>>
> >>> Since I do not have access to your project, can you please try the
> >>> following:
> >>> * Maven 3.7.0 with Resolver 1.4.2
> >>> * Maven 3.6.3 with Resolver 1.6.0
> >>> * If 3.7.0/1.4.2 does not affect the build, do a git bisect with 1.4.2
> >>> and 1.6.0.
> >>>
> >>> Alternatively, provide the log output as configured here:
> >>>
> >>>
> https://maven.apache.org/resolver-archives/resolver-LATEST/maven-resolver-synccontext-global/index.html#Debugging
> >>>
> >>> In 1.6.0 there is even less synchronization because the
> >>> TrackingFileManager does not lock anything anymore.
> >>>
> >>> I will hold off vote completion until I get some analyzable data from
> you.
> >>>
> >>> Michael
> >>>
> >>>
> >>> Am 2020-09-15 um 11:49 schrieb Dan Tran:
> >>>> I build maven 3.7.0 + MResolve 1.6.0.  The same slow build observed at
> >>> my
> >>>> 300+ modules  ( 60min versus 5min)
> >>>>
> >>>> -1 ( non-binding) from me.  there must and option to disable this new
> >>>> feature
> >>>>
> >>>> -D
> >>>>
> >>>> On Mon, Sep 14, 2020 at 4:33 AM Michael Osipov 
> >>> wrote:
> >>>>
> >>>>> Am 2020-09-14 um 10:57 schrieb Dan Tran:
> >>>>>> sorry about the fast finger,  my test shows a huge increase in build
> >>> time
>

Re: [VOTE] Release Maven Resolver version 1.6.0

2020-09-15 Thread Dan Tran
this is my log config

org.slf4j.simpleLogger.defaultLogLevel=info
org.slf4j.simpleLogger.showDateTime=true
org.slf4j.simpleLogger.showThreadName=true
org.slf4j.simpleLogger.showShortLogName=true
org.slf4j.simpleLogger.showLogName=false
org.slf4j.simpleLogger.logFile=System.out
org.slf4j.simpleLogger.cacheOutputStream=true
org.slf4j.simpleLogger.levelInBrackets=true
org.slf4j.simpleLogger.log.Sisu=info
org.slf4j.simpleLogger.warnLevelString=WARNING

# MNG-6181: mvn -X also prints all debug logging from HttpClient
# Be aware that the shaded packages are used
# org.apache.http -> org.apache.maven.wagon.providers.http.httpclient
org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=off
org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off

org.slf4j.simpleLogger.log.org.eclipse.aether.synccontext=trace


no sign of [TRACE]



On Tue, Sep 15, 2020 at 1:30 PM Dan Tran  wrote:

> Maven 3.7.0 with Resolver 1.4.2   -  no issue
>
> Maven 3.7.0 with Resolver 1.6.0  + trace.  I cant get any indication
> about
>
> 4626 [main] [TRACE] GlobalSyncContextFactory$GlobalSyncContext - Acquiring 
> global...
> 35318 [main] [TRACE] GlobalSyncContextFactory$GlobalSyncContext - Releasing 
> global...
>
>
> Very strange
>
> -D
>
> On Tue, Sep 15, 2020 at 4:37 AM Michael Osipov 
> wrote:
>
>> There is no new feature active in 1.6.0 in this regard.
>> Here is the diff:
>>
>> https://github.com/apache/maven-resolver/compare/maven-resolver-1.4.2...maven-resolver-1.6.0?w=1
>>
>> Since I do not have access to your project, can you please try the
>> following:
>> * Maven 3.7.0 with Resolver 1.4.2
>> * Maven 3.6.3 with Resolver 1.6.0
>> * If 3.7.0/1.4.2 does not affect the build, do a git bisect with 1.4.2
>> and 1.6.0.
>>
>> Alternatively, provide the log output as configured here:
>>
>> https://maven.apache.org/resolver-archives/resolver-LATEST/maven-resolver-synccontext-global/index.html#Debugging
>>
>> In 1.6.0 there is even less synchronization because the
>> TrackingFileManager does not lock anything anymore.
>>
>> I will hold off vote completion until I get some analyzable data from you.
>>
>> Michael
>>
>>
>> Am 2020-09-15 um 11:49 schrieb Dan Tran:
>> > I build maven 3.7.0 + MResolve 1.6.0.  The same slow build observed at
>> my
>> > 300+ modules  ( 60min versus 5min)
>> >
>> > -1 ( non-binding) from me.  there must and option to disable this new
>> > feature
>> >
>> > -D
>> >
>> > On Mon, Sep 14, 2020 at 4:33 AM Michael Osipov 
>> wrote:
>> >
>> >> Am 2020-09-14 um 10:57 schrieb Dan Tran:
>> >>> sorry about the fast finger,  my test shows a huge increase in build
>> time
>> >>> for large builds.  Possible to disable this feature?
>> >>
>> >> This cannot be. It has been superceded by
>> >> https://issues.apache.org/jira/browse/MRESOLVER-130. The
>> >> GlobalSyncContextFactory have been moved to a separate module, the
>> >> original behavior has been restored. I.e., this feature is not enabled
>> >> by default.
>> >>
>> >> Are you certain that you don't have leftovers in ${maven.home}/lib/ext?
>> >>
>> >>> On Mon, Sep 14, 2020 at 1:49 AM Dan Tran  wrote:
>> >>>
>> >>>> possible to disable this feature
>> >>>> https://issues.apache.org/jira/browse/MRESOLVER-123 ?
>> >>>>
>> >>>> On Mon, Sep 14, 2020 at 12:06 AM Romain Manni-Bucau <
>> >> rmannibu...@gmail.com>
>> >>>> wrote:
>> >>>>
>> >>>>> +1, tested in java 8 with mvn 3.6.3.
>> >>>>>
>> >>>>> 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 lun. 14 sept. 2020 à 08:58, Enrico Olivelli 
>> a
>> >>>>> écrit :
>> >>>>>
>> >>

Re: [VOTE] Release Maven Resolver version 1.6.0

2020-09-15 Thread Dan Tran
Maven 3.7.0 with Resolver 1.4.2   -  no issue

Maven 3.7.0 with Resolver 1.6.0  + trace.  I cant get any indication about

4626 [main] [TRACE] GlobalSyncContextFactory$GlobalSyncContext -
Acquiring global...
35318 [main] [TRACE] GlobalSyncContextFactory$GlobalSyncContext -
Releasing global...


Very strange

-D

On Tue, Sep 15, 2020 at 4:37 AM Michael Osipov  wrote:

> There is no new feature active in 1.6.0 in this regard.
> Here is the diff:
>
> https://github.com/apache/maven-resolver/compare/maven-resolver-1.4.2...maven-resolver-1.6.0?w=1
>
> Since I do not have access to your project, can you please try the
> following:
> * Maven 3.7.0 with Resolver 1.4.2
> * Maven 3.6.3 with Resolver 1.6.0
> * If 3.7.0/1.4.2 does not affect the build, do a git bisect with 1.4.2
> and 1.6.0.
>
> Alternatively, provide the log output as configured here:
>
> https://maven.apache.org/resolver-archives/resolver-LATEST/maven-resolver-synccontext-global/index.html#Debugging
>
> In 1.6.0 there is even less synchronization because the
> TrackingFileManager does not lock anything anymore.
>
> I will hold off vote completion until I get some analyzable data from you.
>
> Michael
>
>
> Am 2020-09-15 um 11:49 schrieb Dan Tran:
> > I build maven 3.7.0 + MResolve 1.6.0.  The same slow build observed at my
> > 300+ modules  ( 60min versus 5min)
> >
> > -1 ( non-binding) from me.  there must and option to disable this new
> > feature
> >
> > -D
> >
> > On Mon, Sep 14, 2020 at 4:33 AM Michael Osipov 
> wrote:
> >
> >> Am 2020-09-14 um 10:57 schrieb Dan Tran:
> >>> sorry about the fast finger,  my test shows a huge increase in build
> time
> >>> for large builds.  Possible to disable this feature?
> >>
> >> This cannot be. It has been superceded by
> >> https://issues.apache.org/jira/browse/MRESOLVER-130. The
> >> GlobalSyncContextFactory have been moved to a separate module, the
> >> original behavior has been restored. I.e., this feature is not enabled
> >> by default.
> >>
> >> Are you certain that you don't have leftovers in ${maven.home}/lib/ext?
> >>
> >>> On Mon, Sep 14, 2020 at 1:49 AM Dan Tran  wrote:
> >>>
> >>>> possible to disable this feature
> >>>> https://issues.apache.org/jira/browse/MRESOLVER-123 ?
> >>>>
> >>>> On Mon, Sep 14, 2020 at 12:06 AM Romain Manni-Bucau <
> >> rmannibu...@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> +1, tested in java 8 with mvn 3.6.3.
> >>>>>
> >>>>> 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 lun. 14 sept. 2020 à 08:58, Enrico Olivelli 
> a
> >>>>> écrit :
> >>>>>
> >>>>>> +1
> >>>>>> checked checksum and run tests on JDK14 + Mac
> >>>>>>
> >>>>>>mvn -v
> >>>>>>
> >>>>>> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> >>>>>>
> >>>>>> Maven home: xx
> >>>>>>
> >>>>>> Java version: 14, vendor: AdoptOpenJDK, runtime:
> >>>>>> /Library/Java/JavaVirtualMachines/adoptopenjdk-14.jdk/Contents/Home
> >>>>>>
> >>>>>> Default locale: it_IT, platform encoding: UTF-8
> >>>>>>
> >>>>>> OS name: "mac os x", version: "10.15.4", arch: "x86_64", family:
> "mac"
> >>>>>>
> >>>>>> Il giorno lun 14 set 2020 alle ore 08:55 Hervé BOUTEMY <
> >>>>>> herve.bout...@free.fr> ha scritto:
> >>>>>>
> >>>>>>> +1
> >>>>>>>
> >>>>>>> sadly, the build is not reproducible: reference build done with
> JDK 8
> >>>>> on
> >>>>>>> Windows, but Felix Mav

Re: [VOTE] Release Maven Resolver version 1.6.0

2020-09-15 Thread Dan Tran
I build maven 3.7.0 + MResolve 1.6.0.  The same slow build observed at my
300+ modules  ( 60min versus 5min)

-1 ( non-binding) from me.  there must and option to disable this new
feature

-D

On Mon, Sep 14, 2020 at 4:33 AM Michael Osipov  wrote:

> Am 2020-09-14 um 10:57 schrieb Dan Tran:
> > sorry about the fast finger,  my test shows a huge increase in build time
> > for large builds.  Possible to disable this feature?
>
> This cannot be. It has been superceded by
> https://issues.apache.org/jira/browse/MRESOLVER-130. The
> GlobalSyncContextFactory have been moved to a separate module, the
> original behavior has been restored. I.e., this feature is not enabled
> by default.
>
> Are you certain that you don't have leftovers in ${maven.home}/lib/ext?
>
> > On Mon, Sep 14, 2020 at 1:49 AM Dan Tran  wrote:
> >
> >> possible to disable this feature
> >> https://issues.apache.org/jira/browse/MRESOLVER-123 ?
> >>
> >> On Mon, Sep 14, 2020 at 12:06 AM Romain Manni-Bucau <
> rmannibu...@gmail.com>
> >> wrote:
> >>
> >>> +1, tested in java 8 with mvn 3.6.3.
> >>>
> >>> 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 lun. 14 sept. 2020 à 08:58, Enrico Olivelli  a
> >>> écrit :
> >>>
> >>>> +1
> >>>> checked checksum and run tests on JDK14 + Mac
> >>>>
> >>>>   mvn -v
> >>>>
> >>>> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> >>>>
> >>>> Maven home: xx
> >>>>
> >>>> Java version: 14, vendor: AdoptOpenJDK, runtime:
> >>>> /Library/Java/JavaVirtualMachines/adoptopenjdk-14.jdk/Contents/Home
> >>>>
> >>>> Default locale: it_IT, platform encoding: UTF-8
> >>>>
> >>>> OS name: "mac os x", version: "10.15.4", arch: "x86_64", family: "mac"
> >>>>
> >>>> Il giorno lun 14 set 2020 alle ore 08:55 Hervé BOUTEMY <
> >>>> herve.bout...@free.fr> ha scritto:
> >>>>
> >>>>> +1
> >>>>>
> >>>>> sadly, the build is not reproducible: reference build done with JDK 8
> >>> on
> >>>>> Windows, but Felix Maven Bundle Plugin is causing issues in generated
> >>>> META-
> >>>>> INF/MANIFEST.MF (contains username, detailed JDK version, and order
> or
> >>>>> Private
> >>>>> Package not reproducible): I'll have a look to check if recent
> >>> updates to
> >>>>> this
> >>>>> plugin can fix the issue...
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>> Hervé
> >>>>>
> >>>>> Le vendredi 11 septembre 2020, 20:19:56 CEST Michael Osipov a écrit :
> >>>>>> Hi,
> >>>>>>
> >>>>>> We solved 19 issues:
> >>>>>>
> >>>>>
> >>>>
> >>>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628
> >>>>>> rsion=12348666
> >>>>>>
> >>>>>> There are still a couple of issues left in JIRA:
> >>>>>>
> >>>>>
> >>>>
> >>>
> https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissue
> >>>>>> s
> >>>>>>
> >>>>>> Staging repo:
> >>>>>> https://repository.apache.org/content/repositories/maven-1605/
> >>>>>>
> >>>>>
> >>>>
> >>>
> https://repository.apache.org/content/repositories/maven-1605/org/apache/mav
> >>>>>>
> >>>>
> en/resolver/maven-resolver/1.6.0/maven-resolver-1.6.0-source-release.zip
> >>>>>>
> >>>>>> Source release checksum(s):
> >>>>>> maven-resolver-1.6.0-source-release.zip
> >>>>>>
> >>>>>
> >>>>
> >>>
> fd419a3f0bbe3c0ea0b3d7b881c4892fcfc73ec6cf812e7ddb724febb8bc010c754d5845498c
> >>>>>> 6c916a3bbdae2d90dd66787eb44fdbdd27310c745bdc1e8cc15b
> >>>>>>
> >>>>>> Staging site:
> >>>>>> https://maven.apache.org/resolver-archives/resolver-LATEST/
> >>>>>>
> >>>>>> Guide to testing staged releases:
> >>>>>>
> >>>>
> https://maven.apache.org/guides/development/guide-testing-releases.html
> >>>>>>
> >>>>>> Note: This Resolver version offers salvation from a 13.5 years old
> >>>>>> feature request: MNG-2802
> >>>>>> Yes, you can have now concurrent-safe access to your local Maven
> >>>>>> repository synchronized with Redis.
> >>>>>>
> >>>>>> 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
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Release Maven Resolver version 1.6.0

2020-09-14 Thread Dan Tran
sorry about the fast finger,  my test shows a huge increase in build time
for large builds.  Possible to disable this feature?

Thanks

-D

On Mon, Sep 14, 2020 at 1:49 AM Dan Tran  wrote:

> possible to disable this feature
> https://issues.apache.org/jira/browse/MRESOLVER-123 ?
>
> On Mon, Sep 14, 2020 at 12:06 AM Romain Manni-Bucau 
> wrote:
>
>> +1, tested in java 8 with mvn 3.6.3.
>>
>> 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 lun. 14 sept. 2020 à 08:58, Enrico Olivelli  a
>> écrit :
>>
>> > +1
>> > checked checksum and run tests on JDK14 + Mac
>> >
>> >  mvn -v
>> >
>> > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
>> >
>> > Maven home: xx
>> >
>> > Java version: 14, vendor: AdoptOpenJDK, runtime:
>> > /Library/Java/JavaVirtualMachines/adoptopenjdk-14.jdk/Contents/Home
>> >
>> > Default locale: it_IT, platform encoding: UTF-8
>> >
>> > OS name: "mac os x", version: "10.15.4", arch: "x86_64", family: "mac"
>> >
>> > Il giorno lun 14 set 2020 alle ore 08:55 Hervé BOUTEMY <
>> > herve.bout...@free.fr> ha scritto:
>> >
>> > > +1
>> > >
>> > > sadly, the build is not reproducible: reference build done with JDK 8
>> on
>> > > Windows, but Felix Maven Bundle Plugin is causing issues in generated
>> > META-
>> > > INF/MANIFEST.MF (contains username, detailed JDK version, and order or
>> > > Private
>> > > Package not reproducible): I'll have a look to check if recent
>> updates to
>> > > this
>> > > plugin can fix the issue...
>> > >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > > Le vendredi 11 septembre 2020, 20:19:56 CEST Michael Osipov a écrit :
>> > > > Hi,
>> > > >
>> > > > We solved 19 issues:
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628
>> > > > rsion=12348666
>> > > >
>> > > > There are still a couple of issues left in JIRA:
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissue
>> > > > s
>> > > >
>> > > > Staging repo:
>> > > > https://repository.apache.org/content/repositories/maven-1605/
>> > > >
>> > >
>> >
>> https://repository.apache.org/content/repositories/maven-1605/org/apache/mav
>> > > >
>> > en/resolver/maven-resolver/1.6.0/maven-resolver-1.6.0-source-release.zip
>> > > >
>> > > > Source release checksum(s):
>> > > > maven-resolver-1.6.0-source-release.zip
>> > > >
>> > >
>> >
>> fd419a3f0bbe3c0ea0b3d7b881c4892fcfc73ec6cf812e7ddb724febb8bc010c754d5845498c
>> > > > 6c916a3bbdae2d90dd66787eb44fdbdd27310c745bdc1e8cc15b
>> > > >
>> > > > Staging site:
>> > > > https://maven.apache.org/resolver-archives/resolver-LATEST/
>> > > >
>> > > > Guide to testing staged releases:
>> > > >
>> > https://maven.apache.org/guides/development/guide-testing-releases.html
>> > > >
>> > > > Note: This Resolver version offers salvation from a 13.5 years old
>> > > > feature request: MNG-2802
>> > > > Yes, you can have now concurrent-safe access to your local Maven
>> > > > repository synchronized with Redis.
>> > > >
>> > > > Vote open for 72 hours.
>> > > >
>> > > > [ ] +1
>> > > > [ ] +0
>> > > > [ ] -1
>> > > >
>> > > >
>> -
>> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > > > For additional commands, e-mail: dev-h...@maven.apache.org
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > -
>> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > > For additional commands, e-mail: dev-h...@maven.apache.org
>> > >
>> > >
>> >
>>
>


Re: [VOTE] Release Maven Resolver version 1.6.0

2020-09-14 Thread Dan Tran
possible to disable this feature
https://issues.apache.org/jira/browse/MRESOLVER-123 ?

On Mon, Sep 14, 2020 at 12:06 AM Romain Manni-Bucau 
wrote:

> +1, tested in java 8 with mvn 3.6.3.
>
> 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 lun. 14 sept. 2020 à 08:58, Enrico Olivelli  a
> écrit :
>
> > +1
> > checked checksum and run tests on JDK14 + Mac
> >
> >  mvn -v
> >
> > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> >
> > Maven home: xx
> >
> > Java version: 14, vendor: AdoptOpenJDK, runtime:
> > /Library/Java/JavaVirtualMachines/adoptopenjdk-14.jdk/Contents/Home
> >
> > Default locale: it_IT, platform encoding: UTF-8
> >
> > OS name: "mac os x", version: "10.15.4", arch: "x86_64", family: "mac"
> >
> > Il giorno lun 14 set 2020 alle ore 08:55 Hervé BOUTEMY <
> > herve.bout...@free.fr> ha scritto:
> >
> > > +1
> > >
> > > sadly, the build is not reproducible: reference build done with JDK 8
> on
> > > Windows, but Felix Maven Bundle Plugin is causing issues in generated
> > META-
> > > INF/MANIFEST.MF (contains username, detailed JDK version, and order or
> > > Private
> > > Package not reproducible): I'll have a look to check if recent updates
> to
> > > this
> > > plugin can fix the issue...
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le vendredi 11 septembre 2020, 20:19:56 CEST Michael Osipov a écrit :
> > > > Hi,
> > > >
> > > > We solved 19 issues:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628
> > > > rsion=12348666
> > > >
> > > > There are still a couple of issues left in JIRA:
> > > >
> > >
> >
> https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissue
> > > > s
> > > >
> > > > Staging repo:
> > > > https://repository.apache.org/content/repositories/maven-1605/
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/maven-1605/org/apache/mav
> > > >
> > en/resolver/maven-resolver/1.6.0/maven-resolver-1.6.0-source-release.zip
> > > >
> > > > Source release checksum(s):
> > > > maven-resolver-1.6.0-source-release.zip
> > > >
> > >
> >
> fd419a3f0bbe3c0ea0b3d7b881c4892fcfc73ec6cf812e7ddb724febb8bc010c754d5845498c
> > > > 6c916a3bbdae2d90dd66787eb44fdbdd27310c745bdc1e8cc15b
> > > >
> > > > Staging site:
> > > > https://maven.apache.org/resolver-archives/resolver-LATEST/
> > > >
> > > > Guide to testing staged releases:
> > > >
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> > > >
> > > > Note: This Resolver version offers salvation from a 13.5 years old
> > > > feature request: MNG-2802
> > > > Yes, you can have now concurrent-safe access to your local Maven
> > > > repository synchronized with Redis.
> > > >
> > > > 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: [RESULT] [VOTE] Release Maven Resolver version 1.5.0

2020-08-01 Thread Dan Tran
I am interesting pickup latest maven-resolver hoping it can solve some
random issue at our builds

Since 1.5.0 no longer available, I rebuilt maven 3.6.3 with maven-resolver
1.5.1-SNAPSHOT.   and hook it up our internal build

The startup of my build is quite slow... however, I am looking forward to
testing again with next maven-resolver vote

Thanks

-D

On Wed, Jul 22, 2020 at 1:03 AM Mark Derricutt  wrote:

> Hervé, Michael - missed the email about the vote earlier, just went hunting
> for the repo details to try it out on our internal range resolver/locking
> tool.
>
> +1 NON Binding here - passes my unit tests on my library, and the maven
> mojo that uses it runs fine as works as expected.
>
> Mark
>
>
> On 22 July 2020 at 6:05:39 PM, Hervé BOUTEMY (herve.bout...@free.fr)
> wrote:
>
> hey, keep cool, take time: 72h is the minimum, not the period after which
> the vote stops there was some discussions, people are on vacation, it takes
> more time than usual, nothing that a little bit of time won't solve
> Regards, Hervé Le mardi 21 juillet 2020, 20:32:49 CEST Michael Osipov a
> écrit : > Hi, > > The vote has passed and failed to reach a quorum. Only
> one, non-binding > vote has been cast. Therefore, I cancel the release and
> will drop the > staging repo tomorrow. > > Michael
>


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

2020-06-14 Thread Dan Tran
+1 tested with our 300+ maven modules build

Found the following new 'good' behaviors/fixes

   1. Junit 4 test class now have 'public' scope at both class and method
level.
   2. Exception at test 'setup' ( ie @Before) now show up as failures, They
are ignored at M4

Great works

Thanks



On Sat, Jun 13, 2020 at 3:40 PM Tibor Digana  wrote:

> Hi Herve,
>
> We can fork the discussion about this problem apart in the Slack.
> Thx for finding this.
>
> T
>
>
> On Sat, Jun 13, 2020 at 9:35 PM Hervé BOUTEMY 
> wrote:
>
> > +1
> >
> > near full reproducibility of reference artifacts with JDK 8 on Windows:
> 48
> > artifacts are ok, just 2 still have issues:
> > - surefire-3.0.0-M5-source-release.zip: I don't know why my local build
> > added 3 dependency-reduced-pom.xml that do not exist in reference build
> > - surefire-shadefire-3.0.0-M5.jar: some strange timestamp issues for some
> > shaded content, probably a subtle maven-shade-plugin bug
> >
> > Regards,
> >
> > Hervé
> >
> > Le samedi 13 juin 2020, 15:46:10 CEST Tibor Digana a écrit :
> > > Hi,
> > >
> > > We solved 40 issues:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927
> > > rsion=12344612
> > >
> > > There are still a couple of issues left in JIRA:
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20
> > > status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-1590/
> > >
> >
> https://repository.apache.org/content/repositories/maven-1590/org/apache/mav
> > > en/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip
> > >
> > > Source release checksum(s):
> > > surefire-3.0.0-M5-source-release.zip  sha1:
> > > 687a89ceb4a1b2e5dd472deec8d3843f2a98b68f
> > > surefire-3.0.0-M5-source-release.zip  sha512:
> > >
> >
> e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f0
> > > 91081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7
> > >
> > > 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: Same snapshot deploy number for entire build - possible

2019-09-13 Thread Dan Tran
Looks like I need to clear thing a little bit

Assume I have a reactor of few hundreds of maven modules and my CI
build deploys snapshots, first few good builds, each module deployed to
maven repository have same snapshot number

Once we encounter a build failure at a module,  the snapshot number begins
to vary and over time, all modules no longer have the same snapshot number
anymore

To be able to determine a consistent snapshot number at each build,  I
would like to have an ability the tell deploy maven plugin to use an
assigned number for all modules.

Possible?

Thanks

-D






On Thu, Sep 12, 2019 at 11:31 PM Enrico Olivelli 
wrote:

> Dan,
> Are you running a single 'mvn deploy' or do you have multiple runs?
> I have never seen weird behaviours in multi module projects
>
> Cheers
> Enrico
>
> Il ven 13 set 2019, 08:19 Dan Tran  ha scritto:
>
> > Hello, Maven dev
> >
> > any suggestion/thoughts on this issue are very much appreciated
> >
> > Regards
> >
> > -D
> >
> > On Wed, Sep 11, 2019 at 7:06 PM Dan Tran  wrote:
> >
> > > Hello Maven Users and Development Team
> > >
> > > Currently, artifact deployed as snapshot at Maven repository has the
> > > following format
> > >
> > >  artifactId-version-timestamp-NN
> > >
> > > where NN auto-incremented at each maven module and the number varies
> > >
> > > Is there a way to use same snapshot NN for the entire multi-module
> maven
> > > build?
> > >
> > > If I have to implement a solution, would it be as an extension or I
> have
> > > to tinker with maven-deploy-plugin?
> > >
> > > Very appreciated any advice
> > >
> > > -D
> > >
> > >
> > >
> > >
> > >
> >
>


Re: Same snapshot deploy number for entire build - possible

2019-09-13 Thread Dan Tran
Hello, Maven dev

any suggestion/thoughts on this issue are very much appreciated

Regards

-D

On Wed, Sep 11, 2019 at 7:06 PM Dan Tran  wrote:

> Hello Maven Users and Development Team
>
> Currently, artifact deployed as snapshot at Maven repository has the
> following format
>
>  artifactId-version-timestamp-NN
>
> where NN auto-incremented at each maven module and the number varies
>
> Is there a way to use same snapshot NN for the entire multi-module maven
> build?
>
> If I have to implement a solution, would it be as an extension or I have
> to tinker with maven-deploy-plugin?
>
> Very appreciated any advice
>
> -D
>
>
>
>
>


Re: [RESULT] [VOTE] Release Apache Maven Version 3.6.2

2019-09-02 Thread Dan Tran
+1 non-bind, tested with company production builds.

Should we give Intellij user a warning?

On Mon, Sep 2, 2019 at 2:05 PM Enrico Olivelli  wrote:

> Hi,
>
> the vote passed with the following resuts:
> +1 jes...@udby.com, Tibor Digana, Mickael Istria, Romain Manni-Bucau,
> Francois Papon, Hervé Boutemy, Karl Heinz Marbaise, Olivier Lamy, Mirko
> Friedenhagen, Tamas Cserveak, Gabriel Berlingueres, Grzegorz Grzybek,
> Sylwester Lachiewicz, Robert Scholte, Michael Osipov, Arnaud Héritier
>
> PMC Quorum: reached
>
> I will promote the artifacts to the central repo and complete the procedure
>
> Thank you to everyone !
>
> Enrico
>
> Il giorno lun 2 set 2019 alle ore 09:37 Arnaud Héritier <
> aherit...@gmail.com>
> ha scritto:
>
> > +1 (I had only the time to test on few projects - no regression found)
> >
> >
> > On Sun, Sep 1, 2019 at 2:16 PM Romain Manni-Bucau  >
> > wrote:
> >
> > > +1 (non binding)
> > >
> > > Le dim. 1 sept. 2019 à 12:50, Michael Osipov  a
> > > écrit :
> > >
> > > > Am 2019-08-28 um 21:17 schrieb Enrico Olivelli:
> > > > > Hi,
> > > > >
> > > > > We have solved 52 issues:
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12345234
> > > > >
> > > > > 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-1529
> > > > >
> > > > > The distributable binaries and sources can be found here:
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/
> > > > >
> > > > > Specifically the zip, tarball and source archives can be found
> here:
> > > > >
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-bin.zip
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-bin.tar.gz
> > > > >
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-src.zip
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-src.tar.gz
> > > > >
> > > > > The release artifacts are staged for distribution in:
> > > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.2
> > > > >
> > > > > Source release checksum(s):
> > > > > apache-maven-3.6.2-src.tar.gz
> > > > >
> > > > > sha1: 373ffbe9fc88e5facbe10d7a6f6badd243545ade
> > > > > sha512:
> > > > >
> > > >
> > >
> >
> 235198b48d29fe2f2394f2607a9a1637acfd0286beacb974c566f7f36ac6c469871a0db287539b2b62e6322d7423f586949e41cbbfea330fe03bf690688f6fd7
> > > > >
> > > > > apache-maven-3.6.2-src.zip:
> > > > >
> > > > > sha1: c6c5bd9828b3350905e97177978724eed0698de3
> > > > > sha512:
> > > > >
> > > >
> > >
> >
> d7fdafbc16bd547bc3c2513255df375c2a616b04d414c2ffd7d9deb9931fab5db4c7ac912cc4bb0d96d0a083560b3cc1848ea9eecc3aeb4e4c5184329a7ead5b
> > > > >
> > > > > Git tag:
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=40f52333136460af0dc0d7232c0dc0bcf0d9e117
> > > > >
> > > > > Staging site:
> > > > > https://maven.apache.org/components/ref/3-LATEST/
> > > > >
> > > > > Vote open for 72 hours.
> > > >
> > > > +1
> > > >
> > > > Just noticed that almost 50% have been assigned to me ;-)
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >
> > > >
> > >
> >
> >
> > --
> > -
> > Arnaud Héritier
> > http://aheritier.net
> > Mail/GTalk: aheritier AT gmail DOT com
> > Twitter/Skype : aheritier
> >
>


Re: [maven-surefire] branch master updated (f7d4310 -> 8109b4f)

2019-08-25 Thread Dan Tran
Thanks, I am able to pick up the latest surefire 3.0.0-SNAPSHOT and run it
with our builds.  Looking good

Looking forward to a new surefire release

Thanks

-D



On Sun, Aug 25, 2019 at 2:37 AM Tibor Digana  wrote:

> The build is currently running and the 'deploy' is performed at the end.
> https://builds.apache.org/job/maven-box/job/maven-surefire/job/master/53/
> We have to wait few hours because the Jenkins queue is full.
>
> On Sun, Aug 25, 2019 at 9:03 AM Dan Tran  wrote:
>
>> @Tibor Digana   I would be very helpful to
>> deploy last surefire snapshot, so users ( like me) can easily help testing
>> it with our internal builds
>>
>> Thanks
>>
>> -D
>>
>>
>> On Fri, Aug 23, 2019 at 12:32 PM  wrote:
>>
>>> This is an automated email from the ASF dual-hosted git repository.
>>>
>>> tibordigana pushed a change to branch master
>>> in repository https://gitbox.apache.org/repos/asf/maven-surefire.git.
>>>
>>>
>>> from f7d4310  [SUREFIRE-1679] Prevent classpath caching from causing
>>> pollution
>>>  add 8109b4f  [SUREFIRE-1464] Failsafe plugin exposes slf4j-jdk14
>>> dependency
>>>
>>> No new revisions were added by this update.
>>>
>>> Summary of changes:
>>>  pom.xml | 4 
>>>  1 file changed, 4 insertions(+)
>>>
>>>


Re: [maven-surefire] branch master updated (f7d4310 -> 8109b4f)

2019-08-25 Thread Dan Tran
@Tibor Digana   I would be very helpful to
deploy last surefire snapshot, so users ( like me) can easily help testing
it with our internal builds

Thanks

-D


On Fri, Aug 23, 2019 at 12:32 PM  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> tibordigana pushed a change to branch master
> in repository https://gitbox.apache.org/repos/asf/maven-surefire.git.
>
>
> from f7d4310  [SUREFIRE-1679] Prevent classpath caching from causing
> pollution
>  add 8109b4f  [SUREFIRE-1464] Failsafe plugin exposes slf4j-jdk14
> dependency
>
> No new revisions were added by this update.
>
> Summary of changes:
>  pom.xml | 4 
>  1 file changed, 4 insertions(+)
>
>


Re: [VOTE] Release Maven Wagon version 3.3.3

2019-06-15 Thread Dan Tran
+1 none binding, tested with Maven 3.6.2-SNAPSHOT + wagon-3.3.3 ( at
staging) against an internal build

Thanks for pushing out this release

-D

On Sat, Jun 15, 2019 at 3:34 PM Michael Osipov  wrote:

> Am 2019-06-13 um 15:46 schrieb Michael Osipov:
> > Hi,
> >
> > We solved 6 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12345501
> >
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved
> >
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1514/
> >
> https://repository.apache.org/content/repositories/maven-1514/org/apache/maven/wagon/wagon/3.3.3/wagon-3.3.3-source-release.zip
> >
> >
> > Source release checksum(s):
> > wagon-3.3.3-source-release.zip
> > sha512:
> >
> 3fae2bea760a03896df395cee1896aa4a02e031fdc86daaba781243cad9aefa1c1c99fc7daa95e04da0248e5aa7649511d08503807dad5fc92d80e25202c999e
>
> >
> >
> > Staging site:
> > https://maven.apache.org/wagon-archives/wagon-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
>
> I need one more vote until tomorrow...
>
> -
> 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

2019-04-07 Thread Dan Tran
+1 ( non-binding)

Tested with a large multi-modules build using CI/CD mode + m2e under takari
team

Thanks

-D

On Sat, Apr 6, 2019 at 9:29 AM Mickael Istria  wrote:

> Hi,
>
> Unfortunately, we won't have the opportunity to try it in m2e before the
> deadline for voting as it seems like some recent changes would require
> adaptation in m2e (or it's some other bug in m2e that needs to be fixed
> before we can try this 3.6.1 RC).
> https://git.eclipse.org/r/#/c/133590/ shows the tentative change and links
> to the current build/test failures if someone is interested in giving a
> hand ;)
>
> Cheers,
>


Re: Maven 3.6.1 release date

2019-04-01 Thread Dan Tran
MNG-6605 indeed is a good one to have

On Mon, Apr 1, 2019 at 12:08 AM Karl Heinz Marbaise 
wrote:

> Hi Michael,
>
> On 01.04.19 08:54, Michael Osipov wrote:
> > Am 2019-03-31 um 21:36 schrieb Karl Heinz Marbaise:
> >> Hi,
> >>
> >> I would like to collect the issues which should be part of  Maven 3.6.1:
> >
> > MNG-6605 will go into. Non-intrusive, not active by default.
>
> I've seen that...that's good idea...
>
>
> >
> >> On 31.03.19 21:27, Karl Heinz Marbaise wrote:
> >>> Hi Michael,
> >>>
> >>> would it be helpful if I start the release tomorrow ?
> >>>
> >>> Cause I can see the list of issues assigned to Maven 3.6.1 is solved
> the
> >>> status looks Ok to me.
> >>>
> >>> Kind Regards
> >>> Karl Heinz Marbaise
> >>>
> >>> On 31.03.19 21:10, Mickael Istria wrote:
>  Hi,
>  What's the status of the release? Is its backlog «closed» now? When
>  is it
>  supposed to be shipped?
>  I'd like to make sure Eclipse m2e can upgrade before next released
>  as the
>  was already dalyed once.
>  Cheers,
> 
>  On Saturday, March 23, 2019, Hervé BOUTEMY 
>  wrote:
> 
> > there is only one task to do: transform the great minimal testcase
> > provided in
> > https://issues.apache.org/jira/browse/MNG-6506 to an IT, to not just
> > upgrade
> > blindly a dependency but keep track of what it solves
> >
> > Regards,
> >
> > Hervé
> >
> > Le vendredi 22 mars 2019, 11:45:19 CET Roman Grigoriadi a écrit :
> >> What is the issue with including MNG-6543 and MNG-6506?
> >> plexus-classworlds 2.6.0 seems to have a fix for both of them, are
> >> there
> >> any integration failures?
> >>
> >> Roman
> >>
> >> On Fri, Mar 22, 2019 at 9:32 AM Karl Heinz Marbaise
> >> 
> >>
> >> wrote:
> >>> Hi,
> >>>
> >>> On 22.03.19 09:25, Michael Osipov wrote:
>  Am 2019-03-22 um 08:37 schrieb Mickael Istria:
> > Hi,
> >
> > On Sat, Mar 9, 2019 at 6:34 PM Hervé BOUTEMY
> >  >>
> >
> > wrote:
> >> We're working on it, it should happen quite soon, but no date is
> >> really
> >> guaranteed: as you can see from Jira issues to be resolved [1],
> > we're
> >> near...
> >
> > At this point, since there are some blockers issues that have
> been
> > fixed
> > and community is in need of the new release, shouldn't we avoid
> > adding
> > enhancements in 3.6.1 backlog, focus on important remaining
> > bugs and
> > try to
> > ship it ASAP?
> > It seems to me that the scope of 3.6.1 is always growing, at the
> > risk
> > of
> > never releasing a lot of value that was already produced...
> 
>  I agree, I'd move out MNG-6506 and MNG-6543 and continue with the
>  relase.
> 
>  @Karl, can you make MNG-6538 happen?
> >>>
> >>> I will in the evening...already assigned the ticket...
> >>>
> >>
> >> -
> >> 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: 3.6.1 release?

2019-02-13 Thread Dan Tran
love to see 3.6.1 out soon :)

-D

On Mon, Feb 4, 2019 at 9:50 AM Karl Heinz Marbaise 
wrote:

> Hi Michael,
>
> On 04.02.19 17:36, Michael Osipov wrote:
> > I need to push Wagon first. It contains a regression for connection TTL.
>
> Yes of course.I know..
>
> Kind regards
> Karl Heinz Marbaise
> >
> >> Gesendet: Montag, 04. Februar 2019 um 17:25 Uhr
> >> Von: "Karl Heinz Marbaise" 
> >> An: "Maven Developers List" , "Mickael Istria" <
> mist...@redhat.com>
> >> Betreff: Re: 3.6.1 release?
> >>
> >> Hi,
> >>
> >> I will try to do the release planning today in the evening...
> >>
> >> Kind regards
> >> Karl Heinz Marbaise
> >> On 04.02.19 15:17, Mickael Istria wrote:
> >>> Hi all,
> >>>
> >>> Maven 3.6.1 has some noticeable fixes and improvements that we're
> eager to
> >>> leverage in Eclipse m2e. We're also ready for adoption:
> >>> https://git.eclipse.org/r/#/c/133590/ .
> >>> Do you have an estimate of when 3.6.1 should be release? What are the
> >>> issues currently considered as blocker for the release?
> >>>
> >>> Thanks in advance.
> >>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Release Maven Wagon version 3.3.2

2019-02-07 Thread Dan Tran
+1 tested with maven-3.6.1-SNAPSHOT building large maven project

-D

On Wed, Feb 6, 2019 at 4:13 PM Tibor Digana  wrote:

> +1
>
> On Tue, Feb 5, 2019 at 12:15 AM Michael Osipov 
> wrote:
>
> > Hi,
> >
> > We solved 12 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344885
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1485/
> >
> >
> https://repository.apache.org/content/repositories/maven-1485/org/apache/maven/wagon/wagon/3.3.2/wagon-3.3.2-source-release.zip
> >
> > Source release checksum(s):
> > wagon-3.3.2-source-release.zip
> > sha512:
> >
> >
> 48505538ee4eec686dea90a45cb683624a16baf899c3f0372a09520dc7a2bac7c3b92d8caf569a4ad4a7efff1b617824125dc2d3a632ee4fafd5b963d0f9a5cb
> >
> > Staging site:
> > https://maven.apache.org/wagon-archives/wagon-LATEST/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>


Re: [maven] branch master updated: [MNG-6571] forgot to put new instance in cache

2019-02-05 Thread Dan Tran
I am seeing test failure at the latest maven-core.  is it a known issue?

[INFO] Running org.apache.maven.artifact.versioning.VersionRangeTest[ERROR]
Tests run: 8, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.006
s <<< FAILURE! - in
org.apache.maven.artifact.versioning.VersionRangeTest[ERROR]
testIntersections(org.apache.maven.artifact.versioning.VersionRangeTest)
 Time elapsed: 0.004 s  <<<
FAILURE!junit.framework.AssertionFailedError: check number of
restrictions expected:<1> but was:<0>
at 
org.apache.maven.artifact.versioning.VersionRangeTest.testIntersections(VersionRangeTest.java:185)
[ERROR] testRange(org.apache.maven.artifact.versioning.VersionRangeTest)
 Time elapsed: 0 s  <<< FAILURE!junit.framework.AssertionFailedError:
check number of restrictions expected:<1> but was:<0>
at 
org.apache.maven.artifact.versioning.VersionRangeTest.testRange(VersionRangeTest.java:72)



On Mon, Feb 4, 2019 at 11:34 PM  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> hboutemy pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/maven.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
>  new 6bd8bb9  [MNG-6571] forgot to put new instance in cache
> 6bd8bb9 is described below
>
> commit 6bd8bb9ba6515446e3699202104f01f98fea1e63
> Author: Hervé Boutemy 
> AuthorDate: Tue Feb 5 08:34:55 2019 +0100
>
> [MNG-6571] forgot to put new instance in cache
> ---
>  .../src/main/java/org/apache/maven/artifact/versioning/VersionRange.java
> | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git
> a/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/VersionRange.java
> b/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/VersionRange.java
> index 5d7b254..8045bec 100644
> ---
> a/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/VersionRange.java
> +++
> b/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/VersionRange.java
> @@ -241,6 +241,7 @@ public class VersionRange
>  {
>  List restrictions = Collections.emptyList();
>  cached = new VersionRange( new DefaultArtifactVersion(
> version ), restrictions );
> +CACHE.put( version, cached );
>  }
>  return cached;
>  }
>
>


Re: Are snapshots available in some Maven repo?

2019-01-10 Thread Dan Tran
how about just deploy nightly snapshot of active 'main' branch ( ie master)?

-D


On Thu, Jan 10, 2019 at 9:03 AM Robert Scholte  wrote:

> Now that we use branches actively, it is way more important where a
> SNAPSHOT is coming from.
> I've seen it too often that people thought they were testing with a
> version from a specific branch, but that it was redeployed with another
> version.
> The first steps are done to rewrite the pom-file during publication, and
> that might be exactly what we need here: when we're on a branch, the
> branchname should be added to the version.
> Call it work in progress for better support.
>
> thanks,
> Robert
>
> On Thu, 10 Jan 2019 10:50:57 +0100, Stephen Connolly
>  wrote:
>
> > On Thu, 10 Jan 2019 at 09:11, Mickael Istria  wrote:
> >
> >> Hi,
> >>
> >> Eclipse m2e, as a consumer of Maven as a library, would love to see the
> >> latest HEAD from master published automatically as SNAPSHOTs soon after
> >> every change is made. This seems like a requirement to enable continuous
> >> feedback from m2e to Maven.
> >> Publishing some other branches or commits doesn't seem interesting to
> >> Eclipse m2e at the moment.
> >>
> >
> > My point is that we need a clearly defined policy as to exactly what
> > branch(es) are automatically pushed and when.
> >
> > That policy could be *one* of:
> > * "master" if there are SCM changes detected on Sunday at 00:00 UTC
> > * "master" if there are SCM changes detected at 00:00 UTC
> > * "master" as soon as SCM changes are detected
> > * "integration" as soon as SCM changes are detected
> > * etc
> >
> > We just need to be crystal clear exactly what policy we are following.
> > Right now the policy we are following is:
> >
> > * Manually from whatever branch is appropriate and only when there is a
> > request for them to be published.
> >
> > There are good and valid reasons for any of these policies (or indeed
> > other
> > alternative policies). The problems occur if you try to mix policy.
> >
> > For example, if I as a developer know that snapshots could be published
> > at
> > any time then I can choose between `always` and `never` as the update
> > policy depending on whether I want to focus on diagnosing issues on a
> > consistent base or discovering issues on shifting sand.
> >
> > If I know that snapshots will only ever be published once a week then I
> > can
> > leave the update policy at the default of daily because I'll need to
> > rebuild my mental context on the next week anyway and it's only the first
> > build on Monday's that will have the time kill.
> >
> > So the thing that we need to do is decide if we want to change our
> > policy,
> > if yes, then decide what we want to change it to *and* both implement it
> > consistently and publish it clearly.
> >
> > Finally we have the ASF legal requirements that mean we need to clarify
> > to
> > all that -SNAPSHOTs are not actually releases and are only made available
> > for validation prior to VOTE threads... because currently -SNAPSHOTs are
> > rare this is not a big issue... if we have the CI pushing -SNAPSHOTs at a
> > regular cadence the risk of *users* starting to use -SNAPSHOTs as
> > releases
> > rises so we would need to find ways to mitigate such risks
> >
> >
> >>
> >> Cheers,
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Release Maven Wagon version 3.3.1

2019-01-03 Thread Dan Tran
+1 tested with maven-3.6.1-SNAPSHOT plus wagon-3.3.1 against a large build.

-D

On Thu, Jan 3, 2019 at 5:28 AM Michael Osipov  wrote:

> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344772
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1483/
>
> https://repository.apache.org/content/repositories/maven-1483/org/apache/maven/wagon/wagon/3.3.1/wagon-3.3.1-source-release.zip
>
> Source release checksum(s):
> wagon-3.3.1-source-release.zip
> sha512:
>
> 398d8d028cbaff4fdc6380a105af8c2111915931db9c46f404e96c6de82b713995f3842ffd32b61e1a0b6c4249973af69a6256c160babf2d3acf7cff5417a649
>
> Staging site:
> https://maven.apache.org/wagon-archives/wagon-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: VOTE] Release Maven Wagon version 3.3.0

2018-12-28 Thread Dan Tran
Revert  WAGON-537 <https://jira.apache.org/jira/browse/WAGON-537> fixes the
issue.

-D

On Fri, Dec 28, 2018 at 2:25 PM Michael Osipov  wrote:

> Am 2018-12-28 um 20:32 schrieb Dan Tran:
> > The regression was introduced by
> > https://jira.apache.org/jira/browse/WAGON-537 which has changes at
> > AbstractWagon used by all providers.  Best to localize the change for
> > http provider only
> >
> > note: wagon-maven-plugin uses its own wagon-ssh, but still share the base
> > class with its maven runtime. that is why no issue found when running
> with
> > maven 3.6.0, but only with maven 3.6.1 building with the latest wagon (
> ie
> > 3.3.0 at staging)
>
> That's a pointer. Did you bisect? Did you revert the changes on
> AbstractWagon and see that it works again?
>
> > On Fri, Dec 28, 2018 at 6:10 AM Tibor Digana 
> wrote:
> >
> >> +1
> >>
> >> On Thu, Dec 27, 2018 at 11:21 PM Michael Osipov 
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> We solved 4 issues:
> >>>
> >>>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344436
> >>>
> >>> There are still a couple of issues left in JIRA:
> >>>
> >>>
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved
> >>>
> >>> Staging repo:
> >>> https://repository.apache.org/content/repositories/maven-1481/
> >>>
> >>>
> >>
> https://repository.apache.org/content/repositories/maven-1481/org/apache/maven/wagon/wagon/3.3.0/wagon-3.3.0-source-release.zip
> >>>
> >>> Source release checksum(s):
> >>> wagon-3.3.0-source-release.zip
> >>> sha512:
> >>>
> >>>
> >>
> c467bf8d9f5b54602f53ed34e117753f48cf25b611c79dbbba55706ce34a6bb0dec65447a84d6dc5122615147fe4ce19102a94a37d4a0b3a15382aa7fdba7560
> >>>
> >>> Staging site:
> >>> https://maven.apache.org/wagon-archives/wagon-LATEST/
> >>>
> >>> Guide to testing staged releases:
> >>> http://maven.apache.org/guides/development/guide-testing-releases.html
> >>>
> >>> Vote open for 72 hours.
> >>>
> >>> [ ] +1
> >>> [ ] +0
> >>> [ ] -1
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: dev-h...@maven.apache.org
> >>>
> >>>
> >>
> >
>
>


Re: VOTE] Release Maven Wagon version 3.3.0

2018-12-28 Thread Dan Tran
The regression was introduced by
https://jira.apache.org/jira/browse/WAGON-537 which has changes at
AbstractWagon used by all providers.  Best to localize the change for
http provider only

note: wagon-maven-plugin uses its own wagon-ssh, but still share the base
class with its maven runtime. that is why no issue found when running with
maven 3.6.0, but only with maven 3.6.1 building with the latest wagon ( ie
3.3.0 at staging)

-D


On Fri, Dec 28, 2018 at 6:10 AM Tibor Digana  wrote:

> +1
>
> On Thu, Dec 27, 2018 at 11:21 PM Michael Osipov 
> wrote:
>
> > Hi,
> >
> > We solved 4 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344436
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1481/
> >
> >
> https://repository.apache.org/content/repositories/maven-1481/org/apache/maven/wagon/wagon/3.3.0/wagon-3.3.0-source-release.zip
> >
> > Source release checksum(s):
> > wagon-3.3.0-source-release.zip
> > sha512:
> >
> >
> c467bf8d9f5b54602f53ed34e117753f48cf25b611c79dbbba55706ce34a6bb0dec65447a84d6dc5122615147fe4ce19102a94a37d4a0b3a15382aa7fdba7560
> >
> > Staging site:
> > https://maven.apache.org/wagon-archives/wagon-LATEST/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>


Re: VOTE] Release Maven Wagon version 3.3.0

2018-12-27 Thread Dan Tran
Unfortunately, I found a regression at wagon-ssh where ssh download hangs.
See https://jira.apache.org/jira/browse/WAGON-543

On Thu, Dec 27, 2018 at 2:21 PM Michael Osipov  wrote:

> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344436
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1481/
>
> https://repository.apache.org/content/repositories/maven-1481/org/apache/maven/wagon/wagon/3.3.0/wagon-3.3.0-source-release.zip
>
> Source release checksum(s):
> wagon-3.3.0-source-release.zip
> sha512:
>
> c467bf8d9f5b54602f53ed34e117753f48cf25b611c79dbbba55706ce34a6bb0dec65447a84d6dc5122615147fe4ce19102a94a37d4a0b3a15382aa7fdba7560
>
> Staging site:
> https://maven.apache.org/wagon-archives/wagon-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +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 3.6.0

2018-10-28 Thread Dan Tran
+1 (none binding) tested 300+ maven modules project with special interested
of https://issues.apache.org/jira/browse/MNG-6412

On Sun, Oct 28, 2018 at 1:55 PM Sylwester Lachiewicz 
wrote:

> +1 from me. Tested based on Spring Boot multithreaded build and Java 11.
>
> Yes, it would be good to have regression tests with popular IDE. We can try
> to enhance IntelliJ integration with Maven because now they use Maven 3.3.9
> with some work for 3.1.0.
>
> BR
> Sylwester
>
> W dniu niedz., 28.10.2018 o 12:34 Olivier Lamy 
> napisał(a):
>
> > +1 (agree on trying to do better work for backward compat)
> >
> > On Sun, 28 Oct 2018 at 21:08, Hervé BOUTEMY 
> wrote:
> >
> > > works well from CLI, as secured with our Core ITs
> > > Notice that there are some risks for IDE integrations:
> > > - Eclipse, as reported in MNG-6311 [1]
> > > - Intellij, as reported in IDEA-201282 [2] caused by MRESOLVER-36 [3]
> > > AFAIK, these are not really blockers, but we should probably find a way
> > to
> > > be
> > > more conservative on compatibility and find a way for IDE integrations
> to
> > > be
> > > better tested: any idea on how to better test that before releasing?
> > >
> > > all in all, here is my +1
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://issues.apache.org/jira/browse/MNG-6311
> > >
> > > [2] https://youtrack.jetbrains.com/issue/IDEA-201282
> > >
> > > [3] https://issues.apache.org/jira/browse/MRESOLVER-36
> > >
> > > Le mercredi 24 octobre 2018, 21:50:02 CET Karl Heinz Marbaise a écrit :
> > > > Hi,
> > > >
> > > > We have solved 26 issues:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922
> > > > rsion=12338966
> > > >
> > > > There are issues left in JIRA for Maven core:
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resol
> > > >
> > >
> >
> ution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%2
> > > > 0updated%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/mav
> > > > en/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/mav
> > > > en/apache-maven/3.6.0/apache-maven-3.6.0-bin.zip
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/maven-1459/org/apache/ma
> > > > ven/apache-maven/3.6.0/apache-maven-3.6.0-bin.tar.gz
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/maven-1459/org/apache/mav
> > > > en/apache-maven/3.6.0/apache-maven-3.6.0-src.zip
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/maven-1459/org/apache/ma
> > > > ven/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:
> > > >
> > >
> >
> 5b4b5ca569d5476f9d6a2b8080927f58da9ca10a04c593df3d8c012e60fdcf7dcf70c4bc5db0
> > > > d068b3a36785ede62a55fd1778b22ecadcf787485681ddc758a8
> > > >
> > > > apache-maven-3.6.0-src.zip:
> > > >
> > > >sha1: 6149f259489acf36e2c04ec0dd713f99336b3346
> > > > sha512:
> > > >
> > >
> >
> c5794a6723d8d0fc8ff447b42e5a8c13524a44f8508a305d463f811c8039c7e9166d709077c8
> > > > 373d3cf980ce24feaebb2431cb50fb274933ab3bc2a90355
> > > >
> > > > Git tag:
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=97c98ec64a1fdfee7
> > > > 767ce5ffb20918da4f719f3
> > > >
> > > > 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
> > >
> > >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>


Re: issue with junit 5 integration

2018-09-05 Thread Dan Tran
" surefire provider forces 1.2.0" this is not good :-)  i thought surefire
auto detect first one available in classpath

On Tue, Sep 4, 2018 at 11:06 PM Romain Manni-Bucau 
wrote:

> jupiter ;)
>
> junit 5 is not jupiter but platform+ engine*s* so it must detect the full
> stack and not just the default. A first step can be to detect
> platform+jupiter+engine but I guess we will get spock, cucumber etc engine
> quickly so being generic can be worth it. In my case I have vintage-engine
> - cause i have junit4 and junit5 extensions and it is broken cause vintage
> uses platform method of the 1.3.0 and the surefire provider forces 1.2.0.
>
> In my proposal, the project dependencies (likely scope test on user side or
> compile for engine/extension writers) is used and the plugin can
> override/force some dependencies if needed. Alternative surefire could get
> a specific config for that, not sure it does worth it.
>
> Hope it is clearer.
>
> 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 mer. 5 sept. 2018 à 07:41, Dan Tran  a écrit :
>
> > Odd, I am under impression  surefire auto detect  junit-jupiter-engine
> at
> > runtime
> >
> > am I missing something?
> >
> > -D
> >
> > On Tue, Sep 4, 2018 at 10:08 PM Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> > > It does _NOT_ work and as mentionned you can test on meecrowave trying
> to
> > > upgrade the version in junit module.
> > >
> > > The test classpath build ignores project and plugin dependencies. It
> > faked
> > > working until 5.3.0-RC1 cause no breakage was visible.
> > >
> > > When testing, dont forget to use jupiter, vintage engines + platform
> > stack,
> > > otherwise code is compatible with 1.2 which gets loaded. The doc
> ignores
> > > the platform and vintage engine and guess it was not tested at all
> > checking
> > > the code ;). Not a big deal since it is a "first" release but we should
> > be
> > > ablz to get it fixed quickly.
> > >
> > >
> > > Le mar. 4 sept. 2018 23:51, Olivier Lamy  a écrit :
> > >
> > > > Ok perso I don't mind (it just need to be documented)
> > > > But the issue is: users are used to simply upgrade their junit
> > > dependency.
> > > >
> > > >
> > > > On Wed, 5 Sep 2018 at 07:37, Christian Stein 
> > wrote:
> > > >
> > > > > No, it works with Surefire 2.22.0 and JUnit 5.3.
> > > > >
> > > > > Just add (or move) the test-runtime dependencies to the Surefire
> > plugin
> > > > > element:
> > > > >
> > > > > 
> > > > >
> > > > >   
> > > > >   
> > > > >  maven-surefire-plugin
> > > > >  2.22.0
> > > > >  
> > > > >
> > > > >org.junit.jupiter
> > > > >
> junit-jupiter-engine
> > > > >5.3.0
> > > > >
> > > > >  
> > > > >   
> > > > >
> > > > > 
> > > > >
> > > > >
> > > > > Just checking our sample builds over at JUnit 5. Which do _NOT_ do
> > this
> > > > at
> > > > > the moment.
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Sep 4, 2018 at 11:32 PM Olivier Lamy 
> > wrote:
> > > > >
> > > > > > Hi
> > > > > > very embarrassing issue which probably worth a quick release!
> > > > > > Can you create a jira?
> > > > > > As junit 5.3.0 has just been released,  I might be happy to cut
> > > 2.22.1
> > > > > very
> > > > > > quickly with only this fix.
> > > > > > others wdyt?
> > > > > >
> > > > > >
> > > > > > On Wed, 5 Sep 2018 at 06:46, Romain Manni-Bucau <
> > > rmannibu...@gmail.com
> > > > >
> &g

Re: issue with junit 5 integration

2018-09-04 Thread Dan Tran
Odd, I am under impression  surefire auto detect  junit-jupiter-engine  at
runtime

am I missing something?

-D

On Tue, Sep 4, 2018 at 10:08 PM Romain Manni-Bucau 
wrote:

> It does _NOT_ work and as mentionned you can test on meecrowave trying to
> upgrade the version in junit module.
>
> The test classpath build ignores project and plugin dependencies. It faked
> working until 5.3.0-RC1 cause no breakage was visible.
>
> When testing, dont forget to use jupiter, vintage engines + platform stack,
> otherwise code is compatible with 1.2 which gets loaded. The doc ignores
> the platform and vintage engine and guess it was not tested at all checking
> the code ;). Not a big deal since it is a "first" release but we should be
> ablz to get it fixed quickly.
>
>
> Le mar. 4 sept. 2018 23:51, Olivier Lamy  a écrit :
>
> > Ok perso I don't mind (it just need to be documented)
> > But the issue is: users are used to simply upgrade their junit
> dependency.
> >
> >
> > On Wed, 5 Sep 2018 at 07:37, Christian Stein  wrote:
> >
> > > No, it works with Surefire 2.22.0 and JUnit 5.3.
> > >
> > > Just add (or move) the test-runtime dependencies to the Surefire plugin
> > > element:
> > >
> > > 
> > >
> > >   
> > >   
> > >  maven-surefire-plugin
> > >  2.22.0
> > >  
> > >
> > >org.junit.jupiter
> > >junit-jupiter-engine
> > >5.3.0
> > >
> > >  
> > >   
> > >
> > > 
> > >
> > >
> > > Just checking our sample builds over at JUnit 5. Which do _NOT_ do this
> > at
> > > the moment.
> > >
> > >
> > >
> > > On Tue, Sep 4, 2018 at 11:32 PM Olivier Lamy  wrote:
> > >
> > > > Hi
> > > > very embarrassing issue which probably worth a quick release!
> > > > Can you create a jira?
> > > > As junit 5.3.0 has just been released,  I might be happy to cut
> 2.22.1
> > > very
> > > > quickly with only this fix.
> > > > others wdyt?
> > > >
> > > >
> > > > On Wed, 5 Sep 2018 at 06:46, Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Hi guys,
> > > > >
> > > > > Jira seems down so sending a mail.
> > > > >
> > > > > I wanted to upgrade Meecrowave to JUnit 5.3 since it is out but I
> > > > realized
> > > > > the way surefire provider was developped for JUnit 5 was forcing
> the
> > > > > junit-platform-engine even adding it manually in the test
> > dependencies
> > > or
> > > > > plugin dependencies.
> > > > >
> > > > > Side note: I didn't investigated other providers but I guess it is
> > the
> > > > > exact same but the API breakage are happening less often.
> > > > >
> > > > > I therefore created a PR to fix that ->
> > > > > https://github.com/apache/maven-surefire/pull/193
> > > > >
> > > > > Note: I didn't upgrade the JUnit 5 version in the same release but
> it
> > > > > should probably be done too in another commit/PR.
> > > > >
> > > > > I wonder if you have release plans which could include this. In
> terms
> > > of
> > > > > issues I have in mind the other thing about JUnit 5 which would be
> > > great
> > > > to
> > > > > add is the support for display names instead of using the
> class+test
> > > > names
> > > > > in the logs and reports but this is less mandatory than previous
> one
> > > > which
> > > > > fails with a NoSuchMethod error when using vintage engine.
> > > > >
> > > > > 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
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Olivier Lamy
> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > >
> > >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>


Re: [VOTE] Release Apache Maven 3.5.4

2018-06-18 Thread Dan Tran
+1 (non-binding) tested on windows/linux using a large multi-module build
with Takari's smart builder and verified the Jansi multi-threaded fix for
Windows

-D

On Mon, Jun 18, 2018 at 10:32 AM, Sylwester Lachiewicz <
slachiew...@gmail.com> wrote:

> +1 (non binding)
> Sylwester
>
> pon., 18 cze 2018 o 11:02 użytkownik Enrico Olivelli 
> napisał:
>
> > +1 (non binding)
> >
> > checked signatures and hash of staged artifacts
> > I have used the staged binary artifacts to build a bunch of projects on
> > Linux (Fedora 26), all ok
> >
> > We could also consider not to deliver md5 hash anymore (
> > https://www.apache.org/dev/release-signing.html)
> >
> > Enrico
> >
> >
> >
> > Il giorno dom 17 giu 2018 alle ore 23:10 Stephen Connolly <
> > stephen.alan.conno...@gmail.com> ha scritto:
> >
> > > Dang! forgot to paste the link
> > > https://github.com/apache/maven-site/pull/19
> > >
> > > On Sun, 17 Jun 2018 at 22:09, Stephen Connolly <
> > > stephen.alan.conno...@gmail.com> wrote:
> > >
> > > > Draft site changes
> > > >
> > > > On Sun, 17 Jun 2018 at 21:45, Stephen Connolly <
> > > > stephen.alan.conno...@gmail.com> wrote:
> > > >
> > > >>
> > > >>
> > > >> On Sun, 17 Jun 2018 at 21:44, Stephen Connolly <
> > > >> stephen.alan.conno...@gmail.com> wrote:
> > > >>
> > > >>> Hi,
> > > >>>
> > > >>> We solved 16 issues:
> > > >>>
> > > >>>
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12342826=Text=12316922
> > > >>>
> > > >>> There are 356 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%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> > > >>>
> > > >>> Staging repo:
> > > >>> https://repository.apache.org/content/repositories/maven-1438/
> > > >>>
> > > >>> The distributable binaries and sources can be found here:
> > > >>>
> > > >>>
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1438/org/apache/maven/apache-maven/3.5.4/
> > > >>>
> > > >>> Specifically the zip, tarball and source archives can be found
> here:
> > > >>>
> > > >>>
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-bin.zip
> > > >>>
> > > >>>
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-bin.tar.gz
> > > >>>
> > > >>>
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-src.zip
> > > >>>
> > > >>>
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-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.5.4-src.tar.gz sha1:
> > > >>> 04aefb9462af8cf7ca93808cd246f4c28b8ae4a1 sha256:
> > > >>> f3ba1f1b24bbd4c345174ac616d40e26e72dad6022d56317d3ff6f7dd003e2f5
> > > >>> apache-maven-3.5.4-src.zip: sha1:
> > > >>> 1ee9850a046860d71267a043a29e0aa9acc13bcd sha256:
> > > >>> ddcddecc8048d24edd3fa98fe50ae7f6a753389367d24593bf39e37427f643f5
> > > >>>
> > > >>> Git tag:
> > > >>>
> > > >>>
> > >
> > https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=
> 1edded0938998edf8bf061f1ceb3cfdeccf443fe
> > > >>>
> > > >>> Staging site:
> > > >>> https://maven.apache.org/components/ref/3-LATEST/
> > > >>>
> > > >>> Vote open for 72 hours.
> > > >>>
> > > >>> [ ] +1
> > > >>> [ ] +0
> > > >>> [ ] -1
> > > >>>
> > > >>> Thanks,
> > > >>>
> > > >>> Stephen.
> > > >>>
> > > >>
> > > >> $ sra https://repository.apache.org/content/repositories/maven-1438
> > > 3.5.4
> > > >> Analyzer...
> > > >>
> > > >> stagingUrl:
> > > https://repository.apache.org/content/repositories/maven-1438
> > > >> groupId: org.apache.maven
> > > >> artifactId: apache-maven
> > > >> version: 3.5.4
> > > >>
> > > >> Source ZIP url exists.
> > > >>
> > > >>
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-src.zip
> > > >>
> > > >> Source ZIP SHA1 url exists.
> > > >>
> > > >>
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-src.zip.sha1
> > > >>
> > > >> Binary ZIP url exists.
> > > >>
> > > >>
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-bin.zip
> > > >>
> > > >> Binary ZIP SHA1 url exists.
> > > >>
> > > >>
> > >
> > https://repository.apache.org/content/repositories/maven-
> 1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-bin.zip.sha1
> > > >>
> > > >> Calculated SHA1 of source ZIP matches published SHA1 of source ZIP.
> > > >> 

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

2018-06-12 Thread Dan Tran
+1 (Non binding) testest with a large multi-module with mixtures of
junit5/4 and testng

Huge thanks for getting this out and it just works very impressive

-D

On Mon, Jun 11, 2018 at 6:31 PM, Tibor Digana 
wrote:

> Hi,
>
> We solved 15 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317927=12343247
>
> 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-1436/
> https://repository.apache.org/content/repositories/maven-
> 1436/org/apache/maven/surefire/surefire/2.22.0/surefire-2.22.0-source-
> release.zip
>
> Source release checksum(s):
> surefire-2.22.0-source-release.zip sha1:
> 82474b41354d9cf91288dd065c77d3f9ec79d011
>
> 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
>


Re: [VOTE] Release Apache Maven 3.5.3

2018-03-01 Thread Dan Tran
Hi all

Sylwester Lachiewicz provided a fix for jansi 1.18-SNAPSHOT  which resolves
my issue.  I am not able to reproduce antrun issue


-Dan

On Thu, Mar 1, 2018 at 5:00 AM, Stephane Nicoll 
wrote:

> +1
>
> Thanks,
> S.
>
> On Sat, Feb 24, 2018 at 11:01 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > On 24 February 2018 at 22:00, Stephen Connolly <
> > stephen.alan.conno...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > We solved 22 issues:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > version=12341428=Text=12316922
> > >
> > > There are 381 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%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-1401/
> > >
> > > The distributable binaries and sources can be found here:
> > > https://repository.apache.org/content/repositories/maven-
> > > 1401/org/apache/maven/apache-maven/3.5.3/
> > >
> > > Specifically the zip, tarball and source archives can be found here:
> > > https://repository.apache.org/content/repositories/maven-
> > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip
> > > https://repository.apache.org/content/repositories/maven-
> > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.tar.gz
> > > https://repository.apache.org/content/repositories/maven-
> > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip
> > > https://repository.apache.org/content/repositories/maven-
> > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.tar.gz
> > >
> > > The release artifacts are staged for distribution in:
> > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
> > >
> > > Source release checksum(s):
> > > apache-maven-3.5.3-src.tar.gz sha1: 60905d8b8b025b091f456ec25ad60d
> > da56c26ad5
> > > sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd10
> 7e19
> > > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4
> > f1c4c96766
> > > sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7cc
> bd57
> > >
> > > Git tag:
> > > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> > > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297
> > >
> > > Staging site:
> > > https://maven.apache.org/components/ref/3-LATEST/
> > >
> > > Vote open for 72 hours.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> > > Thanks,
> > >
> > > Stephen.
> > >
> >
> >
> > $ sra https://repository.apache.org/content/repositories/maven-1401
> 3.5.3
> > Analyzer...
> >
> > stagingUrl: https://repository.apache.org/content/repositories/maven-
> 1401
> > groupId: org.apache.maven
> > artifactId: apache-maven
> > version: 3.5.3
> >
> > Source ZIP url exists.
> > https://repository.apache.org/content/repositories/maven-
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip
> >
> > Source ZIP SHA1 url exists.
> > https://repository.apache.org/content/repositories/maven-
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip.sha1
> >
> > Binary ZIP url exists.
> > https://repository.apache.org/content/repositories/maven-
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip
> >
> > Binary ZIP SHA1 url exists.
> > https://repository.apache.org/content/repositories/maven-
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip.sha1
> >
> > Calculated SHA1 of source ZIP matches published SHA1 of source ZIP.
> > a9be51d571165261dfb2e0c8ecc6b4f1c4c96766
> >
> > Calculated SHA1 of binary ZIP matches published SHA1 of binary ZIP.
> > 4a4844990333e2548540729ce9ab57f52a63148d
> >
> > Git revision of release as determined from
> > maven-core-3.5.3.jar:org/apache/maven/messages/build.
> > properties(buildNumber):
> > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297
> >
> > Files that are present in the source distribution but not in the source
> > revision:
> > DEPENDENCIES
> >
>


Re: [VOTE] Release Apache Maven 3.5.3

2018-02-27 Thread Dan Tran
Hi all,

I believe my usage of antrun is legit to make sure user who is using  mvn
install ( without clean) has a proper clean up before another plugin
execution

  
org.apache.maven.plugins
maven-antrun-plugin

  
work.around.to.clean.up.classes.before.jsonschema.start
generate-sources

  run


  

  

  

  


here is the command to reproduce the antrun issue


  mvn clean install --builder smart -T1.0C -DskipTests


Add  -B to remove the issue but it is not ideal

Only only happens on windows ( i only test with windows and linux)

-D



On Tue, Feb 27, 2018 at 7:44 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> On 27 February 2018 at 14:46, Mirko Friedenhagen <mfriedenha...@gmail.com>
> wrote:
>
> > +1 from my side, tested with 10 inhouse projects. Or is this vote
> canceled?
> >
>
> Not cancelled yet. Unclear if Dan's issue is something forking maven and
> parsing the output... the task name
> "work.around.to.clean.up.classes.before.jsonschema.start" sounds like it
> could be doing something crazy like that, in which case it is not using -B
> when forking maven in Dan's codebase that could be the root cause.
>
>
> > Regards Mirko
> > --
> > http://illegalstateexception.blogspot.com/
> > https://github.com/mfriedenhagen/
> > https://bitbucket.org/mfriedenhagen/
> >
> >
> > On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran <dant...@gmail.com> wrote:
> > >   correction
> > >
> > > found this reference, found on 3.5.2 but I only encounter this on 3.5.3
> > RC
> > >
> > > https://stackoverflow.com/questions/48723899/maven-
> > > numberformatexception-when-packaging
> > >
> > >
> > > On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran <dant...@gmail.com> wrote:
> > >
> > >> found this reference, found on 3.5.2 but I only encounter this on
> 3.5.2
> > RC
> > >>
> > >> https://stackoverflow.com/questions/48723899/maven-
> > >> numberformatexception-when-packaging
> > >>
> > >> On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran <dant...@gmail.com> wrote:
> > >>
> > >>> my build contains 270+ modules using java 8.  The failure found on
> > >>> windows. Have not tested on Linux  yet
> > >>>
> > >>> -D
> > >>>
> > >>> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran <dant...@gmail.com>
> wrote:
> > >>>
> > >>>> Encounter random failure at antrun MOJO + smart builder
> > >>>>
> > >>>> here is the error message
> > >>>>
> > >>>> [ERROR] Failed to execute goal org.apache.maven.plugins:
> > maven-antrun-plugin:1.8:run
> > >>>> (work.around.to.clean.up.classes.before.jsonschema.start) on
> project
> > >>>> adm-schema: Error executing Ant tasks: For input string: "1;" ->
> > [Help 1]
> > >>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> > >>>> execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run
> > >>>> (work.around.to.clean.up.classes.before.jsonschema.start) on
> project
> > >>>> adm-schema: Error executing Ant tasks: For input string: "1;"
> > >>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > >>>> (MojoExecutor.java:213)
> > >>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > >>>> (MojoExecutor.java:154)
> > >>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > >>>> (MojoExecutor.java:146)
> > >>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> > buildProject
> > >>>> (LifecycleModuleBuilder.java:117)
> > >>>> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
> > >>>> (SmartBuilderImpl.java:205)
> > >>>> at io.takari.maven.builder.smart.SmartBuilderImpl$
> > ProjectBuildTask.run
> > >>>> (SmartBuilderImpl.java:77)
> > >>>> at java.util.concurrent.Executors$RunnableAdapter.call
> > >>>> (Executors.java:511)
> > >>>> at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> > >>>> at java.util.concurrent.ThreadPoolExe

Re: [VOTE] Release Apache Maven 3.5.3

2018-02-25 Thread Dan Tran
  correction

found this reference, found on 3.5.2 but I only encounter this on 3.5.3 RC

https://stackoverflow.com/questions/48723899/maven-
numberformatexception-when-packaging


On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran <dant...@gmail.com> wrote:

> found this reference, found on 3.5.2 but I only encounter this on 3.5.2 RC
>
> https://stackoverflow.com/questions/48723899/maven-
> numberformatexception-when-packaging
>
> On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran <dant...@gmail.com> wrote:
>
>> my build contains 270+ modules using java 8.  The failure found on
>> windows. Have not tested on Linux  yet
>>
>> -D
>>
>> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran <dant...@gmail.com> wrote:
>>
>>> Encounter random failure at antrun MOJO + smart builder
>>>
>>> here is the error message
>>>
>>> [ERROR] Failed to execute goal 
>>> org.apache.maven.plugins:maven-antrun-plugin:1.8:run
>>> (work.around.to.clean.up.classes.before.jsonschema.start) on project
>>> adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run
>>> (work.around.to.clean.up.classes.before.jsonschema.start) on project
>>> adm-schema: Error executing Ant tasks: For input string: "1;"
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>>> (MojoExecutor.java:213)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>>> (MojoExecutor.java:154)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>>> (MojoExecutor.java:146)
>>> at 
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>>> (LifecycleModuleBuilder.java:117)
>>> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
>>> (SmartBuilderImpl.java:205)
>>> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
>>> (SmartBuilderImpl.java:77)
>>> at java.util.concurrent.Executors$RunnableAdapter.call
>>> (Executors.java:511)
>>> at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker
>>> (ThreadPoolExecutor.java:1149)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run
>>> (ThreadPoolExecutor.java:624)
>>> at java.lang.Thread.run (Thread.java:748)
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
>>> executing Ant tasks: For input string: "1;"
>>> at org.apache.maven.plugin.antrun.AntRunMojo.execute
>>> (AntRunMojo.java:347)
>>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>>> (DefaultBuildPluginManager.java:137)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>>> (MojoExecutor.java:208)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>>> (MojoExecutor.java:154)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>>> (MojoExecutor.java:146)
>>> at 
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>>> (LifecycleModuleBuilder.java:117)
>>> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
>>> (SmartBuilderImpl.java:205)
>>> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
>>> (SmartBuilderImpl.java:77)
>>> at java.util.concurrent.Executors$RunnableAdapter.call
>>> (Executors.java:511)
>>> at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker
>>> (ThreadPoolExecutor.java:1149)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run
>>> (ThreadPoolExecutor.java:624)
>>> at java.lang.Thread.run (Thread.java:748)
>>> Caused by: java.lang.NumberFormatException: For input string: "1;"
>>> at java.lang.NumberFormatException.forInputString
>>> (NumberFormatException.java:65)
>>> at java.lang.Integer.parseInt (Integer.java:580)
>>> at java.lang.Integer. (Integer.java:867)
>>> at org.fusesource.jansi.AnsiPrintStream.filter
>>> (AnsiPrintStream.java:129)
>>> at org.fusesource.jansi.FilterPrintStream.write
>>> (FilterPrintStream.java:59)
>>> at org.fusesource.jansi.FilterPrintStream.write
>>> (FilterPrint

Re: [VOTE] Release Apache Maven 3.5.3

2018-02-25 Thread Dan Tran
found this reference, found on 3.5.2 but I only encounter this on 3.5.2 RC

https://stackoverflow.com/questions/48723899/maven-numberformatexception-when-packaging

On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran <dant...@gmail.com> wrote:

> my build contains 270+ modules using java 8.  The failure found on
> windows. Have not tested on Linux  yet
>
> -D
>
> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran <dant...@gmail.com> wrote:
>
>> Encounter random failure at antrun MOJO + smart builder
>>
>> here is the error message
>>
>> [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-antrun-plugin:1.8:run
>> (work.around.to.clean.up.classes.before.jsonschema.start) on project
>> adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run
>> (work.around.to.clean.up.classes.before.jsonschema.start) on project
>> adm-schema: Error executing Ant tasks: For input string: "1;"
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:213)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:154)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:146)
>> at 
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>> (LifecycleModuleBuilder.java:117)
>> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
>> (SmartBuilderImpl.java:205)
>> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
>> (SmartBuilderImpl.java:77)
>> at java.util.concurrent.Executors$RunnableAdapter.call
>> (Executors.java:511)
>> at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker
>> (ThreadPoolExecutor.java:1149)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> (ThreadPoolExecutor.java:624)
>> at java.lang.Thread.run (Thread.java:748)
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
>> executing Ant tasks: For input string: "1;"
>> at org.apache.maven.plugin.antrun.AntRunMojo.execute
>> (AntRunMojo.java:347)
>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>> (DefaultBuildPluginManager.java:137)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:208)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:154)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:146)
>> at 
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>> (LifecycleModuleBuilder.java:117)
>> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
>> (SmartBuilderImpl.java:205)
>> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
>> (SmartBuilderImpl.java:77)
>> at java.util.concurrent.Executors$RunnableAdapter.call
>> (Executors.java:511)
>> at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker
>> (ThreadPoolExecutor.java:1149)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> (ThreadPoolExecutor.java:624)
>> at java.lang.Thread.run (Thread.java:748)
>> Caused by: java.lang.NumberFormatException: For input string: "1;"
>> at java.lang.NumberFormatException.forInputString
>> (NumberFormatException.java:65)
>> at java.lang.Integer.parseInt (Integer.java:580)
>> at java.lang.Integer. (Integer.java:867)
>> at org.fusesource.jansi.AnsiPrintStream.filter
>> (AnsiPrintStream.java:129)
>> at org.fusesource.jansi.FilterPrintStream.write
>> (FilterPrintStream.java:59)
>> at org.fusesource.jansi.FilterPrintStream.write
>> (FilterPrintStream.java:70)
>> at java.io.PrintStream.write (PrintStream.java:480)
>> at sun.nio.cs.StreamEncoder.writeBytes (StreamEncoder.java:221)
>> at sun.nio.cs.StreamEncoder.implFlushBuffer (StreamEncoder.java:291)
>> at sun.nio.cs.StreamEncoder.flushBuffer (StreamEncoder.java:104)
>> at java.io.OutputStreamWriter.flushBuffer
>> (OutputStreamWriter.java:185)
>> at java.io.PrintStream.newLine (PrintStream.java:546)
>> at java.io.PrintStream.println (PrintStream.java:807)
>> at org.apache.tools.ant.DefaultLogger.printMessage
>> (Default

Re: [VOTE] Release Apache Maven 3.5.3

2018-02-25 Thread Dan Tran
my build contains 270+ modules using java 8.  The failure found on windows.
Have not tested on Linux  yet

-D

On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran <dant...@gmail.com> wrote:

> Encounter random failure at antrun MOJO + smart builder
>
> here is the error message
>
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-antrun-plugin:1.8:run
> (work.around.to.clean.up.classes.before.jsonschema.start) on project
> adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run
> (work.around.to.clean.up.classes.before.jsonschema.start) on project
> adm-schema: Error executing Ant tasks: For input string: "1;"
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
> (SmartBuilderImpl.java:205)
> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
> (SmartBuilderImpl.java:77)
> at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
> at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
> at java.lang.Thread.run (Thread.java:748)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
> executing Ant tasks: For input string: "1;"
> at org.apache.maven.plugin.antrun.AntRunMojo.execute
> (AntRunMojo.java:347)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
> (SmartBuilderImpl.java:205)
> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
> (SmartBuilderImpl.java:77)
> at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
> at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
> at java.lang.Thread.run (Thread.java:748)
> Caused by: java.lang.NumberFormatException: For input string: "1;"
> at java.lang.NumberFormatException.forInputString
> (NumberFormatException.java:65)
> at java.lang.Integer.parseInt (Integer.java:580)
> at java.lang.Integer. (Integer.java:867)
> at org.fusesource.jansi.AnsiPrintStream.filter
> (AnsiPrintStream.java:129)
> at org.fusesource.jansi.FilterPrintStream.write
> (FilterPrintStream.java:59)
> at org.fusesource.jansi.FilterPrintStream.write
> (FilterPrintStream.java:70)
> at java.io.PrintStream.write (PrintStream.java:480)
> at sun.nio.cs.StreamEncoder.writeBytes (StreamEncoder.java:221)
> at sun.nio.cs.StreamEncoder.implFlushBuffer (StreamEncoder.java:291)
> at sun.nio.cs.StreamEncoder.flushBuffer (StreamEncoder.java:104)
> at java.io.OutputStreamWriter.flushBuffer
> (OutputStreamWriter.java:185)
> at java.io.PrintStream.newLine (PrintStream.java:546)
> at java.io.PrintStream.println (PrintStream.java:807)
> at org.apache.tools.ant.DefaultLogger.printMessage
> (DefaultLogger.java:346)
> at org.apache.tools.ant.DefaultLogger.targetStarted
> (DefaultLogger.java:218)
> at org.apache.tools.ant.Project.fireTargetStarted (Project.java:2140)
> at org.apache.tools.ant.Target.performTasks (Target.java:454)
> at org.apache.tools.ant.Project.executeSortedTargets
> (Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget (Project.java:1364)
> at org.apache.maven.plugin.antrun.AntRunMojo.execute
> (AntRunMojo.java:313)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMo

Re: [VOTE] Release Apache Maven 3.5.3

2018-02-25 Thread Dan Tran
Encounter random failure at antrun MOJO + smart builder

here is the error message

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.8:run
(work.around.to.clean.up.classes.before.jsonschema.start) on project
adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run
(work.around.to.clean.up.classes.before.jsonschema.start) on project
adm-schema: Error executing Ant tasks: For input string: "1;"
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
(SmartBuilderImpl.java:205)
at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
(SmartBuilderImpl.java:77)
at java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:511)
at java.util.concurrent.FutureTask.run (FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:624)
at java.lang.Thread.run (Thread.java:748)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing
Ant tasks: For input string: "1;"
at org.apache.maven.plugin.antrun.AntRunMojo.execute
(AntRunMojo.java:347)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
(SmartBuilderImpl.java:205)
at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
(SmartBuilderImpl.java:77)
at java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:511)
at java.util.concurrent.FutureTask.run (FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:624)
at java.lang.Thread.run (Thread.java:748)
Caused by: java.lang.NumberFormatException: For input string: "1;"
at java.lang.NumberFormatException.forInputString
(NumberFormatException.java:65)
at java.lang.Integer.parseInt (Integer.java:580)
at java.lang.Integer. (Integer.java:867)
at org.fusesource.jansi.AnsiPrintStream.filter
(AnsiPrintStream.java:129)
at org.fusesource.jansi.FilterPrintStream.write
(FilterPrintStream.java:59)
at org.fusesource.jansi.FilterPrintStream.write
(FilterPrintStream.java:70)
at java.io.PrintStream.write (PrintStream.java:480)
at sun.nio.cs.StreamEncoder.writeBytes (StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer (StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer (StreamEncoder.java:104)
at java.io.OutputStreamWriter.flushBuffer (OutputStreamWriter.java:185)
at java.io.PrintStream.newLine (PrintStream.java:546)
at java.io.PrintStream.println (PrintStream.java:807)
at org.apache.tools.ant.DefaultLogger.printMessage
(DefaultLogger.java:346)
at org.apache.tools.ant.DefaultLogger.targetStarted
(DefaultLogger.java:218)
at org.apache.tools.ant.Project.fireTargetStarted (Project.java:2140)
at org.apache.tools.ant.Target.performTasks (Target.java:454)
at org.apache.tools.ant.Project.executeSortedTargets (Project.java:1393)
at org.apache.tools.ant.Project.executeTarget (Project.java:1364)
at org.apache.maven.plugin.antrun.AntRunMojo.execute
(AntRunMojo.java:313)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
(SmartBuilderImpl.java:205)
at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
(SmartBuilderImpl.java:77)
at java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:511)
at 

Re: [VOTE] Release Apache Maven 3.5.2

2017-10-21 Thread Dan Tran
ouch false alarm,  I forgot to configure the artifactory mirror

Sorry about the noise

-D

On Sat, Oct 21, 2017 at 10:10 AM, Dan Tran <dant...@gmail.com> wrote:

> I am not able getting mvn 3.5.2 to download an internal snapshot
> dependency from comp's central artifactory
>
> here is the error
>
> Caused by: org.eclipse.aether.resolution.DependencyResolutionException:
> Could not find artifact com.oracle.linux.x86_64:jre:rpm:1.8.0_151-SNAPSHOT
> at 
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
> (DefaultRepositorySystem.java:355)
> at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve
> (DefaultProjectDependenciesResolver.java:202)
>
> No issue with 3.5.0 and 3.5.1
>
> Wonder if anyone else encounters the same issue??
>
> Thanks
>
> -Dan
>
> On Fri, Oct 20, 2017 at 7:35 PM, Mark Derricutt <m...@talios.com> wrote:
>
>> +1 looking good from here on my projects/releases.
>>
>> --
>> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
>> Porcupine Tree
>>
>> On Wed, Oct 18, 2017 at 11:50 PM, Stephen Connolly <
>> stephen.alan.conno...@gmail.com> wrote:
>>
>> > Hi,
>> >
>> > We solved 26 issues:
>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> > version=12338964=Text=12316922
>> >
>> > There are 357 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%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/maven-1373/
>> >
>> > The distributable binaries and sources can be found here:
>> > https://repository.apache.org/content/repositories/maven-
>> > 1373/org/apache/maven/apache-maven/3.5.2/
>> >
>> > Specifically the zip, tarball and source archives can be found here:
>> > https://repository.apache.org/content/repositories/maven-
>> > 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip
>> > https://repository.apache.org/content/repositories/maven-
>> > 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.tar.gz
>> > https://repository.apache.org/content/repositories/maven-
>> > 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip
>> > https://repository.apache.org/content/repositories/maven-
>> > 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.tar.gz
>> >
>> > Source release checksum(s):
>> > apache-maven-3.5.2-src.tar.gz sha1: 97d6d7b18485b7906dd7f313cdd411
>> > 91d16dde46
>> > apache-maven-3.5.2-src.zip: sha1: dc8caa5cdacb400943d2491a020f74
>> 2a518e8f08
>> >
>> > Git tag:
>> > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
>> > 138edd61fd100ec658bfa2d307c43b76940a5d7d
>> >
>> > Staging site:
>> > https://maven.apache.org/components/ref/3-LATEST/
>> >
>> > Vote open for 72 hours.
>> >
>> > [ ] +1
>> > [ ] +0
>> > [ ] -1
>> >
>> > Thanks,
>> >
>> > Stephen.
>> >
>>
>
>


Re: [VOTE] Release Apache Maven 3.5.2

2017-10-21 Thread Dan Tran
I am not able getting mvn 3.5.2 to download an internal snapshot dependency
from comp's central artifactory

here is the error

Caused by: org.eclipse.aether.resolution.DependencyResolutionException:
Could not find artifact com.oracle.linux.x86_64:jre:rpm:1.8.0_151-SNAPSHOT
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
(DefaultRepositorySystem.java:355)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve
(DefaultProjectDependenciesResolver.java:202)

No issue with 3.5.0 and 3.5.1

Wonder if anyone else encounters the same issue??

Thanks

-Dan

On Fri, Oct 20, 2017 at 7:35 PM, Mark Derricutt  wrote:

> +1 looking good from here on my projects/releases.
>
> --
> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
> Porcupine Tree
>
> On Wed, Oct 18, 2017 at 11:50 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Hi,
> >
> > We solved 26 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12338964=Text=12316922
> >
> > There are 357 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%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1373/
> >
> > The distributable binaries and sources can be found here:
> > https://repository.apache.org/content/repositories/maven-
> > 1373/org/apache/maven/apache-maven/3.5.2/
> >
> > Specifically the zip, tarball and source archives can be found here:
> > https://repository.apache.org/content/repositories/maven-
> > 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip
> > https://repository.apache.org/content/repositories/maven-
> > 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.tar.gz
> > https://repository.apache.org/content/repositories/maven-
> > 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip
> > https://repository.apache.org/content/repositories/maven-
> > 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.tar.gz
> >
> > Source release checksum(s):
> > apache-maven-3.5.2-src.tar.gz sha1: 97d6d7b18485b7906dd7f313cdd411
> > 91d16dde46
> > apache-maven-3.5.2-src.zip: sha1: dc8caa5cdacb400943d2491a020f74
> 2a518e8f08
> >
> > Git tag:
> > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> > 138edd61fd100ec658bfa2d307c43b76940a5d7d
> >
> > Staging site:
> > https://maven.apache.org/components/ref/3-LATEST/
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Thanks,
> >
> > Stephen.
> >
>


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

2017-09-13 Thread Dan Tran
+1 non binding, works with my production build and I can only  test with
snapshot

On Tue, Sep 12, 2017 at 11:53 PM, Thomas Collignon <tomiphon...@gmail.com>
wrote:

> Hello
>
> +1 for me
>
> 2017-09-12 10:29 GMT+02:00 Tibor Digana <tibor.dig...@googlemail.com>:
>
> > Hi Dan,
> > Yes you can use such version. The URL for snapshots is
> > https://repository.apache.org/content/repositories/snapshots
> >
> > On Tue, Sep 12, 2017 at 5:01 AM, Dan Tran <dant...@gmail.com> wrote:
> >
> > > Is there a snapshot i can test with my production? only see
> 2.21-SNAPSHOT
> > >
> > > Thanks
> > >
> > > -Dan
> > >
> > > On Mon, Sep 11, 2017 at 5:05 AM, Enrico Olivelli <eolive...@gmail.com>
> > > wrote:
> > >
> > > > +1 (non binding)
> > > >
> > > > run unit tests on surefire project itself
> > > >
> > > > on  JDK 9+181 run unit tests of other Java8 projects which required
> > > > java.se.ee module to be present
> > > >
> > > > Thank you !
> > > >
> > > > Enrico
> > > >
> > > >
> > > > 2017-09-11 5:33 GMT+02:00 Tibor Digana <tibor.dig...@googlemail.com
> >:
> > > >
> > > > > Hi,
> > > > >
> > > > > We solved 24 issues:
> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > projectId=12317927=12340297
> > > > >
> > > > > There are 101 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-1366/
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > > 1366/org/apache/maven/surefire/surefire/2.20.1/
> > surefire-2.20.1-source-
> > > > > release.zip
> > > > >
> > > > > Source release checksum(s):
> > > > > maven-surefire-plugin-2.20.1-site-source.zip sha1:
> > > > > 4187a7932268c7ad467973254d87584085e305c1
> > > > >
> > > > > 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
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Cheers
> > Tibor
> >
>


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

2017-09-11 Thread Dan Tran
Is there a snapshot i can test with my production? only see 2.21-SNAPSHOT

Thanks

-Dan

On Mon, Sep 11, 2017 at 5:05 AM, Enrico Olivelli 
wrote:

> +1 (non binding)
>
> run unit tests on surefire project itself
>
> on  JDK 9+181 run unit tests of other Java8 projects which required
> java.se.ee module to be present
>
> Thank you !
>
> Enrico
>
>
> 2017-09-11 5:33 GMT+02:00 Tibor Digana :
>
> > Hi,
> >
> > We solved 24 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12317927=12340297
> >
> > There are 101 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-1366/
> > https://repository.apache.org/content/repositories/maven-
> > 1366/org/apache/maven/surefire/surefire/2.20.1/surefire-2.20.1-source-
> > release.zip
> >
> > Source release checksum(s):
> > maven-surefire-plugin-2.20.1-site-source.zip sha1:
> > 4187a7932268c7ad467973254d87584085e305c1
> >
> > 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
> >
>


Re: [VOTE] Release Apache Maven 3.5.1

2017-09-11 Thread Dan Tran
False alarm, I missed configure global settings.xml, it is missing the
default repository setup

-D

On Sun, Sep 10, 2017 at 11:47 PM, Tibor Digana 
wrote:

> +1:
> 3.5.1 works in my project like a charm ;-)
>
> On Sun, Sep 10, 2017 at 5:39 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Hi,
> >
> > We solved 25 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12338964=Text=12316922
> >
> > There are 350 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%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1364/
> >
> > The distributable binaries and sources can be found here:
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/
> >
> > Specifically the zip, tarball and source archives can be found here:
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-bin.zip
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-bin.tar.gz
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-src.zip
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-src.tar.gz
> >
> > Source release checksum(s):
> > apache-maven-3.5.1-src.tar.gz sha1: 9eb821f153c7667194aa11ccd099b7
> > bd2059560d
> > apache-maven-3.5.1-src.zip: sha1: 121d54b045380a8a4895eb137970ab
> 69e698eb0e
> >
> > Git tag:
> > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> > 094e4e31a5af55bb17be87675da41d9aeca062f3
> >
> > Staging site:
> > https://maven.apache.org/components/ref/3-LATEST/
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Thanks,
> >
> > Stephen.
> >
>
>
>
> --
> Cheers
> Tibor
>


Re: [VOTE] Release Apache Maven 3.5.1

2017-09-11 Thread Dan Tran
I have no issue build maven 3.5.2-SNAPSHOT with clean verify at top level,
 but  the following build fails

mvn clean verify -f apache-maven

C:\views\dev\maven\maven>mvn clean verify -f apache-maven
[INFO] Scanning for projects...
[INFO]
[INFO]

[INFO] Building Apache Maven Distribution 3.5.2-SNAPSHOT
[INFO]

[WARNING] The POM for org.apache.maven:maven-embedder:jar:3.5.2-SNAPSHOT is
missing, no dependency information available
[WARNING] The POM for org.apache.maven:maven-core:jar:3.5.2-SNAPSHOT is
missing, no dependency information available
[WARNING] The POM for org.apache.maven:maven-compat:jar:3.5.2-SNAPSHOT is
missing, no dependency information available
[WARNING] The POM for
org.apache.maven:maven-slf4j-provider:jar:3.5.2-SNAPSHOT is missing, no
dependency information available
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 0.788 s
[INFO] Finished at: 2017-09-10T23:29:22-07:00
[INFO] Final Memory: 10M/243M
[INFO]

[ERROR] Failed to execute goal on project apache-maven: Could not resolve
dependencies for project org.apache.maven:apache-maven:pom:3.5.2-SNAPSHOT:
The following artifacts could not be resolved:
org.apache.maven:maven-embedder:jar:3.5.2-SNAPSHOT,
org.apache.maven:maven-core:jar:3.5.2-SNAPSHOT,
org.apache.maven:maven-compat:jar:3.5.2-SNAPSHOT,
org.apache.maven:maven-slf4j-provider:jar:3.5.2-SNAPSHOT: Could not find
artifact org.apache.maven:maven-embedder:jar:3.5.2-SNAPSHOT -> [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/DependencyResolutionException


no issue with mvn 3.5.0

-Dan

On Sun, Sep 10, 2017 at 11:10 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> I wonder if mng-6275 is affecting that plugin
>
> On Mon 11 Sep 2017 at 01:00, Mark Derricutt  wrote:
>
> > +0 non-commital -
> >
> > Tested on our tiles/osgi based projects and all seems to work, but for
> > some reason - one project that uses the
> > org.openqa.selenium.phantomjs.PhantomJSDriverService seems to blowing up
> > when using 3.5.1 - need to do some more digging and see if I can spot
> whats
> > going on.
> >
> > Will try and dig into this after work tonight.
> >
> > Mark
> >
> > On 11 Sep 2017, at 8:01, Arnaud Héritier wrote:
> >
> > Tested on several projects
> >
> > +1
> >
> > On Sun, Sep 10, 2017 at 5:39 PM, Stephen Connolly <
> > stephen.alan.conno...@gmail.com> wrote:
> >
> > Hi,
> >
> > We solved 25 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12338964=Text=12316922
> >
> > There are 350 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%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1364/
> >
> > The distributable binaries and sources can be found here:
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/
> >
> > Specifically the zip, tarball and source archives can be found here:
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-bin.zip
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-bin.tar.gz
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-src.zip
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-src.tar.gz
> >
> > Source release checksum(s):
> > apache-maven-3.5.1-src.tar.gz sha1: 9eb821f153c7667194aa11ccd099b7
> > bd2059560d
> > apache-maven-3.5.1-src.zip: sha1: 121d54b045380a8a4895eb137970ab
> 69e698eb0e
> >
> > Git tag:
> > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> > 094e4e31a5af55bb17be87675da41d9aeca062f3
> >
> > Staging site:
> > https://maven.apache.org/components/ref/3-LATEST/
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Thanks,
> >
> > Stephen.
> >
> > --
> > -
> > Arnaud Héritier
> > http://aheritier.net
> > Mail/GTalk: aheritier AT gmail DOT com
> > Twitter/Skype : aheritier
> >
> > --
> >
> > "The ease with which a change can 

Re: [VOTE] Release Apache Maven 3.5.1

2017-09-10 Thread Dan Tran
Looks like 3.5.1 not able to resolve snapshot dependencies

i just clone out apache-maven and, change directory to apache-maven and
build from there

here is error

[ERROR] Failed to execute goal on project apache-maven: Could not resolve
dependencies for project org.apache.maven:apache-maven:pom:3.5.2-SNAPSHOT:
The following artifacts could not be resolved:
org.apache.maven:maven-embedder:jar:3.5.2-SNAPSHOT,
org.apache.maven:maven-core:jar:3.5.2-SNAPSHOT,
org.apache.maven:maven-compat:jar:3.5.2-SNAPSHOT,
org.apache.maven:maven-slf4j-provider:jar:3.5.2-SNAPSHOT: Could not find
artifact org.apache.maven:maven-embedder:jar:3.5.2-SNAPSHOT -> [Help 1]

my build is behind artifactory

Same issue also found at my  internal project


-Dan

On Sun, Sep 10, 2017 at 1:01 PM, Arnaud Héritier 
wrote:

> Tested on several projects
>
> +1
>
> On Sun, Sep 10, 2017 at 5:39 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Hi,
> >
> > We solved 25 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12338964=Text=12316922
> >
> > There are 350 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%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1364/
> >
> > The distributable binaries and sources can be found here:
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/
> >
> > Specifically the zip, tarball and source archives can be found here:
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-bin.zip
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-bin.tar.gz
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-src.zip
> > https://repository.apache.org/content/repositories/maven-
> > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-src.tar.gz
> >
> > Source release checksum(s):
> > apache-maven-3.5.1-src.tar.gz sha1: 9eb821f153c7667194aa11ccd099b7
> > bd2059560d
> > apache-maven-3.5.1-src.zip: sha1: 121d54b045380a8a4895eb137970ab
> 69e698eb0e
> >
> > Git tag:
> > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> > 094e4e31a5af55bb17be87675da41d9aeca062f3
> >
> > Staging site:
> > https://maven.apache.org/components/ref/3-LATEST/
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Thanks,
> >
> > Stephen.
> >
>
>
>
> --
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>


Re: [MNG-6084] Support JSR 250 annotations

2017-05-25 Thread Dan Tran
Of course, I second that for 3.5.1

Thanks

-Dan

On Thu, May 25, 2017 at 12:41 AM, Michael Osipov <micha...@apache.org>
wrote:

> Am 2017-05-25 um 05:11 schrieb Dan Tran:
>
>> Thanks Michael for pushing this out. Looking forward to use it in 3.5.1
>>
>
> Just to be sure, you are officially seconding it?
>
>
> On Wed, May 24, 2017 at 4:04 PM, Michael Osipov <micha...@apache.org>
>> wrote:
>>
>> Who seconds MNG-6084 for 3.5.1?
>>>
>>> This one was developed by Dan Tran. I added non-functional fixes to it.
>>> All ITs pass as well as its own IT.
>>>
>>> Michael
>>>
>>> -
>>> 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: [MNG-6084] Support JSR 250 annotations

2017-05-24 Thread Dan Tran
Thanks Michael for pushing this out. Looking forward to use it in 3.5.1

-D

On Wed, May 24, 2017 at 4:04 PM, Michael Osipov <micha...@apache.org> wrote:

> Who seconds MNG-6084 for 3.5.1?
>
> This one was developed by Dan Tran. I added non-functional fixes to it.
> All ITs pass as well as its own IT.
>
> Michael
>
> -
> 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 - TAKE 3

2017-04-09 Thread Dan Tran
Tested with 2.20-SNAPSHOT (no access to staging at production build)

encountered a couple  of failing tests (*Tests.java) which started to run
due to

   - [SUREFIRE-1260 ]
   - Add **/*Tests.java as one of the default include patterns


Other than that,  looks good from me, thanks to putting lots of hard work
on this plugin

+1 non-binding

Thanks

-Dan

-an



On Sun, Apr 9, 2017 at 1:38 PM, Michael Osipov  wrote:

> +1 from me
>
>
> Am 2017-04-09 um 22:35 schrieb Tibor Digana:
>
>> We need to have two more votes.
>>
>> On Sat, Apr 8, 2017 at 11:40 PM, Andreas Gudian [via Maven] <
>> ml-node+s40175n5905323...@n5.nabble.com> wrote:
>>
>> +1
>>>
>>> Tested on a couple of projects, with Maven 3.3.9 and 3.5.0, on Win
>>> (binaries) and macOS (source build).
>>>
>>> Great job, Tibor!
>>>
>>>
>>> 2017-04-08 14:26 GMT+02:00 Petr Široký <[hidden email]
>>> >:
>>>
>>> +1 (non-binding)

 Tested on Fedora 25 + JDK 8u121 + Maven 3.5.0 with several large

>>> projects.
>>>
 No issue found.

 @Tibor, thanks for fixing all the issues I found previously!

 Petr

 On Sat, Apr 8, 2017 at 12:53 PM Tibor Digana <[hidden email]

>>> >
>>>
 wrote:

 Hi,
>
> We solved 70 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>
 projectId=12317927=12334636

>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/i#issues/?jql=project+%;>
>
 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-1330/
>
> https://repository.apache.org/content/repositories/maven-
>
 1330/org/apache/maven/surefire/surefire/2.20/surefire-2.20-
 source-release.

>>>
>>> zip

>
> Source release checksum(s):
> surefire-2.20-source-release.zip sha1:
> fda994228c52dcb581d8ce6d4664f84a29d78797
>
> Git tag:
>
> https://git-wip-us.apache.org/repos/asf?p=maven-surefire.
>
 git;a=commit;h=
>>>
 8c786523414018099b54a0868ae1bc3d64847411

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

>>>
>>> --
>>> If you reply to this email, your message will be added to the discussion
>>> below:
>>> http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-
>>> Surefire-Plugin-version-2-20-TAKE-3-tp5905201p5905323.html
>>> To start a new topic under Maven Developers, email
>>> ml-node+s40175n142166...@n5.nabble.com
>>> To unsubscribe from Maven Developers, click here
>>> >> acro=unsubscribe_by_code=142166=dGlib3JkaWdhbmFAYX
>>> BhY2hlLm9yZ3wxNDIxNjZ8LTI4OTQ5MjEwMg==>
>>> .
>>> NAML
>>> >> acro=macro_viewer=instant_html%21nabble%3Aemail.naml
>>> =nabble.naml.namespaces.BasicNamespace-nabble.view.web.
>>> template.NabbleNamespace-nabble.view.web.template.NodeNamesp
>>> ace=notify_subscribers%21nabble%3Aemail.
>>> naml-instant_emails%21nabble%3Aemail.naml-send_instant_
>>> email%21nabble%3Aemail.naml>
>>>
>>>
>>
>>
>>
>> --
>> View this message in context: http://maven.40175.n5.nabble.c
>> om/VOTE-Release-Apache-Maven-Surefire-Plugin-version-2-20-TA
>> KE-3-tp5905201p5905437.html
>> Sent from the Maven Developers mailing list archive at Nabble.com.
>>
>>
>
>
> -
> 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 - TAKE 2

2017-04-07 Thread Dan Tran
is 2.20-SNAPSHOT up to date? that is only quick way I can test

Thanks

-D

On Fri, Apr 7, 2017 at 2:03 PM, Tibor Digana 
wrote:

> @Petr
> Both issues are fixed now. Would you please verify this version from
> master? I tested on my side.
>
> On Fri, Apr 7, 2017 at 3:42 PM, Petr Široký  wrote:
>
> > I'try to take a look. However, I have no prior experience with jUnit or
> > surefire sources, so it might take a while until I have something.
> >
> > Thanks,
> > Petr
> >
> > On Fri, Apr 7, 2017 at 2:22 PM Tibor Digana  >
> > wrote:
> >
> > > Good point. The PING chcking should be disabled when JMX observes debug
> > > mode.
> > > See implementation in JUnit sources. The same is there.
> > > Can you open pull request with a fix?
> > >
> > > On Fri, Apr 7, 2017 at 11:06 AM, Petr Široký 
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > thanks for the fast turnaround.
> > > >
> > > > I am afraid I've hit another issue (or maybe misconfiguration?). I
> was
> > > > trying to use -Dmaven.surefire.debug in the following project:
> > > > https://github.com/psiroky/surefire-2.20-debug-reproducer
> > > >
> > > > $ mvn clean install -s settings.xml -Dmaven.surefire.debug
> > > >
> > > > The surefire stops the execution and waits for the remote connection
> on
> > > the
> > > > default port 5005. However, I see this warning:
> > > > [WARNING] Corrupted stdin stream in forked JVM 2. See the dump file
> > > > /home/psiroky/tmp/surefire-2.20-debug/target/surefire-
> > > > reports/2017-04-07T11-00-40_341-jvmRun2.dumpstream
> > > >
> > > > Also, once I disconnect the remote debugger, the build fails with
> > > > "ExecutionException The forked VM terminated without properly saying
> > > > goodbye. VM crash or System.exit called?"
> > > > See the full build.log in the above git repo. I've also included the
> > > > '.dumpstream' file.
> > > >
> > > > Petr
> > > >
> > > >
> > > > On Thu, Apr 6, 2017 at 7:56 AM Tibor Digana 
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > We solved 68 issues:
> > > > >
> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > projectId=12317927=12334636
> > > > >
> > > > > 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-1329/
> > > > >
> > > > > https://repository.apache.org/content/repositories/maven-
> > > >
> > > 1329/org/apache/maven/surefire/surefire/2.20/
> > surefire-2.20-source-release.
> > > > zip
> > > > >
> > > > > Source release checksum(s):
> > > > > surefire-2.20-source-release.zip sha1:
> > > > > d76d172588f6ab1ada16db9155b464ffeefffc9b
> > > > >
> > > > > Git tag:
> > > > >
> > > > >
> > > https://git-wip-us.apache.org/repos/asf?p=maven-surefire.
> git;a=commit;h=
> > > > b5cbc6b2822e9eb60c703d46f1d2ed82126909ed
> > > > >
> > > > > 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
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Cheers
> > > Tibor
> > >
> >
>
>
>
> --
> Cheers
> Tibor
>


Re: [VOTE] Release Maven Wagon version 2.12

2017-01-29 Thread Dan Tran
+0

this release works at my side, however

the Http HugeFileDownloadTest almost double between 2.11  (dropped) and
2.12.  162 sec versus 301 sec

on my virtual Centos 7 4CPU, OpenJDK 7

Sorry about late response

May want to have  an explanation for the discrepancy before release

Thanks

-Dan




On Sun, Jan 29, 2017 at 3:01 PM, Olivier Lamy  wrote:

> +1
>
> On 28 January 2017 at 00:17, Michael Osipov  wrote:
>
> > Hi,
> >
> > We solved 28 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > ctId=12318122=12338924
> >
> > There are still a couple of issues left in JIRA:
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%
> > 20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
> > 20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1321/
> > https://repository.apache.org/content/repositories/maven-132
> > 1/org/apache/maven/wagon/wagon/2.12/wagon-2.12-source-release.zip
> >
> > Source release checksum(s):
> > wagon-2.12-source-release.zip sha1: bc948e4a8e56d59b2176892df4ce0f
> > 292a461334
> >
> > Staging site:
> > https://maven.apache.org/wagon-archives/wagon-LATEST/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>


Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

2017-01-08 Thread Dan Tran
+1 (Committer)

Special thanks for pulling all these together

-D

On Sun, Jan 8, 2017 at 1:05 PM, Olivier Lamy  wrote:

> +1
>
> On Sun, 8 Jan 2017 at 6:40 pm, Karl Heinz Marbaise 
> wrote:
>
> > Hi,
> >
> >
> >
> > +1 (PMC + Committer)
> >
> >
> >
> > Kind regards
> >
> > Karl Heinz Marbaise
> >
> >
> >
> > On 08/01/17 05:48, Tibor Digana wrote:
> >
> > > +1
> >
> > >
> >
> > > On Wed, Jan 4, 2017 at 1:16 PM, Stephen Connolly <
> >
> > > stephen.alan.conno...@gmail.com> wrote:
> >
> > >
> >
> > >> Hi,
> >
> > >>
> >
> > >> We have collectively managed to mess up our ability to follow the
> > original
> >
> > >> release plan for 3.4.0 which was originally supposed to consist of an
> >
> > >> effective no-op change of Eclipse's Aether for the code after
> migration
> > to
> >
> > >> Apache's Maven Resolver plus some other orthogonal changes around
> > logging
> >
> > >> colourization and launcher script bug fixes.
> >
> > >>
> >
> > >> Given that some developer private builds of the current master branch
> > have
> >
> > >> been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have
> > been
> >
> > >> closed with a fixed version of 3.4.0.
> >
> > >>
> >
> > >> For us to release a 3.4.0 with those fixes reverted, could cause
> > confusion
> >
> > >> with our user community.
> >
> > >>
> >
> > >> Additionally the informal practice of keeping existing integration
> > tests as
> >
> > >> RTC has not been followed, leading to some people to question whether
> > the
> >
> > >> integration tests remain valid.
> >
> > >>
> >
> > >> For all the above reasons it is proposed to do *all* the following as
> an
> >
> > >> whole:
> >
> > >>
> >
> > >> 1. In git://git.apache.org/maven.git we will rename the current
> master
> >
> > >> branch to `pre-reset-master` and recreate `master`
> >
> > >> as bce33aa2662a51d18cb00347cf2fb174dc195fb1 (
> >
> > >> https://github.com/apache/maven/commit/bce33aa2662a51d18cb00347cf2fb1
> >
> > >> 74dc195fb1
> >
> > >> )
> >
> > >>
> >
> > >> 2. In git://git.apache.org/maven-integration-testing.git we will
> rename
> >
> > >> the
> >
> > >> current master branch to `pre-reset-master` and recreate `master`
> >
> > >> as f31241ad6cb6474e559289f1bd7110ea5d5a4fba (
> >
> > >> https://github.com/apache/maven-integration-testing/commit/
> >
> > >> f31241ad6cb6474e559289f1bd7110ea5d5a4fba
> >
> > >> )
> >
> > >>
> >
> > >> 3. In git://git.apache.org/maven-resolver.git we will rename the
> > current
> >
> > >> master branch to `pre-reset-master` and recreate `master`
> >
> > >> as b74f7a1e8837875b4780199f644119f55d22465d (
> >
> > >> https://github.com/apache/maven-resolver/commit/
> >
> > >> b74f7a1e8837875b4780199f644119f55d22465d),
> >
> > >> i.e. the 1.0.x branch
> >
> > >>
> >
> > >> We will then proceed to have (ideally) the original committers
> > cherry-pick
> >
> > >> (and tidy up an squash... if the original committers are not able to
> > assist
> >
> > >> then squashing may not be practicable) those changes that have been
> > agreed
> >
> > >> for 3.5.0 as summarized on the
> >
> > >> https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki
> > page
> >
> > >> (authorative source of the decisions summarized in the wiki page is
> the
> >
> > >> mail thread:
> >
> > >> https://mail-archives.apache.org/mod_mbox/maven-dev/201612.
> mbox/%3CCA%
> >
> > >> 2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com
> %3E
> >
> > >>  ).
> >
> > >>
> >
> > >> As this involves a --force push on the `master` branch, we want to get
> > the
> >
> > >> approval of the committers before continuing.
> >
> > >>
> >
> > >> The vote will be open for at least 72 hours.
> >
> > >>
> >
> > >> The vote will be decided by a simple majority of valid votes cast.
> > There is
> >
> > >> no veto.
> >
> > >>
> >
> > >> The vote is open to all committers.
> >
> > >>
> >
> > >> In addition, for the vote to be valid, there must be at least 3x+1
> votes
> >
> > >> from PMC members
> >
> > >>
> >
> > >> [ ] +1: Yes
> >
> > >> [ ] 0:
> >
> > >> [ ] -1: No
> >
> > >>
> >
> > >> -Stephen
> >
> > >> --
> >
> > >> Sent from my phone
> >
> > >>
> >
> >
> >
> > -
> >
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
> >
> >
>


[Wagon] http-provider suite is longer by 3 minutes

2017-01-04 Thread Dan Tran
Hi,

before the canceled wagon-1.11 the suite was about 6minutes, now it is 9
min on my virtualbox centos 7,  jdk 7

Is it  a concern?

Thanks

-Dan

PS the good thing the huge http test no longer timeout on my box


Re: Re: [VOTE] Releasing Wagon 2.11 - Cancel

2017-01-04 Thread Dan Tran
I would vote for 2.11.1 same practice at maven core


-Dan

On Wed, Jan 4, 2017 at 1:22 AM, Michael Osipov <1983-01...@gmx.net> wrote:

> If so, I would drop 2.11 altogether and go with 2.12.
>
> > Gesendet: Mittwoch, 04. Januar 2017 um 08:47 Uhr
> > Von: "Hervé BOUTEMY" <herve.bout...@free.fr>
> > An: "Maven Developers List" <dev@maven.apache.org>
> > Betreff: Re: [VOTE] Releasing Wagon 2.11 - Cancel
> >
> > on git, AFAIK, going to 2.11.1 seems the best practice (removing tag in
> origin
> > repo is not reliable given people who have copied it won't have it
> removed
> > automatically)
> >
> > Regards,
> >
> > Hervé
> >
> > Le mardi 3 janvier 2017, 18:59:15 CET Dan Tran a écrit :
> > > I reverted the poms back to 2.11-SNAPSHOT not keep the tag for now
> since
> > > some ppl may object removing remote history.
> > >
> > > so we can keep the tag and move to 2.11.1-SNAPSHOT or remove
> wagon-2.11 tag
> > > and move on
> > >
> > > -Dan
> > >
> > > On Tue, Jan 3, 2017 at 6:08 PM, Dan Tran <dant...@gmail.com> wrote:
> > > > yes I can.  so it is ok to remove the tag?
> > > >
> > > > -D
> > > >
> > > > On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov <micha...@apache.org>
> > > >
> > > > wrote:
> > > >> Am 2016-12-28 um 19:46 schrieb Dan Tran:
> > > >>> Hi
> > > >>>
> > > >>> I am going to cancel this vote due to inconsistent test failure at
> > > >>> wagon-http provider on huge download test.
> > > >>
> > > >> Can you please rollback release commits in the repo?
> > > >>
> > > >> Michael
> > > >>
> > > >> On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov <mosi...@gmx.de>
> wrote:
> > > >>> Am 2016-12-28 um 06:05 schrieb Dan Tran:
> > > >>>> i still see the same timeout error on the jetty8 branch. No issue
> at
> > > >>>>
> > > >>>>> master
> > > >>>>>
> > > >>>>> [ERROR] Failed to execute goal
> > > >>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
> > > >>>>> (default-test) on project wagon-http: There was a timeout or
> other
> > > >>>>> error in the fork -> [Help
> > > >>>>> 1]org.apache.maven.lifecycle.LifecycleExecutionException:
> Failed to
> > > >>>>> execute goal org.apache.maven.plugins:maven
> > > >>>>> -surefire-plugin:2.18.1:test
> > > >>>>> (default-test) on project wagon-http: There was a timeout or
> other
> > > >>>>> error in the fork
> > > >>>>>
> > > >>>>> at org.apache.maven.lifecycle.int
> > > >>>>>
> > > >>>>> ernal.MojoExecutor.execute(Moj
> > > >>>>> oExecutor.java:212)
> > > >>>>
> > > >>>> I have now extended tests to other Linux distros:
> > > >>>>
> > > >>>> Fedora 25, 64 bit:
> > > >>>> OpenJDK 8 Update 111: pass
> > > >>>>
> > > >>>> CentOS 7, 64 bit:
> > > >>>> OpenJDK 8 Update 111: pass
> > > >>>> OpenJDK 7 Update 121: pass*
> > > >>>>
> > > >>>> *This is actually your combo which works for me, but not for
> you...
> > > >>>>
> > > >>>> Additionally, I added this version to Maven 3.4.0-SNAPSHOT and
> ran ITs
> > > >>>> on
> > > >>>> Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> Michael
> > > >>>>
> > > >>>> 
> -
> > > >>>> 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
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Releasing Wagon 2.11 - Cancel

2017-01-03 Thread Dan Tran
I reverted the poms back to 2.11-SNAPSHOT not keep the tag for now since
some ppl may object removing remote history.

so we can keep the tag and move to 2.11.1-SNAPSHOT or remove wagon-2.11 tag
and move on

-Dan

On Tue, Jan 3, 2017 at 6:08 PM, Dan Tran <dant...@gmail.com> wrote:

> yes I can.  so it is ok to remove the tag?
>
> -D
>
> On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov <micha...@apache.org>
> wrote:
>
>> Am 2016-12-28 um 19:46 schrieb Dan Tran:
>>
>>> Hi
>>>
>>> I am going to cancel this vote due to inconsistent test failure at
>>> wagon-http provider on huge download test.
>>>
>>
>> Can you please rollback release commits in the repo?
>>
>> Michael
>>
>>
>> On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov <mosi...@gmx.de> wrote:
>>>
>>> Am 2016-12-28 um 06:05 schrieb Dan Tran:
>>>>
>>>> i still see the same timeout error on the jetty8 branch. No issue at
>>>>> master
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
>>>>> (default-test) on project wagon-http: There was a timeout or other
>>>>> error in the fork -> [Help
>>>>> 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>> execute goal org.apache.maven.plugins:maven
>>>>> -surefire-plugin:2.18.1:test
>>>>> (default-test) on project wagon-http: There was a timeout or other
>>>>> error in the fork
>>>>> at org.apache.maven.lifecycle.int
>>>>> ernal.MojoExecutor.execute(Moj
>>>>> oExecutor.java:212)
>>>>>
>>>>>
>>>> I have now extended tests to other Linux distros:
>>>>
>>>> Fedora 25, 64 bit:
>>>> OpenJDK 8 Update 111: pass
>>>>
>>>> CentOS 7, 64 bit:
>>>> OpenJDK 8 Update 111: pass
>>>> OpenJDK 7 Update 121: pass*
>>>>
>>>> *This is actually your combo which works for me, but not for you...
>>>>
>>>> Additionally, I added this version to Maven 3.4.0-SNAPSHOT and ran ITs
>>>> on
>>>> Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.
>>>>
>>>>
>>>>
>>>> Michael
>>>>
>>>> -
>>>> 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] Releasing Wagon 2.11 - Cancel

2017-01-03 Thread Dan Tran
yes I can.  so it is ok to remove the tag?

-D

On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov <micha...@apache.org> wrote:

> Am 2016-12-28 um 19:46 schrieb Dan Tran:
>
>> Hi
>>
>> I am going to cancel this vote due to inconsistent test failure at
>> wagon-http provider on huge download test.
>>
>
> Can you please rollback release commits in the repo?
>
> Michael
>
>
> On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov <mosi...@gmx.de> wrote:
>>
>> Am 2016-12-28 um 06:05 schrieb Dan Tran:
>>>
>>> i still see the same timeout error on the jetty8 branch. No issue at
>>>> master
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
>>>> (default-test) on project wagon-http: There was a timeout or other
>>>> error in the fork -> [Help
>>>> 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>> execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
>>>> (default-test) on project wagon-http: There was a timeout or other
>>>> error in the fork
>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>>> oExecutor.java:212)
>>>>
>>>>
>>> I have now extended tests to other Linux distros:
>>>
>>> Fedora 25, 64 bit:
>>> OpenJDK 8 Update 111: pass
>>>
>>> CentOS 7, 64 bit:
>>> OpenJDK 8 Update 111: pass
>>> OpenJDK 7 Update 121: pass*
>>>
>>> *This is actually your combo which works for me, but not for you...
>>>
>>> Additionally, I added this version to Maven 3.4.0-SNAPSHOT and ran ITs on
>>> Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.
>>>
>>>
>>>
>>> Michael
>>>
>>> -
>>> 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: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

2016-12-31 Thread Dan Tran
I would like to add MNG-6084   WONTFIX   Support JSR 250 @PreDestory and
@PostContruct


On Sat, Dec 31, 2016 at 5:17 PM, Michael Osipov  wrote:

> Am 2017-01-01 um 02:11 schrieb Anton Tanasenko:
>
>> FIX-3.5.0:
>> MNG-   WONTFIX  Add a ProjectArtifactsCache similar to
>> PluginArtifactsCache
>> That's actually a https://issues.apache.org/jira/browse/MNG-6025
>>
>
> JIRA adjusted, thank you. Stephen, please update your list with MNG-6025.
>
>
> 2017-01-01 2:55 GMT+02:00 Michael Osipov :
>>
>> I just went through the list my issues. Here is a safe list I would
>>> merge/cherry-pick into new master:
>>>
>>> FIX-3.5.0: MNG-5457, MNG-5567, MNG-5579, MNG-5607, MNG-5815, MNG-5954,
>>> MNG-5963, MNG-5975, MNG-5977, MNG-6001, MNG-6003, MNG-6029, MNG-6081,
>>> MNG-6102, MNG-6106, MNG-6115, MNG-6136, MNG-6137, MNG-6138
>>>
>>> To be transfered to someone else:
>>> MNG-6043 can be merged into Hervé's MNG-3507.
>>>
>>> Without issue id FIX-3.5.0:
>>> MNG-   WONTFIX  Added some docs in CLIReporting Utils
>>> NONERemove trailing whitespace
>>> MNG-   WONTFIX  Pass force=true to DefaultWagonManagerTest
>>> #testGetMissingJarForced()
>>> NONEFix checkstyle error
>>> NONEUse static final values instead of literals
>>> NONERemove non-existent m2 include in
>>> component.xml
>>> NONELanguage style improvements for commit
>>> 5dab4940c9a7d3b362bd2a8b078b183e4eb521bb
>>> MNG-   WONTFIX  Update Maven Dependency Plugin in Super POM
>>> to 2.10
>>> MNG-   WONTFIX  Removing redundant test
>>> MNG-   WONTFIX  Work around a rounding bug existed upto
>>> Java 7
>>> MNG-   WONTFIX  Remove ancient Subversion keywords
>>> MNG-   WONTFIX  Use the proper term for char U+002D (-)
>>> hyphen(-minus) instead of dash
>>>
>>> Some of them will be squashed into into closely related commits, will
>>> have
>>> tickets created or are so trivial that they will be applied directly.
>>>
>>> Drop: MNG-5976
>>>
>>> Undecided:
>>> MNG-5708: fixed by Christian's work
>>> MNG-6049: Maybe for Christian, I just pulled PR and IT
>>>
>>> Michael
>>>
>>>
>>>
>>> -
>>> 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] Releasing Wagon 2.11 - Cancel

2016-12-28 Thread Dan Tran
Hi

I am going to cancel this vote due to inconsistent test failure at
wagon-http provider on huge download test.

Thanks

-Dan

On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov <mosi...@gmx.de> wrote:

> Am 2016-12-28 um 06:05 schrieb Dan Tran:
>
>> i still see the same timeout error on the jetty8 branch. No issue at
>> master
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
>> (default-test) on project wagon-http: There was a timeout or other
>> error in the fork -> [Help
>> 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
>> (default-test) on project wagon-http: There was a timeout or other
>> error in the fork
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:212)
>>
>
> I have now extended tests to other Linux distros:
>
> Fedora 25, 64 bit:
> OpenJDK 8 Update 111: pass
>
> CentOS 7, 64 bit:
> OpenJDK 8 Update 111: pass
> OpenJDK 7 Update 121: pass*
>
> *This is actually your combo which works for me, but not for you...
>
> Additionally, I added this version to Maven 3.4.0-SNAPSHOT and ran ITs on
> Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.
>
>
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [1/2] maven-wagon git commit: [WAGON-474] Upgrade and revise all tests for Jetty 8

2016-12-28 Thread Dan Tran
strange, i placed your recommended logger settings
under systemPropertyVariables

and see no log for the timeout issue

Anyway I am going to cancel the vote and have to roll it again

Thanks

-Dan

On Wed, Dec 28, 2016 at 6:18 AM, Michael Osipov  wrote:

> Am 2016-12-28 um 15:07 schrieb Olivier Lamy:
>
>> 2017 is in few days so maybe java 1.7 shouldn't be a big problem
>>
>
> While this is correct, I don't want to change 10 things at once. At last,
> if no one changes the code to 1.7, there won't be any benefit. I'd move
> this for n+1 release.
>
> Michael
>
> On Wed, 28 Dec 2016 at 11:09 am, Michael Osipov 
>> wrote:
>>
>> Am 2016-12-28 um 08:54 schrieb Olivier Lamy:
>>
>> Hi
>>>
>>
>> What about at least Jetty 9.2? (8.x is not anymore supported)
>>>
>>
>>
>>
>> Wagon is still Java 1.6, therefore I had to stick to Jetty 8.
>>
>> Moving from 8 to 9 is easier than from 6 to 9.
>>
>>
>>
>> See:
>>
>> https://www.eclipse.org/jetty/documentation/9.3.x/what-jetty-version.html
>>
>>
>>
>> On 26 December 2016 at 10:58,  wrote:
>>>
>>
>>
>>>
>> Repository: maven-wagon

>>>
>> Updated Branches:

>>>
>>   refs/heads/jetty-8 [created] e707a2691

>>>
>>

>>

>> [WAGON-474] Upgrade and revise all tests for Jetty 8

>>>
>>

>> * Upgrade all test code to Jetty 8.1.22 and Servlet 3.0

>>>
>> * Unify variable names in redirect usecases to realServer and

>>>
>>   redirectServer

>>>
>> * RedirectHandler: redirect code is passed but completely ignored because

>>>
>>   sendRedirect() always sends 302

>>>
>> * Chronologically sort checkHandlerResult() calls

>>>
>> ** Set redirect code (See Other (303)) as requested

>>>
>> ** Update checkHandlerResult() for requested status codes rather sent

>>>
>>chosen by server (mismatched previously)

>>>
>> * testPreemptiveAuthentication*(): properly check for OK for GET and

>>>
>>   CREATED for PUT instead of OK only for both

>>>
>> * WebDavWagonTest: replace status code literal for

>>>
>>   HttpServletResponse.SC_* for better readability

>>>
>> * testRedirect*(): add more checkHandlerResults

>>>
>>

>>

>> Project: http://git-wip-us.apache.org/repos/asf/maven-wagon/repo

>>>
>> Commit:

>>> http://git-wip-us.apache.org/repos/asf/maven-wagon/commit/2e1c807e
>>
>> Tree: http://git-wip-us.apache.org/repos/asf/maven-wagon/tree/2e1c807e

>>>
>> Diff: http://git-wip-us.apache.org/repos/asf/maven-wagon/diff/2e1c807e

>>>
>>

>> Branch: refs/heads/jetty-8

>>>
>> Commit: 2e1c807e5345a1999376771f8b378b8cd3328fee

>>>
>> Parents: b451e41

>>>
>> Author: Michael Osipov 

>>>
>> Authored: Mon Dec 26 00:55:09 2016 +0100

>>>
>> Committer: Michael Osipov 

>>>
>> Committed: Mon Dec 26 00:55:09 2016 +0100

>>>
>>

>> --

>>>
>>  pom.xml |  14 +-

>>>
>>  wagon-provider-test/pom.xml |   8 +-

>>>
>>  .../maven/wagon/http/HttpWagonTestCase.java | 273

>>> ++-
>>
>>  wagon-providers/wagon-http-lightweight/pom.xml  |   4 +-

>>>
>>  .../http/LightweightHttpsWagonTest.java |   6 +-

>>>
>>  wagon-providers/wagon-http/pom.xml  |   8 +-

>>>
>>  .../http/HttpWagonHttpServerTestCase.java   |  14 +-

>>>
>>  .../http/HttpWagonReasonPhraseTest.java |   2 +-

>>>
>>  .../providers/http/HttpWagonTimeoutTest.java|   2 +-

>>>
>>  .../http/HttpsWagonPreemptiveTest.java  |   6 +-

>>>
>>  .../wagon/providers/http/HttpsWagonTest.java|   6 +-

>>>
>>  .../providers/http/HugeFileDownloadTest.java|  14 +-

>>>
>>  wagon-providers/wagon-ssh/pom.xml   |   8 +-

>>>
>>  .../ssh/jsch/ScpWagonWithProxyTest.java |  16 +-

>>>
>>  wagon-providers/wagon-webdav-jackrabbit/pom.xml |   8 +-

>>>
>>  .../wagon/providers/webdav/WebDavWagonTest.java |  73 ++---

>>>
>>  .../providers/webdav/WebDavsWagonTest.java  |   6 +-

>>>
>>  wagon-tcks/wagon-tck-http/pom.xml   |  12 +-

>>>
>>  .../wagon/tck/http/fixture/ServerFixture.java   |  52 ++--

>>>
>>  19 files changed, 278 insertions(+), 254 deletions(-)

>>>
>> --

>>>
>>

>>

>> http://git-wip-us.apache.org/repos/asf/maven-wagon/blob/2e1c807e/pom.xml

>>>
>> --

>>>
>> diff --git a/pom.xml b/pom.xml

>>>
>> index e127da4..a90a1ba 100644

>>>
>> --- a/pom.xml

>>>
>> +++ b/pom.xml

>>>
>> @@ -313,14 +313,14 @@ under the License.

>>>
>>

>>>
>>

>>

>>>
>> -org.mortbay.jetty

>>>
>> -

Re: [VOTE] Releasing Wagon 2.11

2016-12-27 Thread Dan Tran
i still see the same timeout error on the jetty8 branch. No issue at master

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
(default-test) on project wagon-http: There was a timeout or other
error in the fork -> [Help
1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
(default-test) on project wagon-http: There was a timeout or other
error in the fork
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)



It is your call now. since I cant release it

-Dan

On Tue, Dec 27, 2016 at 5:05 PM, Michael Osipov <micha...@apache.org> wrote:

> Hi Dan,
>
> Am 2016-12-25 um 19:51 schrieb Dan Tran:
>
>> Just want to confirm,  your FreeBSD and build.apache.org's ubuntu see the
>> same test failure??
>>
>> Do you think we should cancel the vote and wait for your fix?
>>
>
> I was finally able to complete my coding and testings. After several hours
> of testing and debugging, I've found the reasons why several tests were
> failing sporadically, some were bad test conditions (testSecuredGet(),
> testSecuredGetToStream()) and some rooted in bugs in HttpWagon. I'll go in
> detail:
>
> 1. Flaky testSecuredGet(ToStream):
> This failed once in a while due to race conditions between Jetty's qtp
> threads and the main thread running the tests and the assertions. Jetty did
> not fully complete the process chain while Surefire continued to verify the
> result. This yielded to: expected <2> requests found <1> and so forth. I
> added a simple sleep() and it did work. I avoided to have complex sync code
> with CountDownLatch or alike. Some logging added to the code shows the
> following in Surefire's XML output:
>
> 
>>
>
> now the logging:
>
> > [main] DEBUG org.apache.http.impl.conn.DefaultManagedHttpClientConnection
>> - http-outgoing-86: set socket timeout to 180
>> [main] DEBUG org.apache.http.impl.execchain.MainClientExec - Executing
>> request GET /test-secured-resource HTTP/1.1
>> [main] DEBUG org.apache.http.impl.execchain.MainClientExec - Target auth
>> state: CHALLENGED
>> [main] DEBUG org.apache.http.impl.auth.HttpAuthenticator - Generating
>> response to an authentication challenge using basic scheme
>> [main] DEBUG org.apache.http.impl.execchain.MainClientExec - Proxy auth
>> state: UNCHALLENGED
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >> GET
>> /test-secured-resource HTTP/1.1
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >> Cache-control:
>> no-cache
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >> Cache-store:
>> no-store
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >> Pragma:
>> no-cache
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >> Expires: 0
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >>
>> Accept-Encoding: gzip
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >> Host:
>> localhost:45658
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >> Connection:
>> Keep-Alive
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >> User-Agent:
>> Apache-HttpClient/4.5.2 (Java/1.7.0_111)
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 >> Authorization:
>> Basic dXNlcjpzZWNyZXQ=
>> org.apache.maven.wagon.http.HttpWagonTestCase$TestSecurityHandler@9187167
>> (count 1): handled GET /test-secured-resource with status 401
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 << HTTP/1.1 200 OK
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 << Accept-Ranges:
>> bytes
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 <<
>> Content-Length: 10
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 << Last-Modified:
>> Mon, 26 Dec 2016 23:07:55 GMT
>> [main] DEBUG org.apache.http.headers - http-outgoing-86 << Server:
>> Jetty(8.1.22.v20160922)
>> [main] DEBUG org.apache.http.impl.execchain.MainClientExec - Connection
>> can be kept alive indefinitely
>> [main] DEBUG org.apache.http.impl.auth.HttpAuthenticator -
>> Authentication succeeded
>> [main] DEBUG org.apache.http.impl.client.TargetAuthenticationStrategy -
>> Caching 'basic' auth scheme for http://localhost:45658
>> [main] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager
>> - Connection [id: 86][route: {}->http://localhost:45658] can be kept
>> alive indefinitely
>> [main] DEBUG org.apache.http.impl.conn.PoolingHttpClient

Re: [1/2] maven-wagon git commit: [WAGON-474] Upgrade and revise all tests for Jetty 8

2016-12-25 Thread Dan Tran
redhat7/openjdk 7 ( latest)

this test fails on timeout.  I have seen this issue before not lately. Used
to work on  2.9, 2 10, and 2.11)

-D

On Sun, Dec 25, 2016 at 4:59 PM, Michael Osipov <micha...@apache.org> wrote:

> Am 2016-12-26 um 01:45 schrieb Dan Tran:
>
>> this branch has one test consistently fail test on my local redhat 7,
>> java 7
>>
>> Running org.apache.maven.wagon.providers.http.HugeFileDownloadTest
>>
>
> What does it say? What JDK version do you use?
>
> This test works for me on two operating systems and five JDK versions.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [1/2] maven-wagon git commit: [WAGON-474] Upgrade and revise all tests for Jetty 8

2016-12-25 Thread Dan Tran
this branch has one test consistently fail test on my local redhat 7, java 7

Running org.apache.maven.wagon.providers.http.HugeFileDownloadTest




On Sun, Dec 25, 2016 at 3:58 PM,  wrote:

> Repository: maven-wagon
> Updated Branches:
>   refs/heads/jetty-8 [created] e707a2691
>
>
> [WAGON-474] Upgrade and revise all tests for Jetty 8
>
> * Upgrade all test code to Jetty 8.1.22 and Servlet 3.0
> * Unify variable names in redirect usecases to realServer and
>   redirectServer
> * RedirectHandler: redirect code is passed but completely ignored because
>   sendRedirect() always sends 302
> * Chronologically sort checkHandlerResult() calls
> ** Set redirect code (See Other (303)) as requested
> ** Update checkHandlerResult() for requested status codes rather sent
>chosen by server (mismatched previously)
> * testPreemptiveAuthentication*(): properly check for OK for GET and
>   CREATED for PUT instead of OK only for both
> * WebDavWagonTest: replace status code literal for
>   HttpServletResponse.SC_* for better readability
> * testRedirect*(): add more checkHandlerResults
>
>
> Project: http://git-wip-us.apache.org/repos/asf/maven-wagon/repo
> Commit: http://git-wip-us.apache.org/repos/asf/maven-wagon/commit/2e1c807e
> Tree: http://git-wip-us.apache.org/repos/asf/maven-wagon/tree/2e1c807e
> Diff: http://git-wip-us.apache.org/repos/asf/maven-wagon/diff/2e1c807e
>
> Branch: refs/heads/jetty-8
> Commit: 2e1c807e5345a1999376771f8b378b8cd3328fee
> Parents: b451e41
> Author: Michael Osipov 
> Authored: Mon Dec 26 00:55:09 2016 +0100
> Committer: Michael Osipov 
> Committed: Mon Dec 26 00:55:09 2016 +0100
>
> --
>  pom.xml |  14 +-
>  wagon-provider-test/pom.xml |   8 +-
>  .../maven/wagon/http/HttpWagonTestCase.java | 273 ++-
>  wagon-providers/wagon-http-lightweight/pom.xml  |   4 +-
>  .../http/LightweightHttpsWagonTest.java |   6 +-
>  wagon-providers/wagon-http/pom.xml  |   8 +-
>  .../http/HttpWagonHttpServerTestCase.java   |  14 +-
>  .../http/HttpWagonReasonPhraseTest.java |   2 +-
>  .../providers/http/HttpWagonTimeoutTest.java|   2 +-
>  .../http/HttpsWagonPreemptiveTest.java  |   6 +-
>  .../wagon/providers/http/HttpsWagonTest.java|   6 +-
>  .../providers/http/HugeFileDownloadTest.java|  14 +-
>  wagon-providers/wagon-ssh/pom.xml   |   8 +-
>  .../ssh/jsch/ScpWagonWithProxyTest.java |  16 +-
>  wagon-providers/wagon-webdav-jackrabbit/pom.xml |   8 +-
>  .../wagon/providers/webdav/WebDavWagonTest.java |  73 ++---
>  .../providers/webdav/WebDavsWagonTest.java  |   6 +-
>  wagon-tcks/wagon-tck-http/pom.xml   |  12 +-
>  .../wagon/tck/http/fixture/ServerFixture.java   |  52 ++--
>  19 files changed, 278 insertions(+), 254 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/maven-wagon/blob/2e1c807e/pom.xml
> --
> diff --git a/pom.xml b/pom.xml
> index e127da4..a90a1ba 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -313,14 +313,14 @@ under the License.
>
>
>
> -org.mortbay.jetty
> -jetty
> -6.1.26
> +org.eclipse.jetty.aggregate
> +jetty-all
> +8.1.22.v20160922
>
>
> -org.mortbay.jetty
> -servlet-api
> -2.5-20081211
> +javax.servlet
> +javax.servlet-api
> +3.0.1
>  
>  
>
> @@ -565,5 +565,5 @@ under the License.
>
>  
>
> -
> +
>  
>
> http://git-wip-us.apache.org/repos/asf/maven-wagon/blob/
> 2e1c807e/wagon-provider-test/pom.xml
> --
> diff --git a/wagon-provider-test/pom.xml b/wagon-provider-test/pom.xml
> index b19e7ac..9b0f4e5 100644
> --- a/wagon-provider-test/pom.xml
> +++ b/wagon-provider-test/pom.xml
> @@ -51,12 +51,12 @@ under the License.
>compile
>  
>  
> -  org.mortbay.jetty
> -  jetty
> +  org.eclipse.jetty.aggregate
> +  jetty-all
>  
>  
> -  org.mortbay.jetty
> -  servlet-api
> +  javax.servlet
> +  javax.servlet-api
>  
>  
>org.slf4j
>
> http://git-wip-us.apache.org/repos/asf/maven-wagon/blob/
> 2e1c807e/wagon-provider-test/src/main/java/org/apache/maven/wagon/http/
> HttpWagonTestCase.java
> --
> diff --git a/wagon-provider-test/src/main/java/org/apache/maven/
> wagon/http/HttpWagonTestCase.java b/wagon-provider-test/src/
> main/java/org/apache/maven/wagon/http/HttpWagonTestCase.java
> index dfc499e..cf479fd 100644
> --- a/wagon-provider-test/src/main/java/org/apache/maven/
> 

Re: maven-wagon git commit: [WAGON-471] Clean up dependency mess (reported by dependency:analyze)

2016-12-25 Thread Dan Tran
is it necessary to introduce


 org.slf4j
 slf4j-simple
 

as compile scope?

Thanks

-Dan

On Sun, Dec 25, 2016 at 12:10 PM,  wrote:

> Repository: maven-wagon
> Updated Branches:
>   refs/heads/master 4da2accfd -> b451e418e
>
>
> [WAGON-471] Clean up dependency mess (reported by dependency:analyze)
>
> Followup fix for SLF4J Simple in test scope for file, scm and
> http-lightweight.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/maven-wagon/repo
> Commit: http://git-wip-us.apache.org/repos/asf/maven-wagon/commit/b451e418
> Tree: http://git-wip-us.apache.org/repos/asf/maven-wagon/tree/b451e418
> Diff: http://git-wip-us.apache.org/repos/asf/maven-wagon/diff/b451e418
>
> Branch: refs/heads/master
> Commit: b451e418ed5235f231f5288fd21054f450669aa9
> Parents: 4da2acc
> Author: Michael Osipov 
> Authored: Sun Dec 25 21:09:43 2016 +0100
> Committer: Michael Osipov 
> Committed: Sun Dec 25 21:09:43 2016 +0100
>
> --
>  wagon-providers/wagon-file/pom.xml | 4 
>  wagon-providers/wagon-http-lightweight/pom.xml | 4 
>  wagon-providers/wagon-scm/pom.xml  | 4 
>  3 files changed, 12 insertions(+)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/maven-wagon/blob/
> b451e418/wagon-providers/wagon-file/pom.xml
> --
> diff --git a/wagon-providers/wagon-file/pom.xml
> b/wagon-providers/wagon-file/pom.xml
> index 4e3cb52..a96af63 100644
> --- a/wagon-providers/wagon-file/pom.xml
> +++ b/wagon-providers/wagon-file/pom.xml
> @@ -38,5 +38,9 @@ under the License.
>org.codehaus.plexus
>plexus-utils
>  
> +
> +  org.slf4j
> +  slf4j-simple
> +
>
>  
>
> http://git-wip-us.apache.org/repos/asf/maven-wagon/blob/
> b451e418/wagon-providers/wagon-http-lightweight/pom.xml
> --
> diff --git a/wagon-providers/wagon-http-lightweight/pom.xml
> b/wagon-providers/wagon-http-lightweight/pom.xml
> index 9a0e8c8..f723004 100644
> --- a/wagon-providers/wagon-http-lightweight/pom.xml
> +++ b/wagon-providers/wagon-http-lightweight/pom.xml
> @@ -64,5 +64,9 @@ under the License.
>jetty
>test
>  
> +
> +  org.slf4j
> +  slf4j-simple
> +
>
>  
>
> http://git-wip-us.apache.org/repos/asf/maven-wagon/blob/
> b451e418/wagon-providers/wagon-scm/pom.xml
> --
> diff --git a/wagon-providers/wagon-scm/pom.xml
> b/wagon-providers/wagon-scm/pom.xml
> index 55c14e6..881040a 100644
> --- a/wagon-providers/wagon-scm/pom.xml
> +++ b/wagon-providers/wagon-scm/pom.xml
> @@ -65,6 +65,10 @@ under the License.
>${mavenScmVersion}
>test
>  
> +
> +  org.slf4j
> +  slf4j-simple
> +
>
>
>
>
>


Re: [VOTE] Releasing Wagon 2.11

2016-12-25 Thread Dan Tran
Just want to confirm,  your FreeBSD and build.apache.org's ubuntu see the
same test failure??

Do you think we should cancel the vote and wait for your fix?

Thanks

-Dan

On Sun, Dec 25, 2016 at 10:34 AM, Michael Osipov <micha...@apache.org>
wrote:

> Am 2016-12-25 um 18:45 schrieb Dan Tran:
>
>> Thank Michael
>>
>>   * Test failures at windows are intermittent.  It is a known issue since
>> the last few versions
>>   * No issue at my local redhat 7/java7 build
>>   * I am seeing test failures at
>> https://builds.apache.org/view/All/job/maven-wagon/1323/starting with
>> your change for WAGON-472. Dont think it is related, could be from build
>> env
>>
>
> This is build env. I have tested Wagon on Windows and FreeBSD before any
> patching. Windows was fine, FreeBSD failed for those two cases. It also
> passed on Windows with OpenJDK 7 Update 121 from Azul Systems. Though, I
> have good news: I have been working on the unit tests in genereal the last
> two days by migrating to Jetty 8 (last Java 1.6 supported) version and
> found several bugs in Wagon HTTP Provider and the unit test setup itself. I
> will report them shortly.
>
> Michael
>
>
> On Sat, Dec 24, 2016 at 5:07 AM, Michael Osipov <micha...@apache.org>
>> wrote:
>>
>> Am 2016-12-24 um 04:07 schrieb Dan Tran:
>>>
>>> Hi,
>>>>
>>>> We have fixed 18 issues:
>>>> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
>>>> ectId=12318122=1296
>>>> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
>>>> ectId=12318122=1296>*
>>>>
>>>> There are still issues left in JIRA:
>>>> *https://issues.apache.org/jira/issues/?jql=project%20%3D%
>>>> 20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
>>>> 20created%20DESC%2C%20priority%20DESC
>>>> <https://issues.apache.org/jira/issues/?jql=project%20%3D%
>>>> 20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
>>>> 20created%20DESC%2C%20priority%20DESC>*
>>>>
>>>> Staging repository:
>>>> https://repository.apache.org/content/repositories/maven-1313
>>>> https://repository.apache.org/content/repositories/maven-
>>>> 1313/org/apache/maven/wagon/wagon/2.11/wagon-2.11-source-release.zip
>>>>
>>>> Source release checksum(s):
>>>> wagon-2.11-source-release.zip sha1: 98bc0b031880b175e144c55447a620
>>>> 00c58abfa5
>>>>
>>>> Staging site:
>>>> *http://maven.apache.org/components/wagon-archives/wagon-LATEST/
>>>> <http://maven.apache.org/components/wagon-archives/wagon-LATEST/>*
>>>>
>>>> Guide to testing staged releases:
>>>> https://maven.apache.org/guides/development/guide-testing-releases.html
>>>> <https://maven.apache.org/guides/development/guide-testing-
>>>> releases.html>
>>>> Vote open for 72H + 48H to accomodate for holidays
>>>>
>>>>
>>> +1
>>>
>>> SHA1 is fine, site is fine. Builds passes on Windows but constantly fails
>>> on non-Windows, here on my FreeBSD machine as well as on our Jenkins
>>> Ubuntu
>>> slave. It should probably investigated for the 3.0 release.
>>>
>>> Michael
>>>
>>>
>>>
>>>
>>> -
>>> 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] Releasing Wagon 2.11

2016-12-25 Thread Dan Tran
Thank Michael

  * Test failures at windows are intermittent.  It is a known issue since
the last few versions
  * No issue at my local redhat 7/java7 build
  * I am seeing test failures at
https://builds.apache.org/view/All/job/maven-wagon/1323/starting with
your change for WAGON-472. Dont think it is related, could be from build env


Thanks

On Sat, Dec 24, 2016 at 5:07 AM, Michael Osipov <micha...@apache.org> wrote:

> Am 2016-12-24 um 04:07 schrieb Dan Tran:
>
>> Hi,
>>
>> We have fixed 18 issues:
>> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
>> ectId=12318122=1296
>> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
>> ectId=12318122=1296>*
>>
>> There are still issues left in JIRA:
>> *https://issues.apache.org/jira/issues/?jql=project%20%3D%
>> 20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
>> 20created%20DESC%2C%20priority%20DESC
>> <https://issues.apache.org/jira/issues/?jql=project%20%3D%
>> 20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
>> 20created%20DESC%2C%20priority%20DESC>*
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/maven-1313
>> https://repository.apache.org/content/repositories/maven-
>> 1313/org/apache/maven/wagon/wagon/2.11/wagon-2.11-source-release.zip
>>
>> Source release checksum(s):
>> wagon-2.11-source-release.zip sha1: 98bc0b031880b175e144c55447a620
>> 00c58abfa5
>>
>> Staging site:
>> *http://maven.apache.org/components/wagon-archives/wagon-LATEST/
>> <http://maven.apache.org/components/wagon-archives/wagon-LATEST/>*
>>
>> Guide to testing staged releases:
>> https://maven.apache.org/guides/development/guide-testing-releases.html
>> <https://maven.apache.org/guides/development/guide-testing-releases.html>
>> Vote open for 72H + 48H to accomodate for holidays
>>
>
> +1
>
> SHA1 is fine, site is fine. Builds passes on Windows but constantly fails
> on non-Windows, here on my FreeBSD machine as well as on our Jenkins Ubuntu
> slave. It should probably investigated for the 3.0 release.
>
> Michael
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


[VOTE] Releasing Wagon 2.11

2016-12-23 Thread Dan Tran
Hi,

We have fixed 18 issues:
*https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=1296
*

There are still issues left in JIRA:
*https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created%20DESC%2C%20priority%20DESC
*

Staging repository:
https://repository.apache.org/content/repositories/maven-1313
https://repository.apache.org/content/repositories/maven-
1313/org/apache/maven/wagon/wagon/2.11/wagon-2.11-source-release.zip

Source release checksum(s):
wagon-2.11-source-release.zip sha1: 98bc0b031880b175e144c55447a62000c58abfa5

Staging site:
*http://maven.apache.org/components/wagon-archives/wagon-LATEST/
*

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

Vote open for 72H + 48H to accomodate for holidays

[+1]
[0]
[-1]

Thanks,

The Maven Team


Re: [HEADS UP] Releasing maven-wagon-2.11

2016-12-22 Thread Dan Tran
I am seeing this at my local build

testConnectNullRepository(org.apache.maven.wagon.AbstractWagonTest)
Time elapsed: 0.017 sec  <<< ERROR!
java.lang.NullPointerException: repository cannot be null
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:181)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:134)
at 
org.apache.maven.wagon.AbstractWagonTest.testConnectNullRepository(AbstractWagonTest.java:514)



must have something to do with

   1. [WAGON-473] Don't abuse IllegalArgumentException to intercept null
   input — michaelo <http://10.0.0.9:8080/user/michaelo/> / detail
   
<http://10.0.0.9:8080/view/wagon/job/wagon/job/maven-wagon/63/changes#30631655e8f6cdf121161b3ca09e3da0134a5198>


On Tue, Dec 20, 2016 at 12:38 PM, Michael Osipov <micha...@apache.org>
wrote:

> Am 2016-12-11 um 19:59 schrieb Dan Tran:
>
>> Hi
>>
>> I am planning to stage maven-wagon-2.11  tomorrow night US Pacific time.
>> Let me know if you need me to wait
>>
>
> Dan,
>
> you can start with your preperations. I have done my changes.
>
>
> Michael
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [HEADS UP] Releasing maven-wagon-2.11

2016-12-12 Thread Dan Tran
Sure

-Dan

On Mon, Dec 12, 2016 at 1:06 PM, Michael Osipov <micha...@apache.org> wrote:

> Am 2016-12-11 um 19:59 schrieb Dan Tran:
>
>> Hi
>>
>> I am planning to stage maven-wagon-2.11  tomorrow night US Pacific time.
>> Let me know if you need me to wait
>>
>
> Can you hold it for a week? I am currently investigating an issue with
> duplicate dependencies for the HTTP provider. At the end, several artifacts
> land in {maven.home}/lib twice.
>
> This is worth fixing in 2.11 for Maven 3.4.
>
> Thanks,
>
> Michael
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


[HEADS UP] Releasing maven-wagon-2.11

2016-12-11 Thread Dan Tran
Hi

I am planning to stage maven-wagon-2.11  tomorrow night US Pacific time.
Let me know if you need me to wait

Thanks

-Dan


Need help to fix jenkins build at https://builds.apache.org/job/maven-wagon-1.7/504/

2016-12-01 Thread Dan Tran
Looks like Jenkins does not like the provided maven

ERROR: Processing failed due to a bug in the code. Please report this
to jenkinsci-us...@googlegroups.comjava.lang.IllegalArgumentException
:
/home/jenkins/tools/maven/apache-maven-3.0.5 doesn't have a 'lib'
subdirectory - thus cannot be a valid maven installation!



Thanks

-Dan


Re: Maven Classloader issue at Wagon

2016-11-28 Thread Dan Tran
I went ahead to deploy the fix for user to try out


-Dan

On Sun, Nov 27, 2016 at 10:48 PM, Dan Tran <dant...@gmail.com> wrote:

> I got it working by switching
>
> componentConfigurator.configureComponent( wagon, plexusConf, 
> container.getContainerRealm()
> );
>
> for
>
> componentConfigurator.configureComponent( wagon, plexusConf,
> (ClassRealm)this.getClass().getClassLoader() );
>
> Thoughts?
>
> -Dan
>
> On Sun, Nov 27, 2016 at 9:34 PM, Dan Tran <dant...@gmail.com> wrote:
>
>>
>> I am interested fixing the long waited issue
>> https://issues.apache.org/jira/browse/WAGON-454 ( since introduction of
>> Maven 3)
>>
>> where  a wagon user can configure additional wagon provider configuration
>>  at maven settings
>>
>> It boils down to this line
>>
>> https://github.com/mojohaus/wagon-maven-plugin/blob/master/
>> src/main/java/org/codehaus/mojo/wagon/shared/DefaultWagon
>> Factory.java#L211
>>
>> where plexus not able load the desired class
>>
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostProvider
>> at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.
>> loadClass(SelfFirstStrategy.java:50)
>> at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchroni
>> zedLoadClass(ClassRealm.java:271)
>> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(
>> ClassRealm.java:247)
>> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(
>> ClassRealm.java:239)
>> at org.codehaus.plexus.component.configurator.converters.Abstra
>> ctConfigurationConverter.getClassForImplementatio
>> nHint(AbstractConfigurationConverter.java:121)
>>
>>
>> Advice is very much appreciated
>>
>> -Dan
>>
>>
>>
>


Re: Maven Classloader issue at Wagon

2016-11-27 Thread Dan Tran
I got it working by switching

componentConfigurator.configureComponent( wagon, plexusConf,
container.getContainerRealm()
);

for

componentConfigurator.configureComponent( wagon, plexusConf,
(ClassRealm)this.getClass().getClassLoader() );

Thoughts?

-Dan

On Sun, Nov 27, 2016 at 9:34 PM, Dan Tran <dant...@gmail.com> wrote:

>
> I am interested fixing the long waited issue https://issues.apache.org/
> jira/browse/WAGON-454 ( since introduction of Maven 3)
>
> where  a wagon user can configure additional wagon provider configuration
>  at maven settings
>
> It boils down to this line
>
> https://github.com/mojohaus/wagon-maven-plugin/blob/
> master/src/main/java/org/codehaus/mojo/wagon/shared/
> DefaultWagonFactory.java#L211
>
> where plexus not able load the desired class
>
> Caused by: java.lang.ClassNotFoundException: org.apache.maven.wagon.
> providers.ssh.knownhost.NullKnownHostProvider
> at org.codehaus.plexus.classworlds.strategy.
> SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.
> unsynchronizedLoadClass(ClassRealm.java:271)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.
> loadClass(ClassRealm.java:247)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.
> loadClass(ClassRealm.java:239)
> at org.codehaus.plexus.component.configurator.converters.
> AbstractConfigurationConverter.getClassForImplementatio
> nHint(AbstractConfigurationConverter.java:121)
>
>
> Advice is very much appreciated
>
> -Dan
>
>
>


Maven Classloader issue at Wagon

2016-11-27 Thread Dan Tran
I am interested fixing the long waited issue
https://issues.apache.org/jira/browse/WAGON-454 ( since introduction of
Maven 3)

where  a wagon user can configure additional wagon provider configuration
 at maven settings

It boils down to this line

https://github.com/mojohaus/wagon-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/wagon/shared/DefaultWagonFactory.java#L211

where plexus not able load the desired class

Caused by: java.lang.ClassNotFoundException:
org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostProvider
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at
org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.getClassForImplementatio
nHint(AbstractConfigurationConverter.java:121)


Advice is very much appreciated

-Dan


  1   2   3   4   5   6   7   8   9   >