maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MCOMPILER-128) "Extra" Compiler mojo for non-test, non-main code
Date Sun, 06 Sep 2015 20:18:46 GMT

     [ https://issues.apache.org/jira/browse/MCOMPILER-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov updated MCOMPILER-128:
-------------------------------------
    Fix Version/s:     (was: backlog)

> "Extra" Compiler mojo for non-test, non-main code
> -------------------------------------------------
>
>                 Key: MCOMPILER-128
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-128
>             Project: Maven Compiler Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.3.1
>            Reporter: John Casey
>            Assignee: John Casey
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message