[forge-dev] automatic dependency detection too restrictive?

Thomas Frühbeck fruehbeck at aon.at
Tue Feb 14 02:16:17 EST 2012


> Thomas, perhaps you could try including seam-render instead of MVEL?

That's what I had tried before, Now I tried to set the dependency for seam.render to compile:
<dependency>
<groupId>org.jboss.seam.render</groupId>
<artifactId>seam-render</artifactId>
<scope>provided</scope>
</dependency>

...which will be automatically "repaired" by the build:
***WARNING*** Dependency [org.jboss.seam.render:seam-render:jar::] was not correctly marked as PROVIDED scope; this has been corrected.

But the dependency is set anyway, this is not the solution:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<module xmlns="urn:jboss:module:1.0" name="at.tfr.forge.plugin-faces-id-aware" slot="1.0.0-SNAPSHOT-fc1d2212-5a93-47e7-be64-21e1842fc18f">
<resources>
<resource-root path="plugin-faces-id-aware.jar"/>
</resources>
<dependencies>
<module name="at.tfr.forge.plugin-faces-id-aware.dependencies" slot="1.0.0-SNAPSHOT-fc1d2212-5a93-47e7-be64-21e1842fc18f"/>
<module name="org.jboss.forge.javaee.api" services="import"/>
<module name="org.jboss.forge.maven.api" services="import"/>
<module name="org.jboss.forge.scaffold.api" services="import"/>
<module name="org.jboss.forge.shell.api" services="import"/>
<module name="org.jboss.seam.render" services="import"/>
<module name="javax.api"/>
</dependencies>
</module>

> Make sure you use the same version that Forge Shell uses as a temporary workaround.
I did, no avail:

Wrote /home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware/dependencies/1.0.0-SNAPSHOT-fc1d2212-5a93-47e7-be64-21e1842fc18f/mvel2-2.1.Beta7.jar

[myidaware] myidaware $ scaffold from-entity at.tfr.test.model.* --scaffoldType idaware
Use which scaffold provider?

   1 - [idaware]
   2 - [faces]*

  ? Choose an option by typing the number of the selection [*-default]  [0] 1
***ERROR*** [scaffold from-entity] loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "org/mvel2/templates/CompiledTemplate"

That's why I said: dead end :/

But it works if I put the dependency manually in the module.xml:
<module name="org.jboss.forge.shell.api" services="import"/>
<module name="org.jboss.seam.render" services="import"/>
<module name="javax.api"/>
<module name="org.mvel"/>
<module name="javax.persistence.api"/>

[myidaware] myidaware $ scaffold from-entity at.tfr.test.model.* --scaffoldType idaware
Use which scaffold provider?

   1 - [idaware]
   2 - [faces]*

  ? Choose an option by typing the number of the selection [*-default]  [0] 1
  ? [/raid/home/thomas/NetBeansProjects/myidaware/src/main/java/at/tfr/test/view/TestBean.java] File exists, overwrite? [Y/n]
  ? [/raid/home/thomas/NetBeansProjects/myidaware/src/main/webapp/scaffold/test/create.xhtml] File exists, overwrite? [Y/n]





More information about the forge-dev mailing list