OK the setup was write, there seems to be something that is different from
2.0.2 and 2.0.4.
I switched to 2.0.4 and it worked, with no changes to the pom.

Thanks anyway!


On 5/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

 Has the site:stage been removed?

mvn site:stage -DstagingDirectory=/usr2/local/WWW/

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'site'.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Required goal not found: site:stage
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Tue May 02 14:18:09 CDT 2006
[INFO] Final Memory: 2M/126M
[INFO]
------------------------------------------------------------------------



 On 5/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>  When I tried the file:/// I get this error. Is there something else
> that needs to be setup to use the file:/// command? I opened the
> directory up fully, I am not sure what else to check. What do you have for
> the file:///  syntax.
>
> in my pom, I have:
>  <distributionManagement>
>   <site>
>     <id>website</id>
> <url>file:///usr2/local/WWW</url>
>   </site>
> </distributionManagement>
>
>
>
> >mvn -e site:deploy
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'site'.
> [INFO]
> ----------------------------------------------------------------------------
>
> [INFO] Building Unnamed -
> com.weenergies.csstech.app.servlet:EclipseMigView:war:1.0-SNAPSHOT
> [INFO]    task-segment: [site:deploy]
> [INFO]
> ----------------------------------------------------------------------------
>
> [INFO] [site:deploy]
> file:///usr2/local/WWW - Session: Opened
> file:///usr2/local/WWW - Session: Disconnecting
> file:///usr2/local/WWW - Session: Disconnected
>
> [INFO]
> ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------------
>
> [INFO] Error uploading site
>
> Embedded error: Could not make directory '/usr2/local/WWW/.'.
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException : Error uploading
> site
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:556)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
> DefaultLifecycleExecutor.java:485)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:455)
>         at
> 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
> DefaultLifecycleExecutor.java:303)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:270)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (
> DefaultLifecycleExecutor.java:139)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java
> :322)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>         at org.apache.maven.cli.MavenCli.main (MavenCli.java:249)
>         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:585)
>         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:142)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> DefaultPluginManager.java:415)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:531)
>         ... 16 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Could not
> make directory '/usr2/local/WWW/.'.
>         at org.apache.maven.wagon.providers.file.FileWagon.putDirectory(
> FileWagon.java:113)
>         at org.apache.maven.plugins.site.SiteDeployMojo.execute(
> SiteDeployMojo.java:134)
>         ... 18 more
> [INFO]
> ----------------------------------------------------------------------------
>
> [INFO] Total time: 3 seconds
> [INFO] Finished at: Tue May 02 13:46:37 CDT 2006
> [INFO] Final Memory: 3M/126M
> [INFO]
> ----------------------------------------------------------------------------
>
> Thanks
>
>
>
> On 5/1/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:
> >
> > file://* works just fine. I'm using that right now.
> >
> > Just remember to add an extra slash to indicate it is on the same
> > machine
> > (i.e. file:/// instead of file://)
> >
> > -j
> >
> > ---------------------------------------------------
> > Justin Fung
> > [EMAIL PROTECTED]
> > Sr. Analyst, Business Systems
> > IT Banking Systems, e-Business
> > HSBC Bank Canada
> > http://www.hsbc.ca
> > p: (604) 643-6605
> > f: (604) 643-6727
> >
> >
> >
> >
> >
> >
> >
> >
> > [EMAIL PROTECTED]
> > 05/01/2006 01:41 PM
> > Please respond to "Maven Users List"
> >
> >
> >        To:     "Maven Users List" < users@maven.apache.org>
> >        cc:
> >        Subject:        Re: deploying site generated files
> >
> >      Our Ref:
> >            Your Ref:
> >
> >
> > Can I do a site:deploy with *file://* instead of the *scp://* ? What
> > is
> > the
> > syntax for the file protocol?
> >
> > The build sever is the same as the jboss server.
> >
> > THanks
> >
> >
> > On 5/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > >
> > >  I changed the path, so now I get a little different error. I there
> > a
> > way
> > > to run this without having to type in password every time.
> > >
> > > scp://jstage.com/usr2/local/WWW/ - Session: Opened
> > > Executing command: mkdir -p /usr2/local/WWW/.
> > > Executing command: mkdir -p /usr2/local/WWW/.
> > > Executing command: scp -t /usr2/local/WWW/./wagon30313.zip
> > > scp://jstage.com/usr2/local/WWW/ - Session: Disconnecting
> > > scp://jstage.com/usr2/local/WWW/ - Session: Disconnected
> > >
> > > [INFO]
> > >
> >
> > ----------------------------------------------------------------------------
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> >
> > ----------------------------------------------------------------------------
> > >
> > > [INFO] Error uploading site
> > >
> > > Embedded error: Unexpected end of data
> > >
> > >
> > > Thanks
> > >
> > >
> > >  On 5/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > >
> > > >  I have a jboss server, where exactly are we adding the path, on
> > the
> > > > server?
> > > >
> > > > So after the manual login ssh. Now I get this error:
> > > >
> > > > scp://jstage.com/WWW/ - Session: Opened
> > > > Executing command: mkdir -p /WWW/.
> > > > scp://jstage.com/WWW/ - Session: Disconnecting
> > > > scp://jstage.com/WWW/ - Session: Disconnected
> > > >
> > > > [INFO]
> > > >
> >
> > ----------------------------------------------------------------------------
> > > >
> > > > [ERROR] BUILD ERROR
> > > > [INFO]
> > > >
> >
> > ----------------------------------------------------------------------------
> > > >
> > > > [INFO] Error uploading site
> > > >
> > > > Embedded error: Error performing commands for file transfer
> > > > Exit code: 2 - mkdir: "/WWW/.": Permission denied
> > > >
> > > > Thanks
> > > >
> > > >  On 5/1/06, Wayne Fay < [EMAIL PROTECTED]> wrote:
> > > > >
> > > > > Manually SSH to the box and "permanently accept" the key for
> > this
> > > > > host. Then it shouldn't prompt for "continue connecting" when
> > you
> > run
> > > > > site:deploy later.
> > > > >
> > > > > Wayne
> > > > >
> > > > > On 5/1/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:
> > > > > > I made some changes to the pom, but now I can not continue to
> > > > > connect.
> > > > > > "scp://JSTAGE.com/WWW/" changed in my pom.xml
> > > > > >
> > > > > >
> > > > > > [INFO] Cobertura Report generation was successful.
> > > > > > [INFO] Generate "CPD Report" report.
> > > > > > [ERROR] VM #displayTree: error : too few arguments to macro.
> > Wanted
> > > > > 2 got 0
> > > > > > [ERROR] VM #menuItem: error : too few arguments to macro.
> > Wanted 1
> > > > > got 0
> > > > > > [INFO] Generate "PMD Report" report.
> > > > > > [INFO] Generate "Continuous Integration" report.
> > > > > > [INFO] Generate "Dependencies" report.
> > > > > > [INFO] Generate "Issue Tracking" report.
> > > > > > [INFO] Generate "Project License" report.
> > > > > > [INFO] Generate "Mailing Lists" report.
> > > > > > [INFO] Generate "Source Repository" report.
> > > > > > [INFO] Generate "Project Team" report.
> > > > > > [INFO] Generate an index file for the English version.
> > > > > > [INFO] [site:deploy]
> > > > > > The authenticity of host ' JSTAGE.com' can't be established.
> > > > > > DSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
> > > > > > Are you sure you want to continue connecting? (yes/no):
> > > > > >
> > > > > >
> > > > > > I am now stuck in this loop. Yes or No will not break the
> > loop.
> > > > > >
> > > > > > Is there something I can check for ssh to verify a correct
> > setup?
> > > > > >
> > > > > > THanks
> > > > > >
> > > > > > On 5/1/06, [EMAIL PROTECTED] <
> > [EMAIL PROTECTED] >
> > > > > wrote:
> > > > > > >
> > > > > > > If SSH/SCP is connecting to port 8080 it is probably
> > connecting
> > to
> > > > > an HTTP
> > > > > > > server (Tomcat?), and not an SSH service.  If that is the
> > case,
> > > > > that would
> > > > > > > explain the "invalid server's version string".  I believe
> > the
> > > > > default SSH
> > > > > > > port is 21.
> > > > > > >
> > > > > > > It's better to be hated for who you are
> > > > > > > than loved for who you are not
> > > > > > >
> > > > > > > Ian D. Stewart
> > > > > > > Appl Dev Analyst-Advisory, DCS Automation
> > > > > > > JPMorganChase Global Technology Infrastructure
> > > > > > > Phone: (614) 244-2564
> > > > > > > Pager: (888) 260-0078
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >                      "Wayne Fay"
> > > > > > >                      < [EMAIL PROTECTED]        To:
> > "Maven
> > > > > Users List"
> > > > > > > < users@maven.apache.org >
> > > > > > >                      om>                      cc:
> > > > > > >                                               Subject:  Re:
> > > > > deploying site
> > > > > > > generated files
> > > > > > >                      04/28/2006 05:45
> > > > > > >                      PM
> > > > > > >                      Please respond to
> > > > > > >                      "Maven Users
> > > > > > >                      List"
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > The SCP error message "invalid server's version string"
> > seems to
> > > > > > > indicate that SSH was unable to connect to the SSH server,
> > or
> > > > > there
> > > > > > > was something wrong during the SSH handshake.
> > > > > > >
> > > > > > > SCP is "Secure CoPy" which requires SSH to be installed on
> > the
> > > > > server.
> > > > > > > If you don't have it installed already, you'll need to
> > install
> > it
> > > > > > > before proceeding.
> > > > > > >
> > > > > > > And as Justin noticed, you have configured SCP to connect to
> >
> > port
> > > > > 8080
> > > > > > > which is most likely invalid.
> > > > > > >
> > > > > > > Wayne
> > > > > > >
> > > > > > > On 4/28/06, Edelson, Justin < [EMAIL PROTECTED]>
> > wrote:
> > > > > > > > Just a guess, but 8080 is probably the web server port,
> > not
> > the
> > > > > SSH/SCP
> > > > > > > > port, which is 22 by default.
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]
> > > > > > > > Sent: Friday, April 28, 2006 5:36 PM
> > > > > > > > To: Maven Users List
> > > > > > > > Subject: deploying site generated files
> > > > > > > >
> > > > > > > > I would like to move or deploy the site generated file to
> > my
> > web
> > > > > server
> > > > > > > > (JBoss) that is on the same server as my build (mvn)
> > server.
> > > > > > > >
> > > > > > > > I would like to allow others to view the site files from
> > the
> > web
> > > > > server.
> > > > > > > >
> > > > > > > > Can this be done?
> > > > > > > >
> > > > > > > > I have tried the <url>scp.........<url>
> > > > > > > >
> > > > > > > > I get an error...:
> > > > > > > >
> > > > > > > >
> > > > > > > > [INFO] [site:deploy]
> > > > > > > >  Session error: com.jcraft.jsch.JSchException: invalid
> > server's
> > > > > version
> > > > > > > > string
> > > > > > > > scp://JSTAGE.com:8080/WWW/ - Session: Disconnecting
> > > > > > > > scp://JSTAGE.com:8080/WWW/ - Session: Disconnected
> > > > > > > > [INFO]
> > > > > > > >
> > > > >
> >
> > ------------------------------------------------------------------------
> > > > > > > > ----
> > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > [INFO]
> > > > > > > >
> > > > >
> >
> > ------------------------------------------------------------------------
> > > > > > > > ----
> > > > > > > > [INFO] Error uploading site
> > > > > > > >
> > > > > > > > Embedded error: Cannot connect. Reason: invalid server's
> > version
> > > > > string
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > In my pom:
> > > > > > > >
> > > > > > > > <distributionManagement>
> > > > > > > >  <site>
> > > > > > > >    <id>website</id>
> > > > > > > > <url>scp://JSTAGE.com:8080/WWW/</url>
> > > > > > > >
> > > > > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > > > > 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]
> >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
> >
> > ***************************************************************
> > This email may contain confidential information, and is intended only
> > for
> > the named recipient and may be privileged.  Distribution or copying of
> > this email by anyone other than the named recipient is prohibited. If
> > you
> > are not the named recipient, please notify us immediately and
> > permanently
> > destroy this email and all copies of it.  Internet email is not
> > private,
> > secure, or reliable.  No member of the HSBC Group is liable for any
> > errors
> > or omissions in the content or transmission of this email. Any
> > opinions
> > contained in this email are solely those of the author and, unless
> > clearly
> > indicated otherwise in writing, are not endorsed by any member of the
> > HSBC
> > Group.
> > ***************************************************************
> > Ce courriel peut renfermer des renseignements confidentiels et
> > privilégiés
> > et s'adresse au destinataire désigné seulement.   La distribution ou
> > la
> > copie de ce courriel par toute personne autre que le destinataire
> > désigné
> > est interdite.  Si vous n'êtes pas le destinataire désigné, veuillez
> > nous
> > en aviser immédiatement et détruire de façon permanente ce courriel
> > ainsi
> > que toute copie de celui-ci. La transmission de courriel par Internet
> > ne
> > constitue pas un mode de transmission confidentiel, sécuritaire ou
> > fiable.
> > Aucun membre du Groupe HSBC ne sera responsable des erreurs ou des
> > omissions relatives au contenu ou à la transmission de ce courriel.
> > L'auteur de ce courriel est seul responsable des opinions émises dans
> > ce
> > courriel, lesquelles, à moins  d'un avis contraire fourni par écrit,
> > ne
> > sont pas endossées par aucun membre du Groupe HSBC.
> > ***************************************************************
> >
> >
>

Reply via email to