site deploy SiteToolException: Error parsing site descriptor
We start getting this error today. Anyone know what causes this error? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] SiteToolException: Error parsing site descriptor Expected root element 'project' but found 'html' (position: START_TAG seen ...html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en... @7:68) [INFO] [INFO] For more information, run Maven with the -e switch Thanks. LJ
Re: Problem with SSHEXEC Ant Task
You should use 1.7.1 rather than 1.6.5. There was a bug in 1.6.x that stdout after sshexec was executed will disappear. LJ On Fri, Nov 7, 2008 at 1:15 AM, Baeriswyl Kuno - Extern (IT-BA-MV) [EMAIL PROTECTED] wrote: hello, had the same problem recently: plugin artifactIdmaven-antrun-plugin/artifactId dependencies dependency groupIdant/groupId artifactIdant-jsch/artifactId version1.6.5/version /dependency dependency groupIdjsch/groupId artifactIdjsch/artifactId version0.1.29/version /dependency /dependencies /plugin Kuno -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 7. November 2008 09:35 An: Maven Users List Betreff: Re: Problem with SSHEXEC Ant Task I downloaded the JAR file (jsch.jar) into my ant\lib...What other JAR files are needed? Any ideas? Maven does not know about nor care about your Ant installation. The only jar files it cares about are those which you have specified in the pom file as dependencies or plugins, and nearly all of them are located in your repo cache. You probably need to add the jsch artifact as a dependency to the maven-antrun-plugin in your pom. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with SSHEXEC Ant Task
Try specify version number 1.3 for artifactIdmaven-antrun-
plugin/artifactId
Thanks.
LJ
On Fri, Nov 7, 2008 at 12:51 PM, Durbha, Praveen (GE Healthcare)
[EMAIL PROTECTED] wrote:
Kuno/Wayne,
I am able to get it to work using 1.6.5 only problem is, like L.J
mentioned, any echo statements after the command is executed are not
executed.
sshexec host=gbi-test username=Administrator password=Gbi123Test123
trust=true command=\dev\install.exe -i silent failonerror=true
outputproperty=installprogress/
echo message=Commencing installation .../
echo message=${installprogress}/
However, the build fails when the dependency is changed to 1.7.1 since the
ant jars in the maven repository haven't been upgarded to this
version..correct?
Thanks!
-Original Message-
From: L. J. [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 11:37 AM
To: Maven Users List
Subject: Re: Problem with SSHEXEC Ant Task
You should use 1.7.1 rather than 1.6.5. There was a bug in 1.6.x that
stdout after sshexec was executed will disappear.
LJ
On Fri, Nov 7, 2008 at 1:15 AM, Baeriswyl Kuno - Extern (IT-BA-MV)
[EMAIL PROTECTED] wrote:
hello, had the same problem recently:
plugin
artifactIdmaven-antrun-plugin/artifactId
dependencies
dependency
groupIdant/groupId
artifactIdant-jsch/artifactId
version1.6.5/version
/dependency
dependency
groupIdjsch/groupId
artifactIdjsch/artifactId
version0.1.29/version
/dependency
/dependencies
/plugin
Kuno
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 7. November 2008 09:35
An: Maven Users List
Betreff: Re: Problem with SSHEXEC Ant Task
I downloaded the JAR file (jsch.jar) into my ant\lib...What other
JAR files are needed? Any ideas?
Maven does not know about nor care about your Ant installation. The
only jar files it cares about are those which you have specified in
the pom file as dependencies or plugins, and nearly all of them are
located in your repo cache.
You probably need to add the jsch artifact as a dependency to the
maven-antrun-plugin in your pom.
Wayne
-
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: Ant-based Mojos using Ant 1.6.5
try specifying 1.3 in your maven-antrun-plugin if you are using it. Thanks. LJ On Fri, Nov 7, 2008 at 12:23 PM, Edelson, Justin [EMAIL PROTECTED] wrote: Currently, it seems that the support in Maven for writing plugins in Ant uses Ant 1.6.5. Is there a plan to upgrade this to 1.7.1? I traced the depencency back to plexus-ant-factory, but it looks like this component was deleted from Subversion about a month ago (http://fisheye.codehaus.org/changelog/plexus/plexus-component-factories /trunk/plexus-ant-factory?cs=7731http://fisheye.codehaus.org/changelog/plexus/plexus-component-factories/trunk/plexus-ant-factory?cs=7731 ). Thanks, Justin Edelson VP, Platform Engineering MTV Networks Digital
Re: Question on release plugin
That sounds a normal Maven behavior as it should pull jar from your local/remote repo rather than target during any build cycle. On Tue, Oct 7, 2008 at 6:25 AM, M. Hansen [EMAIL PROTECTED] wrote: Hi, In svn we have our projects organized in a flat hierarchy like this: myproject/myartifactparent/pom.xml myproject/myartifactjar/pom.xml myproject/myartifactear/pom.xml myproject/myartifactwar/pom.xml myproject/myartifactparent/pom.xml looks like this: ... modelVersion4.0.0/modelVersion groupIdmygroup/groupId artifactIdmyartifactparent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version modules module../myartifactjar/module module../myartifactwar/module module../myartifactear/module /modules ... My question is the following. To build the whole project we use myproject/myartifactparent/pom.xml and we issue 'mvn install'. We would like to be able to just use 'mvn package' but apparently it not enough as module dependencies specified in the modules section of myproject/myartifactparent/pom.xml are not honoured as we thought. If myartifactwar depends on myartifactjar, myartifactjar is fetched from the Maven repository and not from the target directory of the myartifactjar directory that has just been build. Is this the right behaviour of Maven? If so it would be a nice feature if one could build a multiproject without being forced to install artifacts locally. /MH
Re: Problem with release plugin
during release:prepare, the plugin should prompt you for the next SNAPSHOT
version of your child2, that's where you can change the version number.
On Mon, Oct 6, 2008 at 6:00 AM, Samuli Saarinen
[EMAIL PROTECTED]wrote:
Hello,
I'm using maven 2.0.9 with a multi-module project and try to make a release
using maven-release-plugin. My project structure is following:
parent
- child1
- child2
parent pom.xml:
project
...
version1.0.2-SNAPSHOT/version
modules
modulechild1/module
modulechild2/module
/modules
...
/project
child1 pom.xml:
project
...
version1.0.3-SNAPSHOT/version
parent
groupIdcom.foo.test/groupId
artifactIdtest/artifactId
version1.0.2-SNAPSHOT/version
/parent
...
/project
child2 pom.xml:
project
...
version1.0.2-SNAPSHOT/version
parent
groupIdcom.foo.test/groupId
artifactIdtest/artifactId
version1.0.2-SNAPSHOT/version
/parent
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdchild1/artifactId
version1.0.3-SNAPSHOT/version
/dependency
/dependencies
...
/project
after I prepare a release the pom.xml.tag for child2 has dependency to
1.0.3 version of child1 as expected but pom.xml.next for child2 contains
dependency to 1.0.3-SNAPSHOT of child1 although the next development version
for child1 is specified as 1.0.4-SNAPSHOT.
Is this the intended behaviour or a bug?
Thanks in advance,
Samuli
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible bug when using ant:run in build configuration
compile is part of mvn package and install build lifecycle.
On Tue, Sep 16, 2008 at 8:44 AM, dmcgeown [EMAIL PROTECTED] wrote:
Hello, im having a problem when trying to run some ant tasks within the
build
configuration. I basically using Ant to generate a build number. However
when i specify the phase to compile then then run 'mvn package' or 'mvn
install' the ant tasks execute even tough they are specified to only run
with the compile phase. Im i doing something stupid here or whats going on.
Pleasse refer to my code snippet below.
Thanks in advance
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.2/version
inheritedfalse/inherited
executions
execution
idcreate.buildnumber/id
phasecompile/phase
goals
goalrun/goal
/goals
configuration
tasks
property name=common value=./system_core/Common/src /
tstamp
format property=time.stamp pattern=MM/dd/ hh:mm aa/
/tstamp
buildnumber file=${basedir}/buildfiles/build.properties/
delete file=${common}/java/com/mycompany/common/Build.java /
copy file=${basedir}/buildfiles/Build.java
todir=${common}/java/com/mycompany/common/ /
loadproperties srcFile=${basedir}/buildfiles/build.properties/
property name=version.build.date value=v${myapp-enterprise-version}
(Build: ${build.number}) ) Date: ${time.stamp}) /
echo message=${version.build.date}/
/tasks
/configuration
/execution
/executions
/plugin
--
View this message in context:
http://www.nabble.com/Possible-bug-when-using-ant%3Arun-in-build-configuration-tp19514566p19514566.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-antrun-plugin
I have the same problem, does anyone get it work?
Thanks.
LJ
On Thu, Oct 4, 2007 at 4:07 AM, Andreas Rudolf [EMAIL PROTECTED] wrote:
Hi,
I tried to use this feature, but with no success.
Neither if nor unless work.
I tried Version 1.1 and 1.2-SNAPSHOT of antrun-plugin.
Is there somewhere a successstory about this tasks attributes?
Regards
Andreas
Michael Meyer-5 wrote:
Hi
in the example[1] they use unless=maven.test.skip and not
unless=${maven.test.skip}. Just a guess...
Cheers, michael
[1]
http://maven.apache.org/plugins/maven-antrun-plugin/examples/tasksAttributes.html
[EMAIL PROTECTED] wrote:
Do the if and/or unless attributes of the tasks element actually work?
It seems that my ant code gets run no matter what.
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseinstall/phase
configuration
tasks if=${XX} !-- runs even if i change to
unless
--
echoEcho here/echo
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
Robert Egan
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended
solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon
this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
--
Michael Meyer | [EMAIL PROTECTED]
phone +41-44-247 79 12 | fax +41-44-247 70 75
Netcetera AG | 8040 Zürich | Switzerland | http://netcetera.ch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/maven-antrun-plugin-tf4272816s177.html#a13037744
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: How to make Continuum ignore the failed junit tests and continue with the build?
-Dmaven.tests.ignore.failure=true On Feb 7, 2008 1:00 PM, Tawfik, Sameh E [EMAIL PROTECTED] wrote: 1. Even though the build was not complete because of the failed junit tests in on of the sub modules, Continuum sent an email indicating the build is successful as follow: [continuum] BUILD SUCCESSFUL: MB1C 1.0 - Build Def: default maven2 buildDefinition In the build output results, the following is displayed: Results : Tests in error: Tests run: 502, Failures: 0, Errors: 2, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to C:\Auto_Builds\working-directory\81\mb1c-dataaccess\target\surefire-repo rts for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 9 minutes 48 seconds [INFO] Finished at: Thu Feb 07 12:35:57 PST 2008 [INFO] Final Memory: 18M/48M [INFO] 2. My project has a parent pom.xml and multiple sub modules, and the build stops when one of the junit tests fails, so is there is a way where I can instruct Continuum to ignore the tests results and continue with the build? We need to know about all the failed tests from all the modules from a complete run, instead one at a time. Thanks, Sameh This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
Creating new user in Continuum 1.1I
Hi, Just want to see if anyone else having this problem. I can only create admin user during the initial installation. After that, whatever the users I created, it says that either the username or password is incorrect while trying to log in. Thanks. LJ
Re: 1.1-beta-4 Out of Memory
I have 22 projects. I run Continuum in AIX so not sure if wrapper.conf is used because I don't see one under bin directory. I don't have a lot build results because this is a fresh 1.1-beta-4installation. Thanks. LJ On 10/31/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: How many projects in your instance? How many memory allowed? it is defined in wrapper.conf Do you have lot of build results by projects? Emmanuel L. J. a écrit : Does anyone have the same problem? 2007-10-31 07:47:49,618 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Executing: /bin/sh -c 'cd /apps/build/continuum-1.1-beta-4/apps/continuum/working-directory/19 cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/home/services/cvs/np -q log -d 2007-10-30 17:20:05-07002007-10-31 07:47:49-0700' 2007-10-31 07:47:49,618 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Working directory: /apps/build/continuum-1.1-beta-4/apps/continuum/working-directory/19 JVMDUMP006I Processing Dump Event systhrow, detail java/lang/OutOfMemoryError - Please Wait. JVMDUMP007I JVM Requesting Snap Dump using '/apps/build/continuum- 1.1-beta-4 /bin/Snap0010.20071031.145834.20730.trc' JVMDUMP010I Snap Dump written to /apps/build/continuum-1.1-beta-4 /bin/Snap0010.20071031.145834.20730.trc JVMDUMP007I JVM Requesting Heap Dump using '/apps/build/continuum- 1.1-beta-4 /bin/heapdump.20071031.145834.20730.phd' JVMDUMP010I Heap Dump written to /apps/build/continuum-1.1-beta-4 /bin/heapdump.20071031.145834.20730.phd JVMDUMP007I JVM Requesting Java Dump using '/apps/build/continuum- 1.1-beta-4 /bin/javacore.20071031.145834.20730.txt' JVMDUMP010I Java Dump written to /apps/build/continuum-1.1-beta-4 /bin/javacore.20071031.145834.20730.txt JVMDUMP013I Processed Dump Event systhrow, detail java/lang/OutOfMemoryError. 2007-10-31 07:58:51,300 [Thread-7] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult( FutureTask.java:299) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get ( FutureTask.java:128) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask (ThreadedTaskQueueExecutor.java:165) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run (ThreadedTaskQueueExecutor.java:127) Caused by: java.lang.OutOfMemoryError at java.lang.StringBuffer.ensureCapacityImpl(StringBuffer.java :386) at java.lang.StringBuffer.append(StringBuffer.java:234) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsLogListener.messageSent (CvsLogListener.java:63) at org.netbeans.lib.cvsclient.event.MessageEvent.fireEvent( MessageEvent.java:109) at org.netbeans.lib.cvsclient.event.EventManager.fireCVSEvent( EventManager.java:127) at org.netbeans.lib.cvsclient.response.MessageResponse.process( MessageResponse.java:59) at org.netbeans.lib.cvsclient.Client.handleResponse(Client.java :570) at org.netbeans.lib.cvsclient.Client.processRequests(Client.java :520) at org.netbeans.lib.cvsclient.command.log.LogCommand.execute( LogCommand.java:132) at org.netbeans.lib.cvsclient.Client.executeCommand(Client.java :629) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.executeCommand (CvsConnection.java:94) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.processCommand (CvsConnection.java:478) at org.apache.maven.scm.provider.cvslib.cvsjava.command.changelog.CvsJavaChangeLogCommand.executeCvsCommand (CvsJavaChangeLogCommand.java:54) at org.apache.maven.scm.provider.cvslib.command.changelog.AbstractCvsChangeLogCommand.executeChangeLogCommand (AbstractCvsChangeLogCommand.java:109) at org.apache.maven.scm.provider.cvslib.command.changelog.AbstractCvsChangeLogCommand.executeChangeLogCommand (AbstractCvsChangeLogCommand.java:61) at org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand (AbstractChangeLogCommand.java:101) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand ( AbstractUpdateCommand.java:75) at org.apache.maven.scm.command.AbstractCommand.execute( AbstractCommand.java:58) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.executeCommand ( AbstractCvsScmProvider.java:521) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.update( AbstractCvsScmProvider.java:659) at org.apache.maven.scm.provider.AbstractScmProvider.update( AbstractScmProvider.java
Re: 1.1-beta-4 Out of Memory
Ok, here is what I have in the plexus.sh PLEXUS_OPTS=$PLEXUS_OPTS -Xmx512m Thanks. LJ On 10/31/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: You use plexus.sh to start Continuum? In this case, the max memory to use is configured in it. Emmanuel L. J. a écrit : I have 22 projects. I run Continuum in AIX so not sure if wrapper.conf is used because I don't see one under bin directory. I don't have a lot build results because this is a fresh 1.1-beta-4installation. Thanks. LJ On 10/31/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: How many projects in your instance? How many memory allowed? it is defined in wrapper.conf Do you have lot of build results by projects? Emmanuel L. J. a écrit : Does anyone have the same problem? 2007-10-31 07:47:49,618 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Executing: /bin/sh -c 'cd /apps/build/continuum-1.1-beta-4/apps/continuum/working-directory/19 cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/home/services/cvs/np -q log -d 2007-10-30 17:20:05-07002007-10-31 07:47:49-0700' 2007-10-31 07:47:49,618 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Working directory: /apps/build/continuum-1.1-beta-4/apps/continuum/working-directory/19 JVMDUMP006I Processing Dump Event systhrow, detail java/lang/OutOfMemoryError - Please Wait. JVMDUMP007I JVM Requesting Snap Dump using '/apps/build/continuum- 1.1-beta-4 /bin/Snap0010.20071031.145834.20730.trc' JVMDUMP010I Snap Dump written to /apps/build/continuum-1.1-beta-4 /bin/Snap0010.20071031.145834.20730.trc JVMDUMP007I JVM Requesting Heap Dump using '/apps/build/continuum- 1.1-beta-4 /bin/heapdump.20071031.145834.20730.phd' JVMDUMP010I Heap Dump written to /apps/build/continuum-1.1-beta-4 /bin/heapdump.20071031.145834.20730.phd JVMDUMP007I JVM Requesting Java Dump using '/apps/build/continuum- 1.1-beta-4 /bin/javacore.20071031.145834.20730.txt' JVMDUMP010I Java Dump written to /apps/build/continuum-1.1-beta-4 /bin/javacore.20071031.145834.20730.txt JVMDUMP013I Processed Dump Event systhrow, detail java/lang/OutOfMemoryError. 2007-10-31 07:58:51,300 [Thread-7] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult( FutureTask.java:299) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get ( FutureTask.java:128) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask (ThreadedTaskQueueExecutor.java:165) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run (ThreadedTaskQueueExecutor.java:127) Caused by: java.lang.OutOfMemoryError at java.lang.StringBuffer.ensureCapacityImpl(StringBuffer.java :386) at java.lang.StringBuffer.append(StringBuffer.java:234) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsLogListener.messageSent (CvsLogListener.java:63) at org.netbeans.lib.cvsclient.event.MessageEvent.fireEvent( MessageEvent.java:109) at org.netbeans.lib.cvsclient.event.EventManager.fireCVSEvent( EventManager.java:127) at org.netbeans.lib.cvsclient.response.MessageResponse.process ( MessageResponse.java:59) at org.netbeans.lib.cvsclient.Client.handleResponse( Client.java :570) at org.netbeans.lib.cvsclient.Client.processRequests( Client.java :520) at org.netbeans.lib.cvsclient.command.log.LogCommand.execute( LogCommand.java:132) at org.netbeans.lib.cvsclient.Client.executeCommand( Client.java :629) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.executeCommand (CvsConnection.java:94) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.processCommand (CvsConnection.java:478) at org.apache.maven.scm.provider.cvslib.cvsjava.command.changelog.CvsJavaChangeLogCommand.executeCvsCommand (CvsJavaChangeLogCommand.java:54) at org.apache.maven.scm.provider.cvslib.command.changelog.AbstractCvsChangeLogCommand.executeChangeLogCommand (AbstractCvsChangeLogCommand.java:109) at org.apache.maven.scm.provider.cvslib.command.changelog.AbstractCvsChangeLogCommand.executeChangeLogCommand (AbstractCvsChangeLogCommand.java:61) at org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand (AbstractChangeLogCommand.java:101) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand ( AbstractUpdateCommand.java:75) at org.apache.maven.scm.command.AbstractCommand.execute( AbstractCommand.java:58
javadoc error from 2.0.4 to 2.0.6/2.0.7
I run mvn javadoc:javadoc with 2.0.6 and 2.0.7, both give me the following error. It works fine if I use 2.0.4. Has anyone seen this error before? Thanks. LJ [INFO] [javadoc:javadoc] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [DEBUG] Trace java.util.NoSuchElementException at java.util.StringTokenizer.nextToken(StringTokenizer.java(Compiled Code)) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocVersion( AbstractJavadocMojo.java:2959) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport (AbstractJavadocMojo.java:1085) at org.apache.maven.plugin.javadoc.JavadocReport.generate( JavadocReport.java:131) at org.apache.maven.plugin.javadoc.JavadocReport.execute( JavadocReport.java:219) at org.apache.maven.plugin.DefaultPluginManager.executeMojo ( DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal ( DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures( DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute ( DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main (MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke ( NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) 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)
Re: javadoc error from 2.0.4 to 2.0.6/2.0.7
Hi Wayne, It is jdk1.4 on AIX. Thanks. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: What JDK and what OS? Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: I run mvn javadoc:javadoc with 2.0.6 and 2.0.7, both give me the following error. It works fine if I use 2.0.4. Has anyone seen this error before? Thanks. LJ [INFO] [javadoc:javadoc] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [DEBUG] Trace java.util.NoSuchElementException at java.util.StringTokenizer.nextToken(StringTokenizer.java (Compiled Code)) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocVersion( AbstractJavadocMojo.java:2959) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport (AbstractJavadocMojo.java:1085) at org.apache.maven.plugin.javadoc.JavadocReport.generate( JavadocReport.java:131) at org.apache.maven.plugin.javadoc.JavadocReport.execute( JavadocReport.java:219) at org.apache.maven.plugin.DefaultPluginManager.executeMojo ( DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal( DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures ( DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute ( DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java :334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main (MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke ( NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) 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) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: javadoc error from 2.0.4 to 2.0.6/2.0.7
Thanks Wayne, Looks like the maven-javadoc-plugin 2.2 works with my maven 2.0.6 on AIX but 2.3 does not. I run the following, and it works. /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-2:javadoc But if I run the following, it gives me the java.util.NoSuchElementExceptionerror. /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.3:javadoc However, even I put the maven-javadoc-plugin version number 2.2 in the pom.xml as below, maven 2.0.6 still uses 2.3. groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.2/version What would be the best way/workaround, any suggestion? Thanks. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: It seems like the newer versions of javadoc plugin are trying to parse version information out of your javadoc tool, and your tool is responding with fewer string tokens than is expected, resulting in the error below. I strongly doubt the Maven team tests on AIX much less with jdk4 on AIX, so it seems like you've simply stumbled into a bug. It would be great if you could grok the code and submit a patch yourself, as I certainly don't have an AIX instance to play with and I doubt many of the Maven team does either. First, go file a bug in JIRA. Then pull down the code and see if you can't figure it out. If you have troubles, jump onto IRC and we'll help you out. Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: Hi Wayne, It is jdk1.4 on AIX. Thanks. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: What JDK and what OS? Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: I run mvn javadoc:javadoc with 2.0.6 and 2.0.7, both give me the following error. It works fine if I use 2.0.4. Has anyone seen this error before? Thanks. LJ [INFO] [javadoc:javadoc] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [DEBUG] Trace java.util.NoSuchElementException at java.util.StringTokenizer.nextToken(StringTokenizer.java (Compiled Code)) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocVersion( AbstractJavadocMojo.java:2959) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport (AbstractJavadocMojo.java:1085) at org.apache.maven.plugin.javadoc.JavadocReport.generate( JavadocReport.java:131) at org.apache.maven.plugin.javadoc.JavadocReport.execute( JavadocReport.java:219) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal( DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures ( DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute ( DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java :334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java :125) at org.apache.maven.cli.MavenCli.main (MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke ( NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) 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) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail
Re: javadoc error from 2.0.4 to 2.0.6/2.0.7
Correction, I ran /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.2:javadoc, not maven-javadoc-plugin:2.0-beta-2. On 8/20/07, L. J. [EMAIL PROTECTED] wrote: Thanks Wayne, Looks like the maven-javadoc-plugin 2.2 works with my maven 2.0.6 on AIX but 2.3 does not. I run the following, and it works. /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-2:javadoc But if I run the following, it gives me the java.util.NoSuchElementException error. /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.3:javadoc However, even I put the maven-javadoc-plugin version number 2.2 in the pom.xml as below, maven 2.0.6 still uses 2.3. groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.2/version What would be the best way/workaround, any suggestion? Thanks. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: It seems like the newer versions of javadoc plugin are trying to parse version information out of your javadoc tool, and your tool is responding with fewer string tokens than is expected, resulting in the error below. I strongly doubt the Maven team tests on AIX much less with jdk4 on AIX, so it seems like you've simply stumbled into a bug. It would be great if you could grok the code and submit a patch yourself, as I certainly don't have an AIX instance to play with and I doubt many of the Maven team does either. First, go file a bug in JIRA. Then pull down the code and see if you can't figure it out. If you have troubles, jump onto IRC and we'll help you out. Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: Hi Wayne, It is jdk1.4 on AIX. Thanks. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: What JDK and what OS? Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: I run mvn javadoc:javadoc with 2.0.6 and 2.0.7, both give me the following error. It works fine if I use 2.0.4. Has anyone seen this error before? Thanks. LJ [INFO] [javadoc:javadoc] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [DEBUG] Trace java.util.NoSuchElementException at java.util.StringTokenizer.nextToken( StringTokenizer.java (Compiled Code)) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocVersion ( AbstractJavadocMojo.java:2959) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport (AbstractJavadocMojo.java:1085) at org.apache.maven.plugin.javadoc.JavadocReport.generate( JavadocReport.java:131) at org.apache.maven.plugin.javadoc.JavadocReport.execute( JavadocReport.java:219) at org.apache.maven.plugin.DefaultPluginManager.executeMojo ( DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals ( DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal ( DefaultLifecycleExecutor.java :493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures ( DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute ( DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute( DefaultMaven.java :334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java :125) at org.apache.maven.cli.MavenCli.main (MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java :85) at sun.reflect.NativeMethodAccessorImpl.invoke ( NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) 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
Re: javadoc error from 2.0.4 to 2.0.6/2.0.7
Thanks. issue/bug is filed. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: You can try locking the version to 2.2 with [2.2] in the version tag. But ideally, you'd file the bug and help fix the issue. ;-) Eventually you will need a feature of javadoc-2.4 or 2.5 and it will still have this bug since it was never dealt with. Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: Correction, I ran /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.2:javadoc, not maven-javadoc-plugin:2.0-beta-2. On 8/20/07, L. J. [EMAIL PROTECTED] wrote: Thanks Wayne, Looks like the maven-javadoc-plugin 2.2 works with my maven 2.0.6 on AIX but 2.3 does not. I run the following, and it works. /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-2:javadoc But if I run the following, it gives me the java.util.NoSuchElementException error. /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.3:javadoc However, even I put the maven-javadoc-plugin version number 2.2 in the pom.xml as below, maven 2.0.6 still uses 2.3. groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.2/version What would be the best way/workaround, any suggestion? Thanks. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: It seems like the newer versions of javadoc plugin are trying to parse version information out of your javadoc tool, and your tool is responding with fewer string tokens than is expected, resulting in the error below. I strongly doubt the Maven team tests on AIX much less with jdk4 on AIX, so it seems like you've simply stumbled into a bug. It would be great if you could grok the code and submit a patch yourself, as I certainly don't have an AIX instance to play with and I doubt many of the Maven team does either. First, go file a bug in JIRA. Then pull down the code and see if you can't figure it out. If you have troubles, jump onto IRC and we'll help you out. Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: Hi Wayne, It is jdk1.4 on AIX. Thanks. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: What JDK and what OS? Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: I run mvn javadoc:javadoc with 2.0.6 and 2.0.7, both give me the following error. It works fine if I use 2.0.4. Has anyone seen this error before? Thanks. LJ [INFO] [javadoc:javadoc] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [DEBUG] Trace java.util.NoSuchElementException at java.util.StringTokenizer.nextToken( StringTokenizer.java (Compiled Code)) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocVersion ( AbstractJavadocMojo.java:2959) at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport (AbstractJavadocMojo.java:1085) at org.apache.maven.plugin.javadoc.JavadocReport.generate( JavadocReport.java:131) at org.apache.maven.plugin.javadoc.JavadocReport.execute( JavadocReport.java:219) at org.apache.maven.plugin.DefaultPluginManager.executeMojo ( DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal ( DefaultLifecycleExecutor.java :493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures ( DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute ( DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute( DefaultMaven.java :334) at org.apache.maven.DefaultMaven.execute( DefaultMaven.java :125) at org.apache.maven.cli.MavenCli.main (MavenCli.java :272
Re: javadoc error from 2.0.4 to 2.0.6/2.0.7
Ok, I try to lock it down, but it give me the error as below: [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-javadoc-plugin Version: [2.2] Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-javadoc-plugin:pom:[2.2] Thanks. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: Using versionx.y.z/version does not necessarily mean you're going to get x.y.z. If you absolutely must only get version 2.2, and nothing newer/older is acceptable, then you should use [2.2] to lock down the version. Wayne On 8/20/07, Michael Meyer [EMAIL PROTECTED] wrote: L. J. schrieb: However, even I put the maven-javadoc-plugin version number 2.2 in the pom.xml as below, maven 2.0.6 still uses 2.3. groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.2/version What would be the best way/workaround, any suggestion? Using version 2.2 of the javadoc plugin is the workaround that I'm using for the following bug: http://jira.codehaus.org/browse/MJAVADOC-135. Are you sure that adding this to your pom doesn't work? reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.2/version /plugin /plugins /reporting Cheers, michael - 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]
Continuum 1.1-beta-1 shell project does not run but runs from command line
Using a shell script /usr/bin/sh build.sh (the script runs mvn -U - Dmaven.test.skip clean install), it works fine from the command line, but if I put in continuum beta-1 as a shell project, it fails. I tried adding the profile but does not help. Any suggestion or idea? Compiling 65 source files to /apps/build/continuum-1.1-beta-1 /apps/continuum/webapp/WEB-INF/working-directory/2/checkoutAdmin/admintoolcontinuum/adminparentPOM/../AdminCache/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure Failure executing javac, but could not parse the error: javac: target release 1.3 conflicts with default source release 1.5 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 27 seconds [INFO] Finished at: Mon Aug 06 15:23:33 PDT 2007 [INFO] Final Memory: 10M/28M [INFO] Thanks. LJ
Re: Continuum 1.1-beta-1 shell project does not run but runs from command line
- remove the SNAPSHOT version in the compiler (2.0.2 has been released)
Does not fix it, get the same error
- give os information
my os is AIX
- the JAVA_HOME value in your system env (if a *n*x the value in the
.profile )
in the .profile, JAVA_HOME is jdk1.4
- have you played with profile and attached a jdk to your build definition
I did, but still get the same error. I have the profile using jdk1.3
It runs fine from the command line tho
Thanks.
LJ
On 8/6/07, LAMY Olivier [EMAIL PROTECTED] wrote:
Can you do :
- remove the SNAPSHOT version in the compiler (2.0.2 has been released)
- give os information
- the JAVA_HOME value in your system env (if a *n*x the value in the
.profile )
- have you played with profile and attached a jdk to your build definition
Thanks,
--
Olivier
-Message d'origine-
De : L. J. [mailto:[EMAIL PROTECTED]
Envoyé : mardi 7 août 2007 01:23
À : continuum-users@maven.apache.org
Objet : Re: Continuum 1.1-beta-1 shell project does not run but runs from
command line
Sure,
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.1-SNAPSHOT/version
configuration
target1.3/target
source1.3/source
/configuration
inheritedtrue/inherited
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
archive
indextrue/index
manifest
addClasspathtrue/addClasspath
addExtensions /
classpathPrefix /
/manifest
manifestEntries
Source-Control-Identifier${
project.scm.connection} ${project.scm.tag}/Source-Control-Identifier
/manifestEntries
/archive
/configuration
inheritedtrue/inherited
/plugin
/plugins
/build
Thanks.
LJ
On 8/6/07, LAMY Olivier [EMAIL PROTECTED] wrote:
Could you show your maven-compiler-plugin configuration.
What are you target/source values ?
-Message d'origine-
De : L. J. [mailto:[EMAIL PROTECTED]
Envoyé : mardi 7 août 2007 01:06
À : continuum-users
Objet : Continuum 1.1-beta-1 shell project does not run but runs from
command line
Using a shell script /usr/bin/sh build.sh (the script runs mvn -U -
Dmaven.test.skip clean install), it works fine from the command line,
but if I put in continuum beta-1 as a shell project, it fails. I tried
adding the profile but does not help.
Any suggestion or idea?
Compiling 65 source files to
/apps/build/continuum-1.1-beta-1/apps/continuum/webapp/WEB-INF/working
-directory/2/checkoutAdmin/admintoolcontinuum/adminparentPOM/../AdminC
ache/target/classes
[INFO]
--
--
[ERROR] BUILD FAILURE
[INFO]
--
--
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
javac: target release 1.3 conflicts with default source release 1.5
[INFO]
--
-- [INFO] For more information, run Maven with the -e switch [INFO]
--
--
[INFO] Total time: 27 seconds
[INFO] Finished at: Mon Aug 06 15:23:33 PDT 2007 [INFO] Final Memory:
10M/28M [INFO]
--
--
Thanks.
LJ
This e-mail, any attachments and the information contained therein
(this
message) are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please send
it back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in
part is strictly prohibited.
**
Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après le message ), sont
confidentiels et destinés exclusivement à l'usage de la personne à
laquelle ils sont adressés. Si vous avez reçu ce message par erreur,
merci de le renvoyer à son émetteur et de le détruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous
quelque forme que se soit non expressément autorisées de ce message,
sont interdites.
**
Continuum 1.1-beta-1 profile does not seem to work
Hi, When using IE 6, I click the add button to add the installation in the profile, it does not do anything. When using Firefox, the add button works, but after save the profile and go back to check the profile, the installation isn't included in the profile. I am running in AIX, Is this because of my OS or has this happened to anyone else? Thanks. LJ
Re: Continuum 1.1-beta-1 shell project does not run but runs from command line
Ok, turns out that it it the bug in beta-1 Profile. After I click save,
the JDK installation is removed from the profile.
However, I can only add installation into profile using Firefox, not IE6.
Thanks.
LJ
On 8/6/07, LAMY Olivier [EMAIL PROTECTED] wrote:
Can you do :
- remove the SNAPSHOT version in the compiler (2.0.2 has been released)
- give os information
- the JAVA_HOME value in your system env (if a *n*x the value in the
.profile )
- have you played with profile and attached a jdk to your build definition
Thanks,
--
Olivier
-Message d'origine-
De : L. J. [mailto:[EMAIL PROTECTED]
Envoyé : mardi 7 août 2007 01:23
À : continuum-users@maven.apache.org
Objet : Re: Continuum 1.1-beta-1 shell project does not run but runs from
command line
Sure,
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.1-SNAPSHOT/version
configuration
target1.3/target
source1.3/source
/configuration
inheritedtrue/inherited
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
archive
indextrue/index
manifest
addClasspathtrue/addClasspath
addExtensions /
classpathPrefix /
/manifest
manifestEntries
Source-Control-Identifier${
project.scm.connection} ${project.scm.tag}/Source-Control-Identifier
/manifestEntries
/archive
/configuration
inheritedtrue/inherited
/plugin
/plugins
/build
Thanks.
LJ
On 8/6/07, LAMY Olivier [EMAIL PROTECTED] wrote:
Could you show your maven-compiler-plugin configuration.
What are you target/source values ?
-Message d'origine-
De : L. J. [mailto:[EMAIL PROTECTED]
Envoyé : mardi 7 août 2007 01:06
À : continuum-users
Objet : Continuum 1.1-beta-1 shell project does not run but runs from
command line
Using a shell script /usr/bin/sh build.sh (the script runs mvn -U -
Dmaven.test.skip clean install), it works fine from the command line,
but if I put in continuum beta-1 as a shell project, it fails. I tried
adding the profile but does not help.
Any suggestion or idea?
Compiling 65 source files to
/apps/build/continuum-1.1-beta-1/apps/continuum/webapp/WEB-INF/working
-directory/2/checkoutAdmin/admintoolcontinuum/adminparentPOM/../AdminC
ache/target/classes
[INFO]
--
--
[ERROR] BUILD FAILURE
[INFO]
--
--
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
javac: target release 1.3 conflicts with default source release 1.5
[INFO]
--
-- [INFO] For more information, run Maven with the -e switch [INFO]
--
--
[INFO] Total time: 27 seconds
[INFO] Finished at: Mon Aug 06 15:23:33 PDT 2007 [INFO] Final Memory:
10M/28M [INFO]
--
--
Thanks.
LJ
This e-mail, any attachments and the information contained therein
(this
message) are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please send
it back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in
part is strictly prohibited.
**
Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après le message ), sont
confidentiels et destinés exclusivement à l'usage de la personne à
laquelle ils sont adressés. Si vous avez reçu ce message par erreur,
merci de le renvoyer à son émetteur et de le détruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous
quelque forme que se soit non expressément autorisées de ce message,
sont interdites.
**
shell execution from 1.1-beta-1
I have a build definition: Build File /usr/bin/sh Arguments buildAdmin.sh It works in alpha and earlier version of continuum. Is the way that the shell script gets executed changed since beta? I got the following error, and wonder why continuum is calling /bin/bash at the very beginning 1705563 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Executing: /bin/bash -c cd /apps/build/continuum-1.1-beta-1/apps/continuum/webapp/WEB-INF/working-directory/2 /usr/bin/sh buildAdmin.sh 1705563 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Working directory: /apps/build/continuum-1.1-beta-1 /apps/continuum/webapp/WEB-INF/working-directory/2 1706375 [pool-1-thread-1] ERROR org.codehaus.plexus.action.Action:execute-builder - Error running buildResult org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while executing shell command. The most common error is that '/usr/bin/sh' is not in your path. at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand (AbstractBuildExecutor.java:218) at org.apache.maven.continuum.execution.shell.ShellBuildExecutor.build( ShellBuildExecutor.java:74) at org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute (ExecuteBuilderContinuumAction.java:140) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction (DefaultBuildController.java:406) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:145) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask (BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run (ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run( FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:801) Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while executing process. at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java :652) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine( CommandLineUtils.java:102) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine( CommandLineUtils.java:89) at org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand (DefaultShellCommandHelper.java:114) at org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand (DefaultShellCommandHelper.java:59) at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand (AbstractBuildExecutor.java:202) ... 11 more Caused by: java.io.IOException: /bin/bash: not found at java.lang.UNIXProcess.fullPath(UNIXProcess.java:365) at java.lang.UNIXProcess.init(UNIXProcess.java:172) at java.lang.ProcessImpl.start(ProcessImpl.java:114) at java.lang.ProcessBuilder.start(ProcessBuilder.java:466) at java.lang.Runtime.exec(Runtime.java:607) at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java :647) ... 16 more 1706710 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action deploy-artifac Thanks. LJ
Re: Continuum 1.1-beta-1 shell project does not run but runs from command line
Sure,
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.1-SNAPSHOT/version
configuration
target1.3/target
source1.3/source
/configuration
inheritedtrue/inherited
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
archive
indextrue/index
manifest
addClasspathtrue/addClasspath
addExtensions /
classpathPrefix /
/manifest
manifestEntries
Source-Control-Identifier${
project.scm.connection} ${project.scm.tag}/Source-Control-Identifier
/manifestEntries
/archive
/configuration
inheritedtrue/inherited
/plugin
/plugins
/build
Thanks.
LJ
On 8/6/07, LAMY Olivier [EMAIL PROTECTED] wrote:
Could you show your maven-compiler-plugin configuration.
What are you target/source values ?
-Message d'origine-
De : L. J. [mailto:[EMAIL PROTECTED]
Envoyé : mardi 7 août 2007 01:06
À : continuum-users
Objet : Continuum 1.1-beta-1 shell project does not run but runs from
command line
Using a shell script /usr/bin/sh build.sh (the script runs mvn -U -
Dmaven.test.skip clean install), it works fine from the command line, but
if I put in continuum beta-1 as a shell project, it fails. I tried adding
the profile but does not help.
Any suggestion or idea?
Compiling 65 source files to
/apps/build/continuum-1.1-beta-1/apps/continuum/webapp/WEB-INF/working-directory/2/checkoutAdmin/admintoolcontinuum/adminparentPOM/../AdminCache/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
javac: target release 1.3 conflicts with default source release 1.5
[INFO]
[INFO] For more information, run Maven with the -e switch [INFO]
[INFO] Total time: 27 seconds
[INFO] Finished at: Mon Aug 06 15:23:33 PDT 2007 [INFO] Final Memory:
10M/28M [INFO]
Thanks.
LJ
This e-mail, any attachments and the information contained therein (this
message) are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please send it back
to the sender and delete it. Unauthorized publication, use, dissemination or
disclosure of this message, either in whole or in part is strictly
prohibited.
**
Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après le message ), sont
confidentiels et destinés exclusivement à l'usage de la personne à laquelle
ils sont adressés. Si vous avez reçu ce message par erreur, merci de le
renvoyer à son émetteur et de le détruire. Toutes diffusion, publication,
totale ou partielle ou divulgation sous quelque forme que se soit non
expressément autorisées de ce message, sont interdites.
**
Can not startup Continuum 1.1-beta-1
Get below exception during startup Exception in thread main java.lang.UnsupportedClassVersionError: org/apache/maven/continuum/xmlrpc/server/ContinuumXmlRpcServlet (Unsupported major.minor version 49.0) Is anyone having the same problem? Thanks. LJ
Re: User Interface Performance of 1.1
Sorry, I meant to say the performance in general compare to 1.0.3 especially page loading while switching pages. Thanks. LJ On 6/4/07, Jesse McConnell [EMAIL PROTECTED] wrote: your still getting 30 second page loads on screens like the project group summary and members pages? jesse On 6/4/07, L. J. [EMAIL PROTECTED] wrote: Hi, Is it just me or anyone else experience the same, alpha-2 does not seem to perform any faster than alpha-1 Thanks. LJ On 5/22/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Performance are fixed in alpha-2 that will be available in few days. Emmanuel Shaun Barriball a écrit : Are there any known ways to improve the performance of Continuum - as per the issue below? Issue 2 - Performance -- Out of the box Continuum 1.1 appears much, much slower than 1.0.3. For example, it takes 30 secs+ after I click MyBigProject to display the contents of the Project Group which has 10 Projects. Are there any logging settings/go faster buttons that would help improve performance? Regards, Shaun. -- jesse mcconnell [EMAIL PROTECTED]
Re: User Interface Performance of 1.1
Hi, Is it just me or anyone else experience the same, alpha-2 does not seem to perform any faster than alpha-1 Thanks. LJ On 5/22/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Performance are fixed in alpha-2 that will be available in few days. Emmanuel Shaun Barriball a écrit : Are there any known ways to improve the performance of Continuum - as per the issue below? Issue 2 - Performance -- Out of the box Continuum 1.1 appears much, much slower than 1.0.3. For example, it takes 30 secs+ after I click MyBigProject to display the contents of the Project Group which has 10 Projects. Are there any logging settings/go faster buttons that would help improve performance? Regards, Shaun.
Re: How to configure 2 projects in the same group to use different build definitions in 1.1-SNAPSHOT?
Thanks, I thought I have tried that, but looks like I did not :) Yes, now I have a build definition for the project level not the group level. Thanks. LJ On 4/3/07, Maria Odea Ching [EMAIL PROTECTED] wrote: Hi, Have you tried doing this in the project build definition instead of at the project group level? Thanks, Deng L. J. wrote: Hi, Can anyone suggest me how to configure this? I have 2 M2 projects that use 2 different arguments which referring to it's own build directory, but they are in the same group. I create 2 build definitions but I can't change the Is this default? option in the build definitions as it affects one and the other. Example below: In the same group name/id Project1 clean deploy -batch-mode --non-recursive - Dproject.path=/apps/continuum/working-directory/20 Proejct2 clean deploy -batch-mode --non-recursive - Dproject.path=/apps/continuum/working-directory/9 Thanks. LJ !DSPAM:602,4612cf0e8561722577945!
How to configure 2 projects in the same group to use different build definitions in 1.1-SNAPSHOT?
Hi, Can anyone suggest me how to configure this? I have 2 M2 projects that use 2 different arguments which referring to it's own build directory, but they are in the same group. I create 2 build definitions but I can't change the Is this default? option in the build definitions as it affects one and the other. Example below: In the same group name/id Project1 clean deploy -batch-mode --non-recursive - Dproject.path=/apps/continuum/working-directory/20 Proejct2 clean deploy -batch-mode --non-recursive - Dproject.path=/apps/continuum/working-directory/9 Thanks. LJ
Re: 1.1-SNAPSHOT fails to check out projects from CVS
The only thing I see from the log is below: 2007-03-29 11:07:32,767 [SocketListener0-0] INFO Continuum:default - Enqueuing 'securityParentPOM' (Build definition id=3). 2007-03-29 11:07:32,794 [pool-1-thread-1] INFO BuildController:default- Initializing build 2007-03-29 11:07:33,138 [pool-1-thread-1] INFO BuildController:default- Starting build of securityParentPOM 2007-03-29 11:07:33,294 [pool-1-thread-1] INFO BuildController:default- Updating working dir 2007-03-29 11:07:33,296 [pool-1-thread-1] INFO BuildController:default- Performing action check-working-directory 2007-03-29 11:07:33,308 [pool-1-thread-1] INFO BuildController:default- Performing action checkout-project 2007-03-29 11:07:33,378 [pool-1-thread-1] INFO ContinuumScm:default - Checking out project: 'securityParentPOM', id: '2' to '/apps/build/artifact-continuum/apps/continuum/working-directory/2'. 2007-03-29 11:07:34,253 [pool-1-thread-1] INFO ScmManager:default - Executing: cvs -z3 -f -d : pserver:[EMAIL PROTECTED]:/home/services/cvs/np -q checkout -d 2 securityparentpom 2007-03-29 11:07:34,255 [pool-1-thread-1] INFO ScmManager:default - Working directory: /apps/build/artifact-continuum/apps/continuum/working-directory 2007-03-29 11:07:34,277 [pool-1-thread-1] INFO BuildController:default- Merging SCM results 2007-03-29 11:07:34,974 [pool-1-thread-1] INFO BuildController:default- Error updating from SCM, not building On 3/29/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Send us the full stacktrace and lines log before it L. J. a écrit : Hi, I just installed the latest build from the trunk continuum-20070327.03.tar.gz, but Continuum 1.1-SNAPSHOT fails to checkout projects from CVS, with the exception in the GUI: Exception: org/apache/maven/scm/provider/cvslib/command/checkout/CvsCheckOutConsumer I manually run the command shows on the log on the UNIX box that the Continuum is running, and it works fine. Any idea? Should I file a issue in jira? Thanks. LJ
Re: 1.1-SNAPSHOT fails to check out projects from CVS
The only exception/stacktrace was showing from the GUI that I sent earlier. No exception from the log Exception: org/apache/maven/scm/provider/cvslib/command/checkout/CvsCheckOutConsumer Thanks. LJ On 3/29/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Send us the full stacktrace and lines log before it L. J. a écrit : Hi, I just installed the latest build from the trunk continuum-20070327.03.tar.gz, but Continuum 1.1-SNAPSHOT fails to checkout projects from CVS, with the exception in the GUI: Exception: org/apache/maven/scm/provider/cvslib/command/checkout/CvsCheckOutConsumer I manually run the command shows on the log on the UNIX box that the Continuum is running, and it works fine. Any idea? Should I file a issue in jira? Thanks. LJ
Re: 1.1-SNAPSHOT fails to check out projects from CVS
I am using 1.1-SNAPSHOT and I also try the latest build from the trunk http://maven.zones.apache.org/~continuum/builds/trunk/ Still can't check out from CVS with the same error. Thanks. LJ On 3/29/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: the checkout seems to be ok, what is your continuum version? L. J. a écrit : The only thing I see from the log is below: 2007-03-29 11:07:32,767 [SocketListener0-0] INFO Continuum:default - Enqueuing 'securityParentPOM' (Build definition id=3). 2007-03-29 11:07:32,794 [pool-1-thread-1] INFO BuildController:default- Initializing build 2007-03-29 11:07:33,138 [pool-1-thread-1] INFO BuildController:default- Starting build of securityParentPOM 2007-03-29 11:07:33,294 [pool-1-thread-1] INFO BuildController:default- Updating working dir 2007-03-29 11:07:33,296 [pool-1-thread-1] INFO BuildController:default- Performing action check-working-directory 2007-03-29 11:07:33,308 [pool-1-thread-1] INFO BuildController:default- Performing action checkout-project 2007-03-29 11:07:33,378 [pool-1-thread-1] INFO ContinuumScm:default - Checking out project: 'securityParentPOM', id: '2' to '/apps/build/artifact-continuum/apps/continuum/working-directory/2'. 2007-03-29 11:07:34,253 [pool-1-thread-1] INFO ScmManager:default - Executing: cvs -z3 -f -d : pserver:[EMAIL PROTECTED]:/home/services/cvs/np -q checkout -d 2 securityparentpom 2007-03-29 11:07:34,255 [pool-1-thread-1] INFO ScmManager:default - Working directory: /apps/build/artifact-continuum/apps/continuum/working-directory 2007-03-29 11:07:34,277 [pool-1-thread-1] INFO BuildController:default- Merging SCM results 2007-03-29 11:07:34,974 [pool-1-thread-1] INFO BuildController:default- Error updating from SCM, not building On 3/29/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Send us the full stacktrace and lines log before it L. J. a écrit : Hi, I just installed the latest build from the trunk continuum-20070327.03.tar.gz, but Continuum 1.1-SNAPSHOT fails to checkout projects from CVS, with the exception in the GUI: Exception: org/apache/maven/scm/provider/cvslib/command/checkout/CvsCheckOutConsumer I manually run the command shows on the log on the UNIX box that the Continuum is running, and it works fine. Any idea? Should I file a issue in jira? Thanks. LJ
1.1-SNAPSHOT fails to check out projects from CVS
Hi, I just installed the latest build from the trunk continuum-20070327.03.tar.gz, but Continuum 1.1-SNAPSHOT fails to checkout projects from CVS, with the exception in the GUI: Exception: org/apache/maven/scm/provider/cvslib/command/checkout/CvsCheckOutConsumer I manually run the command shows on the log on the UNIX box that the Continuum is running, and it works fine. Any idea? Should I file a issue in jira? Thanks. LJ
Re: stop a build from GUI in version 1.1
Thanks. We have a nightly build runs almost 2 hours every night, will it stop the nightly build automatically after 1 hour? Thanks. LJ On 3/12/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: I don't know, but in 1.1 code, we actually stop automatically a build if it isn't finished after 1h. Emmanuel L. J. a écrit : When do you plan to link to the GUI? I can't wait to try it out :) Thanks LJ On 3/8/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: all the code is there but we need to link the gui to it. This feature will be available only for *nix system Emmanuel L. J. a écrit : Sorry if this question has been asked, in 1.0.3, you can't stop a build from the GUI but will this be added as part of version 1.1 new features?
Re: stop a build from GUI in version 1.1
When do you plan to link to the GUI? I can't wait to try it out :) Thanks LJ On 3/8/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: all the code is there but we need to link the gui to it. This feature will be available only for *nix system Emmanuel L. J. a écrit : Sorry if this question has been asked, in 1.0.3, you can't stop a build from the GUI but will this be added as part of version 1.1 new features?
stop a build from GUI in version 1.1
Sorry if this question has been asked, in 1.0.3, you can't stop a build from the GUI but will this be added as part of version 1.1 new features?
Re: validation email url when Register for an Account
http://jira.codehaus.org/browse/CONTINUUM-1043 On 12/22/06, L. J. [EMAIL PROTECTED] wrote: The temp workaround that works for me is changing the localhost URL to http://yourContinuumURL:yourContinuumPort(ex:8080)/continuum/security/x http://yourContinuumURL:yourContinuumPort%28ex:8080%29/continuum/security/x. I tried to change the Base URL, but that does not help. Also, I wonder how can I unlcok admin user admin if it is locked. Thanks. LJ On 12/22/06, LAMY Olivier [EMAIL PROTECTED] wrote: Hi, I have started test on the continuum trunk (congratulations nice job). I'd like to know how to configure the url sended in the Email validation when a new ask an Account. Is-it possible ? (actually the url received is http://localhost/security/login!login.action?validateMe=ad93d7a7b14246f4http://localhost/security/login%21login.action?validateMe=ad93d7a7b14246f4 965e36af3bc7f446 http://localhost/security/login!login.action?validateMe=ad93d7a7b14246fhttp://localhost/security/login%21login.action?validateMe=ad93d7a7b14246f 4965e36af3bc7f446 ). I use the plexus-runtime mode. Thanks, -- Olivier This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ** Ce message electronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci apres le message ), sont confidentiels et destines exclusivement a l'usage de la personne a laquelle ils sont adresses. Si vous avez recu ce message par erreur, merci de le renvoyer a son emetteur et de le detruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressement autorisees de ce message, sont interdites. **
Re: validation email url when Register for an Account
The temp workaround that works for me is changing the localhost URL to http://yourContinuumURL:yourContinuumPort(ex:8080)/continuum/security/x. I tried to change the Base URL, but that does not help. Also, I wonder how can I unlcok admin user admin if it is locked. Thanks. LJ On 12/22/06, LAMY Olivier [EMAIL PROTECTED] wrote: Hi, I have started test on the continuum trunk (congratulations nice job). I'd like to know how to configure the url sended in the Email validation when a new ask an Account. Is-it possible ? (actually the url received is http://localhost/security/login!login.action?validateMe=ad93d7a7b14246f4 965e36af3bc7f446 http://localhost/security/login!login.action?validateMe=ad93d7a7b14246f 4965e36af3bc7f446 ). I use the plexus-runtime mode. Thanks, -- Olivier This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ** Ce message electronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci apres le message ), sont confidentiels et destines exclusivement a l'usage de la personne a laquelle ils sont adresses. Si vous avez recu ce message par erreur, merci de le renvoyer a son emetteur et de le detruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressement autorisees de ce message, sont interdites. **
Installing continuum 1.1 SNAPSHOT
Hi, I try to install the continuum 1.1 SNAPSHOT on my local machine which I build from the main trunk after svn checkout. I can't log on after creating an admin user. Is there anything i am missing during the installation? Thanks. LJ
txt files under build-output-directory
Hi The output txt files are taking too much space on our continuum server, can I remove everything under build-output-directory? Thanks. LJ
Re: settings.xml ignored
Do you have multiple profiles? Try to use help:active-profiles from the command line under the project directory which has the pom.xml. Thanks. LJ On 10/26/06, Attila Mezei-Horvati [EMAIL PROTECTED] wrote: LJ, I have it as: ... profiles profile iddefault/id activation activeByDefault/ /activation ... /profile ... and then I also have: activeProfiles activeProfiledefault/activeProfile /activeProfiles Is there a way to display the active profiles in continuum? I tried to setup a build with help:active-profiles but I don't see where is the output going. I checked the log files for it and it was not there. thanks, Attila __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: settings.xml ignored
Hi Attila, I now have a question and need your help. You said that you have multiple profiles in the settings.xml. If this is the case, do you have 2 profiles using the same variables with different values? (example below) profiles profile idid_1/id sameVariablevalue1sameVariable/ ... /profile profile idid_2/id sameVariablevalue2sameVariable/ ... /profile profiles Does the Continuum pick up the correct values base on the profile you want to use? Thanks LJ On 10/26/06, Attila Mezei-Horvati [EMAIL PROTECTED] wrote: LJ, sorry for all the trouble. I just found out what the problem was. When I first run the add new project, the settings.xml file was not found. Hence the wrong scm url in that window. I deleted the projects and reimported them. This time the settings.xml was found, the project scm url now is correct and they build good. thanks for your help, I appreciate it. Attila __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: settings.xml ignored
Make sure you activate the profile in the serttingx.xml.
activeProfiles
activeProfileyour_profile_id/activeProfile
/activeProfiles
Thanks.
LJ
On 10/25/06, Attila Mezei-Horvati [EMAIL PROTECTED] wrote:
Hi there,
I have installed Continuum 1.0.3. I have a multi
module project. It uses subversion as scm.
When I run 'build now' from the web-interface I get
the following error:
Cannot checkout sources.${scm.base.url}/commons/trunk/
url isn't a valid svn URL. The scm url is invalid.
The ${scm.base.url} is setup in the settings xml which
is in the continuum user/.m2/settings.xml . When
loading continuum I can see this in the log file:
Building Maven user-level settings from:
'/.m2/settings.xml' (i am running as root). It seems
it finds the file. Yet it does not replace the value.
Any suggestions? I tried to find the error in the logs
but could not find anything on it. It just says,
sending mail.
thanks,
Attila
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
How to add additional links on the Continuum in the main page?
Hi I want to add some additional links to my company's internal web links on the Continuum main page. I try to change the .vm files in the continuum-plexus-application-1.0.3.jar, but after bouncing the server, I do not see anything changed. Is there something else I miss? Thanks. LJ
Re: multiple profiles in settings.xml
Thanks, yes, I have tried that before sending this email, did not work either. I guess Continuum loads all profiles at once and if duplicate variables found, it will just pick up the one from the last profile in the settings.xml. Thanks. LJ On 10/22/06, Adam Hardy [EMAIL PROTECTED] wrote: Try removing the space after -P -Padmintool L. J. on 17/10/06 01:11, wrote: I have multiple profiles in my settings.xml as below. While I run clean install -P admintool -Dmaven.test.skip in the Continuum, it does not pick up cvstagADMINTOOL_200609040300/cvstag but it picks up cvstagDEV_HEAD_393/cvstag from profile id r9. I have tried bouncing the server and changiung the profile id. but can get it work. Can someone help? thanks a lot!! profiles profile idr7/id properties cvstagDEV_HEAD_391/cvstag /properties /profile profile idr9/id properties cvstagDEV_HEAD_393/cvstag /properties /profile profile idadmintool/id properties cvstagADMINTOOL_200609040300/cvstag /properties /profile /profiles
multiple profiles in settings.xml
I have multiple profiles in my settings.xml as below. While I run clean install -P admintool -Dmaven.test.skip in the Continuum, it does not pick up cvstagADMINTOOL_200609040300/cvstag but it picks up cvstagDEV_HEAD_393/cvstag from profile id r9. I have tried bouncing the server and changiung the profile id. but can get it work. Can someone help? thanks a lot!! profiles profile idr7/id properties cvstagDEV_HEAD_391/cvstag /properties /profile profile idr9/id properties cvstagDEV_HEAD_393/cvstag /properties /profile profile idadmintool/id properties cvstagADMINTOOL_200609040300/cvstag /properties /profile /profiles LJ
Re: running multiple instances of continuum on one machine
Yes, it is possible, we run 3 instances of Continuum on one AIX machine using different ports On 8/31/06, Feniks Nator [EMAIL PROTECTED] wrote: Hey, I'm wondering if it is possible to run multiple instances of Continuum on the same machine? We have a lot of projects (each possibly having one or more modules), and this results in a long list of modules/projects. As far as I know it's not (yet?) possible to filter the last based on name or group. So I was thinking about running a second instance of continuum listening on another port. What would be the best way to do this? We run on windows, continuum installed as a service. Duplicate the whole continuum installation and change the config in that location to run on another port? Consequence of this is that the existing users are lost. Another solution is creating a second wrapper.config file. But I'm not sure what will be the result. MAybe we'll encounter threading/concurrency issues. Anyone already tried this out? Any suggestions? Thanks
Re: accessing continuum DB
I have tried this but always get the error message: java.security.PrivilegedActionException : Error opening socket to server servername on port 1527 with message : null Any suggestion? Thanks. LJ On 8/31/06, Artamonov, Juri [EMAIL PROTECTED] wrote: I don't know why you need this, but here are instruction that were taken by me from another mail on this list Downloaded SQuirreL SQL from http://squirrel-sql.sourceforge.net/. Selected Modify Driver for Apache Derby Embedded and added the Derby jar files, derby.jar and derbyclient.jar to the Extra Class Path tab. Created a new continuum entry in the Aliases window. These are the properties: Name: continuum Driver: Apache Derby Embedded URL: jdbc:derby:c:/temp/continuum/database UserName: sa In Linux the URL is: jdbc:derby:/usr/local/bin/continuum-1.0.3/apps/continuum/database I can now connect to the database... -Original Message- From: L. J. [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 11:09 PM To: continuum-users Subject: accessing continuum DB Could anyone kindly provide me a step by step instructions on how to access the continuum DB? Also, what tool should I use? Thanks. LJ
Re: accessing continuum DB
I shut down continuum but still get the same error message. I am following the SQuirreL SQL instructions that Artamonov provides in this email. My JDBC connection is jdbc:derby://server_ip/apps/build/continuum- 1.0.3/apps/continuum/database Thanks. L. J. On 8/31/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: what is the jdbc url you use? You must shutdown continuum before to access to the database. Emmanuel L. J. a écrit : I have tried this but always get the error message: java.security.PrivilegedActionException : Error opening socket to server servername on port 1527 with message : null Any suggestion? Thanks. LJ On 8/31/06, Artamonov, Juri [EMAIL PROTECTED] wrote: I don't know why you need this, but here are instruction that were taken by me from another mail on this list Downloaded SQuirreL SQL from http://squirrel-sql.sourceforge.net/. Selected Modify Driver for Apache Derby Embedded and added the Derby jar files, derby.jar and derbyclient.jar to the Extra Class Path tab. Created a new continuum entry in the Aliases window. These are the properties: Name: continuum Driver: Apache Derby Embedded URL: jdbc:derby:c:/temp/continuum/database UserName: sa In Linux the URL is: jdbc:derby:/usr/local/bin/continuum-1.0.3/apps/continuum/database I can now connect to the database... -Original Message- From: L. J. [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 11:09 PM To: continuum-users Subject: accessing continuum DB Could anyone kindly provide me a step by step instructions on how to access the continuum DB? Also, what tool should I use? Thanks. LJ
accessing continuum DB
Could anyone kindly provide me a step by step instructions on how to access the continuum DB? Also, what tool should I use? Thanks. LJ
Why does Continuum build the projects even there is no change
We have 20+ projects that are scheduled to be built every 3 hours daily. Some of them are built even there is no changes. Some of them do not get built while no changes. Does anyone know why this is happening? I read earlier email about putting target directory in the cvsignore file, but this does not seem to help. Also, for those projects that do not get built while there is no changes, I see either they do not have cvsignore file or the cvsignore file only contains bin directory. Thanks. LJ
