Re: Reporting in maven. help please

2020-11-29 Thread Bernd Eckenfels
Hello,

There are a number of static code analyses which also happen to have a maven 
plugin (with sire reporting integration), for example pmd, findbugs/spotbugs, 
checker framework, checkstyle, (static-Code-analysis) Javancss, taglist, l10n 
status, jdepend and dependency-Check, and a few external tools with maven 
integration like sonarqube, lgtm or Snyk, see also here 
https://maven.apache.org/code-quality-management.html

Most of those plugins are best used when you have a matching CI plugin to 
record long term trends or if they have their own database (like sonarqube).

Gruss
Bernd
--
http://bernd.eckenfels.net

Von: Aitor Iturriondobeitia 
Gesendet: Sunday, November 29, 2020 6:47:13 PM
An: Maven Users List 
Betreff: Reporting in maven. help please

Hello
i am new using maven and i am reading documentation.
Can you say me which plugins can i use for reporting the code quality?
any example?
thanks


Re: Reporting in maven. help please

2020-11-29 Thread John Patrick
Is this the documentation you said you are reading
https://maven.apache.org/plugins/index.html, as it has a reporting
section for maven maintained plugins.

but to highlight some, take a look at;
checkstyle https://maven.apache.org/plugins/maven-checkstyle-plugin/
pmd/cpd https://maven.apache.org/plugins/maven-pmd-plugin/
spotbugs (was findbugs) https://spotbugs.github.io/spotbugs-maven-plugin/

harder setup as requires installing separate tooling, and most overlap
with checkstyle, pmd and sportbugs in the free version.
sonarqube 
https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-maven/

for your dependencies look at owasp and
https://jeremylong.github.io/DependencyCheck/dependency-check-maven/index.html

If you're on github or bitbucket and are an open source project then
they have lots of both apps or integration tooling that can check
dependencies, code coverage. But if it's a closed private repo then it
will cost you something $$$ per month.

John

On Sun, 29 Nov 2020 at 17:47, Aitor Iturriondobeitia
 wrote:
>
> Hello
> i am new using maven and i am reading documentation.
> Can you say me which plugins can i use for reporting the code quality?
> any example?
> thanks

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



Reporting in maven. help please

2020-11-29 Thread Aitor Iturriondobeitia
Hello
i am new using maven and i am reading documentation.
Can you say me which plugins can i use for reporting the code quality?
any example?
thanks


Re: Help[please]: maven-surefire-plugin with TestNG group dependencies not working....

2014-02-20 Thread Jeff
Anyone have similar issues running tests w/ group dependencies?


On Tue, Feb 18, 2014 at 5:52 PM, Jeff predato...@gmail.com wrote:

 I'm having a frustrating test dependency issue and I don't know if it is
 my configuration or a problem.  I've got two test classes in my maven
 project using testng:6.8.7 and maven-surefire-plugin:2.16.

 The first test class has the following annotation on the test *class* which
 should be inherited by the test methods:

 * @Test(groups={ functional })*
 *  public class FuncTest{...}*

 on the other test *class*, I have:

 * @Test(groups={ load }, dependsOnGroups = { functional })*
 *  public class LoadTest {...}*

 When I run the following:

  *mvn test*

 I get the error:

  *[ERROR] DependencyMap::Method LoadTest depends on nonexistent group
 functional*

 If I REMOVE the dependsOnGroups... it works.  If I do any of the
 following but keep the dependsOnGroups option:

 * mvn test -Dtest=LoadTest,FuncTest*
 * mvn test -Dgroups=functional,load*
 * mvn test -Dgroups=functional,load **-Dtest=LoadTest,FuncTest*

 it fails with the error above.  If I run it outside of Maven by calling
 org.testng.TestNG directly, it works fine.

 I also tried moving the group definitions/dependencies to the test method
 directly, but that didn't change.

 *What am I missing?  *

 Thanks!

 --
 Jeff Vincent
 See my LinkedIn profile at:
 http://www.linkedin.com/in/rjeffreyvincent




-- 
Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent


Help[please]: maven-surefire-plugin with TestNG group dependencies not working....

2014-02-18 Thread Jeff
I'm having a frustrating test dependency issue and I don't know if it is my
configuration or a problem.  I've got two test classes in my maven project
using testng:6.8.7 and maven-surefire-plugin:2.16.

The first test class has the following annotation on the test *class* which
should be inherited by the test methods:

* @Test(groups={ functional })*
*  public class FuncTest{...}*

on the other test *class*, I have:

* @Test(groups={ load }, dependsOnGroups = { functional })*
*  public class LoadTest {...}*

When I run the following:

 *mvn test*

I get the error:

 *[ERROR] DependencyMap::Method LoadTest depends on nonexistent group
functional*

If I REMOVE the dependsOnGroups... it works.  If I do any of the
following but keep the dependsOnGroups option:

* mvn test -Dtest=LoadTest,FuncTest*
* mvn test -Dgroups=functional,load*
* mvn test -Dgroups=functional,load **-Dtest=LoadTest,FuncTest*

it fails with the error above.  If I run it outside of Maven by calling
org.testng.TestNG directly, it works fine.

I also tried moving the group definitions/dependencies to the test method
directly, but that didn't change.

*What am I missing?  *

Thanks!

-- 
Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent


Re: maven jax-ws and jdk7. help please

2013-01-28 Thread Anders Hammar
Most likely due to different version of some framework (jaxb?) being used.

/Anders


On Mon, Jan 28, 2013 at 8:58 AM, laudio.info laudio.i...@gmail.com wrote:

 Thanks

 I have seen that, using the same java code and the same configuration, the
 problem appears if i use the jdk7. Using the jdk there is not problem


 2013/1/27 Wayne Fay wayne...@gmail.com

   Caused by: java.security.PrivilegedActionException:
   com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of
   IllegalAnnotationExceptions
   java.lang.StackTraceElement does not have a no-arg default constructor.
 
  This seems to be the root cause of your problem. I would start
  removing your Webservices one by one until you figure out which one is
  causing this error to be thrown. Then compare it to the others you are
  building with no issues.
 
  Also I'd take this question to a Java Webservices forum or mailing
  list, as this really has nothing to do with Maven.
 
  Wayne
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 



Re: maven jax-ws and jdk7. help please

2013-01-28 Thread Jörg Schaible
laudio.info wrote:

 Thanks
 
 I have seen that, using the same java code and the same configuration, the
 problem appears if i use the jdk7. Using the jdk there is not problem

The jaxws plugin does not respect the compiler settings for source/target. 
On top of it, the exception has additional info since JDK 7, so any code 
that uses reflection to map an exception class to something else, will be 
affected by the different Java runtime. AFAICS JAXB is such a tool.

Nothing of this has to do with Maven directly though.

- Jörg


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



AW: maven jax-ws and jdk7. help please

2013-01-28 Thread Stadelmann Josef
I fully support that! 
I had a nightmare with Axis2-1.6.2 and JDK1.6.0_30
when it comes to use jax-ws and jaxb with ALLOWED ANNOTATIONS;

Axis-1.6.2 has a jax-ws interface which knows about 4 args to some annotations,
so the compiler had absolute no problem. But then JDK 1.6.0_30 RT.jar has only 
an implementation for 3 args to be set on a annotation class, hence 
calling through the interface the 4 arg to be set, returnd a class not found 
exception.

The cure was to endorse from JDK 1.7 into JDK1.6.0_30/jre/lib/endorsed 
the proper jar files; This works now for us very well for Vista and OpenVMS

Josef 



-Ursprüngliche Nachricht-
Von: Jörg Schaible [mailto:joerg.schai...@scalaris.com] 
Gesendet: Montag, 28. Januar 2013 10:37
An: users@maven.apache.org
Betreff: Re: maven jax-ws and jdk7. help please

laudio.info wrote:

 Thanks
 
 I have seen that, using the same java code and the same configuration, 
 the problem appears if i use the jdk7. Using the jdk there is not 
 problem

The jaxws plugin does not respect the compiler settings for source/target. 
On top of it, the exception has additional info since JDK 7, so any code that 
uses reflection to map an exception class to something else, will be affected 
by the different Java runtime. AFAICS JAXB is such a tool.

Nothing of this has to do with Maven directly though.

- Jörg


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



Re: maven jax-ws and jdk7. help please

2013-01-27 Thread Wayne Fay
 Caused by: java.security.PrivilegedActionException:
 com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of
 IllegalAnnotationExceptions
 java.lang.StackTraceElement does not have a no-arg default constructor.

This seems to be the root cause of your problem. I would start
removing your Webservices one by one until you figure out which one is
causing this error to be thrown. Then compare it to the others you are
building with no issues.

Also I'd take this question to a Java Webservices forum or mailing
list, as this really has nothing to do with Maven.

Wayne

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



Re: maven jax-ws and jdk7. help please

2013-01-27 Thread laudio.info
Thanks

I have seen that, using the same java code and the same configuration, the
problem appears if i use the jdk7. Using the jdk there is not problem


2013/1/27 Wayne Fay wayne...@gmail.com

  Caused by: java.security.PrivilegedActionException:
  com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of
  IllegalAnnotationExceptions
  java.lang.StackTraceElement does not have a no-arg default constructor.

 This seems to be the root cause of your problem. I would start
 removing your Webservices one by one until you figure out which one is
 causing this error to be thrown. Then compare it to the others you are
 building with no issues.

 Also I'd take this question to a Java Webservices forum or mailing
 list, as this really has nothing to do with Maven.

 Wayne

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




New to maven and loving it :) Need a little help please...

2010-03-12 Thread Yucca Nel
Hello, google has helped me fantastically up to now and I am in a little need 
of further info.

I am in the process of changing my development environment (JEE5 + JEE6) and 
have started to utilise Maven. I am looking for a xml pom snippet that can help 
me deploy directly to Jboss6 or glassfish v3 when building my pom. If no 
solution exists, I am open to trying geronimo in the hope of better integration 
with maven.

Re: New to maven and loving it :) Need a little help please...

2010-03-12 Thread Anders Hammar
Try the cargo plugin or the jboss specific one:
http://cargo.codehaus.org/Maven2+plugin
http://mojo.codehaus.org/jboss-maven-plugin/

/Anders

On Fri, Mar 12, 2010 at 14:06, Yucca Nel yucca...@live.co.za wrote:

 Hello, google has helped me fantastically up to now and I am in a little
 need of further info.

 I am in the process of changing my development environment (JEE5 + JEE6)
 and have started to utilise Maven. I am looking for a xml pom snippet that
 can help me deploy directly to Jboss6 or glassfish v3 when building my pom.
 If no solution exists, I am open to trying geronimo in the hope of better
 integration with maven.


scm plugin help please

2009-02-20 Thread Mick Knutson
I am trying to use the scm plugin to perform an svn update. I can
successfully run svn cleanup, svn up, and svn ci from the command line. But
when I run a mvn scm:update -e I get an error saying my pom.xml is locked as
shown below:


*733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup

733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn up
At revision 5.*

*733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ mvn
scm:update -e*
*+ Error stacktraces are turned on.*
*[INFO] Scanning for projects...*
*[INFO] Searching repository for plugin with prefix: 'scm'.*
*WAGON_VERSION: 1.0-beta-2*
*[INFO]
*
*[INFO] Building FXG:: POM*
*[INFO]task-segment: [scm:update] (aggregator-style)*
*[INFO]
*
*[INFO] [scm:update]*
*[INFO] Executing: cmd.exe /X /C svn --non-interactive update
c:\opt\projects\grd\trunk\fxg-pom*
*[INFO] Working directory: c:\opt\projects\grd\trunk\fxg-pom*
*[INFO] Svn command failed due to some locks in working copy. We try to run
a 'svn cleanup'.*
*[INFO] Executing: cmd.exe /X /C svn*
*[INFO] Working directory: c:\opt\projects\grd\trunk\fxg-pom*
*[ERROR] Provider message:*
*[ERROR] The svn command failed.*
*[ERROR] Command output:*
*[ERROR] svn: Working copy 'c:\opt\projects\grd\trunk\fxg-pom' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
Type 'svn help' for usage.*

*[INFO]
*
*[ERROR] BUILD ERROR*
*[INFO]
*
*[INFO] Command failed.The svn command failed.*
*[INFO]
*
*[INFO] Trace*
*org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.The
svn command failed.*
*at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
*
*at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
*
*at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
*
*at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
*
*at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
*
*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: Command
failed.The svn command failed.*
*at
org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java:400)
*
*at
org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:93)*
*at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
*
*at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
*
*... 16 more*
*[INFO]
*
*[INFO] Total time: 7 seconds*
*[INFO] Finished at: Fri Feb 20 09:34:57 EST 2009*
*[INFO] Final Memory: 8M/16M*
*[INFO]
*

*733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $*


---
Thank You…

Mick Knutson, President

BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring  Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233

Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Twitter: http://twitter.com/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---


AW: scm plugin help please

2009-02-20 Thread Mark Struberg
may this be a reincarnation of the --non-interactive bug with svn-1.5 on MacOsX?

http://jira.codehaus.org/browse/SCM-402

what says svn if you execute the SVN command with and without the 
--non-interactive?

txs and LieGrue,
strub

--- Mick Knutson mickknut...@gmail.com schrieb am Fr, 20.2.2009:

 Von: Mick Knutson mickknut...@gmail.com
 Betreff: scm plugin help please
 An: maven users@maven.apache.org
 Datum: Freitag, 20. Februar 2009, 15:38
 I am trying to use the scm plugin to perform an svn update.
 I can
 successfully run svn cleanup, svn up, and svn ci from the
 command line. But
 when I run a mvn scm:update -e I get an error saying my
 pom.xml is locked as
 shown below:
 
 
 *733...@d5400lpl:
 /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup
 
 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom
 $ svn up
 At revision 5.*
 
 *733...@d5400lpl:
 /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ mvn
 scm:update -e*
 *+ Error stacktraces are turned on.*
 *[INFO] Scanning for projects...*
 *[INFO] Searching repository for plugin with prefix:
 'scm'.*
 *WAGON_VERSION: 1.0-beta-2*
 *[INFO]
 *
 *[INFO] Building FXG:: POM*
 *[INFO]task-segment: [scm:update] (aggregator-style)*
 *[INFO]
 *
 *[INFO] [scm:update]*
 *[INFO] Executing: cmd.exe /X /C svn
 --non-interactive update
 c:\opt\projects\grd\trunk\fxg-pom*
 *[INFO] Working directory:
 c:\opt\projects\grd\trunk\fxg-pom*
 *[INFO] Svn command failed due to some locks in working
 copy. We try to run
 a 'svn cleanup'.*
 *[INFO] Executing: cmd.exe /X /C svn*
 *[INFO] Working directory:
 c:\opt\projects\grd\trunk\fxg-pom*
 *[ERROR] Provider message:*
 *[ERROR] The svn command failed.*
 *[ERROR] Command output:*
 *[ERROR] svn: Working copy
 'c:\opt\projects\grd\trunk\fxg-pom'
 locked
 svn: run 'svn cleanup' to remove locks (type
 'svn help cleanup' for details)
 Type 'svn help' for usage.*
 
 *[INFO]
 *
 *[ERROR] BUILD ERROR*
 *[INFO]
 *
 *[INFO] Command failed.The svn command failed.*
 *[INFO]
 *
 *[INFO] Trace*
 *org.apache.maven.lifecycle.LifecycleExecutionException:
 Command failed.The
 svn command failed.*
 *at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
 *
 *at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
 *
 *at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
 *
 *at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
 *
 *at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
 *
 *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:
 Command
 failed.The svn command failed.*
 *at
 org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java:400)
 *
 *at
 org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:93)*
 *at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
 *
 *at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
 *
 *... 16 more*
 *[INFO]
 *
 *[INFO] Total time: 7 seconds*
 *[INFO] Finished at: Fri Feb 20 09:34:57 EST 2009*
 *[INFO] Final Memory: 8M/16M*
 *[INFO]
 *
 
 *733...@d5400lpl:
 /cygdrive/c/opt/projects/grd/trunk/fxg-pom $*
 
 
 ---
 Thank You…
 
 Mick Knutson

Re: scm plugin help please

2009-02-20 Thread Mick Knutson
Does not look like that is it:

733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $
733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $
733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ *svn
--non-interactive up
At revision 5.*
733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup
--non-interactive
733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $* svn up
At revision 5.*
733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup
733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $

---
Thank You…

Mick Knutson, President

BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring  Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233

Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Twitter: http://twitter.com/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---



