[jbosstools-issues] [JBoss JIRA] (JBIDE-10710) ***ERROR*** [entity] Plugin is not usable in current scope or project.

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662396#comment-12662396 ] 

Max Rydahl Andersen commented on JBIDE-10710:
---------------------------------------------

not every archetype - just the quickstarts distributed with AS ;)

Won't sourcescanning cause a rather large overhead for this ?

in jbosstools maven integration we consider the marker files first, then dependency names and in some cases lookup specific classes in classpath (i.e. JSF's Application) to know (and also to seperate what version is being used).

                
> ***ERROR*** [entity] Plugin is not usable in current scope or project.
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-10710
>                 URL: https://issues.jboss.org/browse/JBIDE-10710
>             Project: Tools (JBoss Tools)
>          Issue Type: Component  Upgrade
>            Reporter: Burr Sutter
>            Assignee: Koen Aers
>            Priority: Critical
>         Attachments: myproject.zip
>
>
> Steps to reproduce:
> - Select the "Java EE Web Project" from JBoss Central
> - Name it "myproject" with package "com.myproject"
> - Start the Forge console with Ctrl-4/Command-4
> - at the forge console type "pwd" - that should indicate it is in the current workspace
> - "cd myproject"
> - "ls"
> - "entity --named Books"
> result is ***ERROR*** [entity] Plugin is not usable in current scope or project.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira