Hello Oleg, 2017-06-14 8:32 GMT+02:00 Oleg Nenashev <[email protected]>:
> Hi, > > This, though practical, does not follow Jenkins versioning convention and >> thus does not work well with several tools/libraries which understand this >> convention as existing. > > > There is no versioning convention in Jenkins. If PCT does custom version > matching logic, maybe you may have to add more flexibility/hacks there > The convention is "you can use what you want while the Jenkins infrastruture (UCs, ATH, etc..) works properly". What do you think? IMHO, It would be easier to release this *wrapper* plugin following the most used format, instead of applying more hacks in the PCT. Regards, > > For Library wrapper plugins like jQuery I would vote for staying on the > current approach when the plugins version equals to the bundled lib version. > > BR, Oleg > > > > вторник, 13 июня 2017 г., 11:32:33 UTC+2 пользователь Evaristo Gutierrez > написал: >> >> Summarizing: PCT gathers dependencies for a plugin and adds the necessary >> ones to a modified plugin POM. To process the version of such dependencies, >> VersionNumber library is being used and it always returns version tokens >> split by '.'. The result is a wrong version is added to the POM and then >> the artifact cannot be gathered. >> >> On Tue, Jun 13, 2017 at 10:57 AM, Daniel Beck <[email protected]> wrote: >> >>> >>> > On 13. Jun 2017, at 09:57, Evaristo Gutierrez <[email protected]> >>> wrote: >>> > >>> > @Daniel what do you mean with the impact? >>> >>> What is the motivation to change things here? How does that versioning >>> scheme result in those tools not working properly? >>> >>> >>> -- >>> 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/to >>> pic/jenkinsci-dev/qpXChF4R2Ro/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/ms >>> gid/jenkinsci-dev/C0251B45-0F9A-42CE-A8F5-385716743F1C%40beckweb.net. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Best regards, >> Evaristo. >> > -- > 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/05cc6f5c-3ba6-4dc2-803a-cdb6b1392ce2% > 40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/05cc6f5c-3ba6-4dc2-803a-cdb6b1392ce2%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Manuel Recena Soto * manuelrecena.com [/blog] * linkedin.com/in/recena -- 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/CABa-UodgN9GzS-zvTqZcDbRvu%2Bcd3v6%3DxoYBinB3Nr4drUgQ7g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
