do you have a PR I can checkout locally?
On Monday, January 20, 2020 at 10:13:54 PM UTC, Ullrich Hafner wrote:
>
> Ok, thanks. 2.164 would be ok for me.
>
> Now I get:
>
> mvn validate
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [ERROR] 'dependencies.dependency.version' for
> org.kohsuke:access-modifier-annotation:jar must be a valid version but is
> '${access-modifier-annotation.version}'. @
> org.jenkins-ci.main:jenkins-bom:2.164.3,
> /Users/hafner/.m2/repository/org/jenkins-ci/main/jenkins-bom/2.164.3/jenkins-bom-2.164.3.pom,
>
> line 211, column 18
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project
> org.jvnet.hudson.plugins:analysis-pom:2.0.0-beta-2-SNAPSHOT
> (/Users/hafner/Development/git/warnings-ng-plugin-devenv/analysis-pom-plugin/pom.xml)
>
> has 1 error
> [ERROR] 'dependencies.dependency.version' for
> org.kohsuke:access-modifier-annotation:jar must be a valid version but is
> '${access-modifier-annotation.version}'. @
> org.jenkins-ci.main:jenkins-bom:2.164.3,
> /Users/hafner/.m2/repository/org/jenkins-ci/main/jenkins-bom/2.164.3/jenkins-bom-2.164.3.pom,
>
> line 211, column 18
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
>
>
> Am 20.01.2020 um 14:09 schrieb James Nord <jn...@cloudbees.com
> <javascript:>>:
>
> On Friday, January 17, 2020 at 1:28:09 PM UTC, James Nord wrote:
>>
>>
>> On Friday, January 17, 2020 at 12:46:15 PM UTC, Ullrich Hafner wrote:
>>>
>>> Would its make sense to remove that part from the pom until we have
>>> older Jenkins versions supported? Otherwise we will hardly find some
>>> testers for the changes...
>>>
>>> Am 17.01.2020 um 12:16 schrieb Oleg Nenashev <o.v.n...@gmail.com>:
>>>
>>> IIUC James was about retrospectively doing releases for older versions.
>>> https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-bom/ now
>>> lists only 2.190.x indeed
>>>
>>>
>> 2.190.x was retrospectively published. I have an internal task (now up)
>> to publish some boms for CloudBees' fixed lines (which is pretty much
>> 2.164.[1-3] ) , which will be adapted for OSS jenkins and make their way
>> into repo.jenkins.org, it just got paused due to Christmas/New Year,
>> sickness and investigating
>> https://issues.jenkins-ci.org/browse/JENKINS-60754 (thanks Jesse!).
>>
>> However anything older than 2.164 should be a security risk now (I do not
>> know of any other companies performing releases with backports of Jenkins
>> security fixes) - so I am not intending to publish anything else other than
>> the 2.164 line as this enables users bad habits of upgrading plugins to get
>> new features whilst still running an insecure core, hence I would recommend
>> bumping to at least 2.164.x in the warnings-ng plugins in preparation.
>>
>> of note 93% of users who are using the latest warnings-ng plugin are on
>> 2.190.1 or higher and 99% are on 2.164.1 or higher, so I would not expect
>> this to be an issue for users of your (well at least warnings-ng) plugins.
>>
>>
> 2.164.[1-3] and 2.176.[1-4] have now been published to repo.jenkins-ci.org
> .
>
> I'm not intending to publish more versions, however if there is a
> demonstrable need then I can publish some more.
>
> For trying to track down changes between versions you can still use
> -Djenkins.version=x.zyz if you also specify -Djenkins-bom.version=a.abc
> which will not be 100% correct but should be close enough. (only ant,slf4j
> commons-codec and spotbugs-annotations have changed between the published
> versions)
>
> /James
>
>
> --
> 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 jenkin...@googlegroups.com <javascript:>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/9640e383-2686-41fe-b80b-26df95d5d13e%40googlegroups.com
>
> <https://groups.google.com/d/msgid/jenkinsci-dev/9640e383-2686-41fe-b80b-26df95d5d13e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/94a1c57b-7c5f-4f66-8047-07055920bf90%40googlegroups.com.
