Hi Robert,

 

Thanks for the info, I wasn't aware of this wiki page.

 

I pushed a fix of MDEPLOY-212 and MDEPLOY-213 using this idea in a forked 
repository of maven-plugins here https://github.com/Tunaki/maven-plugins/. All 
the IT still pass (expect from MDEPLOY-181 that is expected to fail) but I'd 
like to have a quick review before committing in trunk.

 

Thanks,

Guillaume

 

> Message du 22/07/16 19:58
> De : "Robert Scholte" 
> A : "Maven Developers List" 
> Copie à : 
> Objet : Re: Deprecation of ArtifactFactory and its use in new code
> 
> Hi Guillaume,
> 
> we have a wiki[1] describing most of the steps that need to be taken.
> Especially the ArtifactFactory is a tricky one. For deploying a 
> MavenProject (deploy:deploy) it should be straight forward.
> For deploying files (deploy:deploy-file) it is probably better to 
> translate it all back to new instance of a MavenProject, attach extra 
> artifacts with the MavenProjectHelper. If I'm correct in that case there's 
> no need for the ArtifactFactory anymore.
> 
> Robert
> 
> [1] 
> https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies
> 
> On Fri, 22 Jul 2016 00:54:09 +0200, Guillaume Boué  
> wrote:
> 
> > Hi,
> >
> > 
> > While working on a fix for 
> > https://issues.apache.org/jira/browse/MDEPLOY-212, I found out that the 
> > plugin is using the interface ArtifactFactory (Maven Core), that was 
> > deprecated as of Maven 3. The fix would need to utilize this class in 
> > order to create artifacts but this would add deprecation warnings.
> >
> > 
> > Am I right in saying that this was replaced by RepositorySystem? Should 
> > this one be used for new commit code or is there a plan to fix all of 
> > the deprecation in the future? I'm not sure of all the possible 
> > compatibility consequences of using this interface instead of 
> > ArtifactFactory.
> >
> > 
> > Additionally, I couldn't find a JIRA issue about the correction of those 
> > deprecation (only https://issues.apache.org/jira/browse/MNG-5782 
> > suggesting improving the doc about it): should one be created?
> >
> > 
> > Thanks,
> >
> > Guillaume
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
>

Reply via email to