Community
Participate
Working Groups
Development in E4 requires the E4 tools to be developed. At the moment, the Eclipse IDE promotes development of Eclipse 3.x plug-ins and views because of the lack of built-in tooling for E4 based applications, and/or for the built-in backwards compatibility frameworks (E4 in E3.x) available. To improve this, and given that the E4 tooling has migrated into its own repository, it would be good to have the E4 tools available in the standard IDE for Eclipse committers so that it can be utilised by developers to encourage adoption of Eclipse 4 APIs and tooling.
Adding Lars for thoughts.
And also to the RCP package. Note that e4 tools should soon be moved to Platform https://projects.eclipse.org/projects/eclipse.e4/reviews/move-e4-tools-eclipse-platform-ui
I'm open to accept a review for M6. That's about the last milestone to add features to a package. Alternatively, a list of feature ids is also sufficient. :)
Lars, will e4 tools participat in the release train? Will it publish something into the common release repository that I can consume in the package?
(In reply to Gunnar Wagenknecht from comment #4) > Lars, will e4 tools participat in the release train? Will it publish > something into the common release repository that I can consume in the > package? Build should be ready with todays I-build. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=459799
Is this done? the tools are already inegtrated into the RCP and modeling package...
(In reply to Jonas Helming from comment #6) > Is this done? the tools are already inegtrated into the RCP and modeling > package... Gunnar just said via Twitter that he wants a Gerrit review. Can you do this Jonas?
As discussed on twitter, it is too late now for Mars, I will do this for SR1 :-(
Adding Markus for feedback.
Gerrit review can be done now to avoid any delay for SR1.
@Gunnar: It is to late for Mars, I will add it to SR1
https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03579.html
OK, so we are rebuilding the packages for Mars. Markus is considering a change for the JEE package. If you can provide a review today, I'd give it my +2, given that it already works successfully in other packages. If Markus also +1 it then it could be in Mars.
The change in the Java EE package is a bit different from this here. In the Java EE case it is done to mitigate a bad user experience, which isn't the case here. I'd suggest to use SR1 to add this feature to the package.
(In reply to Markus Knauer from comment #14) > The change in the Java EE package is a bit different from this here. In the > Java EE case it is done to mitigate a bad user experience, which isn't the > case here. Promoting E4 Tools as a top feature of this release and not including it in the committer package is also a bad user experience IMO. Since there is time, and there will be respin anyway, it would be a shame to not being agile enough to integrate such a patch. (Less than my 2c, as I actually use the RCP package and have claimed multiple times the Committers package is the one too many anyway)
It is a mistake to release the IDE for committers without the tools needed to commit against Eclipse 4. I would not advocate adding it to other packages but it is crazy to not have it in the very package that needs it.
New Gerrit change created: https://git.eclipse.org/r/50414
We have just created a gerrit, which adds the e4 tools, but I am actually not in favor to push it into Mars, but apply it for SR1 instead. For 3 major releases, meaning for 3 years, the tools have not been graduated nor been part of any EP. I did not like this situation, especially for new people, that is why we moved the e4 tools. However, all people who use e4 know that they have to install the tool, so I think waiting another 3 month to make them available doesn't sound crazy. Additionally, I expect the committer package to be used by expert users. Finally, I almost never need the e4 tools to commit to the platform. Still I agree, that is is bad, that the tools did not make it inot that package. No offense to anyone, but this BR was created 4 month ago. Since 2 month the tools were available to be added. I even pinged the BR again 1 month ago. Now we start a huge discussion 2 days after the final deadline. The mentioned re-spin was clearly announced to only allow the discussed change and freeze all other contributions. I think in an agile process it is still important to respect some rules and one is that if something is not finished until a deadline it is move to the next milestone rather than shifting the deadline. Probably the change does not harm to the EP, but if we allow another change for the re-spin, probably other projects want to add other changes, too. Just my 2 cents, this is not my decision anyways...
Right now we are in quiet week before our release, and only going to make changes if there are blockers, stop-ship bugs, or legal reasons that force us to take action. All other changes need to wait until SR1. For this enhancement request there are several options: Use a different package that has the E4 tools included, or install them from the preconfigured Mars p2 repository.
Gerrit change https://git.eclipse.org/r/50414 was merged to [master]. Commit: http://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/commit/?id=9374f86e8c3edd9ab3c666b79474404a525314ca
I think this was fixed for Mars, please reopen if I'm wrong.
It was not in Mars for the committers package. It may be added in SR1.
