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

[Olivier Lamy]

+1

On 18 July 2017 at 06:05, Robert Scholte  wrote:

> Hi,
>
> We solved 18 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12317529=12330875=Text
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%
> 2012317529%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%
> 20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1347
> https://repository.apache.org/content/repositories/maven-134
> 7/org/apache/maven/plugins/maven-javadoc-plugin/3.0.0-M1/mav
> en-javadoc-plugin-3.0.0-M1-source-release.zip
> Source release checksum(s):
> maven-javadoc-plugin-3.0.0-M1-source-release.zip  sha1:
> e12404f679e95e1d7f7e0526839a428d510d362d
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> NOTE: this is a milestone release, because there are still some open
> issues which need to be fixed before the official 3.0.0, e.g. replace some
> deprecated parameters.
> This release is mainly there to provide a Java9 compatible plugin (now it
> fails), even though not all Java 9 features are supported yet.
>
> [ ] +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: Maven Resolver

[Michael Osipov]

Am 2017-07-19 um 23:52 schrieb Manfred Moser:

Great.

https://issues.apache.org/jira/browse/MRESOLVER-28
https://issues.apache.org/jira/browse/MRESOLVER-29

Let me know if you want me to work on them.


Yes, please do so. I'd review the PRs.


Michael Osipov wrote on 2017-07-19 14:44:


Am 2017-07-19 um 23:39 schrieb Manfred Moser:

Hi all,

I found out that maven-resolver has main codebase, demos and ant
tasks as separate branches in the same repository. Anybody know why
this is the case instead of having three separate repositories? I
must have missed that in the discussions about pulling Aether in..

Related to that the demos and ant tasks still use 1.0.3 .. any
objections if I upgrade this to the latest 1.1.0 release?

Or should we even look at pulling the two branches into master as
additional modules? Or separate them out into different repositories?


Hi Manfred,

this is simply a time issue. I wasn't able to make it into 1.1.0. I my
opinion, I see no reason to have it as three repos, but simply as
modules of the regular reactor. The burden two release two more
components is too huge which I won't do.
You should simply file two JIRA issues to merge them into master as modules.

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

Re: Maven Resolver

[Manfred Moser]

Great.

https://issues.apache.org/jira/browse/MRESOLVER-28
https://issues.apache.org/jira/browse/MRESOLVER-29

Let me know if you want me to work on them.

Manfred

Michael Osipov wrote on 2017-07-19 14:44:

> Am 2017-07-19 um 23:39 schrieb Manfred Moser:
>> Hi all,
>>
>> I found out that maven-resolver has main codebase, demos and ant
>> tasks as separate branches in the same repository. Anybody know why
>> this is the case instead of having three separate repositories? I
>> must have missed that in the discussions about pulling Aether in..
>>
>> Related to that the demos and ant tasks still use 1.0.3 .. any
>> objections if I upgrade this to the latest 1.1.0 release?
>>
>> Or should we even look at pulling the two branches into master as
>> additional modules? Or separate them out into different repositories?
> 
> Hi Manfred,
> 
> this is simply a time issue. I wasn't able to make it into 1.1.0. I my 
> opinion, I see no reason to have it as three repos, but simply as 
> modules of the regular reactor. The burden two release two more 
> components is too huge which I won't do.
> You should simply file two JIRA issues to merge them into master as modules.
> 
> 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: Maven Resolver

[Michael Osipov]

Am 2017-07-19 um 23:39 schrieb Manfred Moser:

Hi all,

I found out that maven-resolver has main codebase, demos and ant
tasks as separate branches in the same repository. Anybody know why
this is the case instead of having three separate repositories? I
must have missed that in the discussions about pulling Aether in..

Related to that the demos and ant tasks still use 1.0.3 .. any
objections if I upgrade this to the latest 1.1.0 release?

Or should we even look at pulling the two branches into master as
additional modules? Or separate them out into different repositories?


Hi Manfred,

this is simply a time issue. I wasn't able to make it into 1.1.0. I my 
opinion, I see no reason to have it as three repos, but simply as 
modules of the regular reactor. The burden two release two more 
components is too huge which I won't do.

You should simply file two JIRA issues to merge them into master as modules.

Michael

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

Maven Resolver

[Manfred Moser]

Hi all,

I found out that maven-resolver has main codebase, demos and ant tasks as 
separate branches in the same repository. Anybody know why this is the case 
instead of having three separate repositories? I must have missed that in the 
discussions about pulling Aether in.. 

Related to that the demos and ant tasks still use 1.0.3 .. any objections if I 
upgrade this to the latest 1.1.0 release? 

Or should we even look at pulling the two branches into master as additional 
modules? Or separate them out into different repositories? 

manfred

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