On Fri, Feb 20, 2009 at 9:44 AM, Mark Struberg strub...@yahoo.de wrote:

 may this be a reincarnation of the --non-interactive bug with svn-1.5 on
 MacOsX?

 http://jira.codehaus.org/browse/SCM-402

 what says svn if you execute the SVN command with and without the
 --non-interactive?

 txs and LieGrue,
 strub

 --- Mick Knutson mickknut...@gmail.com schrieb am Fr, 20.2.2009:

  Von: Mick Knutson mickknut...@gmail.com
  Betreff: scm plugin help please
  An: maven users@maven.apache.org
  Datum: Freitag, 20. Februar 2009, 15:38
  I am trying to use the scm plugin to perform an svn update.
  I can
  successfully run svn cleanup, svn up, and svn ci from the
  command line. But
  when I run a mvn scm:update -e I get an error saying my
  pom.xml is locked as
  shown below:
 
 
  *733...@d5400lpl:
  /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup
 
  733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom
  $ svn up
  At revision 5.*
 
  *733...@d5400lpl:
  /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ mvn
  scm:update -e*
  *+ Error stacktraces are turned on.*
  *[INFO] Scanning for projects...*
  *[INFO] Searching repository for plugin with prefix:
  'scm'.*
  *WAGON_VERSION: 1.0-beta-2*
  *[INFO]
  *
  *[INFO] Building FXG:: POM*
  *[INFO]task-segment: [scm:update] (aggregator-style)*
  *[INFO]
  *
  *[INFO] [scm:update]*
  *[INFO] Executing: cmd.exe /X /C svn
  --non-interactive update
  c:\opt\projects\grd\trunk\fxg-pom*
  *[INFO] Working directory:
  c:\opt\projects\grd\trunk\fxg-pom*
  *[INFO] Svn command failed due to some locks in working
  copy. We try to run
  a 'svn cleanup'.*
  *[INFO] Executing: cmd.exe /X /C svn*
  *[INFO] Working directory:
  c:\opt\projects\grd\trunk\fxg-pom*
  *[ERROR] Provider message:*
  *[ERROR] The svn command failed.*
  *[ERROR] Command output:*
  *[ERROR] svn: Working copy
  'c:\opt\projects\grd\trunk\fxg-pom'
  locked
  svn: run 'svn cleanup' to remove locks (type
  'svn help cleanup' for details)
  Type 'svn help' for usage.*
 
  *[INFO]
  *
  *[ERROR] BUILD ERROR*
  *[INFO]
  *
  *[INFO] Command failed.The svn command failed.*
  *[INFO]
  *
  *[INFO] Trace*
  *org.apache.maven.lifecycle.LifecycleExecutionException:
  Command failed.The
  svn command failed.*
  *at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
  *
  *at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
  *
  *at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
  *
  *at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
  *
  *at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
  *
  *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

Re: [m2] issue activating profiles. NEED HELP PLEASE

2007-12-13 Thread Mick Knutson
So I keep getting:
[WARNING] Overriding profile: 'documentation' (source: pom) with new
instance from source: profiles.xml
[WARNING] Overriding profile: 'dev-' (source: pom) with new instance
from source: profiles.xml

I have tried with an without:
profile
iddev-/id
properties
envdev-/env
build.typeno-documentation/build.type
/properties
/profile

in my profiles.xml

Basically, I am trying to do the following 2 things:

1. I want to run with the properties I set in my properties section if
there is NOT a -P [profilename] specified:
properties
*envlocal/env
build.typeno-documentation/build.type*

2. If a profile is specified such as dev-, I want those settings to
override the properties settings:

profile
id*documentation*/id
properties
*build.typedocumentation/build.type*
/properties
/profile
profile
id*dev-*/id
properties
   * envdev-/env
build.typeno-documentation/build.type
*
Then, I have a module group that has to have an activation switch on
build.type like:

profile
id*documentation*/id
modules
modulebusiness-services/module
modulecommon-c2/module
/modules
/profile

profile
id*no-documentation*/id
activation
  property
*namebuild.type/name
value!documentation/value*
  /property
/activation
modules
*modulebpel/module*
modulebusiness-services/module
modulecommon-c2/module
/modules
/profile

The BPEL will fail the entire site:site process due to the nature of the
Oracle bpel ant tasks. No way around this so I just don't want to run them
if I plan to run site documentation.



So here is what is happening:

when I run *mvn package* or I run *mvn -P dev- package* I get
*dev-7778*used every time. It shows that ALL profiles are active, but
only takes the
last one which is dev-7778 not local or dev-

With this, no matter what, the* build.type* is never *documentation *as it
appears that dev-7778 overrides that property. so my site:site fails every
time. Even when I do a *mvn -P documentation site:site*






On Dec 11, 2007 1:55 PM, Mick Knutson [EMAIL PROTECTED] wrote:

 I keep getting this:


 The following profiles are active:

  - local (source: settings.xml)
  - local (source: settings.xml)
  - local (source: settings.xml)
  - dev- (source: *profiles*.xml)
  - documentation (source: *profiles*.xml)
  - dev-7778 (source: *profiles*.xml)



 Not all of these profiles have been activated. Only local is active by
 default. The other 3 profiles exist in profiles.xml , but have not been
 activated.






 On Dec 11, 2007 1:33 PM, Patrick Schneider [EMAIL PROTECTED] wrote:

  I haven't seen those warnings before...
 
  Have you tried using help:active-profiles?  Try:
 
  $ mvn -P dev- help:active-profiles
 
  This will list (surprise!) the currently active profiles with which
  Maven is
  executing.
 
 
  Patrick
 
  On Dec 11, 2007 12:43 PM, Mick Knutson [EMAIL PROTECTED] wrote:
 
   I am trying to switch profiles for each environment.
   I have dev-, and dev-7778
  
   Then in my profiles.xml I have:
  
   *profile
  iddev-/id
  properties
  envdev-/env
  build.typeno-documentation/build.type
  /properties
  /profile
  
  profile
  iddev-7778/id
  properties
  envdev-7778/env
  build.typeno-documentation/build.type
  /properties
  /profile*
  
  
   *When I run:*
   *mvn -P dev- assembly:assembly -e -X  .out.txt*
   *
   I keep getting this:*
  
   *[WARNING] Overriding profile: 'dev-' (source: pom) with new
  instance
   from source: profiles.xml
   [WARNING] Overriding profile: 'dev-7778' (source: pom) with new
  instance
   from source: profiles.xml*
  
  
   so it looks like I get both, but 7778 seems to always override . I
   only
   want one of these profiles active at the same time. Can someone please
   help
   me out?
  
  
   --
   Thanks,
   Mick Knutson
  
   http://www.baselogic.com
   http://www.blincmagazine.com
   http://www.djmick.com
   http://www.myspace.com/mickknutson
   http://www.myspace.com/BLiNCMagazine
   http://tahoe.baselogic.com
   ---
  
 



 --

 Thanks,
 Mick Knutson

 http://www.baselogic.com
 http://www.blincmagazine.com
 http://www.djmick.com
 http://www.myspace.com/mickknutson
 http://www.myspace.com/BLiNCMagazine
 http://tahoe.baselogic.com
 ---




-- 
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com

Re: Can't deploy site,Help please.

2007-02-07 Thread Markku Saarela

Hi,

You configure authentication in settings.xml.

Look here for details:  http://maven.apache.org/settings.html#Servers

rgds,

markku

jiangshachina wrote:

Hello,
I tried to deploy project via scp just now, but authentication failed.
How to set the user/password of remote machine in POM file?

a cup of Java, cheers!
Sha Jiang


Markku Saarela wrote:
  

One slash character was dropped out :-)
file:///192.1.1.0/temp/directory

- markku


Markku Saarela wrote:


Hi,

No, File protocol can deploy any directory in network where user has
access. The first slash character is defining that path is absolute two
others are some server delimiters.

file:/c:/temp vs. file:///someserver/depl or even
file://192.1.1.0/temp/directory

rgds,
markku

jiangshachina wrote:
  
  

Hello,
  



I have solved the issue by used file:///path/to/deployment/dir

  
  

file protocol just deploys to a local path, doesn't it?

a cup of Java, cheers!
Sha Jiang


秋秋 wrote:
  



Hi,
yes,I have solved the issue by used
file:///path/to/deployment/dir*, *
thanks.


2007/2/6, Tim Kettler [EMAIL PROTECTED]:

  
  

Hi,

the URL you give in the distribution management section is the HTTP
URL
of your projects site. To deploy it you need to specify a valid
deployment URL. This could be something like:

- scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
- sftp://my.server.com/deployment/dir (for SFTP deployment)
- file:///path/to/deployment/dir (for deploying to a local file
system)

Hope this helps
-Tim

Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
  



Hi,
I  use apache-tomcat-5.5.17 as a server for the project site,the

  
  

url
is
  



http://localhost:8080/pcie/, I have added the configuration in the
pom.xmllike this:
distributionManagement
  site
   idmaven/id
   urlscp://localhost:8080/pcie//url
  /site
 /distributionManagement

I have start up the server successfull as well as I Have execute
site
command,but when I execute site-deploy,I appear the error like
this:
FATAL ERROR: Error executing Maven for a project
org.apache.maven.lifecycle.LifecycleExecutionException: Error
uploading

  
  

site
  



 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:559)
 at


  
  

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
  



(DefaultLifecycleExecutor.java:475)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:454)
 at


  
  

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
  



(DefaultLifecycleExecutor.java:306)
 at

  
  

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
  



DefaultLifecycleExecutor.java:273)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:140)
 at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java

  
  

:441)
  



 at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java

  
  

:382)
  



 at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error

  
  

uploading
  



site
 at org.apache.maven.plugins.site.SiteDeployMojo.execute(

  
  

SiteDeployMojo.java
  



:184)
 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:412)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:534)
 ... 8 more
Caused by:

  
  

org.apache.maven.wagon.authentication.AuthenticationException
:
  



Cannot connect. Reason: invalid server's version string
 at

  
  

org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
(
  



AbstractSshWagon.java:239)
 at

  
  

org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
  



 at

  
  

org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
  



 at org.apache.maven.plugins.site.SiteDeployMojo.execute(

  
  

SiteDeployMojo.java
  



:153)
 ... 10 more
Caused by: com.jcraft.jsch.JSchException: invalid server's version

  
  

string
  

 

Re: Can't deploy site,Help please.

2007-02-07 Thread jiangshachina

Hello,
My local machine is Windows 2000, the remote machine is RedHat AS 4.0.

I set the following statements in my pom.xml,
distributionManagement
repository
idtest/id
urlscp://HostIP/Absolute_Path_To_Repo/url
/repository
/distributionManagement
and run command mvn deploy.
Maven indicated me to login remote machine via [EMAIL PROTECTED],
but there isn't the user in remote machine,
factly, Administrator is my current user in local machine.
Absolutely, the authentication would be failed.

a cup of Java, cheers!
Sha Jiang


jiangshachina wrote:
 
 Hello,
 I tried to deploy project via scp just now, but authentication failed.
 How to set the user/password of remote machine in POM file?
 
 a cup of Java, cheers!
 Sha Jiang
 
 
 Markku Saarela wrote:
 
 One slash character was dropped out :-)
 file:///192.1.1.0/temp/directory
 
 - markku
 
 
 Markku Saarela wrote:
 Hi,

 No, File protocol can deploy any directory in network where user has
 access. The first slash character is defining that path is absolute two
 others are some server delimiters.

 file:/c:/temp vs. file:///someserver/depl or even
 file://192.1.1.0/temp/directory

 rgds,
 markku

 jiangshachina wrote:
   
 Hello,
   
 
 I have solved the issue by used file:///path/to/deployment/dir
 
   
 file protocol just deploys to a local path, doesn't it?

 a cup of Java, cheers!
 Sha Jiang


 秋秋 wrote:
   
 
 Hi,
 yes,I have solved the issue by used
 file:///path/to/deployment/dir*, *
 thanks.


 2007/2/6, Tim Kettler [EMAIL PROTECTED]:
 
   
 Hi,

 the URL you give in the distribution management section is the HTTP
 URL
 of your projects site. To deploy it you need to specify a valid
 deployment URL. This could be something like:

 - scp://my.server.com/var/www/htdocs/myproject (for SSH's secure
 copy)
 - sftp://my.server.com/deployment/dir (for SFTP deployment)
 - file:///path/to/deployment/dir (for deploying to a local file
 system)

 Hope this helps
 -Tim

 Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
   
 
 Hi,
 I  use apache-tomcat-5.5.17 as a server for the project site,the
 
   
 url
 is
   
 
 http://localhost:8080/pcie/, I have added the configuration in the
 pom.xmllike this:
 distributionManagement
   site
idmaven/id
urlscp://localhost:8080/pcie//url
   /site
  /distributionManagement

 I have start up the server successfull as well as I Have execute
 site
 command,but when I execute site-deploy,I appear the error like
 this:
 FATAL ERROR: Error executing Maven for a project
 org.apache.maven.lifecycle.LifecycleExecutionException: Error
 uploading
 
   
 site
   
 
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:559)
  at

 
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
   
 
 (DefaultLifecycleExecutor.java:475)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
 DefaultLifecycleExecutor.java:454)
  at

 
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
   
 
 (DefaultLifecycleExecutor.java:306)
  at
 
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
   
 
 DefaultLifecycleExecutor.java:273)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
 DefaultLifecycleExecutor.java:140)
  at
 org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
   
 :441)
   
 
  at
 org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
   
 :382)
   
 
  at
 org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
 
   
 uploading
   
 
 site
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
   
 SiteDeployMojo.java
   
 
 :184)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:412)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:534)
  ... 8 more
 Caused by:
 
   
 org.apache.maven.wagon.authentication.AuthenticationException
 :
   
 
 Cannot connect. Reason: invalid server's version string
  at
 
   
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
   
 
 AbstractSshWagon.java:239)
  at
 
   
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
   
 
  at
 
   
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
   
 
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
   
 SiteDeployMojo.java
   
 
 :153)
  ... 

Re: Can't deploy site,Help please.

2007-02-07 Thread jiangshachina

Hi,
OK, I get it!
Thanks very much!

a cup of Java, cheers!
Sha Jiang


Markku Saarela wrote:
 
 Hi,
 
 You configure authentication in settings.xml.
 
 Look here for details:  http://maven.apache.org/settings.html#Servers
 
 rgds,
 
 markku
 
 jiangshachina wrote:
 Hello,
 I tried to deploy project via scp just now, but authentication failed.
 How to set the user/password of remote machine in POM file?

 a cup of Java, cheers!
 Sha Jiang


 Markku Saarela wrote:
   
 One slash character was dropped out :-)
 file:///192.1.1.0/temp/directory

 - markku


 Markku Saarela wrote:
 
 Hi,

 No, File protocol can deploy any directory in network where user has
 access. The first slash character is defining that path is absolute two
 others are some server delimiters.

 file:/c:/temp vs. file:///someserver/depl or even
 file://192.1.1.0/temp/directory

 rgds,
 markku

 jiangshachina wrote:
   
   
 Hello,
   
 
 
 I have solved the issue by used file:///path/to/deployment/dir
 
   
   
 file protocol just deploys to a local path, doesn't it?

 a cup of Java, cheers!
 Sha Jiang


 秋秋 wrote:
   
 
 
 Hi,
 yes,I have solved the issue by used
 file:///path/to/deployment/dir*, *
 thanks.


 2007/2/6, Tim Kettler [EMAIL PROTECTED]:
 
   
   
 Hi,

 the URL you give in the distribution management section is the HTTP
 URL
 of your projects site. To deploy it you need to specify a valid
 deployment URL. This could be something like:

 - scp://my.server.com/var/www/htdocs/myproject (for SSH's secure
 copy)
 - sftp://my.server.com/deployment/dir (for SFTP deployment)
 - file:///path/to/deployment/dir (for deploying to a local file
 system)

 Hope this helps
 -Tim

 Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
   
 
 
 Hi,
 I  use apache-tomcat-5.5.17 as a server for the project
 site,the
 
   
   
 url
 is
   
 
 
 http://localhost:8080/pcie/, I have added the configuration in the
 pom.xmllike this:
 distributionManagement
   site
idmaven/id
urlscp://localhost:8080/pcie//url
   /site
  /distributionManagement

 I have start up the server successfull as well as I Have execute
 site
 command,but when I execute site-deploy,I appear the error like
 this:
 FATAL ERROR: Error executing Maven for a project
 org.apache.maven.lifecycle.LifecycleExecutionException: Error
 uploading
 
   
   
 site
   
 
 
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:559)
  at

 
   
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
   
 
 
 (DefaultLifecycleExecutor.java:475)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
 DefaultLifecycleExecutor.java:454)
  at

 
   
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
   
 
 
 (DefaultLifecycleExecutor.java:306)
  at
 
   
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
   
 
 
 DefaultLifecycleExecutor.java:273)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
 DefaultLifecycleExecutor.java:140)
  at
 org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
   
   
 :441)
   
 
 
  at
 org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
   
   
 :382)
   
 
 
  at
 org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
 
   
   
 uploading
   
 
 
 site
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
   
   
 SiteDeployMojo.java
   
 
 
 :184)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:412)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:534)
  ... 8 more
 Caused by:
 
   
   
 org.apache.maven.wagon.authentication.AuthenticationException
 :
   
 
 
 Cannot connect. Reason: invalid server's version string
  at
 
   
   
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
   
 
 
 AbstractSshWagon.java:239)
  at
 
   
   
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
   
 
 
  at
 
   
   
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
   
 
 
  at 

