Possible bug in the ProjectBuilder (3.5.4) ?

2018-09-24 Thread Cristiano 
Hello, I need some assistance in order to identify whether the issue I'm 
facing is a bug or a missing feature.


I'm adding a goal to my plugin that must read a POM project from a 
repository and get details about the dependencies declared on it.


In order to build the POM object I've created the method below that are 
using Core's org.apache.maven.project.ProjectBuilder:



    public MavenProject loadProject(Artifact artifact,
   MavenSession session,
    boolean pResolveDependencies) throws
   ProjectBuildingException {
    ProjectBuildingRequest request = new
   DefaultProjectBuildingRequest();
   request.setLocalRepository(session.getLocalRepository());
    request.setRemoteRepositories(
   session.getCurrentProject().getRemoteArtifactRepositories());
    request.setResolveDependencies(pResolveDependencies);
   request.setRepositorySession(session.getRepositorySession());
    request.setInactiveProfileIds(
   Arrays.asList("when-building-java-using-java8"));  ---> I added
   this in order to try no get one of the errors reported.
    return projectBuilder.build(artifact,
   request).getProject();
    }


   In order to test it I'm trying to read this [pom]
   
https://search.maven.org/classic/#artifactdetails%7Cbr.com.c8tech.releng%7Cfpom-deps-felix%7C2.1%7Cpom.

   This POM has declared a POM fragment:


    
    
    
br.com.c8tech.releng
    2.1
fpom-deps-osgi
    import
    pom


   And I'm using this code:

   {

 pom = loadProject(
    new
   DefaultArtifact("br.com.c8tech.releng:fpom-deps-felix:pom:2.1"),
    true);

   }

   The error I'm getting from ProjectBuilder is about not being able to
   get the versions declared in the imported POM ( declared in its
   dependencyManagement) and also not being able to determine the Java
   version of a profile activated by  property.



Caused by: org.apache.maven.project.ProjectBuildingException: Some
problems were encountered while processing the POMs:
[ERROR] Failed to determine Java version for profile
when-building-java-using-java8 @
br.com.c8tech.releng:maven-parent-java:2.1,

/home/cvgaviao/.m2/repository/br/com/c8tech/releng/maven-parent-java/2.1/maven-parent-java-2.1.pom,
line 658, column 22
[ERROR] 'dependencies.dependency.version' for
net.java.dev.jna:jna:jar is missing. @
br.com.c8tech.releng:fpom-deps-felix:[unknown-version],

/home/cvgaviao/.m2/repository/br/com/c8tech/releng/fpom-deps-felix/2.1/fpom-deps-felix-2.1.pom,
line 329, column 21
[ERROR] 'dependencies.dependency.version' for
ch.qos.logback:logback-core:jar is missing. @
br.com.c8tech.releng:fpom-deps-felix:[unknown-version],

/home/cvgaviao/.m2/repository/br/com/c8tech/releng/fpom-deps-felix/2.1/fpom-deps-felix-2.1.pom,
line 337, column 21


could someone tell me if its a missing feature, a bug or maybe am I 
missing something ?



thanks a lot,


Cristiano

Re: Cut Maven Core Release 3.6.0

2018-09-24 Thread Hervé BOUTEMY 
notice that the script will have to be updated for sha512 (that is not 
published to staging repo)

most of the release procedure for core is exactly the same as for any 
component:
https://maven.apache.org/developers/release/maven-core-release.html

Regards,

Hervé

