Re: problem building continuum
Progress, but not yet happiness. I'm running Out of Memory when the build is running. I hunted down (google); activation, mail, jta, connector (note connector is named connector-api on the maven mini guide, but is just connector in the build) mvn install:install-file -Dfile=jta-1_0_1B-classes.zip -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -DgroupId=javax.transaction # I add connector with both names... Once using the maven's recommended naming, once using what Continuum requires mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip -DartifactId=connector-api -Dversion=1.0 -Dpackaging=jar -DgroupId=javax.resource mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip -DartifactId=connector -Dversion=1.0 -Dpackaging=jar -DgroupId=javax.resource mvn install:install-file -Dfile=/ul/javamail-1_3_3_01.zip -DartifactId=mail -Dversion=1.3.2 -Dpackaging=jar -DgroupId=javax.mail mvn install:install-file -Dfile=/ul/jaf-1_0_2-upd2.zip -DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar -DgroupId=javax.activation I then I started again, $ svn co http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/ $ cd continuum-1.0.x $ sh build.sh ... 2006-02-02 21:30:17,967 [main] INFO RDBMS - Validated 1 unique key(s) for table PROJECTNOTIFIER 2006-02-02 21:30:21,639 [main] ERROR SCHEMA - An exception was thrown while adding/validating class(es) : Java exception: ': java.lang.OutOfMemoryError'. java.lang.OutOfMemoryError 2006-02-02 21:30:21,639 [main] ERROR SCHEMA - SQL Exception: Java exception: ': java.lang.OutOfMemoryError'. 2006-02-02 21:30:22,351 [main] ERROR SCHEMA - Failed initialising database. Exception : An exception was thrown while adding/validating class(es) : Java exception: ': java.lang.OutOfMemoryError'. java.lang.OutOfMemoryError ... I imagine I need to jam -Xmx1g somewhere, but I'm not sure how to set that in the right place. Help? Thanks -bob Emmanuel Venisse wrote: Continuum use some SUN jars that can't be redistributed. So you need to download them from sun site and copy them in the correct group in your repository like describe there : http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html Emmanuel Bob Herrmann a écrit : ok, $ svn co http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/ $ cd continuum-1.0.x $ sh build.sh ... [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. required artifacts missing: javax.resource:connector:jar:1.0 javax.transaction:jta:jar:1.0.1B for the artifact: org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) Why am I getting these missing resources? I'm following the building continuum instructions, http://maven.apache.org/continuum/guides/development/guide-build-continuum.html and dont see any reference to needed external stuff. (I did already put maven-2.0.2 in my path.) Cheers -bob
Re: problem building continuum
ok, $ svn co http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/ $ cd continuum-1.0.x $ sh build.sh ... [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. required artifacts missing: javax.resource:connector:jar:1.0 javax.transaction:jta:jar:1.0.1B for the artifact: org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) Why am I getting these missing resources? I'm following the building continuum instructions, http://maven.apache.org/continuum/guides/development/guide-build-continuum.html and dont see any reference to needed external stuff. (I did already put maven-2.0.2 in my path.) Cheers -bob
[jira] Commented: (SCM-142) Starteam tree stale
[ http://jira.codehaus.org/browse/SCM-142?page=comments#action_56927 ] Bob Herrmann commented on SCM-142: -- The output of bco is different enough that it doesnt detect file changes. So the "stcmd" to "bco" thing is only really useful if you only always force builds (and don't mind that it always says No Changes.) I'm experimenting some more, trying to get this stuff to work correctly. Will keep this bug advised of developements > Starteam tree stale > --- > > Key: SCM-142 > URL: http://jira.codehaus.org/browse/SCM-142 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: continuum-1.0.2 > Reporter: Bob Herrmann > > > It only takes a few changes to starteam for the checked out filesystem to > become hopelessly stale. The only recovery option is to completely remove > all files and startover. Either the code checking out is not handing the > timestamps correctly, or starteam command line has problems keeping a checked > out tree in sync (this more likely - as we also see this problem with AntHill > when using it's incremental builder.) Possible fixes might be to detect > 'unknown' status's and flush the checked out tree. Or try using the 2005 bco > command instead of stcmd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-142) Starteam tree stale
[ http://jira.codehaus.org/browse/SCM-142?page=comments#action_56800 ] Bob Herrmann commented on SCM-142: -- full checkout has 7524 files (most .jsp and .java files) I found by renaming "stccmd" and "stcmd.lax" to; "stcmd.real" and "stcmd.real.lax", that I can substitute this script for stcmd, if [ "$1" = "co" ] then bco -vb -p bobh:[EMAIL PROTECTED]:49303/PR-j/PR-j -fp /home/bobh/continuum-1.0.2/apps/continuum/working-directory/1 -is "*" else stcmd.real $* fi Naturally this is a tad specific to my env, although it could be generalized. I find that my problems have gone away > Starteam tree stale > --- > > Key: SCM-142 > URL: http://jira.codehaus.org/browse/SCM-142 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: continuum-1.0.2 > Reporter: Bob Herrmann > > > It only takes a few changes to starteam for the checked out filesystem to > become hopelessly stale. The only recovery option is to completely remove > all files and startover. Either the code checking out is not handing the > timestamps correctly, or starteam command line has problems keeping a checked > out tree in sync (this more likely - as we also see this problem with AntHill > when using it's incremental builder.) Possible fixes might be to detect > 'unknown' status's and flush the checked out tree. Or try using the 2005 bco > command instead of stcmd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-142) Starteam tree stale
[ http://jira.codehaus.org/browse/SCM-142?page=comments#action_56775 ] Bob Herrmann commented on SCM-142: -- Ok, it isnt a deleted (local) file issue. for some reason, its not always getting the current contents of starteam. Seems like it sometimes skips some files. The only corrective measure I can take is to blow away the working-directory and let it recheck everything out. I'm suspecting this has something to do with how files are checked out of starteam. stcmd co -x -nologo -stop -p [EMAIL PROTECTED]:49303/PR-j/PR-j -fp /home/bobh/continuum-1.0.2/apps/continuum/working-directory/1 -merge -neverprompt -is stcmd delete-local -x -nologo -stop -p [EMAIL PROTECTED]:49303/PR-j/PR-j -fp /home/bobh/continuum-1.0.2/apps/continuum/working-directory/1 -is -filter N These commmands look fine. Although we have had problems doing incremental builds with AntHill too. So I suspect something funny with starteam. > Starteam tree stale > --- > > Key: SCM-142 > URL: http://jira.codehaus.org/browse/SCM-142 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: continuum-1.0.2 > Reporter: Bob Herrmann > > > It only takes a few changes to starteam for the checked out filesystem to > become hopelessly stale. The only recovery option is to completely remove > all files and startover. Either the code checking out is not handing the > timestamps correctly, or starteam command line has problems keeping a checked > out tree in sync (this more likely - as we also see this problem with AntHill > when using it's incremental builder.) Possible fixes might be to detect > 'unknown' status's and flush the checked out tree. Or try using the 2005 bco > command instead of stcmd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-142) Starteam tree stale
Starteam tree stale --- Key: SCM-142 URL: http://jira.codehaus.org/browse/SCM-142 Project: Maven SCM Type: Bug Components: maven-scm-provider-starteam Environment: continuum-1.0.2 Reporter: Bob Herrmann It only takes a few changes to starteam for the checked out filesystem to become hopelessly stale. The only recovery option is to completely remove all files and startover. Either the code checking out is not handing the timestamps correctly, or starteam command line has problems keeping a checked out tree in sync (this more likely - as we also see this problem with AntHill when using it's incremental builder.) Possible fixes might be to detect 'unknown' status's and flush the checked out tree. Or try using the 2005 bco command instead of stcmd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPSCM-71) Starteam no revision comments
Starteam no revision comments - Key: MPSCM-71 URL: http://jira.codehaus.org/browse/MPSCM-71 Project: maven-scm-plugin Type: Bug Environment: continumm on Linux Reporter: Bob Herrmann Priority: Minor I'm using continuum to build a project from Starteam. Continuum shows what files changed in Starteam from build to but not the entered revision comments for why the file was changed. Emmanuel Venisse said that this was probably a bug in the starteam provider, and asked that I file a bug here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
