Hi, where can i find that page?
After writing test cases i now know how to read the binary files, almost without the code but i need at least two defined constants "a long magic number". But as far as i know it is still called copying, if i used the original code to see what it does. Does the EPL allow repackaging? copying singular class files from the original jar and put them in a other (along with the legal notice, and no change what so ever). This is the first time (a least one i know of) but surly not the last time the maven-eclipse-plugin needs "something" from eclipse, so this should be solved. When we really do not want this dependency, we could include a parameter to point to the eclipse installation directory ........ (but i don't think thats a good solution) regards, Ritchie Carl Trieloff wrote: > > yes and no. > > You can NOT copy files from EPL into an ASL project, or modify them in > an ASL project. However you can take a binary (jar) dependency on an EPL > binary. So you would have to copy the jar that the source is in. > However, the source or part of the jar is also not permitted by the > combination of ASL / EPL. i.e. only binary dependencies on EPL will work > under ASL. Cliff has a good page posted on topic posted. > > Carl. > > Arnaud HERITIER wrote: >> Hi Guys, >> >> Thus what can I do ? >> Richard proposed a patch (http://jira.codehaus.org/browse/MECLIPSE-344) >> which is very useful for our eclipse plugin, but it bundles 2 java >> classes >> coming from eclipse (IBM - EPL 1.0). Those sources are in >> src/main/eclipse >> with the license file. >> >> Can I add them, or is it prohibited ? >> >> Arnaud >> >> On Nov 14, 2007 4:37 AM, Brett Porter <[EMAIL PROTECTED]> wrote: >> >> >>> On 13/11/2007, at 4:37 AM, Richard van Nieuwenhoven wrote: >>> >>> >>>> I see different solutions, but witch one to take .... >>>> - copy the sources and leaf them as untouched as possible (may be even >>>> in a own source folder to separate them and exclude them from code >>>> reformating) >>>> >>> yes, they will need to be separate in this case - note that the EPL >>> requires you contribute enhancements and fixes back to the author. >>> >>> >>>> - extract the classes or sources at build time and include them in the >>>> package as classes >>>> >>> this is likely a better alternative to the above, but remember you >>> need to include the relevant license/notice if you distribute your code. >>> >>> >>>> - completely rewrite the part i need (to remove the copyright) >>>> >>> you can't just "remove copyright" and rewrite in place - if you >>> rewrite it must be free of influence from the original. >>> >>> >>>> - include the dependency anyway >>>> >>> that might be the best place to start, and use exclusions to remove >>> the tree of deps you don't need. >>> >>> - Brett >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
