[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5834) Move to m2eclipse 0.10

[Nick Boldt (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12514578#action_12514578 ] 

Nick Boldt commented on JBIDE-5834:
-----------------------------------

DONE: repo aggregation script & p2.inf files for maven and maven.seam features now point at new m2e sites instead of temporary one

TODO: switch build to use p2 repo or newer repo2runnable-converted zip, pulled from new m2e update site(s) (rather than the snapshot that Sneja built last week)



> Move to m2eclipse 0.10
> ----------------------
>
>                 Key: JBIDE-5834
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5834
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: maven
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 3.1.0.CR2
>
>
> m2eclipse have decided to release m2eclipse 0.10 which has different plugin names/ids causing a breakage in compatibility.
> The challenge is though that m2eclipse 0.10 is not available yet from an updatesite.
> To make sure we work with upcoming m2eclipse and not have to go through loops during 3.1.x update cycle and to encapsulate us from the yet to be released 0.10 the suggestion from snjezana is:
>  If we want to use 0.10, we need to do the following:
> [8:20:04 PM] Snjezana Peco: - add m2eclipse 0.10 driver to the build
> [8:20:47 PM] Snjezana Peco: - commit the changes in the JBT Maven plugins
> [8:22:03 PM] Snjezana Peco: - create a temporary update site for m2eclipse 0.10 (it is already 0.10.1 in the trunk)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira