You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eric Berry (JIRA)" <ji...@codehaus.org> on 2010/05/27 20:06:12 UTC

[jira] Created: (MSITE-481) Deploy site:deploy not working for maven 3 for DAV

Deploy site:deploy not working for maven 3 for DAV
--------------------------------------------------

                 Key: MSITE-481
                 URL: http://jira.codehaus.org/browse/MSITE-481
             Project: Maven 2.x Site Plugin
          Issue Type: Bug
          Components: site:deploy
    Affects Versions: 3.0-alpha-1
         Environment: Using 3.0.0-beta-1-SNAPSHOT of site plugin and maven 3.0.0-beta-1 (snapshot version from 5/3).
            Reporter: Eric Berry


Sorry if this is not where this goes.

I include this in my pom
		<extensions>
			<extension>
				<groupId>org.apache.maven.wagon</groupId>
				<artifactId>wagon-webdav-jackrabbit</artifactId>
				<version>1.0-beta-6</version>
			</extension>
		</extensions>
There seems to be a conflict between this extension and
 	<reporting>
		<plugins>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-project-info-reports-plugin</artifactId>
				<version>2.2</version>
I get an error saying that there are two versions of org.apache.commons.logging.LogFactory in the ClassLoader.


I fixed this problem by modifying the wagon-webdav-jackrabbit pom to exlcude commons-logging from its dependencies and specified a dependency on commons-logging-1.1.1.  So that is problem number 1.


At that point when I tried to deploy my site, I get this error:
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://vmswdev1/product-sites/config/SNAPSHOT/./css/maven-base.css. Return code is: 401

My site distribtion management setting is:
		<site>
			<id>sweng-projects</id>
			<url>dav+https://${webdavserver.hostname}/config/${product-sites.version}</url>
		</site>
My server setting in settings.xml is (actual values replaced with ***):
	<server>
		<id>sweng-projects</id>
		<username>****</username>
		<password>****</password>
	</server>
Problem number 2 is that site:deploy does not seem to using the username/password info from settings.xml.

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

        

[jira] Commented: (MSITE-481) Deploy site:deploy not working for maven 3 for DAV

Posted by "Eric Berry (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MSITE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222907#action_222907 ] 

Eric Berry commented on MSITE-481:
----------------------------------

Its caused by the FIXME on line 207 of SiteDeployMojo.  Uncommenting the FIXME and removing the following wagon.connect fixed my problem.  So whatever the reason for the original FIXME seems to be working in non-proxy mode.

> Deploy site:deploy not working for maven 3 for DAV
> --------------------------------------------------
>
>                 Key: MSITE-481
>                 URL: http://jira.codehaus.org/browse/MSITE-481
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0-alpha-1
>         Environment: Using 3.0.0-beta-1-SNAPSHOT of site plugin and maven 3.0.0-beta-1 (snapshot version from 5/3).
>            Reporter: Eric Berry
>
> Sorry if this is not where this goes.
> I include this in my pom
> 		<extensions>
> 			<extension>
> 				<groupId>org.apache.maven.wagon</groupId>
> 				<artifactId>wagon-webdav-jackrabbit</artifactId>
> 				<version>1.0-beta-6</version>
> 			</extension>
> 		</extensions>
> There seems to be a conflict between this extension and
>  	<reporting>
> 		<plugins>
> 			<plugin>
> 				<groupId>org.apache.maven.plugins</groupId>
> 				<artifactId>maven-project-info-reports-plugin</artifactId>
> 				<version>2.2</version>
> I get an error saying that there are two versions of org.apache.commons.logging.LogFactory in the ClassLoader.
> I fixed this problem by modifying the wagon-webdav-jackrabbit pom to exlcude commons-logging from its dependencies and specified a dependency on commons-logging-1.1.1.  So that is problem number 1.
> At that point when I tried to deploy my site, I get this error:
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://vmswdev1/product-sites/config/SNAPSHOT/./css/maven-base.css. Return code is: 401
> My site distribtion management setting is:
> 		<site>
> 			<id>sweng-projects</id>
> 			<url>dav+https://${webdavserver.hostname}/config/${product-sites.version}</url>
> 		</site>
> My server setting in settings.xml is (actual values replaced with ***):
> 	<server>
> 		<id>sweng-projects</id>
> 		<username>****</username>
> 		<password>****</password>
> 	</server>
> Problem number 2 is that site:deploy does not seem to using the username/password info from settings.xml.

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

        

