Thanks for the hint, this was really helpful, at least to understand the issue.
However, in order to solve it decently for eclipse, I would have to remove that annotation, that seems unpractical to me. I will need a different solution if possible. So far I have not found anything on the web on that annotation in the web, so eclipse won't be aware of such a problem. With the risk of being naive (actually new to jenkins), why not simply remove the annotation from the jenkins core and solve that differently? Or should an issue be opened with eclipse? Definitely, I will try with jenkins-core in the workspace first, may be that helps. Reto Am Dienstag, 27. Mai 2014 21:36:46 UTC+2 schrieb Vincent Latombe: > > Hi, > > this is an eclipse-only issue. You can check out another thread on the ML > talking about this > > > https://groups.google.com/forum/#!searchin/jenkinsci-dev/Problems$20building$20maven-plugin$20in$20Eclipse/jenkinsci-dev/4rvorfnry1w/pRUPajeESCAJ > > > > Vincent > > > 2014-05-27 21:29 GMT+02:00 Surya Gaddipati <[email protected]<javascript:> > >: > >> I am running into the same exact problem. You can easily reproduce this >> >> 1. Create a new jenkins plugin >> >> mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create >> >> 2. Upgrade jenkins version to 1.564 in pom.xml >> >> >> 3. create an eclipse project and import it in eclipse >> >> mvn -DdownloadSources=true -DdownloadJavadocs=true >> -DoutputDirectory=target/eclipse-classes eclipse:eclipse >> >> >> 4. Now all the static inner classes in jenkins core are not accessible in >> eclipse . Strangely it complies fine on commandline with mvn install >> though. >> >> >> On Monday, May 26, 2014 4:36:26 PM UTC-5, Reto Hirt wrote: >>> >>> Hi there, >>> >>> I'm currently working on some enhancements for the build-pipeline plugin >>> and recently had to update Jenkins to 1.563. In order to follow up with the >>> plugin, I updated the dependency to 1.563/4 also but ran into a problem I >>> don't quite understand. It seems that in the Jenkins Core, the Class >>> hudson.model.Queue now denies access to it's inner classes like Item and >>> WaitingItem? Especially the latter was of great use, as it allowed me to >>> show scheduled jobs with estimated starting time and expected wait time in >>> the plugin. >>> >>> So, in 1.509.3 I could do this: >>> >>> ... >>> final List<Queue.Item> qitems = Jenkins.getInstance().getQueue(). >>> getApproximateItemsQuickly(); >>> >>> and later on.... >>> if (qitem instanceof Queue.WaitingItem).... >>> >>> These two things fail in 1.563 (did not try in between). >>> >>> Does anyone know if and why this is actually the case, and might be able >>> to give me an idea how to access the same information in 1.563 or newer? I >>> had a look around, but don't see it (yet). >>> >>> Kind regards >>> Reto >>> >> -- >> 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] <javascript:>. >> 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]. For more options, visit https://groups.google.com/d/optout.