Re: Can't deploy site,Help please.

2007-02-06 Thread Tim Kettler
Hi,

the URL you give in the distribution management section is the HTTP URL
of your projects site. To deploy it you need to specify a valid
deployment URL. This could be something like:

- scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
- sftp://my.server.com/deployment/dir (for SFTP deployment)
- file:///path/to/deployment/dir (for deploying to a local file system)

Hope this helps
-Tim

Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
 Hi,
 I  use apache-tomcat-5.5.17 as a server for the project site,the url is
 http://localhost:8080/pcie/, I have added the configuration in the
 pom.xmllike this:
 distributionManagement
   site
idmaven/id
urlscp://localhost:8080/pcie//url
   /site
  /distributionManagement
 
 I have start up the server successfull as well as I Have execute site
 command,but when I execute site-deploy,I appear the error like this:
 FATAL ERROR: Error executing Maven for a project
 org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:559)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
 (DefaultLifecycleExecutor.java:475)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
 DefaultLifecycleExecutor.java:454)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
 (DefaultLifecycleExecutor.java:306)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
 DefaultLifecycleExecutor.java:273)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
 DefaultLifecycleExecutor.java:140)
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441)
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382)
  at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading
 site
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java
 :184)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:412)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:534)
  ... 8 more
 Caused by: org.apache.maven.wagon.authentication.AuthenticationException:
 Cannot connect. Reason: invalid server's version string
  at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
 AbstractSshWagon.java:239)
  at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
  at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java
 :153)
  ... 10 more
 Caused by: com.jcraft.jsch.JSchException: invalid server's version string
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
 AbstractSshWagon.java:228)
  ... 13 more
 
 
 what can I do?


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



Re: Can't deploy site,Help please.

2007-02-06 Thread sam

Hi,
   yes,I have solved the issue by used file:///path/to/deployment/dir*, *
thanks.


2007/2/6, Tim Kettler [EMAIL PROTECTED]:


Hi,

the URL you give in the distribution management section is the HTTP URL
of your projects site. To deploy it you need to specify a valid
deployment URL. This could be something like:

- scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
- sftp://my.server.com/deployment/dir (for SFTP deployment)
- file:///path/to/deployment/dir (for deploying to a local file system)

Hope this helps
-Tim

Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
 Hi,
 I  use apache-tomcat-5.5.17 as a server for the project site,the url
is
 http://localhost:8080/pcie/, I have added the configuration in the
 pom.xmllike this:
 distributionManagement
   site
idmaven/id
urlscp://localhost:8080/pcie//url
   /site
  /distributionManagement

 I have start up the server successfull as well as I Have execute site
 command,but when I execute site-deploy,I appear the error like this:
 FATAL ERROR: Error executing Maven for a project
 org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
site
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:559)
  at

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
 (DefaultLifecycleExecutor.java:475)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
 DefaultLifecycleExecutor.java:454)
  at

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
 (DefaultLifecycleExecutor.java:306)
  at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
 DefaultLifecycleExecutor.java:273)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
 DefaultLifecycleExecutor.java:140)
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
:441)
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
:382)
  at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
uploading
 site
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
SiteDeployMojo.java
 :184)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:412)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:534)
  ... 8 more
 Caused by: org.apache.maven.wagon.authentication.AuthenticationException
:
 Cannot connect. Reason: invalid server's version string
  at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
(
 AbstractSshWagon.java:239)
  at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
  at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
SiteDeployMojo.java
 :153)
  ... 10 more
 Caused by: com.jcraft.jsch.JSchException: invalid server's version
string
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
(
 AbstractSshWagon.java:228)
  ... 13 more


 what can I do?


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




Re: Can't deploy site,Help please.

2007-02-06 Thread jiangshachina

Hello,
 I have solved the issue by used file:///path/to/deployment/dir
file protocol just deploys to a local path, doesn't it?

a cup of Java, cheers!
Sha Jiang


秋秋 wrote:
 
 Hi,
 yes,I have solved the issue by used file:///path/to/deployment/dir*, *
 thanks.
 
 
 2007/2/6, Tim Kettler [EMAIL PROTECTED]:

 Hi,

 the URL you give in the distribution management section is the HTTP URL
 of your projects site. To deploy it you need to specify a valid
 deployment URL. This could be something like:

 - scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
 - sftp://my.server.com/deployment/dir (for SFTP deployment)
 - file:///path/to/deployment/dir (for deploying to a local file system)

 Hope this helps
 -Tim

 Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
  Hi,
  I  use apache-tomcat-5.5.17 as a server for the project site,the
 url
 is
  http://localhost:8080/pcie/, I have added the configuration in the
  pom.xmllike this:
  distributionManagement
site
 idmaven/id
 urlscp://localhost:8080/pcie//url
/site
   /distributionManagement
 
  I have start up the server successfull as well as I Have execute site
  command,but when I execute site-deploy,I appear the error like this:
  FATAL ERROR: Error executing Maven for a project
  org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
 site
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
  DefaultLifecycleExecutor.java:559)
   at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
  (DefaultLifecycleExecutor.java:475)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
  DefaultLifecycleExecutor.java:454)
   at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
  (DefaultLifecycleExecutor.java:306)
   at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
  DefaultLifecycleExecutor.java:273)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
  DefaultLifecycleExecutor.java:140)
   at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 :441)
   at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 :382)
   at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
  Caused by: org.apache.maven.plugin.MojoExecutionException: Error
 uploading
  site
   at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 SiteDeployMojo.java
  :184)
   at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
  DefaultPluginManager.java:412)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
  DefaultLifecycleExecutor.java:534)
   ... 8 more
  Caused by:
 org.apache.maven.wagon.authentication.AuthenticationException
 :
  Cannot connect. Reason: invalid server's version string
   at
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
  AbstractSshWagon.java:239)
   at
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
   at
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
   at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 SiteDeployMojo.java
  :153)
   ... 10 more
  Caused by: com.jcraft.jsch.JSchException: invalid server's version
 string
   at com.jcraft.jsch.Session.connect(Unknown Source)
   at com.jcraft.jsch.Session.connect(Unknown Source)
   at
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
  AbstractSshWagon.java:228)
   ... 13 more
 
 
  what can I do?


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


 
 

-- 
View this message in context: 
http://www.nabble.com/Can%27t-deploy-site%2CHelp-please.-tf3178351s177.html#a8840223
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: Can't deploy site,Help please.

2007-02-06 Thread Markku Saarela
Hi,

No, File protocol can deploy any directory in network where user has
access. The first slash character is defining that path is absolute two
others are some server delimiters.

file:/c:/temp vs. file:///someserver/depl or even
file://192.1.1.0/temp/directory

rgds,
markku

jiangshachina wrote:
 Hello,
   
 I have solved the issue by used file:///path/to/deployment/dir
 
 file protocol just deploys to a local path, doesn't it?

 a cup of Java, cheers!
 Sha Jiang


 秋秋 wrote:
   
 Hi,
 yes,I have solved the issue by used file:///path/to/deployment/dir*, *
 thanks.


 2007/2/6, Tim Kettler [EMAIL PROTECTED]:
 
 Hi,

 the URL you give in the distribution management section is the HTTP URL
 of your projects site. To deploy it you need to specify a valid
 deployment URL. This could be something like:

 - scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
 - sftp://my.server.com/deployment/dir (for SFTP deployment)
 - file:///path/to/deployment/dir (for deploying to a local file system)

 Hope this helps
 -Tim

 Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
   
 Hi,
 I  use apache-tomcat-5.5.17 as a server for the project site,the
 
 url
 is
   
 http://localhost:8080/pcie/, I have added the configuration in the
 pom.xmllike this:
 distributionManagement
   site
idmaven/id
urlscp://localhost:8080/pcie//url
   /site
  /distributionManagement

 I have start up the server successfull as well as I Have execute site
 command,but when I execute site-deploy,I appear the error like this:
 FATAL ERROR: Error executing Maven for a project
 org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
 
 site
   
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:559)
  at

 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
   
 (DefaultLifecycleExecutor.java:475)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
 DefaultLifecycleExecutor.java:454)
  at

 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
   
 (DefaultLifecycleExecutor.java:306)
  at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
   
 DefaultLifecycleExecutor.java:273)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
 DefaultLifecycleExecutor.java:140)
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
 :441)
   
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
 :382)
   
  at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
 
 uploading
   
 site
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
 SiteDeployMojo.java
   
 :184)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:412)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:534)
  ... 8 more
 Caused by:
 
 org.apache.maven.wagon.authentication.AuthenticationException
 :
   
 Cannot connect. Reason: invalid server's version string
  at
 
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
   
 AbstractSshWagon.java:239)
  at
 
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
   
  at
 
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
   
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
 SiteDeployMojo.java
   
 :153)
  ... 10 more
 Caused by: com.jcraft.jsch.JSchException: invalid server's version
 
 string
   
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at
 
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
   
 AbstractSshWagon.java:228)
  ... 13 more


 what can I do?
 
 -
 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: Can't deploy site,Help please.

2007-02-06 Thread Tim Kettler
Am Dienstag, den 06.02.2007, 21:40 -0800 schrieb jiangshachina:
 Hello,
  I have solved the issue by used file:///path/to/deployment/dir
 file protocol just deploys to a local path, doesn't it?

Correct.

 a cup of Java, cheers!
 Sha Jiang

-Tim

 秋秋 wrote:
  
  Hi,
  yes,I have solved the issue by used file:///path/to/deployment/dir*, *
  thanks.
  
  
  2007/2/6, Tim Kettler [EMAIL PROTECTED]:
 
  Hi,
 
  the URL you give in the distribution management section is the HTTP URL
  of your projects site. To deploy it you need to specify a valid
  deployment URL. This could be something like:
 
  - scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
  - sftp://my.server.com/deployment/dir (for SFTP deployment)
  - file:///path/to/deployment/dir (for deploying to a local file system)
 
  Hope this helps
  -Tim
 
  Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
   Hi,
   I  use apache-tomcat-5.5.17 as a server for the project site,the
  url
  is
   http://localhost:8080/pcie/, I have added the configuration in the
   pom.xmllike this:
   distributionManagement
 site
  idmaven/id
  urlscp://localhost:8080/pcie//url
 /site
/distributionManagement
  
   I have start up the server successfull as well as I Have execute site
   command,but when I execute site-deploy,I appear the error like this:
   FATAL ERROR: Error executing Maven for a project
   org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
  site
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
   DefaultLifecycleExecutor.java:559)
at
  
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
   (DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
   DefaultLifecycleExecutor.java:454)
at
  
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
   (DefaultLifecycleExecutor.java:306)
at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
   DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
   DefaultLifecycleExecutor.java:140)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
  :441)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
  :382)
at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
   Caused by: org.apache.maven.plugin.MojoExecutionException: Error
  uploading
   site
at org.apache.maven.plugins.site.SiteDeployMojo.execute(
  SiteDeployMojo.java
   :184)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
   DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
   DefaultLifecycleExecutor.java:534)
... 8 more
   Caused by:
  org.apache.maven.wagon.authentication.AuthenticationException
  :
   Cannot connect. Reason: invalid server's version string
at
  org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
  (
   AbstractSshWagon.java:239)
at
  org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
at
  org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
at org.apache.maven.plugins.site.SiteDeployMojo.execute(
  SiteDeployMojo.java
   :153)
... 10 more
   Caused by: com.jcraft.jsch.JSchException: invalid server's version
  string
at com.jcraft.jsch.Session.connect(Unknown Source)
at com.jcraft.jsch.Session.connect(Unknown Source)
at
  org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
  (
   AbstractSshWagon.java:228)
... 13 more
  
  
   what can I do?
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
  
  
 
 -- 
 View this message in context: 
 http://www.nabble.com/Can%27t-deploy-site%2CHelp-please.-tf3178351s177.html#a8840223
 Sent from the Maven - Users mailing list archive at Nabble.com.
 
 
 -
 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: Can't deploy site,Help please.

2007-02-06 Thread Markku Saarela
One slash character was dropped out :-)
file:///192.1.1.0/temp/directory

- markku


Markku Saarela wrote:
 Hi,

 No, File protocol can deploy any directory in network where user has
 access. The first slash character is defining that path is absolute two
 others are some server delimiters.

 file:/c:/temp vs. file:///someserver/depl or even
 file://192.1.1.0/temp/directory

 rgds,
 markku

 jiangshachina wrote:
   
 Hello,
   
 
 I have solved the issue by used file:///path/to/deployment/dir
 
   
 file protocol just deploys to a local path, doesn't it?

 a cup of Java, cheers!
 Sha Jiang


 秋秋 wrote:
   
 
 Hi,
 yes,I have solved the issue by used file:///path/to/deployment/dir*, *
 thanks.


 2007/2/6, Tim Kettler [EMAIL PROTECTED]:
 
   
 Hi,

 the URL you give in the distribution management section is the HTTP URL
 of your projects site. To deploy it you need to specify a valid
 deployment URL. This could be something like:

 - scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
 - sftp://my.server.com/deployment/dir (for SFTP deployment)
 - file:///path/to/deployment/dir (for deploying to a local file system)

 Hope this helps
 -Tim

 Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
   
 
 Hi,
 I  use apache-tomcat-5.5.17 as a server for the project site,the
 
   
 url
 is
   
 
 http://localhost:8080/pcie/, I have added the configuration in the
 pom.xmllike this:
 distributionManagement
   site
idmaven/id
urlscp://localhost:8080/pcie//url
   /site
  /distributionManagement

 I have start up the server successfull as well as I Have execute site
 command,but when I execute site-deploy,I appear the error like this:
 FATAL ERROR: Error executing Maven for a project
 org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
 
   
 site
   
 
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:559)
  at

 
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
   
 
 (DefaultLifecycleExecutor.java:475)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
 DefaultLifecycleExecutor.java:454)
  at

 
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
   
 
 (DefaultLifecycleExecutor.java:306)
  at
 
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
   
 
 DefaultLifecycleExecutor.java:273)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
 DefaultLifecycleExecutor.java:140)
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
   
 :441)
   
 
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
   
 :382)
   
 
  at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
 
   
 uploading
   
 
 site
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
   
 SiteDeployMojo.java
   
 
 :184)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:412)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:534)
  ... 8 more
 Caused by:
 
   
 org.apache.maven.wagon.authentication.AuthenticationException
 :
   
 
 Cannot connect. Reason: invalid server's version string
  at
 
   
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
   
 
 AbstractSshWagon.java:239)
  at
 
   
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
   
 
  at
 
   
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
   
 
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
   
 SiteDeployMojo.java
   
 
 :153)
  ... 10 more
 Caused by: com.jcraft.jsch.JSchException: invalid server's version
 
   
 string
   
 
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at
 
   
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
   
 
 AbstractSshWagon.java:228)
  ... 13 more


 what can I do?
 
   
 -
 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: Can't deploy site,Help please.

2007-02-06 Thread jiangshachina

Hello,
I tried to deploy project via scp just now, but authentication failed.
How to set the user/password of remote machine in POM file?

a cup of Java, cheers!
Sha Jiang


Markku Saarela wrote:
 
 One slash character was dropped out :-)
 file:///192.1.1.0/temp/directory
 
 - markku
 
 
 Markku Saarela wrote:
 Hi,

 No, File protocol can deploy any directory in network where user has
 access. The first slash character is defining that path is absolute two
 others are some server delimiters.

 file:/c:/temp vs. file:///someserver/depl or even
 file://192.1.1.0/temp/directory

 rgds,
 markku

 jiangshachina wrote:
   
 Hello,
   
 
 I have solved the issue by used file:///path/to/deployment/dir
 
   
 file protocol just deploys to a local path, doesn't it?

 a cup of Java, cheers!
 Sha Jiang


 秋秋 wrote:
   
 
 Hi,
 yes,I have solved the issue by used
 file:///path/to/deployment/dir*, *
 thanks.


 2007/2/6, Tim Kettler [EMAIL PROTECTED]:
 
   
 Hi,

 the URL you give in the distribution management section is the HTTP
 URL
 of your projects site. To deploy it you need to specify a valid
 deployment URL. This could be something like:

 - scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
 - sftp://my.server.com/deployment/dir (for SFTP deployment)
 - file:///path/to/deployment/dir (for deploying to a local file
 system)

 Hope this helps
 -Tim

 Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
   
 
 Hi,
 I  use apache-tomcat-5.5.17 as a server for the project site,the
 
   
 url
 is
   
 
 http://localhost:8080/pcie/, I have added the configuration in the
 pom.xmllike this:
 distributionManagement
   site
