[jira] Commented: (MAVEN-1545) Specify target jdk per project in multibuild

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (MAVEN-1545) Specify target jdk per project in multibuild

JIRA jira@codehaus.org
     [ http://jira.codehaus.org/browse/MAVEN-1545?page=comments#action_38729 ]
     
Mark Proctor commented on MAVEN-1545:
-------------------------------------

I'm adding this converation bob and I had with trygvis, to see if it sheds any more light:

[13:35] <trygvis> why didn't brett's solution fix your problem conan?
[13:37] <conan> trygvis: because groovy would not work with jdk1.5, not matter what you set the comile source and target to
[13:37] <trygvis> "not work", how?
[13:37] <conan> trygvis: let me find the groovy jira
[13:37] <bob> trygvis: groovy has bugs
[13:38] <trygvis> well, that's not new is it? :p
[13:38] <bob> nope, but something we have to work around
[13:40] <conan> http://jira.codehaus.org/browse/GROOVY-280 http://jira.codehaus.org/browse/GROOVY-520 http://jira.codehaus.org/browse/GROOVY-477
[13:40] <conan> trygvis: no its not new barry originally opened the jira some time ago, brett closed it off as a "wont fix" - I dont think he fully understood the situation.
[13:41] <trygvis> no, and neither did I
[13:41] <conan> trygvis: we could not compile drools with jdk1.5 because groovy would not work - groovy broke the jdk1.5 verifier.
[13:42] <conan> yes it was a fault of groovy, not jdk/maven, but maven did not facilitate an easy workaround.
[13:42] <trygvis> sounds like the code/bytecode that you're generating is no good, don't see the relation to maven
[13:43] <trygvis> what more did you want from maven? you tell it the source level for you code and it'll use that as a argument to javac
[13:43] <conan> trygvis: no that didn't work with the groovy issue.
[13:43] <bob> use a different javac I'd think
[13:43] <bob> ie, set java.home per project
[13:44] <conan> trygvis: thats what I'm saying if a project like Groovy/ASM does something silly that worked with jdk1.4 but not with jdk1.5 it screws over projects like drools.
[13:44] <trygvis> why would you want to do that? if you build with a 1.5 jdk that would contain everything you need
[13:44] <conan> trygvis: which means we either have to hack maven, or switch to ant.
[13:44] <conan> trygvis: but we could not build with jdk1.5, thats the point.
[13:45] <bob> using jdk1.5 with source-level 1.4 still buggers groovy
[13:45] <trygvis> aha
[13:46] <bob> sure, blame groovy, ultimately
[13:46] <trygvis> or the jdk
[13:47] <conan> trygvis: but ultimately specifying not only compile src and target but also a jdk home would be a good thing - this keeps maven inline with how eclipse and intellij work too.


> Specify target jdk per project in multibuild
> --------------------------------------------
>
>          Key: MAVEN-1545
>          URL: http://jira.codehaus.org/browse/MAVEN-1545
>      Project: maven
>         Type: Improvement
>     Versions: 1.0.2
>     Reporter: Barry Kaplan

>
>
> We have a project (Drools) in which some modules require compilation with jdk5 and requires pre-jdk5. Both these modules cannot exists in the overall multi-project build.
> Maybe some type of property which indicates the JAVA_HOME to be used for a project can be added. I suppose this might mean forking off a new maven when the jdk changes from that of the top-level multi-build project.

--
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, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]