I need one more binding vote...
Regards,
Hervé
Le vendredi 4 juillet 2014 01:00:20 Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 13 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146&styleName=H
> tml&version=19228
>
> There are still a couple of issues left in JIRA:
> ht
What about a per groupId repo routing in settings.xml
I believe John started something. As it no pom change.
--
Olivier
On Jul 5, 2014 2:57 AM, "Robert Scholte" wrote:
> In addition to our hangout session: isn't it weird that for a dependency
> Maven can go over all the repositories, even though
If we did that - would it be to good to provide a basic/minimal "Maven
Repository Manager Daemon" as a standard part of Maven.
Eliminate the localRepo entirely ( something like this would actually be
useful in solving some cross-repository, non-multimodule-build
integration issues I'm trying t
That would in part align things with Aether's somewhat annoying/retarded
behaviour of saying "oh I see com.acme:special tool:1.0-alpha-1" but it
came from repo-1, not repo-2 - so "suck it up - I can't resolve this.".
I can understand the idea behind this - two artefacts from two different
repo
Github user a-horst commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-48114857
Alright, so with Robert's fix of the [IT]
(https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs%20(unstable)/job/core-it-maven-3-win/602/changes)
eventually all ITs s
Github user a-horst commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-48112720
Any news on this? FYI: I used ```cmd.exe``` and ```cygwin```.
I see that you fixed the IT on [Jenkins]
(https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs%2
