[
https://issues.jboss.org/browse/FORGE-980?page=com.atlassian.jira.plugin....
]
Lennart Jörelid resolved FORGE-980.
-----------------------------------
Labels: documentation (was: )
Assignee: Lennart Jörelid
Resolution: Partially Completed
h2. Workaround
# Define the dependencies-as-resource-root element within the META-INF/forge.xml file
# Your project must also explicitly import any transitive Maven dependencies, as the Forge
ClassLoader structure prevents transitive dependencies to be “seen” by your plugin. A good
help to find all transitive dependencies is the “mvn dependency:tree” command, which
should be run in your Plugin’s Maven project.
Failed retrieving forge modules (ClassNotFoundException:
org.jboss.forge.maven.plugins.Configuration)
-----------------------------------------------------------------------------------------------------
Key: FORGE-980
URL:
https://issues.jboss.org/browse/FORGE-980
Project: Forge
Issue Type: Bug
Reporter: Lennart Jörelid
Assignee: Lennart Jörelid
Labels: documentation
Attachments: jbossForgeClassLoadingDebugging_1_incorrectRejectionMaybe.png,
jbossForgeClassLoadingDebugging_2_okModuleClassLoader.png, jbossForgePlugin.txt
https://community.jboss.org/message/825612
Following a successful build, including unit tests for the Forge plugin, the installation
(forge source-install . ) fails with a ClassNotFoundException:
org.jboss.forge.maven.plugins.Configuration within the ~/.forge/runtime.log.
This class is located in forge-maven-api, which should be available for all plugins being
installed.
--
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