On 2/20/09 14:53, "Zingo Andersen" <[email protected]> wrote:
>
> It all boils down to license compabilety, dont know if they are (probably not
> compleatly).
>
> This is how TPTP seem to solve it:
> http://www.eclipse.org/tptp/home/documents/process/How_to_Incorporate_Non_EPL_
> Content_into_TPTP.html
>
The Apache license allows inclusion with the requirement that a notice be
included that code that was originally Apache licensed is present.
> Don't know how easy it is to replace the ini4j stuff in the patch compared to
> "double licensing"?
I would be willing to write a clean ini file reader or to add an option in
hg paths.
My personal preference would be to have the plugin read ini files as this
gives more flexibility and doesn't tie down release cycles too much. But of
course the drawback is that mercurial eclipse would have to track any ini
changes in hg, which may not be desirable.
In any case, we at Cleversafe are considering switching to Mercurial
internally, but we sort of need this feature to convince our developers (the
mercurial plugin has to be comparable in features to subclipse). So I am
highly motivated to work this out!
Wesley Leggette
Cleversafe, Inc.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MercurialEclipse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/mercurialeclipse?hl=en
-~----------~----~----~----~------~----~------~--~---
