Return-Path: X-Original-To: apmail-maven-dev-archive@www.apache.org Delivered-To: apmail-maven-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 32FC717A89 for ; Sun, 8 Mar 2015 10:42:07 +0000 (UTC) Received: (qmail 51846 invoked by uid 500); 8 Mar 2015 10:42:06 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 51766 invoked by uid 500); 8 Mar 2015 10:42:06 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 51753 invoked by uid 99); 8 Mar 2015 10:42:06 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Mar 2015 10:42:06 +0000 Received: from robertscholte.dynamic.ziggo.nl (5248749D.cm-4-1b.dynamic.ziggo.nl [82.72.116.157]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id E70041A02E4 for ; Sun, 8 Mar 2015 10:42:05 +0000 (UTC) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Maven Developers List" Subject: Re: Maven Compat + Maven 3.0 Plugin Part 1: Mercury References: Date: Sun, 08 Mar 2015 11:42:01 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Robert Scholte" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.17 (Win32) Seems like we need the same kind of solution as done with the Dependency= = Tree. I've introduced a new shared component: maven-artifact-transfer At least the following plugins are nominated to use this: maven-install-plugin maven-deploy-plugin maven-invoker-plugin thanks, Robert Op Sat, 07 Mar 2015 16:04:41 +0100 schreef Robert Scholte = : > Hi, > > when we start requiring Maven 3.0 for our plugins, IMO they should all= = > work *without* depending on Maven Compat. > I've tried to do this for the maven-invoker-plugin and hit the first = > issue. > They all have to do with artifacts: ArtifactInstaller, = > ArtifactRepository, ArtifactRepositoryFactory, ArtifactResolver. > The original code doesn't describe what to do, but after some digging = I = > found this: > > https://cwiki.apache.org/confluence/display/MAVEN/Compatibility+with+M= aven+2.x > > bq. > Maven Artifact > = > Maven Artifact will be entirely extricated from the core of Maven 3.x= = > and replaced with Mercury, but we will make a best effort to > ensure the compatibility of plugins that use Maven Artifact. There = > are, however, components and classes that are just so broken or confli= ct > with standard ways of doing resolution and conflict reduction that w= e = > can't support them. > = > Supported Compatibility > =E2=80=A2org.apache.maven.artifact.deployer.ArtifactDeployer > =E2=80=A2org.apache.maven.artifact.factory.ArtifactFactory > =E2=80=A2org.apache.maven.artifact.handler.ArtifactHandler > =E2=80=A2org.apache.maven.artifact.installer.ArtifactInstaller > =E2=80=A2org.apache.maven.artifact.manager.WagonManager (1) > =E2=80=A2org.apache.maven.artifact.repository.ArtifactRepository > =E2=80=A2org.apache.maven.artifact.repository.ArtifactRepositoryPolic= y > =E2=80=A2org.apache.maven.artifact.repository.ArtifactRepositoryFacto= ry > =E2=80=A2org.apache.maven.artifact.repository.layout.ArtifactReposito= ryLayout > =E2=80=A2org.apache.maven.artifact.resolver.ArtifactResolver > =E2=80=A2org.apache.maven.artifact.resolver.filter.ArtifactFilter > =E2=80=A2org.apache.maven.artifact.resolver.filter.Artifact > = > (1) In r746285 various methods have been removed from the WagonManage= r = > which breaks the maven-project-info-reports-plugin, the > maven-site-plugin and the maven-stage-plugin, e.g. due to a linkage = = > error on getAuthentaticationInfo(). > = > Unsupported Compatibility > =E2=80=A2org.apache.maven.artifact.metadata.ArtifactMetadataSource > =E2=80=A2org.apache.maven.artifact.metadata.ResolutionGroup > =E2=80=A2org.apache.maven.artifact.repository.metadata.* > =E2=80=A2org.apache.maven.artifact.resolver.ResolutionNode > =E2=80=A2org.apache.maven.artifact.resolver.ResolutionListener > =E2=80=A2org.apache.maven.artifact.resolver.metadata.* > =E2=80=A2org.apache.maven.artifact.resolver.transform.* > =E2=80=A2org.apache.maven.artifact.resolver.versioning.* > > > Mercury? I guess some of it is now part of Aether, but I think we shou= ld = > keep the abstraction layer (remember the issues we got Aether moved fr= om = > Sonatype to Eclipse and the amount of workarounds). > What to do? Move them back, make new APIs for Maven4, like = > ArtifactTransferor? > > My first conclusion is that we can't make these plugins Maven3 = > compatible without the maven-compat, unless we embed the classes in th= e = > plugin. > > thanks, > Robert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org > For additional commands, e-mail: dev-help@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org