[ 
http://jira.codehaus.org/browse/MGROOVY-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stig Lau updated MGROOVY-136:
-----------------------------

    Attachment: groovymixedcompiler.zip

I doodled up a quick mvn'able example of the hen and egg groovy/java compile 
issue. 
This might be a problem concerning Swing GUIBuilder  (where i first saw the 
issue) and not groovy compilation, though

 mvn clean groovy:compile install ...
[INFO] Building Unnamed - no.lau:groovymixedcompiler:jar:1.0
[INFO]    task-segment: [clean, groovy:compile, install] ...
[INFO] [groovy:compile] ...
[ERROR] BUILD ERROR ...
[INFO] startup failed, 
/Volumes/McFeasty/Users/Stig/jobb/utvikling/groovymixedcompiler/src/main/groovy/MechanicGUI.groovy:
 6: unable to resolve class Mechanic 
 @ line 6, column 14.
       Mechanic mechanic
                ^
/Volumes/McFeasty/Users/Stig/jobb/utvikling/groovymixedcompiler/src/main/groovy/MechanicGUI.groovy:
 6: unable to resolve class Mechanic 
 @ line 6, column 14.
       Mechanic mechanic
                ^
/Volumes/McFeasty/Users/Stig/jobb/utvikling/groovymixedcompiler/src/main/groovy/MechanicGUI.groovy:
 12: unable to resolve class Mechanic 
 @ line 12, column 25.
                           new Mechanic().fix(new Car())
                           ^
3 errors

> Complex Mixed compilation howto
> -------------------------------
>
>                 Key: MGROOVY-136
>                 URL: http://jira.codehaus.org/browse/MGROOVY-136
>             Project: GMaven
>          Issue Type: Wish
>    Affects Versions: 1.0-rc-1
>         Environment: Java, Groovy
>            Reporter: Stig Lau
>            Assignee: Jason Dillon
>            Priority: Minor
>             Fix For: 1.0-rc-3
>
>         Attachments: groovymixedcompiler.zip
>
>
> There is a problem with groovy when one has a complex dependencies of java 
> and groovy classes on oneanother.
> Eg. Groovy Domainclasses <-- Java services <-- Groovy XML builder
> One can create workarounds for this by doing several (failing) compilation, 
> which builds the depending layers one at a time.
> The other option is to have the groovy and java layers in seperate modules, 
> which in turn are built correctly, but with unwanted complexity of chai of 
> module dependencies.
> There may be some magic switch I have missed; but if not, this problem should 
> be clarified to all the happy punters who dream of infinate layers of 
> java/groovy interdependencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to