[jira] Resolved: (MEVENIDE-661) Adding test library always creates compile scope dependency

View: New views
1 Messages — Rating Filter:   Alert me  

[jira] Resolved: (MEVENIDE-661) Adding test library always creates compile scope dependency

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/MEVENIDE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint resolved MEVENIDE-661.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: NB_FUTURE

fixed. to appear in 7.0 m1
http://hg.netbeans.org/main/rev/6d8fe7a4594f

> Adding test library always creates compile scope dependency
> -----------------------------------------------------------
>
>                 Key: MEVENIDE-661
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-661
>             Project: mevenide
>          Issue Type: Improvement
>          Components: mevenide2-netbeans
>    Affects Versions: NB_3.1
>         Environment: netbeans 6.1
>            Reporter: Tyler Southwick
>            Assignee: Milos Kleint
>            Priority: Trivial
>             Fix For: NB_FUTURE
>
>
> When a new library is added by right clicking on the Test Libraries folder, it is added as a dependency to the compile scope and not the test scope.

--
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 from this list, please visit:

    http://xircles.codehaus.org/manage_email