Mailing-List: contact users-help@groovy.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@groovy.incubator.apache.org
Subject: Re: IntelliJ/Maven/GMavenPlus project, groovy scripts and run
 CLASSPATH
To: users@groovy.incubator.apache.org
References: <560CE0D6.6080802@gmx.com>
 <CAL2qGUGoOfd=3nDz2M4ZJ=vDo5wQyhWvpEQ7qc_b=a6PGeCGSg@mail.gmail.com>
From: Maarten Boekhold <boekhold@gmx.com>
Message-ID: <5610D55F.5080302@gmx.com>
Date: Sun, 4 Oct 2015 11:29:35 +0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: 
 <CAL2qGUGoOfd=3nDz2M4ZJ=vDo5wQyhWvpEQ7qc_b=a6PGeCGSg@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------040207070607010008030108"

This is a multi-part message in MIME format.
--------------040207070607010008030108
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Keegan,

Let me describe how everything is normally run in "deployed mode", and 
then what my development environment in maven/IntelliJ looks like.

Deployed mode:

  * Java code/jars are installed in ${dir}/lib
  * Groovy code installed in ${dir}/scripts
      o This is a mix of interface declarations, 'real classes' and
        scripts, uncompiled
  * Start/stop scripts in ${dir}/etc
  * CLASSPATH /only/ has the JAR files from under ${lib} in it!
  * When running the program, a configuration file tells the application
    to load/parseClass() all groovy files under ${dir}/scripts using a
    GroovyClassLoader instance. There is some logic there to load/parse
    things in order so as to handle dependency issues between
    classes/scripts. The resulting classes are cached in a Map. Based on
    certain events (data mapping requests) a class instance is retrieved
    from the Map, instantiated and run.
      o In fact, the application uses the JSR223 API to load things, and
        under the hood, that uses GroovyClassLoader.parseClass()


Maven/IntelliJ:

  * Java code under src/main/java
  * Groovy code under src/main/groovy
  *  From the "Maven Projects" tool window, I use "mvn clean compile" to
    compile all code. This *also* compiles all groovy files and
    generates class files under target/classes!
  * I have a "Run Configuration" that uses the "classpath of module".
  * The configuration file tells the main application "load all groovy
    files under src/main/groovy"
  * The problem here is that when building the project, 'mvn clean
    compile' also compiles all groovy scripts to target/classes.
  * When I now run my run configuration, the /groovy classes/interfaces/
    are already on the CLASSPATH, so there's a conflict between running
    the scripts as loaded by GroovyClassLoader.parseClass() and the ones
    that are already on the classpath. I'm getting lots of
    GroovyClassCastExceptions because it's trying to cast to classes
    that are loaded by a different classloader (eg from the classpath).
    This is the thing I need to avoid/fix.
      o I also need to write unit tests for the groovy code, and for
        that I do need all groovy code on the test-classpath, just to
        complicate things a bit more. Btw for those unit tests there's
        no loading of classes via GroovyClassLoader/jsr223 involved, so
        that makes things a bit simpler again.

I could of course just remove GMavenPlus from my pom.xml, but then my 
groovy code isn't compiled at all, and I do want that "safety net" to 
capture errors in that part of the (groovy) code.

Still a bit of a complicated description I guess, but I hope it's a 
little bit more clear what I'm trying to achieve now.

Maarten

On 2015-10-04 07:16, Keegan Witt wrote:
> How about adding them in a non-standard directory (to avoid IntelliJ 
> knowing where they are) then add them as test sources to GMavenPlus?  
> If that'd work, please see here 
> <https://github.com/groovy/GMavenPlus/wiki/Examples#additional-sources> for 
> an example.  It might not though, because I'm not sure I'm fully 
> understanding your use case.  It wasn't clear to me how you were 
> deploying the scripts so you could do the 
> GroovyClassLoader.parseClass() calls in production.
>
> -Keegan
>
> On Thu, Oct 1, 2015 at 3:29 AM, Maarten Boekhold <boekhold@gmx.com 
> <mailto:boekhold@gmx.com>> wrote:
>
>     Hi all,
>
>     Not strictly a groovy-specific question I believe, but I also
>     believe that if anybody knows the answer to this, they'll be on
>     this list.
>
>     I am working on a project that is mixed Java and groovy code. I'm
>     developing in IntelliJ, it's a maven project that is using
>     GMavenPlus (1.5).
>
>     When the resulting artifact is run after I have installed it, the
>     groovy scripts should***not* be on the CLASSPATH of the
>     application; instead they are loaded dynamically
>     (GroovyClassLoader.parseClass()). So, also inside IntelliJ, when
>     running or debugging the full application, I want to exclude the
>     groovy sources (or compiled artifacts) from the CLASSPATH.
>     However, while developing I *do* want these scripts to be
>     *compiled *so I can see any errors. Also when running unit tests
>     the scripts will need to be on the classpath.
>
>     I'm looking for a way to achieve the following:
>     - Groovy sources are compiled when building the project
>     - Groovy artifacts are NOT on the CLASSPATH when running/debugging
>     the application inside IntelliJ
>     - Groovy artifacts ARE on the CLASSPATH when running unit tests
>
>     Does anybody have any idea how to do this?
>
>     Maarten
>
>


