Export-Package is something your plugin exports for other plugins to use. Since you have just one plugin, there's no need for that header. I think you should link all third-party libraries that are not present in Eclipse (including Cayenne itself) just like you did before (using Bundle-Classpath), but link all Eclipse-contained bundles using Require-Bundle, like you do now. Also, we need to decide what versions of Eclipse we're supporting (I suggest Eclipse 3.5+) and maybe remove bundle-version attribute
2011/6/23 Eshan Sudharaka <[email protected]> > ---------- Forwarded message ---------- > From: Eshan Sudharaka <[email protected]> > Date: Thu, Jun 23, 2011 at 12:36 PM > Subject: Re: Gsoc project Patch > To: [email protected] > > > Manifest-Version: 1.0 > Bundle-Name: Cayenne Modeler Plugin for Eclipse > Created-By: Apache Maven Bundle Plugin > Bundle-Vendor: Apache Cayenne > Build-Jdk: 1.6.0_11 > Bundle-Version: 3.1.0.SNAPSHOT > Bnd-LastModified: 1308209524304 > Bundle-Activator: org.apache.cayenne.Activator > Bundle-ManifestVersion: 2 > Bundle-SymbolicName: cayenne-modeler-eclipse-plugin;singleton:=true > Require-Bundle: org.eclipse.ui;bundle-version="3.5.1";visibility:=reexport, > org.eclipse.ui.editors;bundle-version="3.5.0";visibility:=reexport, > org.eclipse.jface.text;bundle-version="3.5.1";visibility:=reexport, > org.eclipse.ui.ide;bundle-version="3.5.1";visibility:=reexport, > org.eclipse.ui.navigator;bundle-version="3.4.1";visibility:=reexport, > org.eclipse.ui.views;bundle-version="3.4.1", > org.eclipse.core.resources, > org.eclipse.ui.navigator.resources, > org.eclipse.ui.console;bundle-version="3.4.0", > org.eclipse.ltk.ui.refactoring;bundle-version="3.4.100", > > > org.eclipse.ui.workbench.texteditor;bundle-version="3.5.1";visibility:=reexport, > org.eclipse.core.filesystem;bundle-version="1.2.1" > Export-Package: org.overture.ide.ui, > org.apache.cayenne.extentions.*, > org.apache.cayenne.cayenne-modeler, > org.apache.cayenne.unpublished.cayenne-project-unpublished, > org.apache.cayenne.unpublished.cayenne-jdk1.5-unpublished, > org.apache.cayenne.cayenne-tools, > org.apache.cayenne.unpublished.cayenne-wocompat-unpublished, > org.apache.cayenne.unpublished.cayenne-di-unpublished > > > I created manifest file manually (with out using felix plugin). But it > seems > that export packages are not loading. Do i need to put those packages in to > class path ? Since manifest contains errors i can not run this as a eclipse > application from eclipse IDE. > > I found a example pom file which uses felix and now trying to do it in this > way. > > > http://dirstudio-ldap-tooling.googlecode.com/svn/trunk/persistence-tooling/persistence-ui/pom.xml > > > On Wed, Jun 22, 2011 at 6:07 PM, Eshan Sudharaka <[email protected] > >wrote: > > > hi, > > > > On Wed, Jun 22, 2011 at 2:28 AM, Andrey Razumovsky < > > [email protected]> wrote: > > > >> Let me join the discussion.. > >> > >> Eshan, the new dependencies are Eclipse dependencies, right? Are they > >> *default* Eclipse bundles? > > > > > > yes. They all are included in Eclipse bundles. > > > > If so, it is incorrect to provide them as Maven > >> dependencies, because they will be included in our bundle, while they > are > >> already in Eclipse. It's also incorrect to rely on certain Eclipse > bundles > >> (like workbench-3.6.1.M20100826-1330.jar), because plugin can be run in > >> different versions of Eclipse. > >> > >> I strongly advice you to add all Eclipse bundles via Require-Bundle > header > >> in manifest, and do not mess with Maven currently at all.. We can figure > >> out > >> how to build plugin using Maven later. > >> Currently manifest in your patch contains lots of unneeded stuff, it > >> should > >> be really little (most of Private-Package and Import-Package would go > >> away, > >> since Eclipse bundles would be attached via Require-Bundle). I'm pretty > >> sure > >> this is the only correct way. > >> > >> Good luck! > >> > > thanks for the help. > > > >> > >> 2011/6/21 Andrus Adamchik <[email protected]> > >> > >> > > >> > On Jun 21, 2011, at 4:46 AM, Aristedes Maniatis wrote: > >> > > >> > > Isn't there a process for submitting artifacts to central? > >> > > >> > BTW, I tried to investigate that for core Cayenne dependencies still > >> > sitting on objectstyle.org. Central has a requirement to have a -src > >> and > >> > -javadoc artifacts submitted with the binary. This is a reasonable > >> > expectation for an open source project, but in practice it means a bit > >> of an > >> > effort to prepare a compatible distro. > >> > > >> > E.g. it took some time to even find the SVN for Hessian: svn:// > >> > svn.caucho.com/resin/ And now I have to checkout everything to find > the > >> > sources for the right version of Hessian, the figure out how to build > >> it. > >> > > >> > But in case of Eclipse and friends that seems moot, as it is all in > >> their > >> > p2 repositories already. So it is a question of an appropriate > adapter, > >> like > >> > Tycho. (this is my assumption anyways; I am not an Eclipse dev of > >> course). > >> > > >> > Some more googling shows that Nexus Professional can proxy p2 repos ( > >> > http://www.sonatype.com/books/nexus-book/reference/p2.html), which is > >> not > >> > very helpful either (we don't have a "canonical" install of Nexus > >> > Professional). > >> > > >> > Andrus > >> > > >> > > >> > >> > >> -- > >> Andrey > >> > > > > > > > > -- > > *~Thanks & Regards~* > > *** > > * > > P.A.Eshan Sudharaka > > Dept of Computer Science and Engineering > > University of Moratuwa > > Sri Lanka > > http://esudharaka.blogspot.com/ > > > > > > > -- > *~Thanks & Regards~* > *** > * > P.A.Eshan Sudharaka > Dept of Computer Science and Engineering > University of Moratuwa > Sri Lanka > http://esudharaka.blogspot.com/ > > > > > -- > *~Thanks & Regards~* > *** > * > P.A.Eshan Sudharaka > Dept of Computer Science and Engineering > University of Moratuwa > Sri Lanka > http://esudharaka.blogspot.com/ > -- Andrey
