The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Tue, 22 Feb 2005 1:13 AM
Changes:
environment changed to
Component changed to model additions
Component changed from core
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-806?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-806
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-806
Summary: Dependencies and build/test/run configurations : Addition of
flexibility
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
model additions
Versions:
1.1
Assignee:
Reporter: Andy Jefferson
Created: Wed, 10 Sep 2003 4:48 AM
Updated: Tue, 22 Feb 2005 1:13 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
