[jira] Created: (MOJO-1450) Sonar mojo: remove the scope "provided" of all Maven dependencies
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
[jira] Created: (MOJO-1450) Sonar mojo: remove the scope "provided" of all Maven dependencies
by JIRA jira@codehaus.org
::
Rate this Message:
Sonar mojo: remove the scope "provided" of all Maven dependencies
----------------------------------------------------------------- Key: MOJO-1450 URL: http://jira.codehaus.org/browse/MOJO-1450 Project: Mojo Issue Type: Bug Reporter: Simon Brandhof Dependencies on Maven artifacts are set with the scope 'provided'. It raises some errors with Maven 2.2. See [this discussion for more details|http://markmail.org/thread/c6jezn72f4d5icol]. -- 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 |
|
|
[jira] Assigned: (MOJO-1450) Sonar mojo: remove the scope "provided" of all Maven dependencies
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MOJO-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Brandhof reassigned MOJO-1450: ------------------------------------ Assignee: Simon Brandhof > Sonar mojo: remove the scope "provided" of all Maven dependencies > ----------------------------------------------------------------- > > Key: MOJO-1450 > URL: http://jira.codehaus.org/browse/MOJO-1450 > Project: Mojo > Issue Type: Bug > Reporter: Simon Brandhof > Assignee: Simon Brandhof > > Dependencies on Maven artifacts are set with the scope 'provided'. It raises some errors with Maven 2.2. See [this discussion for more details|http://markmail.org/thread/c6jezn72f4d5icol]. -- 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 |
|
|
[jira] Issue Comment Edited: (MOJO-1450) Sonar mojo: remove the scope "provided" of all Maven dependencies
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MOJO-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197323#action_197323 ] Benjamin Bentmann edited comment on MOJO-1450 at 11/5/09 4:23 AM: ------------------------------------------------------------------ Note: Whether you declare the dependency on maven-model with provided scope or not, the JAR will not be part of the plugin class loader. Instead, the model classes are supposed to be provided via delegation to the parent class loader, i.e. the Maven core class loader. So this looks more like some class loader problem than a dependency problem. was (Author: bentmann): Note: Whether you declare the dependency on maven-model with provided scope or not, the JAR will not be part of the plugin class loader. Instead, the model classes are supposed to be provided via delegation to the parent class loader, i.e. the Maven core class loader. So this looks more like some class loader problem that a dependency problem. > Sonar mojo: remove the scope "provided" of all Maven dependencies > ----------------------------------------------------------------- > > Key: MOJO-1450 > URL: http://jira.codehaus.org/browse/MOJO-1450 > Project: Mojo > Issue Type: Bug > Reporter: Simon Brandhof > Assignee: Simon Brandhof > > Dependencies on Maven artifacts are set with the scope 'provided'. It raises some errors with Maven 2.2. See [this discussion for more details|http://markmail.org/thread/c6jezn72f4d5icol]. -- 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 |
|
|
[jira] Commented: (MOJO-1450) Sonar mojo: remove the scope "provided" of all Maven dependencies
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MOJO-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197323#action_197323 ] Benjamin Bentmann commented on MOJO-1450: ----------------------------------------- Note: Whether you declare the dependency on maven-model with provided scope or not, the JAR will not be part of the plugin class loader. Instead, the model classes are supposed to be provided via delegation to the parent class loader, i.e. the Maven core class loader. So this looks more like some class loader problem that a dependency problem. > Sonar mojo: remove the scope "provided" of all Maven dependencies > ----------------------------------------------------------------- > > Key: MOJO-1450 > URL: http://jira.codehaus.org/browse/MOJO-1450 > Project: Mojo > Issue Type: Bug > Reporter: Simon Brandhof > Assignee: Simon Brandhof > > Dependencies on Maven artifacts are set with the scope 'provided'. It raises some errors with Maven 2.2. See [this discussion for more details|http://markmail.org/thread/c6jezn72f4d5icol]. -- 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 |
|
|
[jira] Commented: (MOJO-1450) Sonar mojo: remove the scope "provided" of all Maven dependencies
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MOJO-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197328#action_197328 ] Simon Brandhof commented on MOJO-1450: -------------------------------------- Thanks Benjamin for the notification. I'm going to search for another clue. > Sonar mojo: remove the scope "provided" of all Maven dependencies > ----------------------------------------------------------------- > > Key: MOJO-1450 > URL: http://jira.codehaus.org/browse/MOJO-1450 > Project: Mojo > Issue Type: Bug > Reporter: Simon Brandhof > Assignee: Simon Brandhof > > Dependencies on Maven artifacts are set with the scope 'provided'. It raises some errors with Maven 2.2. See [this discussion for more details|http://markmail.org/thread/c6jezn72f4d5icol]. -- 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 |
| Free embeddable forum powered by Nabble | Forum Help |
