Am 03/21/17 um 19:44 schrieb Hervé BOUTEMY:
> -1
>
> see MNG-5164
Thanks for pointing this out. I closed the issue "Won't Fix" and flagged
it a duplicate of MNG-5164. Branch is dropped. This would have went
unnoticed into the 3.4.0 release :-).
Regards,
--
Christian
Github user sesuncedu commented on the issue:
https://github.com/apache/maven-indexer/pull/16
I have changed the package version for index-reader to 5.2.0, since there
is a minor level change from 5.1.2.snapshot.
---
If your project is set up for it, you can reply to this email
Github user sesuncedu commented on the issue:
https://github.com/apache/maven-indexer/pull/13
I have changed the package version for the indexer to 5.2.0 because there
are minor changes from prior 5.1.2.SNAPSHOT versions. The overall 5.x release
version might want to skip to 5.1.3
-1
see MNG-5164
Regards,
Hervé
Le mardi 21 mars 2017, 18:20:21 CET schu...@apache.org a écrit :
> [MNG-6113] Rename the 'Central Repository' to 'Maven Central Repository' in
> the 4.0.0 super POM.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/maven/repo
> Commit:
Hi,
tested with several project also a large OSGi build ...without any issue..
+1 from me.
Kind regards
Karl Heinz Marbaise
On 20/03/17 19:18, Stephen Connolly wrote:
Hi,
We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339665=Text
There are
Hi,
look here https://github.com/apache/maven
maven-aether-provider has been moved to maven-resolver-provider
so simply delete maven-aether-provider directory first (git didn't clean
target directory)
On 22 March 2017 at 15:16, Mark Derricutt
wrote:
> Hey all,
>
> I
>>Question is: How to decide which commits/JIRA
issues will be merged to master for the next release?
Usually I respect the Jira priority, e.g. blocker or critical or I change
the priority, and then those issues are preferable which necessarily must
change the architecture first due to other Jira
GitHub user trajano opened a pull request:
https://github.com/apache/maven-plugins/pull/108
Updated dependencies
Key upgrade was the maven-invoker-plugin which prevented execution on
current version of Maven due to change from mvn.bat to mvn.cmd
Code change to
Hey all,
I was about to start testing the beta-1 release when I noticed my nightly
snapshots were out of date by a month or so (not so nightly ).
Looking at my builds I see:
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
(rat-check) on project maven: Too many