Sure; thanks for the clarification of the pattern. Paul
On 30 Jun 2014, at 11:26, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > please do not put `-plugin` in the artifactId. > > The pattern is: > > github repo name is: X-plugin > artifactId is: X > groupId is: org.jenkins-ci.plugins > > package name is one of: > > * org.jenkinsci.plugins.X; or > * jenkins.plugins.X; or > * com.mycompany.jenkins.X (if you want to credit a company providing the vast > bulk of the contribution *and* intending to maintain the plugin going foward) > > HTH > > > On 30 June 2014 11:20, Paul Allen <pal...@perforce.com> wrote: > Hi Oleg, > > On 27 Jun 2014, at 17:11, Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > > > I would need to learn about configuration migration, if you know of another > > tool or example that performs this task please let me know. > > > > https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility > > describes common cases, which may be used. When you finish the > > implementation, it may be possible to migrate configs by redirecting > > XStreams. Legacy configurations can be handled by existing routines in > > PerforceSCM (e.g. "update to the version XXX before the migration") > > Thanks for the link on backwards compatibility. > > > > I would have preferred a branch on the 'Perforce' name-space, but rather > > than delay the release any longer I am happy to go with an alternate name. > > I'd guess you would prefer org.jenkinsci.plugins.perforce.X (or even > > com.perforce.jenkinsci.plugins.perforce.X) instead of the legacy > > hudson.plugins.perforce.X > > org.jenkinsci.plugins.perforce, jenkins.plugins.perforce or something like > that. Is there a standard format for new plugins? > > The other issue is the plugin name 'perforce-plugin'; I could use > 'p4-plugin', so the namespace would be org.jenkinsci.plugins.p4 or similar? > > > Kind regards, > Paul > > > 2014-06-27 0:11 GMT+04:00 Paul Allen <pal...@perforce.com>: > > Hi Oleg, > > > > On 26 Jun 2014, at 15:53, Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > > > > > My managers don't want to invest into such migration without a > > > middle-term advantage. > > > They think that Perforce guys should be responsible for the compatibility > > > since we pay you money ;) > > > I definitely don't want to spend my spare time for such activity. > > > > I totally understand; the migration is in the back log, but not something I > > will be able to work on right now. Migrations can be tricky, especially if > > the dataset has had older versions or not totally clean. > > > > I would need to learn about configuration migration, if you know of another > > tool or example that performs this task please let me know. > > > > > If we don't end up using the Perforce namespace, I had thought about > > > splitting the plugin into separate projects > > > * Is there any need to keep p4-credentials and p4-core separately? > > > * Probably, it could be useful to have p4-api (Credentials, P4Java > > > wrappers, etc.) and p4-scm plugins > > > * p4-labels could be merged with p4-scm > > > > > I suppose we can go forward with independent workspaces since you agree > > > with such approach > > > > I would have preferred a branch on the 'Perforce' name-space, but rather > > than delay the release any longer I am happy to go with an alternate name. > > Perhaps later on, if we can provide a suitable migration path, we could > > look to merge the two name spaces. > > > > Kind regards, > > Paul > > > > -------------------------------------------------------------------------------- > > This email and any files transmitted with it are confidential and intended > > solely for the use of the individual or entity to whom they are addressed. > > If > > you have received this email in error please notify the system manager. > > Please > > note that any views or opinions presented in this email are solely those of > > the > > author and do not necessarily represent those of Perforce Software. Finally, > > the recipient should check this email and any attachments for the presence > > of > > viruses. Perforce Software accepts no liability for any damage caused by any > > virus transmitted by this email. > > > > Perforce Software UK Ltd is registered in England and Wales as company no. > > 3816019 at the following address: West Forest Gate, Wellington Road, > > Wokingham, > > RG40 2AT, UK > > -------------------------------------------------------------------------------- > > > > -- > > 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/v-u3HRvFCi8/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > > jenkinsci-dev+unsubscr...@googlegroups.com. > > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > > > -------------------------------------------------------------------------------- > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. If > you have received this email in error please notify the system manager. Please > note that any views or opinions presented in this email are solely those of > the > author and do not necessarily represent those of Perforce Software. Finally, > the recipient should check this email and any attachments for the presence of > viruses. Perforce Software accepts no liability for any damage caused by any > virus transmitted by this email. > > Perforce Software UK Ltd is registered in England and Wales as company no. > 3816019 at the following address: West Forest Gate, Wellington Road, > Wokingham, > RG40 2AT, UK > -------------------------------------------------------------------------------- > > -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -------------------------------------------------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Perforce Software. Finally, the recipient should check this email and any attachments for the presence of viruses. Perforce Software accepts no liability for any damage caused by any virus transmitted by this email. Perforce Software UK Ltd is registered in England and Wales as company no. 3816019 at the following address: West Forest Gate, Wellington Road, Wokingham, RG40 2AT, UK -------------------------------------------------------------------------------- -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
