You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@codehaus.org> on 2012/02/01 08:53:02 UTC

[jira] (MSITE-629) Adding additional wagon provider as dependency does not work

Anders Hammar created MSITE-629:
-----------------------------------

             Summary: Adding additional wagon provider as dependency does not work
                 Key: MSITE-629
                 URL: https://jira.codehaus.org/browse/MSITE-629
             Project: Maven 2.x and 3.x Site Plugin
          Issue Type: Bug
          Components: site:deploy
    Affects Versions: 3.0
         Environment: Mac OS 10.7.2, Apple Java 1.6.0_29, Maven 3.0.3/3.0.4
Windows XP, SUN Java 1.6.0_24, Maven 3.0.4
            Reporter: Anders Hammar
         Attachments: console.txt, mvnsite-dav-dep-bug.zip

According to http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html is should be possible to add additional wagon provider as a dependency to the site plugin. For a project deploying via dav, doing so using the wagon-webdav-jackrabbit makes Maven through a NoClassDefFoundError. Of adding the wagon as a global extension it works.
Not sure if this is a maven-site-plugin issue though, or possible something in the specific wagon.

I'm attaching a test project as well as the console output showing the error.

--
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

        

[jira] (WAGON-370) Adding additional wagon provider as dependency does not work

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/WAGON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg moved MSITE-629 to WAGON-370:
---------------------------------------------

          Component/s:     (was: site:deploy)
                       wagon-webdav
    Affects Version/s:     (was: 3.0)
                       2.2
                  Key: WAGON-370  (was: MSITE-629)
              Project: Maven Wagon  (was: Maven 2.x and 3.x Site Plugin)
    
> Adding additional wagon provider as dependency does not work
> ------------------------------------------------------------
>
>                 Key: WAGON-370
>                 URL: https://jira.codehaus.org/browse/WAGON-370
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-webdav
>    Affects Versions: 2.2
>         Environment: Mac OS 10.7.2, Apple Java 1.6.0_29, Maven 3.0.3/3.0.4
> Windows XP, SUN Java 1.6.0_24, Maven 3.0.4
>            Reporter: Anders Hammar
>         Attachments: console.txt, mvnsite-dav-dep-bug.zip
>
>
> According to http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html is should be possible to add additional wagon provider as a dependency to the site plugin. For a project deploying via dav, doing so using the wagon-webdav-jackrabbit makes Maven through a NoClassDefFoundError. Of adding the wagon as a global extension it works.
> Not sure if this is a maven-site-plugin issue though, or possible something in the specific wagon.
> I'm attaching a test project as well as the console output showing the error.

--
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

        

[jira] (MSITE-629) Adding additional wagon provider as dependency does not work

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MSITE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290740#comment-290740 ] 

Dennis Lundberg commented on MSITE-629:
---------------------------------------

I think wagon needs to have some dependency on slf4j. When I looked at svn history for the POM there was a commit that removed such a dependency. I'll go and add that back. Until then you can use the above as a temporary workaround.
                
> Adding additional wagon provider as dependency does not work
> ------------------------------------------------------------
>
>                 Key: MSITE-629
>                 URL: https://jira.codehaus.org/browse/MSITE-629
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0
>         Environment: Mac OS 10.7.2, Apple Java 1.6.0_29, Maven 3.0.3/3.0.4
> Windows XP, SUN Java 1.6.0_24, Maven 3.0.4
>            Reporter: Anders Hammar
>         Attachments: console.txt, mvnsite-dav-dep-bug.zip
>
>
> According to http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html is should be possible to add additional wagon provider as a dependency to the site plugin. For a project deploying via dav, doing so using the wagon-webdav-jackrabbit makes Maven through a NoClassDefFoundError. Of adding the wagon as a global extension it works.
> Not sure if this is a maven-site-plugin issue though, or possible something in the specific wagon.
> I'm attaching a test project as well as the console output showing the error.

--
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

        

[jira] (MSITE-629) Adding additional wagon provider as dependency does not work

Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MSITE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290693#comment-290693 ] 

Anders Hammar commented on MSITE-629:
-------------------------------------

Yes, that works!
I was thinking of that solution, but at the time of writing this ticket I didn't think that I should be forced to add it manually. But now I'm not that sure any more. What I don't really understand is why it works without this extra dep when the wagon is added as a global extension. There has to be a slf4j impl somewhere on the classpath. Why isn't it available when the wagon is added as a dep to the m-site-p?
                