idmaven/id
urlscp://localhost:8080/pcie//url
   /site
  /distributionManagement

 I have start up the server successfull as well as I Have execute
 site
 command,but when I execute site-deploy,I appear the error like
 this:
 FATAL ERROR: Error executing Maven for a project
 org.apache.maven.lifecycle.LifecycleExecutionException: Error
 uploading
 
   
 site
   
 
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:559)
  at

 
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
   
 
 (DefaultLifecycleExecutor.java:475)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
 DefaultLifecycleExecutor.java:454)
  at

 
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
   
 
 (DefaultLifecycleExecutor.java:306)
  at
 
   
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
   
 
 DefaultLifecycleExecutor.java:273)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
 DefaultLifecycleExecutor.java:140)
  at
 org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
   
 :441)
   
 
  at
 org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
   
 :382)
   
 
  at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
 
   
 uploading
   
 
 site
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
   
 SiteDeployMojo.java
   
 
 :184)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:412)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:534)
  ... 8 more
 Caused by:
 
   
 org.apache.maven.wagon.authentication.AuthenticationException
 :
   
 
 Cannot connect. Reason: invalid server's version string
  at
 
   
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
   
 
 AbstractSshWagon.java:239)
  at
 
   
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
   
 
  at
 
   
 org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
   
 
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
   
 SiteDeployMojo.java
   
 
 :153)
  ... 10 more
 Caused by: com.jcraft.jsch.JSchException: invalid server's version
 
   
 string
   
 
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at
 
   
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
 (
   
 
 AbstractSshWagon.java:228)
  ... 13 more


 what can I do?
 
   
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


   

Can't deploy site,Help please.

2007-02-05 Thread 秋秋

Hi,
   I  use apache-tomcat-5.5.17 as a server for the project site,the url is
http://localhost:8080/pcie/, I have added the configuration in the
pom.xmllike this:
distributionManagement
 site
  idmaven/id
  urlscp://localhost:8080/pcie//url
 /site
/distributionManagement

I have start up the server successfull as well as I Have execute site
command,but when I execute site-deploy,I appear the error like this:
FATAL ERROR: Error executing Maven for a project
org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:140)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382)
at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading
site
at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java
:184)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:534)
... 8 more
Caused by: org.apache.maven.wagon.authentication.AuthenticationException:
Cannot connect. Reason: invalid server's version string
at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
AbstractSshWagon.java:239)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java
:153)
... 10 more
Caused by: com.jcraft.jsch.JSchException: invalid server's version string
at com.jcraft.jsch.Session.connect(Unknown Source)
at com.jcraft.jsch.Session.connect(Unknown Source)
at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
AbstractSshWagon.java:228)
... 13 more


what can I do?


Re: maven-changes-plugin help please

2006-10-25 Thread Naess, Ronny
 
Does maven-changes-plugin work well with M2 and what version should I
choose? I tried it a while ago without success.
By the way, we use Subversion.

-Ronny

-Opprinnelig melding-
Fra: Dennis Lundberg [mailto:[EMAIL PROTECTED] 
Sendt: 24. oktober 2006 23:15
Til: Maven Users List; [EMAIL PROTECTED]
Emne: Re: maven-changes-plugin help please

The Apache-version of the plugin is a reporting-plugin. This means that
it will generate its output during site generation. It also means that
configuration should be in the reporting section of your pom. Please
see:
   http://maven.apache.org/plugins/maven-changes-plugin/usage.html

--
Dennis Lundberg

Pete wrote:
 Help, I'm trying to switch from the old codehaus maven-changes-plugin 
 to the new org.apache.maven.plugins version.
 
 Previously I had my pom configured to use the old plugin during the 
 compile phase, so that a changes-report.html could be nested inside 
 the web app's pages.
 
 Now with the new plugin it doesn't seem to generate a report at all, 
 is there something about the new plugin which means it will only 
 generate during the 'site' goal ?
 
 I've tried with and without a phase, and -X doesn't show any 
 configuration for the plugin happening at all  :-
 
 
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-changes-plugin/artifactId
 version2.0-beta-2-SNAPSHOT/version
 executions
 execution
 idproduce changes html page/id
 
 !-- phasecompile/phase--
 inheritedfalse/inherited
 configuration   
   

xmlPath${project.build.outputDirectory}/changes/changes.xml/xmlPath
 reportSets
 reportSet
 reports
 reportchanges-report/report
 /reports
 /reportSet
 /reportSets
 /configuration
 goals
 goalchanges-report/goal
 /goals
 /execution
 /executions
 /plugin
 
 -
 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]


!DSPAM:453e87fd64881357017964!


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



AW: maven-changes-plugin help please

2006-10-25 Thread Fred . Hauschel
Hi
I use

plugin
groupIdorg.codehaus.mojo/groupId

artifactIdchanges-maven-plugin/artifactId
version2.0-beta-1/version
reportSets
reportSet
reports

reportchanges-report/report
/reports
/reportSet
/reportSets
/plugin

works fine!



-Ursprüngliche Nachricht-
Von: Naess, Ronny [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 25. Oktober 2006 10:16
An: Maven Users List
Betreff: Re: maven-changes-plugin help please


 
Does maven-changes-plugin work well with M2 and what version should I
choose? I tried it a while ago without success.
By the way, we use Subversion.

-Ronny

-Opprinnelig melding-
Fra: Dennis Lundberg [mailto:[EMAIL PROTECTED] 
Sendt: 24. oktober 2006 23:15
Til: Maven Users List; [EMAIL PROTECTED]
Emne: Re: maven-changes-plugin help please

The Apache-version of the plugin is a reporting-plugin. This means that
it will generate its output during site generation. It also means that
configuration should be in the reporting section of your pom. Please
see:
   http://maven.apache.org/plugins/maven-changes-plugin/usage.html

--
Dennis Lundberg

Pete wrote:
 Help, I'm trying to switch from the old codehaus maven-changes-plugin 
 to the new org.apache.maven.plugins version.
 
 Previously I had my pom configured to use the old plugin during the 
 compile phase, so that a changes-report.html could be nested inside 
 the web app's pages.
 
 Now with the new plugin it doesn't seem to generate a report at all, 
 is there something about the new plugin which means it will only 
 generate during the 'site' goal ?
 
 I've tried with and without a phase, and -X doesn't show any 
 configuration for the plugin happening at all  :-
 
 
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-changes-plugin/artifactId
 version2.0-beta-2-SNAPSHOT/version
 executions
 execution
 idproduce changes html page/id
 
 !-- phasecompile/phase--
 inheritedfalse/inherited
 configuration   
   

xmlPath${project.build.outputDirectory}/changes/changes.xml/xmlPath
 reportSets
 reportSet
 reports
 reportchanges-report/report
 /reports
 /reportSet
 /reportSets
 /configuration
 goals
 goalchanges-report/goal
 /goals
 /execution
 /executions
 /plugin
 
 -
 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]


!DSPAM:453e87fd64881357017964!


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

  
 

Kabel Deutschland bietet Ihnen Internet, Telefonieren und Fernsehen aus einer 
Hand. Informieren Sie sich über unsere Produkte unter 

www.kabeldeutschland.de
 
Diese E-Mail und etwaige Anhänge enthalten vertrauliche und/oder rechtlich 
geschützte Informationen. Wenn Sie nicht der richtige Adressat sind, 
benachrichtigen Sie bitte den Absender und vernichten Sie anschließend diese 
Mail und die Anlagen.


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



SV: maven-changes-plugin help please

2006-10-25 Thread Naess, Ronny
Aha, I am mixing this plugin with the maven-developer-activity-plugin.

I tought this the changes-maven-plugin created a report based on filechanges in 
SCM, but thats ofcourse not the case :-) 
It is the other one I am interested in. Thx anyway.

-Ronny

-Opprinnelig melding-
Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sendt: 25. oktober 2006 10:20
Til: users@maven.apache.org
Emne: AW: maven-changes-plugin help please

Hi
I use

plugin
groupIdorg.codehaus.mojo/groupId

artifactIdchanges-maven-plugin/artifactId
version2.0-beta-1/version
reportSets
reportSet
reports

reportchanges-report/report
/reports
/reportSet
/reportSets
/plugin

works fine!



-Ursprüngliche Nachricht-
Von: Naess, Ronny [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 25. Oktober 2006 10:16
An: Maven Users List
Betreff: Re: maven-changes-plugin help please


 
Does maven-changes-plugin work well with M2 and what version should I choose? I 
tried it a while ago without success.
By the way, we use Subversion.

-Ronny

-Opprinnelig melding-
Fra: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sendt: 24. oktober 2006 23:15
Til: Maven Users List; [EMAIL PROTECTED]
Emne: Re: maven-changes-plugin help please

The Apache-version of the plugin is a reporting-plugin. This means that it will 
generate its output during site generation. It also means that configuration 
should be in the reporting section of your pom. Please
see:
   http://maven.apache.org/plugins/maven-changes-plugin/usage.html

--
Dennis Lundberg

Pete wrote:
 Help, I'm trying to switch from the old codehaus maven-changes-plugin 
 to the new org.apache.maven.plugins version.
 
 Previously I had my pom configured to use the old plugin during the 
 compile phase, so that a changes-report.html could be nested inside 
 the web app's pages.
 
 Now with the new plugin it doesn't seem to generate a report at all, 
 is there something about the new plugin which means it will only 
 generate during the 'site' goal ?
 
 I've tried with and without a phase, and -X doesn't show any 
 configuration for the plugin happening at all  :-
 
 
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-changes-plugin/artifactId
 version2.0-beta-2-SNAPSHOT/version
 executions
 execution
 idproduce changes html page/id
 
 !-- phasecompile/phase--
 inheritedfalse/inherited
 configuration   
   

xmlPath${project.build.outputDirectory}/changes/changes.xml/xmlPath
 reportSets
 reportSet
 reports
 reportchanges-report/report
 /reports
 /reportSet
 /reportSets
 /configuration
 goals
 goalchanges-report/goal
 /goals
 /execution
 /executions
 /plugin
 
 -
 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]





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

  
 

Kabel Deutschland bietet Ihnen Internet, Telefonieren und Fernsehen aus einer 
Hand. Informieren Sie sich über unsere Produkte unter 

www.kabeldeutschland.de
 
Diese E-Mail und etwaige Anhänge enthalten vertrauliche und/oder rechtlich 
geschützte Informationen. Wenn Sie nicht der richtige Adressat sind, 
benachrichtigen Sie bitte den Absender und vernichten Sie anschließend diese 
Mail und die Anlagen.


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


!DSPAM:453f1e7819381367111490!


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



Re: AW: maven-changes-plugin help please

2006-10-25 Thread Markku Saarela

You should use changes plugin it is newer version of that codehaus plugin:

 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-changes-plugin/artifactId
   configuration
 xmlPath${basedir}/src/site/changes.xml/xmlPath
   /configuration
   reportSets
 reportSet
   reports
 reportchanges-report/report
   /reports
 /reportSet
   /reportSets
 /plugin


[EMAIL PROTECTED] wrote:

Hi
I use

plugin
groupIdorg.codehaus.mojo/groupId

artifactIdchanges-maven-plugin/artifactId
version2.0-beta-1/version
reportSets
reportSet
reports

reportchanges-report/report
/reports
/reportSet
/reportSets
/plugin

works fine!