Le lundi 24 septembre 2018, 20:44:59 CEST Karl Heinz Marbaise a écrit :
> Hi Stephen,
> 
> On 24/09/18 20:43, Karl Heinz Marbaise wrote:
> > Hi Stephen,
> > 
> > I appreciate that...
> > 
> > That will a lot..
> 
> Too fast with the send button.
> 
> This should be read as:
> 
> That will help a lot...
> 
> ;-)..
> 
> Kind regards
> Karl Heinz Marbaise
> 
> > Thanks.
> > 
> > Kind regards
> > Karl Heinz Marbaise
> > 
> > On 24/09/18 10:39, Stephen Connolly wrote:
> >> I assume you would like my notes from the 3.5.3 release: (also the
> >> source-release-validator is at
> >> g...@github.com:stephenc/source-release-validator.git
> >> )
> >> 
> >> $ export JAVA_HOME=jdk7
> >> $ export PATH=${JAVA_HOME}/bin:${PATH}
> >> $ export MAVEN_OPTS="-Xmx2048m -XX:MaxPermSize=512m"
> >> $ mvn release:prepare release:perform
> >> $ cd target/checkout
> >> $ mvn -Preporting site site:stage && mvn scm-publish:publish-scm
> >> $ cd ../../../maven-integration-testing
> >> $ docker build --tag maven-it:latest environments/debian-jdk7 &&
> >> docker run
> >> -it --rm -v $(pwd):/root/maven-integration-testing -v
> >> $(pwd)/../maven:/root/maven maven-it:latest  bash -c "cd
> >> /root/maven-integration-testing && for dist in
> >> /root/maven/target/checkout/apache-maven/target/apache-maven-*-bin.zip
> >> ; do
> >> mvn clean install -Prun-its -Dmaven.repo.local=\$HOME/tmp/repo
> >> -DmavenDistro=\$dist ; done"
> >> $ mvn -Preporting site site:stage && mvn scm-publish:publish-scm
> >> 
> >> Close staging repo
> >> 
> >> $ cd ~/tmp
> >> $ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3 maven-dist
> >> $ cd maven-dist
> >> $ mkdir -p 3.5.3/{binaries,source}
> >> $ for ext in tar.gz zip ; do ( cd 3.5.3/binaries/ ; for hash in "" .asc
> >> .md5 .sha1 ; do curl -O
> >> https://repository.apache.org/content/repositories/maven-1401/org/apache/
> >> maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.$ext$hash
> >> 
> >> ; done ) done
> >> $ for ext in tar.gz zip ; do ( cd 3.5.3/source/ ; for hash in "" .asc
> >> .md5
> >> .sha1 ; do curl -O
> >> https://repository.apache.org/content/repositories/maven-1401/org/apache/
> >> maven/apache-maven/3.5.3/apache-maven-3.5.3-src.$ext$hash
> >> 
> >> ; done ) done
> >> 
> >> $ for f in $(find . -name \*.tar.gz -o -name \*.zip) ; do echo -n
> >> $(gsha256sum "$f" | sed -e 's/ .*$//') > "${f}.sha256" ; done
> >> 
> >> $ svn add 3.5.3
> >> $ svn ci -m "Staging the 3.5.3 binaries for the release vote"
> >> Send vote email
> >> $ cd ../source-release-validator && target/appassembler/bin/sra
> >> https://repository.apache.org/content/repositories/maven-1401 3.5.3
> >> Send release-validator email
> >> Start preparing the release notes
> >> Start changes to recommended version in maven-site/pom.xml
> >> 
> >> 
> >> ---
> >> 
> >> $ svn ci -m "update release notes"
> >> $ cd ~/apache/maven && vi doap_Maven.rdf && git commit -m "update doap"
> >> doap_Maven.rdf && git push
> >> $ svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
> >> https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Release
> >> 3.5.3"
> >> $ svn cp
> >> https://svn.apache.org/repos/asf/maven/website/components/ref/3-LATEST
> >> https://svn.apache.org/repos/asf/maven/website/components/ref/3.5.4 -m
> >> "Deploy the 3.5.4 reference documentation"
> >> $ Mark version released in JIRA
> >> $ release staging repo
> >> 
> >> --- wait the sync to mirrors ---
> >> 
> >> 24. Publish the website with https://cms.apache.org/maven/publish
> >> 25. Send the announcement email
> >> 26. (PMC only) Record the release on
> >> https://reporter.apache.org/addrelease.html?maven
> >> 27. Tweet the release
> >> 28. Wait for the announcement email to show up on the
> >> https://mail-archives.apache.org/mod_mbox/maven-announce/ archives
> >> 29. Update the site history with the announce email
> >> 30. Publish the site again
> >> 31. Celebrate!!!
> >> 
> >> On Sun, 23 Sep 2018 at 19:05, Karl Heinz Marbaise 
> >> 
> >> wrote:
> >>> Hi,
> >>> 
> >>> based on the feedback we had I would like to announce to cut a release
> >>> at the end of next Week which means (likely on Saturday/Sunday 29.09 /
> >>> 30.09 )...
> >>> 
> >>> If anyone has something which should be put into Maven core release the
> >>> next week is your chance...
> >>> 
> >>> So this time I'm stepping up to be release manager for 3.6.0 of Maven
> >>> core...(if no one has objections to this.)..
> >>> 
> >>> Currently maven master is fine ...so keep it green...ah...sorry blue
> >>> ;-)..
> >>> 
> >>> 
> >>> Kind regards
> >>> Karl Heinz Marbaise
> >>> 
> >>> On 13/09/18 22:20, Karl Heinz Marbaise wrote:
>  Hi,
>  based on the issues have been solved..
>  
>  from my point of view waiting

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

2018-09-24 Thread Hervé BOUTEMY 
+1

Regards,

Hervé

Le samedi 22 septembre 2018, 13:29:51 CEST Robert Scholte a écrit :
> Hi,
> 
> We solved 18 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527
> rsion=12330848=Text
> 
> There is still 1 issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317527%20AND%20
> status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1449/
> https://repository.apache.org/content/repositories/maven-1449/org/apache/mav
> en/jxr/jxr/3.0.0/jxr-3.0.0-source-release.zip
> 
> Source release checksum(s):
> jxr-3.0.0-source-release.zip sha512:
> ccf691d97fa933030af58755fcf18678b7f4ed65b5ee4733e45cdbf023a51f755049fa3355e9
> d4aad8e78da510915695263f3363d517a2d562bc8780c765734b
> 
> Staging site:
> https://maven.apache.org/jxr-archives/jxr-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: Cut Maven Core Release 3.6.0

2018-09-24 Thread Karl Heinz Marbaise 

Hi Elliotte,

On 24/09/18 21:59, Elliotte Rusty Harold wrote:

https://github.com/apache/maven-site


The web site is up-to-date (https://maven.apache.org/ of 09/22/2019 
means two days old) ?


Is there something special you have in mind?

Kind regards
Karl Heinz Marbaise


That is, most of the content found on https://maven.apache.org/

On Mon, Sep 24, 2018 at 2:44 PM, Karl Heinz Marbaise  wrote:

Hi Elliotte,

On 24/09/18 15:42, Elliotte Rusty Harold wrote:


What's the procedure/plans for updating the web site and docs in sync
with a new release? Most of the site seems to be in a separate repo.



Can you be more specific about which sites/docs you are talking about?


Kind regards
Karl Heinz Marbaise



On Sun, Sep 23, 2018 at 2:05 PM, Karl Heinz Marbaise 
wrote:


Hi,

based on the feedback we had I would like to announce to cut a release
at the end of next Week which means (likely on Saturday/Sunday 29.09 /
30.09
)...