> Adding additional wagon provider as dependency does not work
> ------------------------------------------------------------
>
>                 Key: MSITE-629
>                 URL: https://jira.codehaus.org/browse/MSITE-629
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0
>         Environment: Mac OS 10.7.2, Apple Java 1.6.0_29, Maven 3.0.3/3.0.4
> Windows XP, SUN Java 1.6.0_24, Maven 3.0.4
>            Reporter: Anders Hammar
>         Attachments: console.txt, mvnsite-dav-dep-bug.zip
>
>
> According to http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html is should be possible to add additional wagon provider as a dependency to the site plugin. For a project deploying via dav, doing so using the wagon-webdav-jackrabbit makes Maven through a NoClassDefFoundError. Of adding the wagon as a global extension it works.
> Not sure if this is a maven-site-plugin issue though, or possible something in the specific wagon.
> I'm attaching a test project as well as the console output showing the error.

--
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

        

[jira] (WAGON-370) Adding additional wagon provider as dependency does not work

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/WAGON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg closed WAGON-370.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3

The upgraded version of slf4j-api being used in 2.3-SNAPSHOT is more stable if no slf4j implementation is provided. It gracefully falls back to NOOP logger which is exactly what we wanted.
                
> Adding additional wagon provider as dependency does not work
> ------------------------------------------------------------
>
>                 Key: WAGON-370
>                 URL: https://jira.codehaus.org/browse/WAGON-370
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-webdav
>    Affects Versions: 2.2
>         Environment: Mac OS 10.7.2, Apple Java 1.6.0_29, Maven 3.0.3/3.0.4
> Windows XP, SUN Java 1.6.0_24, Maven 3.0.4
>            Reporter: Anders Hammar
>             Fix For: 2.3
>
>         Attachments: console.txt, mvnsite-dav-dep-bug.zip
>
>
> According to http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html is should be possible to add additional wagon provider as a dependency to the site plugin. For a project deploying via dav, doing so using the wagon-webdav-jackrabbit makes Maven through a NoClassDefFoundError. Of adding the wagon as a global extension it works.
> Not sure if this is a maven-site-plugin issue though, or possible something in the specific wagon.
> I'm attaching a test project as well as the console output showing the error.

--
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

        

[jira] (MSITE-629) Adding additional wagon provider as dependency does not work

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MSITE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290524#comment-290524 ] 

Dennis Lundberg commented on MSITE-629:
---------------------------------------

I've tried this locally and was able to get past your error message, but ended up with another error due to the fact that I don't have a local Nexus installation. Can you try it and see if it works for you?

Add the following as an extra dependency to maven-site-plugin:
{code}
            <dependency>
              <groupId>org.slf4j</groupId>
              <artifactId>slf4j-nop</artifactId>
              <version>1.5.3</version>
              <scope>runtime</scope>
            </dependency>
{code}

                
> Adding additional wagon provider as dependency does not work
> ------------------------------------------------------------
>
>                 Key: MSITE-629
>                 URL: https://jira.codehaus.org/browse/MSITE-629
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0
>         Environment: Mac OS 10.7.2, Apple Java 1.6.0_29, Maven 3.0.3/3.0.4
> Windows XP, SUN Java 1.6.0_24, Maven 3.0.4
>            Reporter: Anders Hammar
>         Attachments: console.txt, mvnsite-dav-dep-bug.zip
>
>
> According to http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html is should be possible to add additional wagon provider as a dependency to the site plugin. For a project deploying via dav, doing so using the wagon-webdav-jackrabbit makes Maven through a NoClassDefFoundError. Of adding the wagon as a global extension it works.
> Not sure if this is a maven-site-plugin issue though, or possible something in the specific wagon.
> I'm attaching a test project as well as the console output showing the error.

--
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

        

[jira] (MSITE-629) Adding additional wagon provider as dependency does not work

Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MSITE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290697#comment-290697 ] 

Anders Hammar commented on MSITE-629:
-------------------------------------

I see that it's one of the dependencies of the wagon (jackrabbit-webdav) that uses slf4j. Shouldn't the wagon then include this runtime dependency?
                
> Adding additional wagon provider as dependency does not work
> ------------------------------------------------------------
>
>                 Key: MSITE-629
>                 URL: https://jira.codehaus.org/browse/MSITE-629
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0
>         Environment: Mac OS 10.7.2, Apple Java 1.6.0_29, Maven 3.0.3/3.0.4
> Windows XP, SUN Java 1.6.0_24, Maven 3.0.4
>            Reporter: Anders Hammar
>         Attachments: console.txt, mvnsite-dav-dep-bug.zip
>
>
> According to http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html is should be possible to add additional wagon provider as a dependency to the site plugin. For a project deploying via dav, doing so using the wagon-webdav-jackrabbit makes Maven through a NoClassDefFoundError. Of adding the wagon as a global extension it works.
> Not sure if this is a maven-site-plugin issue though, or possible something in the specific wagon.
> I'm attaching a test project as well as the console output showing the error.

--
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