Re: [tycho-user] FW: Cannot find layout implementation error using mvn 3

[Warwick Burrows <warwick.burrows@xxxxxxxxxx>]

We definitely will do that but we don't have the resources to make the switch at this time.  We have a entire "local" deployment configuration for our product built around proprietary plugins built for mvn 2 and our build team are best suited to getting all that cleanly ported to mvn 3.  I'm looking for something that I can do quickly just to be able to reference these plugins in the mvn 2 build.

Thanks,
Warwick


-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Dahanne, Anthony
Sent: Friday, November 18, 2011 3:19 PM
To: Tycho user list
Subject: Re: [tycho-user] FW: Cannot find layout implementation error using mvn 3 and tycho artifacts with mvn 2

What are your reasons for not switching to maven 3 ? it is stable and is the current version maintained.



 
Le contenu de ce courriel s'adresse au destinataire seulement. Il contient de l'information pouvant être confidentielle. Vous ne devez ni le copier ni l'utiliser ni le divulguer à qui que ce soit à moins que vous soyez le destinataire ou une personne désignée autorisée. Si vous le receviez par erreur, veuillez nous aviser immédiatement et le détruire.
 
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
 

De : tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] De la part de Warwick Burrows
Envoyé : 18 novembre 2011 16:17
À : Tycho user list
Objet : Re: [tycho-user] FW: Cannot find layout implementation error using mvn 3 and tycho artifacts with mvn 2

Ok thanks for the clarification.  So then is it possible to configure mvn 2 to understand p2 layouts with a plugin?  Is it possible to backport the plugin in mvn 3 to mvn 2.  Or maybe there's a switch for tycho, or mvn 3, to produce artifacts in a format mvn 2 can work with?  

Thanks


-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Alex Blewitt
Sent: Friday, November 18, 2011 3:09 PM
To: Tycho user list
Cc: Tycho user list
Subject: Re: [tycho-user] FW: Cannot find layout implementation error using mvn 3 and tycho artifacts with mvn 2

This is correct. Mvn 2 doesn't understand P2 layouts, and it is trying to download the jar and its Pom.xml to acquire its dependencies. Since it doesn't know how to proceed the build fails. 

Alex 

Sent from my iPhone 4S

On 18 Nov 2011, at 20:23, Warwick Burrows <warwick.burrows@xxxxxxxxxx> wrote:

> Hi, 
> 
> I'm very new to maven and tycho. I first asked this question on the maven list but was redirected here.  I'm getting error messages trying to reference an artifact that was built with mvn 3 and tycho in an mvn 2 build.  The mvn 2 build doesn't use tycho and uses the mvn 3 artifact as a build dependency.  The artifacts are deployed to a common maven repo (archiva) by mvn 3 but it seems that the format they are deployed in isn't recognized by mvn 2, or maybe its the artifacts at eclipse that my plugin references that aren't recognized?  e.g. When the maven 2 build runs and tries to fetch the artifact I get this:
> 
> Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'com.e2open.sitoolkit.mse:com.e2open.sitoolkit.mse.model:jar': Cannot find layout implementation corresponding to: 'p2' for remote repository with id: 'helios'. for project com.e2open.sitoolkit.mse:mse 
>     at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:200) 
> 
> build 15-Nov-2011 18:21:16 Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayoutp2. 


> build 15-Nov-2011 18:21:16  at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323) 
> build 15-Nov-2011 18:21:16  at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) 
> build 15-Nov-2011 18:21:16  at org.apache.maven.project.ProjectUtils.getRepositoryLayout(ProjectUtils.java:153) 
> build 15-Nov-2011 18:21:16  ... 33 more 
> 
> Where I have seen references to this problem the answer has been to use mvn 3 but that was because the users have been building an mvn 3 source tree with mvn 2.  In my case its a little different in that I want to reference mvn 3/tycho artifacts in an mvn 2 build.  So with all that background...  is there a way that mvn2 can use these artifacts. e.g.  Is there a tycho "p2" layout implementation plugin I can add to mvn 2?  Or is there a way to deploy the artifacts from the mvn 3/tycho build in a way that will be compatible with mvn2? 
> 
> Thanks, 
> Warwick 
> 
> 
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user