Hi,
I can’t reproduce the issue in my development environments (Neither on Luna nor Mars, with respectively JDT 3.10.0-2014-09-02 and JDT 3.11.0-2014-09-17)
Camille
Hi,
- Indeed i got the same error.
- No idea how to solve it without adding org.eclipse.xtext.common.types in the manifest
- Explanation :
An incremental Java compiler. Implemented as an Eclipse builder, it is based on technology evolved from VisualAge for Java compiler. In particular, it allows to run and debug code which still contains unresolved errors.
o whereas Hudson/maven/tycho use
- Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
o Its working fine in Papyrus 1.0.0 and on Hudson
o There was a change of version in jdt core (org.eclipse.jdt.core_3.10.0.v20140604-1726.jar to org.eclipse.jdt.core_3.11.0.v20140806-1653.jar)
ð My guess there is some regression on the new version of the eclipse java incremental compiler
I didn’t find any referenced bugs between org.eclipse.jdt.core and guice
Regards,
Benoit Maggi
Hi, team,
For some while, now, I have had a compilation error in my workspace in code that I don't work on:
Plug-in: org.eclipse.papyrus.infra.gmfdiag.css.configuration
Class: org.eclipse.papyrus.infra.gmfdiag.css.configuration.providers.StylesheetLabelProvider
Error: The type org.eclipse.xtext.common.types.access.IJvmTypeProvider$Factory cannot be resolved. It is indirectly referenced from required .class files
As indicated, the compile-time classpath for this source file is incomplete. The usual reason for this is that the bundle manifest is missing a package-import or require-bundle for an API dependency that a declared dependency does not re-export.
Am I the only one with this error? Why does it not break the build? And how can I fix it in my local environment without changing this plug-in's bundle manifest, if indeed it is a problem in my development environment, as is suggested by the fact that the nightly builds succeed?
To change your delivery options, retrieve your password, or unsubscribe from this list, visit