You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/05/16 05:27:35 UTC
[jira] Closed: (MAVEN-806) Dependencies and build/test/run configurations : Addition of flexibility
[ http://jira.codehaus.org/browse/MAVEN-806?page=all ]
Brett Porter closed MAVEN-806:
------------------------------
Resolution: Won't Fix
we have compile/runtime/test in Maven 2.0. Won't be backported due to the amount of changes required to all plugins.
Per configuration dependencies will be supported by profiles, currently being designed and will be discussed on dev@maven.apache.org
> Dependencies and build/test/run configurations : Addition of flexibility
> ------------------------------------------------------------------------
>
> Key: MAVEN-806
> URL: http://jira.codehaus.org/browse/MAVEN-806
> Project: maven
> Type: New Feature
> Components: model additions
> Versions: 1.1
> Reporter: Andy Jefferson
>
>
> I would like to have the ability to have different test and runtime configurations within Maven. Currently there are limitations with how Maven's test process works.
> a). Dependencies for testing have to be put in the overall dependencies section.
> b). There is no separation of the different types of dependencies.
> How about a revision to the POM as follows ...
> <build>
> <sourceDirectory>...</sourceDirectory>
> <dependencies>
> ...
> </dependencies>
> <configurations>
> <configuration name="Windows">
> <dependencies>
> ...
> </dependencies>
> </configuration>
> </configurations>
> </build>
> <test>
> <sourceDirectory>...</sourceDirectory>
> <dependencies>
> ...
> </dependencies>
> <configurations>
> <configuration name="MySQL">
> <dependencies>
> ....
> </dependencies>
> </configuration>
> </configurations>
> </test>
> <run>
> <dependencies>
> ...
> </dependencies>
> <configurations>
> <configuration name="Linux">
> <dependencies>
> ....
> </dependencies>
> </configuration>
> </configurations>
> </run>
> This provides the separation of the different types of dependencies. It provides for
> * platform specific builds
> * different test configurations (e.g with different DB's).
> * different runtime dependencies dependent on the deployment environment
> * ability to specify dependencies for all build configurations, and to add ones specific to particular configs.
> * ability to specify dependencies for all test configurations, and to add ones particular to particular configs.
> The above is intended as a talking point and as provocation :-) to getting Maven up to a point where it can cope with the various situations found in typical projects.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org