Just put a copy of osgi.annotation.jar in your repo. It's not big :-) Then you are self-contained. --
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From: Raymond Auge <raymond.a...@liferay.com> To: Equinox development mailing list <equinox-dev@eclipse.org> Date: 2014/04/10 09:44 Subject: Re: [equinox-dev] branch for R6 Sent by: equinox-dev-boun...@eclipse.org Next concern is that this is a cross repo dependency. Is it ok for a bundle in one repo to reference a bundle in another repo? jars.extra.classpath = platform:/plugin/org.eclipse.osgi/osgi/osgi.annotation.jar Aren't these repos "theoretically" standalone for the purpose of building? - Ray On Thu, Apr 10, 2014 at 9:08 AM, Thomas Watson <tjwat...@us.ibm.com> wrote: For what its worth, the equinox build does build against the OSGi classes from other bundles in equinox. BJ says, people should also not compile against an OSGi framework implementation to get OSGi packages. That may be true, but in equinox our bundles most definitely do compile against org.eclipse.osgi to get the core osgi packages because in our build org.eclipse.osgi is considered just another bundle. That is just how our mavin/tycho build works. Other than that tidbit I agree with BJ about how to proceed with the annotations.jar. Tom BJ Hargrave---04/10/2014 06:49:08 AM---See http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/org.eclipse.osgi/osgi/os From: BJ Hargrave/Austin/IBM@IBMUS To: Equinox development mailing list <equinox-dev@eclipse.org>, Date: 04/10/2014 06:49 AM Subject: Re: [equinox-dev] branch for R6 Sent by: equinox-dev-boun...@eclipse.org See http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/org.eclipse.osgi/osgi/osgi.annotation.jar . The projects build.properties includes it as an extra jar: http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/org.eclipse.osgi/build.properties#n34 The org.osgi.annotation.versioning package is not a runtime package. Therefore, an OSGi framework must not include that package and must not export that package at runtime. People should also not compile against an OSGi framework implementation to get the OSGi packages. Your project can do the same for osgi.annotation.jar as the org.eclipse.osgi project. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From: Raymond Auge <raymond.a...@liferay.com> To: Equinox development mailing list <equinox-dev@eclipse.org> Date: 2014/04/09 22:26 Subject: [equinox-dev] branch for R6 Sent by: equinox-dev-boun...@eclipse.org Is there an rt.equinox.framework R6 branch? I don't see one which includes org.osgi.annotation.versioning package. The latest http spec depends on this annotation unless I strip the Version package annotation from this work. Thoughts? -- Raymond Augé (@rotty3000) Senior Software Architect Liferay, Inc. (@Liferay) _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev -- Raymond Augé (@rotty3000) Senior Software Architect Liferay, Inc. (@Liferay) _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<image/gif>>
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
