All,<div><br></div><div>I&#39;m also experiencing linkage errors which wasn&#39;t the case with the beta series.</div><div><br></div><div>I have some code that uses the google guava stuff.  And now I have to remove the scope provided in order to have the plugin installed successfully.</div>
<div><div>    &lt;dependency&gt;</div><div>      &lt;groupId&gt;com.google.guava&lt;/groupId&gt;</div><div>      &lt;artifactId&gt;guava&lt;/artifactId&gt;</div><div>      &lt;version&gt;r06&lt;/version&gt;</div><div>    &lt;/dependency&gt;</div>
<div><br></div><div>I also see that the up- and down-key don&#39;t scroll through the history anymore (or was that my imagination that it used to do that)</div><div><br></div><div>version:  CR1, OS : Windows (yes one of the die-hard&#39;s ;) )</div>
<div><br></div><div>regards</div><div>Rudy</div><br><div class="gmail_quote">On 14 February 2012 16:09, Ryan Bradley <span dir="ltr">&lt;<a href="mailto:rbradley@redhat.com">rbradley@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Lincoln, frankly, I&#39;m stumped by this one.  I never received a
    LoaderConstraintViolation or anything similar.  My issue was with
    the seam-render not being added as a module to the plugin, since it
    was already included with the Forge core.  However, that issue has
    since been resolved.<br>
    <br>
    Thomas, I&#39;m not sure of the cause of your exception, as including
    seam-render and MVEL as dependencies solved the problem for me.  If
    I understand your most recent e-mail correctly, your problem is
    solved if MVEL is manually added to module.xml?  MVEL is not
    required for my ScaffoldProvider implementation, so maybe you are
    experiencing a similar problem?<br>
    <br>
    Sorry,<br>
    Ryan<br>
    <br>
    On 02/13/2012 07:15 PM, Lincoln Baxter, III wrote:
    <blockquote type="cite">Ryan, how did you get around this?<br>
      <br>
      Thomas, perhaps you could try including seam-render instead of
      MVEL? Make sure you use the same version that Forge Shell uses as
      a temporary workaround.<br>
      <br>
      ~Lincoln<br>
      <br>
      <div class="gmail_quote">
        On Mon, Feb 13, 2012 at 5:33 PM, Thomas Frühbeck <span dir="ltr">&lt;<a href="mailto:fruehbeck@aon.at" target="_blank">fruehbeck@aon.at</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
          Hi Ryan, Lincoln<br>
          <div><br>
            &gt; I ran into similar problems with my own plugin
            development.  Including<br>
            &gt; MVEL as a Maven dependency in your pom.xml should
            resolve this issue.<br>
            <br>
          </div>
          this is exactly what I have tried to do. This will really look
          ugly :/<br>
          I will write it as clear as possible:<br>
          <br>
          in pom.xml  I added:<br>
          &lt;dependency&gt;<br>
          &lt;groupId&gt;org.mvel&lt;/groupId&gt;<br>
          &lt;artifactId&gt;mvel2&lt;/artifactId&gt;<br>
          &lt;scope&gt;compile&lt;/scope&gt;<br>
          &lt;/dependency&gt;<br>
          <br>
          On forge install-plugin ~/blabla/  I get:<br>
          ***SUCCESS*** Installed from [plugin-faces-idaware]
          successfully.<br>
          Wrote
          /home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware<br>
          Wrote
/home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware/1.0.0-SNAPSHOT-6c38c8fd-45f4-4736-ad0a-467dc9154a11<br>
          Wrote
/home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware/1.0.0-SNAPSHOT-6c38c8fd-45f4-4736-ad0a-467dc9154a11/plugin-faces-id-aware.jar<br>
          Wrote
/home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware/1.0.0-SNAPSHOT-6c38c8fd-45f4-4736-ad0a-467dc9154a11/module.xml<br>
          Wrote
/home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware/dependencies<br>
          Wrote
/home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware/dependencies/1.0.0-SNAPSHOT-6c38c8fd-45f4-4736-ad0a-467dc9154a11<br>
          Wrote
/home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware/dependencies/1.0.0-SNAPSHOT-6c38c8fd-45f4-4736-ad0a-467dc9154a11/metawidget-all-2.0.jar<br>
          Wrote
/home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware/dependencies/1.0.0-SNAPSHOT-6c38c8fd-45f4-4736-ad0a-467dc9154a11/mvel2-2.1.Beta7.jar<br>
          Wrote
/home/thomas/.forge/plugins/at/tfr/forge/plugin-faces-id-aware/dependencies/1.0.0-SNAPSHOT-6c38c8fd-45f4-4736-ad0a-467dc9154a11/module.xml<br>
          <br>
          So to me it is clear, that I was successful, integration of
          Mvel libraries is done.<br>
          But when I invoke my plugin, I get _a
          LoaderConstraintViolation_!!<br>
          <br>
          [myidaware] myidaware $ set VERBOSE true<br>
          [myidaware] myidaware $ scaffold from-entity
          at.tfr.test.model.* --scaffoldType idaware<br>
          Use which scaffold provider?<br>
          <br>
            1 - [idaware]<br>
            2 - [faces]*<br>
          <br>
           ? Choose an option by typing the number of the selection
          [*-default]  [0] 1<br>
          <div>***ERROR*** [scaffold from-entity] loader
            constraint violation: loader (instance of
            org/jboss/modules/ModuleClassLoader) previously initiated
            loading for a different type with name
            &quot;org/mvel2/templates/CompiledTemplate&quot;<br>
          </div>
          org.jboss.forge.shell.exceptions.CommandExecutionException:
          loader constraint violation: loader (instance of
          org/jboss/modules/ModuleClassLoader) previously initiated
          loading for a different type with name
          &quot;org/mvel2/templates/CompiledTemplate&quot;<br>
          <br>
          Caused by: java.lang.LinkageError: loader constraint
          violation: loader (instance of
          org/jboss/modules/ModuleClassLoader) previously initiated
          loading for a different type with name
          &quot;org/mvel2/templates/CompiledTemplate&quot;<br>
          <br>
          <br>
          So for me it is evident, that I brought my own Mvel jar, but
          the module loader will not let me use it!<br>
          <div>
            <div><br>
              Regards,<br>
              Thomas<br>
              _______________________________________________<br>
              forge-dev mailing list<br>
              <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
              <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
      <br clear="all"><span class="HOEnZb"><font color="#888888">
      <br>
      -- <br>
      Lincoln Baxter, III<br>
      <a href="http://ocpsoft.com" target="_blank">http://ocpsoft.com</a><br>
      <a href="http://scrumshark.com" target="_blank">http://scrumshark.com</a><br>
      &quot;Keep it Simple&quot;<br>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
forge-dev mailing list
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a>
</pre>
    </font></span></blockquote>
    <br>
  </div>

<br>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Rudy De Busscher<br><a href="http://www.c4j.be" target="_blank">http://www.c4j.be</a><br><br>
</div>