[jira] Closed: (MSITE-481) Deploy site:deploy not working for maven 3 for DAV

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MSITE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MSITE-481.
------------------------------

    Resolution: Fixed

junits added

> Deploy site:deploy not working for maven 3 for DAV
> --------------------------------------------------
>
>                 Key: MSITE-481
>                 URL: http://jira.codehaus.org/browse/MSITE-481
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0-beta-1
>         Environment: Using 3.0.0-beta-1-SNAPSHOT of site plugin and maven 3.0.0-beta-1 (snapshot version from 5/3).
>            Reporter: Eric Berry
>            Assignee: Olivier Lamy
>            Priority: Critical
>             Fix For: 3.0-beta-2
>
>
> Sorry if this is not where this goes.
> I include this in my pom
> 		<extensions>
> 			<extension>
> 				<groupId>org.apache.maven.wagon</groupId>
> 				<artifactId>wagon-webdav-jackrabbit</artifactId>
> 				<version>1.0-beta-6</version>
> 			</extension>
> 		</extensions>
> There seems to be a conflict between this extension and
>  	<reporting>
> 		<plugins>
> 			<plugin>
> 				<groupId>org.apache.maven.plugins</groupId>
> 				<artifactId>maven-project-info-reports-plugin</artifactId>
> 				<version>2.2</version>
> I get an error saying that there are two versions of org.apache.commons.logging.LogFactory in the ClassLoader.
> I fixed this problem by modifying the wagon-webdav-jackrabbit pom to exlcude commons-logging from its dependencies and specified a dependency on commons-logging-1.1.1.  So that is problem number 1.
> At that point when I tried to deploy my site, I get this error:
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://vmswdev1/product-sites/config/SNAPSHOT/./css/maven-base.css. Return code is: 401
> My site distribtion management setting is:
> 		<site>
> 			<id>sweng-projects</id>
> 			<url>dav+https://${webdavserver.hostname}/config/${product-sites.version}</url>
> 		</site>
> My server setting in settings.xml is (actual values replaced with ***):
> 	<server>
> 		<id>sweng-projects</id>
> 		<username>****</username>
> 		<password>****</password>
> 	</server>
> Problem number 2 is that site:deploy does not seem to using the username/password info from settings.xml.

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

        

[jira] Commented: (MSITE-481) Deploy site:deploy not working for maven 3 for DAV

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MSITE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231636#action_231636 ] 

Olivier Lamy commented on MSITE-481:
------------------------------------

first patche committed in rev 984263. 
Tested with dav without proxy and with scp
If someone has time to test scpexe and dav with proxy ?

