[jira] (MCOMPILER-165) Child modules don't seem to be able to use a different compilerId to their parent modules when built from the parent POM.

[ https://jira.codehaus.org/browse/MCOMPILER-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301606#comment-301606 ] Edd grant commented on MCOMPILER-165: - What exactly do you mean by a 'different maven-compil

[jira] (MCOMPILER-165) Child modules don't seem to be able to use a different compilerId to their parent modules when built from the parent POM.

[ https://jira.codehaus.org/browse/MCOMPILER-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292002#comment-292002 ] Edd grant commented on MCOMPILER-165: - I have checked out the code and will investigate myse

[jira] (MCOMPILER-165) Child modules don't seem to be able to use a different compilerId to their parent modules when built from the parent POM.

[ https://jira.codehaus.org/browse/MCOMPILER-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edd grant updated MCOMPILER-165: Attachment: multiple-pom-mixed-java-groovy-project-test.zip Attached project which demonstrates the i

[jira] (MCOMPILER-165) Child modules don't seem to be able to use a different compilerId to their parent modules when built from the parent POM.

[ https://jira.codehaus.org/browse/MCOMPILER-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291640#comment-291640 ] Edd grant commented on MCOMPILER-165: - Have just done some testing and have discovered that

[jira] (MCOMPILER-165) Child modules don't seem to be able to use a different compilerId to their parent modules when built from the parent POM.

Edd grant created MCOMPILER-165: --- Summary: Child modules don't seem to be able to use a different compilerId to their parent modules when built from the parent POM. Key: MCOMPILER-165 URL: https://jira.codehaus.org/