Re: Maven and DevOps

2016-05-01 Thread Karl Heinz Marbaise
t the artifacts are doing for users.. In such case however dependencies would not point to a version like (4.2.1.RELEASE) but instead to 20160501-235901. In order to pick the right technical version you would lookup the collaborative meta data. I do not expect everybody to shout hurray to th

Maven and DevOps

2016-05-01 Thread Hohwiller , Jörg
reports, etc. Vote +1/-1 on quality or security... * Still the project releasing the artifacts could label releases and associate minor/major release numbers to branches. In such case however dependencies would not point to a version like (4.2.1.RELEASE) but instead to 20160501-235901. In order to

Re: [RFC] MJAR-193

2016-05-01 Thread Robert Scholte
Hi, I'm not into OSGi, so I don't fully understand the requirement. But what I can say is that one of the principals of Maven is that maven-plugins don't depend on each other. Regarding the MANIFEST.MF file, I think that both the maven-ear-plugin and the maven-shade-plugin are good examples o

Re: Maven Site Generation

2016-05-01 Thread Karl Heinz Marbaise
Hi Hervé, On 5/1/16 5:03 PM, Hervé BOUTEMY wrote: Hi, fixed in http://svn.apache.org/r1741867 I'll upgrade back to 30-SNAPSHOT Sure.Thanks for fixing it... Kind regards Karl Heinz Regards, Hervé Le dimanche 1 mai 2016 11:59:02 Karl Heinz Marbaise a écrit : Hi, unfortunately there

Re: Maven Site Generation

2016-05-01 Thread Hervé BOUTEMY
Hi, fixed in http://svn.apache.org/r1741867 I'll upgrade back to 30-SNAPSHOT Regards, Hervé Le dimanche 1 mai 2016 11:59:02 Karl Heinz Marbaise a écrit : > Hi, > > unfortunately there was a commit to upgrade the maven site parent > https://svn.apache.org/repos/asf/maven/site/trunk which cause

[RFC] MJAR-193

2016-05-01 Thread Karl Heinz Marbaise
Hi, currently there are some requirements to allow other mojo's to contribute to MANIFEST.MF which is used during the package of for example of maven-jar-plugin... The question is: o Does someone has a good idea to solve such things ? Or what might be a good direction to go? o Let ot

[ANN] Apache Maven Shared Component: Maven Archiver Version 3.0.2 Released

2016-05-01 Thread Karl Heinz Marbaise
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Archiver Version 3.0.2. https://maven.apache.org/shared/maven-archiver/ The Maven Archiver is mainly used by plugins to handle packaging. The version numbers referenced in the Since column on th

Maven Site Generation

2016-05-01 Thread Karl Heinz Marbaise
Hi, unfortunately there was a commit to upgrade the maven site parent https://svn.apache.org/repos/asf/maven/site/trunk which caused the site https://ci.apache.org/builders/maven-site-staging/ compile to fail. At the moment i have undone those changes to get a working site publishing. Kind re

[RESULT] [VOTE] Release Apache Maven Shared Component: Maven Archiver 3.0.2

2016-05-01 Thread Karl Heinz Marbaise
Hi, The vote has passed with the following result: +1 : Anders Hammar, Robert Scholte, Hervè Boutemy, Karl Heinz Marbaise PMC quorum: achieved. I will promote the artifacts to the central repo Kind regards Karl Heinz Marbaise --

Re: [VOTE] Release Apache Maven Shared Component: Maven Archiver 3.0.2

2016-05-01 Thread Hervé BOUTEMY
+1 Regards, Hervé Le mercredi 27 avril 2016 19:57:04 Karl Heinz Marbaise a écrit : > Hi, > > We solved 1 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&ve > rsion=12335563 > > Staging repo: > https://repository.apache.org/content/repositories/maven-1264 >