If anyone has something which should be put into Maven core release the
next
week is your chance...

So this time I'm stepping up to be release manager for 3.6.0 of Maven
core...(if no one has objections to this.)..

Currently maven master is fine ...so keep it green...ah...sorry blue
;-)..


Kind regards
Karl Heinz Marbaise

On 13/09/18 22:20, Karl Heinz Marbaise wrote:



Hi,
based on the issues have been solved..

from my point of view waiting at the moment for the following issues:


* MNG-6311
* MNG-6391

Afterwards I would like to cut a release of Maven Core...

This results into the question:

Should we call it 3.6.0 or 3.5.5..?

Based on the fixed issues which are only bug fixes (my opinion)...I
would
vote for 3.5.5 ?

What do you think?



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

Re: Cut Maven Core Release 3.6.0

2018-09-24 Thread Elliotte Rusty Harold 
https://github.com/apache/maven-site

That is, most of the content found on https://maven.apache.org/

On Mon, Sep 24, 2018 at 2:44 PM, Karl Heinz Marbaise  wrote:
> Hi Elliotte,
>
> On 24/09/18 15:42, Elliotte Rusty Harold wrote:
>>
>> What's the procedure/plans for updating the web site and docs in sync
>> with a new release? Most of the site seems to be in a separate repo.
>
>
> Can you be more specific about which sites/docs you are talking about?
>
>
> Kind regards
> Karl Heinz Marbaise
>
>>
>> On Sun, Sep 23, 2018 at 2:05 PM, Karl Heinz Marbaise 
>> wrote:
>>>
>>> Hi,
>>>
>>> based on the feedback we had I would like to announce to cut a release
>>> at the end of next Week which means (likely on Saturday/Sunday 29.09 /
>>> 30.09
>>> )...
>>>
>>> If anyone has something which should be put into Maven core release the
>>> next
>>> week is your chance...
>>>
>>> So this time I'm stepping up to be release manager for 3.6.0 of Maven
>>> core...(if no one has objections to this.)..
>>>
>>> Currently maven master is fine ...so keep it green...ah...sorry blue
>>> ;-)..
>>>
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>> On 13/09/18 22:20, Karl Heinz Marbaise wrote:


 Hi,
 based on the issues have been solved..

 from my point of view waiting at the moment for the following issues:


* MNG-6311
* MNG-6391

 Afterwards I would like to cut a release of Maven Core...

 This results into the question:

 Should we call it 3.6.0 or 3.5.5..?

 Based on the fixed issues which are only bug fixes (my opinion)...I
 would
 vote for 3.5.5 ?

 What do you think?

>



-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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

Re: Cut Maven Core Release 3.6.0

2018-09-24 Thread Karl Heinz Marbaise 

Hi Stephen,

I think we should consider to move the code of that repository into the 
ASF...


we need to check the permission with Jason ...

Kind regards
Karl Heinz Marbaise
On 24/09/18 10:39, Stephen Connolly wrote:

I assume you would like my notes from the 3.5.3 release: (also the
source-release-validator is at
g...@github.com:stephenc/source-release-validator.git
)

$ export JAVA_HOME=jdk7
$ export PATH=${JAVA_HOME}/bin:${PATH}
$ export MAVEN_OPTS="-Xmx2048m -XX:MaxPermSize=512m"
$ mvn release:prepare release:perform
$ cd target/checkout
$ mvn -Preporting site site:stage && mvn scm-publish:publish-scm
$ cd ../../../maven-integration-testing
$ docker build --tag maven-it:latest environments/debian-jdk7 && docker run
-it --rm -v $(pwd):/root/maven-integration-testing -v
$(pwd)/../maven:/root/maven maven-it:latest  bash -c "cd
/root/maven-integration-testing && for dist in
/root/maven/target/checkout/apache-maven/target/apache-maven-*-bin.zip ; do
mvn clean install -Prun-its -Dmaven.repo.local=\$HOME/tmp/repo
-DmavenDistro=\$dist ; done"
$ mvn -Preporting site site:stage && mvn scm-publish:publish-scm

Close staging repo

$ cd ~/tmp
$ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3 maven-dist
$ cd maven-dist
$ mkdir -p 3.5.3/{binaries,source}
$ for ext in tar.gz zip ; do ( cd 3.5.3/binaries/ ; for hash in "" .asc
.md5 .sha1 ; do curl -O
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.$ext$hash
; done ) done
$ for ext in tar.gz zip ; do ( cd 3.5.3/source/ ; for hash in "" .asc .md5
.sha1 ; do curl -O
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.$ext$hash
; done ) done

$ for f in $(find . -name \*.tar.gz -o -name \*.zip) ; do echo -n
$(gsha256sum "$f" | sed -e 's/ .*$//') > "${f}.sha256" ; done

$ svn add 3.5.3
$ svn ci -m "Staging the 3.5.3 binaries for the release vote"
Send vote email
$ cd ../source-release-validator && target/appassembler/bin/sra
https://repository.apache.org/content/repositories/maven-1401 3.5.3
Send release-validator email
Start preparing the release notes
Start changes to recommended version in maven-site/pom.xml


---

$ svn ci -m "update release notes"
$ cd ~/apache/maven && vi doap_Maven.rdf && git commit -m "update doap"
doap_Maven.rdf && git push
$ svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Release 3.5.3"
$ svn cp
https://svn.apache.org/repos/asf/maven/website/components/ref/3-LATEST
https://svn.apache.org/repos/asf/maven/website/components/ref/3.5.4 -m
"Deploy the 3.5.4 reference documentation"
$ Mark version released in JIRA
$ release staging repo

