Actually this is trivial to do with no restructuring. Just need to change the <developerConnection> in the pom.xml from [email protected] to https://github.com in the libraries.
Whilst I thought about doing that I didn't want to incur the wrath of the community when they could no longer easily release from their machine (if they chose to)... /James On Wednesday, October 7, 2015 at 11:31:58 PM UTC+2, Oleg Nenashev wrote: > > It could be done, but it requires a reorganization of projects to folders. > It's a single-time manual effort, so we could do it IMO. > > For plugins the same thing cannot be done without some DevOps stuff. We > have no database of plugin owners to drive it automagically. > > среда, 7 октября 2015 г., 19:50:45 UTC+3 пользователь Jesse Glick написал: >> >> On Tue, Oct 6, 2015 at 5:54 AM, James Nord <[email protected]> wrote: >> > you can perform releases directly from Jenkins™ (just as you can with >> the plugins). >> >> Can we have the committer or author set to the logged-in user? >> Otherwise we just have no idea who performed a release. >> >> >> https://github.com/jenkinsci/maven-plugin/commit/1b292a33289c946969975416daa164489da9678f >> >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7cda9d09-a41a-48ed-a7e9-347369bb8caf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
