[jetty-dev] [jira] (JETTY-1498) Add ability to put <scope>provided</scope> artifacts on system classpath for jetty-jspc-maven-plugin

     [ https://jira.codehaus.org/browse/JETTY-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Bartel resolved JETTY-1498.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 8.1.3
                   7.6.3

Fixed for 7.6.3/8.1.3
                
> Add ability to put <scope>provided</scope> artifacts on system classpath for jetty-jspc-maven-plugin
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JETTY-1498
>                 URL: https://jira.codehaus.org/browse/JETTY-1498
>             Project: Jetty
>          Issue Type: Improvement
>          Components: Maven
>    Affects Versions: 7.6.2
>            Reporter: Jan Bartel
>            Assignee: Jan Bartel
>             Fix For: 7.6.3, 8.1.3
>
>
> The jetty-maven-plugin has a <useProvidedScope> configuration option which will put all dependencies with <scope>provided</scope> onto the execution classpath.
> Although this can be a dangerous option to use, as you can wind up with duplicate classes on the classpath (2 different artifacts containing the same classes, one on the plugin classpath and one on the project classpath for example), it may be a useful option to have also in the jspc plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.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