[
https://issues.jboss.org/browse/JBDS-2144?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-2144:
-------------------------------------
The issue happens because Forge doesn't consult the settings.xml file when solving
maven dependencies.
Burr,
You can check this by adding JBoss Maven EAP repository to the project's pom.xml
file.
I have created a pull request for the Forge -
https://github.com/forge/core/pull/157. The
Forge Runtime doesn't have any option to change the user or global settings file so
that settings.xml has to be in a default location ($USER_HOME/.m2/.settings.xml
The patched forge distribution is placed at
https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/forge/forge-d...
If you use this distribution, you won't have to add the JBoss Maven EAP repository to
the project's pom.xml.
Martin,
I am not sure why you can't reproduce the issue. It is always reproducible.
How did you add the JBoss Maven EAP Repository?
JBDS 5 Beta 3 - enterprise=true breaks Forge
--------------------------------------------
Key: JBDS-2144
URL:
https://issues.jboss.org/browse/JBDS-2144
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.0.0.Beta3
Environment: Version: 5.0.0.Beta3
Build id: v20120514-2058-H159-Beta3
Build date: 20120514-2058
Reporter: Burr Sutter
Assignee: Koen Aers
Priority: Blocker
Fix For: 5.0.0.CR1
Attachments: Forge_Beta3_bug.png, JBDS.log, pom.xml, settings.xml
steps to reproduce:
1) Click on Java EE Web Project in JBoss Central
2) Select EAP6 Beta2 as the Target Runtime - assumes you have updated the settings.xml
with the correct EAP6.1 maven repo
3) Run As on Server works
4) Right-click on Project name and select Show In Forge Console
5) Type "entity" and hit return
[jboss-javaee6-webapp-eap] jboss-javaee6-webapp-eap $ entity
***ERROR*** [entity] Plugin is not usable in current scope or project
attached is the pom.xml for the 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