[
https://issues.jboss.org/browse/JBIDE-10710?page=com.atlassian.jira.plugi...
]
Lincoln Baxter III commented on JBIDE-10710:
--------------------------------------------
Hey Max,
I'd rather just implement source scanning, the proper solution - imo. For now, if
people really want to use Forge and Eclipse for something at the same time, they can just
type "blah setup" which will add the blank activator that Forge expects. If
that's a blocker, then we can talk about this, but if not, Forge needs to be locking
down and stabilizing for Final release soon. I don't think this will make it for Final
if we don't absolutely need it.
I agree it needs to be solved, but more and more keeps getting added to Final and it's
adding up :) We had originally said that we would only ensure apps-created with Forge
deploy against AS7; now we're talking about making sure Forge works on every Archetype
without any extra config, and I think this is a bit much creep for Final.
However, if you have someone that has time to work on this for Final, I'll be glad to
assist as much as possible! If we really want to hack it, we could add a facet override
that allows manual installed/not installed settings for individual facets by name.
E.g: `forge> project list-facets`
~Lincoln
***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