-Ursprüngliche Nachricht-
Von: Naess, Ronny [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 25. Oktober 2006 10:16
An: Maven Users List
Betreff: Re: maven-changes-plugin help please


 
Does maven-changes-plugin work well with M2 and what version should I

choose? I tried it a while ago without success.
By the way, we use Subversion.

-Ronny

-Opprinnelig melding-
Fra: Dennis Lundberg [mailto:[EMAIL PROTECTED] 
Sendt: 24. oktober 2006 23:15

Til: Maven Users List; [EMAIL PROTECTED]
Emne: Re: maven-changes-plugin help please

The Apache-version of the plugin is a reporting-plugin. This means that
it will generate its output during site generation. It also means that
configuration should be in the reporting section of your pom. Please
see:
   http://maven.apache.org/plugins/maven-changes-plugin/usage.html

--
Dennis Lundberg

Pete wrote:
  
Help, I'm trying to switch from the old codehaus maven-changes-plugin 
to the new org.apache.maven.plugins version.


Previously I had my pom configured to use the old plugin during the 
compile phase, so that a changes-report.html could be nested inside 
the web app's pages.


Now with the new plugin it doesn't seem to generate a report at all, 
is there something about the new plugin which means it will only 
generate during the 'site' goal ?


I've tried with and without a phase, and -X doesn't show any 
configuration for the plugin happening at all  :-



plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
version2.0-beta-2-SNAPSHOT/version
executions
execution
idproduce changes html page/id

!-- phasecompile/phase--
inheritedfalse/inherited
configuration   
  



xmlPath${project.build.outputDirectory}/changes/changes.xml/xmlPath
  

reportSets
reportSet
reports
reportchanges-report/report
/reports
/reportSet
/reportSets
/configuration
goals
goalchanges-report/goal
/goals
/execution
/executions
/plugin

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


!DSPAM:453e87fd64881357017964!


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

  
 

Kabel Deutschland bietet Ihnen Internet, Telefonieren und Fernsehen aus einer Hand. Informieren Sie sich über unsere Produkte unter 


www.kabeldeutschland.de
 
Diese E-Mail und etwaige Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind, benachrichtigen Sie bitte den Absender und vernichten Sie anschließend diese Mail und die Anlagen.



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



AW: AW: maven-changes-plugin help please

2006-10-25 Thread Fred . Hauschel
thanks!




-Ursprüngliche Nachricht-
Von: Markku Saarela [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 25. Oktober 2006 12:38
An: Maven Users List
Betreff: Re: AW: maven-changes-plugin help please


You should use changes plugin it is newer version of that codehaus plugin:

  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
configuration
  xmlPath${basedir}/src/site/changes.xml/xmlPath
/configuration
reportSets
  reportSet
reports
  reportchanges-report/report
/reports
  /reportSet
/reportSets
  /plugin


[EMAIL PROTECTED] wrote:
 Hi
 I use

   plugin
   groupIdorg.codehaus.mojo/groupId
   
 artifactIdchanges-maven-plugin/artifactId
   version2.0-beta-1/version
   reportSets
   reportSet
   reports
   
 reportchanges-report/report
   /reports
   /reportSet
   /reportSets
   /plugin

 works fine!



 -Ursprüngliche Nachricht-
 Von: Naess, Ronny [mailto:[EMAIL PROTECTED]
 Gesendet: Mittwoch, 25. Oktober 2006 10:16
 An: Maven Users List
 Betreff: Re: maven-changes-plugin help please


  
 Does maven-changes-plugin work well with M2 and what version should I
 choose? I tried it a while ago without success.
 By the way, we use Subversion.

 -Ronny

 -Opprinnelig melding-
 Fra: Dennis Lundberg [mailto:[EMAIL PROTECTED] 
 Sendt: 24. oktober 2006 23:15
 Til: Maven Users List; [EMAIL PROTECTED]
 Emne: Re: maven-changes-plugin help please

 The Apache-version of the plugin is a reporting-plugin. This means that
 it will generate its output during site generation. It also means that
 configuration should be in the reporting section of your pom. Please
 see:
http://maven.apache.org/plugins/maven-changes-plugin/usage.html

 --
 Dennis Lundberg

 Pete wrote:
   
 Help, I'm trying to switch from the old codehaus maven-changes-plugin 
 to the new org.apache.maven.plugins version.

 Previously I had my pom configured to use the old plugin during the 
 compile phase, so that a changes-report.html could be nested inside 
 the web app's pages.

 Now with the new plugin it doesn't seem to generate a report at all, 
 is there something about the new plugin which means it will only 
 generate during the 'site' goal ?

 I've tried with and without a phase, and -X doesn't show any 
 configuration for the plugin happening at all  :-


 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-changes-plugin/artifactId
 version2.0-beta-2-SNAPSHOT/version
 executions
 execution
 idproduce changes html page/id

 !-- phasecompile/phase--
 inheritedfalse/inherited
 configuration   
   

 
 xmlPath${project.build.outputDirectory}/changes/changes.xml/xmlPath
   
 reportSets
 reportSet
 reports
 reportchanges-report/report
 /reports
 /reportSet
 /reportSets
 /configuration
 goals
 goalchanges-report/goal
 /goals
 /execution
 /executions
 /plugin

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


 !DSPAM:453e87fd64881357017964!


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

   
  

 Kabel Deutschland bietet Ihnen Internet, Telefonieren und Fernsehen aus einer 
 Hand. Informieren Sie sich über unsere Produkte unter 

 www.kabeldeutschland.de
  
 Diese E-Mail und etwaige Anhänge enthalten vertrauliche und/oder rechtlich 
 geschützte Informationen. Wenn Sie nicht der richtige Adressat sind, 
 benachrichtigen Sie bitte den Absender und vernichten Sie anschließend diese 
 Mail und die Anlagen.


 -
 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: maven-changes-plugin help please

2006-10-24 Thread Dennis Lundberg
The Apache-version of the plugin is a reporting-plugin. This means that 
it will generate its output during site generation. It also means that 
configuration should be in the reporting section of your pom. Please see:

  http://maven.apache.org/plugins/maven-changes-plugin/usage.html

--
Dennis Lundberg

Pete wrote:

Help, I'm trying to switch from the old codehaus maven-changes-plugin
to the new org.apache.maven.plugins version.

Previously I had my pom configured to use the old plugin during the
compile phase, so that a changes-report.html could be nested inside
the web app's pages.

Now with the new plugin it doesn't seem to generate a report at all,
is there something about the new plugin which means it will only
generate during the 'site' goal ?

I've tried with and without a phase, and -X doesn't show any
configuration for the plugin happening at all  :-


plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
version2.0-beta-2-SNAPSHOT/version
executions
execution
idproduce changes html page/id

!-- phasecompile/phase--
inheritedfalse/inherited
configuration   
  
xmlPath${project.build.outputDirectory}/changes/changes.xml/xmlPath

reportSets
reportSet
reports
reportchanges-report/report
/reports
/reportSet
/reportSets
/configuration
goals
goalchanges-report/goal
/goals
/execution
/executions
/plugin

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



maven-changes-plugin help please

2006-09-19 Thread Pete

Help, I'm trying to switch from the old codehaus maven-changes-plugin
to the new org.apache.maven.plugins version.

Previously I had my pom configured to use the old plugin during the
compile phase, so that a changes-report.html could be nested inside
the web app's pages.

Now with the new plugin it doesn't seem to generate a report at all,
is there something about the new plugin which means it will only
generate during the 'site' goal ?

I've tried with and without a phase, and -X doesn't show any
configuration for the plugin happening at all  :-


plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
version2.0-beta-2-SNAPSHOT/version
executions
execution
idproduce changes html page/id

!-- phasecompile/phase--
inheritedfalse/inherited
configuration   
  
xmlPath${project.build.outputDirectory}/changes/changes.xml/xmlPath
reportSets
reportSet
reports

reportchanges-report/report
/reports
/reportSet
/reportSets
/configuration
goals
goalchanges-report/goal
/goals
/execution
/executions
/plugin

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



Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Wayne Fay
Looks like you're using an old doxia? NoSuchMethodError would suggest
that your version of doxia is missing a method or that signatures
aren't proper.

[DEBUG] Trace
java.lang.NoSuchMethodError:
org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)

Wayne

On 3/30/06, Mick Knutson [EMAIL PROTECTED] wrote:
 [INFO] No goals needed for project - skipping
 [DEBUG] com.furl:furl:pom:1.3 (selected for null)
 [DEBUG] Configuring mojo
 'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:stage' --
 [DEBUG]   (f) generateReports = true
 [DEBUG]   (f) generatedSiteDirectory =
 c:\opt\furl\furlm2\trunk\target\generated-site
 [DEBUG]   (f) localRepository = [local] - file://C:\Documents and
 Settings\mknutson\.m2\repository
 [DEBUG]   (f) outputDirectory = c:\opt\furl\furlm2\trunk\target\site
 [DEBUG]   (f) outputEncoding = ISO-8859-1
 [DEBUG]   (f) project = [EMAIL PROTECTED]
 [DEBUG]   (f) reactorProjects =
 [EMAIL PROTECTED],
 [EMAIL PROTECTED], org.apache.maven.proj
 [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED], org.apache.maven.project.Ma
 [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.project.MavenPro
 [EMAIL PROTECTED], [EMAIL PROTECTED]
 [DEBUG]   (f) reports =
 [EMAIL PROTECTED],
 [EMAIL PROTECTED], org.apache.maven.p
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED], or
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.report.proj
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.changelog.FileActivityRepor
 [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.plugin.taglist.TagListReport@
 132021a, [EMAIL PROTECTED]
 [DEBUG]   (f) repositories = [[backup] - http://repo1.maven.org/maven2,
 [apache.snapshots] - http://cvs.apache.org/maven-snapshot-repository,
 [centr
 al] - http://repo1.maven.org/maven2]
 [DEBUG]   (f) resourcesDirectory =
 c:\opt\furl\furlm2\trunk\src\site\resources
 [DEBUG]   (f) siteDirectory = c:\opt\furl\furlm2\trunk\src\site
 [DEBUG]   (f) stagingDirectory = C:\TEMP\stage
 [DEBUG]   (f) xdocDirectory = c:\opt\furl\furlm2\trunk\xdocs
 [DEBUG] -- end configuration --
 [INFO] [site:stage]
 [WARNING] Error loading report org.apache.maven.changelog.ChangeLogReport -
 AbstractMethodError: canGenerateReport()
 [WARNING] Error loading report org.apache.maven.changelog.FileActivityReport
 - AbstractMethodError: canGenerateReport()
 [WARNING] Error loading report org.apache.maven.plugin.jxr.JxrReport -
 AbstractMethodError: canGenerateReport()
 [WARNING] Error loading report org.apache.maven.plugin.taglist.TagListReport
 - AbstractMethodError: canGenerateReport()
 [DEBUG] Skipping disabled repository backup
 [DEBUG] Skipping disabled repository central
 [DEBUG] maven-stylus-skin: using locally installed snapshot
 [INFO]
 
 [ERROR] FATAL ERROR
 [INFO]
 
 [INFO]
 org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
 [INFO]
 
 [DEBUG] Trace
 java.lang.NoSuchMethodError:
 org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)
at
 org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:111)
at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
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:324)
at
 

Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Mick Knutson
1. I don't know what the doxia is as I did not import it. How do I fix it 
please?

Should I add that dependancy?


---
Thank You
Mick Knutson

BASE logic, inc.
(415) 648-1804 (San Francisco, CA)
http://www.BASELogic.com

http://www.djmick.com
---





From: Wayne Fay [EMAIL PROTECTED]
Reply-To: Maven Users List users@maven.apache.org
To: Maven Users List users@maven.apache.org
Subject: Re: [m202] Still can't get site to work... Help please
Date: Thu, 6 Apr 2006 12:26:30 -0500

Looks like you're using an old doxia? NoSuchMethodError would suggest
that your version of doxia is missing a method or that signatures
aren't proper.

[DEBUG] Trace
java.lang.NoSuchMethodError:
org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)

Wayne

On 3/30/06, Mick Knutson [EMAIL PROTECTED] wrote:
 [INFO] No goals needed for project - skipping
 [DEBUG] com.furl:furl:pom:1.3 (selected for null)
 [DEBUG] Configuring mojo
 'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:stage' --
 [DEBUG]   (f) generateReports = true
 [DEBUG]   (f) generatedSiteDirectory =
 c:\opt\furl\furlm2\trunk\target\generated-site
 [DEBUG]   (f) localRepository = [local] - file://C:\Documents and
 Settings\mknutson\.m2\repository
 [DEBUG]   (f) outputDirectory = c:\opt\furl\furlm2\trunk\target\site
 [DEBUG]   (f) outputEncoding = ISO-8859-1
 [DEBUG]   (f) project = [EMAIL PROTECTED]
 [DEBUG]   (f) reactorProjects =
 [EMAIL PROTECTED],
 [EMAIL PROTECTED], org.apache.maven.proj
 [EMAIL PROTECTED], 
[EMAIL PROTECTED],
 [EMAIL PROTECTED], 
org.apache.maven.project.Ma

 [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.project.MavenPro
 [EMAIL PROTECTED], [EMAIL PROTECTED]
 [DEBUG]   (f) reports =
 [EMAIL PROTECTED],
 [EMAIL PROTECTED], org.apache.maven.p
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED], or
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.report.proj
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.changelog.FileActivityRepor
 [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.plugin.taglist.TagListReport@
 132021a, [EMAIL PROTECTED]
 [DEBUG]   (f) repositories = [[backup] - http://repo1.maven.org/maven2,
 [apache.snapshots] - http://cvs.apache.org/maven-snapshot-repository,
 [centr
 al] - http://repo1.maven.org/maven2]
 [DEBUG]   (f) resourcesDirectory =
 c:\opt\furl\furlm2\trunk\src\site\resources
 [DEBUG]   (f) siteDirectory = c:\opt\furl\furlm2\trunk\src\site
 [DEBUG]   (f) stagingDirectory = C:\TEMP\stage
 [DEBUG]   (f) xdocDirectory = c:\opt\furl\furlm2\trunk\xdocs
 [DEBUG] -- end configuration --
 [INFO] [site:stage]
 [WARNING] Error loading report 
org.apache.maven.changelog.ChangeLogReport -

 AbstractMethodError: canGenerateReport()
 [WARNING] Error loading report 
org.apache.maven.changelog.FileActivityReport

 - AbstractMethodError: canGenerateReport()
 [WARNING] Error loading report org.apache.maven.plugin.jxr.JxrReport -
 AbstractMethodError: canGenerateReport()
 [WARNING] Error loading report 
org.apache.maven.plugin.taglist.TagListReport

 - AbstractMethodError: canGenerateReport()
 [DEBUG] Skipping disabled repository backup
 [DEBUG] Skipping disabled repository central
 [DEBUG] maven-stylus-skin: using locally installed snapshot
 [INFO]
 


 [ERROR] FATAL ERROR
 [INFO]
 


 [INFO]
 
org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V

 [INFO]
 


 [DEBUG] Trace
 java.lang.NoSuchMethodError:
 
org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
at 
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)

at
 
org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:111)

at
 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)

at
 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)

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

Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Wayne Fay
Try mvn -U site:site

Wayne

On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
 1. I don't know what the doxia is as I did not import it. How do I fix it
 please?
 Should I add that dependancy?


 ---
 Thank You
 Mick Knutson

 BASE logic, inc.
 (415) 648-1804 (San Francisco, CA)
 http://www.BASELogic.com

 http://www.djmick.com
 ---




 From: Wayne Fay [EMAIL PROTECTED]
 Reply-To: Maven Users List users@maven.apache.org
 To: Maven Users List users@maven.apache.org
 Subject: Re: [m202] Still can't get site to work... Help please
 Date: Thu, 6 Apr 2006 12:26:30 -0500
 
 Looks like you're using an old doxia? NoSuchMethodError would suggest
 that your version of doxia is missing a method or that signatures
 aren't proper.
 
 [DEBUG] Trace
 java.lang.NoSuchMethodError:
 org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
 at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)
 
 Wayne
 
 On 3/30/06, Mick Knutson [EMAIL PROTECTED] wrote:
   [INFO] No goals needed for project - skipping
   [DEBUG] com.furl:furl:pom:1.3 (selected for null)
   [DEBUG] Configuring mojo
   'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:stage' --
   [DEBUG]   (f) generateReports = true
   [DEBUG]   (f) generatedSiteDirectory =
   c:\opt\furl\furlm2\trunk\target\generated-site
   [DEBUG]   (f) localRepository = [local] - file://C:\Documents and
   Settings\mknutson\.m2\repository
   [DEBUG]   (f) outputDirectory = c:\opt\furl\furlm2\trunk\target\site
   [DEBUG]   (f) outputEncoding = ISO-8859-1
   [DEBUG]   (f) project = [EMAIL PROTECTED]
   [DEBUG]   (f) reactorProjects =
   [EMAIL PROTECTED],
   [EMAIL PROTECTED], org.apache.maven.proj
   [EMAIL PROTECTED],
 [EMAIL PROTECTED],
   [EMAIL PROTECTED],
 org.apache.maven.project.Ma
   [EMAIL PROTECTED], [EMAIL PROTECTED],
   [EMAIL PROTECTED],
   org.apache.maven.project.MavenPro
   [EMAIL PROTECTED], [EMAIL PROTECTED]
   [DEBUG]   (f) reports =
   [EMAIL PROTECTED],
   [EMAIL PROTECTED], org.apache.maven.p
   [EMAIL PROTECTED],
   [EMAIL PROTECTED],
   [EMAIL PROTECTED], or
   [EMAIL PROTECTED],
   [EMAIL PROTECTED],
   org.apache.maven.report.proj
   [EMAIL PROTECTED],
   [EMAIL PROTECTED],
   [EMAIL PROTECTED],
   [EMAIL PROTECTED],
   [EMAIL PROTECTED],
   org.apache.maven.changelog.FileActivityRepor
   [EMAIL PROTECTED], [EMAIL PROTECTED],
   [EMAIL PROTECTED],
   org.apache.maven.plugin.taglist.TagListReport@
   132021a, [EMAIL PROTECTED]
   [DEBUG]   (f) repositories = [[backup] - http://repo1.maven.org/maven2,
   [apache.snapshots] - http://cvs.apache.org/maven-snapshot-repository,
   [centr
   al] - http://repo1.maven.org/maven2]
   [DEBUG]   (f) resourcesDirectory =
   c:\opt\furl\furlm2\trunk\src\site\resources
   [DEBUG]   (f) siteDirectory = c:\opt\furl\furlm2\trunk\src\site
   [DEBUG]   (f) stagingDirectory = C:\TEMP\stage
   [DEBUG]   (f) xdocDirectory = c:\opt\furl\furlm2\trunk\xdocs
   [DEBUG] -- end configuration --
   [INFO] [site:stage]
   [WARNING] Error loading report
 org.apache.maven.changelog.ChangeLogReport -
   AbstractMethodError: canGenerateReport()
   [WARNING] Error loading report
 org.apache.maven.changelog.FileActivityReport
   - AbstractMethodError: canGenerateReport()
   [WARNING] Error loading report org.apache.maven.plugin.jxr.JxrReport -
   AbstractMethodError: canGenerateReport()
   [WARNING] Error loading report
 org.apache.maven.plugin.taglist.TagListReport
   - AbstractMethodError: canGenerateReport()
   [DEBUG] Skipping disabled repository backup
   [DEBUG] Skipping disabled repository central
   [DEBUG] maven-stylus-skin: using locally installed snapshot
   [INFO]
  
 
   [ERROR] FATAL ERROR
   [INFO]
  
 
   [INFO]
  
 org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
   [INFO]
  
 
   [DEBUG] Trace
   java.lang.NoSuchMethodError:
  
 org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
  at
 org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)
  at
  
 org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:111)
  at
  
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
  at
  
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
  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

Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Mick Knutson
'
[INFO] Velocimacro :  VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in 
templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may 
NOT replace previous VM definitions
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be  
global in scope if allowed.

[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] artifact org.apache.maven.plugins:maven-project-info-reports-plugin: 
checking for updates from central
[INFO] snapshot 
org.codehaus.mojo:surefire-report-maven-plugin:2.0-beta-2-SNAPSHOT: checking 
for updates from mojo_snapshot
[INFO] snapshot 
org.codehaus.mojo:surefire-report-maven-plugin:2.0-beta-2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] snapshot org.codehaus.mojo:jdepend-maven-plugin:2.0-beta-1-SNAPSHOT: 
checking for updates from mojo_snapshot
[INFO] snapshot org.codehaus.mojo:jdepend-maven-plugin:2.0-beta-1-SNAPSHOT: 
checking for updates from apache.snapshots

[INFO] Preparing surefire-report:report
[INFO] No goals needed for project - skipping
[INFO] Preparing jdepend:generate
[INFO] No goals needed for project - skipping
[INFO] [site:site]
[WARNING] Error loading report org.apache.maven.changelog.ChangeLogReport - 
AbstractMethodError: canGenerateReport()
[WARNING] Error loading report org.apache.maven.changelog.FileActivityReport 
- AbstractMethodError: canGenerateReport()
[WARNING] Error loading report org.apache.maven.plugin.jxr.JxrReport - 
AbstractMethodError: canGenerateReport()
[WARNING] Error loading report org.apache.maven.plugin.taglist.TagListReport 
- AbstractMethodError: canGenerateReport()
[INFO] snapshot org.apache.maven.skins:maven-stylus-skin:1.0-SNAPSHOT: 
checking for updates from apache.snapshots
[INFO] 


[ERROR] FATAL ERROR
[INFO] 

[INFO] 
org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
[INFO] 


[INFO] Trace
java.lang.NoSuchMethodError: 
org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V

   at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)
   at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
   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:324)
   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)
[INFO] 


[INFO] Total time: 26 seconds
[INFO] Finished at: Thu Apr 06 10:32:36 PDT 2006
[INFO] Final Memory: 16M/30M
[INFO] 











---
Thank You
Mick Knutson

BASE logic, inc.
(415) 648-1804 (San Francisco, CA)
http://www.BASELogic.com

http://www.djmick.com
---





