Home » General (non-technical) » Eclipse Foundation » Move / Copy an Eclipse project artifact into another project (What it is needed to take an editor from one Eclipse project to another)
|Move / Copy an Eclipse project artifact into another project [message #1711578]
||Sat, 17 October 2015 17:23
| Patrik Suzzi
Registered: February 2018
I recently read the interesting mail thread Ctrl-1 driven development, in [ide-dev] , about improving Eclipse editors.
While reading the mail thread it came out the idea that the Eclipse Platform could benefit by shipping the WST.XML Editor that is part of another project.
This is a kind of new thing to me, and I wanted to know more about this, in particular:
- It is possible to move (or copy) one module, from one project, to another project ? (as example the XML editor from WST to Platform)
- If the above is possible, which are the rules to govern this process ?( are there some rules to govern this process, or it depends only on PMC )
|Re: Move / Copy an Eclipse project artifact into another project [message #1711603 is a reply to message #1711578]
||Sun, 18 October 2015 08:17
| Ed Merks
Registered: July 2009
On 17/10/2015 7:23 PM, Patrik Suzzi wrote:
> I recently read the interesting mail thread
> https://dev.eclipse.org/mhonarc/lists/ide-dev/msg00807.html , about
> improving Eclipse editors.
Yes, it's a very long, but interesting thread...
> While reading the mail thread it came out the idea that the Eclipse
> Platform could benefit by shipping the WST.XML Editor that is part of
> another project.
The platform already ships code from other projects. E.g., from ECF and
EMF. Shipping something is completely unrelated to project
organization, though clearly coordination effort is needed. E.g., EMF
provides a "base build" that the platform build can consume to build the
> This is a kind of new thing to me, and I wanted to know more about
> this, in particular:
> It is possible to move (or copy) one module, from one project, to
> another project ? (as example the XML editor from WST to Platform)
Yes, but this is not necessary, and perhaps even pointless. The point
is that there are EPP packages and they can combine and ship whatever is
determined to be useful for that package. For example, the Java package
already includes the XML Editor:
> If the above is possible, which are the rules to govern this process
> ?( are there some rules to govern this process, or it depends only on
> PMC )
It's part of the review process:
Moving code is an organizational issue. I doubt it makes sense to move
the XML Editor purely for the purpose of shipping it in more packages,
or in particular purely for the purpose that it's in the "Platform"
package, which isn't an an EPP package in the first place but rather
something a user would get from:
What's in the platform package is purely for the platform PMC to
decide. The point is there's absolutely no reason to move code between
projects. Furthermore, the "Platform" package has little impact on end
users who, I believe, generally download something from:
And for that purpose, the package maintainers decide what's in the
package and can decide to include the XML Editor. That will be more
compelling if the XML Editor is more compelling. Certainly changing the
default tab for that editor must be an extremely simple change and seems
to me a first step in making that editor more obviously useful. In fact
I would argue that what's in the design tab should be in the outline and
the editor should show only source...
> Kind Regards.
> Patrik Suzzi
Professional Support: https://www.macromodeling.com/
Current Time: Wed Jan 19 12:13:38 GMT 2022
Powered by FUDForum
. Page generated in 0.01950 seconds