Community
Participate
Working Groups
Created attachment 210093 [details] Feature (package) and bundle (branding plug-in) projects for Eclipse IDE for Automotive Software Developers On behalf of the Eclipse Automotive Industry Working Group (IWG)[1], we would like to provide a new Eclipse package dedicated to developers of embedded control software in the automotive industry. Since its beginnings, Eclipse has been making inroads at automotive suppliers and manufacturers. Aiming at handling the development of modern and increasingly complex automotive software more accurately and efficiently, Eclipse has been adopted as platform for creating sophisticated in-house development tools and integrating those with commercial design tools to highly dedicated tool chains. With companies like BMW, Bosch and Continental having joined the Eclipse Foundation as official members, this tendency has significantly gained in momentum over the past years. In 2011, the Eclipse Automotive IWG has been founded [2] so as to federate and streamline Eclipse-related activities across company boundaries and work upon establishing Eclipse as the number one tool and tool integration platform in the automotive industry. One key activity of the Eclipse Automotive IWG is to define and provide an Eclipse Automotive Tools Platform consisting of selected existing Eclipse components that are frequently used in the automotive industry. The intention of this platform is to provide a reference for both vendors and users of Eclipse-based automotive software design tools and to enable the latter to be consistently and reliably integrated in user-defined tool chains. The implementation of the Eclipse Automotive Tools Platform includes a corresponding Eclipse package made available for download at Eclipse.org [3]. The name of the package is going to be "Eclipse IDE for Automotive Software Developers" which concisely describes the targeted audience and appears to be well aligned with names of existing Eclipse packages. In addition to Eclipse Platform, Java Development Tools, and Plug-in Development Environment, it will include EMF, GMF, Xtext, UML, selected other modeling components, C/C++ Development Tools, and XML/XSD editors and tools. It will bundle the complete SDKs, i.e., runtime binaries, source code, and documentation. [1] http://wiki.eclipse.org/Auto_IWG [2] http://www.eclipse.org/org/press-release/20110720_autoiwg.php [3] http://eclipse.org/downloads
Created attachment 210121 [details] Updated feature (package) and bundle (branding plug-in) projects for Eclipse IDE for Automotive Software Developers
Created attachment 210229 [details] Updated feature (package) and bundle (branding plug-in) projects for Eclipse IDE for Automotive Software Developers
Created attachment 210343 [details] Re-updated feature (package) and bundle (branding plug-in) projects for Eclipse IDE for Automotive Software Developers
Markus, is the information on the wiki regarding creating a new package up-to-date? http://wiki.eclipse.org/EPP/How_to_create_a_package
(In reply to comment #4) > Markus, is the information on the wiki regarding creating a new package > up-to-date? > > http://wiki.eclipse.org/EPP/How_to_create_a_package Yepp, especially the last paragraph about adding the parallel package is important for every new Juno package. I will be looking into this package for Juno M6.
(In reply to comment #5) > (In reply to comment #4) > > Markus, is the information on the wiki regarding creating a new package > > up-to-date? > > > > http://wiki.eclipse.org/EPP/How_to_create_a_package > > Yepp, especially the last paragraph about adding the parallel package is > important for every new Juno package. I will be looking into this package for > Juno M6. Might be a silly question, but is there any chance to get this into Indigo SR-2? If not, should the package product and feature attached to this bug be updated to Juno M5 (currently they are based on Indigo SR-1)? Is there any other action required from our side?
I am currently going through the attached projects for the Automotive Package. http://www.eclipse.org/downloads/images/automotive.png is referenced in eclipse_automotive_indigo.xml * can you provide an icon and attach it to this bug * then we can ask Nathan to upload it to the correct location I changed a few minor things, such as * renamed eclipse_automotive_indigo.xml to eclipse_automotive_juno.xml * removed the 'version' attribute in the feature.xml - in most cases it is enough to use the latest version from the Simultaneous Release * copyright date (2012 instead of 2011) * the version - all EPP Juno packages are currently build with version 1.5.0 * removed plugin_customization.ini from the feature (it's in the branding plug-in) * removed: <import feature="org.eclipse.epp.mpc.source" />
* Added org.eclipse.epp.package.automotive.feature to org.eclipse.epp.allpackages.juno.feature * feature and branding plug-in committed to Git: http://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/tree/packages
(In reply to comment #7) > http://www.eclipse.org/downloads/images/automotive.png is referenced in > eclipse_automotive_indigo.xml > * can you provide an icon and attach it to this bug Sure. This will take us some time however. Until when would you ideally need it? > I changed a few minor things, such as > > * renamed eclipse_automotive_indigo.xml to eclipse_automotive_juno.xml I guess that the <product name="eclipse-automotive-indigo-SR2" /> element in this file should also be changed. The same applies to <discovery label="Indigo" url="http://download.eclipse.org/releases/indigo/"/> in feature.xml. > * removed the 'version' attribute in the feature.xml - in most cases it is > enough to use the latest version from the Simultaneous Release > * copyright date (2012 instead of 2011) Ok. > * the version - all EPP Juno packages are currently build with version 1.5.0 Do you mean the versions in epp.product, feature.xml, eclipse_automotive_indigo.xml, and MANIFEST.MF of org.eclipse.epp.package.automotive? > * removed plugin_customization.ini from the feature (it's in the branding > plug-in) Sure. > * removed: <import feature="org.eclipse.epp.mpc.source" /> Will it be automatically included or not at all?
(In reply to comment #9) > (In reply to comment #7) > > http://www.eclipse.org/downloads/images/automotive.png is referenced in > > eclipse_automotive_indigo.xml > > * can you provide an icon and attach it to this bug > > Sure. This will take us some time however. Until when would you ideally need > it? *Ideally* until Friday when we have to release M6 ;-) But I think we can live without it for the time being, the package and its content are more important for now. > > I changed a few minor things, such as > > > > * renamed eclipse_automotive_indigo.xml to eclipse_automotive_juno.xml > > I guess that the <product name="eclipse-automotive-indigo-SR2" /> element in > this file should also be changed. > > The same applies to <discovery label="Indigo" > url="http://download.eclipse.org/releases/indigo/"/> in feature.xml. I did this already but forgot to mention it in the comment. > > * the version - all EPP Juno packages are currently build with version 1.5.0 > > Do you mean the versions in epp.product, feature.xml, > eclipse_automotive_indigo.xml, and MANIFEST.MF of > org.eclipse.epp.package.automotive? Yes, exactly. > > * removed: <import feature="org.eclipse.epp.mpc.source" /> > > Will it be automatically included or not at all? If there is a dependency somewhere then it would be included. In this particular case I don't think the source of MPC will be there. Speaking of the org.eclipse.epp.mpc feature: I just saw that the Automotive package didn't contain the org.eclipse.epp.package.common.feature yet (which includes the org.eclipse.epp.mpc feature). I've now replaced the org.eclipse.epp.mpc.feature with org.eclipse.epp.package.common.feature. That's a more general question: I've seen that this package consists of SDK features only. Most SDK features include source code and other pieces that are usually *not* required in a package but in a target environment. Without knowing the use cases for the Automotive Package, I doubt that all sources are required. Instead I think we should try to find the really required features which had the advantage that the package would be much smaller.
Maybe it is a temporary problem but the following feature is currently (2012-03-20) not available in /releases/staging. It could be that they are providing their feature at +2 or +3 days, or they have renamed this feature, or they are not providing anything at all for Juno. Can you find out the current status, Stephan? <import feature="org.eclipse.xtext.xtend2.sdk" /> For now, I've commented out this feature in order to get a running package build that includes the Automotive Package. Another problem is the Equinox executables feature. This is currently not provided by the team to the Simultaneous Release repository in /releases/staging (or /releases/juno). Therefore I had to disable this, too. If it is not possible for the Eclipse Platform/Equinox team to provide this via the Simultaneous Release repositories, we could implement this as a *workaround* in EPP, but first I'd like to learn the reasons of the Equinox team why they are not providing this feature. <import feature="org.eclipse.equinox.executable" />
(In reply to comment #11) > > Another problem is the Equinox executables feature. This is currently not > provided by the team to the Simultaneous Release repository in > /releases/staging (or /releases/juno). Therefore I had to disable this, too. If > it is not possible for the Eclipse Platform/Equinox team to provide this via > the Simultaneous Release repositories, we could implement this as a > *workaround* in EPP, but first I'd like to learn the reasons of the Equinox > team why they are not providing this feature. > > <import feature="org.eclipse.equinox.executable" /> Looks like "our" (platform) bug. I've opened bug 374768 ... but, will likely be 5 or 6 (Eastern) at earliest before fixed. (maybe midnight again :/
(In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #7) > > > http://www.eclipse.org/downloads/images/automotive.png is referenced in > > > eclipse_automotive_indigo.xml > > > * can you provide an icon and attach it to this bug > > > > Sure. This will take us some time however. Until when would you ideally need > > it? > > *Ideally* until Friday when we have to release M6 ;-) > But I think we can live without it for the time being, the package and its > content are more important for now. Ok, perfect. We'll make it available for M7 then. > > > * removed: <import feature="org.eclipse.epp.mpc.source" /> > > > > Will it be automatically included or not at all? > > If there is a dependency somewhere then it would be included. In this > particular case I don't think the source of MPC will be there. No, we definitely don't need the sources for this. > Speaking of the org.eclipse.epp.mpc feature: I just saw that the Automotive > package didn't contain the org.eclipse.epp.package.common.feature yet (which > includes the org.eclipse.epp.mpc feature). I've now replaced the > org.eclipse.epp.mpc.feature with org.eclipse.epp.package.common.feature. Ok, perfect. > That's a more general question: I've seen that this package consists of SDK > features only. Most SDK features include source code and other pieces that are > usually *not* required in a package but in a target environment. Without > knowing the use cases for the Automotive Package, I doubt that all sources are > required. Instead I think we should try to find the really required features > which had the advantage that the package would be much smaller. Hmm, yes and no. I see the implication wrt package size. But users of this package might want to use it for developing there own plug-ins/features on top of it, i.e. without a dedicated target platform. Aside from that, it looks that there are other packages that slightly derive from the "runtimes-only" policy, e.g., http://eclipse.org/downloads/packages/eclipse-modeling-tools/indigosr2 I suggest that we go with it as is for the time being and we readdress this topic in the Automotive IWG. We could then adjust the features for M7. How about that?
(In reply to comment #11) > Maybe it is a temporary problem but the following feature is currently > (2012-03-20) not available in /releases/staging. It could be that they are > providing their feature at +2 or +3 days, or they have renamed this feature, or > they are not providing anything at all for Juno. Can you find out the current > status, Stephan? > > <import feature="org.eclipse.xtext.xtend2.sdk" /> > > For now, I've commented out this feature in order to get a running package > build that includes the Automotive Package. That's strange. Xtend2 is actually a part of Xtext. The Juno version for both org.eclipse.xtext.sdk and org.eclipse.xtext.xtend2.sdk are originally provided in this update site: http://download.eclipse.org/modeling/tmf/xtext/updates/composite/milestones. So, my question is, is only Xtend2 missing or is Xtext also not there?
(In reply to comment #13) > > That's a more general question: I've seen that this package consists of SDK > > features only. Most SDK features include source code and other pieces that are > > usually *not* required in a package but in a target environment. Without > > knowing the use cases for the Automotive Package, I doubt that all sources are > > required. Instead I think we should try to find the really required features > > which had the advantage that the package would be much smaller. > > Hmm, yes and no. I see the implication wrt package size. But users of this > package might want to use it for developing there own plug-ins/features on top > of it, i.e. without a dedicated target platform. Aside from that, it looks that > there are other packages that slightly derive from the "runtimes-only" policy, > e.g., http://eclipse.org/downloads/packages/eclipse-modeling-tools/indigosr2 > > I suggest that we go with it as is for the time being and we readdress this > topic in the Automotive IWG. We could then adjust the features for M7. How > about that? M7 is fine with me but I really think it is worth a discussion because the first package build (even without the two missing features in comment 11) created an Automotive package with about 330MB - the biggest package so far! And it is always easier to start small (in Juno) and to enhance the package based on the requests from users. FYI: The Automotive Package is now included in all builds after 20120320-1505 from this URL: http://build.eclipse.org/technology/epp/epp_build/juno/download/ (In reply to comment #14) > (In reply to comment #11) > > <import feature="org.eclipse.xtext.xtend2.sdk" /> > > > > For now, I've commented out this feature in order to get a running package > > build that includes the Automotive Package. > > That's strange. Xtend2 is actually a part of Xtext. The Juno version for both > org.eclipse.xtext.sdk and org.eclipse.xtext.xtend2.sdk are originally provided > in this update site: > http://download.eclipse.org/modeling/tmf/xtext/updates/composite/milestones. > > So, my question is, is only Xtend2 missing or is Xtext also not there? At the moment I find these features in releases/staging/features; did they rename something? org.eclipse.xtend_1.2.1.v201203090226.jar org.eclipse.xtend.dependencies_1.2.1.v201203090226.jar org.eclipse.xtend.dependencies.source_1.2.1.v201203090226.jar org.eclipse.xtend.sdk_2.3.0.v201203090946.jar org.eclipse.xtend.source_1.2.1.v201203090226.jar org.eclipse.xtend.typesystem.emf_1.2.1.v201203090226.jar org.eclipse.xtend.typesystem.emf.source_1.2.1.v201203090226.jar org.eclipse.xtend.typesystem.uml2_1.2.1.v201203090226.jar org.eclipse.xtend.typesystem.uml2.source_1.2.1.v201203090226.jar org.eclipse.xtend.typesystem.xsd_1.2.1.v201203090226.jar org.eclipse.xtend.typesystem.xsd.source_1.2.1.v201203090226.jar org.eclipse.xtend.ui_1.2.1.v201203090226.jar org.eclipse.xtend.ui.source_1.2.1.v201203090226.jar org.eclipse.xtext.docs_2.3.0.v201203090946.jar org.eclipse.xtext.examples_2.3.0.v201203090946.jar org.eclipse.xtext.examples.source_2.3.0.v201203090946.jar org.eclipse.xtext.runtime_2.3.0.v201203090946.jar org.eclipse.xtext.runtime.source_2.3.0.v201203090946.jar org.eclipse.xtext.sdk_2.3.0.v201203090946.jar org.eclipse.xtext.ui_2.3.0.v201203090946.jar org.eclipse.xtext.ui.source_2.3.0.v201203090946.jar org.eclipse.xtext.xbase_2.3.0.v201203090946.jar org.eclipse.xtext.xbase.source_2.3.0.v201203090946.jar org.eclipse.xtext.xtext.ui_2.3.0.v201203090946.jar org.eclipse.xtext.xtext.ui.source_2.3.0.v201203090946.jar
Hi guys, > Maybe it is a temporary problem but the following feature is currently > (2012-03-20) not available in /releases/staging. It could be that they are > providing their feature at +2 or +3 days Xtext and Xtend are +2 projects Juno M6 contribution was completed today > or they have renamed this feature Yes, you are right. Xtend was moved to tools project. So org.eclipse.xtext.xtend2.sdk was renamed to org.eclipse.xtend.sdk > they are not providing anything at all for Juno. We do. > Can you find out the current > status, Stephan? The status is: org.eclipse.xtext.xtend2.sdk is deprecated. Use org.eclipse.xtend.sdk instead. > For now, I've commented out this feature in order to get a running package > build that includes the Automotive Package. > > So, my question is, is only Xtend2 missing or is Xtext also not there? > > At the moment I find these features in releases/staging/features; did they > rename something? Both projects are contributed to juno b3 aggregator job. And should be available right now. So use: org.eclipse.xtext.sdk org.eclipse.xtend.sdk Best regards, Dennis.
(In reply to comment #11) > <import feature="org.eclipse.xtend.sdk" /> > <import feature="org.eclipse.equinox.executable" /> Re-enabled both features.
Since I didn't see any response to comment 15 where I mention the download location: http://build.eclipse.org/technology/epp/epp_build/juno/download/ It's very likely that 20120322-1743 will be the final M6 build (currently building!). If you have some time to spend while you are preparing for EclipseCon, feel free to start testing. Another important thing that I forgot to mention so far: Please subscribe to the epp-dev mailing list, because all package maintainers must be responsible to test requests sent to this list.
(In reply to comment #18) > Since I didn't see any response to comment 15 where I mention the download > location: > > http://build.eclipse.org/technology/epp/epp_build/juno/download/ > > It's very likely that 20120322-1743 will be the final M6 build (currently > building!). If you have some time to spend while you are preparing for > EclipseCon, feel free to start testing. Ok. > Another important thing that I forgot to mention so far: Please subscribe to > the epp-dev mailing list, Already done. > because all package maintainers must be responsible > to test requests sent to this list. No such received so far. Or have I missed anything?
(In reply to comment #19) > > Another important thing that I forgot to mention so far: Please subscribe to > > the epp-dev mailing list, > > Already done. Great! ;-) > > because all package maintainers must be responsible > > to test requests sent to this list. > > No such received so far. Or have I missed anything? No, I just thought I'd mention it here for the future. Sometimes it is important to get someone with insights in the package content (I, for instance, don't know the details from each and every modeling project) if a build breaks for some reasons. And because EPP is always the last one in the build process, these things are very often time critical.
(In reply to comment #20) > > > because all package maintainers must be responsible > > > to test requests sent to this list. > > > > No such received so far. Or have I missed anything? > > No, I just thought I'd mention it here for the future. Ok, that's also what I was thinking. > Sometimes it is > important to get someone with insights in the package content (I, for instance, > don't know the details from each and every modeling project) if a build breaks > for some reasons. Sure. > And because EPP is always the last one in the build process, > these things are very often time critical. I'll do my best to monitor such requests and respond in a timely manner.
(In reply to comment #15) > (In reply to comment #13) > > > That's a more general question: I've seen that this package consists of SDK > > > features only. Most SDK features include source code and other pieces that are > > > usually *not* required in a package but in a target environment. Without > > > knowing the use cases for the Automotive Package, I doubt that all sources are > > > required. Instead I think we should try to find the really required features > > > which had the advantage that the package would be much smaller. > > > > Hmm, yes and no. I see the implication wrt package size. But users of this > > package might want to use it for developing there own plug-ins/features on top > > of it, i.e. without a dedicated target platform. Aside from that, it looks that > > there are other packages that slightly derive from the "runtimes-only" policy, > > e.g., http://eclipse.org/downloads/packages/eclipse-modeling-tools/indigosr2 > > > > I suggest that we go with it as is for the time being and we readdress this > > topic in the Automotive IWG. We could then adjust the features for M7. How > > about that? > > M7 is fine with me but I really think it is worth a discussion because the > first package build (even without the two missing features in comment 11) > created an Automotive package with about 330MB - the biggest package so far! > And it is always easier to start small (in Juno) and to enhance the package > based on the requests from users. As promised, we have meanwhile had a discussion wrt including or not the SDKs in the automotive package and came to the conclusion that we don't need them :) So I'd like to submit a revised version of the package sources including the only the runtimes. For that I thought that I could clone the EPP Git repo so as to base my resubmission on the latest state of the art. However, it looks that I'm not allowed to do so. When attempting to clone http://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/ I get a HTTP 403 Forbidden error. Could you please tell me how to proceed? Thanks.
(In reply to comment #22) > So I'd like to submit a revised version of the package sources including the > only the runtimes. For that I thought that I could clone the EPP Git repo so as > to base my resubmission on the latest state of the art. However, it looks that > I'm not allowed to do so. When attempting to clone > http://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/ I get a HTTP 403 > Forbidden error. > > Could you please tell me how to proceed? Thanks. You're likely trying to clone using the git web interface URL instead of the "real" one. Use one of the following: git://git.eclipse.org/gitroot/epp/org.eclipse.epp.packages.git ssh://git.eclipse.org/gitroot/epp/org.eclipse.epp.packages.git http://git.eclipse.org/gitroot/epp/org.eclipse.epp.packages.git
(In reply to comment #23) > You're likely trying to clone using the git web interface URL instead of the > "real" one. > > Use one of the following: > git://git.eclipse.org/gitroot/epp/org.eclipse.epp.packages.git > ssh://git.eclipse.org/gitroot/epp/org.eclipse.epp.packages.git > http://git.eclipse.org/gitroot/epp/org.eclipse.epp.packages.git Great, thanks!
Created attachment 214784 [details] Patch for feature definition to make it include only the runtimes but no SDKs
(In reply to comment #25) > Created attachment 214784 [details] > Patch for feature definition to make it include only the runtimes but no SDKs Applied and pushed. Now we need to wait for the first updates of the staging repository before starting the next EPP build.
The change from SDK-features including sources etc. to standard runtime features was worth the effort: From 327MB in M6 to 176MB in M7 for the Automotive Package. Now we need to make sure that all required items are still included in the package. Can you download one of the last builds from http://build.eclipse.org/technology/epp/epp_build/juno/download - maybe build http://build.eclipse.org/technology/epp/epp_build/juno/download/20120505-1549?
(In reply to comment #27) > The change from SDK-features including sources etc. to standard runtime > features was worth the effort: From 327MB in M6 to 176MB in M7 for the > Automotive Package. :) > Now we need to make sure that all required items are still included in the > package. > Can you download one of the last builds from > http://build.eclipse.org/technology/epp/epp_build/juno/download - maybe build > http://build.eclipse.org/technology/epp/epp_build/juno/download/20120505-1549? I've downloaded and tested build 20120507-0240. Everything looks OK.
Closing as fixed. The Automotive Package has been created (back in 2012) and is still happily alive. Thanks.
