[
https://issues.apache.org/jira/browse/SLING-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003372#comment-14003372
]
Robert Munteanu commented on SLING-3174:
----------------------------------------
I'm going to need to move some functionality out of the eclipse-m2e-ui plugin,
notably the
org.apache.sling.ide.eclipse.ui.wizards.np.AbstractNewSlingApplicationWizard
class to make it reusable for this task.
That class will move to eclipse-ui, with the Maven-specific functionality
remaining in eclipse-m2e-ui as an AbstractNewMavenBasedSlingApplicationWizard (
or a better name , if someone suggests one )
> Add new simple project content wizard
> -------------------------------------
>
> Key: SLING-3174
> URL: https://issues.apache.org/jira/browse/SLING-3174
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Reporter: Stefan Egli
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> We should include a new wizards which creates a simple content 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 this wizard would do very trivial
> tasks, IMO this will help users kickstart projects and get into the mindset
> of slingclipse.
> The initial content should be something like
> {code}
> .
> ├── jcr_root
> │ ├── content
> │ └───── example
> └── META-INF
> └── vault
> ├── config.xml
> ├── filter.xml
> └── settings.xml
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
