Getting the releases again to maven repo as well

[TuomasKiviaho]

I wondered where why the new versions were not showing and discovered that they go to jenkins repo from 1.4 forward.

7f66040

I propose that the artifacts are either to be duplicated or deployment repo changed back to the original.

I'm trying to propose an API change to a non-jenkins related project (querydsl) and this tool seemed to provide a nifty solution. It would seem a bit cumbersome when actions taken to preserve backwards compatibility suddenly introduce a non backwards compatible repository requirement. I try to avoid hardcoding the repo to the pom.xml because that's considered a bad practise, but currently that the only solution I've got if the older 1.4 version fails me.

Tuomas

[irobertson]

Alternatively, would it be possible to work with the maven central maintainers to have http://repo.jenkins-ci.org/releases/ mirrored to central?

[kohsuke]

I deployed it to Jenkins repo just because it was easier. Let me get the group ID registered with central so that I can push there.

[kohsuke]

I filed it under https://issues.sonatype.org/browse/OSSRH-7697

[kohsuke]

1.11 is now in central

[TuomasKiviaho]

Thanks a bunch (for the lightning fast response as well),

org.jenkins-ci:annotation-indexer🫙1.4 seems to be missing from central. I got this working by excluding it and reverting back to the older org.jvnet.hudson version.

PS. It seems that annotation-indexer is also leaving traces of itself in form of META-INF/annotations markers. It might be wise to remove these automatically since they are not needed at runtime

[jglick]

org.jenkins-ci:annotation-indexer:jar:1.4 seems to be missing from central

Yeah this just gets published to the Jenkins repo currently.

(BTW I just published 1.6 today.)

annotation-indexer is also leaving traces of itself in form of META-INF/annotations markers

Yes, that is the whole point of the library. Otherwise they would be unindexed annotations.

they are not needed at runtime

They are needed at runtime. See Index.list.

[irobertson]

Wait - they are needed at the runtime of the maven plugin, but they aren't
need at the runtime of the resulting jar, right?

On Wed, Nov 6, 2013 at 1:16 PM, Jesse Glick notifications@github.comwrote:

org.jenkins-ci:annotation-indexer:jar:1.4 seems to be missing from central

Yeah this just gets published to the Jenkins repo currently.

(BTW I just published 1.6 today.)

annotation-indexer is also leaving traces of itself in form of
META-INF/annotations markers

Yes, that is the whole point of the library. Otherwise they would be
unindexed annotations.

they are not needed at runtime

They are needed at runtime. See Index.list.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-27909584
.

[jglick]

No, they are needed when the application runs. That is the only way it can find the elements containing the indexable annotations. (Well it could fall back to a complete bytecode scan of the classpath, as e.g. Sisu-Guice does, but this is quite inefficient.)