[jbosstools-issues] [JBoss JIRA] (JBIDE-14461) Update Kepler M7 target platforms to include EGit 3.0

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim commented on JBIDE-14461:
------------------------------------------

on the 8th of May EGit build a first EGit 3.0 that shall get contributed to Kepler M7:
http://dev.eclipse.org/mhonarc/lists/egit-dev/msg03127.html

{quote}
I created stable-3.0 branches and taggedÂ3.0.0.201305080800-m7 and contributed it to Kepler M7.

Find this version here:

Kepler staging p2 repository
http://download.eclipse.org/releases/staging

JGit/EGit p2 repository:
online
http://download.eclipse.org/egit/staging/v3.0.0.201305080800-m7
zip downloadÂ
http://download.eclipse.org/egit/staging/3.0.0.M7/org.eclipse.egit.repository-3.0.0.201305080800-m7.zip

EGit Github connector p2 repository:
online
http://download.eclipse.org/egit/github/staging/v3.0.0.201305080800-m7
zip download
http://download.eclipse.org/egit/staging/3.0.0.M7/github-updatesite-3.0.0.201305080800-m7.zip

JGit maven repository
http://download.eclipse.org/jgit/staging/3.0.0.M7/m2

Please help to test this version and report problems.

>From now on push any changes which should reach 3.0 to review for branch stable-3.0.

--
Matthias

{quote}
                
> Update Kepler M7 target platforms to include EGit 3.0
> -----------------------------------------------------
>
>                 Key: JBIDE-14461
>                 URL: https://issues.jboss.org/browse/JBIDE-14461
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: target-platform
>            Reporter: Max Rydahl Andersen
>            Assignee: Andre Dietisheim
>            Priority: Blocker
>             Fix For: 4.1.0.Beta1
>
>
> [~adietish] has requested we use EGit 3 instead of 2.3.1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira