Kosta has a very good point here:
moberhuber@build:/home/data/httpd/download.eclipse.org/releases/juno/201302220900<mailto:moberhuber@build:/home/data/httpd/download.eclipse.org/releases/juno/201302220900>>
unzip -p content.jar | egrep 'unit id=|required.*eclipse..git' | grep -B 10
'required.*git.*2\.3' | less
<unit id='org.eclipse.mylyn.github.core' version='2.3.0.201302130906'>
<required namespace='java.package' name='org.eclipse.egit.core'
range='[2.3.0,2.4.0)'/>
<required namespace='java.package' name='org.eclipse.egit.github.core'
range='[2.3.0,2.4.0)'/>
[…]
<unit id='org.eclipse.mylyn.github.ui' version='2.3.0.201302130906'>
<required namespace='java.package' name='org.eclipse.egit.core'
range='[2.3.0,2.4.0)'/>
<required namespace='java.package' name='org.eclipse.egit.core.op'
range='[2.3.0,2.4.0)'/>
[…]
<unit id='org.eclipse.egit.mylyn.ui' version='2.3.0.201302130906'>
<required namespace='java.package' name='org.eclipse.egit.core'
range='[2.3.0,2.4.0)'/>
<required namespace='java.package'
name='org.eclipse.egit.core.synchronize' range='[2.3.0,2.4.0)'/>
That should be all dependencies onto egit-2.3.
I think that egit.mylyn.ui comes from egit itself, but where does the mylyn
github feature actually come from ?
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: [email protected]
[mailto:[email protected]] On Behalf Of Konstantin
Komissarchik
Sent: Friday, February 22, 2013 9:24 PM
To: 'Cross project issues'
Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay
one week, Friday 3/1
I hate to throw a stick in the spokes, but what happens if another project in
the aggregate repository already has a min dependency on EGit 2.2 or even 2.3?
- Konstantin
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Matthias
Sohn
Sent: Friday, February 22, 2013 12:15 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay
one week, Friday 3/1
2013/2/22 David M Williams
<[email protected]<mailto:[email protected]>>
After some painful conversation with the Planning Council members, the
conclusion was to delay the release 1 week, but not do a full respin, to only
revert the EGit contribution.
The plan is to redo the common repository and EPP packages, with the EGit
contribution reverted to what it was in SR1, which I believe is identical to
what it was in RC3. There are a few "technical tricks" I can try to accomplish
this, so all other projects do not have to do any re-work ... just wait until
Friday 3/1, before making your releases "visible".
no, SR2 RC3 contains EGit 2.2.0 [1] which was released in December and SR1
contains EGit 2.1.0
I'd prefer if you could rollback to 2.2.0 but if the planning council decided
otherwise be it like that.
[1]
https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?h=Juno_maintenance&id=e5209e06bfbe2284a96b1ce357b9fcd1053072d1
--
Matthias
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
