[
http://jira.codehaus.org/browse/MAVENUPLOAD-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94263
]
Tim Ducheyne commented on MAVENUPLOAD-1497:
-------------------------------------------
Let me explain what I'm trying to do.
Our library has need for different configurations depending on the project
envrionment that is going to use it. For example, there are 3 different unit
testing frameworks supported: JUnit3, JUnit4 and TestNG. The project that is
going to use Unitils needs to decide which one it wants to use. If it uses
JUnit3 as test library, it does not want to retrieve the JUnit4 and TestNG
libraries.
That's why I set all such dependencies to provided and optional:
Provided, so that the projects need to include the dependencies themselves. In
the example, the project will need to explicitly add JUnit 3 as dependency.
Optional, to indicate that the libraries are not strictly required for Unitils
to function. For example, if JUnit3 is used, JUnit4 and TestNG are not required.
As you requested, I moved all provided libs to the compile scope and made them
optional again. The downside is that projects will now explicitly have to
exclude all libraries that are not in their environment (a large exclude list).
Any suggestions on how to avoid this (without using the provided scope)?
I've uploaded it in a new bundle jar, the url remains the same.
Thanks for installing the new bundle.
Tim
> Upload Unitils 1.0 rc 2
> -----------------------
>
> Key: MAVENUPLOAD-1497
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1497
> Project: maven-upload-requests
> Issue Type: Task
> Reporter: Tim Ducheyne
>
--
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