--- wait the sync to mirrors ---

24. Publish the website with https://cms.apache.org/maven/publish
25. Send the announcement email
26. (PMC only) Record the release on
https://reporter.apache.org/addrelease.html?maven
27. Tweet the release
28. Wait for the announcement email to show up on the
https://mail-archives.apache.org/mod_mbox/maven-announce/ archives
29. Update the site history with the announce email
30. Publish the site again
31. Celebrate!!!

On Sun, 23 Sep 2018 at 19:05, Karl Heinz Marbaise  wrote:


Hi,

based on the feedback we had I would like to announce to cut a release
at the end of next Week which means (likely on Saturday/Sunday 29.09 /
30.09 )...

If anyone has something which should be put into Maven core release the
next week is your chance...

So this time I'm stepping up to be release manager for 3.6.0 of Maven
core...(if no one has objections to this.)..

Currently maven master is fine ...so keep it green...ah...sorry blue ;-)..


Kind regards
Karl Heinz Marbaise

On 13/09/18 22:20, Karl Heinz Marbaise wrote:

Hi,
based on the issues have been solved..

from my point of view waiting at the moment for the following issues:


   * MNG-6311
   * MNG-6391

Afterwards I would like to cut a release of Maven Core...

This results into the question:

Should we call it 3.6.0 or 3.5.5..?

Based on the fixed issues which are only bug fixes (my opinion)...I
would vote for 3.5.5 ?

What do you think?

Kind regards
Karl Heinz Marbaise


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

Re: Second MNG-6415

2018-09-24 Thread Enrico Olivelli 
+1 (non binding)

Enrico

Il lun 24 set 2018, 20:41 Karl Heinz Marbaise  ha
scritto:

> Hi Robert,
>
> I second this change for 3.6.0.
>
> +1...
>
>
> Kind regards
> Karl Heinz Marbaise
>
> On 24/09/18 20:30, Robert Scholte wrote:
> > [MNG-6415] Project Artifacts Cache does not retain the order of
> > classpath entries.
> >
> > Who can second this?
> >
> > thanks,
> > Robert
> >
> > JIRA:https://issues.apache.org/jira/browse/MNG-6415
> >
> > GIT:
> >
> https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=7c1e7129b12973769f49cd946236e43f4bd17d51
> >
> >
> > JENKINS: https://builds.apache.org/job/maven-box/job/maven/job/MNG-6415/
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --


-- Enrico Olivelli

Re: Cut Maven Core Release 3.6.0

2018-09-24 Thread Karl Heinz Marbaise 

Hi Stephen,

On 24/09/18 20:43, Karl Heinz Marbaise wrote:

Hi Stephen,

I appreciate that...

That will a lot..


Too fast with the send button.

This should be read as:

That will help a lot...

;-)..

Kind regards
Karl Heinz Marbaise


Thanks.

Kind regards
Karl Heinz Marbaise
On 24/09/18 10:39, Stephen Connolly wrote:

I assume you would like my notes from the 3.5.3 release: (also the
source-release-validator is at
g...@github.com:stephenc/source-release-validator.git
)

$ export JAVA_HOME=jdk7
$ export PATH=${JAVA_HOME}/bin:${PATH}
$ export MAVEN_OPTS="-Xmx2048m -XX:MaxPermSize=512m"
$ mvn release:prepare release:perform
$ cd target/checkout
$ mvn -Preporting site site:stage && mvn scm-publish:publish-scm
$ cd ../../../maven-integration-testing
$ docker build --tag maven-it:latest environments/debian-jdk7 && 
docker run

-it --rm -v $(pwd):/root/maven-integration-testing -v
$(pwd)/../maven:/root/maven maven-it:latest  bash -c "cd
/root/maven-integration-testing && for dist in
/root/maven/target/checkout/apache-maven/target/apache-maven-*-bin.zip 
; do

mvn clean install -Prun-its -Dmaven.repo.local=\$HOME/tmp/repo
-DmavenDistro=\$dist ; done"
$ mvn -Preporting site site:stage && mvn scm-publish:publish-scm

Close staging repo

$ cd ~/tmp
$ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3 maven-dist
$ cd maven-dist
$ mkdir -p 3.5.3/{binaries,source}
$ for ext in tar.gz zip ; do ( cd 3.5.3/binaries/ ; for hash in "" .asc
.md5 .sha1 ; do curl -O
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.$ext$hash 


; done ) done
$ for ext in tar.gz zip ; do ( cd 3.5.3/source/ ; for hash in "" .asc 
.md5

.sha1 ; do curl -O
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.$ext$hash 


; done ) done

$ for f in $(find . -name \*.tar.gz -o -name \*.zip) ; do echo -n
$(gsha256sum "$f" | sed -e 's/ .*$//') > "${f}.sha256" ; done

$ svn add 3.5.3
$ svn ci -m "Staging the 3.5.3 binaries for the release vote"
Send vote email
$ cd ../source-release-validator && target/appassembler/bin/sra
https://repository.apache.org/content/repositories/maven-1401 3.5.3
Send release-validator email
Start preparing the release notes
Start changes to recommended version in maven-site/pom.xml


---

$ svn ci -m "update release notes"
$ cd ~/apache/maven && vi doap_Maven.rdf && git commit -m "update doap"
doap_Maven.rdf && git push
$ svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Release 
3.5.3"

$ svn cp
https://svn.apache.org/repos/asf/maven/website/components/ref/3-LATEST
https://svn.apache.org/repos/asf/maven/website/components/ref/3.5.4 -m
"Deploy the 3.5.4 reference documentation"
$ Mark version released in JIRA
$ release staging repo

