[ https://issues.apache.org/jira/browse/SLING-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-3136. ------------------------------------ Resolution: Fixed - http://svn.apache.org/viewvc?view=revision&revision=1596528 detect potential content projects by looking for a directory containing both jcr_root and META-INF/vault/filter.xml - http://svn.apache.org/viewvc?view=revision&revision=1596529 use the standard naming of 'Sling Content Project' and 'Sling Bundle Project' for the convert actions - http://svn.apache.org/viewvc?view=revision&revision=1596530 ConvertToBundleAction now considers all Java projects as candidates > Configure -> Convert to Bundle/Content Package project should not assume the > project is Maven-based > --------------------------------------------------------------------------------------------------- > > Key: SLING-3136 > URL: https://issues.apache.org/jira/browse/SLING-3136 > Project: Sling > Issue Type: Improvement > Components: IDE > Reporter: Robert Munteanu > Assignee: Robert Munteanu > Fix For: Sling Eclipse IDE 1.0.0 > > > There are a couple of issues with the way the current configuration actions > are done: > - it is only enabled for Maven projects ; this does not apply to all projects > and is confusing > - for the Content Package action, it only enables itself for projects of type > 'content-package' . This should not be checked against since this packaging > does not exist from a Sling point of view > - for the Content package action, it assumes that the content sync root is > src/main/content/jcr_root, even though it may not exist. > Instead, I propose the following: > 1. Use only the WST facets definition to decide if we can convert a project > to a facet ; I guess for now we can simply disallow projects from having both > facets ( content + bundle ) > 2. Do not make Maven a hard requirement > 3. Use the following heuristic to detect the content sync root: > - look for the following ( can be made configurable later ) directories > - jcr_root > - src/main/content/jcr_root > Whenever such a project is found, make it the default jcr_root directory. If > none is found, ask the user for input. > More specific actions can be done as part of the m2e configurator for content > packages tracked under SLING-3100 . -- This message was sent by Atlassian JIRA (v6.2#6252)