Maven Resolver Provider, Repo Provisioner and 3.5.1

[Manfred Moser]

Hi all,

I moved my Maven Repository Provisioner to using Maven Resolver and 3.5.0 from 
Aether and 3.3.9 and have to say.. nice work on the migration. It essentially 
compiled after just changing a few dependencies!

I did run into an issue in the Maven Resolver Provider where a missing setter 
causes an NPE and found that Igor already fixed that in master.
Details are at https://github.com/simpligility/maven-repository-tools/pull/31

So now my questions is ... when is 3.5.1 planned for?

Manfred



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

Re: [VOTE] Release Apache Maven Invoker Plugin version 3.0.1 / Apache Maven Script Interpreter 1.2 (take 2)

[Guillaume Boué]

+1 from me too (non-binding)


Le 17/07/2017 à 13:08, Olivier Lamy a écrit :

Hi,
I'd like to release Apache Maven Invoker Plugin version 3.0.1 and Apache
Maven Script Interpreter 1.2.

We fixed 2 issues for Script interpreter:
https://s.apache.org/MSCRIPT-INTERPRETER-JIRA-1.2
We fixed 4 issues for Invoker plugin:
https://s.apache.org/MINVOKER-JIRA-3.0.1

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

Source releases:
*
https://repository.apache.org/content/repositories/maven-1346/org/apache/maven/plugins/maven-invoker-plugin/3.0.1/maven-invoker-plugin-3.0.1-source-release.zip
*
https://repository.apache.org/content/repositories/maven-1346/org/apache/maven/shared/maven-script-interpreter/1.2/maven-script-interpreter-1.2-source-release.zip

Staging sites:
http://maven.apache.org/components/plugins-archives/maven-invoker-plugin-LATEST/
http://maven.apache.org/components/shared-archives/maven-script-interpreter-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

My +1

Cheers



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus


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

Re: [VOTE] Release Apache Maven Invoker Plugin version 3.0.1 / Apache Maven Script Interpreter 1.2 (take 2)

[Robert Scholte]

+1

On Mon, 17 Jul 2017 13:08:55 +0200, Olivier Lamy  wrote:


Hi,
I'd like to release Apache Maven Invoker Plugin version 3.0.1 and Apache
Maven Script Interpreter 1.2.

We fixed 2 issues for Script interpreter:
https://s.apache.org/MSCRIPT-INTERPRETER-JIRA-1.2
We fixed 4 issues for Invoker plugin:
https://s.apache.org/MINVOKER-JIRA-3.0.1

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


Source releases:
*
https://repository.apache.org/content/repositories/maven-1346/org/apache/maven/plugins/maven-invoker-plugin/3.0.1/maven-invoker-plugin-3.0.1-source-release.zip
*
https://repository.apache.org/content/repositories/maven-1346/org/apache/maven/shared/maven-script-interpreter/1.2/maven-script-interpreter-1.2-source-release.zip

Staging sites:
http://maven.apache.org/components/plugins-archives/maven-invoker-plugin-LATEST/
http://maven.apache.org/components/shared-archives/maven-script-interpreter-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

My +1

Cheers


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

[GitHub] maven issue #127: [MNG-6255] Fix concat_lines in mvn to deal with CRLF

[grkvlt]

Github user grkvlt commented on the issue:

https://github.com/apache/maven/pull/127
  
@Tunaki I will disable the *CR* test, then


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] maven-integration-testing issue #23: [MNG-6265] Integration test for Maven s...

[etzelc]

Github user etzelc commented on the issue:

https://github.com/apache/maven-integration-testing/pull/23
  
Thanks for your testing effort. I am surprised both tests pass in your 
Windows environment with 3.5.0. I tested the IT with two different clients 
(Windows 7 and Windows 10) and while `folder-with- -space/pom.xml` passes, the 
`folder-with-)-closing-bracket/pom.xml` test fails. 
The `folder-with- -space/pom.xml` test was developed to cover MNG-6177 
(https://issues.apache.org/jira/browse/MNG-6177), which has no IT and was 
already targeting "special" characters like spaces and more.

I have implemented the IT in a way to perform a successful maven run, since 
this is what you usually expect from maven. The example `mvn -f 
"folderWithClosing)Bracket/pomFolder"` from issue MNG-6256 
(https://issues.apache.org/jira/browse/MNG-6256) was chosen to have a very 
short example with no prerequisites. With 3.5.0 you should see the same error 
even if a well formed POM exist at the specified location and you set 
additionally a goal (see IT test `folder-with-)-closing-bracket/pom.xml`).
I did not implement a dedicated test for the error message, because it may 
change over the time and the purpose of my patch was not to have a correct 
error message (which is included in the patch implicitly), but have a 
successful maven run.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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