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

2016-02-13 Thread Tibor Digana
We already discussed @irc and Herve found the issue in Jenkins. On Sat, Feb 13, 2016 at 6:40 PM, Karl Heinz Marbaise wrote: > Hi Tibor, > > On 2/13/16 6:22 PM, Tibor Digana wrote: > >> -1: issue with flushing *-sources.jar >> > > Can you explain what you mean by "issue with flushing" .. ? > > >

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

2016-02-13 Thread Karl Heinz Marbaise
Hi Tibor, On 2/13/16 6:22 PM, Tibor Digana wrote: -1: issue with flushing *-sources.jar Can you explain what you mean by "issue with flushing" .. ? Kind regards Karl Heinz Marbaise On Wed, Feb 10, 2016 at 9:19 PM, Karl Heinz Marbaise wrote: Hi, We solved 18 issues: https://issues.apac

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

2016-02-13 Thread Tibor Digana
-1: issue with flushing *-sources.jar On Wed, Feb 10, 2016 at 9:19 PM, Karl Heinz Marbaise wrote: > Hi, > > We solved 18 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12331545 > > There are no issues left in JIRA... > > Staging repo: > https://repo

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

2016-02-13 Thread Hervé BOUTEMY
notice I'm not the only one affected by this failure! https://builds.apache.org/job/maven-plugins/org.apache.maven.plugins$maven-source-plugin/5090/console Regards, Hervé Le samedi 13 février 2016 14:53:23 Hervé BOUTEMY a écrit : > +1 > > strangely, when I build the code from a directory store

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

2016-02-13 Thread Hervé BOUTEMY
+1 strangely, when I build the code from a directory stored on a HDD on my Linux box, I get a failure: Failed tests: TestSourceJarMojoTest.testIncludeMavenDescriptorWhenExplicitlyConfigured:70- >AbstractSourcePluginTestCase.doTestProjectWithSourceArchive:112- >AbstractSourcePluginTestCase.doT

[GitHub] maven pull request: MNG-3092: Adds version range result filter beh...

2016-02-13 Thread barthel
Github user barthel commented on the pull request: https://github.com/apache/maven/pull/70#issuecomment-183661203 @jvanzyl , @michael-o : I start working on the integration tests. It's more complicated than I thought. The default handling works but I have difficulties to inje

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

2016-02-13 Thread Tibor Digana
+1 On Wed, Feb 10, 2016 at 9:19 PM, Karl Heinz Marbaise wrote: > Hi, > > We solved 18 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12331545 > > There are no issues left in JIRA... > > Staging repo: > https://repository.apache.org/content/repositor

Re: [VOTE] Release Apache Maven Doxia Sitetools version 1.7

2016-02-13 Thread Petar Tahchiev
Hello, +1 from me. Looks good :) 2016-02-13 12:26 GMT+02:00 Karl Heinz Marbaise : > Hi, > > checked SHA1 Ok. > > Tested to build with Maven 3.0.5, 3.1.1, 3.2.5, 3.3.9 without any issue > > so +1 from me... > > Kind regards > Karl Heinz Marbaise > > > On 2/11/16 11:35 PM, Hervé BOUTEMY wrote: > >

Re: [VOTE] Release Apache Maven Doxia Sitetools version 1.7

2016-02-13 Thread Karl Heinz Marbaise
Hi, checked SHA1 Ok. Tested to build with Maven 3.0.5, 3.1.1, 3.2.5, 3.3.9 without any issue so +1 from me... Kind regards Karl Heinz Marbaise On 2/11/16 11:35 PM, Hervé BOUTEMY wrote: Hi, We solved 38 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12330653&styleName

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

2016-02-13 Thread Karl Heinz Marbaise
Hi, here is my +1 and there are missing some VOTES... Kind regard Karl Heinz Marbaise On 2/10/16 9:19 PM, Karl Heinz Marbaise wrote: Hi, We solved 18 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12331545 There are no issues left in JIRA... Stag

Some interesting thoughts on project dependency models

2016-02-13 Thread Stephen Connolly
https://medium.com/@sdboyer/so-you-want-to-write-a-package-manager-4ae9c17d9527#.mnt09gdr7 I like the lock file concept... Would it make ranges actually useful for maven? That is, leave the version range in the pom, have the resolved version in the lock file that gets checked in and published to