developing m1 and m2 plugins relying on m2 api

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

developing m1 and m2 plugins relying on m2 api

Gilles Dodinet
hi-

i'd like to know if it would be possible to upload m2 libraries to an
m1-friendly repository. should i create a jira entry for this ?

i'll try  to explain my needs in case i took the wrong approach: i'm
writing a plugin which i'd like to be both m1 and m2 compliant. so i
have three modules : core, m1 and m2, core relies on m2 api (f.i.
MavenProject) and m1 provides taglib which  converts relevant parts into
m2 compatible objects which are then passed to core entities. now the
issue is that i cannot build the m1 plugin w/o explicitly installing m2
libs into the m1 repo. any idea,  suggestion, best practice ?

on the same topic, is there a tool to convert a m1 Project instance into
an (eventually incomplete) m2 MavenProject instance ?

thanks !

-- gd

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: developing m1 and m2 plugins relying on m2 api

brettporter
Administrator
Gilles Dodinet wrote:

> hi-
>
> i'd like to know if it would be possible to upload m2 libraries to an
> m1-friendly repository.

yes, we want to get to the point that everything gets into both. Well,
actually the point to get to is to allow Maven 1.1 to use the new repo
so we can start looking at getting rid of the old one :)

> should i create a jira entry for this ?

yes, that's the easiest way. Use the MEV or MAVENUPLOAD projects.

> i'll try  to explain my needs in case i took the wrong approach: i'm
> writing a plugin which i'd like to be both m1 and m2 compliant. so i
> have three modules : core, m1 and m2, core relies on m2 api (f.i.
> MavenProject) and m1 provides taglib which  converts relevant parts
> into m2 compatible objects which are then passed to core entities. now
> the issue is that i cannot build the m1 plugin w/o explicitly
> installing m2 libs into the m1 repo. any idea,  suggestion, best
> practice ?

This sounds like the right way. Incidentally, m2 should be able to build
an m1 plugin for you, so that might be an option to be able to use m2
all round (if that is what you want).

>
> on the same topic, is there a tool to convert a m1 Project instance
> into an (eventually incomplete) m2 MavenProject instance ?

Sort of. The 'repoclean' project in the sandbox contains the most up to
date code for converting models (you still need to pass that model to
the MavenProjectBuilder to create a MavenProject though).

Cheers,
Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: developing m1 and m2 plugins relying on m2 api

Gilles Dodinet
Brett,

thanks for your reply.  if m2 can generate the m1 plugin for me, then
there's no point anymore to code it :) sadly i ve begun with core and m1
part. anyway i think this removes the need for repo synchronization at
the moment.

regards,

-- gd

Brett Porter wrote:

>Gilles Dodinet wrote:
>
>  
>
>>hi-
>>
>>i'd like to know if it would be possible to upload m2 libraries to an
>>m1-friendly repository.
>>    
>>
>
>yes, we want to get to the point that everything gets into both. Well,
>actually the point to get to is to allow Maven 1.1 to use the new repo
>so we can start looking at getting rid of the old one :)
>
>  
>
>>should i create a jira entry for this ?
>>    
>>
>
>yes, that's the easiest way. Use the MEV or MAVENUPLOAD projects.
>
>  
>
>>i'll try  to explain my needs in case i took the wrong approach: i'm
>>writing a plugin which i'd like to be both m1 and m2 compliant. so i
>>have three modules : core, m1 and m2, core relies on m2 api (f.i.
>>MavenProject) and m1 provides taglib which  converts relevant parts
>>into m2 compatible objects which are then passed to core entities. now
>>the issue is that i cannot build the m1 plugin w/o explicitly
>>installing m2 libs into the m1 repo. any idea,  suggestion, best
>>practice ?
>>    
>>
>
>This sounds like the right way. Incidentally, m2 should be able to build
>an m1 plugin for you, so that might be an option to be able to use m2
>all round (if that is what you want).
>
>  
>
>>on the same topic, is there a tool to convert a m1 Project instance
>>into an (eventually incomplete) m2 MavenProject instance ?
>>    
>>
>
>Sort of. The 'repoclean' project in the sandbox contains the most up to
>date code for converting models (you still need to pass that model to
>the MavenProjectBuilder to create a MavenProject though).
>
>Cheers,
>Brett
><
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
>
>
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]