From: Wayne Fay [EMAIL PROTECTED]
Reply-To: Maven Users List users@maven.apache.org
To: Maven Users List users@maven.apache.org
Subject: Re: [m202] Still can't get site to work... Help please
Date: Thu, 6 Apr 2006 12:30:59 -0500

Try mvn -U site:site

Wayne

On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
 1. I don't know what the doxia is as I did not import it. How do I fix 
it

 please?
 Should I add that dependancy?


 ---
 Thank You
 Mick Knutson

 BASE logic, inc.
 (415) 648-1804 (San Francisco, CA)
 http://www.BASELogic.com

 http

Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Wayne Fay
] Still can't get site to work... Help please
 Date: Thu, 6 Apr 2006 12:30:59 -0500
 
 Try mvn -U site:site
 
 Wayne
 
 On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
   1. I don't know what the doxia is as I did not import it. How do I fix
 it
   please?
   Should I add that dependancy?
  
  
   ---
   Thank You
   Mick Knutson
  
   BASE logic, inc.
   (415) 648-1804 (San Francisco, CA)
   http://www.BASELogic.com
  
   http://www.djmick.com
   ---
  
  
  
  
   From: Wayne Fay [EMAIL PROTECTED]
   Reply-To: Maven Users List users@maven.apache.org
   To: Maven Users List users@maven.apache.org
   Subject: Re: [m202] Still can't get site to work... Help please
   Date: Thu, 6 Apr 2006 12:26:30 -0500
   
   Looks like you're using an old doxia? NoSuchMethodError would suggest
   that your version of doxia is missing a method or that signatures
   aren't proper.
   
   [DEBUG] Trace
   java.lang.NoSuchMethodError:
  
  org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
   at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)
   
   Wayne
   
   On 3/30/06, Mick Knutson [EMAIL PROTECTED] wrote:
 [INFO] No goals needed for project - skipping
 [DEBUG] com.furl:furl:pom:1.3 (selected for null)
 [DEBUG] Configuring mojo
 'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:stage' --
 [DEBUG]   (f) generateReports = true
 [DEBUG]   (f) generatedSiteDirectory =
 c:\opt\furl\furlm2\trunk\target\generated-site
 [DEBUG]   (f) localRepository = [local] - file://C:\Documents and
 Settings\mknutson\.m2\repository
 [DEBUG]   (f) outputDirectory = c:\opt\furl\furlm2\trunk\target\site
 [DEBUG]   (f) outputEncoding = ISO-8859-1
 [DEBUG]   (f) project =
 [EMAIL PROTECTED]
 [DEBUG]   (f) reactorProjects =
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.proj
 [EMAIL PROTECTED],
   [EMAIL PROTECTED],
 [EMAIL PROTECTED],
   org.apache.maven.project.Ma
 [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.project.MavenPro
 [EMAIL PROTECTED], [EMAIL PROTECTED]
 [DEBUG]   (f) reports =
 [EMAIL PROTECTED],
 [EMAIL PROTECTED], org.apache.maven.p
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED], or
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.report.proj
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.changelog.FileActivityRepor
 [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED],
 org.apache.maven.plugin.taglist.TagListReport@
 132021a, [EMAIL PROTECTED]
 [DEBUG]   (f) repositories = [[backup] -
 http://repo1.maven.org/maven2,
 [apache.snapshots] -
 http://cvs.apache.org/maven-snapshot-repository,
 [centr
 al] - http://repo1.maven.org/maven2]
 [DEBUG]   (f) resourcesDirectory =
 c:\opt\furl\furlm2\trunk\src\site\resources
 [DEBUG]   (f) siteDirectory = c:\opt\furl\furlm2\trunk\src\site
 [DEBUG]   (f) stagingDirectory = C:\TEMP\stage
 [DEBUG]   (f) xdocDirectory = c:\opt\furl\furlm2\trunk\xdocs
 [DEBUG] -- end configuration --
 [INFO] [site:stage]
 [WARNING] Error loading report
   org.apache.maven.changelog.ChangeLogReport -
 AbstractMethodError: canGenerateReport()
 [WARNING] Error loading report
   org.apache.maven.changelog.FileActivityReport
 - AbstractMethodError: canGenerateReport()
 [WARNING] Error loading report org.apache.maven.plugin.jxr.JxrReport
 -
 AbstractMethodError: canGenerateReport()
 [WARNING] Error loading report
   org.apache.maven.plugin.taglist.TagListReport
 - AbstractMethodError: canGenerateReport()
 [DEBUG] Skipping disabled repository backup
 [DEBUG] Skipping disabled repository central
 [DEBUG] maven-stylus-skin: using locally installed snapshot
 [INFO]

  
  
 [ERROR] FATAL ERROR
 [INFO]

  
  
 [INFO]

  
  org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
 [INFO]

  
  
 [DEBUG] Trace
 java.lang.NoSuchMethodError:

  
  org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
at
   org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)
at

  
  org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:111)
at

  
  org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
at

  
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531

Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Mick Knutson
I removed the site dependancy declaration in my pom, and it works for 
site:site


But I want to run site:stage and that does not seem to be found:
-
[INFO] Searching repository for plugin with prefix: 'site'.
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for 
updates from central
[INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for 
updates from central
[INFO] 


[ERROR] BUILD FAILURE
[INFO] 


[INFO] Required goal not found: site:stage
[INFO] 


[INFO] Trace
org.apache.maven.BuildFailureException: Required goal not found: site:stage
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1499)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:378
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:134)

   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:324)
   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)
[INFO] 


[INFO] Total time: 19 seconds
[INFO] Finished at: Thu Apr 06 11:02:09 PDT 2006
[INFO] Final Memory: 4M/7M
[INFO] 





---
Thank You
Mick Knutson

BASE logic, inc.
(415) 648-1804 (San Francisco, CA)
http://www.BASELogic.com

http://www.djmick.com
---





From: Wayne Fay [EMAIL PROTECTED]
Reply-To: Maven Users List users@maven.apache.org
To: Maven Users List users@maven.apache.org
Subject: Re: [m202] Still can't get site to work... Help please
Date: Thu, 6 Apr 2006 12:50:53 -0500

Try the following:
mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=myapp
mvn site:site

If this completes successfully, then you've probably got a problem in
your project's pom.

If it fails, then we can continue debugging.

Wayne


On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
 Seemed to download different stuff, but still same error:

 
 [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking 
for

 updates from central
 Downloading:
 
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.1/maven-compiler-plugin-2.0.1.pom

 1K downloaded
 Downloading:
 
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.1/maven-compiler-plugin-2.0.1.jar

 14K downloaded
 [INFO]
 


 [INFO] Building LS Furl Project
 [INFO]task-segment: [site:site]
 [INFO]
 


 [INFO] snapshot
 org.apache.maven.doxia:doxia-site-renderer:1.0-alpha-8-SNAPSHOT: 
checking

 for updates from mojo_snapshot
 [INFO] snapshot
 org.apache.maven.doxia:doxia-site-renderer:1.0-alpha-8-SNAPSHOT: 
checking

 for updates from snapshots
 [INFO] snapshot
 org.apache.maven.doxia:doxia-site-renderer:1.0-alpha-8-SNAPSHOT: 
checking

 for updates from apache.snapshots
 [INFO] snapshot org.apache.maven.doxia:doxia:1.0-alpha-8-SNAPSHOT: 
checking

 for updates from mojo_snapshot
 [INFO] snapshot org.apache.maven.doxia:doxia:1.0-alpha-8-SNAPSHOT: 
checking

 for updates from snapshots
 [INFO] snapshot org.apache.maven.doxia:doxia:1.0-alpha-8-SNAPSHOT: 
checking

 for updates from apache.snapshots
 [INFO] snapshot org.apache.maven.doxia:doxia-core:1.0-alpha-8-SNAPSHOT:
 checking for updates from mojo_snapshot
 [INFO] snapshot org.apache.maven.doxia:doxia-core:1.0-alpha-8-SNAPSHOT:
 checking for updates from snapshots
 [INFO] snapshot org.apache.maven.doxia:doxia-core:1.0-alpha-8-SNAPSHOT:
 checking for updates from apache.snapshots
 [INFO] snapshot

Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Wayne Fay
Run mvn -X site:stage and let us know what version of site plugin is
being used. It sounds like your version of the site plugin does not
contain the stage goal.

I don't use site:stage and I have no idea when it was added to the
plugin. If it was recent, then it might not have made its way to
ibiblio yet, and you will need to either add the snapshot repo to your
pom or pull the code and build it yourself.

Wayne

On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
 I removed the site dependancy declaration in my pom, and it works for
 site:site

 But I want to run site:stage and that does not seem to be found:
 -
 [INFO] Searching repository for plugin with prefix: 'site'.
 [INFO] org.apache.maven.plugins: checking for updates from central
 [INFO] org.codehaus.mojo: checking for updates from central
 [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for
 updates from central
 [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for
 updates from central
 [INFO]
 
 [ERROR] BUILD FAILURE
 [INFO]
 
 [INFO] Required goal not found: site:stage
 [INFO]
 
 [INFO] Trace
 org.apache.maven.BuildFailureException: Required goal not found: site:stage
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1499)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:378
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:134)
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:324)
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)
 [INFO]
 
 [INFO] Total time: 19 seconds
 [INFO] Finished at: Thu Apr 06 11:02:09 PDT 2006
 [INFO] Final Memory: 4M/7M
 [INFO]
 



 ---
 Thank You
 Mick Knutson

 BASE logic, inc.
 (415) 648-1804 (San Francisco, CA)
 http://www.BASELogic.com

 http://www.djmick.com
 ---




 From: Wayne Fay [EMAIL PROTECTED]
 Reply-To: Maven Users List users@maven.apache.org
 To: Maven Users List users@maven.apache.org
 Subject: Re: [m202] Still can't get site to work... Help please
 Date: Thu, 6 Apr 2006 12:50:53 -0500
 
 Try the following:
 mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=myapp
 mvn site:site
 
 If this completes successfully, then you've probably got a problem in
 your project's pom.
 
 If it fails, then we can continue debugging.
 
 Wayne
 
 
 On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
   Seemed to download different stuff, but still same error:
  
   
   [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking
 for
   updates from central
   Downloading:
  
 http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.1/maven-compiler-plugin-2.0.1.pom
   1K downloaded
   Downloading:
  
 http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.1/maven-compiler-plugin-2.0.1.jar
   14K downloaded
   [INFO]
  
 
   [INFO] Building LS Furl Project
   [INFO]task-segment: [site:site]
   [INFO]
  
 
   [INFO] snapshot
   org.apache.maven.doxia:doxia-site-renderer:1.0-alpha-8-SNAPSHOT:
 checking
   for updates from mojo_snapshot
   [INFO] snapshot
   org.apache.maven.doxia:doxia-site-renderer:1.0-alpha-8-SNAPSHOT:
 checking
   for updates from snapshots
   [INFO] snapshot
   org.apache.maven.doxia:doxia-site-renderer:1.0-alpha-8-SNAPSHOT:
 checking
   for updates from apache.snapshots
   [INFO] snapshot org.apache.maven.doxia:doxia:1.0-alpha-8-SNAPSHOT:
 checking
   for updates from mojo_snapshot
   [INFO] snapshot

Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Brett Porter
Correct, site:stage is a new feature in 2.0-beta-5, which will be
voted on today. I'll update the snapshots now.

- Brett

On 4/7/06, Wayne Fay [EMAIL PROTECTED] wrote:
 Run mvn -X site:stage and let us know what version of site plugin is
 being used. It sounds like your version of the site plugin does not
 contain the stage goal.

 I don't use site:stage and I have no idea when it was added to the
 plugin. If it was recent, then it might not have made its way to
 ibiblio yet, and you will need to either add the snapshot repo to your
 pom or pull the code and build it yourself.

 Wayne

 On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
  I removed the site dependancy declaration in my pom, and it works for
  site:site
 
  But I want to run site:stage and that does not seem to be found:
  -
  [INFO] Searching repository for plugin with prefix: 'site'.
  [INFO] org.apache.maven.plugins: checking for updates from central
  [INFO] org.codehaus.mojo: checking for updates from central
  [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for
  updates from central
  [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for
  updates from central
  [INFO]
  
  [ERROR] BUILD FAILURE
  [INFO]
  
  [INFO] Required goal not found: site:stage
  [INFO]
  
  [INFO] Trace
  org.apache.maven.BuildFailureException: Required goal not found: site:stage
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1499)
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:378
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:134)
 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:324)
 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)
  [INFO]
  
  [INFO] Total time: 19 seconds
  [INFO] Finished at: Thu Apr 06 11:02:09 PDT 2006
  [INFO] Final Memory: 4M/7M
  [INFO]
  
 
 
 
  ---
  Thank You
  Mick Knutson
 
  BASE logic, inc.
  (415) 648-1804 (San Francisco, CA)
  http://www.BASELogic.com
 
  http://www.djmick.com
  ---
 
 
 
 
  From: Wayne Fay [EMAIL PROTECTED]
  Reply-To: Maven Users List users@maven.apache.org
  To: Maven Users List users@maven.apache.org
  Subject: Re: [m202] Still can't get site to work... Help please
  Date: Thu, 6 Apr 2006 12:50:53 -0500
  
  Try the following:
  mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=myapp
  mvn site:site
  
  If this completes successfully, then you've probably got a problem in
  your project's pom.
  
  If it fails, then we can continue debugging.
  
  Wayne
  
  
  On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
Seemed to download different stuff, but still same error:
   

[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking
  for
updates from central
Downloading:
   
  http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.1/maven-compiler-plugin-2.0.1.pom
1K downloaded
Downloading:
   
  http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.1/maven-compiler-plugin-2.0.1.jar
14K downloaded
[INFO]
   
  
[INFO] Building LS Furl Project
[INFO]task-segment: [site:site]
[INFO]
   
  
[INFO] snapshot
org.apache.maven.doxia:doxia-site-renderer:1.0-alpha-8-SNAPSHOT:
  checking
for updates from mojo_snapshot
[INFO] snapshot
org.apache.maven.doxia:doxia-site-renderer:1.0-alpha-8-SNAPSHOT:
  checking

Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Wayne Fay
Thanks for the clarification, Brett.

In that case, Mick, you'll need to download and build/install locally
if you want to use site:stage.

Wayne


On 4/6/06, Brett Porter [EMAIL PROTECTED] wrote:
 Correct, site:stage is a new feature in 2.0-beta-5, which will be
 voted on today. I'll update the snapshots now.

 - Brett

 On 4/7/06, Wayne Fay [EMAIL PROTECTED] wrote:
  Run mvn -X site:stage and let us know what version of site plugin is
  being used. It sounds like your version of the site plugin does not
  contain the stage goal.
 
  I don't use site:stage and I have no idea when it was added to the
  plugin. If it was recent, then it might not have made its way to
  ibiblio yet, and you will need to either add the snapshot repo to your
  pom or pull the code and build it yourself.
 
  Wayne
 
  On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
   I removed the site dependancy declaration in my pom, and it works for
   site:site
  
   But I want to run site:stage and that does not seem to be found:
   -
   [INFO] Searching repository for plugin with prefix: 'site'.
   [INFO] org.apache.maven.plugins: checking for updates from central
   [INFO] org.codehaus.mojo: checking for updates from central
   [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking 
   for
   updates from central
   [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for
   updates from central
   [INFO]
   
   [ERROR] BUILD FAILURE
   [INFO]
   
   [INFO] Required goal not found: site:stage
   [INFO]
   
   [INFO] Trace
   org.apache.maven.BuildFailureException: Required goal not found: 
   site:stage
  at
   org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1499)
  at
   org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:378
  at
   org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:134)
  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:324)
  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)
   [INFO]
   
   [INFO] Total time: 19 seconds
   [INFO] Finished at: Thu Apr 06 11:02:09 PDT 2006
   [INFO] Final Memory: 4M/7M
   [INFO]
   
  
  
  
   ---
   Thank You
   Mick Knutson
  
   BASE logic, inc.
   (415) 648-1804 (San Francisco, CA)
   http://www.BASELogic.com
  
   http://www.djmick.com
   ---
  
  
  
  
   From: Wayne Fay [EMAIL PROTECTED]
   Reply-To: Maven Users List users@maven.apache.org
   To: Maven Users List users@maven.apache.org
   Subject: Re: [m202] Still can't get site to work... Help please
   Date: Thu, 6 Apr 2006 12:50:53 -0500
   
   Try the following:
   mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=myapp
   mvn site:site
   
   If this completes successfully, then you've probably got a problem in
   your project's pom.
   
   If it fails, then we can continue debugging.
   
   Wayne
   
   
   On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
 Seemed to download different stuff, but still same error:

 
 [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: 
 checking
   for
 updates from central
 Downloading:

   http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.1/maven-compiler-plugin-2.0.1.pom
 1K downloaded
 Downloading:

   http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.1/maven-compiler-plugin-2.0.1.jar
 14K downloaded
 [INFO]

   
 [INFO] Building LS Furl Project
 [INFO]task-segment: [site:site

Re: [m202] Still can't get site to work... Help please

2006-04-06 Thread Mick Knutson

Thanks.
I actually just tried, but I need 2.0.3/4 and I can't upgrade this week. I 
will re-visit next week.


---
Thank You
Mick Knutson

BASE logic, inc.
(415) 648-1804 (San Francisco, CA)
http://www.BASELogic.com

http://www.djmick.com
---





From: Wayne Fay [EMAIL PROTECTED]
Reply-To: Maven Users List users@maven.apache.org
To: Maven Users List users@maven.apache.org
Subject: Re: [m202] Still can't get site to work... Help please
Date: Thu, 6 Apr 2006 15:18:53 -0500

Thanks for the clarification, Brett.

In that case, Mick, you'll need to download and build/install locally
if you want to use site:stage.

Wayne


On 4/6/06, Brett Porter [EMAIL PROTECTED] wrote:
 Correct, site:stage is a new feature in 2.0-beta-5, which will be
 voted on today. I'll update the snapshots now.

 - Brett

 On 4/7/06, Wayne Fay [EMAIL PROTECTED] wrote:
  Run mvn -X site:stage and let us know what version of site plugin is
  being used. It sounds like your version of the site plugin does not
  contain the stage goal.
 
  I don't use site:stage and I have no idea when it was added to the
  plugin. If it was recent, then it might not have made its way to
  ibiblio yet, and you will need to either add the snapshot repo to your
  pom or pull the code and build it yourself.
 
  Wayne
 
  On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
   I removed the site dependancy declaration in my pom, and it works 
for

   site:site
  
   But I want to run site:stage and that does not seem to be found:
   
-

   [INFO] Searching repository for plugin with prefix: 'site'.
   [INFO] org.apache.maven.plugins: checking for updates from central
   [INFO] org.codehaus.mojo: checking for updates from central
   [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: 
checking for

   updates from central
   [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking 
for

   updates from central
   [INFO]
   


   [ERROR] BUILD FAILURE
   [INFO]
   


   [INFO] Required goal not found: site:stage
   [INFO]
   


   [INFO] Trace
   org.apache.maven.BuildFailureException: Required goal not found: 
site:stage

  at
   
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1499)

  at
   
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:378

  at
   
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:134)
  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:324)
  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)
   [INFO]
   


   [INFO] Total time: 19 seconds
   [INFO] Finished at: Thu Apr 06 11:02:09 PDT 2006
   [INFO] Final Memory: 4M/7M
   [INFO]
   


  
  
  
   ---
   Thank You
   Mick Knutson
  
   BASE logic, inc.
   (415) 648-1804 (San Francisco, CA)
   http://www.BASELogic.com
  
   http://www.djmick.com
   ---
  
  
  
  
   From: Wayne Fay [EMAIL PROTECTED]
   Reply-To: Maven Users List users@maven.apache.org
   To: Maven Users List users@maven.apache.org
   Subject: Re: [m202] Still can't get site to work... Help please
   Date: Thu, 6 Apr 2006 12:50:53 -0500
   
   Try the following:
   mvn -e archetype:create -DgroupId=com.mycompany.app 
