On Tue, Oct 8, 2013 at 4:11 AM, Stephen Connolly <[email protected]> wrote: > it has been, for too long, tied to the version of Jenkins that you are using. > My > understanding is that this requirement has been resolved
Right, it has long behaved like a normal plugin and keeping it in core just made it that much harder to deliver timely updates, as well as bloating the core repository and increasing core build/test times quite a bit. > you can remove that stupid project type completely Not really. Like any plugin you could already disable it as you wished; and it is still bundled in jenkins.war. So the only user impact should be that the release cycle need not be weekly like core’s, and the core dependency version can freely float to whatever is most appropriate. > I suspect KK & Jesse were having a hangout party while hacking it out of core We did talk about the possibility during JavaOne, among other potential modularizations (I just did matrix-auth as a little project). KK prepared the main code move but held off on pushing it for a bit since the trunk version referred to 1.532 APIs (ArtifactManager) that were not yet in a core release, and then I followed up by moving the functional tests. As to why the move did not get properly discussed/announced, there is no good reason other than laziness on our part. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
