Re: [tycho-user] Java Annotations problem
unfortunately JDT binaries are not on maven central, details see 
If you want newer JDT maven artifacts, I guess you will have to add an eclipse.org maven repo to your pom.xml or settings.xml
At least that's what eclipse platform seems to be doing
On 13.10.17, 12:02, "tycho-user-bounces@xxxxxxxxxxx on behalf of Ed Willink" <tycho-user-bounces@xxxxxxxxxxx on behalf of ed@xxxxxxxxxxxxx> wrote:
Thanks. The bleeding edge of JDT annotations is pretty bloody.
It appears that
Buckmister / Tycho 0.26.0 predate the custom annotation support / nullable-non-null return checks. No problems.
Tycho 1.0.0 is in the middle of experimental functionality. Spurious problems.
Oxygen JDT is useable. Only minor problems.
I have succeeded in setting cbi-jdt-version/cbi-jdt-apt-version in so far as I get errors reporting that the override versions are not found.
I can force the correct versions to be pulled from the Oxygen release but it appears that Tycho insists on using versions that come from (but are not in) Maven central. The platform is ignored.
i.e. my repo shows a -SNAPSHOT for my explicit forced load but a -V2017... for the failed Maven access.
How about a use platform JDT configuration option?
On 13/10/2017 08:08, Sievers, Jan wrote:
What is the underlying JDT in 0.26.0 / 1.0.0?
Is it controllable?
you can override the default JDT/APT artifacts used (although I don't think this is the solution to the problem at hand). Make sure they match though. See e.g.
Is there some configuration magic for Java annotation paths?
not that I know of, unless you are talking about annotation processing to generate sources, see
The point that you are getting different errors/warnings may be simply related to your compiler errors/warnings configuration.
Since 1.0.0 .settings/org.eclipse.jdt.core.prefs is used by default, see announcement
tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>