I would like to be able to specify a system path for any dependency regardless of the scope. For example, I would like to mark junit-3.8.1 as being in the "test" scope, yet point at a jar that is not in the repository. Something like this:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
<path>${cots.top}/junit/junit.jar</path>
</dependency>
I don't want to mark it as "system" scope, simply to say it is not in the repository because that would lose the fact that it is really something scoped for the unit test phase.
I understand the preferred way to use maven is to install 3rd-party artifacts in the repository (and the public ibiblio repository if possible), but the security culture in my company will not allow it (there is a rigid procedure for how 3rd-party jars and tools get downloaded, installed, and used - not uncommon in our particular industry). Without this feature I will be forced to mark all 3rd-party jars as "system" scoped, which I want to avoid. Regardless of my special circumstances, this feature would add a little more flexibility to maven for handling special cases.
So to summarize, I would like to be able to tag certain dependencies with a system path, but still tag them with an appropriate build scope such as"runtime", "test" or "provided". If tagged with a path, the dependency would not go to the repository to resolve the jar, but instead would follow the system path. Additionally, the path should be allowed to contain variables so I can make the build portable across operating systems (for example, by using a varaible to indicate the root directory of COTS software installations).
I would be happy to help out with the implementation, though I would need a few pointers of where to focus my attention.
Task
Open
Trivial
I would like to be able to specify a system path for any dependency regardless of the scope. For example, I would like to mark junit-3.8.1 as being in the "test" scope, yet point at a jar that is not in the repository. Something like this:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
<path>${cots.top}/junit/junit.jar</path>
</dependency>
I don't want to mark it as "system" scope, simply to say it is not in the repository because that would lose the fact that it is really something scoped for the unit test phase.
I understand the preferred way to use maven is to install 3rd-party artifacts in the repository (and the public ibiblio repository if possible), but the security culture in my company will not allow it (there is a rigid procedure for how 3rd-party jars and tools get downloaded, installed, and used - not uncommon in our particular industry). Without this feature I will be forced to mark all 3rd-party jars as "system" scoped, which I want to avoid. Regardless of my special circumstances, this feature would add a little more flexibility to maven for handling special cases.
So to summarize, I would like to be able to tag certain dependencies with a system path, but still tag them with an appropriate build scope such as"runtime", "test" or "provided". If tagged with a path, the dependency would not go to the repository to resolve the jar, but instead would follow the system path. Additionally, the path should be allowed to contain variables so I can make the build portable across operating systems (for example, by using a varaible to indicate the root directory of COTS software installations).
I would be happy to help out with the implementation, though I would need a few pointers of where to focus my attention.