All, with a very small code change and 2 small sources from a eclipse-plugin the maven-eclipse-plugin will be able to connect projects to the projects in the workspace instead of the jars for the repository. This is a very important feature for the maven-eclipse-plugin.
Now to my question: To do this, i need two small sources from a eclipse-plugin that reads a special binary file. But a dependency to the eclipse-plugin would include a deep tree of dependencies, what i would think is way to big for those two small classes (they are probably not intended to be part of a public API anyway).... 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) - extract the classes or sources at build time and include them in the package as classes - completely rewrite the part i need (to remove the copyright) - include the dependency anyway - any other solution? Specially the legal considerations make it difficult for me to decide for a solution. The eclipse-plugin has this copyright http://www.eclipse.org/legal/epl-v10.html and the maven-eclipse-plugin has this one http://maven.apache.org/plugins/maven-eclipse-plugin/license.html Probably i am not the fist one fighting with such considerations, so what is the "standard" way to go? thanks for any help, Ritchie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
