https://issues.apache.org/bugzilla/show_bug.cgi?id=50604
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #7 from Mark Thomas <ma...@apache.org> ---
This came up at work today.
>From this Eclipse bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=283745
it doesn't look like the necessary jar is going to be routinely published to
Maven central any time soon.
I also discovered that the version number of the JAR is not 4.4.RC4 but
3.10.0.v20140604-1726. I suspect that should Eclipse ever upload these JARs to
central there are going to be version issues with the existing JARs that the
community has uploaded.
Options considered to address this:
a) continue as is and let consumers of tomcat-jasper deal with this
b) drop the Maven releases
c) delay the release to Maven central until the ecj JAR is available
- delay likely to be 1-2 weeks after upload is requested
- either release manager has to arrange for upload or wait for the community
to do it (longer delay)
d) get Eclipse to upload JARs to central as part of their release process
e) upload the JAR under the Tomcat groupId
f) add the p2 repository to the pom
a) is far from ideal as this is causing pain for some users
b) is not a serious option as Maven releases are used too widely
c) will cause problems for projects (TomEE?) that work from the zips that are
released to Maven as access to the latest releases will be delayed
d) looks to be unlikely given how long the current bug requesting this has been
open
e) could result in class loading issues if a project has a dependency on an
older ecj JAR that is in central unless we package rename
f) this should work in theory but I couldn't get it to work and not all build
tools that use Maven central can access p2 repositories
Given all of the above, the best way forward appears to be a variation of e)
using jarjar to repackage the JAR (org.apache.tomact.org.eclipse.jdt.*) and
then upload that to central under Tomcat's group ID. I don't really like doing
this but don't see a better way forward at this point.
--
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