-DartifactId=myapp

   mvn site:site
   
   If this completes successfully, then you've probably got a problem 
in

   your project's pom.
   
   If it fails, then we can continue debugging.
   
   Wayne
   
   
   On 4/6/06, Mick Knutson [EMAIL PROTECTED] wrote:
 Seemed to download different stuff, but still same error:

 
 [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: 
checking

   for
 updates

[m202] Still can't get site to work... Help please

2006-03-30 Thread Mick Knutson

[INFO] No goals needed for project - skipping
[DEBUG] com.furl:furl:pom:1.3 (selected for null)
[DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT:stage' --

[DEBUG]   (f) generateReports = true
[DEBUG]   (f) generatedSiteDirectory = 
c:\opt\furl\furlm2\trunk\target\generated-site
[DEBUG]   (f) localRepository = [local] - file://C:\Documents and 
Settings\mknutson\.m2\repository

[DEBUG]   (f) outputDirectory = c:\opt\furl\furlm2\trunk\target\site
[DEBUG]   (f) outputEncoding = ISO-8859-1
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG]   (f) reactorProjects = 
[EMAIL PROTECTED], 
[EMAIL PROTECTED], org.apache.maven.proj
[EMAIL PROTECTED], [EMAIL PROTECTED], 
[EMAIL PROTECTED], org.apache.maven.project.Ma
[EMAIL PROTECTED], [EMAIL PROTECTED], 
[EMAIL PROTECTED], 
org.apache.maven.project.MavenPro

[EMAIL PROTECTED], [EMAIL PROTECTED]
[DEBUG]   (f) reports = 
[EMAIL PROTECTED], 
[EMAIL PROTECTED], org.apache.maven.p
[EMAIL PROTECTED], 
[EMAIL PROTECTED], 
[EMAIL PROTECTED], or
[EMAIL PROTECTED], 
[EMAIL PROTECTED], 
org.apache.maven.report.proj
[EMAIL PROTECTED], 
[EMAIL PROTECTED], 
[EMAIL PROTECTED],
[EMAIL PROTECTED], 
[EMAIL PROTECTED], 
org.apache.maven.changelog.FileActivityRepor
[EMAIL PROTECTED], [EMAIL PROTECTED], 
[EMAIL PROTECTED], 
org.apache.maven.plugin.taglist.TagListReport@

132021a, [EMAIL PROTECTED]
[DEBUG]   (f) repositories = [[backup] - http://repo1.maven.org/maven2, 
[apache.snapshots] - http://cvs.apache.org/maven-snapshot-repository, 
[centr

al] - http://repo1.maven.org/maven2]
[DEBUG]   (f) resourcesDirectory = 
c:\opt\furl\furlm2\trunk\src\site\resources

[DEBUG]   (f) siteDirectory = c:\opt\furl\furlm2\trunk\src\site
[DEBUG]   (f) stagingDirectory = C:\TEMP\stage
[DEBUG]   (f) xdocDirectory = c:\opt\furl\furlm2\trunk\xdocs
[DEBUG] -- end configuration --
[INFO] [site:stage]
[WARNING] Error loading report org.apache.maven.changelog.ChangeLogReport - 
AbstractMethodError: canGenerateReport()
[WARNING] Error loading report org.apache.maven.changelog.FileActivityReport 
- AbstractMethodError: canGenerateReport()
[WARNING] Error loading report org.apache.maven.plugin.jxr.JxrReport - 
AbstractMethodError: canGenerateReport()
[WARNING] Error loading report org.apache.maven.plugin.taglist.TagListReport 
- AbstractMethodError: canGenerateReport()

[DEBUG] Skipping disabled repository backup
[DEBUG] Skipping disabled repository central
[DEBUG] maven-stylus-skin: using locally installed snapshot
[INFO] 


[ERROR] FATAL ERROR
[INFO] 

[INFO] 
org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V
[INFO] 


[DEBUG] Trace
java.lang.NoSuchMethodError: 
org.apache.maven.doxia.siterenderer.SiteRenderingContext.setTemplate(Ljava/lang/String;)V

   at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:386)
   at 
org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:111)
   at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
   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:324)
   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)
[INFO] 


[INFO] Total time: 11 seconds
[INFO] Finished at: Thu Mar 30 14:14:05 PST 2006
[INFO] Final Memory: 17M/30M
[INFO] 

Need Help, Please

