Re: site-deploy using wagon-ssh: User input needed
Hi Gerrit, I see in the Jenkins Build log that wagon-ssh keeps asking if it should trust the connection by showing the SSH RSA fingerprint. Maybe your Jenkins's %USER_HOME% is simply not set as you expect? Apparently [2], Jenkins on Windows defaults to C:\Users\[MY_USER]\.jenkins, so maybe you need to put your known_hosts in C:\Users\[MY_USER]\.jenkins\.ssh\known_hosts in order for it to run properly with Jenkins? The easiest way would be if I would be able to specify the path of the known_hosts file in the settings.xml. Looking at the relevant maven-wagon source [1], it is clear there is a bunch of logic for managing a KnownHostsProvider (which controls where the known_hosts data comes from). So I would be very surprised if this was not exposed at the Maven level -- i.e., if there was not a way to configure this in the POM somehow. Unfortunately wagon-ssh also doesn't show at which location it tries to open the known_hosts file. Did you try with mvn -X? That is verbose/debug mode. If it still doesn't echo the path, please file a JIRA issue for it: https://jira.codehaus.org/browse/WAGON (create account at https://xircles.codehaus.org/signup) Does no one of you use that wagon-ssh? My group uses wagon-webdav-jackrabbit for artifact deploys, and we aren't deploying our Maven sites properly yet. Regards, Curtis [1] https://github.com/apache/maven-wagon/blob/41336732524e33fa3fdc99f07b6add013b23dfa7/wagon-providers/wagon-ssh/src/main/java/org/apache/maven/wagon/providers/ssh/jsch/AbstractJschWagon.java#L89 [2] http://stackoverflow.com/q/12689139 On Tue, Jun 24, 2014 at 6:42 AM, Hohl, Gerrit g.h...@aurenz.de wrote: Hello everyone, I still having this problem. Does no one of you use that wagon-ssh? Don't you upload the Maven report on a web server? Or do you use simply other methods? If there is a better method I would be happy to know that. :) Regards, Gerrit -Ursprüngliche Nachricht- Von: Hohl, Gerrit [mailto:g.h...@aurenz.de] Gesendet: Donnerstag, 12. Juni 2014 17:40 An: Maven Users List Betreff: AW: site-deploy using wagon-ssh: User input needed Hello everyone, :) okay, I tried a different approach: Instead of that configuration section in the settings.xml I copied my local know_hosts file from C:\Users\[MY_USER]\.ssh\known_hosts to the server: C:\Windows\system32\config\.ssh\known_hosts I read in the Internet that this folder is the folder of the system account which is used e.g. by Tomcat. And as Jenkins and Maven are executed by Tomcat, they should work on the same folder. Unfortunately I didn't work: I see in the Jenkins Build log that wagon-ssh keeps asking if it should trust the connection by showing the SSH RSA fingerprint. Unfortunately wagon-ssh also doesn't show at which location it tries to open the known_hosts file. The easiest way would be if I would be able to specify the path of the known_hosts file in the settings.xml. But I haven't found anything about a configuration parameter like that. Regards, Gerrit - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy using wagon-ssh: User input needed
That's the Jenkins home directory not the user home direcory of the user account that jenkins is running as On 24 June 2014 15:18, Hohl, Gerrit g.h...@aurenz.de wrote: Hello Curtis, thanks for your reply. The Jenkins configuration says that C:\.jenkins is the home directory. So I created a .ssh folder there and places the know_hosts in it. But it didn't work. I also started the build enabling the verbose output, like you wrote. That is really very verbose. Also the build process stopped very early, I got a 7 GB log file. ;) Unfortunately I don't see any path there. Only that the uses the proper ID of the server and also uses the credentials which have been configured for it. That's all. I go for your suggestion about creating an account at codehaus. I will create a bug ticket there. Thanks again for your mail. :) Regards, Gerrit -Ursprüngliche Nachricht- Von: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] Im Auftrag von Curtis Rueden Gesendet: Dienstag, 24. Juni 2014 14:36 An: Maven Users List Betreff: Re: site-deploy using wagon-ssh: User input needed Hi Gerrit, I see in the Jenkins Build log that wagon-ssh keeps asking if it should trust the connection by showing the SSH RSA fingerprint. Maybe your Jenkins's %USER_HOME% is simply not set as you expect? Apparently [2], Jenkins on Windows defaults to C:\Users\[MY_USER]\.jenkins, so maybe you need to put your known_hosts in C:\Users\[MY_USER]\.jenkins\.ssh\known_hosts in order for it to run properly with Jenkins? The easiest way would be if I would be able to specify the path of the known_hosts file in the settings.xml. Looking at the relevant maven-wagon source [1], it is clear there is a bunch of logic for managing a KnownHostsProvider (which controls where the known_hosts data comes from). So I would be very surprised if this was not exposed at the Maven level -- i.e., if there was not a way to configure this in the POM somehow. Unfortunately wagon-ssh also doesn't show at which location it tries to open the known_hosts file. Did you try with mvn -X? That is verbose/debug mode. If it still doesn't echo the path, please file a JIRA issue for it: https://jira.codehaus.org/browse/WAGON (create account at https://xircles.codehaus.org/signup) Does no one of you use that wagon-ssh? My group uses wagon-webdav-jackrabbit for artifact deploys, and we aren't deploying our Maven sites properly yet. Regards, Curtis [1] https://github.com/apache/maven-wagon/blob/41336732524e33fa3fdc99f07b6add013b23dfa7/wagon-providers/wagon-ssh/src/main/java/org/apache/maven/wagon/providers/ssh/jsch/AbstractJschWagon.java#L89 [2] http://stackoverflow.com/q/12689139 On Tue, Jun 24, 2014 at 6:42 AM, Hohl, Gerrit g.h...@aurenz.de wrote: Hello everyone, I still having this problem. Does no one of you use that wagon-ssh? Don't you upload the Maven report on a web server? Or do you use simply other methods? If there is a better method I would be happy to know that. :) Regards, Gerrit -Ursprüngliche Nachricht- Von: Hohl, Gerrit [mailto:g.h...@aurenz.de] Gesendet: Donnerstag, 12. Juni 2014 17:40 An: Maven Users List Betreff: AW: site-deploy using wagon-ssh: User input needed Hello everyone, :) okay, I tried a different approach: Instead of that configuration section in the settings.xml I copied my local know_hosts file from C:\Users\[MY_USER]\.ssh\known_hosts to the server: C:\Windows\system32\config\.ssh\known_hosts I read in the Internet that this folder is the folder of the system account which is used e.g. by Tomcat. And as Jenkins and Maven are executed by Tomcat, they should work on the same folder. Unfortunately I didn't work: I see in the Jenkins Build log that wagon-ssh keeps asking if it should trust the connection by showing the SSH RSA fingerprint. Unfortunately wagon-ssh also doesn't show at which location it tries to open the known_hosts file. The easiest way would be if I would be able to specify the path of the known_hosts file in the settings.xml. But I haven't found anything about a configuration parameter like that. Regards, Gerrit - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy upload location
Documented behavior: If subprojects inherit the site URL from a parent
POM, they will automatically append their artifactId to form their
effective deployment location.
This is the default behavior and currently cannot be switched off. If
you want to change this, you have to explicitly set the url in all
sub-projects.
HTH,
-Lukas
David Kendall wrote:
Is there any way to control the exact upload location when doing a mvn
site-deploy?
I am working with a code base that has a number of parent pom files -
different parents for different types of project. When i do a mvn
site-deploy the site is uploaded to something like
${site.deploy.base.url}/${grandparent.artifactid}/${parent.artifactid}/${project.artifactId}/...
What I really want is for the site-deploy to ignore the parent poms and
to upload to a pattern more like this
${site.deploy.base.url}/${project.groupId}/${project.artifactId}/${project.version}/...
In my parent pom I have tried adding specifying
distributionManagement
site
iddocumentation-site/id
url${site.deploy.base.url}/${project.groupId}/${project.artifactId}/${project.version}/url
/site
/distributionManagement
.. but maven just appends the names of the parent poms to the paths anyway.
I am using maven 2.0.11 and deploying using SCP - in case this is
significant.
Is there any way to override the default upload path when deploying a site?
Thanks
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deploy problem
site-plugin-2.3 has some problems with property resolution, see eg
http://jira.codehaus.org/browse/MSITE-585. I'm not sure if this is the
same issue as yours, could you try with 2.4-SNAPSHOT?
HTH,
-Lukas
Johan Vogelzang wrote:
Oh I forgot...
I use Maven 2.2.1 and maven-site-plugin version 2.3.
The behavior is the same on Windows and Linux.
Johan.
2011/7/13 Johan Vogelzangjohan.vogelz...@gmail.com
Hi Maven users,
I've a problem with deploying a site to an url containing property
variables.
The site url -as part of the distributionManagement section- is located in
the company parent pom:
properties
reposerver.host.namemyrepohost/reposerver.host.name
/properties
...
distributionManagement
site
idsite-repo/id
urlscp://${reposerver.host.name}/var/www/html/maven2/sites/url
/site
/distributionManagement
When I execute mvn help:effective-pom I see that the url is correctly
resolved to: scp://myrepohost/var/www/html/maven2/sites
But when I execute mvn site-deploy the build fails with an
UnknownHostException. In the logging I see that the url is not resolved:
[INFO] [site:deploy {execution: default-deploy}]
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Connection refused
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnecting
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Cannot connect. Reason: java.net.UnknownHostException: ${
reposerver.host.name}
Thanks in advance,
--
Johan Vogelzang
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deploy problem
Oh I forgot...
I use Maven 2.2.1 and maven-site-plugin version 2.3.
The behavior is the same on Windows and Linux.
Johan.
2011/7/13 Johan Vogelzang johan.vogelz...@gmail.com
Hi Maven users,
I've a problem with deploying a site to an url containing property
variables.
The site url -as part of the distributionManagement section- is located in
the company parent pom:
properties
reposerver.host.namemyrepohost/reposerver.host.name
/properties
...
distributionManagement
site
idsite-repo/id
urlscp://${reposerver.host.name}/var/www/html/maven2/sites/url
/site
/distributionManagement
When I execute mvn help:effective-pom I see that the url is correctly
resolved to: scp://myrepohost/var/www/html/maven2/sites
But when I execute mvn site-deploy the build fails with an
UnknownHostException. In the logging I see that the url is not resolved:
[INFO] [site:deploy {execution: default-deploy}]
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Connection refused
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnecting
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Cannot connect. Reason: java.net.UnknownHostException: ${
reposerver.host.name}
Thanks in advance,
--
Johan Vogelzang
--
Johan Vogelzang
Antwort: Re: Site deploy problem
Hi, Oh I forgot... I use Maven 2.2.1 and maven-site-plugin version 2.3. The behavior is the same on Windows and Linux. What kind of SCP transfer do you want to use? Password-less, i.e. public-key-authentification, or using username/password? In the first case: Did you upload your public key to the remote machine? In the latter case: You have to add a server entry section containing your user credentials in your $HOME/.m2/settings.xml: servers server idsite-repo/id usernameyour_username/username passwordyour_password/password /server ... /servers Regards Thorsten
Re: Re: Site deploy problem
Thorsten, We use username/password authentication, and my settings.xml is set up as you described. But I don't think this is a authentication issue. As you can see the hostname is not resolved properly so there is no server connection to do the authentication. Regards, Johan. 2011/7/13 Thorsten Heit thorsten.h...@vkb.de Hi, Oh I forgot... I use Maven 2.2.1 and maven-site-plugin version 2.3. The behavior is the same on Windows and Linux. What kind of SCP transfer do you want to use? Password-less, i.e. public-key-authentification, or using username/password? In the first case: Did you upload your public key to the remote machine? In the latter case: You have to add a server entry section containing your user credentials in your $HOME/.m2/settings.xml: servers server idsite-repo/id usernameyour_username/username passwordyour_password/password /server ... /servers Regards Thorsten -- Johan Vogelzang
Re: Site deploy problem
I just did a test with maven-site-plugin version 2.0-beta-7 (instead of 2.3)
and with this one the build seems to run ok (!?).
build
pluginManagement
plugins
plugin
artifactIdmaven-site-plugin/artifactId
version2.0-beta-7/version
/plugin
Can anyone confirm if this is a known bug?
Regards,
Johan.
2011/7/13 Johan Vogelzang johan.vogelz...@gmail.com
Hi Maven users,
I've a problem with deploying a site to an url containing property
variables.
The site url -as part of the distributionManagement section- is located in
the company parent pom:
properties
reposerver.host.namemyrepohost/reposerver.host.name
/properties
...
distributionManagement
site
idsite-repo/id
urlscp://${reposerver.host.name}/var/www/html/maven2/sites/url
/site
/distributionManagement
When I execute mvn help:effective-pom I see that the url is correctly
resolved to: scp://myrepohost/var/www/html/maven2/sites
But when I execute mvn site-deploy the build fails with an
UnknownHostException. In the logging I see that the url is not resolved:
[INFO] [site:deploy {execution: default-deploy}]
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Connection refused
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnecting
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Cannot connect. Reason: java.net.UnknownHostException: ${
reposerver.host.name}
Thanks in advance,
--
Johan Vogelzang
--
Johan Vogelzang
Re: Site deploy problem
http://jira.codehaus.org/browse/MSITE-585 ?
Regards,
Hervé
Le mercredi 13 juillet 2011, Johan Vogelzang a écrit :
I just did a test with maven-site-plugin version 2.0-beta-7 (instead of
2.3) and with this one the build seems to run ok (!?).
build
pluginManagement
plugins
plugin
artifactIdmaven-site-plugin/artifactId
version2.0-beta-7/version
/plugin
Can anyone confirm if this is a known bug?
Regards,
Johan.
2011/7/13 Johan Vogelzang johan.vogelz...@gmail.com
Hi Maven users,
I've a problem with deploying a site to an url containing property
variables.
The site url -as part of the distributionManagement section- is located
in the company parent pom:
properties
reposerver.host.namemyrepohost/reposerver.host.name
/properties
...
distributionManagement
site
idsite-repo/id
urlscp://${reposerver.host.name}/var/www/html/maven2/sites/url
/site
/distributionManagement
When I execute mvn help:effective-pom I see that the url is correctly
resolved to: scp://myrepohost/var/www/html/maven2/sites
But when I execute mvn site-deploy the build fails with an
UnknownHostException. In the logging I see that the url is not resolved:
[INFO] [site:deploy {execution: default-deploy}]
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Connection refused
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnecting
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Cannot connect. Reason: java.net.UnknownHostException: ${
reposerver.host.name}
Thanks in advance,
--
Johan Vogelzang
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy suppresses actual build in my project
I am staring at it now, and I don't. I see it running the enforcer plugin, and gets no errors, and then goes on to the next project. I'm going to see if 3.0.3 is different or more informative. On Thu, May 26, 2011 at 10:00 PM, Martin Gainty mgai...@hotmail.com wrote: run mvn -e -X deploy site-deploy to see environment and debug information do you see anything missing (.properties or.xml or a folder) ? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Thu, 26 May 2011 21:47:28 -0400 Subject: site-deploy suppresses actual build in my project From: bimargul...@gmail.com To: users@maven.apache.org After not releasing a particular project of mine for a moment, I found that release:perform failed today. After some sleuthing, I discover that the problem is that running mvn deploy site-deploy in this project results in stopping dead before even running compile. No failure, it just doesn't finish the lifecycle, and then the Leaving out the site-deploy fixes the problem. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy suppresses actual build in my project
With maven3.0.3, I get: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on project perceptron-training: failed to get Reports: Failed to execute goal on project average-perceptron-entities: Could not resolve dependencies for project com.basistech.rex2009:average-perceptron-entities:jar:28-SNAPSHOT: Could not find artifact com.basistech.rex2009:gazeteer-decoder-wrapper:jar:28-SNAPSHOT - [Help 1] that is, I run what the release plugin runs: mvn site site-deploy. This is a top-level project with modules. It runs the build and deploy of the top-level, and then immediately fails with the above. What it is doing in 'Reports' before it's run the builds proper? On Thu, May 26, 2011 at 10:00 PM, Martin Gainty mgai...@hotmail.com wrote: run mvn -e -X deploy site-deploy to see environment and debug information do you see anything missing (.properties or.xml or a folder) ? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Thu, 26 May 2011 21:47:28 -0400 Subject: site-deploy suppresses actual build in my project From: bimargul...@gmail.com To: users@maven.apache.org After not releasing a particular project of mine for a moment, I found that release:perform failed today. After some sleuthing, I discover that the problem is that running mvn deploy site-deploy in this project results in stopping dead before even running compile. No failure, it just doesn't finish the lifecycle, and then the Leaving out the site-deploy fixes the problem. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy suppresses actual build in my project
I found the culprit, but I don't understand it, and I don't know if it's a defect. The following reporting config for javadoc sets this problem into motion, apparently since maven-site-plugin 2.2, or perhaps an update to the javadoc plugin. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.8/version reportSets reportSet idnon-aggregate/id configuration /configuration reports reportjavadoc/report /reports /reportSet reportSet idaggregate/id configuration /configuration reports reportaggregate/report /reports /reportSet /reportSets /plugin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: site-deploy suppresses actual build in my project
run mvn -e -X deploy site-deploy to see environment and debug information do you see anything missing (.properties or.xml or a folder) ? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Thu, 26 May 2011 21:47:28 -0400 Subject: site-deploy suppresses actual build in my project From: bimargul...@gmail.com To: users@maven.apache.org After not releasing a particular project of mine for a moment, I found that release:perform failed today. After some sleuthing, I discover that the problem is that running mvn deploy site-deploy in this project results in stopping dead before even running compile. No failure, it just doesn't finish the lifecycle, and then the Leaving out the site-deploy fixes the problem. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy always appends ${project.artifactId} in the deploy URL
This is expected and documented [1]: 'If subprojects inherit the site
URL from a parent POM, they will automatically append their artifactId
to form their effective deployment location'. If you want to overide
that, you need to declare a site.url in the sub-project.
HTH,
-Lukas
[1] http://maven.apache.org/plugins/maven-site-plugin/usage.html
Simone Tripodi wrote:
Hi all guys,
I'm facing a wired issue, I don't understand if it concerns the
maven-site-plugin or the deploy plugin, btw every time I try to deploy
the site, the ${project.artifactId} is always appended to the
distributionManagement.site.url
i.e. if the url is
ftp://ftp.acme.org/projects/${project.artifactId}/${project.version}
the resulting url will be
ftp://ftp.acme.org/projects/${project.artifactId}/${project.version}/${project.artifactId}
Any hint/suggestion? My parent pom is public and can be found on
github[1], many thanks in advance!
Simo
[1] https://github.com/99soft/infra
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy always appends ${project.artifactId} in the deploy URL
gotcha, looks like I overlooked that part.
KUDOS for you Lukas! thanks a lot, it worked :)
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Feb 18, 2011 at 9:47 PM, Lukas Theussl ltheu...@apache.org wrote:
This is expected and documented [1]: 'If subprojects inherit the site URL
from a parent POM, they will automatically append their artifactId to form
their effective deployment location'. If you want to overide that, you need
to declare a site.url in the sub-project.
HTH,
-Lukas
[1] http://maven.apache.org/plugins/maven-site-plugin/usage.html
Simone Tripodi wrote:
Hi all guys,
I'm facing a wired issue, I don't understand if it concerns the
maven-site-plugin or the deploy plugin, btw every time I try to deploy
the site, the ${project.artifactId} is always appended to the
distributionManagement.site.url
i.e. if the url is
ftp://ftp.acme.org/projects/${project.artifactId}/${project.version}
the resulting url will be
ftp://ftp.acme.org/projects/${project.artifactId}/${project.version}/${project.artifactId}
Any hint/suggestion? My parent pom is public and can be found on
github[1], many thanks in advance!
Simo
[1] https://github.com/99soft/infra
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy and m-release-p
OK, I've discovered part of the problem I was having here. The company pom
defined the m-site-p in the build section which was invoking it when it
should not have been. Now I have the m-site-p configured in the company pom
in the pluginManagement section only and am getting much closer to the
desired outcome. The problem now is that the new dev version of the site is
being deployed even though the maven logs are saying otherwise.
Is anyone else seeing anything like this on m3 with m-site-p:3.0-beta-2 and
m-release-p:2.1?
It would seem that my current configuration should actually do what I want
but there seems to be something amiss between using ${project.version} in
the site.url and the actual version that gets uploaded.
I'll continue to investigate but if anyone has any input I would be
grateful.
-Ryan
On Sun, Jan 9, 2011 at 11:24 AM, Ryan Connolly ryn...@gmail.com wrote:
Hello:
I am trying to update my company pom to include a m-release-p
configuration for all other internal projects to use and in the process I am
hoping to get site deployment to upload just the released version of
javadocs upon release. It would appear that using the default release goals
of deploy site-deploy is uploading the current SNAPSHOT version of the
site on prepare and the updated dev version on perform. What I would like
to have happen is for the site-deploy goal to be run from the checkout
directory resulting in one site deployment of the released site. Is there
any way to do this by configuring the m-release-p and a site
distributionManagement element only or would this require a release profile
and perhaps antrun? I also don't want to require my team to remember to cd
into the checkout directory and run site-deploy there in order to get
released site deployments working.
I'm hoping to end up with a structure on my webserver after performing
releases to project1 and project2 as follows:
project1
- 1.0
- 1.1
project2
- 1.0
- 1.1
I have defined the site distributionManagement as follows in each POM:
distributionManagement
site
idsite/id
nameAPI Documentation/name
url${site.deploy.url}/${project.artifactId}/${project.version}/url
/site
/distributionManagement
Does anyone have any ideas on how I might get this to work out?
Thanks in advance,
-Ryan
Re: site-deploy and m-release-p
Sorry for all the noise... I have this working now. The only real issue
here was that there was a m-site-p definition in the company pom build
section. Everything else is working as it should be. Time to take the rest
of the day off!
Thanks for listenting :)
-Ryan
On Sun, Jan 9, 2011 at 12:22 PM, Ryan Connolly ryn...@gmail.com wrote:
OK, I've discovered part of the problem I was having here. The company pom
defined the m-site-p in the build section which was invoking it when it
should not have been. Now I have the m-site-p configured in the company pom
in the pluginManagement section only and am getting much closer to the
desired outcome. The problem now is that the new dev version of the site is
being deployed even though the maven logs are saying otherwise.
Is anyone else seeing anything like this on m3 with m-site-p:3.0-beta-2 and
m-release-p:2.1?
It would seem that my current configuration should actually do what I want
but there seems to be something amiss between using ${project.version} in
the site.url and the actual version that gets uploaded.
I'll continue to investigate but if anyone has any input I would be
grateful.
-Ryan
On Sun, Jan 9, 2011 at 11:24 AM, Ryan Connolly ryn...@gmail.com wrote:
Hello:
I am trying to update my company pom to include a m-release-p
configuration for all other internal projects to use and in the process I am
hoping to get site deployment to upload just the released version of
javadocs upon release. It would appear that using the default release goals
of deploy site-deploy is uploading the current SNAPSHOT version of the
site on prepare and the updated dev version on perform. What I would like
to have happen is for the site-deploy goal to be run from the checkout
directory resulting in one site deployment of the released site. Is there
any way to do this by configuring the m-release-p and a site
distributionManagement element only or would this require a release profile
and perhaps antrun? I also don't want to require my team to remember to cd
into the checkout directory and run site-deploy there in order to get
released site deployments working.
I'm hoping to end up with a structure on my webserver after performing
releases to project1 and project2 as follows:
project1
- 1.0
- 1.1
project2
- 1.0
- 1.1
I have defined the site distributionManagement as follows in each POM:
distributionManagement
site
idsite/id
nameAPI Documentation/name
url${site.deploy.url}/${project.artifactId}/${project.version}/url
/site
/distributionManagement
Does anyone have any ideas on how I might get this to work out?
Thanks in advance,
-Ryan
Re: site-deploy: configured password is ignored
I found the reason:
the sshd on the server used PasswordAuthentication no. After
switching to yes my maven config works fine.
Regards,
Lars
2010/6/10 Lars Fischer lfisc...@fastmail.fm:
Hello
i would like to deploy a mvn-site using scp with user/password.
This is contained the settings.xml:
server
idsite/id
usernameaUser/username
passwordmyPassword/password
/server
The pom.xml looks like this:
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.1.1/version
/plugin
[...]
distributionManagement
[...]
site
idsite/id
urlscp://${scm.host}/srv/www/htdocs/maven/${project.artifactId}/url
/site
/distributionManagement
Running site-deploy, maven asks for the password:
[INFO] [site:deploy {execution: default-deploy}]
Keyboard interactive required, supplied password is ignored
Password:
Why is the configured password ignored?
Where is my mistake?
Regards,
Lars
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy using DAV with digest-auth
thanks Brett,
I had a look in the httpd error_log. When using wagon-1.0-beta-2 the server
logs:
Digest: client used wrong authentication scheme `Basic': /test/
Apparently, it simply doesn't support digest auth.
So I changed the extension to wagon-webdav-jackrabbit:1.0-beta-6 and now it
works (after some adjustment of the httpd.conf).
brettporter wrote:
It seems you have pegged the webdav provider to 1.0-beta-2.
I'd suggest removing that build extension, or replacing it with:
g: org.apache.maven.wagon
a: wagon-webdav-jackrabbit
v: 1.0-beta-6
Cheers,
Brett
On 25/09/2009, at 7:48 PM, Marc Lustig wrote:
I tried using Mvn 2.2.1 and got the same error from the wagon plugin:
[INFO] [site:deploy {execution: default-deploy}]
WAGON_VERSION: 1.0-beta-2
http://ci1.xxx/test - Session: Opened
Uploading: ./css/maven-base.css to http://ci1.xxx/test
# Transfer error: org.apache.commons.httpclient.HttpException:
Unbuffered
entity enclosing request can not be repeated.
http://ci1.xxx/test - Session: Disconnecting
http://ci1.xxx/test - Session: Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: PUT request for: ./css/maven-base.css to maven-
base.css
failed
Unbuffered entity enclosing request can not be repeated.
I also tried using -X but got no more output to indicate the root
cause.
brettporter wrote:
This is probably related to the authentication re-submissions that
John worked on. Is it any better in Maven 2.2.1?
- Brett
On 23/09/2009, at 10:19 PM, Marc Lustig wrote:
Hi,
we have configured our httpd to use digest-authentication for dav
write-operations.
In the pom, we have configured the site distribution
site
idmaven-site/id
urldav:http://server/test/url
/site
In settings, we have configured the credentials as a server-tag
server
idmaven-site/id
usernameusername/username
passwordpw/password
/server
When we run maven 2.1 site-deploy, we get the following error:
[INFO] [site:deploy]
http://ci1.muc.allianz/test - Session: Opened
Uploading: ./css/maven-base.css to http://ci1.muc.allianz/test
# Transfer error: org.apache.commons.httpclient.HttpException:
Unbuffered
entity enclosing request can not be repeated.
http://ci1.muc.allianz/test - Session: Disconnecting
http://ci1.muc.allianz/test - Session: Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: PUT request for: ./css/maven-base.css to maven-
base.css
failed
Unbuffered entity enclosing request can not be repeated.
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
uploading site
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
uploading
site
at
org.apache.maven.plugins.site.SiteDeployMojo.execute
(SiteDeployMojo.java:200)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
Re: site-deploy using DAV with digest-auth
It seems you have pegged the webdav provider to 1.0-beta-2.
I'd suggest removing that build extension, or replacing it with:
g: org.apache.maven.wagon
a: wagon-webdav-jackrabbit
v: 1.0-beta-6
Cheers,
Brett
On 25/09/2009, at 7:48 PM, Marc Lustig wrote:
I tried using Mvn 2.2.1 and got the same error from the wagon plugin:
[INFO] [site:deploy {execution: default-deploy}]
WAGON_VERSION: 1.0-beta-2
http://ci1.xxx/test - Session: Opened
Uploading: ./css/maven-base.css to http://ci1.xxx/test
# Transfer error: org.apache.commons.httpclient.HttpException:
Unbuffered
entity enclosing request can not be repeated.
http://ci1.xxx/test - Session: Disconnecting
http://ci1.xxx/test - Session: Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: PUT request for: ./css/maven-base.css to maven-
base.css
failed
Unbuffered entity enclosing request can not be repeated.
I also tried using -X but got no more output to indicate the root
cause.
brettporter wrote:
This is probably related to the authentication re-submissions that
John worked on. Is it any better in Maven 2.2.1?
- Brett
On 23/09/2009, at 10:19 PM, Marc Lustig wrote:
Hi,
we have configured our httpd to use digest-authentication for dav
write-operations.
In the pom, we have configured the site distribution
site
idmaven-site/id
urldav:http://server/test/url
/site
In settings, we have configured the credentials as a server-tag
server
idmaven-site/id
usernameusername/username
passwordpw/password
/server
When we run maven 2.1 site-deploy, we get the following error:
[INFO] [site:deploy]
http://ci1.muc.allianz/test - Session: Opened
Uploading: ./css/maven-base.css to http://ci1.muc.allianz/test
# Transfer error: org.apache.commons.httpclient.HttpException:
Unbuffered
entity enclosing request can not be repeated.
http://ci1.muc.allianz/test - Session: Disconnecting
http://ci1.muc.allianz/test - Session: Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: PUT request for: ./css/maven-base.css to maven-
base.css
failed
Unbuffered entity enclosing request can not be repeated.
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
uploading site
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
uploading
site
at
org.apache.maven.plugins.site.SiteDeployMojo.execute
(SiteDeployMojo.java:200)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.apache.maven.wagon.TransferFailedException: PUT
request for:
./css/maven-base.css to maven-base.css failed
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.put
(WebDavWagon.java:326)
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory
(WebDavWagon.java:555)
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory
(WebDavWagon.java:549)
at
Re: site-deploy using DAV with digest-auth
I tried using Mvn 2.2.1 and got the same error from the wagon plugin:
[INFO] [site:deploy {execution: default-deploy}]
WAGON_VERSION: 1.0-beta-2
http://ci1.xxx/test - Session: Opened
Uploading: ./css/maven-base.css to http://ci1.xxx/test
# Transfer error: org.apache.commons.httpclient.HttpException: Unbuffered
entity enclosing request can not be repeated.
http://ci1.xxx/test - Session: Disconnecting
http://ci1.xxx/test - Session: Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: PUT request for: ./css/maven-base.css to maven-base.css
failed
Unbuffered entity enclosing request can not be repeated.
I also tried using -X but got no more output to indicate the root cause.
brettporter wrote:
This is probably related to the authentication re-submissions that
John worked on. Is it any better in Maven 2.2.1?
- Brett
On 23/09/2009, at 10:19 PM, Marc Lustig wrote:
Hi,
we have configured our httpd to use digest-authentication for dav
write-operations.
In the pom, we have configured the site distribution
site
idmaven-site/id
urldav:http://server/test/url
/site
In settings, we have configured the credentials as a server-tag
server
idmaven-site/id
usernameusername/username
passwordpw/password
/server
When we run maven 2.1 site-deploy, we get the following error:
[INFO] [site:deploy]
http://ci1.muc.allianz/test - Session: Opened
Uploading: ./css/maven-base.css to http://ci1.muc.allianz/test
# Transfer error: org.apache.commons.httpclient.HttpException:
Unbuffered
entity enclosing request can not be repeated.
http://ci1.muc.allianz/test - Session: Disconnecting
http://ci1.muc.allianz/test - Session: Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: PUT request for: ./css/maven-base.css to maven-
base.css
failed
Unbuffered entity enclosing request can not be repeated.
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
uploading site
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
uploading
site
at
org.apache.maven.plugins.site.SiteDeployMojo.execute
(SiteDeployMojo.java:200)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.apache.maven.wagon.TransferFailedException: PUT
request for:
./css/maven-base.css to maven-base.css failed
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.put
(WebDavWagon.java:326)
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory
(WebDavWagon.java:555)
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory
(WebDavWagon.java:549)
at
org.apache.maven.plugins.site.SiteDeployMojo.execute
(SiteDeployMojo.java:184)
... 18 more
Caused by:
Re: site-deploy using DAV with digest-auth
This is probably related to the authentication re-submissions that John worked on. Is it any better in Maven 2.2.1? - Brett On 23/09/2009, at 10:19 PM, Marc Lustig wrote: Hi, we have configured our httpd to use digest-authentication for dav write-operations. In the pom, we have configured the site distribution site idmaven-site/id urldav:http://server/test/url /site In settings, we have configured the credentials as a server-tag server idmaven-site/id usernameusername/username passwordpw/password /server When we run maven 2.1 site-deploy, we get the following error: [INFO] [site:deploy] http://ci1.muc.allianz/test - Session: Opened Uploading: ./css/maven-base.css to http://ci1.muc.allianz/test # Transfer error: org.apache.commons.httpclient.HttpException: Unbuffered entity enclosing request can not be repeated. http://ci1.muc.allianz/test - Session: Disconnecting http://ci1.muc.allianz/test - Session: Disconnected [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error uploading site Embedded error: PUT request for: ./css/maven-base.css to maven- base.css failed Unbuffered entity enclosing request can not be repeated. [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments (DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading site at org.apache.maven.plugins.site.SiteDeployMojo.execute (SiteDeployMojo.java:200) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:558) ... 16 more Caused by: org.apache.maven.wagon.TransferFailedException: PUT request for: ./css/maven-base.css to maven-base.css failed at org.apache.maven.wagon.providers.webdav.WebDavWagon.put (WebDavWagon.java:326) at org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory (WebDavWagon.java:555) at org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory (WebDavWagon.java:549) at org.apache.maven.plugins.site.SiteDeployMojo.execute (SiteDeployMojo.java:184) ... 18 more Caused by: org.apache.commons.httpclient.HttpException: Unbuffered entity enclosing request can not be repeated. Is this problem related to the wagon-plugin? Is the wagon-plugin not compatible with digest auth ? -- View this message in context: http://www.nabble.com/site-deploy-using-DAV-with-digest-auth-tp25531105p25531105.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deploy - missing site descriptor?
Oops! Nevermind. Chalk this one up to blondness. :-)
David C. Hicks wrote:
I keep getting the error Missing site information in the distribution
management element in the project.., but I clearly have a site
descriptor in that section...
site
idags-utilities.allureglobal.com/id
nameAGS Utilities/name
url${site.deploy.base}/url
/site
/distributionManagement
${site.deploy.base} is defined in a set of properties ahead of the
distributionManagement section.
Can anyone give me any clues how to track down this problem? The error
is simply not descriptive enough - to me. :-)
Thanks,
Dave
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: site deploy SiteToolException: Error parsing site descriptor
Take a look at your site descriptor. (src/site/site.xml) It should follow the decorations schema [1] It looks like yours start with html instead of project. [1] http://maven.apache.org/doxia/doxia-sitetools-1.0.x/doxia-decoration-model/decoration.html Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, May 5, 2009 at 9:02 PM, L. J. apache.maill...@gmail.com wrote: Expected root element 'project' but found 'html' - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deploy to local directory
Use mvn %some_other_goal% site:stage -DstagingDirectory=%desired_site_dir%
Regards,
Stevo.
On Fri, Apr 10, 2009 at 6:41 PM, David Hoffer dhoff...@gmail.com wrote:
Can someone help with a simple site plugin question?
I am just trying to build a site of a multi-module project and want to
publish it to my local hard drive. Here is my pom.
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.0/version
/plugin
/plugins
distributionManagement
...
site
idwebsite/id
urlfile://${basedir}/target/website/url
/site
/distributionManagement
If I run mvn site:deploy it creates only part of the site at
${basedir}/target/website, the root content is there and just one project
module, it's like it just quit!
If I run mvn site:stage it creates a valid site with all links working but
at a project specific staging location.
If I run mvn site:stage-deploy it creates a valid site but all links are
back up to the original module target locations.
None of these options create a valid web site under the specified URL
location. How can I do this?
Re: Site deploy to local directory
That doesn't really help it just overrides
urlfile://${basedir}/target/website/url
It still puts the content at %stagingDirectory%localhost/[SVN check out
folder]/target/website/[website content here]
I need a fixed location relative to %stagingDirectory%. I don't want [SVN
check out folder] to be part of the destination because it isn't constent.
-Dave
On Fri, Apr 10, 2009 at 10:56 AM, Stevo Slavić ssla...@gmail.com wrote:
Use mvn %some_other_goal% site:stage
-DstagingDirectory=%desired_site_dir%
Regards,
Stevo.
On Fri, Apr 10, 2009 at 6:41 PM, David Hoffer dhoff...@gmail.com wrote:
Can someone help with a simple site plugin question?
I am just trying to build a site of a multi-module project and want to
publish it to my local hard drive. Here is my pom.
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.0/version
/plugin
/plugins
distributionManagement
...
site
idwebsite/id
urlfile://${basedir}/target/website/url
/site
/distributionManagement
If I run mvn site:deploy it creates only part of the site at
${basedir}/target/website, the root content is there and just one project
module, it's like it just quit!
If I run mvn site:stage it creates a valid site with all links working
but
at a project specific staging location.
If I run mvn site:stage-deploy it creates a valid site but all links are
back up to the original module target locations.
None of these options create a valid web site under the specified URL
location. How can I do this?
Re: Site deploy to local directory
I think I forgot something, mvn site-deploy should deploy site to URL
specified in site section right?
The parent project does deploy here correctly. However the child modules do
not. So I figured each child pom must need its own site configuration to
append its module name to the URL, like:
site
idwebsite/id
url${website-root}/${project.artifactId}/url
/site
However this still doesn't work, the children keep putting their output in
their own target/website folder.
How can I enable the children to use the children's site URL?
-Dave
On Fri, Apr 10, 2009 at 11:11 AM, David Hoffer dhoff...@gmail.com wrote:
That doesn't really help it just overrides
urlfile://${basedir}/target/website/url
It still puts the content at %stagingDirectory%localhost/[SVN check out
folder]/target/website/[website content here]
I need a fixed location relative to %stagingDirectory%. I don't want [SVN
check out folder] to be part of the destination because it isn't constent.
-Dave
On Fri, Apr 10, 2009 at 10:56 AM, Stevo Slavić ssla...@gmail.com wrote:
Use mvn %some_other_goal% site:stage
-DstagingDirectory=%desired_site_dir%
Regards,
Stevo.
On Fri, Apr 10, 2009 at 6:41 PM, David Hoffer dhoff...@gmail.com wrote:
Can someone help with a simple site plugin question?
I am just trying to build a site of a multi-module project and want to
publish it to my local hard drive. Here is my pom.
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.0/version
/plugin
/plugins
distributionManagement
...
site
idwebsite/id
urlfile://${basedir}/target/website/url
/site
/distributionManagement
If I run mvn site:deploy it creates only part of the site at
${basedir}/target/website, the root content is there and just one
project
module, it's like it just quit!
If I run mvn site:stage it creates a valid site with all links working
but
at a project specific staging location.
If I run mvn site:stage-deploy it creates a valid site but all links are
back up to the original module target locations.
None of these options create a valid web site under the specified URL
location. How can I do this?
Re: Site deploy to local directory
Perhaps my macro is wrong.
How can I get parent's .${project.build.directory} in child?
-Dave
On Fri, Apr 10, 2009 at 12:28 PM, David Hoffer dhoff...@gmail.com wrote:
I think I forgot something, mvn site-deploy should deploy site to URL
specified in site section right?
The parent project does deploy here correctly. However the child modules
do not. So I figured each child pom must need its own site configuration to
append its module name to the URL, like:
site
idwebsite/id
url${website-root}/${project.artifactId}/url
/site
However this still doesn't work, the children keep putting their output in
their own target/website folder.
How can I enable the children to use the children's site URL?
-Dave
On Fri, Apr 10, 2009 at 11:11 AM, David Hoffer dhoff...@gmail.com wrote:
That doesn't really help it just overrides
urlfile://${basedir}/target/website/url
It still puts the content at %stagingDirectory%localhost/[SVN check out
folder]/target/website/[website content here]
I need a fixed location relative to %stagingDirectory%. I don't want [SVN
check out folder] to be part of the destination because it isn't constent.
-Dave
On Fri, Apr 10, 2009 at 10:56 AM, Stevo Slavić ssla...@gmail.com wrote:
Use mvn %some_other_goal% site:stage
-DstagingDirectory=%desired_site_dir%
Regards,
Stevo.
On Fri, Apr 10, 2009 at 6:41 PM, David Hoffer dhoff...@gmail.com
wrote:
Can someone help with a simple site plugin question?
I am just trying to build a site of a multi-module project and want to
publish it to my local hard drive. Here is my pom.
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.0/version
/plugin
/plugins
distributionManagement
...
site
idwebsite/id
urlfile://${basedir}/target/website/url
/site
/distributionManagement
If I run mvn site:deploy it creates only part of the site at
${basedir}/target/website, the root content is there and just one
project
module, it's like it just quit!
If I run mvn site:stage it creates a valid site with all links working
but
at a project specific staging location.
If I run mvn site:stage-deploy it creates a valid site but all links
are
back up to the original module target locations.
None of these options create a valid web site under the specified URL
location. How can I do this?
Re: Site deploy to local directory
That's what it was...anybody know a better way to get the parent build dir
than
${project.build.directory}/../../target/
-Dave
On Fri, Apr 10, 2009 at 12:47 PM, David Hoffer dhoff...@gmail.com wrote:
Perhaps my macro is wrong.
How can I get parent's .${project.build.directory} in child?
-Dave
On Fri, Apr 10, 2009 at 12:28 PM, David Hoffer dhoff...@gmail.com wrote:
I think I forgot something, mvn site-deploy should deploy site to URL
specified in site section right?
The parent project does deploy here correctly. However the child modules
do not. So I figured each child pom must need its own site configuration to
append its module name to the URL, like:
site
idwebsite/id
url${website-root}/${project.artifactId}/url
/site
However this still doesn't work, the children keep putting their output in
their own target/website folder.
How can I enable the children to use the children's site URL?
-Dave
On Fri, Apr 10, 2009 at 11:11 AM, David Hoffer dhoff...@gmail.comwrote:
That doesn't really help it just overrides
urlfile://${basedir}/target/website/url
It still puts the content at %stagingDirectory%localhost/[SVN check out
folder]/target/website/[website content here]
I need a fixed location relative to %stagingDirectory%. I don't want
[SVN check out folder] to be part of the destination because it isn't
constent.
-Dave
On Fri, Apr 10, 2009 at 10:56 AM, Stevo Slavić ssla...@gmail.comwrote:
Use mvn %some_other_goal% site:stage
-DstagingDirectory=%desired_site_dir%
Regards,
Stevo.
On Fri, Apr 10, 2009 at 6:41 PM, David Hoffer dhoff...@gmail.com
wrote:
Can someone help with a simple site plugin question?
I am just trying to build a site of a multi-module project and want to
publish it to my local hard drive. Here is my pom.
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.0/version
/plugin
/plugins
distributionManagement
...
site
idwebsite/id
urlfile://${basedir}/target/website/url
/site
/distributionManagement
If I run mvn site:deploy it creates only part of the site at
${basedir}/target/website, the root content is there and just one
project
module, it's like it just quit!
If I run mvn site:stage it creates a valid site with all links working
but
at a project specific staging location.
If I run mvn site:stage-deploy it creates a valid site but all links
are
back up to the original module target locations.
None of these options create a valid web site under the specified URL
location. How can I do this?
Re: Site deploy to local directory
On Fri, Apr 10, 2009 at 12:29 PM, David Hoffer dhoff...@gmail.com wrote:
That's what it was...anybody know a better way to get the parent build dir
than
${project.build.directory}/../../target/
Why? Normally you share things through the repository.
--
Wendy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deploy to local directory
I don't think this is the case for sharing; all I am trying to do is specify
the site deployment folder for child modules.
-Dave
On Fri, Apr 10, 2009 at 4:04 PM, Wendy Smoak wsm...@gmail.com wrote:
On Fri, Apr 10, 2009 at 12:29 PM, David Hoffer dhoff...@gmail.com wrote:
That's what it was...anybody know a better way to get the parent build
dir
than
${project.build.directory}/../../target/
Why? Normally you share things through the repository.
--
Wendy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deploy to local directory
On Fri, Apr 10, 2009 at 9:41 AM, David Hoffer dhoff...@gmail.com wrote:
Can someone help with a simple site plugin question?
I am just trying to build a site of a multi-module project and want to
publish it to my local hard drive. Here is my pom.
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.0/version
/plugin
/plugins
distributionManagement
...
site
idwebsite/id
urlfile://${basedir}/target/website/url
/site
/distributionManagement
If I run mvn site:deploy it creates only part of the site at
${basedir}/target/website, the root content is there and just one project
module, it's like it just quit!
What happens if you publish to file:///tmp/website?
Maven uses the 'target' directory as its work area, trying to publish
there doesn't make sense. And ${basedir} is different in each
submodule so as you've discovered, it's not going to work when
inherited.
--
Wendy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deploy to local directory
Yes file:///tmp/website would work but not for the child modules; its in the
child that I have the issue.
I got it working by specifying the parent folder as two levels up from each
child (module). (it seems there should be a maven property to get this
directly in the child.)
Actually /target/website worked fine because I'm deploying to a subfolder
after everything else is done. Then our CI (TeamCity) picks up the contents
from here and publishes the entire website for us, so we just use this as a
temp folder.
T-Dave
On Fri, Apr 10, 2009 at 4:30 PM, Wendy Smoak wsm...@gmail.com wrote:
On Fri, Apr 10, 2009 at 9:41 AM, David Hoffer dhoff...@gmail.com wrote:
Can someone help with a simple site plugin question?
I am just trying to build a site of a multi-module project and want to
publish it to my local hard drive. Here is my pom.
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.0/version
/plugin
/plugins
distributionManagement
...
site
idwebsite/id
urlfile://${basedir}/target/website/url
/site
/distributionManagement
If I run mvn site:deploy it creates only part of the site at
${basedir}/target/website, the root content is there and just one project
module, it's like it just quit!
What happens if you publish to file:///tmp/website?
Maven uses the 'target' directory as its work area, trying to publish
there doesn't make sense. And ${basedir} is different in each
submodule so as you've discovered, it's not going to work when
inherited.
--
Wendy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deploy to local directory
On Fri, Apr 10, 2009 at 4:06 PM, David Hoffer dhoff...@gmail.com wrote: Yes file:///tmp/website would work but not for the child modules; its in the child that I have the issue. It should work, and you shouldn't have to specify a site url in each child module. For example the site at [1] comes from the pom [2] which does not have a distributionManagement section. The url is inherited from the parent, then the artifactId is appended for each child module. [1] http://continuum.apache.org/ref/1.3.2/continuum-core/ [2] http://svn.apache.org/repos/asf/continuum/tags/continuum-1.3.2/continuum-core/pom.xml -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deploy to local directory
That is the behavior that I expected but it did not work. Instead the child modules put their site output in their own target folder. I could not find any solution other than redirect it back up. BTW, I'm using v2.1. -Dave On Fri, Apr 10, 2009 at 5:27 PM, Wendy Smoak wsm...@gmail.com wrote: On Fri, Apr 10, 2009 at 4:06 PM, David Hoffer dhoff...@gmail.com wrote: Yes file:///tmp/website would work but not for the child modules; its in the child that I have the issue. It should work, and you shouldn't have to specify a site url in each child module. For example the site at [1] comes from the pom [2] which does not have a distributionManagement section. The url is inherited from the parent, then the artifactId is appended for each child module. [1] http://continuum.apache.org/ref/1.3.2/continuum-core/ [2] http://svn.apache.org/repos/asf/continuum/tags/continuum-1.3.2/continuum-core/pom.xml -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site deploy ignoring server username and password settings
I workaround by putting username into my distribution management url as follows distributionManagement site idsomeservername.com/id urlscp://[EMAIL PROTECTED]/url /site /distributionManagement On 9/12/07, Sebastian Johnck [EMAIL PROTECTED] wrote: Sorry if this has been asked and answered. Despite having set the remote username and password in my settings.xmllike so server idsomeservername.com /id usernameremoteuser/username passwordremotepass/password /server and then in my pom configured like so: distributionManagement site idsomeservername.com/id urlsomeurl/url /site /distributionManagement The site deploy goal consistently attempts to login to someservername.comwith my windows username, and prompts me for my windows password. I'm on maven 2.0.6. Anyone been able to get this to work? -z -- Sebastian Johnck ~~~ MotionBased, A Division of Garmin International 180 Harbor Dr. Sausalito, CA 94965 www.motionbased.com Coordinates: N37° 51' 33 W 122° 29' 08 ~~~
Re: site-deploy asks for password...
Do you have more than one item in your settings.xml with id cedarsoftWeb? I have encountered the problem when I also had a mirror or repository with the same id, then it wouldn't find the password. My solution was to postfix all my servers with .server (i.e. cedarsoftWeb.server) and use that in distributionManagement. Hth, Nick Stolwijk Johannes Schneider wrote: Hi, I use the following to deploy my site: pom.xml: distributionManagement site idcedarsoftWeb/id nameCedarsoft Web/name urlscp://cedarsoft.org/var/customers/webs/jschneider/cedarsoft.org/url /site /distributionManagement my settings.xml looks like that: servers server idcedarsoftWeb/id usernamejohannes/username passwordmySecretPassword/password /server /servers When I try to site-deploy, Maven asks for my password interactivly Any suggestions? ssh -l johannes cedarsoft.org works with the given password... Regards, Johannes Schneider - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site-deploy asks for password...
No, I have just one server setting with that name. Johannes Schneider Nick Stolwijk wrote: Do you have more than one item in your settings.xml with id cedarsoftWeb? I have encountered the problem when I also had a mirror or repository with the same id, then it wouldn't find the password. My solution was to postfix all my servers with .server (i.e. cedarsoftWeb.server) and use that in distributionManagement. Hth, Nick Stolwijk Johannes Schneider wrote: Hi, I use the following to deploy my site: pom.xml: distributionManagement site idcedarsoftWeb/id nameCedarsoft Web/name urlscp://cedarsoft.org/var/customers/webs/jschneider/cedarsoft.org/url /site /distributionManagement my settings.xml looks like that: servers server idcedarsoftWeb/id usernamejohannes/username passwordmySecretPassword/password /server /servers When I try to site-deploy, Maven asks for my password interactivly Any suggestions? ssh -l johannes cedarsoft.org works with the given password... Regards, Johannes Schneider - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Johannes Schneider Im Lindenwasen 15 72810 Gomaringen Fon +49 7072 9229972 Fax +49 7072 50 Mobil +49 178 1364488 [EMAIL PROTECTED] http://www.johannes-schneider.info smime.p7s Description: S/MIME Cryptographic Signature
RE: site-deploy asks for password...
Do you have this directory $HOME/.ssh in your file system ? -- Olivier -Message d'origine- De : Nick Stolwijk [mailto:[EMAIL PROTECTED] Envoyé : mercredi 5 septembre 2007 16:07 À : Maven Users List Objet : Re: site-deploy asks for password... Do you have more than one item in your settings.xml with id cedarsoftWeb? I have encountered the problem when I also had a mirror or repository with the same id, then it wouldn't find the password. My solution was to postfix all my servers with .server (i.e. cedarsoftWeb.server) and use that in distributionManagement. Hth, Nick Stolwijk Johannes Schneider wrote: Hi, I use the following to deploy my site: pom.xml: distributionManagement site idcedarsoftWeb/id nameCedarsoft Web/name urlscp://cedarsoft.org/var/customers/webs/jschneider/cedarsoft.org/ url /site /distributionManagement my settings.xml looks like that: servers server idcedarsoftWeb/id usernamejohannes/username passwordmySecretPassword/password /server /servers When I try to site-deploy, Maven asks for my password interactivly Any suggestions? ssh -l johannes cedarsoft.org works with the given password... Regards, Johannes Schneider - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site-deploy asks for password...
Yes, I do. I tried to use the private key authentication: server idcedarsoftWeb/id usernamejohannes/username privateKey/home/johannes/.ssh/id_dsa/privateKey /server That works... Really strange. Johannes Schneider LAMY Olivier wrote: Do you have this directory $HOME/.ssh in your file system ? -- Olivier -Message d'origine- De : Nick Stolwijk [mailto:[EMAIL PROTECTED] Envoyé : mercredi 5 septembre 2007 16:07 À : Maven Users List Objet : Re: site-deploy asks for password... Do you have more than one item in your settings.xml with id cedarsoftWeb? I have encountered the problem when I also had a mirror or repository with the same id, then it wouldn't find the password. My solution was to postfix all my servers with .server (i.e. cedarsoftWeb.server) and use that in distributionManagement. Hth, Nick Stolwijk Johannes Schneider wrote: Hi, I use the following to deploy my site: pom.xml: distributionManagement site idcedarsoftWeb/id nameCedarsoft Web/name urlscp://cedarsoft.org/var/customers/webs/jschneider/cedarsoft.org/ url /site /distributionManagement my settings.xml looks like that: servers server idcedarsoftWeb/id usernamejohannes/username passwordmySecretPassword/password /server /servers When I try to site-deploy, Maven asks for my password interactivly Any suggestions? ssh -l johannes cedarsoft.org works with the given password... Regards, Johannes Schneider - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Johannes Schneider Im Lindenwasen 15 72810 Gomaringen Fon +49 7072 9229972 Fax +49 7072 50 Mobil +49 178 1364488 [EMAIL PROTECTED] http://www.johannes-schneider.info smime.p7s Description: S/MIME Cryptographic Signature
Re: site-deploy asks for password...
One more detail: Deploying works with the same username ans password (other id). So I think it might be related to the site plugin. Johannes Schneider Johannes Schneider wrote: Hi, I use the following to deploy my site: pom.xml: distributionManagement site idcedarsoftWeb/id nameCedarsoft Web/name urlscp://cedarsoft.org/var/customers/webs/jschneider/cedarsoft.org/url /site /distributionManagement my settings.xml looks like that: servers server idcedarsoftWeb/id usernamejohannes/username passwordmySecretPassword/password /server /servers When I try to site-deploy, Maven asks for my password interactivly Any suggestions? ssh -l johannes cedarsoft.org works with the given password... Regards, Johannes Schneider -- Johannes Schneider Im Lindenwasen 15 72810 Gomaringen Fon +49 7072 9229972 Fax +49 7072 50 Mobil +49 178 1364488 [EMAIL PROTECTED] http://www.johannes-schneider.info smime.p7s Description: S/MIME Cryptographic Signature
Re: site-deploy
Dear Paul,
I have configured my pom as you said. But it doesn't work.
Could you have a look to my pom?
Or to the fulltrace of mvn site-deploy?
You can see that it use evrytime wagon *1.0-alpha-5*
It seems that the ewtensions is not well read.
Thanks again for your help.
If you need more information, do not hesitate.
Francois
=
POM
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdfr.cns.genoscope.nemo/groupId
artifactIdnemo-knowledge-base/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
nameNemo Knowledge Base/name
inceptionYear2006/inceptionYear
description
This project is the knowledge base for all technologies relative
to nemo projects.
/description
organization
nameGenoscope - Centre National de Sequencage/name
urlhttp://www.genoscope.cns.fr//url
/organization
url
http://www.genoscope.cns.fr/nemo/projects/${project.artifactId}
/url
prerequisites
maven2.0/maven
/prerequisites
developers
developer
idccombe/id
nameCyril Combe/name
email[EMAIL PROTECTED]/email
organization
Genoscope- Computational System Biology Group - NEtwork
MOdelling Group
/organization
roles
roleDeveloper/role
/roles
timezone+1/timezone
/developer
developer
idflefevre/id
nameFrancois Le Fevre/name
email[EMAIL PROTECTED]/email
organization
Genoscope - Computational System Biology Group - NEtwork
MOdelling Group
/organization
roles
roleDeveloper/role
/roles
timezone+1/timezone
/developer
/developers
!-- The issue management system --
issueManagement
systemBugzilla/system
urlhttp://mars.pc.local/bugzilla//url
/issueManagement
!-- The source repository --
scm
connection
scm:svn:svn+ssh://subversion.genoscope.cns.fr/env/database/subversion/nemo/nemo_studio_repo/${project.artifactId}/trunk
/connection
developerConnection
scm:svn:svn+ssh://subversion.genoscope.cns.fr/env/database/subversion/nemo/nemo_studio_repo/${project.artifactId}/trunk
/developerConnection
!-- Si viewCVS or fisheye --
!--
urlhttp://www.genoscope.cns.fr/viewcvs.cgi/${project.artifactId}/url--
/scm
!-- Continuous integration --
ciManagement
systemcontinuum/system
urlhttp://taal.genoscope.cns.fr:8090/continuum/url
notifiers
notifier
typemail/type
configuration
sendOnSuccesstrue/sendOnSuccess
sendOnWarningtrue/sendOnWarning
sendOnFailuretrue/sendOnFailure
sendOnErrortrue/sendOnError
address[EMAIL PROTECTED]/address
/configuration
/notifier
/notifiers
/ciManagement
distributionManagement
!-- Configuration pour deployer le site web --
site
idMaven Developper Doc Website/id
url
scp://masaya1.genoscope.cns.fr/env/cns/pub/www/data/externe/nemo/projects/${project.artifactId}
/url
/site
!-- Configuration pour deployer le projet dans le remote repository
attention ne devrait ne plus etre associer au developpeur
mais seulement a Ci
donc juste pour la definition dans Ci puis a retirer --
repository
idinhouse/id
nameInhouse Internal Release Repository/name
url
scp://taal.genoscope.cns.fr/var/www/html/maven_repositories/inhouse
/url
/repository
snapshotRepository
idinhouse_snapshot/id
nameInhouse Internal Snapshot Repository/name
url
scp://taal.genoscope.cns.fr/var/www/html/maven_repositories/inhouse_snapshot
/url
uniqueVersionfalse/uniqueVersion
/snapshotRepository
/distributionManagement
reporting
plugins
!-- JAVADOC --
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjxr-maven-plugin/artifactId
/plugin
!-- CHANGE LOG FROM SCM --
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdchangelog-maven-plugin/artifactId
/plugin
!-- JUNIT REPORT --
plugin
artifactIdmaven-surefire-plugin/artifactId
Re: site-deploy
Dear Paul, Here an extract of my log when running mvn site-deploy -X -e Sincerly [] [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-repository-metadata:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime (selected for runtime) [DEBUG]* org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime)* [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-profile:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] [] [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-settings:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtime) *[DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtime (selected for runtime)* *[DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime (selected for runtime)* [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-plugin-descriptor:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime (selected for runtime) [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) *[DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime (selected for runtime)* [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) [DEBUG] velocity:velocity:jar:1.4:runtime (selected for runtime) [DEBUG] velocity:velocity-dep:jar:1.4:runtime (selected for runtime) *[DEBUG] Retrieving parent-POM: org.apache.maven.wagon:wagon::1.0-alpha-4 for project: null:wagon-provider-api:jar:1.0-alpha-4 from the repository. [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-4:runtime (selected for runtime)* [DEBUG] plexus:plexus-utils:jar:1.0.3:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0-beta-1 for project: org.apache.maven:maven-model:jar:2.0-beta-1 from the reposito [...] [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime (selected for runtime) *[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime)* [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for runtime) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-core:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtime) *[DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime (selected for runtime)* [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime (selected for runtime) *[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime)* [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) *[DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime (selected for runtime)* [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) [...] [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] -- end configuration -- [INFO] [site:deploy] *Using private key: /env/cns/home/flefevre/.ssh/id_rsa Password for [EMAIL PROTECTED]: * scp://masaya1.genoscope.cns.fr/env/cns/pub/www/data/externe/nemo/projects/nemo-knowledge-base - Session: Opened Executing command: mkdir -p /env/cns/pub/www/data/externe/nemo/projects/nemo-knowledge-base/. Executing command: mkdir -p /env/cns/pub/www/data/externe/nemo/projects/nemo-knowledge-base/. Dear Paul, I have configured my pom as you said. But it doesn't work. Could you have a look to my pom? Or to the fulltrace of mvn site-deploy? You can see that it use evrytime wagon *1.0-alpha-5* It seems that the ewtensions is not well read. Thanks again for your help. If you need more information, do not hesitate. Francois = POM project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Re: site-deploy
Dear Paul,
You are right but I could find the solution.
I have founded this post :
http://jira.codehaus.org/browse/MASSEMBLY-153
Upgrading wagon to version 1.0-beta-1 seems to have solved this issue
for us. Just replace the wagon*.jar files in the maven/lib directory
with the newer versions.
But it doesn't change anything!
Can you tell me where to configure in my pom which version of wagon to
use ??
Thanks
Francois
Hi Francois,
I'm not sure about the password prompt, but the file permissions problem
looks like another case of this:
http://jira.codehaus.org/browse/MASSEMBLY-153
Paul
Francois Le Fevre wrote:
Dear all,
I am using maven 2 on a linux OS
I want to deploy my project.
I have 2 problems:
-password authentification
-right on the web site files
1. Password
* so when i execute the commande mvn site-deploy,
* I need to enter each time my password !!, soi i need tyo put
it in my settings.xml even if i use a id_rsh key
2. Right on files
* the file generated have the following rights :
o drwx-w 5 flefevre g_nemo 8192 Nov 16 12:00
nemo-studio-bio
o -rw--w 1 flefevre g_nemo 5478 Nov 16 12:00
jxr.html
* i would like to have 664, and even if i put it to my
settings.xml it doesn't work
Thanks a lot for your help.
Francois
* My pom.xml
o distributionManagement
site
idNemo Projects Website/id
url
scp://masaya1.genoscope.cns.fr/env/cns/pub/www/data/externe/nemo/projects/${project.artifactId}
/url
/site
* My settings.xml
o server
idNemo Projects Website/id
usernameflefevre/username
privateKey/env/export/masaya/home/flefevre/.ssh/id_rsa/privateKey
!--directoryPermissions775/directoryPermissions
filePermissions664/filePermissions--
passwordXX/password
/server
--
Francois Le Fevre
Bioinformatics Engineer
Computational Systems Biology Group
Genoscope
Tél. : (+33) 1 60 87 45 83
Web : http://www.genoscope.cns.fr/bioinfo
--
Francois Le Fevre
Bioinformatics Engineer
Computational Systems Biology Group
Genoscope
Tél. : (+33) 1 60 87 45 83
Web : http://www.genoscope.cns.fr/bioinfo
Re: site-deploy
Paul,
i have made a false copy and paste : the post was
http://jira.codehaus.org/browse/WAGONSSH-44
a more precise question: where can I overwrite the version of
wagon-ssh-external or wagin-ssh ?
in which pom ? in which parapgraph.
Thanks a lot.
Francois
Dear Paul,
You are right but I could find the solution.
I have founded this post :
http://jira.codehaus.org/browse/MASSEMBLY-153
Upgrading wagon to version 1.0-beta-1 seems to have solved this issue
for us. Just replace the wagon*.jar files in the maven/lib directory
with the newer versions.
But it doesn't change anything!
Can you tell me where to configure in my pom which version of wagon to
use ??
Thanks
Francois
Hi Francois,
I'm not sure about the password prompt, but the file permissions problem
looks like another case of this:
http://jira.codehaus.org/browse/MASSEMBLY-153
Paul
Francois Le Fevre wrote:
Dear all,
I am using maven 2 on a linux OS
I want to deploy my project.
I have 2 problems:
-password authentification
-right on the web site files
1. Password
* so when i execute the commande mvn site-deploy,
* I need to enter each time my password !!, soi i need tyo put
it in my settings.xml even if i use a id_rsh key
2. Right on files
* the file generated have the following rights :
o drwx-w 5 flefevre g_nemo 8192 Nov 16 12:00
nemo-studio-bio
o -rw--w 1 flefevre g_nemo 5478 Nov 16 12:00
jxr.html
* i would like to have 664, and even if i put it to my
settings.xml it doesn't work
Thanks a lot for your help.
Francois
* My pom.xml
o distributionManagement
site
idNemo Projects Website/id
url
scp://masaya1.genoscope.cns.fr/env/cns/pub/www/data/externe/nemo/projects/${project.artifactId}
/url
/site
* My settings.xml
o server
idNemo Projects Website/id
usernameflefevre/username
privateKey/env/export/masaya/home/flefevre/.ssh/id_rsa/privateKey
!--directoryPermissions775/directoryPermissions
filePermissions664/filePermissions--
passwordXX/password
/server
--
Francois Le Fevre
Bioinformatics Engineer
Computational Systems Biology Group
Genoscope
Tél. : (+33) 1 60 87 45 83
Web : http://www.genoscope.cns.fr/bioinfo
--
Francois Le Fevre
Bioinformatics Engineer
Computational Systems Biology Group
Genoscope
Tél. : (+33) 1 60 87 45 83
Web : http://www.genoscope.cns.fr/bioinfo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: site-deploy
I'm not positive, but it is probably something like what I've got for
wagon-ftp in one of my projects:
project
...
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-ftp/artifactId
version1.0-beta-1/version
/extension
/extensions
...
/project
Paul
Francois Le Fevre wrote:
Paul,
i have made a false copy and paste : the post was
http://jira.codehaus.org/browse/WAGONSSH-44
a more precise question: where can I overwrite the version of
wagon-ssh-external or wagin-ssh ?
in which pom ? in which parapgraph.
Thanks a lot.
Francois
Dear Paul,
You are right but I could find the solution.
I have founded this post :
http://jira.codehaus.org/browse/MASSEMBLY-153
Upgrading wagon to version 1.0-beta-1 seems to have solved this issue
for us. Just replace the wagon*.jar files in the maven/lib directory
with the newer versions.
But it doesn't change anything!
Can you tell me where to configure in my pom which version of wagon to
use ??
Thanks
Francois
Hi Francois,
I'm not sure about the password prompt, but the file permissions problem
looks like another case of this:
http://jira.codehaus.org/browse/MASSEMBLY-153
Paul
Francois Le Fevre wrote:
Dear all,
I am using maven 2 on a linux OS
I want to deploy my project.
I have 2 problems:
-password authentification
-right on the web site files
1. Password
* so when i execute the commande mvn site-deploy,
* I need to enter each time my password !!, soi i need tyo put
it in my settings.xml even if i use a id_rsh key
2. Right on files
* the file generated have the following rights :
o drwx-w 5 flefevre g_nemo 8192 Nov 16 12:00
nemo-studio-bio
o -rw--w 1 flefevre g_nemo 5478 Nov 16 12:00
jxr.html
* i would like to have 664, and even if i put it to my
settings.xml it doesn't work
Thanks a lot for your help.
Francois
* My pom.xml
o distributionManagement
site
idNemo Projects Website/id
url
scp://masaya1.genoscope.cns.fr/env/cns/pub/www/data/externe/nemo/projects/${project.artifactId}
/url
/site
* My settings.xml
o server
idNemo Projects Website/id
usernameflefevre/username
privateKey/env/export/masaya/home/flefevre/.ssh/id_rsa/privateKey
!--directoryPermissions775/directoryPermissions
filePermissions664/filePermissions--
passwordXX/password
/server
--
Francois Le Fevre
Bioinformatics Engineer
Computational Systems Biology Group
Genoscope
Tél. : (+33) 1 60 87 45 83
Web : http://www.genoscope.cns.fr/bioinfo
--
Francois Le Fevre
Bioinformatics Engineer
Computational Systems Biology Group
Genoscope
Tél. : (+33) 1 60 87 45 83
Web : http://www.genoscope.cns.fr/bioinfo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/site-deploy-tf2642252s177.html#a7405500
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: site-deploy not copying Java Docs
Good day to you, Dmystery, In the build output, what gets processed first, javadoc or site:stage? Thanks, Franz Dmystery wrote: I've a multi-module project for which i'm generating a site. I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works fine and the modules are linked properly too. However, the Java doc generated are not copied to the staging directory. Only the index.html is copied, the rest remains in the project build directory. My parent pom looks like, . . distributionManagement site idmy-site/id namemy-site/name urlfile:///url /site /distributionManagement reporting plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdjxr-maven-plugin/artifactId /plugin /plugins /reporting . . Interestingly, instead of the above command, if i use 'mvn site-deploy' with site idmy-site/id namemy-site/name urlfile://c:/somedirectory/url /site in my pom, the apidocs are copied but the module and apidocs links do not exists. Is there a clean way of deploying a site on to the local machine?? -- View this message in context: http://www.nabble.com/site-deploy-not-copying-Java-Docs-tf2628872s177.html#a7374535 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site-deploy not copying Java Docs
site:stage gets processed first. I got the problem though. I now do a 'site-deploy' and all the links are working fine. There was a jira issue filed which said that the top most pom should have a url tag in it or else the modules links wont work good. franz see wrote: Good day to you, Dmystery, In the build output, what gets processed first, javadoc or site:stage? Thanks, Franz Dmystery wrote: I've a multi-module project for which i'm generating a site. I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works fine and the modules are linked properly too. However, the Java doc generated are not copied to the staging directory. Only the index.html is copied, the rest remains in the project build directory. My parent pom looks like, . . distributionManagement site idmy-site/id namemy-site/name urlfile:///url /site /distributionManagement reporting plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdjxr-maven-plugin/artifactId /plugin /plugins /reporting . . Interestingly, instead of the above command, if i use 'mvn site-deploy' with site idmy-site/id namemy-site/name urlfile://c:/somedirectory/url /site in my pom, the apidocs are copied but the module and apidocs links do not exists. Is there a clean way of deploying a site on to the local machine?? -- View this message in context: http://www.nabble.com/site-deploy-not-copying-Java-Docs-tf2628872s177.html#a7375485 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site-deploy
Hi Francois,
I'm not sure about the password prompt, but the file permissions problem
looks like another case of this:
http://jira.codehaus.org/browse/MASSEMBLY-153
Paul
Francois Le Fevre wrote:
Dear all,
I am using maven 2 on a linux OS
I want to deploy my project.
I have 2 problems:
-password authentification
-right on the web site files
1. Password
* so when i execute the commande mvn site-deploy,
* I need to enter each time my password !!, soi i need tyo put
it in my settings.xml even if i use a id_rsh key
2. Right on files
* the file generated have the following rights :
o drwx-w 5 flefevre g_nemo 8192 Nov 16 12:00
nemo-studio-bio
o -rw--w 1 flefevre g_nemo 5478 Nov 16 12:00
jxr.html
* i would like to have 664, and even if i put it to my
settings.xml it doesn't work
Thanks a lot for your help.
Francois
* My pom.xml
o distributionManagement
site
idNemo Projects Website/id
url
scp://masaya1.genoscope.cns.fr/env/cns/pub/www/data/externe/nemo/projects/${project.artifactId}
/url
/site
* My settings.xml
o server
idNemo Projects Website/id
usernameflefevre/username
privateKey/env/export/masaya/home/flefevre/.ssh/id_rsa/privateKey
!--directoryPermissions775/directoryPermissions
filePermissions664/filePermissions--
passwordXX/password
/server
--
Francois Le Fevre
Bioinformatics Engineer
Computational Systems Biology Group
Genoscope
Tél. : (+33) 1 60 87 45 83
Web : http://www.genoscope.cns.fr/bioinfo
--
View this message in context:
http://www.nabble.com/site-deploy-tf2642252s177.html#a7380192
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: site-deploy not copying Java Docs
Dmystery wrote: I've a multi-module project for which i'm generating a site. I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works fine and the modules are linked properly too. However, the Java doc generated are not copied to the staging directory. Only the index.html is copied, the rest remains in the project build directory. My parent pom looks like, . . distributionManagement site idmy-site/id namemy-site/name urlfile:///url /site /distributionManagement reporting plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdjxr-maven-plugin/artifactId /plugin /plugins /reporting . . Interestingly, instead of the above command, if i use 'mvn site-deploy' with site idmy-site/id namemy-site/name urlfile://c:/somedirectory/url /site in my pom, the apidocs are copied but the module and apidocs links do not exists. Is there a clean way of deploying a site on to the local machine?? You might want to replace the old org.codehaus.mojo:jxr-maven-plugin with the newer org.apache.maven.plugins:maven-jxr-plugin. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site-deploy not copying Java Docs
I dont think it adresses the issue here. I changed it to the lastest plugin though :) dennisl-2 wrote: Dmystery wrote: I've a multi-module project for which i'm generating a site. I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works fine and the modules are linked properly too. However, the Java doc generated are not copied to the staging directory. Only the index.html is copied, the rest remains in the project build directory. My parent pom looks like, . . distributionManagement site idmy-site/id namemy-site/name urlfile:///url /site /distributionManagement reporting plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdjxr-maven-plugin/artifactId /plugin /plugins /reporting . . Interestingly, instead of the above command, if i use 'mvn site-deploy' with site idmy-site/id namemy-site/name urlfile://c:/somedirectory/url /site in my pom, the apidocs are copied but the module and apidocs links do not exists. Is there a clean way of deploying a site on to the local machine?? You might want to replace the old org.codehaus.mojo:jxr-maven-plugin with the newer org.apache.maven.plugins:maven-jxr-plugin. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/site-deploy-not-copying-Java-Docs-tf2628872s177.html#a7352031 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: site-deploy and webdav
You'll need to add two pieces to your POM to get it to work. 1. Add the webdav extension to the build element. Something like this: build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId /extension /extensions ... /build 2. Put dav: in front of all URLs that you want deployed via WebDAV. So, instead of http://webdavserver/folder; you would use dav:http://webdavserver/folder;. -Nathan -Original Message- From: juergen.schumacher [mailto:[EMAIL PROTECTED] Sent: Monday, August 14, 2006 5:55 AM To: users@maven.apache.org Subject: site-deploy and webdav Hi, for site-deploy I would like to use webdav because my webserver running on windows and I found the ssh rather complicated on windows. On one post here I found webdav is also supported by the site-deploy plugin. But how can I set this up in the POM.XML ?? Using http://webdavserver/folder shows an error, using file:webdavserver/project show a successful build but no files are copied. Thank you for any help and have a nice day, juergen -- View this message in context: http://www.nabble.com/site-deploy-and-webdav-tf2102662.html#a5794662 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site-deploy problem with Windows shared directory
try to set your url to file:///\\hostname/ On 6/23/06, Gray, Jonathan [EMAIL PROTECTED] wrote: Hi All, I'm currently having a problem deploying the site for a multi-module project to a windows shared directory. The share is specified in the parent POM as follows: distributionManagement site idproject/id urlfile:/hostname-on-network/shared-directory//url /site /distributionManagement The generated site for the parent project deploys fine. However, when it comes to the child modules, the site logs that it is trying to deploy to, for example: [site:deploy] file:///hostname-on-network/shared-directory/module-name/ However, 'module-name' directory is never created and the contents never copied. I have tried creating the 'module-name' directory manually but no contents are copied. The unusual thing is that multi-module project sites work perfectly if the file URL is local. Can anyone help with this problem? Regards, Jon --- Jon This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site deploy in ASF help one project to another
Thanks a bunch, working nicely for us! :-) Carlos Sanchez wrote: Check site inside distributionManagement here http://svn.apache.org/viewcvs.cgi/maven/components/trunk/pom.xml?rev=382904view=markup That's how we publish it There's an option to deploy to Subversion in development, it's working for me. Docs are at http://maven.apache.org/wagon/ref/1.0-alpha-7-SNAPSHOT/wagon-providers/wagon-scm/ On 3/8/06, rick rineholt [EMAIL PROTECTED] wrote: Hello Maven developers, We're in the beginning stages with our Tuscany site and we are using Maven 2.x. Currently our site is generated (mvn site) and then both the src and target/site is checked in to subversion. It seems we then need to logon to the apache site machine and do svn update. This seems a little less than optimal considering especially that maven site has a deploy ( I think it scp which I'm not too familiar with) Is ASF set up to handle this ? Is there a better way to manage this? This may be a little of topic for this group but googling and searching the mailing achieves has left me with no hints. So I figured you are the experts :-) Any advise how to handle this would be appreciated .. thanks. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : Site deploy in ASF help one project to another
Great feature. Deploying artifact with wagon-scm will be supported too ? - Olivier -Message d'origine- De : rick rineholt [mailto:[EMAIL PROTECTED] Envoyé : jeudi 9 mars 2006 18:31 À : Maven Users List Objet : Re: Site deploy in ASF help one project to another Thanks a bunch, working nicely for us! :-) Carlos Sanchez wrote: Check site inside distributionManagement here http://svn.apache.org/viewcvs.cgi/maven/components/trunk/pom.xml?rev=382 904view=markup That's how we publish it There's an option to deploy to Subversion in development, it's working for me. Docs are at http://maven.apache.org/wagon/ref/1.0-alpha-7-SNAPSHOT/wagon-providers/w agon-scm/ On 3/8/06, rick rineholt [EMAIL PROTECTED] wrote: Hello Maven developers, We're in the beginning stages with our Tuscany site and we are using Maven 2.x. Currently our site is generated (mvn site) and then both the src and target/site is checked in to subversion. It seems we then need to logon to the apache site machine and do svn update. This seems a little less than optimal considering especially that maven site has a deploy ( I think it scp which I'm not too familiar with) Is ASF set up to handle this ? Is there a better way to manage this? This may be a little of topic for this group but googling and searching the mailing achieves has left me with no hints. So I figured you are the experts :-) Any advise how to handle this would be appreciated .. thanks. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ** Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site deploy in ASF help one project to another
what? deploying to svn or to minoutaur ssh server? On 3/9/06, rick rineholt [EMAIL PROTECTED] wrote: Thanks a bunch, working nicely for us! :-) Carlos Sanchez wrote: Check site inside distributionManagement here http://svn.apache.org/viewcvs.cgi/maven/components/trunk/pom.xml?rev=382904view=markup That's how we publish it There's an option to deploy to Subversion in development, it's working for me. Docs are at http://maven.apache.org/wagon/ref/1.0-alpha-7-SNAPSHOT/wagon-providers/wagon-scm/ On 3/8/06, rick rineholt [EMAIL PROTECTED] wrote: Hello Maven developers, We're in the beginning stages with our Tuscany site and we are using Maven 2.x. Currently our site is generated (mvn site) and then both the src and target/site is checked in to subversion. It seems we then need to logon to the apache site machine and do svn update. This seems a little less than optimal considering especially that maven site has a deploy ( I think it scp which I'm not too familiar with) Is ASF set up to handle this ? Is there a better way to manage this? This may be a little of topic for this group but googling and searching the mailing achieves has left me with no hints. So I figured you are the experts :-) Any advise how to handle this would be appreciated .. thanks. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : Site deploy in ASF help one project to another
that's the next step. It should work already but haven't tried On 3/9/06, Olivier Lamy [EMAIL PROTECTED] wrote: Great feature. Deploying artifact with wagon-scm will be supported too ? - Olivier -Message d'origine- De : rick rineholt [mailto:[EMAIL PROTECTED] Envoyé : jeudi 9 mars 2006 18:31 À : Maven Users List Objet : Re: Site deploy in ASF help one project to another Thanks a bunch, working nicely for us! :-) Carlos Sanchez wrote: Check site inside distributionManagement here http://svn.apache.org/viewcvs.cgi/maven/components/trunk/pom.xml?rev=382 904view=markup That's how we publish it There's an option to deploy to Subversion in development, it's working for me. Docs are at http://maven.apache.org/wagon/ref/1.0-alpha-7-SNAPSHOT/wagon-providers/w agon-scm/ On 3/8/06, rick rineholt [EMAIL PROTECTED] wrote: Hello Maven developers, We're in the beginning stages with our Tuscany site and we are using Maven 2.x. Currently our site is generated (mvn site) and then both the src and target/site is checked in to subversion. It seems we then need to logon to the apache site machine and do svn update. This seems a little less than optimal considering especially that maven site has a deploy ( I think it scp which I'm not too familiar with) Is ASF set up to handle this ? Is there a better way to manage this? This may be a little of topic for this group but googling and searching the mailing achieves has left me with no hints. So I figured you are the experts :-) Any advise how to handle this would be appreciated .. thanks. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ** Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site deploy in ASF help one project to another
Check site inside distributionManagement here http://svn.apache.org/viewcvs.cgi/maven/components/trunk/pom.xml?rev=382904view=markup That's how we publish it There's an option to deploy to Subversion in development, it's working for me. Docs are at http://maven.apache.org/wagon/ref/1.0-alpha-7-SNAPSHOT/wagon-providers/wagon-scm/ On 3/8/06, rick rineholt [EMAIL PROTECTED] wrote: Hello Maven developers, We're in the beginning stages with our Tuscany site and we are using Maven 2.x. Currently our site is generated (mvn site) and then both the src and target/site is checked in to subversion. It seems we then need to logon to the apache site machine and do svn update. This seems a little less than optimal considering especially that maven site has a deploy ( I think it scp which I'm not too familiar with) Is ASF set up to handle this ? Is there a better way to manage this? This may be a little of topic for this group but googling and searching the mailing achieves has left me with no hints. So I figured you are the experts :-) Any advise how to handle this would be appreciated .. thanks. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site deploy fails with m2.0.2: any easy workaround?
Hi Nicolas, You can generate the site for a project even if you don't have any file related to the site (site.xml, Xdoc, apt, fml, ...). As for your error when you try to deploy, this is probably because you didn't define the credentials for repository in your settings.xml. If you try to deploy via scp, you need to have something in your settings.xml file that looks like: (cf. http://maven.apache.org/guides/mini/guide-deployment-security-settings.html) settings . . servers server idrepo1/id usernamerepouser/username !-- other optional elements: passwordmy_login_password/password privateKey/path/to/identity/privateKey (default is ~/.ssh/id_dsa) passphrasemy_key_passphrase/passphrase -- /server /servers . . /settings You can also deploy via the file protocol. In this case, you would have in your POM something like: distributionManagement site iddeployFolder/id urlfile:///foo/myWebFolder//url /site /distributionManagement More generally, you'll find almost all you need at : http://maven.apache.org/guides/index.html Hope this helps, Best Regards / Cordialement, Fabrice BELLINGARD DINQ/DSIN/INSI/EATE/IDVS/AIDV (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] Nicolas Gonzalez nicogonzalez200 [EMAIL PROTECTED] Pour Maven Users List 15/02/2006 15:49 users@maven.apache.org cc VeuillezObjet répondre à Re: Site deploy fails with m2.0.2: Maven Users List any easy workaround? [EMAIL PROTECTED] che.org Hi Fabrice, I've been reading the maven site mini guide but i cant't find out where to configure the user, password and that sort of stuffs. The only thing i've done is to add distributionManagement/ in pom.xml but i get this exception when invoking mvn site:deploy = Session error: com.jcraft.jsch.JSchException: Session.connect: java.net.ConnectException: Connectio n refused: connect Is it necessary to create site.xml? if so, am i responsible for creating the tree directory explained at: http://maven.apache.org/guides/mini/guide-site.html ??? I really appreciate your help but i can't figure out what to do... Regards, Nicolas Gonzalez Buenos Aires - Argentina ___ 1GB gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo.yahoo.com.ar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site deploy fails with m2.0.2: any easy workaround?
Theres a patched jar file available on the jira page. Use it to replace the wagon-file jar in your MAVEN_HOME lib directory and you should be fine. This worked fine for me anyway. :-) [EMAIL PROTECTED] wrote: Hi guys, I'm trying to deploy the generated site with maven 2.0.2 and the site plugin 2.0-beta-4, and I get the following error, which some of you already experienced: Embedded error: Could not make directory '/users2/jip00/jip01/root/.'. The bug is known (http://jira.codehaus.org/browse/WAGON-30) and seems to be fixed in SVN. However, is there an _easy_ workaround to make site:deploy work while waiting for the next release? (I tried Brett's workaround - i.e. delete everything before deploying, but it still breaks when Maven tries to create the directory.) If not, this will prevent me from using Maven 2.0.2, which is annoying because 2.0.3 does not seem to be ready any time soon... Best Regards / Cordialement, Fabrice BELLINGARD DINQ/DSIN/INSI/EATE/IDVS/AIDV (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Tim Davies Analyst Developer KTS PLC: Service you can bank on 8th Floor, Finsbury Tower, 103-105 Bunhill Row, London EC1Y 8LZ tel: +44 (0)20 7256 2300 fax: +44 (0)20 7256 2301 email: [EMAIL PROTECTED] web: http://www.ktsplc.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site deploy fails with m2.0.2: any easy workaround?
I'm having a problem with maven site-deploy: the fact is that i don't know how to use it and how to configure it. Could you sen me your pom as an example? Thanks in advance Nicolas Gonzalez Buenos Aires - Argentina P.S.: Sorry for my english!! ___ 1GB gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo.yahoo.com.ar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site deploy fails with m2.0.2: any easy workaround?
Hi Nicolas, Here's what you've always dreamt to learn about the site plugin: http://maven.apache.org/guides/mini/guide-site.html Especially, look at section Deploying the site for your problem. HTH, Best Regards / Cordialement, Fabrice BELLINGARD DINQ/DSIN/INSI/EATE/IDVS/AIDV (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] Nicolas Gonzalez nicogonzalez200 [EMAIL PROTECTED] Pour Maven Users List 15/02/2006 16:11 users@maven.apache.org cc VeuillezObjet répondre à Re: Site deploy fails with m2.0.2: Maven Users List any easy workaround? [EMAIL PROTECTED] che.org I'm having a problem with maven site-deploy: the fact is that i don't know how to use it and how to configure it. Could you sen me your pom as an example? Thanks in advance Nicolas Gonzalez Buenos Aires - Argentina P.S.: Sorry for my english!! ___ 1GB gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo.yahoo.com.ar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site deploy fails with m2.0.2: any easy workaround?
Hi Fabrice, I've been reading the maven site mini guide but i cant't find out where to configure the user, password and that sort of stuffs. The only thing i've done is to add distributionManagement/ in pom.xml but i get this exception when invoking mvn site:deploy = Session error: com.jcraft.jsch.JSchException: Session.connect: java.net.ConnectException: Connectio n refused: connect Is it necessary to create site.xml? if so, am i responsible for creating the tree directory explained at: http://maven.apache.org/guides/mini/guide-site.html ??? I really appreciate your help but i can't figure out what to do... Regards, Nicolas Gonzalez Buenos Aires - Argentina ___ 1GB gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo.yahoo.com.ar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: site deploy hangs on large files
Yes but I can't find the JIRA issue right now. Essentially there's no workaround. You need to use a different provider. Wagon unzips the files but does not use unzip -q so the process output buffer fills up and blocks. We use the file protocol so our build machine publishes locally to the Apache HTML document root. -Original Message- From: Shukla, Sanjay [mailto:[EMAIL PROTECTED] Sent: Monday, February 13, 2006 11:30 AM To: Maven Users List Subject: site deploy hangs on large files I tried sftp and scp, site deploy will hang forever for large site deploys. Is this a known issue ? ## Transfer finished. 1038911 bytes copied in 3.807 seconds Executing command: cd /web/sites/mhhe.com/home/m2sites/rms/rmsws/.; unzip -o wagon24200.zip; rm -f wagon24200.zip Wait here forever . Sanjay Shukla, HPI Product Engineering, 2 Penn Plaza, NY. 212 904 3629 Office 732 692 4419 Cell - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site-deploy or wagon hanging (Maven 2.0.2, Red Hat and SuSe)
Hi, The site:deploy hang situation has been fixed and will be released in maven 2.0.3. See http://jira.codehaus.org/browse/MNG-1938 and http://jira.codehaus.org/browse/WAGONSSH-36 Ørjan Johnson, Jonathan wrote: Hi all, Is anyone aware that the following command mvn clean install deploy site-deploy will hang when site-deploy executes the following rm command command: cd /home/builder/454/deploy/site/common/.; unzip -o wagon47499.zip; rm -f wagon47499.zip I'm using Maven 2.0.2, Red Hat 4. Arnaud Bally reported the same using Maven 2.0.2, SuSe 9.2. The threads below are from our discussions in the Continuum group. We determined this is NOT a Continuum problem, rather is appears to be consistently stemming from the site-deploy plugin. -Original Message- From: Michael Böckling [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 07, 2006 5:05 AM To: continuum-users@maven.apache.org Subject: Re: Continuum and site-deploy or wagon hanging Nope, I experienced the exact same problem. Here it happens on a SuSe 9.2 with Maven 2.0.2 (and also in Continuum, of course). I had the impression that this does not affect small sites, but only large ones with many reports and all. It seems the site *does* get deployed correctly, but it hangs at very same line (wagon47499.zip; rm -f wagon47499.zip) when trying to delete the temporary upload file. Can't be a problem with permissions, since it only happens now and then. Defining a timeout is really essential, since it hangs forever once it gets stuck. Regards, Michael Hmm, all problems were fixed in wagon for maven 2.0.2. If you have pb with this version, send a message to maven user list. Emmanuel Arnaud Bailly a écrit : Hi, We are experiencing same problem : wagon hangs on ssh deploy and site-deploy in a random way. Sometimes it works, sometimes it doesn't. This has nothing to do with continuum as the problem occurs in maven direct invocations. Solutions are of course welcomed, I was not able to trace the cause of this problem (files permissions ok, ssh auth ok). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site deploy exclude directory
Lets have a look at this http://www.mail-archive.com/users@maven.apache.org/msg16791.html Cheers, Vincent On Tue, 15 Mar 2005 09:50:46 -0500, Howard Lin [EMAIL PROTECTED] wrote: Hi, I'm wondering if it's possible to exclude certain directories inside xdocs when doing site:deploy. (I don't find a property, like maven.site.deploy.exclude, which may be for this purpose.) Thanks, Howard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[SOLVED User error]Re: Site deploy fs.
Sorry, not a maven thing a permissions thing. c. Chris Huisman wrote: I am trying to deploy my generated site to a local directory but I'm having problems. My site directory in project.xml is: siteDirectory/var/www/html/QS/projects/primerib//siteDirectory The only site property I have is: maven.site.deploy.method=fs The error I get is: [java] site:init: [java] [java] site:fsdeploy: [java] [echo] [java] siteAddress = cooper [java] siteDirectory = /var/www/html/QS/projects/primerib/ [java] [java] [copy] Copying 677 files to /var/www/html/QS/projects/primerib [java] [java] BUILD FAILED [java] File.. /home/devel/.maven/cache/maven-site-plugin-1.5.2/plugin.jelly [java] Element... copy [java] Line.. 169 [java] Column 40 [java] Failed to copy /home/devel/build/checkout/primerib/target/docs/apidocs/com/taylor/qseries/client/framework/model/class-use/Machine.html to /var/www/html/QS/projects/primerib/apidocs/com/taylor/qseries/client/framework/model/class-use/Machine.html due to /var/www/html/QS/projects/primerib/apidocs/com/taylor/qseries/client/framework/model/class-use/Machine.html (No such file or directory) So I guess my question is, does site:fsdeploy make the necessary directories? Or is there another reason why this isn't working? Thanks, c. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