--- wait the sync to mirrors ---

24. Publish the website with https://cms.apache.org/maven/publish
25. Send the announcement email
26. (PMC only) Record the release on
https://reporter.apache.org/addrelease.html?maven
27. Tweet the release
28. Wait for the announcement email to show up on the
https://mail-archives.apache.org/mod_mbox/maven-announce/ archives
29. Update the site history with the announce email
30. Publish the site again
31. Celebrate!!!

On Sun, 23 Sep 2018 at 19:05, Karl Heinz Marbaise  
wrote:



Hi,

based on the feedback we had I would like to announce to cut a release
at the end of next Week which means (likely on Saturday/Sunday 29.09 /
30.09 )...

If anyone has something which should be put into Maven core release the
next week is your chance...

So this time I'm stepping up to be release manager for 3.6.0 of Maven
core...(if no one has objections to this.)..

Currently maven master is fine ...so keep it green...ah...sorry blue 
;-)..



Kind regards
Karl Heinz Marbaise

On 13/09/18 22:20, Karl Heinz Marbaise wrote:

Hi,
based on the issues have been solved..

from my point of view waiting at the moment for the following issues:


   * MNG-6311
   * MNG-6391

Afterwards I would like to cut a release of Maven Core...

This results into the question:

Should we call it 3.6.0 or 3.5.5..?

Based on the fixed issues which are only bug fixes (my opinion)...I
would vote for 3.5.5 ?

What do you think?



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

Re: Cut Maven Core Release 3.6.0

2018-09-24 Thread Karl Heinz Marbaise 

Hi Elliotte,

On 24/09/18 15:42, Elliotte Rusty Harold wrote:

What's the procedure/plans for updating the web site and docs in sync
with a new release? Most of the site seems to be in a separate repo.


Can you be more specific about which sites/docs you are talking about?

Kind regards
Karl Heinz Marbaise



On Sun, Sep 23, 2018 at 2:05 PM, Karl Heinz Marbaise  wrote:

Hi,

based on the feedback we had I would like to announce to cut a release
at the end of next Week which means (likely on Saturday/Sunday 29.09 / 30.09
)...

If anyone has something which should be put into Maven core release the next
week is your chance...

So this time I'm stepping up to be release manager for 3.6.0 of Maven
core...(if no one has objections to this.)..

Currently maven master is fine ...so keep it green...ah...sorry blue ;-)..


Kind regards
Karl Heinz Marbaise

On 13/09/18 22:20, Karl Heinz Marbaise wrote:


Hi,
based on the issues have been solved..

from my point of view waiting at the moment for the following issues:


   * MNG-6311
   * MNG-6391

Afterwards I would like to cut a release of Maven Core...

This results into the question:

Should we call it 3.6.0 or 3.5.5..?

Based on the fixed issues which are only bug fixes (my opinion)...I would
vote for 3.5.5 ?

What do you think?



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

Re: Cut Maven Core Release 3.6.0

2018-09-24 Thread Karl Heinz Marbaise 

Hi Stephen,

I appreciate that...

That will a lot..

Thanks.

Kind regards
Karl Heinz Marbaise
On 24/09/18 10:39, Stephen Connolly wrote:

I assume you would like my notes from the 3.5.3 release: (also the
source-release-validator is at
g...@github.com:stephenc/source-release-validator.git
)

$ export JAVA_HOME=jdk7
$ export PATH=${JAVA_HOME}/bin:${PATH}
$ export MAVEN_OPTS="-Xmx2048m -XX:MaxPermSize=512m"
$ mvn release:prepare release:perform
$ cd target/checkout
$ mvn -Preporting site site:stage && mvn scm-publish:publish-scm
$ cd ../../../maven-integration-testing
$ docker build --tag maven-it:latest environments/debian-jdk7 && docker run
-it --rm -v $(pwd):/root/maven-integration-testing -v
$(pwd)/../maven:/root/maven maven-it:latest  bash -c "cd
/root/maven-integration-testing && for dist in
/root/maven/target/checkout/apache-maven/target/apache-maven-*-bin.zip ; do
mvn clean install -Prun-its -Dmaven.repo.local=\$HOME/tmp/repo
-DmavenDistro=\$dist ; done"
$ mvn -Preporting site site:stage && mvn scm-publish:publish-scm

Close staging repo

$ cd ~/tmp
$ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3 maven-dist
$ cd maven-dist
$ mkdir -p 3.5.3/{binaries,source}
$ for ext in tar.gz zip ; do ( cd 3.5.3/binaries/ ; for hash in "" .asc
.md5 .sha1 ; do curl -O
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.$ext$hash
; done ) done
$ for ext in tar.gz zip ; do ( cd 3.5.3/source/ ; for hash in "" .asc .md5
.sha1 ; do curl -O
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.$ext$hash
; done ) done

$ for f in $(find . -name \*.tar.gz -o -name \*.zip) ; do echo -n
$(gsha256sum "$f" | sed -e 's/ .*$//') > "${f}.sha256" ; done

$ svn add 3.5.3
$ svn ci -m "Staging the 3.5.3 binaries for the release vote"
Send vote email
$ cd ../source-release-validator && target/appassembler/bin/sra
https://repository.apache.org/content/repositories/maven-1401 3.5.3
Send release-validator email
Start preparing the release notes
Start changes to recommended version in maven-site/pom.xml


---

