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 2006/02/14 06:54:47 UTC
[jira] Closed: (MNG-2070) systemPath is needed for tests as well as
compile time scope
[ http://jira.codehaus.org/browse/MNG-2070?page=all ]
Brett Porter closed MNG-2070:
-----------------------------
Assign To: Brett Porter
Resolution: Duplicate
> systemPath is needed for tests as well as compile time scope
> ------------------------------------------------------------
>
> Key: MNG-2070
> URL: http://jira.codehaus.org/browse/MNG-2070
> Project: Maven 2
> Type: Improvement
> Components: Dependencies
> Environment: n/a
> Reporter: Lars Rosenberg Nielsen
> Assignee: Brett Porter
>
>
> I think you should be able to specify a systemPath for your dependencies for test as well as compile time (system scope). Why? Well WebLogic for example, Bea has designed their weblogic.jar so you cannot move it out of WL_HOME/server/lib/ This means I cannot e.g. create a plugin that can do WebLogic server management before my integration tests are launched because I can only for compile time specify a dependency to c:/bea/weblogic81/server/lib/weblogic.jar or whereever I have installed my WebLogic server. I do not want to manage my WebLogic server at compile time.
> Lars
--
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