[
https://issues.apache.org/jira/browse/SLING-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791365#comment-13791365
]
Carsten Ziegeler commented on SLING-3019:
-----------------------------------------
Sure, we could upload the whole jar, but this requires more work to do in
Eclipse - instead of just doing a simple ping to the server.
I believe that in the local case, the current mechanism is a little bit faster
(we could even improve and create the jar just in memory).
The alternative would be to post against the web console and let the web
console do the stuff (install or update, refresh packages etc.) - this would be
the same as the maven sling plugin does ootb
> 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)