2005-09-14 Thread Qin Ding
I am learning to use Maven.  Following the tutorial on serverside.com 
(http://www.theserverside.com/articles/article.tss?l=MavenMagic), to setup 
the directory structure like the folloing:

c:\sample-maven-project
src/config
  /myapp.properties
src/java
/com/myapp/MyApp.java
src/test
   /com/myapp/MyAppTest.java

After I do
maven java:compile

I got:

build:start:

java:prepare-filesystem:

java:compile:
[echo] Compiling to C:\Sample-Maven-Project/target/classes
[echo] No java source files to compile.
BUILD SUCCESSFUL
Total time: 3 seconds
Finished at: Wed Sep 14 14:29:47 CDT 2005

In my project.xml, I have build defined like this:
build
   nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
   sourceDirectory${basedir}/src/java/sourceDirectory
   unitTestSourceDirectory${basedir}/test/java/unitTestSourceDirectory
   unitTest
  includes
 include**/*Test.java/include
  /includes
   /unitTest

   resources
  resource
 directory${basedir}/src/conf/directory
 includes
include*.properties/include
 /includes
  /resource
   /resources
 /build

Why maven can't find the java source to compile?  Should I or where can I 
define the basedir?

Qin

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.



RE: Need Help, Please

2005-09-14 Thread Litton, Tom - CEPM
try droping the ${basedir}/ from the dirs.  like:
sourceDirectorysrc/java/sourceDirectory
unitTestSourceDirectorytest/java/unitTestSourceDirectory
directorysrc/conf/directory
 
-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 14, 2005 2:43 PM
To: Maven Users List
Subject: Need Help, Please


I am learning to use Maven.  Following the tutorial on serverside.com 
(http://www.theserverside.com/articles/article.tss?l=MavenMagic), to setup 
the directory structure like the folloing:

c:\sample-maven-project
src/config
  /myapp.properties
src/java
/com/myapp/MyApp.java
src/test
   /com/myapp/MyAppTest.java

After I do
maven java:compile

I got:

build:start:

java:prepare-filesystem:

java:compile:
[echo] Compiling to C:\Sample-Maven-Project/target/classes
[echo] No java source files to compile.
BUILD SUCCESSFUL
Total time: 3 seconds
Finished at: Wed Sep 14 14:29:47 CDT 2005

In my project.xml, I have build defined like this:
build
   nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
   sourceDirectory${basedir}/src/java/sourceDirectory
   unitTestSourceDirectory${basedir}/test/java/unitTestSourceDirectory
   unitTest
  includes
 include**/*Test.java/include
  /includes
   /unitTest

   resources
  resource
 directory${basedir}/src/conf/directory
 includes
include*.properties/include
 /includes
  /resource
   /resources
 /build

Why maven can't find the java source to compile?  Should I or where can I 
define the basedir?

Qin

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.



--
The information contained in this transmission is intended only for
the personal and confidential use of the designated recipients named
herein.  If the reader of this transmission is not the intended
recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this
transmission in error, and that any review, dissemination,
distribution, or copying of this transmission is strictly prohibited.
If you have received this communication in error, please notify the
sender and return and delete the original transmission immediately.
Thank you.


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



Re: Need Help, Please

2005-09-14 Thread John Casey

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

not entirely sure (my maven-1 is a bit rusty...), but try leaving off
the '${basedir}/' prefix for sourceDirectory and unitTestSourceDirectory.

HTH,

john

Qin Ding wrote:
| I am learning to use Maven.  Following the tutorial on serverside.com
| (http://www.theserverside.com/articles/article.tss?l=MavenMagic), to
setup
| the directory structure like the folloing:
|
| c:\sample-maven-project
| src/config
|   /myapp.properties
| src/java
| /com/myapp/MyApp.java
| src/test
|/com/myapp/MyAppTest.java
|
| After I do
| maven java:compile
|
| I got:
|
| build:start:
|
| java:prepare-filesystem:
|
| java:compile:
| [echo] Compiling to C:\Sample-Maven-Project/target/classes
| [echo] No java source files to compile.
| BUILD SUCCESSFUL
| Total time: 3 seconds
| Finished at: Wed Sep 14 14:29:47 CDT 2005
|
| In my project.xml, I have build defined like this:
| build
|nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
|sourceDirectory${basedir}/src/java/sourceDirectory
|unitTestSourceDirectory${basedir}/test/java/unitTestSourceDirectory
|unitTest
|   includes
|  include**/*Test.java/include
|   /includes
|/unitTest
|
|resources
|   resource
|  directory${basedir}/src/conf/directory
|  includes
| include*.properties/include
|  /includes
|   /resource
|/resources
|  /build
|
| Why maven can't find the java source to compile?  Should I or where can I
| define the basedir?
|
| Qin
|
- 


| This is a PRIVATE message. If you are not the intended recipient, please
| delete without copying and kindly advise us by e-mail of the mistake in
| delivery. NOTE: Regardless of content, this e-mail shall not operate to
| bind CSC to any order or other contract unless pursuant to explicit
| written agreement or government initiative expressly permitting the
use of
| e-mail for such purpose.
|
- 


|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDKINWK3h2CZwO/4URAlkOAJ9fAwdOksY7Cd1XYSnroHlDi9jzmwCgnPp2
KapzhfKpK5msLxFDcrEnhMM=
=cBdG
-END PGP SIGNATURE-

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



Re: Need Help, Please

2005-09-14 Thread Rob Dingwell
Try changing the sourceDirectory to src/java instead of /src/java. I 
think it may be searching from the root of the drive for your files.


Rob


Qin Ding wrote:


Tom:

I erased the ${basedir} as you suggested, but I still got No java source 
to compile. 


By the way, my Maven version is 1.0.2.

Qin

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.







Litton, Tom - CEPM Tom.Litton
@cepm-us.com
09/14/2005 02:54 PM
Please respond to Maven Users List

   To: Maven Users List users@maven.apache.org
   cc: 
   Subject:RE: Need Help, Please



try droping the ${basedir}/ from the dirs.  like:
sourceDirectorysrc/java/sourceDirectory
unitTestSourceDirectorytest/java/unitTestSourceDirectory
directorysrc/conf/directory

-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 14, 2005 2:43 PM
To: Maven Users List
Subject: Need Help, Please


I am learning to use Maven.  Following the tutorial on serverside.com 
(http://www.theserverside.com/articles/article.tss?l=MavenMagic), to setup 


the directory structure like the folloing:

c:\sample-maven-project
src/config
 /myapp.properties
src/java
   /com/myapp/MyApp.java
src/test
  /com/myapp/MyAppTest.java

After I do
maven java:compile

I got:

build:start:

java:prepare-filesystem:

java:compile:
   [echo] Compiling to C:\Sample-Maven-Project/target/classes
   [echo] No java source files to compile.
BUILD SUCCESSFUL
Total time: 3 seconds
Finished at: Wed Sep 14 14:29:47 CDT 2005

In my project.xml, I have build defined like this:
build
  nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
  sourceDirectory${basedir}/src/java/sourceDirectory
  unitTestSourceDirectory${basedir}/test/java/unitTestSourceDirectory
  unitTest
 includes
include**/*Test.java/include
 /includes
  /unitTest

  resources
 resource
directory${basedir}/src/conf/directory
includes
   include*.properties/include
/includes
 /resource
  /resources
/build

Why maven can't find the java source to compile?  Should I or where can I 
define the basedir?


Qin

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 


e-mail for such purpose.



--
The information contained in this transmission is intended only for
the personal and confidential use of the designated recipients named
herein.  If the reader of this transmission is not the intended
recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this
transmission in error, and that any review, dissemination,
distribution, or copying of this transmission is strictly prohibited.
If you have received this communication in error, please notify the
sender and return and delete the original transmission immediately.
Thank you.


-
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: Need Help, Please

2005-09-14 Thread David Jackman
It definitely isn't ${basedir}, and I would recommend leaving that in.

From what I can see, it should work for the source code, but the test
code wouldn't because the paths are different (src/test vs. test/java).
Can you double-check the paths you put in your email to make sure
they're correct for what's actually on your machine?

Also, the Maven standard (as outlined in
http://maven.apache.org/reference/conventions.html) is to put the main
source in src/main/java and the tests in src/test/java.  The article
used something different, and what they suggested should work as well as
long as the paths are the same everywhere.

..David.. 

-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 14, 2005 2:09 PM
To: Maven Users List
Subject: RE: Need Help, Please

Tom:

I erased the ${basedir} as you suggested, but I still got No java
source to compile. 

By the way, my Maven version is 1.0.2.

Qin


This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.







Litton, Tom - CEPM Tom.Litton
@cepm-us.com
09/14/2005 02:54 PM
Please respond to Maven Users List
 
To: Maven Users List users@maven.apache.org
cc: 
Subject:RE: Need Help, Please


try droping the ${basedir}/ from the dirs.  like:
sourceDirectorysrc/java/sourceDirectory
unitTestSourceDirectorytest/java/unitTestSourceDirectory
directorysrc/conf/directory
 
-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 14, 2005 2:43 PM
To: Maven Users List
Subject: Need Help, Please


I am learning to use Maven.  Following the tutorial on serverside.com
(http://www.theserverside.com/articles/article.tss?l=MavenMagic), to
setup 

the directory structure like the folloing:

c:\sample-maven-project
src/config
  /myapp.properties
src/java
/com/myapp/MyApp.java
src/test
   /com/myapp/MyAppTest.java

After I do
maven java:compile

I got:

build:start:

java:prepare-filesystem:

java:compile:
[echo] Compiling to C:\Sample-Maven-Project/target/classes
[echo] No java source files to compile.
BUILD SUCCESSFUL
Total time: 3 seconds
Finished at: Wed Sep 14 14:29:47 CDT 2005

In my project.xml, I have build defined like this:
build
   nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
   sourceDirectory${basedir}/src/java/sourceDirectory
 
unitTestSourceDirectory${basedir}/test/java/unitTestSourceDirectory
   unitTest
  includes
 include**/*Test.java/include
  /includes
   /unitTest

   resources
  resource
 directory${basedir}/src/conf/directory
 includes
include*.properties/include
 /includes
  /resource
   /resources
 /build

Why maven can't find the java source to compile?  Should I or where can
I define the basedir?

Qin


This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of 

e-mail for such purpose.




--
The information contained in this transmission is intended only for the
personal and confidential use of the designated recipients named herein.
If the reader of this transmission is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you are
hereby notified that you have received this transmission in error, and
that any review, dissemination, distribution, or copying of this
transmission is strictly prohibited.
If you have received this communication in error, please notify the
sender and return and delete the original transmission immediately.
Thank you.


-
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: Need Help, Please

2005-09-14 Thread Qin Ding
I removed ${basedir}, which has no positive effect.  I double check the 
directories 

src/java, which has com.myapp.MyApp.java
src/config, which has myapp.properties
test/java, which has com.myapp.MyAppTest.java

project.xml
build
   nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
   sourceDirectorysrc/java/sourceDirectory
   unitTestSourceDirectorytest/java/unitTestSourceDirectory
   unitTest
  includes
 include**/*Test.java/include
  /includes
   /unitTest

   resources
  resource
 directorysrc/config/directory
 includes
include*.properties/include
 /includes
  /resource
   /resources
 /build


This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.






David Jackman David.Jackman
@fastsearch.com
09/14/2005 03:22 PM
Please respond to Maven Users List
 
To: Maven Users List users@maven.apache.org
cc: 
Subject:RE: Need Help, Please


It definitely isn't ${basedir}, and I would recommend leaving that in.

From what I can see, it should work for the source code, but the test
code wouldn't because the paths are different (src/test vs. test/java).
Can you double-check the paths you put in your email to make sure
they're correct for what's actually on your machine?

Also, the Maven standard (as outlined in
http://maven.apache.org/reference/conventions.html) is to put the main
source in src/main/java and the tests in src/test/java.  The article
used something different, and what they suggested should work as well as
long as the paths are the same everywhere.

..David.. 

-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 14, 2005 2:09 PM
To: Maven Users List
Subject: RE: Need Help, Please

Tom:

I erased the ${basedir} as you suggested, but I still got No java
source to compile. 

By the way, my Maven version is 1.0.2.

Qin


This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.







Litton, Tom - CEPM Tom.Litton
@cepm-us.com
09/14/2005 02:54 PM
Please respond to Maven Users List
 
To: Maven Users List users@maven.apache.org
cc: 
Subject:RE: Need Help, Please


try droping the ${basedir}/ from the dirs.  like:
sourceDirectorysrc/java/sourceDirectory
unitTestSourceDirectorytest/java/unitTestSourceDirectory
directorysrc/conf/directory
 
-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 14, 2005 2:43 PM
To: Maven Users List
Subject: Need Help, Please


I am learning to use Maven.  Following the tutorial on serverside.com
(http://www.theserverside.com/articles/article.tss?l=MavenMagic), to
setup 

the directory structure like the folloing:

c:\sample-maven-project
src/config
  /myapp.properties
src/java
/com/myapp/MyApp.java
src/test
   /com/myapp/MyAppTest.java

After I do
maven java:compile

I got:

build:start:

java:prepare-filesystem:

java:compile:
[echo] Compiling to C:\Sample-Maven-Project/target/classes
[echo] No java source files to compile.
BUILD SUCCESSFUL
Total time: 3 seconds
Finished at: Wed Sep 14 14:29:47 CDT 2005

In my project.xml, I have build defined like this:
build
   nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
   sourceDirectory${basedir}/src/java/sourceDirectory
 
unitTestSourceDirectory${basedir}/test/java/unitTestSourceDirectory
   unitTest
  includes
 include**/*Test.java/include
  /includes
   /unitTest

   resources
  resource
 directory${basedir}/src/conf/directory
 includes
include*.properties/include
 /includes
  /resource
   /resources
 /build

Why maven can't find the java source to compile?  Should I or where can
I define the basedir?

Qin


This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us

RE: Need Help, Please

2005-09-14 Thread Leck, William C \(Bill\)
Try adding -X to the maven command.  You may want to direct that output
to a file.  -X is the debug option.  Examine the output carefully.  You
should see where Maven is trying to pickup the source from.  I suspect
your project.xml file is in the wrong location.  It should be in the
parent directory to src and test; which is where you should also be
executing maven from.  Also restore ${basedir}.  ${basedir} is
equivalent to PWD.

Bill

-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 14, 2005 2:33 PM
To: Maven Users List
Subject: RE: Need Help, Please

I removed ${basedir}, which has no positive effect.  I double check the 
directories 

src/java, which has com.myapp.MyApp.java
src/config, which has myapp.properties
test/java, which has com.myapp.MyAppTest.java

project.xml
build
   nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
   sourceDirectorysrc/java/sourceDirectory
   unitTestSourceDirectorytest/java/unitTestSourceDirectory
   unitTest
  includes
 include**/*Test.java/include
  /includes
   /unitTest

   resources
  resource
 directorysrc/config/directory
 includes
include*.properties/include
 /includes
  /resource
   /resources
 /build



This is a PRIVATE message. If you are not the intended recipient, please

delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use
of 
e-mail for such purpose.







David Jackman David.Jackman
@fastsearch.com
09/14/2005 03:22 PM
Please respond to Maven Users List
 
To: Maven Users List users@maven.apache.org
cc: 
Subject:RE: Need Help, Please


It definitely isn't ${basedir}, and I would recommend leaving that in.

From what I can see, it should work for the source code, but the test
code wouldn't because the paths are different (src/test vs. test/java).
Can you double-check the paths you put in your email to make sure
they're correct for what's actually on your machine?

Also, the Maven standard (as outlined in
http://maven.apache.org/reference/conventions.html) is to put the main
source in src/main/java and the tests in src/test/java.  The article
used something different, and what they suggested should work as well as
long as the paths are the same everywhere.

..David.. 

-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 14, 2005 2:09 PM
To: Maven Users List
Subject: RE: Need Help, Please

Tom:

I erased the ${basedir} as you suggested, but I still got No java
source to compile. 

By the way, my Maven version is 1.0.2.

Qin


This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.







Litton, Tom - CEPM Tom.Litton
@cepm-us.com
09/14/2005 02:54 PM
Please respond to Maven Users List
 
To: Maven Users List users@maven.apache.org
cc: 
Subject:RE: Need Help, Please


try droping the ${basedir}/ from the dirs.  like:
sourceDirectorysrc/java/sourceDirectory
unitTestSourceDirectorytest/java/unitTestSourceDirectory
directorysrc/conf/directory
 
-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 14, 2005 2:43 PM
To: Maven Users List
Subject: Need Help, Please


I am learning to use Maven.  Following the tutorial on serverside.com
(http://www.theserverside.com/articles/article.tss?l=MavenMagic), to
setup 

the directory structure like the folloing:

c:\sample-maven-project
src/config
  /myapp.properties
src/java
/com/myapp/MyApp.java
src/test
   /com/myapp/MyAppTest.java

After I do
maven java:compile

I got:

build:start:

java:prepare-filesystem:

java:compile:
[echo] Compiling to C:\Sample-Maven-Project/target/classes
[echo] No java source files to compile.
BUILD SUCCESSFUL
Total time: 3 seconds
Finished at: Wed Sep 14 14:29:47 CDT 2005

In my project.xml, I have build defined like this:
build
   nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
   sourceDirectory${basedir}/src/java/sourceDirectory
 
unitTestSourceDirectory${basedir}/test/java

RE: Need Help, Please

2005-09-14 Thread Qin Ding
)
at 
org.apache.maven.project.Repository.getScmType(Repository.java:115)
... 33 more
build:start:

java:prepare-filesystem:

java:compile:
[echo] Compiling to C:\My Projects\Sample-Maven-Project/target/classes
[echo]
==

  NOTE: Targetting JVM 1.4, classes
  will not run on earlier JVMs

==

BUILD SUCCESSFUL
Total time: 5 seconds
Finished at: Wed Sep 14 16:28:33 CDT 2005




This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.






Leck, William C \(Bill\) wleck
@avaya.com
09/14/2005 03:56 PM
Please respond to Maven Users List
 
To: Maven Users List users@maven.apache.org
cc: 
Subject:RE: Need Help, Please


Try adding -X to the maven command.  You may want to direct that output
to a file.  -X is the debug option.  Examine the output carefully.  You
should see where Maven is trying to pickup the source from.  I suspect
your project.xml file is in the wrong location.  It should be in the
parent directory to src and test; which is where you should also be
executing maven from.  Also restore ${basedir}.  ${basedir} is
equivalent to PWD.

Bill

-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 14, 2005 2:33 PM
To: Maven Users List
Subject: RE: Need Help, Please

I removed ${basedir}, which has no positive effect.  I double check the 
directories 

src/java, which has com.myapp.MyApp.java
src/config, which has myapp.properties
test/java, which has com.myapp.MyAppTest.java

project.xml
build
   nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress
   sourceDirectorysrc/java/sourceDirectory
   unitTestSourceDirectorytest/java/unitTestSourceDirectory
   unitTest
  includes
 include**/*Test.java/include
  /includes
   /unitTest

   resources
  resource
 directorysrc/config/directory
 includes
include*.properties/include
 /includes
  /resource
   /resources
 /build



This is a PRIVATE message. If you are not the intended recipient, please

delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use
of 
e-mail for such purpose.







David Jackman David.Jackman
@fastsearch.com
09/14/2005 03:22 PM
Please respond to Maven Users List
 
To: Maven Users List users@maven.apache.org
cc: 
Subject:RE: Need Help, Please


It definitely isn't ${basedir}, and I would recommend leaving that in.

From what I can see, it should work for the source code, but the test
code wouldn't because the paths are different (src/test vs. test/java).
Can you double-check the paths you put in your email to make sure
they're correct for what's actually on your machine?

Also, the Maven standard (as outlined in
http://maven.apache.org/reference/conventions.html) is to put the main
source in src/main/java and the tests in src/test/java.  The article
used something different, and what they suggested should work as well as
long as the paths are the same everywhere.

..David.. 

-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 14, 2005 2:09 PM
To: Maven Users List
Subject: RE: Need Help, Please

Tom:

I erased the ${basedir} as you suggested, but I still got No java
source to compile. 

By the way, my Maven version is 1.0.2.

Qin


This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.







Litton, Tom - CEPM Tom.Litton
@cepm-us.com
09/14/2005 02:54 PM
Please respond to Maven Users List
 
To: Maven

RE: Need Help, Please

2005-09-14 Thread Leck, William C \(Bill\)
Notice this error in you stack trace.   Caused by:
java.lang.IllegalArgumentException: repository connection must 
start
with scm[delim]

Somewhere it is trying to pick-up an SCM connection.

Have you defined a build.properties in your home directory (BTW, home
directory for XP, as far as Apache is concerned, is C:\Documents and
Setting\user id.  If you are behind a firewall, you will need to add
the following lines in a build.properties file in your home directory:

maven.proxy.host=URL to proxy
maven.proxy.port=port used by proxy

Have you also done something like maven.repo.repository.X in the
build.properties file?  Try removing these lines and allow Maven to
pickup the files it needs from the remote repositories.

The order of precedence for Maven to pickup properties is:

1) Built-in properties
2) ${basedir}/project.properties
3) ${basedir}/build.properties
4) ${user.home}/build.properties
5) System properties (e.g. -Dsome.property=x)

Additionally the only valid protocols supported for repos are scp://,
sftp://, ftp://, file://, scpexe://

Hope this helps

-Original Message-
From: Qin Ding [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 14, 2005 3:31 PM
To: Maven Users List
Subject: RE: Need Help, Please

The problem is I carelessly named my project.xml file as
project.xml.xml.  
After I correct the file name, I got the following error:

C:\My Projects\Sample-Maven-Projectmaven java:compile
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

[MethodExpression] Cannot evaluate expression
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at 
org.apache.commons.betwixt.expression.MethodExpression.evaluate(Metho
dExpression.java:96)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(Abstrac
tBeanWriter.java:658)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(A
bstractBeanWriter.java:539)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWr
iter.java:481)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(Abstrac
tBeanWriter.java:643)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(A
bstractBeanWriter.java:539)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWr
iter.java:513)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWr
iter.java:233)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(Abstrac
tBeanWriter.java:630)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(A
bstractBeanWriter.java:539)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWr
iter.java:513)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWr
iter.java:233)
at 
org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWr
iter.java:162)
at 
org.apache.commons.betwixt.io.BeanWriter.write(BeanWriter.java:217)
at 
org.apache.maven.MavenUtils.getProjectString(MavenUtils.java:432)
at 
org.apache.maven.MavenUtils.getInterpolatedPOM(MavenUtils.java:383)
at 
org.apache.maven.MavenUtils.getJellyProject(MavenUtils.java:360)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:122)
at 
org.apache.maven.MavenSession.initializeRootProject(MavenSession.java
:232)
at
org.apache.maven.MavenSession.initialize(MavenSession.java:172)
at org.apache.maven.cli.App.doMain(App.java:475)
at org.apache.maven.cli.App.main(App.java:1239)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
Caused by: java.lang.IllegalArgumentException: repository connection
must 
start
with scm[delim]
at 
org.apache.maven.project.Repository.splitSCMConnection(Repository.jav
a:244)
at 
org.apache.maven.project.Repository.getCvsModule(Repository.java:216)

at 
org.apache.maven.project.Repository.getCvsModule(Repository.java:144)

... 33 more
[MethodExpression] Cannot evaluate expression
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0

Help please.

2003-12-31 Thread Mostashfi, Ali
Hello,

Anyone know how one can control the left-hand-side navigation bar's width of
the site generated files?  

Also, anyone have any problems with the checkstyle-report.html file?  It
doesn't get generated for my setup, and I have not been able to find out
where anything gets set for that portion.

Lastly, does anyone know how I can configure maven with following
source-code's directory structure?

The source directory is:
.
|-- project.properties
|-- project.xml
|-- project
|`-- src
||`-- com
| |`-- sra
|  |`-- app
|   |`-- App.java
|
|`-- unit_test
|`-- src
 |`-- com
  |`-- sra
   |`-- app
|-- AppTest.java

I apologize if my questions are too basic, but I have been having a lot of
difficulty with this.

Best wishes,
-AM




Re: Help please.

2003-12-31 Thread Keith Irwin

On Wed, 2003-12-31 at 08:34, Mostashfi, Ali wrote:
 Hello,

Hi!

 Anyone know how one can control the left-hand-side navigation bar's width of
 the site generated files?  

I'm not sure.  There's a way to work with stylesheets.  You might check
the site plugin documentation page.  I haven't gotten to this type of
thing myself yet.

Also:

http://maven.apache.org/reference/user-guide.html#Stylesheets

 Also, anyone have any problems with the checkstyle-report.html file?  It
 doesn't get generated for my setup, and I have not been able to find out
 where anything gets set for that portion.

I've got the same problem.  I just removed it from my list of reports
because I don't really need it.

 Lastly, does anyone know how I can configure maven with following
 source-code's directory structure?

Okay, this I might be able to answer, though it's a guess:

 The source directory is:
 .
 |-- project.properties
 |-- project.xml
 |-- project
 |`-- src
 ||`-- com
 | |`-- sra
 |  |`-- app
 |   |`-- App.java
 |
 |`-- unit_test
 |`-- src
  |`-- com
   |`-- sra
|`-- app
 |-- AppTest.java

In your project.xml file, you'll need something like:

  sourceDirectory
project/src
  /sourceDirectory

  unitTestSourceDirectory
project/unit_test/src
  /unitTestSourceDirectory

The problem is that the unit test directory falls under the src
directory, so I think you'll have to set some includes and excludes
in the unitTest element of the project.xml. I'm not sure how to fix
the sourceDirectory as I don't see any properties for dealing with
that.  Is it impossible to re-arrange your source code?

There's also the resources element, but I've not seen any explanation
anywhere about what that does or what that means.

Finally, if all else fails, maybe including something in maven.xml will
work, though I have to admit, if you have to do a lot in there, you
might as well use ant, eh?  :)

Your best bet is to re-arrange the source code and be done with it. ;)

Good luck!

Keith

 I apologize if my questions are too basic, but I have been having a lot of
 difficulty with this.

 Best wishes,
 -AM
 
 


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