$ svn ci -m "update release notes"
$ cd ~/apache/maven && vi doap_Maven.rdf && git commit -m "update doap"
doap_Maven.rdf && git push
$ svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Release 3.5.3"
$ svn cp
https://svn.apache.org/repos/asf/maven/website/components/ref/3-LATEST
https://svn.apache.org/repos/asf/maven/website/components/ref/3.5.4 -m
"Deploy the 3.5.4 reference documentation"
$ Mark version released in JIRA
$ release staging repo

--- wait the sync to mirrors ---

24. Publish the website with https://cms.apache.org/maven/publish
25. Send the announcement email
26. (PMC only) Record the release on
https://reporter.apache.org/addrelease.html?maven
27. Tweet the release
28. Wait for the announcement email to show up on the
https://mail-archives.apache.org/mod_mbox/maven-announce/ archives
29. Update the site history with the announce email
30. Publish the site again
31. Celebrate!!!

On Sun, 23 Sep 2018 at 19:05, Karl Heinz Marbaise  wrote:


Hi,

based on the feedback we had I would like to announce to cut a release
at the end of next Week which means (likely on Saturday/Sunday 29.09 /
30.09 )...

If anyone has something which should be put into Maven core release the
next week is your chance...

So this time I'm stepping up to be release manager for 3.6.0 of Maven
core...(if no one has objections to this.)..

Currently maven master is fine ...so keep it green...ah...sorry blue ;-)..


Kind regards
Karl Heinz Marbaise

On 13/09/18 22:20, Karl Heinz Marbaise wrote:

Hi,
based on the issues have been solved..

from my point of view waiting at the moment for the following issues:


   * MNG-6311
   * MNG-6391

Afterwards I would like to cut a release of Maven Core...

This results into the question:

Should we call it 3.6.0 or 3.5.5..?

Based on the fixed issues which are only bug fixes (my opinion)...I
would vote for 3.5.5 ?

What do you think?

Kind regards
Karl Heinz Marbaise


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

Re: Second MNG-6415

2018-09-24 Thread Karl Heinz Marbaise 

Hi Robert,

I second this change for 3.6.0.

+1...


Kind regards
Karl Heinz Marbaise

On 24/09/18 20:30, Robert Scholte wrote:
[MNG-6415] Project Artifacts Cache does not retain the order of 
classpath entries.


Who can second this?

thanks,
Robert

JIRA:    https://issues.apache.org/jira/browse/MNG-6415

GIT: 
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=7c1e7129b12973769f49cd946236e43f4bd17d51 



JENKINS: https://builds.apache.org/job/maven-box/job/maven/job/MNG-6415/


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

Second MNG-6415

2018-09-24 Thread Robert Scholte 
[MNG-6415] Project Artifacts Cache does not retain the order of classpath  
entries.


Who can second this?

thanks,
Robert

JIRA:https://issues.apache.org/jira/browse/MNG-6415

GIT:  
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=7c1e7129b12973769f49cd946236e43f4bd17d51


JENKINS: https://builds.apache.org/job/maven-box/job/maven/job/MNG-6415/

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

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

2018-09-24 Thread Karl Heinz Marbaise 

Hi,

On 24/09/18 11:14, Eric Lilja wrote:



 > 2. Both projects (install, deploy) have several warnings

Can you be more accurate? Where ?



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


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


After taking a look into it...

The point is that those JIRA issues which are marked "WARNING" are 
issues which have been fixed in Subversion before the migration to 
Git/GitBox... ..but the changes are part of the code...


I have checked Maven Deploy as well as Maven Install part ...

Can you please share a link with an issue which contains a reference to 
an open PR as you mentioned?


Kind regards
Karl Heinz Marbaise

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

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

2018-09-24 Thread Tibor Digana 
Eric,
Feel free to summarize the Warnings and TODOs in Jira issue unless such
issue(s) have already been created.
I believe then somebody will have a look.
This definitely helps improving the plugin.
The developers have to see how urgent the warnings are for this release as
well.

T

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

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

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

2018-09-24 Thread Tibor Digana 
+1

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

> Hi,
>
> We solved 32 issues:
> https://issues.apache.org/jira/projects/MINSTALL/versions/12334343
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINSTALL%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1450
>
> https://repository.apache.org/content/repositories/maven-1450/org/apache/maven/plugins/maven-install-plugin/3.0.0-M1/maven-install-plugin-3.0.0-M1-source-release.zip
>
> Source release checksum(s):
> maven-install-plugin-3.0.0-M1-source-release.zip
> sha512:
>
> 2f50d276c89a6f77df9dd7f220719ea3a85c63567ce5489978bf599527a5b62dd113bfea45eea8b8326d61d6e495c81fc89da1d8c0586503415e8941e5a0cd6d
> sha1: 338f04e24940a5c14b7c8ec78c5f307f6f342308
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-install-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

2018-09-24 Thread Tibor Digana 
+1

On Sat, Sep 22, 2018 at 1:29 PM Robert Scholte  wrote:

> Hi,
>
> We solved 18 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527=12330848=Text
>
> There is still 1 issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317527%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1449/
>
> https://repository.apache.org/content/repositories/maven-1449/org/apache/maven/jxr/jxr/3.0.0/jxr-3.0.0-source-release.zip
>
> Source release checksum(s):
> jxr-3.0.0-source-release.zip sha512:
>
> ccf691d97fa933030af58755fcf18678b7f4ed65b5ee4733e45cdbf023a51f755049fa3355e9d4aad8e78da510915695263f3363d517a2d562bc8780c765734b
>
> Staging site:
> https://maven.apache.org/jxr-archives/jxr-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

2018-09-24 Thread Tibor Digana 
+1

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

