You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2003/09/10 11:49:10 UTC

[jira] Created: (MAVEN-806) Dependencies and build/test/run configurations : Addition of flexibility

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=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

 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             core
   Versions:
             1.1

   Assignee: 
   Reporter: Andy Jefferson

    Created: Wed, 10 Sep 2003 4:48 AM
    Updated: Wed, 10 Sep 2003 4:48 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org