[
https://issues.apache.org/jira/browse/SLING-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781765#comment-13781765
]
Robert Munteanu commented on SLING-3125:
----------------------------------------
Fixed in http://svn.apache.org/viewvc?view=revision&revision=1527531
> Centralize and improve embedded artifact handling
> -------------------------------------------------
>
> Key: SLING-3125
> URL: https://issues.apache.org/jira/browse/SLING-3125
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> We will probably keep our embedded artifact handling, to support cases where
> users don't have access to artifacts we use, and to provide consistency to
> the user experience. I can imagine at least:
> - embedding archetypes to generate projects
> - embedding additional, development-time only, bundles for the sling
> installation
> To make them reusable from multiple contexts, I propose that we
> 1. Package all the embedded artifacts into a single plugin - can be the
> eclipse.core plugin for now, but I'd prefer something like
> org.apache.sling.ide.artifacts
> 2. Create an OSGi DS component which reads the artifacts using the bundle
> context
> 3. Do not hardcode versions. Rather, read them from the embedded manifest -
> for bundles, or pom.properties - for non-OSGi Maven artifacts. Possibly cache
> this information lazily, once it's retrieved.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
