[ https://issues.apache.org/jira/browse/SLING-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801864#comment-13801864 ]
Robert Munteanu commented on SLING-3019: ---------------------------------------- I've implemented the items we've discussed above: * Return messages to clients in JSON format in http://svn.apache.org/viewvc?view=revision&revision=1534644 * Allow installing/updating a bundle from an uploaded jar file in http://svn.apache.org/viewvc?view=revision&revision=1534645 * Some code cleanups in http://svn.apache.org/viewvc?view=revision&revision=1534646 * Refresh packages in install/update in http://svn.apache.org/viewvc?view=revision&revision=1534647 I'm leaving this open in case anyone spots any implementation mistakes or would like some changes made, but I think the feature set is enough for the current Sling IDE Tooling use cases. > Provide a mechanism to install a bundle based on a directory > ------------------------------------------------------------ > > Key: SLING-3019 > URL: https://issues.apache.org/jira/browse/SLING-3019 > Project: Sling > Issue Type: New Feature > Components: IDE > Reporter: Carsten Ziegeler > Assignee: Carsten Ziegeler > > With an IDE integration and incremental builds, it would be great to have a > mechanism to install/update a bundle based on the output directory of a > project. > I'll start with a prototype of a bundle which receives post requests > containing the path of a local directory. The servlet will then either > install or update the bundle from that directory > For this to work, the scr descriptor files of a project should go into a > bundle. So configure the scr plugin like this: > <plugin> > <groupId>org.apache.felix</groupId> > <artifactId>maven-scr-plugin</artifactId> > <configuration> > > <outputDirectory>${project.build.directory}/classes</outputDirectory> > </configuration> > </plugin> -- This message was sent by Atlassian JIRA (v6.1#6144)