Well, I would prefer to rename the component and repo, since those (if I am
thinking about it right) will break fewer things, and those things it does
break are either admin-side or developer side.
The only arguments I can see against that are the time to change the
component and repo names, and that "negotiate-sso" may better follow a
naming convention.
I was guessing that changing the artifactId would probably break updates, as
well as a few other things - the download history, for example.
-----Original Message-----
From: Daniel Beck
Sent: Thursday, December 24, 2015 3:36 AM
To: [email protected]
Subject: Re: Plugin wiki page problem - artifact/plugin id vs repo/issue URL
The wiki macro supports the optional parameters jiraComponent and sourceDir
(from back when everything was in SVN) to change where those point to. So I
fixed this for you.
Ideally we'd rename the component and repo to match the artifact ID (at
least case insensitively). I can do that if you like.
The problem with changing artifactId is that we'd need to exclude the old ID
from the update sites, and existing users won't be offered plugin updates
(as it would be considered a separate plugin). You could do this as well,
but be aware of this limitation. Maybe now with only a few users it's still
a feasible solution.
On 24.12.2015, at 08:10, [email protected] wrote:
Wiki page:
https://wiki.jenkins-ci.org/display/JENKINS/Negotiate+SSO+for+Windows
My plugin page has broken links in the auto-generated
"Jenkins-plugin-info:pluginId=..." block, because of discrepancies between
the name of the repository/issue tracker and the artifactId set in the
pom.xml file - the artifactId was set to "NegotiateSSO" before the forked
repo was created, but the repo and issue tracker were set up for
"negotiate-sso-plugin". I want to resolve the issue, but wanted advice on
how to get it done. Options I know of:
- Try out maven's "relocation" capabilities to see if everything will link
up for updates, etc.; the artifactId would be changed from "NegotiateSSO"
to "Negotiate-SSO". (I can probably take care of most of this myself, but
will probably need help understanding all that I need to do to make it
work properly)
- Have repository, issue tracker, build job, etc. renamed to
"negotiatesso-plugin". (Intervention by admins likely needed for some
parts)
- Rename it, change the wiki page, and hope people find the update.
Any ideas to help resolve this?
--
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/1d14826e-9862-4162-b865-fbfecc0d47ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/W-USbhOubrQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/2EEB5306-30BD-425A-9483-B297A8604755%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
--
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/9B425C638E3D44E9BA6D68B6AC4EBA27%40HAFBeast.
For more options, visit https://groups.google.com/d/optout.
