Re: unable to deploy site with webdav

2009-05-06 Thread rossputin

Hi Michael,

I switched to use scp and all is good :-)

Sorry I can not help you with the webdav thing,

 - Ross


Michael K. wrote:
 
 Hello Ross,
 
 I have the same problem as you had. Did you get resolve the problem?
 I would appreciate your help.
 
 Kind regards,
 
 Michael 
 
 
 rossputin wrote:
 
 Hi,
 
 I am using maven 2.0.9, and everything is working great except for site
 deployment with webdav.  I have not tried any other kind of deployment
 yet, as I do it manually, so it may not be just site deployment that is
 not working for me.  I have an apache webdav setup in place, and can
 access it in a browser or in Cadaver via command line.  When I execute my
 maven site:deploy command, I always get a '500 Internal Server Error'
 with wagon-webdav 1.0-beta-2, and with wagon-webdav 1.0-beta-1 nothing
 much seems to happen, the process executes successfully, but nothing is
 copied across.
 
 Has anyone successfully deployed with any recent version of maven over
 webdav?  One of the books I have on it suggests using it.  I have not
 seen much on the mailing list though.
 
 Thanks in advance for your help.
 
 Ross
 
 
 

-- 
View this message in context: 
http://www.nabble.com/unable-to-deploy-site-with-webdav-tp17276670p23406609.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: plugins now require me to provide a version ?

2009-01-06 Thread rossputin

Hi,

I don't recall changing anything in the local Maven repository...

things are building now that I have provided versions, but I was under the
impression that if I did not provide versions, the latest would be used ?

Regards,

Ross



jeffma...@jeffmaury.com wrote:
 
 Did you change something in your local Maven repository ?
 
 Regards
 Jeff MAURY
 
 On Tue, Jan 6, 2009 at 12:10 PM, rossputin rossaj...@yahoo.co.uk wrote:
 

 Hi guys,

 wondering if someone can enlighten me a little.  Since I came back from
 the
 Christmas holidays, all of a sudden various plugins are working
 differently
 in my pom.

 - maven-eclipse-plugin now needs me to provide a version or the project
 will
 not build
 - maven-changes-plugin now needs me to provide a version of the project
 will
 not build
 - maven-javadoc-plugin now needs me to provide a version etc etc
 - maven-jxr-plugin needs a version
 - surefire needs a version

 Can someone explain why the behaviour has changed.. was I remiss in not
 providing the version before, or did I miss out on an important
 announcement
 explaining that I suddenly need to provide version information ?  Perhaps
 I
 have done something to my pom which has upset the balance ?

 Additionally, now I have provided the version information, I am getting a
 complaint that the 'maven-default-skin' does not exist, I have not
 updated
 my site docs in anyway.

 Thanks in advance for your help,

 regards,

 Ross

 --
 View this message in context:
 http://www.nabble.com/plugins-now-require-me-to-provide-a-version---tp21308561p21308561.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


 
 
 -- 
 La mélancolie c'est communiste
 Tout le monde y a droit de temps en temps
 La mélancolie n'est pas capitaliste
 C'est même gratuit pour les perdants
 La mélancolie c'est pacifiste
 On ne lui rentre jamais dedans
 La mélancolie oh tu sais ça existe
 Elle se prend même avec des gants
 La mélancolie c'est pour les syndicalistes
 Il faut juste sa carte de permanent
 
 Miossec (2006)
 
 http://www.jeffmaury.com
 http://riadiscuss.jeffmaury.com
 http://www.lastfm.fr/listen/user/jeffmaury/personal
 Mes CDs à récupérer:
 http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTAhl=en
 
 

-- 
View this message in context: 
http://www.nabble.com/plugins-now-require-me-to-provide-a-version---tp21308561p21308838.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: plugins now require me to provide a version ?

2009-01-06 Thread rossputin

Aha, just found the cause of this.. in my case, someone clobbered my
Artifactory instance yesterday... sorry my fault for not thinking of
checking on it before, thanks for your help anyway.

Regards,

Ross



Baptiste MATHUS-4 wrote:
 
 2009/1/6 rossputin rossaj...@yahoo.co.uk
 

 Can someone explain why the behaviour has changed.. was I remiss in not
 providing the version before, or did I miss out on an important
 announcement
 
 
 In short, yes :-). Though it's a quite common mistake, it's good practice
 to
 always specify the versions of the plugin you're using. In fact, if you
 don't, by default maven will look  for the latest available version and it
 might break your build if the default configuration changed.
 

 explaining that I suddenly need to provide version information ?  Perhaps
 I
 have done something to my pom which has upset the balance ?

 Additionally, now I have provided the version information, I am getting a
 complaint that the 'maven-default-skin' does not exist, I have not
 updated
 
 
 I remember going into such kind of problem, but unfortunately I don't
 remember what it was.
 
 Cheers.
 -- 
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !
 
 

-- 
View this message in context: 
http://www.nabble.com/plugins-now-require-me-to-provide-a-version---tp21308561p21314979.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: unable to deploy site with webdav

2008-05-19 Thread rossputin

Hi,

I have since successfully deployed the site with scp, so the problem is
definitely with webdav, or my configuration of it.

My parent pom.xml contains a 'distributionManagement' element as below:

distributionManagement
site
idourproject.website/id
urldav:http://our.webserver.com/projects/ourproject/url
/site
/distributionManagement

My settings.xml has an entry as below:

server
idourproject.website/id
usernameouruser/username
passwordourpassword/password
/server

I tried also adding to my build element:

extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-webdav/artifactId
version1.0-beta-2/version
/extension
/extensions

I also tried changing the version of wagon-webdav to 1.0-beta-1.

Thanks for your help,

regards,

Ross

rossputin wrote:
 
 Hi,
 
 I am using maven 2.0.9, and everything is working great except for site
 deployment with webdav.  I have not tried any other kind of deployment
 yet, as I do it manually, so it may not be just site deployment that is
 not working for me.  I have an apache webdav setup in place, and can
 access it in a browser or in Cadaver via command line.  When I execute my
 maven site:deploy command, I always get a '500 Internal Server Error' with
 wagon-webdav 1.0-beta-2, and with wagon-webdav 1.0-beta-1 nothing much
 seems to happen, the process executes successfully, but nothing is copied
 across.
 
 Has anyone successfully deployed with any recent version of maven over
 webdav?  One of the books I have on it suggests using it.  I have not seen
 much on the mailing list though.
 
 Thanks in advance for your help.
 
 Ross
 
-- 
View this message in context: 
http://www.nabble.com/unable-to-deploy-site-with-webdav-tp17276670p17316639.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



unable to deploy site with webdav

2008-05-16 Thread rossputin

Hi,

I am using maven 2.0.9, and everything is working great except for site
deployment with webdav.  I have not tried any other kind of deployment yet,
as I do it manually, so it may not be just site deployment that is not
working for me.  I have an apache webdav setup in place, and can access it
in a browser or in Cadaver via command line.  When I execute my maven
site:deploy command, I always get a '500 Internal Server Error' with
wagon-webdav 1.0-beta-2, and with wagon-webdav 1.0-beta-1 nothing much seems
to happen, the process executes successfully, but nothing is copied across.

Has anyone successfully deployed with any recent version of maven over
webdav?  One of the books I have on it suggests using it.  I have not seen
much on the mailing list though.

Thanks in advance for your help.

Ross
-- 
View this message in context: 
http://www.nabble.com/unable-to-deploy-site-with-webdav-tp17276670p17276670.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]