On 10/08/2014 14:24, Konstantin Kolinko wrote: > 2014-08-08 21:12 GMT+04:00 Mark Thomas <ma...@apache.org>:
<snip/> >> 3. We will not normally update Tomcat's dependency on JDT until the >> 'small' JAR is available in Maven Central. <snip/> > I disagree (-0, not a stopper) with 3., as this procedure lacks > explicit step that triggers upload of "small" jar. > > Currently the incentive for the upload is our having started to use > the new version. There is no incentive other than that, as I think no > other project besides us uses the jar. > > Essentially we have to announce that we want to update the dependency > and wait for a volunteer to notice the announcement. Ah. That makes things more problematic, especially if they wait for the pom to be updated and start to fail before they start their update process. <snip/> > I think that the procedure is > 1) update build.properties.default and IDE project files > 2) post a heads-up notice on dev/users and wait a few days > 3) update POM (using the fallback options) It is going to be a while before we need to update this again. I suspect there will have to be a little bit of trial and error until we find the smoothest process. It would help if we knew who was currently uploading the JDT jar then we could ping them directly (unless they are already watching the dev list). Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