--------------040207070607010008030108
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Keegan,<br>
    <br>
    Let me describe how everything is normally run in "deployed mode",
    and then what my development environment in maven/IntelliJ looks
    like.<br>
    <br>
    Deployed mode:<br>
    <ul>
      <li>Java code/jars are installed in ${dir}/lib</li>
      <li>Groovy code installed in ${dir}/scripts</li>
      <ul>
        <li>This is a mix of interface declarations, 'real classes' and
          scripts, uncompiled<br>
        </li>
      </ul>
      <li>Start/stop scripts in ${dir}/etc</li>
      <li>CLASSPATH <i>only</i> has the JAR files from under ${lib} in
        it!</li>
      <li>When running the program, a configuration file tells the
        application to load/parseClass() all groovy files under
        ${dir}/scripts using a GroovyClassLoader instance. There is some
        logic there to load/parse things in order so as to handle
        dependency issues between classes/scripts. The resulting classes
        are cached in a Map. Based on certain events (data mapping
        requests) a class instance is retrieved from the Map,
        instantiated and run.</li>
      <ul>
        <li>In fact, the application uses the JSR223 API to load things,
          and under the hood, that uses GroovyClassLoader.parseClass()<br>
        </li>
      </ul>
    </ul>
    <br>
    Maven/IntelliJ:<br>
    <ul>
      <li>Java code under src/main/java</li>
      <li>Groovy code under src/main/groovy</li>
      <li>From the "Maven Projects" tool window, I use "mvn clean
        compile" to compile all code. This *also* compiles all groovy
        files and generates class files under target/classes!<br>
      </li>
      <li>I have a "Run Configuration" that uses the "classpath of
        module".</li>
      <li>The configuration file tells the main application "load all
        groovy files under src/main/groovy"</li>
      <li>The problem here is that when building the project, 'mvn clean
        compile' also compiles all groovy scripts to target/classes.</li>
      <li>When I now run my run configuration, the <i>groovy
          classes/interfaces</i> are already on the CLASSPATH, so
        there's a conflict between running the scripts as loaded by
        GroovyClassLoader.parseClass() and the ones that are already on
        the classpath. I'm getting lots of GroovyClassCastExceptions
        because it's trying to cast to classes that are loaded by a
        different classloader (eg from the classpath). This is the thing
        I need to avoid/fix.</li>
      <ul>
        <li>I also need to write unit tests for the groovy code, and for
          that I do need all groovy code on the test-classpath, just to
          complicate things a bit more. Btw for those unit tests there's
          no loading of classes via GroovyClassLoader/jsr223 involved,
          so that makes things a bit simpler again.<br>
        </li>
      </ul>
    </ul>
    <p>I could of course just remove GMavenPlus from my pom.xml, but
      then my groovy code isn't compiled at all, and I do want that
      "safety net" to capture errors in that part of the (groovy) code.<br>
    </p>
    <p>Still a bit of a complicated description I guess, but I hope it's
      a little bit more clear what I'm trying to achieve now.<br>
    </p>
    <p>Maarten<br>
    </p>
    <div class="moz-cite-prefix">On 2015-10-04 07:16, Keegan Witt wrote:<br>
    </div>
    <blockquote
cite="mid:CAL2qGUGoOfd=3nDz2M4ZJ=vDo5wQyhWvpEQ7qc_b=a6PGeCGSg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>How about adding them in a non-standard directory (to avoid
          IntelliJ knowing where they are) then add them as test sources
          to GMavenPlus?  If that'd work, please see <a
            moz-do-not-send="true"
href="https://github.com/groovy/GMavenPlus/wiki/Examples#additional-sources">here</a>
          for an example.  It might not though, because I'm not sure I'm
          fully understanding your use case.  It wasn't clear to me how
          you were deploying the scripts so you could do the
          GroovyClassLoader.parseClass() calls in production.<br>
          <br>
        </div>
        -Keegan<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Oct 1, 2015 at 3:29 AM, Maarten
          Boekhold <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:boekhold@gmx.com" target="_blank">boekhold@gmx.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"> Hi all,<br>
              <br>
              Not strictly a groovy-specific question I believe, but I
              also believe that if anybody knows the answer to this,
              they'll be on this list.<br>
              <br>
              I am working on a project that is mixed Java and groovy
              code. I'm developing in IntelliJ, it's a maven project
              that is using GMavenPlus (1.5).<br>
              <br>
              When the resulting artifact is run after I have installed
              it, the groovy scripts should<b> </b><b>not</b> be on the
              CLASSPATH of the application; instead they are loaded
              dynamically (GroovyClassLoader.parseClass()). So, also
              inside IntelliJ, when running or debugging the full
              application, I want to exclude the groovy sources (or
              compiled artifacts) from the CLASSPATH. However, while
              developing I <b>do</b> want these scripts to be <b>compiled

              </b>so I can see any errors. Also when running unit tests
              the scripts will need to be on the classpath.<br>
              <br>
              I'm looking for a way to achieve the following:<br>
              - Groovy sources are compiled when building the project<br>
              - Groovy artifacts are NOT on the CLASSPATH when
              running/debugging the application inside IntelliJ<br>
              - Groovy artifacts ARE on the CLASSPATH when running unit
              tests<br>
              <br>
              Does anybody have any idea how to do this?<span
                class="HOEnZb"><font color="#888888"><br>
                  <br>
                  Maarten<br>
                </font></span></div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------040207070607010008030108--