> Hi,
>
> We solved 31 issues:
> https://issues.apache.org/jira/projects/MDEPLOY/versions/12330476
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDEPLOY%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1451/
>
> https://repository.apache.org/content/repositories/maven-1451/org/apache/maven/plugins/maven-deploy-plugin/3.0.0-M1/maven-deploy-plugin-3.0.0-M1-source-release.zip
>
> Source release checksum(s):
> maven-deploy-plugin-3.0.0-M1-source-release.zip
> sha512:
>
> 980493bc4a2d2e818b5b551bcc86391f897ac28c36fe45575f36166a66e69b45e8955d7456562c63921330354bc245eb011e43441d616eb6104819ba947d262f
> sha1: 1e35caa35ffb3ffbe074756589ff2433c5b81a71
>
> Staging site:
> http://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Cut Maven Core Release 3.6.0

2018-09-24 Thread Elliotte Rusty Harold 
What's the procedure/plans for updating the web site and docs in sync
with a new release? Most of the site seems to be in a separate repo.

On Sun, Sep 23, 2018 at 2:05 PM, Karl Heinz Marbaise  wrote:
> Hi,
>
> based on the feedback we had I would like to announce to cut a release
> at the end of next Week which means (likely on Saturday/Sunday 29.09 / 30.09
> )...
>
> If anyone has something which should be put into Maven core release the next
> week is your chance...
>
> So this time I'm stepping up to be release manager for 3.6.0 of Maven
> core...(if no one has objections to this.)..
>
> Currently maven master is fine ...so keep it green...ah...sorry blue ;-)..
>
>
> Kind regards
> Karl Heinz Marbaise
>
> On 13/09/18 22:20, Karl Heinz Marbaise wrote:
>>
>> Hi,
>> based on the issues have been solved..
>>
>> from my point of view waiting at the moment for the following issues:
>>
>>
>>   * MNG-6311
>>   * MNG-6391
>>
>> Afterwards I would like to cut a release of Maven Core...
>>
>> This results into the question:
>>
>> Should we call it 3.6.0 or 3.5.5..?
>>
>> Based on the fixed issues which are only bug fixes (my opinion)...I would
>> vote for 3.5.5 ?
>>
>> What do you think?
>>
>> 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
>



-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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

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

2018-09-24 Thread Eric Lilja 
>
>
>
> > 2. Both projects (install, deploy) have several warnings
>
> Can you be more accurate? Where ?
>


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

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

- Eric L


>
>
>

Re: Cut Maven Core Release 3.6.0

2018-09-24 Thread Stephen Connolly 
I assume you would like my notes from the 3.5.3 release: (also the
source-release-validator is at
g...@github.com:stephenc/source-release-validator.git
)

$ export JAVA_HOME=jdk7
$ export PATH=${JAVA_HOME}/bin:${PATH}
$ export MAVEN_OPTS="-Xmx2048m -XX:MaxPermSize=512m"
$ mvn release:prepare release:perform
$ cd target/checkout
$ mvn -Preporting site site:stage && mvn scm-publish:publish-scm
$ cd ../../../maven-integration-testing
$ docker build --tag maven-it:latest environments/debian-jdk7 && docker run
-it --rm -v $(pwd):/root/maven-integration-testing -v
$(pwd)/../maven:/root/maven maven-it:latest  bash -c "cd
/root/maven-integration-testing && for dist in
/root/maven/target/checkout/apache-maven/target/apache-maven-*-bin.zip ; do
mvn clean install -Prun-its -Dmaven.repo.local=\$HOME/tmp/repo
-DmavenDistro=\$dist ; done"
$ mvn -Preporting site site:stage && mvn scm-publish:publish-scm

Close staging repo

$ cd ~/tmp
$ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3 maven-dist
$ cd maven-dist
$ mkdir -p 3.5.3/{binaries,source}
$ for ext in tar.gz zip ; do ( cd 3.5.3/binaries/ ; for hash in "" .asc
.md5 .sha1 ; do curl -O
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.$ext$hash
; done ) done
$ for ext in tar.gz zip ; do ( cd 3.5.3/source/ ; for hash in "" .asc .md5
.sha1 ; do curl -O
https://repository.apache.org/content/repositories/maven-1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.$ext$hash
; done ) done

$ for f in $(find . -name \*.tar.gz -o -name \*.zip) ; do echo -n
$(gsha256sum "$f" | sed -e 's/ .*$//') > "${f}.sha256" ; done

$ svn add 3.5.3
$ svn ci -m "Staging the 3.5.3 binaries for the release vote"
Send vote email
$ cd ../source-release-validator && target/appassembler/bin/sra
https://repository.apache.org/content/repositories/maven-1401 3.5.3
Send release-validator email
Start preparing the release notes
Start changes to recommended version in maven-site/pom.xml


---

$ svn ci -m "update release notes"
$ cd ~/apache/maven && vi doap_Maven.rdf && git commit -m "update doap"
doap_Maven.rdf && git push
$ svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Release 3.5.3"
$ svn cp
https://svn.apache.org/repos/asf/maven/website/components/ref/3-LATEST
https://svn.apache.org/repos/asf/maven/website/components/ref/3.5.4 -m
"Deploy the 3.5.4 reference documentation"
$ Mark version released in JIRA
$ release staging repo

--- wait the sync to mirrors ---

24. Publish the website with https://cms.apache.org/maven/publish
25. Send the announcement email
26. (PMC only) Record the release on
https://reporter.apache.org/addrelease.html?maven
27. Tweet the release
28. Wait for the announcement email to show up on the
https://mail-archives.apache.org/mod_mbox/maven-announce/ archives
29. Update the site history with the announce email
30. Publish the site again
31. Celebrate!!!

