Hi,
after going through the git history i found several contributors which
are currently not mentioned and issue which have been fixed without an
JIRA issue...
I will update the list within the next days...
And of course i will the VOTErs for the Release as well...
Kind regards
Karl Heinz
I took a look and added a test. Can you see if master
(f684761dee739b4ec8a7e6db5a0a6a0b809e66c9) fixes your issue?
> On Oct 29, 2015, at 5:21 PM, Igor Fedorenko wrote:
>
> -1
>
> 3.3.7 fails with string-index-out-of-range exception when parent pom has
> scm and I assume other elements with emp
-1
3.3.7 fails with string-index-out-of-range exception when parent pom has
scm and I assume other elements with empty child
I think the problem was introduced with recent changes in
DefaultInheritanceAssembler, at least the problem goes away if I replace
the class with the pre
The Apache Maven team is pleased to announce the release of the Apache Maven
JDeps Plugin, version 3.0.0
The JDeps Plugin uses the jdeps tool to analyze classes for internal API
calls. For more information about the standard jdeps tool, please refer to
Java+Dependency+Analysis+Tool.
http://m
Hi,
The vote has passed with the following result:
+1 : Arnaud Héritier, Jason van Zyl, Olivier Lamy, Robert Scholte, Tamás
Cservenák, Andreas Gudian, Hervé Boutemy
PMC quorum: Arnaud Héritier, Jason van Zyl, Olivier Lamy
I will promote the artifacts to the central repo.
--
here is my +1
Regards,
Hervé
Le lundi 26 octobre 2015 23:21:10 Hervé BOUTEMY a écrit :
> Hi,
>
> This is the first release of this new plugin.
> The JDeps Plugin uses the jdeps tool to analyze classes for internal API
> calls. For more information about the standard jdeps tool, please refer to
On 29 Oct 2015, at 19:13, Stephen Connolly wrote:
> FYI Mark, your vote is binding as a contributor... i.e. if you voted
> -1 the release manager would have to consider aborting the release,
> your vote just does not provide one of the three required +1's by PMC
*nod* I think I implicitly adopted
Tried out with a couple of projects that contributed to burning two of the
previous release attempts plus a couple more. All good!
+1
2015-10-29 23:37 GMT+02:00 jieryn :
> Tested with a few projects, I see no issues with this release. Thank you,
> +1 non-binding.
> On Oct 29, 2015 17:15, "Tamás C
Tested with a few projects, I see no issues with this release. Thank you,
+1 non-binding.
On Oct 29, 2015 17:15, "Tamás Cservenák" wrote:
> +1 beer
>
> On Thu, Oct 29, 2015, 21:29 Andreas Gudian
> wrote:
>
> > It's a smooth ride. Here's my +1 ... not legally, but morally binding ;)
> >
> > 2015-
+1 beer
On Thu, Oct 29, 2015, 21:29 Andreas Gudian wrote:
> It's a smooth ride. Here's my +1 ... not legally, but morally binding ;)
>
> 2015-10-28 14:30 GMT+01:00 Jason van Zyl :
>
> > Hi,
> >
> > Time to release Maven 3.3.7!
> >
> > Here is a link to the issues resolved:
> >
> >
> https://issu
It's a smooth ride. Here's my +1 ... not legally, but morally binding ;)
2015-10-28 14:30 GMT+01:00 Jason van Zyl :
> Hi,
>
> Time to release Maven 3.3.7!
>
> Here is a link to the issues resolved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12333074
>
>
+1 :)
2015-10-29 15:19 GMT+01:00 Tamás Cservenák :
> +1
>
> On Wed, Oct 28, 2015 at 5:28 PM Robert Scholte
> wrote:
>
> > +1
> > Robert Scholte
>
+1
On Wed, Oct 28, 2015 at 5:28 PM Robert Scholte
wrote:
> +1
> Robert Scholte
GitHub user partis opened a pull request:
https://github.com/apache/maven-scm/pull/40
Upadate StartteamTagCommand.java
Update to fix bug around tagging by inverting the logic around empty
fileset. Same change as has been made to the svn provider.
You can merge this pull request int
BTW, the following issues should be marked as fixed in Maven 3.3.7 due to the
upgrade to Sisu 0.3.2:
https://issues.apache.org/jira/browse/MNG-5440
https://issues.apache.org/jira/browse/MPLUGIN-271
Another thing that might be worth mentioning is that Maven now uses the
official Guice 4.0 rele
+1 to that suggestion also
On 29 October 2015 at 10:08, Mark Derricutt wrote:
> On Thu, Oct 29, 2015 at 7:39 PM, Karl Heinz Marbaise
> wrote:
>
>> WDYT
>
>
> With regards to the other email to the list regarding non-binding voting,
> would it be worth including those who voted on the release not
On Thu, Oct 29, 2015 at 7:39 PM, Karl Heinz Marbaise
wrote:
> WDYT
With regards to the other email to the list regarding non-binding voting,
would it be worth including those who voted on the release notes as well,
giving visibility to those who 'contribute' by way of testing?
Mark
--
"Great
To give some context.
Before the project can release code under the protection of the
foundation, there must be three +1 votes by members of the PMC.
The legal requirement for invoking the protection of the foundation
says nothing about how many -1 votes there are. In fact we could have
a release
18 matches
Mail list logo
