1:04 p.m.
Nick Boldt created JBDS-2001:
--------------------------------
Summary: Investigate use of egit 1.3 in JBDS 5 and JBoss Central
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.M5
Reporter: Fred Bricon
Assignee: Len DiMaggio
Fix For: 5.0.0.Beta1
I've been using native svn 1.7 for a while now, Today while reinstalling a new Eclipse
installation from scratch, I installed subclipse from JBoss Central.
After installation, I tried to share my existing projects in eclipse but couldn't,
since the 1.7 checkout is not supported by subclipse (based on svn 1.6).
Can we update the subclipse version from central to use the 1.8.x stream?
With svn 1.7, you have only have one .svn folder at the root of your checkout, no more
.svn folders crawling everywhere making copying and moving folders a breathe.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:10 p.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2001:
-----------------------------
Description:
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
was:
I've been using native svn 1.7 for a while now, Today while reinstalling a new Eclipse
installation from scratch, I installed subclipse from JBoss Central.
After installation, I tried to share my existing projects in eclipse but couldn't,
since the 1.7 checkout is not supported by subclipse (based on svn 1.6).
Can we update the subclipse version from central to use the 1.8.x stream?
With svn 1.7, you have only have one .svn folder at the root of your checkout, no more
.svn folders crawling everywhere making copying and moving folders a breathe.
Affects Version/s: 5.0.0.Beta1
(was: 5.0.0.M5)
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Fred Bricon
Assignee: Len DiMaggio
Fix For: 5.0.0.Beta1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:16 p.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2001:
-----------------------------
Reporter: Nick Boldt (was: Fred Bricon)
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Fix For: 5.0.0.Beta1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:16 p.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Nick Boldt reassigned JBDS-2001:
--------------------------------
Assignee: Andre Dietisheim (was: Len DiMaggio)
Andre, need your +1, then bounce this to Len.
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Andre Dietisheim
Fix For: 5.0.0.Beta1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:08 a.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Andre Dietisheim commented on JBDS-2001:
----------------------------------------
I guess that it's a good habit to follow the latest and greatest since we'd then
get the lastest fixes.
The only pieces of informations I catched (no new and noteworthy published yet) were on
egit-dev and I catched the following new bug that one introduced in 1.3:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370132
On the other hand I guess we should also see if they fixed bugs that could justify us to
go upstream even with that new bug.
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Andre Dietisheim
Fix For: 5.0.0.Beta1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:24 a.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2001:
-----------------------------
Fix Version/s: 5.0.0.CR1
(was: 5.0.0.Beta1)
(2012-02-03 12:16:38) nickboldt: adietisheim1: your comments sound like a +0.5. Do you
want to move up, or wait for future nightly release and more investigation ?
(2012-02-03 12:18:55) adietisheim1: nickboldt: I guess the safe path would be to keep
sticking to 1.2
(2012-02-03 12:19:26) adietisheim1: nickboldt: i'd stick unless we have major bugfixes
in 1.3 but I can't find any changelog so far
12:20
(2012-02-03 12:20:06) adietisheim1: so for now I'd stay with 1.2
Bump to CR1.
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Andre Dietisheim
Fix For: 5.0.0.CR1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 p.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Andre Dietisheim commented on JBDS-2001:
----------------------------------------
in the meantime, the official egit release turned 1.3:
http://www.eclipse.org/egit/download/:
{quote}
Installing the Latest Release: 1.3.0.201202151440-r
{quote}
Guess it would be worth a try and see if things work as expected. Being on the latest egit
would most likely be a benefit for GA.
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Andre Dietisheim
Fix For: 5.0.0.CR1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:22 p.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Nick Boldt reassigned JBDS-2001:
--------------------------------
Assignee: Len DiMaggio (was: Andre Dietisheim)
Andre has +1'd the desire to move from egit 1.2 to 1.3. Len, need your +1 to proceed.
Do you need me to pull a mirror onto download.jboss.org, or can you test out egit 1.3 from
its eclipse.org site?
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Fix For: 5.0.0.CR1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:59 p.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Len DiMaggio commented on JBDS-2001:
------------------------------------
Hey Nick - yes - can you pull a mirror onto download.jboss.org? Thanks!
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Fix For: 5.0.0.CR1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:55 p.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2001:
----------------------------------
Here ya go:
http://download.jboss.org/jbosstools/updates/requirements/egit/1.3.0.2012...
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Fix For: 5.0.0.CR1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:59 a.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2001:
-------------------------------------------
what is the point to move up to egit 1.3 ?
We want to be sure Indigo users can work with this - and egit 1.3 is not default in Indigo
so there got to be a good reason for this.
-1 until such reason is provided.
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Fix For: 5.0.0.CR1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:29 a.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2001:
-------------------------------------------
I read the initial comments as egit 1.3 was in addition to indigo not that it was *part*
of Indigo.
Anyhow our ranges allow it to be installed but lets not update this while locking down for
GA without having a good/known reason for it.
After reading http://wiki.eclipse.org/EGit/New_and_Noteworthy/1.3 there are though 2
features which are nice, but we don't have a huge need for right now:
* submodules
* extendable clone wizard (would make sense to have OpenShift as a source here)
Question is if we should bump this now or wait?
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Fix For: 5.0.0.CR1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:31 a.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen updated JBDS-2001:
--------------------------------------
Priority: Critical (was: Major)
Andre reports 1.3 is the version he uses locally.
I'm inclined to say we should update if we have a JBDS feature that is locking that
feature down so users can't use it.
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Priority: Critical
Fix For: 5.0.0.CR1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:11 a.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Andre Dietisheim commented on JBDS-2001:
----------------------------------------
We currently have no required feature/bugfix that would force us to upgrade the required
version. I therefore kept us requiring 1.2.
Furthermore I removed the upper bounds that were excluding 2.0 since we have Juno ahead.
Juno M7 offers egit/jgit 1.3 on it's update site but I suspect that will change when
Juno gets final.
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Priority: Critical
Fix For: 5.0.0.CR1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:07 p.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2001:
-----------------------------
Fix Version/s: 5.0.1.GA
(was: 5.0.0.CR1)
Based on Andre's comments I'm slipping this to 5.0.1
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Priority: Critical
Fix For: 5.0.1.GA
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:54 p.m.
[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2001:
-----------------------------
Fix Version/s: 5.0.2.GA
(was: 5.0.1.GA)
Slip to 5.0.2
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Priority: Critical
Fix For: 5.0.2.GA
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5026
days inactive
5184
days old
jbosstools-issues@lists.jboss.org
15 comments
4 participants
participants (4)
-
Andre Dietisheim (JIRA) -
Len DiMaggio (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)