> Deploy site:deploy not working for maven 3 for DAV
> --------------------------------------------------
>
>                 Key: MSITE-481
>                 URL: http://jira.codehaus.org/browse/MSITE-481
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0-beta-1
>         Environment: Using 3.0.0-beta-1-SNAPSHOT of site plugin and maven 3.0.0-beta-1 (snapshot version from 5/3).
>            Reporter: Eric Berry
>            Assignee: Olivier Lamy
>            Priority: Critical
>             Fix For: 3.0-beta-2
>
>
> Sorry if this is not where this goes.
> I include this in my pom
> 		<extensions>
> 			<extension>
> 				<groupId>org.apache.maven.wagon</groupId>
> 				<artifactId>wagon-webdav-jackrabbit</artifactId>
> 				<version>1.0-beta-6</version>
> 			</extension>
> 		</extensions>
> There seems to be a conflict between this extension and
>  	<reporting>
> 		<plugins>
> 			<plugin>
> 				<groupId>org.apache.maven.plugins</groupId>
> 				<artifactId>maven-project-info-reports-plugin</artifactId>
> 				<version>2.2</version>
> I get an error saying that there are two versions of org.apache.commons.logging.LogFactory in the ClassLoader.
> I fixed this problem by modifying the wagon-webdav-jackrabbit pom to exlcude commons-logging from its dependencies and specified a dependency on commons-logging-1.1.1.  So that is problem number 1.
> At that point when I tried to deploy my site, I get this error:
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://vmswdev1/product-sites/config/SNAPSHOT/./css/maven-base.css. Return code is: 401
> My site distribtion management setting is:
> 		<site>
> 			<id>sweng-projects</id>
> 			<url>dav+https://${webdavserver.hostname}/config/${product-sites.version}</url>
> 		</site>
> My server setting in settings.xml is (actual values replaced with ***):
> 	<server>
> 		<id>sweng-projects</id>
> 		<username>****</username>
> 		<password>****</password>
> 	</server>
> Problem number 2 is that site:deploy does not seem to using the username/password info from settings.xml.

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

        

[jira] Commented: (MSITE-481) Deploy site:deploy not working for maven 3 for DAV

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MSITE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231635#action_231635 ] 

Olivier Lamy commented on MSITE-481:
------------------------------------

I don't follow you here ? you mean removing call of connect method ?
Could provide a patch with what works for you ?
Thanks

> Deploy site:deploy not working for maven 3 for DAV
> --------------------------------------------------
>
>                 Key: MSITE-481
>                 URL: http://jira.codehaus.org/browse/MSITE-481
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0-beta-1
>         Environment: Using 3.0.0-beta-1-SNAPSHOT of site plugin and maven 3.0.0-beta-1 (snapshot version from 5/3).
>            Reporter: Eric Berry
>            Assignee: Olivier Lamy
>            Priority: Critical
>             Fix For: 3.0-beta-2
>
>
> Sorry if this is not where this goes.
> I include this in my pom
> 		<extensions>
> 			<extension>
> 				<groupId>org.apache.maven.wagon</groupId>
> 				<artifactId>wagon-webdav-jackrabbit</artifactId>
> 				<version>1.0-beta-6</version>
> 			</extension>
> 		</extensions>
> There seems to be a conflict between this extension and
>  	<reporting>
> 		<plugins>
> 			<plugin>
> 				<groupId>org.apache.maven.plugins</groupId>
> 				<artifactId>maven-project-info-reports-plugin</artifactId>
> 				<version>2.2</version>
> I get an error saying that there are two versions of org.apache.commons.logging.LogFactory in the ClassLoader.
> I fixed this problem by modifying the wagon-webdav-jackrabbit pom to exlcude commons-logging from its dependencies and specified a dependency on commons-logging-1.1.1.  So that is problem number 1.
> At that point when I tried to deploy my site, I get this error:
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://vmswdev1/product-sites/config/SNAPSHOT/./css/maven-base.css. Return code is: 401
> My site distribtion management setting is:
> 		<site>
> 			<id>sweng-projects</id>
> 			<url>dav+https://${webdavserver.hostname}/config/${product-sites.version}</url>
> 		</site>
> My server setting in settings.xml is (actual values replaced with ***):
> 	<server>
> 		<id>sweng-projects</id>
> 		<username>****</username>
> 		<password>****</password>
> 	</server>
> Problem number 2 is that site:deploy does not seem to using the username/password info from settings.xml.

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

        

[jira] Commented: (MSITE-481) Deploy site:deploy not working for maven 3 for DAV

Posted by "Eric Berry (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MSITE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222902#action_222902 ] 

Eric Berry commented on MSITE-481:
----------------------------------

Problem 1 goes away if I make the weddav wagon a dependency of the site plugin instead of an extension.

