Thats true, Jesse and splitting off the maven plugin from the main repo was a topic quite a couple of times already - maybe we should have a go on this then. But if we do this, would it not make sense to split of the MavenTask too? Maybe a MavenBuilder/task-plugin an then the maven-plugin which extends/uses the first one. This way we could still have basic features used by both maven integrations and have releases independent from the core (e.g. things like the SettingsProvider). regards Domi
On 18.05.2013, at 15:52, Jesse Glick <[email protected]> wrote: > On 05/18/2013 03:28 AM, domi wrote: >> Without this one we have to stick to 1.480.3 which is a real bummer > > I can think of several bugs off the top of my head which will be prime > candidates for 1.509.3 once fixed in trunk. So long as vjuranek is willing to > produce new LTS versions I see no harm in sticking to the “train” model. > > JENKINS-17508 could probably be fixed for you by just updating the Maven > plugin, by the way. And we should look into splitting this plugin out into > its own repository so it can have an independent lifecycle and not hold core > releases hostage. As far as I know the only thing stopping that from > happening is compatibility in the test harness, which is an annoyance but > probably not a blocker. > > -- > 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. > > -- 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.