On Sun, 23 Sep 2018 at 19:05, Karl Heinz Marbaise  wrote:

> Hi,
>
> based on the feedback we had I would like to announce to cut a release
> at the end of next Week which means (likely on Saturday/Sunday 29.09 /
> 30.09 )...
>
> If anyone has something which should be put into Maven core release the
> next week is your chance...
>
> So this time I'm stepping up to be release manager for 3.6.0 of Maven
> core...(if no one has objections to this.)..
>
> Currently maven master is fine ...so keep it green...ah...sorry blue ;-)..
>
>
> Kind regards
> Karl Heinz Marbaise
>
> On 13/09/18 22:20, Karl Heinz Marbaise wrote:
> > Hi,
> > based on the issues have been solved..
> >
> > from my point of view waiting at the moment for the following issues:
> >
> >
> >   * MNG-6311
> >   * MNG-6391
> >
> > Afterwards I would like to cut a release of Maven Core...
> >
> > This results into the question:
> >
> > Should we call it 3.6.0 or 3.5.5..?
> >
> > Based on the fixed issues which are only bug fixes (my opinion)...I
> > would vote for 3.5.5 ?
> >
> > What do you think?
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Release Plugin -Dproject.scm.developerConnection

2018-09-24 Thread Stephen Connolly 
On Wed, 19 Sep 2018 at 06:54, Lui Baeumer  wrote:

> Hi developers,
>
> I've got an issue with the release plugin as it does not recognize the
> parameter
> -Dproject.scm.developerConnection.
>
> My build fails with:
> Missing required setting: scm connection or developerConnection must
> be specified.
>
> It works if I add an scm tag to the pom.xml, but I would prefer to
> pass the scm connection via commandline as describes here:
> https://maven.apache.org/guides/mini/guide-releasing.html
>
> The reason is that we have got a central build pipeline which builds
> 100+ applications. After migrating to the (great) release plugin
> mechanism, we have to add the scm tag to all application pom.xml
> files. Therefore I would like to pass the parameter from outside via
> -D option.
>
> If you confirm that this is an issue I would have a look at the code
> and might provide a patch.
>

The  tag is supposed to be defined in all pom.xml files that are a
release root, as the value of that tag is used to perform the checkout for
the release:perform build.

Depending on your SCM you may not need to define it for all your poms.

For example, if you use Subversion as a SCM, and your project is structured
such that the parent is in the parent directory then the calculated
inherited scm tag will match the effective scm tag.

On the other hand, if you use Git as a SCM then you will just need to put
the scm tag in the root pom of every git repo (because with Git, best
practice is to have the release root as the root pom)

My recommendation is just to always define the  tag if the project is
a release root. This has the benefit of signalling to readers that the pom
is intended to be a release root.

FYI: by "release root" I mean the root project of a multi-module set of
projects that get released and versioned atomically. You only *need* the
scm tag in the release root poms (you may also want to add the scm tag to
child poms that do not share the inheritance hierarchy if you are using the
site plugin to generate documentation - as in those cases the computed scm
URL would be incorrect... but it is not required by the release plugin)


> Best regards,
>
> Lui
>
> P.S. full output attached
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org

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

2018-09-24 Thread Karl Heinz Marbaise 

Hi Eric,

On 24/09/18 09:29, Eric Lilja wrote:



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


Hi,

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


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


Sorry of course...pasted the wrong link into the message...my fault..

Try this one:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317524=12334343



2. Both projects (install, deploy) have several warnings


Can you be more accurate? Where ?


3. Both projects have an issue still in TODO.


Yes that's correct. In Maven Install Plugin MINSTALL-126 cause it's not 
yet ready which I had planned to be part of the final 3.0.0 
release...Maybe I have time to fix this ...if not it will be postponed 
to the next release..



In Maven Deploy PLugin the issue MDEPLOY-243 which I have created after 
taking a deeper look into the generated site which I will fix for the 
final 3.0.0 release...


Thanks for checking this...

Kind regards
Karl Heinz Marbaise


Seems some JIRA managemenet is in order  here...

- Eric L





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

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

2018-09-24 Thread Eric Lilja 
solve versions should have been "solved issues"

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

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

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

2018-09-24 Thread Eric Lilja 
On Sun, Sep 23, 2018 at 7:44 PM Karl Heinz Marbaise 
wrote:

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

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

Seems some JIRA managemenet is in order  here...

- Eric L

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

2018-09-24 Thread Jesper Udby 
+1

:-)
> Den 24. september 2018 klokken 01:19 skrev Olivier Lamy : > 
> > > +1 > > On Sat, 22 Sep 2018 at 21:29, Robert Scholte 
>  wrote: > > > Hi, > > > > We solved 18 issues: > > > > 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527=12330848=Text
>  > > > > There is still 1 issues left in JIRA: > > > > 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317527%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>  > > > > Staging repo: > > 
> https://repository.apache.org/content/repositories/maven-1449/ > > > > 
> https://repository.apache.org/content/repositories/maven-1449/org/apache/maven/jxr/jxr/3.0.0/jxr-3.0.0-source-release.zip
>  > > > > Source release checksum(s): > > jxr-3.0.0-source-release.zip sha512: 
> > > > > 
> ccf691d97fa933030af58755fcf18678b7f4ed65b5ee4733e45cdbf023a51f755049fa3355e9d4aad8e78da510915695263f3363d517a2d562bc8780c765734b
>  > > > > Staging site: > > https://maven.apache.or
 g/jxr-archives/jxr-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 > > > > > > -- > 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