> Deploy site:deploy not working for maven 3 for DAV
> --------------------------------------------------
>
>                 Key: MSITE-481
>                 URL: http://jira.codehaus.org/browse/MSITE-481
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0-alpha-1
>         Environment: Using 3.0.0-beta-1-SNAPSHOT of site plugin and maven 3.0.0-beta-1 (snapshot version from 5/3).
>            Reporter: Eric Berry
>
> Sorry if this is not where this goes.
> I include this in my pom
> 		<extensions>
> 			<extension>
> 				<groupId>org.apache.maven.wagon</groupId>
> 				<artifactId>wagon-webdav-jackrabbit</artifactId>
> 				<version>1.0-beta-6</version>
> 			</extension>
> 		</extensions>
> There seems to be a conflict between this extension and
>  	<reporting>
> 		<plugins>
> 			<plugin>
> 				<groupId>org.apache.maven.plugins</groupId>
> 				<artifactId>maven-project-info-reports-plugin</artifactId>
> 				<version>2.2</version>
> I get an error saying that there are two versions of org.apache.commons.logging.LogFactory in the ClassLoader.
> I fixed this problem by modifying the wagon-webdav-jackrabbit pom to exlcude commons-logging from its dependencies and specified a dependency on commons-logging-1.1.1.  So that is problem number 1.
> At that point when I tried to deploy my site, I get this error:
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://vmswdev1/product-sites/config/SNAPSHOT/./css/maven-base.css. Return code is: 401
> My site distribtion management setting is:
> 		<site>
> 			<id>sweng-projects</id>
> 			<url>dav+https://${webdavserver.hostname}/config/${product-sites.version}</url>
> 		</site>
> My server setting in settings.xml is (actual values replaced with ***):
> 	<server>
> 		<id>sweng-projects</id>
> 		<username>****</username>
> 		<password>****</password>
> 	</server>
> Problem number 2 is that site:deploy does not seem to using the username/password info from settings.xml.

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

        

[jira] Updated: (MSITE-481) Deploy site:deploy not working for maven 3 for DAV

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MSITE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MSITE-481:
-------------------------------

         Priority: Critical  (was: Major)
    Fix Version/s: 3.0-beta-2
         Assignee: Olivier Lamy

> Deploy site:deploy not working for maven 3 for DAV
> --------------------------------------------------
>
>                 Key: MSITE-481
>                 URL: http://jira.codehaus.org/browse/MSITE-481
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0-beta-1
>         Environment: Using 3.0.0-beta-1-SNAPSHOT of site plugin and maven 3.0.0-beta-1 (snapshot version from 5/3).
>            Reporter: Eric Berry
>            Assignee: Olivier Lamy
>            Priority: Critical
>             Fix For: 3.0-beta-2
>
>
> Sorry if this is not where this goes.
> I include this in my pom
> 		<extensions>
> 			<extension>
> 				<groupId>org.apache.maven.wagon</groupId>
> 				<artifactId>wagon-webdav-jackrabbit</artifactId>
> 				<version>1.0-beta-6</version>
> 			</extension>
> 		</extensions>
> There seems to be a conflict between this extension and
>  	<reporting>
> 		<plugins>
> 			<plugin>
> 				<groupId>org.apache.maven.plugins</groupId>
> 				<artifactId>maven-project-info-reports-plugin</artifactId>
> 				<version>2.2</version>
> I get an error saying that there are two versions of org.apache.commons.logging.LogFactory in the ClassLoader.
> I fixed this problem by modifying the wagon-webdav-jackrabbit pom to exlcude commons-logging from its dependencies and specified a dependency on commons-logging-1.1.1.  So that is problem number 1.
> At that point when I tried to deploy my site, I get this error:
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://vmswdev1/product-sites/config/SNAPSHOT/./css/maven-base.css. Return code is: 401
> My site distribtion management setting is:
> 		<site>
> 			<id>sweng-projects</id>
> 			<url>dav+https://${webdavserver.hostname}/config/${product-sites.version}</url>
> 		</site>
> My server setting in settings.xml is (actual values replaced with ***):
> 	<server>
> 		<id>sweng-projects</id>
> 		<username>****</username>
> 		<password>****</password>
> 	</server>
> Problem number 2 is that site:deploy does not seem to using the username/password info from settings.xml.

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