The following projects have changed:
bundles/org.eclipse.e4.tools.emf.liveeditor
The build contains commits that mentioned these bugs:
+ Bug 425866 - Add README.md to the e4 tools projects (NEW)
___
e4-dev mailing list
e4-dev@eclipse.org
https://dev.ecli
Filed: https://bugs.eclipse.org/bugs/show_bug.cgi?id=428375 (Adopt the E4
tools Model Editor)
On Mon, Feb 17, 2014 at 5:00 PM, John Arthorne wrote:
> I think the only location for tools that makes sense is PDE. We don't
> include plug-in tooling with the core platform because end users don't nee
I think the only location for tools that makes sense is PDE. We don't
include plug-in tooling with the core platform because end users don't
need it unless they are doing plugin/app development. To me the model
editor belongs right alongside the product editor, manifest editors, etc
as part of
OK, open questions for me are:
1. Where to move: Platform or PDE (as I wrote I rather prefer Platform)
2. Shall we split org.eclipse.e4.tools.services into one bundle which
remains in e4 and move the services, which are used by the tools to a
new bundle (or maybe just into the tools bundle.
I rea
Hi,
on stackoverflow there was a question on how to modify the default
behaviour for loading ResourceBundles. The question was how to do that for
the application model and the new message extension aswell.
http://stackoverflow.com/questions/21776496/eclipse-rcp-getting-resourcebundles-using-custo
