Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Subject: Re: Preleminary Maven 3.4.0-SNAPSHOT Testing
To: Maven Users List <users@maven.apache.org>
References: <5b57fe47-9869-6879-a828-c489ac62746a@gmx.de>
 <56c2a41f-6e55-13de-95fb-a39f61ff2339@swe-blog.net>
 <575DCF68.9080904@schulte.it>
 <97a368d2-2a40-082f-0480-71ac750447e0@swe-blog.net>
 <CABLGb9xQMm8vxA3U9w6MP-eQoTPeJ7P6RRTOPFDQywL=i=Z_mg@mail.gmail.com>
 <f794858a-3aca-bb6b-bcdd-1f1335bb14e0@swe-blog.net>
 <57685EB7.50804@apache.org>
From: "Oliver B. Fischer" <o.b.fischer@swe-blog.net>
Message-ID: <577e4f6a-4a08-b213-18b1-bf8cfae55583@swe-blog.net>
Date: Sat, 2 Jul 2016 12:36:01 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <57685EB7.50804@apache.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Sat, 02 Jul 2016 10:36:15 -0000

My suggestions is based on the view of a Maven user who would like to do 
it's daily job ;-)

In our team we have > 20 Maven projects and as a Maven 'User' you need 
the chance to fix such issues before the break your build. Everyone 
would blame Maven for this. We should have the chance to fix these 
problems before they become serious.

WDYT?

Oliver

Am 20.06.16 um 23:23 schrieb Christian Schulte:
> Am 06/20/16 um 22:00 schrieb Oliver B. Fischer:
>> Yes, I think this  would be very helpfull. Otherwise I see a lot of
>> people complaining about Maven and that is not able to do its work.
> Such warning messages could only be issued by Aether. That cannot be
> done in 3.4. We already reverted the things in question in 3.4 so that
> the issues you are running into no longer exist in 3.4 although it's
> really the other way around. There are issues in the project you could
> not notice because Maven makes those issues appear as correct behaviour.
> They will pop up again in a later Maven version. Maybe 3.5. No one knows
> right now. I ran a build of your project and just saw it will start
> throwing ClassNotFound related exceptions/compilation issues. Not having
> looked into any details. What is written here
> <http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html>
> is what Maven is aiming to adhere to. If we find a bug which makes it
> behave differently, we need to fix that on our side. The sooner the
> better so that people get a chance to notice as early as possible.
> That's what has happened. Current 3.4.0-SNAPSHOT should again support
> your project the way it did before. Does not solve the issues at hand.
> You can always download a recent Maven SNAPSHOT from
> <https://builds.apache.org/view/All/job/maven-3.3-release-status-build/>. It
> would help a lot if people would be using such a SNAPSHOT more
> frequently so that we can sort out things more efficiently. Also helps
> to find out what to focus in the release notes.
>
>
> Regards,

-- 
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org