Bug 2758 - Update the output folder name of eclipse plugin from indigo to juno
Summary: Update the output folder name of eclipse plugin from indigo to juno
Status: RESOLVED FIXED
Alias: None
Product: Eclipse Plugin
Classification: Yocto Project Subprojects
Component: eclipse-plugin (show other bugs)
Version: 1.3
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.4 M2
Assignee: Beth Flanagan
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-07-13 05:48 UTC by Hongna Xu
Modified: 2013-02-26 16:16 UTC (History)
10 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hongna Xu 2012-07-13 05:48:38 UTC
hi, beth.juno eclipse is finally officially release on the end of june, so from 1.3 M2, we will use juno instead of indigo, please update the output folder name , thanks a lot.
Comment 1 Beth Flanagan 2012-07-16 15:48:30 UTC
We should look at doing this via the eclipse build scripts. The issue is that I have to maintain backwards compatibility with indigo builds and if I now have to check the git log (instead of the build script putting it in the right place in the first place) to figure out if it's indigo or juno, it's going to make a mess.
Comment 2 Jessica 2012-07-25 17:38:42 UTC
Per our discussion, please refer to setup.sh EP_VERSIOn to distinguish Indigo and Juno, Indigo should be 3.x and Juno should be 4.x
Comment 3 Beth Flanagan 2012-08-27 21:25:59 UTC
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=dd04d2dde867a60429480556c4a720ad612a6875

Leaving this open as a placeholder for the correct fix, but this solves most of the issue.
Comment 4 Beth Flanagan 2013-02-26 16:16:33 UTC
We won't be building indigo anymore. closing.