-
1. Re: [m2e] [maven-bundle-plugin] Adding OSGI bundle resource to a server
ebelanger070 Jun 20, 2012 3:17 PM (in response to ebelanger070)I found the answer. It seems that JBoss Tools uses the build.properties file that is created in a plugin project to build the resource. What needs to be done is to go in the MANIFEST.MF edition view and generate a build.properties from there. JBoss Tools will now detect the project.
-
2. Re: [m2e] [maven-bundle-plugin] Adding OSGI bundle resource to a server
rob.stryker Jun 21, 2012 2:48 AM (in response to ebelanger070)The code we use to determine whether to turn a project into a deployable osgi feature is:
protected IModule[] createModules(IProject project) { if (!WorkspaceModelManager.isBinaryProject(project) && WorkspaceModelManager.isPluginProject(project)) { IModel model = PluginRegistry.findModel(project); if (model != null && isValidModel(model) && hasBuildProperties((IPluginModelBase) model)) { IModule module = createModule(project.getName(), project.getName(), MODULE_TYPE, VERSION, project); return new IModule[] { module }; } } return null; }
So yes, we require that osgi recognizes it as a plugin project *and* that it has a build properties file :)
-
3. Re: [m2e] [maven-bundle-plugin] Adding OSGI bundle resource to a server
jigneshmpatel Jun 28, 2012 7:32 PM (in response to rob.stryker)After adding build details when I tried to deploy I got following
aused by: java.lang.ClassNotFoundException: com.icare.rpc.registration.RegistrationActivator from [Module "deployment.registration:1.0.0.BUILD-2012-06-25" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:132) [jboss-modules.jar:1.1.1.GA]
at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:114) [jbosgi-framework-core-1.1.8.Final.jar:1.1.8.Final]
at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:415) [jbosgi-framework-core-1.1.8.Final.jar:1.1.8.Final]
at org.jboss.osgi.framework.internal.HostBundleState.loadClass(HostBundleState.java:151) [jbosgi-framework-core-1.1.8.Final.jar:1.1.8.Final]
at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:294) [jbosgi-framework-core-1.1.8.Final.jar:1.1.8.Final]
... 10 more
here is my build.properties file
bin.includes = META-INF/,\
After further research it seems eclipse Indio R2 doesn't recognize the target/classes location.
-
4. Re: [m2e] [maven-bundle-plugin] Adding OSGI bundle resource to a server
maxandersen Jul 30, 2012 3:35 AM (in response to jigneshmpatel)jignesh, Indigo recognize target/classes location if your build.properties file and .classpath/.project files are correct and specify these as its output.