I have had a discussion with somebody from the Eclipse project, as well
as doing some reading. The new GPL (v3) will be compatible with the EPL,
but more im****tantly, the plugin is something that would be distributed
together with Eclipse rather than a Modula-3 distribution, if only
because it should be independent of them, while being heavily dependent
on Eclipse.
Personally I found that a most convincing argument, so I specified EPL
when requesting the sourceforge project.
We'll work out some boilerplate template text for the Java files later
on. Copyright will just be your own, license EPL.
Step one will be getting the editor, but that is mostly standard Eclipse
stuff. Next come the syntax coloring and auto-complete. Finally, if we
can get some form of compilation working, we'll be able to add syntax
checking and outlines. Build may be a bit different, as -last time I
looked- M3 compilers tend to be even more holistic than Java; they want
the whole project rather than individual modules/interfaces. I'ld like
to automate that, but don't know yet if that would actually be easy to do.
Cheers,
Bert
Daniel Benavides wrote:
> I think you are the head of the project, so I prefer let that clear,
> giving you the recognize of leading the project.
> As we know the project is aproved on sourceforge
> https://sourceforge.net/projects/m3clipse/
> However we must think if the plugin will be distributed with m3
> distribution sources.
> In that case, we must ask whether the EPL license is compatible with
> the m3 distribution licences.
> If not, as we may think, because of the nature of the package, we can
> think that EPL will be compatible with GPL software (look on
> http://en.wikipedia.org/wiki/Eclipse_Public_License
).
>
> Daniel Benavides
|
