Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Local build error in org.eclipse.papyrus.uml.oclconstraintevaluation plug-in
Hi

It is what JDT used to distribute as the compile-time org.eclipse.jdt.annotation 1.1.0 before they introduced an incompatible load-time 2.0 for Java 8.

It is a compile-time only requirement, since it contains only the @NonNull and @Nullable source annotations.

It is not needed for binary builds so is not in the SDK. Providing it might cause trouble for Java 8 users who need the load-time version.

Papyrus should not need it, since I think Papyrus does not use @NonNull etc. If/when Papyrus does use @NonNull but remains on Java 6/7 it may want org.eclipse.ocl.jdt.annotation7.

The problem is probably due to a leakage from the OCL dev environment that uses @NonNull when fixing Papyrus problems for the promoted OCL code.

So just delete rather than resolve the reference.

How can it be that the Gerrit build approved the patch?

    Regards

        Ed Willink

On 04/02/2015 21:07, Christian W. Damus wrote:
Hi, team,

Today (Mars M5 day) the org.eclipse.papyrus.uml.oclconstraintevaluation plug-in has an error in its build.properties file:

    Bundle org.eclipse.ocl.jdt.annotation7 cannot be resolved

This is in an “additional.bundles” properties in the build.properties.

I have some questions about it:
  • what is the purpose of this bundle? What does it do for this plug-in?
  • is it needed at run-time?  Does it need to be deployed with Papyrus to make our plug-in work?
  • why is it not in the OCL 6.0 M5 SDK that is installed in my PDE target by Oomph?
  • where do I get this bundle to resolve the build problem?
Thanks,

Christian
 




_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5646 / Virus Database: 4281/9056 - Release Date: 02/04/15


Back to the top