Hi
It looks like an 'impossible' problem. I have used JDT's @Nullable in a
variety of configurations; it seems ok.
Maybe it's time to force a JDT repo reload of your target and maybe even
wipe everything.
(I presume you are not accidentally trying to use Java 6 where
jdt.annotations was very different.)
If using a Java > 8, the migration of modules in particular
javax.annotation causes many excitements.
Regards
Ed Willink
On 14/02/2019 20:24, Bernd Hufmann wrote:
On my laptop it’s openjdk version "1.8.0_171".
I still try to understand why the change in my target definition to
use a different platform updates site causes this particular failure
while using the same java, tycho and Trace Compass version. I don’t
see the connection.
Bernd
*From:*cross-project-issues-dev-boun...@eclipse.org
<cross-project-issues-dev-boun...@eclipse.org> *On Behalf Of *Daniel
Megert
*Sent:* February-14-19 11:34 AM
*To:* Cross project issues <cross-project-issues-dev@eclipse.org>
*Subject:* Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
I can't say much without more details. The error looks strange. It's
not directly a Java compile error but an issue with visibility/access
based on the class path. What Java version are you using?
Dani
From: Bernd Hufmann <bernd.hufm...@ericsson.com
<mailto:bernd.hufm...@ericsson.com>>
To: Cross project issues <cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>>
Date: 14.02.2019 17:27
Subject: Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
Sent by: cross-project-issues-dev-boun...@eclipse.org
<mailto:cross-project-issues-dev-boun...@eclipse.org>
------------------------------------------------------------------------
Hi Dani
The only change is the platform version. The patch on Gerrit had other
things. But I can reproduce it on my laptop where I only change the
platform version to the one listed below.
What part of the platform updates is used during compilation step in
maven/tycho?
Bernd
*From:*cross-project-issues-dev-boun...@eclipse.org
<cross-project-issues-dev-boun...@eclipse.org
<mailto:cross-project-issues-dev-boun...@eclipse.org>> *On Behalf Of
*Daniel Megert*
Sent:* February-14-19 11:07 AM*
To:* Cross project issues <cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>>*
Subject:* Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
Did you check whether something change, e.g. JRE or Tycho version?
Dani
From: Bernd Hufmann <bernd.hufm...@ericsson.com
<mailto:bernd.hufm...@ericsson.com>>
To: Cross project issues <cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>>
Date: 14.02.2019 17:01
Subject: Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
Sent by: cross-project-issues-dev-boun...@eclipse.org
<mailto:cross-project-issues-dev-boun...@eclipse.org>
------------------------------------------------------------------------
Hi Vikas,
Thanks for the reply.
>>You can probably circumvent this issue by setting the compiler option for
that project to
>> Windows -> Preferences -> Java -> Compiler -> Errors/Warnings ->
>>Deprecated and restricted API -> Forbidden reference (access rules):
-> change to warning
I tried that but it still doesn’t work.
>>I tried in eclipse IDE with a new projected that used
Nullableannotation and I didnt get any changed behavior.
I only get the error when running a maven build from command-line. I
don’t see the same behaviour within the Eclipse IDE (both 4.10 and 4.11)
>>Can you please open a bug in eclipse with detailed steps to recreate
this on eclipse?
Yes, I can write a bug. I try to reproduce it with a small example.
What component should write the bug on (Eclipse JDT or PDE or platform
or other)?
Bernd
*From:*cross-project-issues-dev-boun...@eclipse.org
<cross-project-issues-dev-boun...@eclipse.org
<mailto:cross-project-issues-dev-boun...@eclipse.org>> *On Behalf Of
*Vikas Chandra*
Sent:* February-14-19 12:51 AM*
To:* Cross project issues <cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>>*
Subject:* Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
>>is there something that I could do in Trace Compass that will fix
the problem
You can probably circumvent this issue by setting the compiler option
for that project to
Windows -> Preferences -> Java -> Compiler -> Errors/Warnings ->
Deprecated and restricted API -> Forbidden reference (access rules):
-> change to warning
I tried in eclipse IDE with a new projected that used
Nullableannotation and I didnt get any changed behavior.
Can you please open a bug in eclipse with detailed steps to recreate
this on eclipse?
Regards,
Vikas
------------------------------------------------------------------------
Eclipse PDE lead,
IBM Rational
EGL D Block - Bangalore, India
Office Phone No : +91 - 80 - 41776506
------------------------------------------------------------------------
Bernd Hufmann ---02/13/2019 06:33:46 PM---Hi, For the Trace Compass
project, I changed the target definition to use the latest platform integr
From: Bernd Hufmann <bernd.hufm...@ericsson.com
<mailto:bernd.hufm...@ericsson.com>>
To: Cross project issues <cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>>
Date: 02/13/2019 06:33 PM
Subject: [cross-project-issues-dev] Build problems with recent
platform 4.11-I-builds
Sent by: cross-project-issues-dev-boun...@eclipse.org
<mailto:cross-project-issues-dev-boun...@eclipse.org>
------------------------------------------------------------------------
Hi,
For the Trace Compass project, I changed the target definition to use
the latest platform integration build and I get some unexpected
compilation errors when building with tycho. Reference [1] shows a
Jenkins build for the failure. See below for an example of the error
print-outs. See below for an example of the error print-outs. I was
able to track down first build version when this problem happens. So,
when building with platform integration build [2], there is
compilation error. When using integration build [3], then I get the
error below. It seems, that on February 08 some change was merged that
causes the problem.
I’m at loss at them moment and I don’t know how to trouble-shoot
further and find a solution. Does anybody have an idea what could be
the cause of the problem? Was there a bug introduced in the platform
build? Or is there something that I could do in Trace Compass that
will fix the problem. By the way, we use Tycho version 1.3.0.
In advance thank you very much.
Best Regards
Bernd
[1] https://hudson.eclipse.org/tracecompass/job/tracecompass-gerrit/21235/
[2]
http://download.eclipse.org/eclipse/updates/4.11-I-builds/I20190207-1800/
[3]
http://download.eclipse.org/eclipse/updates/4.11-I-builds/I20190208-1800/
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:1.3.0:compile
(default-compile) on project org.eclipse.tracecompass.tmf.ui:
Compilation failure: Compilation failure:
[ERROR]
/home/hudson/jenkins-slave-tracecompass/workspace/tracecompass-gerrit/tmf/org.eclipse.tracecompass.tmf.ui/src/org/eclipse/tracecompass/internal/tmf/ui/project/wizards/importtrace/ZipLeveledStructureProvider.java:[32]
[ERROR] import org.eclipse.jdt.annotation.Nullable;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] Access restriction: The type 'Nullable' is not API
(restriction on classpath entry
'/home/hudson/jenkins-slave-tracecompass/workspace/tracecompass-gerrit/.repository/p2/osgi/bundle/org.eclipse.jdt.annotation/2.2.200.v20180921-1416/org.eclipse.jdt.annotation-2.2.200.v20180921-1416.jar')
[ERROR]
/home/hudson/jenkins-slave-tracecompass/workspace/tracecompass-gerrit/tmf/org.eclipse.tracecompass.tmf.ui/src/org/eclipse/tracecompass/internal/tmf/ui/project/wizards/importtrace/ZipLeveledStructureProvider.java:[118]
[ERROR] @Nullable List<ZipArchiveEntry> childList = children.get(parent);
[ERROR] ^^^^^^^^
[ERROR] Access restriction: The type 'Nullable' is not API
(restriction on classpath entry
'/home/hudson/jenkins-slave-tracecompass/workspace/tracecompass-gerrit/.repository/p2/osgi/bundle/org.eclipse.jdt.annotation/2.2.200.v20180921-1416/org.eclipse.jdt.annotation-2.2.200.v20180921-1416.jar')
_______________________________________________
cross-project-issues-dev mailing list_
_cross-project-issues-...@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit_
_https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
[attachment "image001.gif" deleted by Daniel Megert/Zurich/IBM]
_______________________________________________
cross-project-issues-dev mailing list_
_cross-project-issues-...@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit_
_https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
