Am 12/11/16 um 22:56 schrieb Michael Osipov:
> I just ran ITs with current master, only one IT fails:
Should be fixed now.
Regards,
--
Christian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
Am 12/12/16 um 00:51 schrieb Igor Fedorenko:
> I'm traveling until next weekend and won't be able to review your changes
> properly until I'm back. I do want to stress that maven plugins are not
> dependencies, they are resolved the same way as projects.
Yes. I agree to that. It's not
I'm traveling until next weekend and won't be able to review your changes
properly until I'm back. I do want to stress that maven plugins are not
dependencies, they are resolved the same way as projects.
--
Regards,
Igor
On December 11, 2016 1:59:39 PM Christian Schulte
There's a pull request waiting for review by resolver experts:
https://github.com/apache/maven-resolver/pull/2
https://issues.apache.org/jira/browse/MRESOLVER-7
This is a recap of a PR I originally submitted last year, which has been
pending while Aether move from Eclipse to ASF was in
Can someone please take a look at that build job. It is failing with
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "main"
for quite some time now.
Regards,
--
Christian
-
To
Do we want to deploy a 'maven-aether-provider' relocating to
'maven-resolver-provider'?
Regards,
--
Christian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Can someone please take a look at this and verify the changes are
correct? I am not sure the former artifacts also need to be exported.
For the sonatype ones the package names are different. For the eclipse
ones the package names are identical. Not sure, though.
org.eclipse.aether:aether-api
Thanks. Noticed this myself yesterday. Wanted to wait for Jenkins to
finish all pending jobs. Haven't expected any IT to fail. Will have a look.
Am 12/11/16 um 22:56 schrieb Michael Osipov:
> Am 2016-12-10 um 16:06 schrieb Christian Schulte:
>> If it's happening just due to the upgrade of the
Am 2016-12-10 um 16:06 schrieb Christian Schulte:
If it's happening just due to the upgrade of the resolver, then it's a
resolver bugfix the IT hasn't been updated to reflect. I discussed this
issue with Jason in december last year when upgrading the resolver to
1.1 needed to be reverted.
Hi
I am planning to stage maven-wagon-2.11 tomorrow night US Pacific time.
Let me know if you need me to wait
Thanks
-Dan
Am 12/11/16 um 03:29 schrieb Igor Fedorenko:
> Why do you say Dependency A is transitive? Maven plugin directly depends
> on Dependency A, so I expect it to be present on the plugin classpath.
> This is consistent with how project direct optional dependencies are
> always present on classpath.
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/114
@Fuud
You mean this PR does not pass on Win or the master origin?
Please see our Jenkins on Windows. It passed
https://builds.apache.org/job/maven-surefire-windows
---
If your
I agree since it helps improving the code clarity but currently I cannot do
it because I am preparing a new release and several commits are pending.
On Sat, Dec 10, 2016 at 8:08 PM, Benedikt Ritter [via Maven] <
ml-node+s40175n5888093...@n5.nabble.com> wrote:
> Hello,
>
> at the moment the
13 matches
Mail list logo