https://issues.apache.org/bugzilla/show_bug.cgi?id=50604
--- Comment #12 from Mark Thomas <ma...@apache.org> --- (In reply to Konstantin Kolinko from comment #11) > (In reply to Mark Thomas from comment #7) > > I think e) is not possible, because Eclipse uses a different license. The license looks OK as long as we only ship the package renamed binary. I don't think we'd be able to ship the source. Keep in mind we used to do some major re-packaging of Eclipse JARs and that wasn't an issue. > An additional idea: > > g) Remove that dependency. (At least mark it optional). > > First, Tomcat can be used with javac compiler from JDK. > > Second, if someone wants to re-bundle the ecj jar, > I think they can depend on the "Binary distribution" bundle of Tomcat > (the one that publishes zip and tar.gz) and unzip ecj.jar from within the > lib/ directory there. That is about the same level of pain that folks see at the moment (and what I'd like to avoid). > > I also discovered that the version number of > > the JAR is not 4.4.RC4 but 3.10.0.v20140604-1726. > > It is no wonder. Each component in Eclipse has its own version like that. > > > The f) option sounds interesting. > I do not know what it actually looks like. How it works? > (Are there some examples, precedents?) I experimented with the tycho plugin but couldn't get it to use the p2 repo. The issue remains with that option of buidl tools other than Maven that use maven central and can't talk to p2 repositories. > In general, is it possible to teach Maven to download some known version of > a dependency from some fixed known location (like our Ant script downloads > from sourceforge.net and from eclipse.org)? As far as my research shows, no. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
