[ https://issues.jboss.org/browse/JBIDE-9424?page=com.atlassian.jira.plugin... ] Fred Bricon commented on JBIDE-9424: ------------------------------------ For your information, you can deploy the helloworld-osgi app from JBoss Tools You need : - Eclipse Indigo Java EE - m2e, available from http://download.eclipse.org/releases/indigo - JBoss Archive Tools and JBossAS Tools, from http://download.jboss.org/jbosstools/updates/nightly/trunk/ - m2eclipse-tycho from the m2e marketplace (Window > Preferences > Maven > Discovery > Open catalog) You need to : - create a JBoss AS 7 server - import helloworld-osgi (from https://github.com/jbossas/quickstart/tree/master/helloworld-osgi) as a Maven Project in Eclipse - open the Project Archive View (Window > show view > other ...) - select the helloworld-osgi project - in the project archive view, right click on helloworld-osgi > New Archive > Jar - change the destination to /jboss-as-helloworld-osgi/target (to avoid polluting your source code) - choose exploded archive if you want - click finish - A Project archives node appears in the Project Explorer view, having a jboss-as-helloworld-osgi.jar node - right click on the jboss-as-helloworld-osgi.jar node (either in the Project Explorer or Project archives view), choose New Fileset - In the root directory input, enter target/classes (or select that folder via the Workspace button) - click finish - right click on the jboss-as-helloworld-osgi.jar node (either in the Project Explorer or Project archives view), Publish to server - select the AS7 instance, choose Always Publish and Autodeploy - In you servers view, start your AS7 instance - See how your bundle writes to the console. And for the sweet part : - add a break point in your code - start AS7 in debug mode - once the thread hits your break point, change some code in your method (add/change a out.writeln(...)) - See how it hot reloads your code \o/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9424?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-9424: ------------------------------------ Also, because I re-use their export operation, only .jar files are supported. No exploded deployments for osgi. Sorry. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9424?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-9424: ------------------------------------ David: As of now, the code basically uses the exact same code as the "export" command for osgi. It removes almost all of the options and sets the values directly. The only time I think this is an issue, though, is when selecting which dependencies to export along with it. As of now, it hard-codes that it will only publish the one osgi bundle which corresponds to the project, and NONE of its dependencies. I'd love to hear some feedback from you when using the feature, so I can know if my usecase is too narrow or if it's reasonable to expect users to move all the bundles over in the add / remove modules wizard. Thanks again! Was kinda awesome that I could get this done so quick. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9424?page=com.atlassian.jira.plugin... ] David Bosschaert commented on JBIDE-9424: ----------------------------------------- Rob: Excellent! Could you send me some instructions on how to set this up so I can play with it? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9424?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-9424: ------------------------------------ I've updated the icon to not violate osgi tm's -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9424?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-9424. -------------------------------- Fix Version/s: 3.3.0.M3 Resolution: Done It seems that the current implementation functions exactly as well as the OSGi launch configuration, and the export mechanism. They allow you to select which modules to include, but do no real dependency management in demanding a required bundle gets included. Export doesn't show an error if you try to export MasterBundle without exporting DependencyBundle. The launch config behaves similarly, without even a warning. In this regard, I'd declare that this jira is closed. It seems in the OSGi launch configuration, it pre-selects "Equinox" as the only possible implementation. I'd need a lot of help from an AS developer to learn how to launch an absolutely bare-bones AS7 OSGi configuration and include the selected bundles in it on-the-fly. I don't think that is something that can be addressed by this JIRA and is not feasible in the short term future. If you have specific ideas or details how that can be accomplished, please feel free to open another JIRA with that request :D -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9424?page=com.atlassian.jira.plugin... ] David Bosschaert edited comment on JBIDE-9424 at 8/22/11 3:35 AM: ------------------------------------------------------------------ {quote}Rob wrote: It seems that the current implementation functions exactly as well as the OSGi launch configuration, and the export mechanism. They allow you to select which modules to include, but do no real dependency management in demanding a required bundle gets included.{quote} You are right that the OSGi launch configuration doesn't force you to do things, but it does help in some regard. By clicking the 'Add Required Bundles' it figures out (by walking Import-Package, Require-Bundle and Fragment-Host headers) what other bundles could be included to satisfy bundle dependencies and selects them for you. Another useful aspect here is the ability to specify start levels and whether a bundle should be started at all. However I agree that this is a larger piece of work and should probably be tracked in another bug :) was (Author: bosschaert): {quote}It seems that the current implementation functions exactly as well as the OSGi launch configuration, and the export mechanism. They allow you to select which modules to include, but do no real dependency management in demanding a required bundle gets included.{quote} You are right that the OSGi launch configuration doesn't force you to do things, but it does help in some regard. By clicking the 'Add Required Bundles' it figures out (by walking Import-Package, Require-Bundle and Fragment-Host headers) what other bundles could be included to satisfy bundle dependencies and selects them for you. Another useful aspect here is the ability to specify start levels and whether a bundle should be started at all. However I agree that this is a larger piece of work and should probably be tracked in another bug :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9424?page=com.atlassian.jira.plugin... ] Libor Zoubek updated JBIDE-9424: -------------------------------- Assignee: Libor Zoubek (was: Rob Stryker) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9424?page=com.atlassian.jira.plugin... ] Libor Zoubek closed JBIDE-9424. ------------------------------- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira