Am 05/07/16 um 20:05 schrieb Karl Heinz Marbaise:
> Hi to all,
>
> based on the number issues which have been fixed in the current 3.4.0...
>
> I would like to ask if there are objections to make a new release within
> the next 2 or 3 weeks...except we have very important fixes to do?..
There a
I'm using Win10
The funny thing:
Manifest-Version: 1.0
Implementation-Vendor: The Apache Software Foundation
Implementation-Title: Apache Maven JAR Plugin
Implementation-Version: 3.0.0
Implementation-Vendor-Id: org.apache.maven.plugins
Built-By: Robert Scholte
Build-Jdk: 1.7.0_55
Specification-Ve
Hi Robert,
On 5/7/16 10:24 PM, Robert Scholte wrote:
This is my content of
maven-jar-plugin-3.0.0\target\it\manifest-content\target\manifest-content-1.0-SNAPSHOT.jar!/META-INF/MANIFEST.MF
Manifest-Version: 1.0
Implementation-Vendor: jar plugin it
Implementation-Title: manifest-content-it
Imple
This is my content of
maven-jar-plugin-3.0.0\target\it\manifest-content\target\manifest-content-1.0-SNAPSHOT.jar!/META-INF/MANIFEST.MF
Manifest-Version: 1.0
Implementation-Vendor: jar plugin it
Implementation-Title: manifest-content-it
Implementation-Version: 1.0-SNAPSHOT
Implementation-Vendor-Id
Hi,
On 5/7/16 9:35 PM, Uwe Barthel wrote:
* MNG-3092: https://github.com/apache/maven/pull/70
The current PR has conflicts...which needs to be solved first...apart
from that we have a candiate which would like to be part of 3.4.0...
other candidates ?
Kind regards
Karl Heinz Marbaise
-
RERO! :-)
Gary
On Sat, May 7, 2016 at 11:05 AM, Karl Heinz Marbaise
wrote:
> Hi to all,
>
> based on the number issues which have been fixed in the current 3.4.0...
>
> I would like to ask if there are objections to make a new release within
> the next 2 or 3 weeks...except we have very importa
* MNG-3092: https://github.com/apache/maven/pull/70
-- barthel
> On 07 May 2016, at 20:05, Karl Heinz Marbaise wrote:
>
> Hi to all,
>
> based on the number issues which have been fixed in the current 3.4.0...
>
> I would like to ask if there are objections to make a new release within the
It works for me. Do you by any chance have an old staged 3.0.0 of the
plugin in your local repo?
/Anders (mobile)
On May 7, 2016 20:35, "Robert Scholte" wrote:
> https://issues.apache.org/jira/browse/MJAR-218
> is this really fixed?
>
> I still see a versionless Apache Maven in the MANIFEST.MF
>
Hi Robert,
On 5/7/16 8:35 PM, Robert Scholte wrote:
https://issues.apache.org/jira/browse/MJAR-218
is this really fixed?
I still see a versionless Apache Maven in the MANIFEST.MF
Hm...I tested with Maven 3.0.5 and 3.3.9 via
mvn -Prun-its clean verify
and checked the generated JAR files whic
https://issues.apache.org/jira/browse/MJAR-218
is this really fixed?
I still see a versionless Apache Maven in the MANIFEST.MF
Executed as
d:\apache-maven-3.3.9\bin\mvn clean verify -Prun-its
-Dinvoker.mavenHome=d:\apache-maven-3.0
thanks,
Robert
On Wed, 04 May 2016 20:16:20 +0200, Karl Hei
+1, non-binding
/Anders
On Wed, May 4, 2016 at 8:16 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 21 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12334171
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jir
Hi to all,
based on the number issues which have been fixed in the current 3.4.0...
I would like to ask if there are objections to make a new release within
the next 2 or 3 weeks...except we have very important fixes to do?..
Are there things missing ?
As a preparation to the above i would s
Hi,
i need one more PMC vote...
Kind regards
Karl Heinz
On 5/4/16 8:16 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 21 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12334171
There are still a couple of issues left in JIRA:
https://issues.apache.org
+1, big fan of Semantic Versioning.
Keeping the version string consistent hammers in that we follow semver
rules. I think Maven plugins generally do anyway. :)
As for Maven plugins the API is generally the goals and
(and associated files, e.g. assembly xml) rather than the Java API.
So example:
On 3 May 2016 6:19 p.m., "Hervé BOUTEMY" wrote:
> > +1, but note that maven-1006 is not a valid repo. Probably a typo.
> uh, I didn't notice that the usual maven- prefix was changed to
> orgapacheapache- ...
>
> if tis is persistent, it'll be useful to change the release procedure
It is probably
+1
/Anders (mobile)
On May 6, 2016 22:00, "Karl Heinz Marbaise" wrote:
> Hi to all,
>
> I would like to suggest to keep the version number of the plugins and
> shared components to the following format (and may be also things we are
> using like plexus?):
>
> Major.Minor.Patch(-SNAPSHOT):
>
> (F
Hi,
here is my +1
Kind regards
Karl Heinz
On 5/6/16 1:46 AM, Karl Heinz Marbaise wrote:
Hi,
We solved 20 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317827&version=12331252
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?
Hi,
The vote has passed with the following result:
+1 : Michael Osipov, Karl Heinz Marbaise, Christopher Tubbs, Hervé Boutemy
PMC quorum: reached
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail:
here is my +1
Regards,
Hervé
Le mardi 3 mai 2016 01:50:24 Hervé BOUTEMY a écrit :
> Hi,
>
> In preparation to Apache parent pom version 18, we need a little bugfix on
> Apache Source Release Assembly Descriptor to fix MPOM-106
>
> We solved 1 issue:
> https://issues.apache.org/jira/secure/Rele
+1
Regards,
Hervé
Le mercredi 4 mai 2016 20:16:20 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 21 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&ve
> rsion=12334171
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/i
Hi,
see here:
http://mail-archives.apache.org/mod_mbox/maven-dev/201503.mbox/%3C20150320213920.6AE4B17423%40minotaur.apache.org%3E
In contradiction to the mail we have decided to define the minimum Maven
version 3.0 ...
Based on the minimum we have decided (3.0) this means JDK 6 minimum...
21 matches
Mail list logo