You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2013/09/25 11:08:03 UTC
[jira] [Comment Edited] (SLING-3102) Inconsistent behaviour when
loading archetypes in new Sling bundle project wizard
[ https://issues.apache.org/jira/browse/SLING-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777293#comment-13777293 ]
Stefan Egli edited comment on SLING-3102 at 9/25/13 9:06 AM:
-------------------------------------------------------------
I think we won't get around without adding some support for archetype discovery here - it seems like m2eclipse (or for that matter maven)'s handling of archetypes is slightly non intuitive. From what I understand:
* m2eclipse maintains a list of archetype catalogs. By default the list contains three entries: internal, local and remote. The user can add additional ones.
* without any further ado, m2eclipse doesn't notice new archetypes being generated in public repositories (someone correct me if I'm wrong).
* hence it seems like we need to kick maven/m2eclipse to update the archetype catalogs to find new published archetypes (like the one we have in granite)
* the current way to deal with this fact in slingclipse is to install an embedded version of the archetype in the local repository - this is probably not what we want in the final version..
* another way would be to trigger a 'crawl' using the following maven command:
mvn archetype:crawl -Dcatalog=/home/<me>/.m2/archetype-catalog.xml
(see http://stackoverflow.com/questions/635543/what-are-the-urls-of-all-the-maven-archetype-catalogs-that-you-know-about)
this regenerates the local (ie ~/.m2/archetype-catalog.xml) and should learn from any configured repository.
I doubt that there is an API in m2eclipse which allows an archetype:crawl command - so it's probably up to issuing a 'raw' maven command here..
The whole thing could be an optional step in the 'new sling project' wizard, in case the archetype does not show up properly as expected.
wdyt?
was (Author: egli):
we need to give the unfamiliar user some help here - it seems like m2eclipse (or for that matter maven)'s handling of archetypes is slightly non intuitive. From what I understand:
* m2eclipse maintains a list of archetype catalogs. By default the list contains three entries: internal, local and remote. The user can add additional ones.
* without any further ado, m2eclipse doesn't notice new archetypes being generated in public repositories (someone correct me if I'm wrong).
* hence it seems like we need to kick maven/m2eclipse to update the archetype catalogs to find new published archetypes (like the one we have in granite)
* the current way to deal with this fact in slingclipse is to install an embedded version of the archetype in the local repository - this is probably not what we want in the final version..
* another way would be to trigger a 'crawl' using the following maven command:
mvn archetype:crawl -Dcatalog=/home/<me>/.m2/archetype-catalog.xml
(see http://stackoverflow.com/questions/635543/what-are-the-urls-of-all-the-maven-archetype-catalogs-that-you-know-about)
this regenerates the local (ie ~/.m2/archetype-catalog.xml) and should learn from any configured repository.
I doubt that there is an API in m2eclipse which allows an archetype:crawl command - so it's probably up to issuing a 'raw' maven command here..
The whole thing could be an optional step in the 'new sling project' wizard, in case the archetype does not show up properly as expected.
wdyt?
> Inconsistent behaviour when loading archetypes in new Sling bundle project wizard
> ---------------------------------------------------------------------------------
>
> Key: SLING-3102
> URL: https://issues.apache.org/jira/browse/SLING-3102
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The archetype selection wizard has an inconsistent behaviour
> - sometimes only the 'embedded' archetype is shown
> - sometimes the 'embedded' archetype and the 1.0 versions are shown
> However, I can't get the 1.0.1-SNAPSHOT archetype version, which is supposedly installed by us, to show.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira