[
https://issues.apache.org/jira/browse/SLING-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002978#comment-14002978
]
Robert Munteanu commented on SLING-3174:
----------------------------------------
I see your point.
For this simple bundle project we must minimally have:
* a MANIFEST.MF
* dependencies to a couple of jars - org.apache.sling.api and javax.servlet
* an OSGi component, probably configured with a XML DS descriptor
I have done this for the
[BundleDeploymentTest|https://github.com/apache/sling/blob/c6b87d8043efde46dad6cb360df738b821da206c/tooling/ide/eclipse-test/src/org/apache/sling/ide/test/impl/BundleDeploymentTest.java#L75],
and therefore know what to do. I see a couple of problems with this approach
though:
* We should not use the DS annotations, because we can't enable a builder which
will generate the XML descriptors
* We do not have access to the Maven repository for dependencies since the
simple archetypes must be Maven-free
My proposal would then be to stick to the Maven-driven process for creating
bundle projects, and only add a wizard for simple content projects for 1.0.0 .
We can always revisit later, but I don't think this is critical for the 1.0.0
release.
[~egli] - how does that sound?
> [Tooling] add 'new simple content/bundle project' wizards
> ---------------------------------------------------------
>
> Key: SLING-3174
> URL: https://issues.apache.org/jira/browse/SLING-3174
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Reporter: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> We should include 'new' wizards which create simple content/bundle projects.
> The project would simply create a faceted project with the according facet
> set and set any additional type specific properties (eg with content it would
> create a jcr_root directory). Although these two wizards would do very
> trivial tasks, IMO this will help users kickstart projects and get into the
> mindset of slingclipse.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
