[jira] Commented: (MCOMPILER-128) "Extra" Compiler mojo for non-test, non-main code

["Brett Porter (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MCOMPILER-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222086#action_222086 ] 

Brett Porter commented on MCOMPILER-128:
----------------------------------------

sounds a bit odd to me, would be worth some discussion.

What is the more concrete use case?

Why doesn't an additional execution of the current compiler mojo suit?

> "Extra" Compiler mojo for non-test, non-main code
> -------------------------------------------------
>
>                 Key: MCOMPILER-128
>                 URL: http://jira.codehaus.org/browse/MCOMPILER-128
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.3.1
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.4
>
>
> It'd be nice to be able to specify another compile step in the build process, pointed at different source code and compiling to some alternative location. Using this approach, one could easily segregate test-fixture code that depends on the current module from the unit tests for that module, then use something like the assembly plugin to jar up the compiled test fixtures for distribution.
> Obviously, once this "extra" compile step was completed, the resulting location would have to be added to the appropriate classpath for test compilation, etc. This could be handled using a system dependency (ick) or something like a test-resource with filtering turned off (much the way image resources are handled), which would make it available on the classpath.

-- 
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