[jira] Created: (CONTINUUM-1327) in the schedules page: add possibility to force build of all projects/build definitions associated with this schedule
in the schedules page: add possibility to force build of all projects/build definitions associated with this schedule - Key: CONTINUUM-1327 URL: http://jira.codehaus.org/browse/CONTINUUM-1327 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-alpha-2 Reporter: [EMAIL PROTECTED] in the schedules page: add possibility to force build of all projects/build definitions associated with this schedule -- 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: (CONTINUUM-1328) create build-definition-templates and link to them in build-definitons
create build-definition-templates and link to them in build-definitons -- Key: CONTINUUM-1328 URL: http://jira.codehaus.org/browse/CONTINUUM-1328 Project: Continuum Issue Type: New Feature Components: Web interface Affects Versions: 1.1-alpha-2 Reporter: [EMAIL PROTECTED] now the build definitions have to be create with all extra options for every module, when it changes we need to change all build definitions It would be nice , in a build definition if you could select a build-definition-template, like for a schedule = if parameters of build need to change, we need to change them only once I use this for reporting-maven -- 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: (CONTINUUM-1331) create new page: show current build queue with project name, next build time
create new page: show current build queue with project name, next build time Key: CONTINUUM-1331 URL: http://jira.codehaus.org/browse/CONTINUUM-1331 Project: Continuum Issue Type: New Feature Components: Web interface Affects Versions: 1.1-alpha-2 Reporter: [EMAIL PROTECTED] show current build queue with project name, next build time -- 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: (CONTINUUM-1330) build results page: show delta time in seconds next to start/endtime
build results page: show delta time in seconds next to start/endtime Key: CONTINUUM-1330 URL: http://jira.codehaus.org/browse/CONTINUUM-1330 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-alpha-2 Reporter: [EMAIL PROTECTED] Priority: Minor build results page: show delta time in seconds next to start/endtime -- 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: (CONTINUUM-1332) project summary: show per project the last build time
project summary: show per project the last build time - Key: CONTINUUM-1332 URL: http://jira.codehaus.org/browse/CONTINUUM-1332 Project: Continuum Issue Type: New Feature Components: Web interface Affects Versions: 1.1-alpha-2 Reporter: tony nys project summary: show per project the last build time -- 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: (CONTINUUM-1328) create build-definition-templates and link to them in build-definitons
[ http://jira.codehaus.org/browse/CONTINUUM-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101106 ] Olivier Lamy commented on CONTINUUM-1328: - Will be solved with profile [doc|http://docs.codehaus.org/display/CONTINUUM/CI+profiles]. When profile will include : goals, arguments etc create build-definition-templates and link to them in build-definitons -- Key: CONTINUUM-1328 URL: http://jira.codehaus.org/browse/CONTINUUM-1328 Project: Continuum Issue Type: New Feature Components: Web interface Affects Versions: 1.1-alpha-2 Reporter: tony nys now the build definitions have to be create with all extra options for every module, when it changes we need to change all build definitions It would be nice , in a build definition if you could select a build-definition-template, like for a schedule = if parameters of build need to change, we need to change them only once I use this for reporting-maven -- 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: (CONTINUUM-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101107 ] Olivier Lamy commented on CONTINUUM-44: --- Can we close the issue and create a new one for profile inheritance and other profile features ? multiple profiles - Key: CONTINUUM-44 URL: http://jira.codehaus.org/browse/CONTINUUM-44 Project: Continuum Issue Type: New Feature Components: Core - Profiles Reporter: Brett Porter Assignee: Emmanuel Venisse Fix For: 1.1-alpha-3 Attachments: CONTINUUM-44, CONTINUUM-44, CONTINUUM-44-continuum-data-management, CONTINUUM-44-continuum-data-management, CONTINUUM-44-GOODIES, CONTINUUM-44-GOODIES, CONTINUUM-44-LICENSE-REFORMATED would like to be able to define a profile (which can include certain environmental things such as the version of m2 to use, the JDK version, etc). Profiles should be able to be used globally, per group or per project. In this way, you could build certain projects under a variety of different JDKs for example. -- 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] Closed: (CONTINUUM-1223) Ability to choose JVM (export JAVA_HOME) for different projects
[ http://jira.codehaus.org/browse/CONTINUUM-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1223. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-beta-1 Fixed by CONTINUUM-44 Ability to choose JVM (export JAVA_HOME) for different projects --- Key: CONTINUUM-1223 URL: http://jira.codehaus.org/browse/CONTINUUM-1223 Project: Continuum Issue Type: Test Components: Integration - Maven 2 Affects Versions: 1.0.3 Environment: N/A Reporter: David J. M. Karlsen Assignee: Emmanuel Venisse Fix For: 1.1-beta-1 Although it's possible to configure compile-plugin, surefire etc to use specific JVM's - there should be an option to specify the JVM (e.g. export JAVA_HOME before executing mvn) as different plugins and so on migth require a specific JVM. -- 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] Closed: (CONTINUUM-1258) Configure the possibility of resolving or not the search of build executables (maven, ant ...)
[ http://jira.codehaus.org/browse/CONTINUUM-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1258. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-beta-1 Fixed by CONTINUUM-44 Configure the possibility of resolving or not the search of build executables (maven, ant ...) -- Key: CONTINUUM-1258 URL: http://jira.codehaus.org/browse/CONTINUUM-1258 Project: Continuum Issue Type: Wish Components: Environmental, Integration - Ant Affects Versions: 1.1-alpha-1 Environment: anyone i tested only on Redhat Reporter: Charles Paulet Assignee: Emmanuel Venisse Priority: Critical Fix For: 1.1-beta-1 When continuum 1.1 starts, logs contains : 2007-04-26 11:55:45,827 [main] WARN ContinuumBuildExecutor:maven-1 - Could not find the executable 'maven' in the path '[$PATH]'. 2007-04-26 11:55:45,833 [main] INFO ContinuumBuildExecutor:ant - Resolved the executable 'ant' to '/usr/bin/ant'. 2007-04-26 11:55:46,600 [main] WARN ContinuumBuildExecutor:maven2 - Could not find the executable 'mvn' in the path '[$PATH]'. This search override any alias defined in a user environment. This search follows the PATH definition order We want to use another ant with Continuum (using a shell script to launch ant in a specific environnement) We can't change the Path order because of internal conflicts. It would be fine if the Continuum configuration contains a check path for build executables parameter. -- 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] Closed: (CONTINUUM-1222) usage of an alternative maven2-executable
[ http://jira.codehaus.org/browse/CONTINUUM-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1222. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-beta-1 Fixed by CONTINUUM-44 usage of an alternative maven2-executable - Key: CONTINUUM-1222 URL: http://jira.codehaus.org/browse/CONTINUUM-1222 Project: Continuum Issue Type: New Feature Components: Integration - Maven 2 Affects Versions: 1.0.3 Environment: unix / linux Reporter: cla monsch Assignee: Emmanuel Venisse Fix For: 1.1-beta-1 it would be very useful to define an alternativ maven2 executable. analog to the 'mvnscript' attribute within the maven2 tag of the cruisecontrol config. there are some cases which are calling i.e. for a wrapper script to start maven2. i think at the moment it isn't possible to define such a script in continuum. -- 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: (MEV-537) aspectwerkz-core 2.0 POM is invalid
aspectwerkz-core 2.0 POM is invalid --- Key: MEV-537 URL: http://jira.codehaus.org/browse/MEV-537 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM Reporter: Dror Bereznitsky There are invalid elements in the aspectwerkz-core 2.0 pom : 'groupgroupId', 'artifactgroupId' groupgroupIdaspectwerkz/groupgroupId artifactgroupIdaspectwerkz-core/artifactgroupId -- 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] Closed: (CONTINUUM-1244) project group name is not validated when left blank in Edit Project Group page, resulting to an error
[ http://jira.codehaus.org/browse/CONTINUUM-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1244. --- Resolution: Fixed Applied. project group name is not validated when left blank in Edit Project Group page, resulting to an error - Key: CONTINUUM-1244 URL: http://jira.codehaus.org/browse/CONTINUUM-1244 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1-alpha-1 Reporter: Lester Ecarma Assignee: Emmanuel Venisse Fix For: 1.1-beta-1 Attachments: CONTINUUM-1244.patch User is redirected to the error page, with the following error: org.apache.maven.continuum.ContinuumException: unable to rename the project group -- 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] Updated: (CONTINUUM-1244) project group name is not validated when left blank in Edit Project Group page, resulting to an error
[ http://jira.codehaus.org/browse/CONTINUUM-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1244: Assignee: Emmanuel Venisse Affects Version/s: (was: 1.0.3) 1.1-alpha-1 Fix Version/s: 1.1-beta-1 project group name is not validated when left blank in Edit Project Group page, resulting to an error - Key: CONTINUUM-1244 URL: http://jira.codehaus.org/browse/CONTINUUM-1244 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1-alpha-1 Reporter: Lester Ecarma Assignee: Emmanuel Venisse Fix For: 1.1-beta-1 Attachments: CONTINUUM-1244.patch User is redirected to the error page, with the following error: org.apache.maven.continuum.ContinuumException: unable to rename the project group -- 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] Closed: (CONTINUUM-827) notification emails missing svn information
[ http://jira.codehaus.org/browse/CONTINUUM-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-827. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: (was: 1.1-beta-1) 1.1-alpha-2 notification emails missing svn information --- Key: CONTINUUM-827 URL: http://jira.codehaus.org/browse/CONTINUUM-827 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.0.3 Reporter: Brian Fox Assignee: Emmanuel Venisse Fix For: 1.1-alpha-2 Attachments: continumm-build-result-view.JPG I'm using 1.0.3 and svn 1.3.2. 99% of the time, the notifications do not list the developer or the commit message. I just get a list of changed files. I have seen it in the past occasionally but almost always the info isn't there. This includes times when there was only 1 commit since the last build. -- 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] Closed: (CONTINUUM-1270) Release artifacts are missing license and notice files
[ http://jira.codehaus.org/browse/CONTINUUM-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1270. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-alpha-2 Release artifacts are missing license and notice files -- Key: CONTINUUM-1270 URL: http://jira.codehaus.org/browse/CONTINUUM-1270 Project: Continuum Issue Type: Task Affects Versions: 1.1-alpha-1 Reporter: Wendy Smoak Assignee: Emmanuel Venisse Fix For: 1.1-alpha-2 The Continuum build does not package license and notice files in the jars or the .tar.gz distribution. This was recently fixed in Archiva, the same configuration can be used 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
[jira] Closed: (CONTINUUM-972) Unable to delete projects
[ http://jira.codehaus.org/browse/CONTINUUM-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-972. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: (was: 1.1-beta-1) 1.1-alpha-1 I can't reproduce it with 1.1 Unable to delete projects - Key: CONTINUUM-972 URL: http://jira.codehaus.org/browse/CONTINUUM-972 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.0.3 Environment: Redhat Enterprise 3 Reporter: Uri Moszkowicz Assignee: Emmanuel Venisse Fix For: 1.1-alpha-1 I am unable to delete project sometimes. I've tried creating a simple project and immediately deleting it. That seems to work. But when I create a real project, let it run for a few days and then try to delete it I cannot. To reproduce: 1. Install continuum 2. Create a project 3. Let it run for at least one build (success or failure doesn't matter) 4. Delete the project by clicking on X from main project page. A delete confirmation page should then appear. 5. Click on the delete button to confirm. The web browser then begins loading but it never terminates. The logs show no exceptions. The delete just hangs. I've removed all the files from the build-output and working-directory and tried deleting again. This makes no difference. If you interrupt the delete and click on show projects the projects page ends up in an inconsistent state (not as many columns, no buttons, an Apache copyright message). -- 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: (MEV-538) aspectwerkz-core 2.0 has missing dependencies
aspectwerkz-core 2.0 has missing dependencies - Key: MEV-538 URL: http://jira.codehaus.org/browse/MEV-538 Project: Maven Evangelism Issue Type: Sub-task Components: Dependencies Reporter: Dror Bereznitsky aspectwerkz-core 2.0 has dependencies that does not exist in repo1.maven.org: dependency groupIdasm/groupId artifactIdasm/artifactId version1.5.4-snapshot/version /dependency dependency groupIdasm-attrs/groupId artifactIdasm-attrs/artifactId version1.5.4-snapshot/version /dependency dependency groupIdasm-util/groupId artifactIdasm-util/artifactId version1.5.4-snapshot/version /dependency -- 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] Closed: (CONTINUUM-955) deployment repository should be required and have a default in initial continuum setup.
[ http://jira.codehaus.org/browse/CONTINUUM-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-955. -- Resolution: Fixed Fix Version/s: (was: 1.1-beta-1) deployment repository should be required and have a default in initial continuum setup. --- Key: CONTINUUM-955 URL: http://jira.codehaus.org/browse/CONTINUUM-955 Project: Continuum Issue Type: Improvement Components: Core system, Web interface Affects Versions: 1.1-alpha-1 Reporter: Christian Gruber Assignee: Emmanuel Venisse Attachments: make_deployment_dir_default.diff, make_deployment_dir_default.diff Deployment repository should be required and have a default in initial continuum setup. If it does not, and empty string is provided, then it deploys to crazy places, and during jetty:run execution, it deploys in places that really messes up the project folders. Patch provided. -- 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] Reopened: (CONTINUUM-955) deployment repository should be required and have a default in initial continuum setup.
[ http://jira.codehaus.org/browse/CONTINUUM-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse reopened CONTINUUM-955: deployment repository should be required and have a default in initial continuum setup. --- Key: CONTINUUM-955 URL: http://jira.codehaus.org/browse/CONTINUUM-955 Project: Continuum Issue Type: Improvement Components: Core system, Web interface Affects Versions: 1.1-alpha-1 Reporter: Christian Gruber Assignee: Emmanuel Venisse Attachments: make_deployment_dir_default.diff, make_deployment_dir_default.diff Deployment repository should be required and have a default in initial continuum setup. If it does not, and empty string is provided, then it deploys to crazy places, and during jetty:run execution, it deploys in places that really messes up the project folders. Patch provided. -- 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] Closed: (CONTINUUM-955) deployment repository should be required and have a default in initial continuum setup.
[ http://jira.codehaus.org/browse/CONTINUUM-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-955. -- Assignee: Emmanuel Venisse Resolution: Won't Fix deployment repository can't be a required field deployment repository should be required and have a default in initial continuum setup. --- Key: CONTINUUM-955 URL: http://jira.codehaus.org/browse/CONTINUUM-955 Project: Continuum Issue Type: Improvement Components: Core system, Web interface Affects Versions: 1.1-alpha-1 Reporter: Christian Gruber Assignee: Emmanuel Venisse Fix For: 1.1-beta-1 Attachments: make_deployment_dir_default.diff, make_deployment_dir_default.diff Deployment repository should be required and have a default in initial continuum setup. If it does not, and empty string is provided, then it deploys to crazy places, and during jetty:run execution, it deploys in places that really messes up the project folders. Patch provided. -- 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] Updated: (DOXIA-70) Scope test must be added in dependency doxia-core:test-jar in doxia-modules
[ http://jira.codehaus.org/browse/DOXIA-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIA-70: --- Priority: Trivial (was: Major) Fix Version/s: 1.0-alpha-9 Component/s: (was: Core) Scope test must be added in dependency doxia-core:test-jar in doxia-modules - Key: DOXIA-70 URL: http://jira.codehaus.org/browse/DOXIA-70 Project: doxia Issue Type: Bug Affects Versions: 1.0-alpha-8 Environment: WinXp, Java5 Reporter: Martin Zeltner Priority: Trivial Fix For: 1.0-alpha-9 Attachments: patch_doxia-modules.txt Original Estimate: 5 minutes Remaining Estimate: 5 minutes Scope test must be added in dependency doxia-core:test-jar in doxia-modules. See appended patch. Cheers, Martin -- 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: (CONTINUUM-1333) show in project group summary per project also the status counters (as they are shown on the project groups pages)
show in project group summary per project also the status counters (as they are shown on the project groups pages) --- Key: CONTINUUM-1333 URL: http://jira.codehaus.org/browse/CONTINUUM-1333 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-alpha-2 Reporter: tony nys show in project group summary per project also the status counters (as they are shown on the project groups pages) -- 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: (CONTINUUM-1093) After validation, logged in user is shown the login page
[ http://jira.codehaus.org/browse/CONTINUUM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101121 ] Emmanuel Venisse commented on CONTINUUM-1093: - Is it fixed? After validation, logged in user is shown the login page Key: CONTINUUM-1093 URL: http://jira.codehaus.org/browse/CONTINUUM-1093 Project: Continuum Issue Type: Improvement Components: Web - UI Affects Versions: 1.1-alpha-1 Reporter: Wendy Smoak Fix For: 1.1-beta-1 After registering, clicking the validation email link, and completing validation, the user is already logged in, but the login page is displayed. The Project Groups page seems to be the default for the rest of the app, and would be more appropriate. -- 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] Closed: (CONTINUUM-729) Conitnnum buids project twice when clicking on 'build now'
[ http://jira.codehaus.org/browse/CONTINUUM-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-729. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: (was: 1.1-beta-1) 1.1-alpha-1 Can't be reproduced with 1.1 Conitnnum buids project twice when clicking on 'build now' -- Key: CONTINUUM-729 URL: http://jira.codehaus.org/browse/CONTINUUM-729 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.0.3 Environment: Continuum-1.0.3 / Maven-2.0.4 / JSE 1.5.0 update 06 / Windows Server 2003 Reporter: Thomas Cornet Assignee: Emmanuel Venisse Fix For: 1.1-alpha-1 Attachments: continuum-log.txt Whenever I click on the 'build now' link in the project list or on the 'build now' button in the project info page, the selected project is build twice. If I let the scheduler do its work, all is fine and build once when necessary, the problem occurs only when I force the build -- 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: (CONTINUUM-1333) show in project group summary per project also the status counters (as they are shown on the project groups pages)
[ http://jira.codehaus.org/browse/CONTINUUM-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101123 ] tony nys commented on CONTINUUM-1333: - I mean the total number of success builds/failure/error I guess on the project groups page, it is the #subprojects show in project group summary per project also the status counters (as they are shown on the project groups pages) --- Key: CONTINUUM-1333 URL: http://jira.codehaus.org/browse/CONTINUUM-1333 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-alpha-2 Reporter: tony nys show in project group summary per project also the status counters (as they are shown on the project groups pages) -- 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] Closed: (CONTINUUM-671) Small visualization issue
[ http://jira.codehaus.org/browse/CONTINUUM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-671. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: (was: 1.1-beta-1) 1.1-alpha-1 Seems to be ok with 1.1 Small visualization issue - Key: CONTINUUM-671 URL: http://jira.codehaus.org/browse/CONTINUUM-671 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.0.3 Reporter: Reinhard Spisser Assignee: Emmanuel Venisse Priority: Minor Fix For: 1.1-alpha-1 When Continuum is opened the first time with a browser and the user selects the build now button, the actual status of the build is not shown (buttons are not greyed out, building icon is not displayed in the Build column). The issue occurs only when no build is already in progress. Builds are performed correctly, the current state of the build is not correctly displayed. A click on Show Projects will show the real state of the build. Guest users must be enabled to build projects to reproduce this issue. This issue does not occur with authenticated users. -- 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: (MEV-539) XStream 1.2.x relocation POMs wrong on central repo
XStream 1.2.x relocation POMs wrong on central repo --- Key: MEV-539 URL: http://jira.codehaus.org/browse/MEV-539 Project: Maven Evangelism Issue Type: Task Components: Invalid POM Reporter: Joerg Schaible XStream has been relocated from xstream to com.thoughtworks.xstream since version 1.2. However, the provided relocation POMs did miss the modelVersion element, so it does not work (as reported on Maven's user list http://www.mail-archive.com/[EMAIL PROTECTED]/msg68494.html). Meanwhile we updated our POMs in the Codehaus repo, regenerated the md5 files and added also the missing sha1 files. Unfortunately the modified files (POMs and MD5) are not synchronized to the central repo anymore, while the new SHA1 files have been transfered. So please someone with proper rights on central should remove the pom and md5 files in xstream/xstream/*/* to get the corrected ones with the next Codehaus synchronization. Thanks, Jörg -- 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] Closed: (CONTINUUM-817) The generated output in the Working Copy page displays the wrong content
[ http://jira.codehaus.org/browse/CONTINUUM-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-817. -- Assignee: Emmanuel Venisse Resolution: Fixed The generated output in the Working Copy page displays the wrong content Key: CONTINUUM-817 URL: http://jira.codehaus.org/browse/CONTINUUM-817 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1-alpha-1 Environment: Linux FC4, Maven 2.0.4, JDK 1.5 Reporter: Napoleon Esmundo C. Ramirez Assignee: Emmanuel Venisse Fix For: 1.1-beta-1 The Working Copy page displays html codes (which it shouldn't). In the page source, nbsp; is generated as amp;nbsp; and so on... -- 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: (CONTINUUM-737) Database log contains continuum user passwords in clear text
[ http://jira.codehaus.org/browse/CONTINUUM-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101126 ] Emmanuel Venisse commented on CONTINUUM-737: which log file? Database log contains continuum user passwords in clear text Key: CONTINUUM-737 URL: http://jira.codehaus.org/browse/CONTINUUM-737 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.0.3 Reporter: Bernhard Wellhöfer Priority: Minor Fix For: To Sort Hello, The database log contains the continuum user passwords in clear text. This is kind of a security issue. Regards, Bernd -- 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] Updated: (CONTINUUM-1199) Password Characters Not Supported in HTTP Authentication
[ http://jira.codehaus.org/browse/CONTINUUM-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1199: Fix Version/s: (was: 1.1-beta-1) To Sort Password Characters Not Supported in HTTP Authentication Key: CONTINUUM-1199 URL: http://jira.codehaus.org/browse/CONTINUUM-1199 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1-alpha-1 Reporter: Stephen Duncan Jr Fix For: To Sort When entering a url +username + password to download a pom to configure a project, certain password characters will cause it to fail. This is because the password is inserted into the url, so url special characters (@,?, etc) will not work. The password should be provided in response to the challenge, rather than as part of the url. -- 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] Updated: (CONTINUUM-1200) Password Characters Not Supported in SCM Checkout
[ http://jira.codehaus.org/browse/CONTINUUM-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1200: Fix Version/s: (was: 1.1-beta-1) To Sort Password Characters Not Supported in SCM Checkout - Key: CONTINUUM-1200 URL: http://jira.codehaus.org/browse/CONTINUUM-1200 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.1-alpha-1 Reporter: Stephen Duncan Jr Fix For: To Sort Certain characters are not supported for the password for an SCM checkout. For instance if a ')' is the first character, then the command fails. This is because the password is provided as a CLI parameter, and is not surrounded by quotes. Obviously, adding quotes might break other passwords, so it would be best to pass the password along some other way. -- 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] Updated: (CONTINUUM-383) Build Status Notification Information Promotion
[ http://jira.codehaus.org/browse/CONTINUUM-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-383: --- Fix Version/s: (was: 1.1-beta-1) To Sort Build Status Notification Information Promotion Key: CONTINUUM-383 URL: http://jira.codehaus.org/browse/CONTINUUM-383 Project: Continuum Issue Type: Improvement Components: Notifier - Mail Affects Versions: 1.0.1 Reporter: Natalie Burdick Fix For: To Sort Change to build status notification e-mail from Continuum, so that specific Build Failure information is displayed at the Top (and Bottom) of the report -- see below for sample: Build statistics: State: Failed Failure(s): File.. /home/foconer/maven/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly Element... maven:reactor Line.. 217 Column 9 Unable to obtain goal [test:test] -- /home/foconer/maven/.maven/cache/maven-test-plugin-1.6.2/plugin.jelly:181:54: fail Previous State: Failed Started at: Thu, 27 Oct 2005 15:02:38 -0700 Finished at: Thu, 27 Oct 2005 15:06:36 -0700 Total time: 3m 57s Build Trigger: Schedule Exit code: 70 Building machine hostname: iago Operating system : Linux(unknown) Java version : 1.5.0_05(Sun Microsystems Inc.) Changes assembly/project.xml assembly/src/release/examples/basic/servicemix.xml assembly/src/release/examples/jms-binding/servicemix.xml assembly/src/release/examples/bpel/servicemix.xml assembly/src/release/examples/file-binding/servicemix.xml assembly/src/release/examples/http-binding/servicemix.xml assembly/src/release/examples/quartz-binding/servicemix.xml project.properties servicemix-all/maven.xml servicemix-all/project.xml core/project.properties core/maven.xml core/project.xml etc/project.properties etc/maven.xml Output: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 build:start: clean:clean: [delete] Deleting directory /opt/continuum/continuum-1.0-beta-1/apps/continuum/working-directory/2/target init: [echo] init basedir=/opt/continuum/continuum-1.0-beta-1/apps/continuum/working-directory/2 jar:install: multiproject:projects-init: [echo] Gathering project list Starting the reactor... Our processing order: ServiceMix :: JBI ServiceMix :: Core ServiceMix :: Components ServiceMix :: XFire ServiceMix :: JAXWS ServiceMix Full Package + | Gathering project list ServiceMix :: JBI | Memory: 5M/7M + + | Gathering project list ServiceMix :: Core | Memory: 5M/7M + + | Gathering project list ServiceMix :: Components | Memory: 5M/7M + + | Gathering project list ServiceMix :: XFire | Memory: 5M/7M + + | Gathering project list ServiceMix :: JAXWS | Memory: 5M/7M + + | Gathering project list ServiceMix Full Package | Memory: 5M/7M + Starting the reactor... Our processing order: ServiceMix :: JBI ServiceMix :: Core ServiceMix :: Components ServiceMix :: XFire ServiceMix :: JAXWS ServiceMix Full Package + | Executing jar:install ServiceMix :: JBI | Memory: 5M/7M + multiproject:goal: build:start: java:prepare-filesystem: java:compile: [echo] Compiling to /opt/continuum/continuum-1.0-beta-1/apps/continuum/working-directory/2/jbi/target/classes java:jar-resources: test:prepare-filesystem: test:test-resources: test:compile: [echo] No test source files to compile. test:test: [echo] No tests to run. Copying: from '/opt/continuum/continuum-1.0-beta-1/apps/continuum/working-directory/2/jbi/target/servicemix-jbi-2.0-SNAPSHOT.jar' to: '/home/foconer/maven/.maven/repository/servicemix/jars/servicemix-jbi-2.0-SNAPSHOT.jar' Copying: from
[jira] Updated: (CONTINUUM-256) trace memory leak with yourkit
[ http://jira.codehaus.org/browse/CONTINUUM-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-256: --- Fix Version/s: (was: 1.1-beta-1) To Sort trace memory leak with yourkit -- Key: CONTINUUM-256 URL: http://jira.codehaus.org/browse/CONTINUUM-256 Project: Continuum Issue Type: Bug Components: Core system Reporter: Brett Porter Fix For: To Sort Attachments: nohup.out.tar.gz continuum has been spitting OOME in our test environment -- 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] Updated: (CONTINUUM-745) Uploading pom file does not support projects with modules
[ http://jira.codehaus.org/browse/CONTINUUM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-745: --- Fix Version/s: (was: 1.1-beta-1) To Sort Uploading pom file does not support projects with modules - Key: CONTINUUM-745 URL: http://jira.codehaus.org/browse/CONTINUUM-745 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.0.3 Environment: debian linux / ubuntu linux Reporter: Andrew Williams Priority: Critical Fix For: To Sort Uploaded pom files cannot contain sub modules. I see in issue CONTINUUM-425 that this is known, but it really should be possible to fix. Can we not just read the scm and download _before_ trying to read the child poms? -- 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] Updated: (CONTINUUM-801) Maven2: Add Project Homepage URL to the project info page and build result page.
[ http://jira.codehaus.org/browse/CONTINUUM-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-801: --- Fix Version/s: (was: 1.1-beta-1) To Sort Maven2: Add Project Homepage URL to the project info page and build result page. Key: CONTINUUM-801 URL: http://jira.codehaus.org/browse/CONTINUUM-801 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.0.3 Reporter: Sharmarke Aden Priority: Minor Fix For: To Sort Attachments: continuum_webinterface_homepage.patch In maven 2 you can specify a URL for your project's homepage in the pom.xml. It would be nice if a link to this URL could be show on the project info page and the build result page of continuum web interface. Attached is a patch that adds a row containing project homepage to both View.vm and ProjectBuild.vm if the property $project.url exists. -- 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] Updated: (CONTINUUM-731) New Example: XML-RPC Calls in Groovy
[ http://jira.codehaus.org/browse/CONTINUUM-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-731: --- Fix Version/s: (was: 1.1-beta-1) To Sort New Example: XML-RPC Calls in Groovy Key: CONTINUUM-731 URL: http://jira.codehaus.org/browse/CONTINUUM-731 Project: Continuum Issue Type: Improvement Components: XMLRPC Interface Reporter: Michael Rimov Priority: Minor Fix For: To Sort Attachments: getprojects.groovy I spend the evening learning about XML-RPC in general, Groovy Client Implementations, and finally, pulled it alltogether with some calls to my own continuum repository. So I figured I could at least clean up my work and submit it as a potential for a documentation example. It will have to be updated for authentication as soon as CONTINUUM-684 is fixed, but until then I hope this helps. -Mike (R) -- 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] Updated: (CONTINUUM-1054) IllegalStateException stack adding pom
[ http://jira.codehaus.org/browse/CONTINUUM-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1054: Fix Version/s: (was: 1.1-beta-1) To Sort IllegalStateException stack adding pom -- Key: CONTINUUM-1054 URL: http://jira.codehaus.org/browse/CONTINUUM-1054 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1-alpha-1 Reporter: Carlos Sanchez Fix For: To Sort Adding a m2 pom from a web location causes this stack trace, although seems to work fine 2006-12-13 10:46:07,109 [SocketListener0-1] INFO DispatcherUtils - Unable to find 'webwork.multipart.saveDir' property setting. Defaulting to javax.servlet.context.tempdir 2006-12-13 10:46:07,156 [SocketListener0-1] WARN MultiPartRequest - Item is a file upload of 0 size, ignoring 2006-12-13 10:46:07,156 [SocketListener0-1] ERROR DispatcherUtils - Error setting character encoding to 'UTF-8' - ignoring. java.lang.IllegalStateException: getReader() or getInputStream() called at org.mortbay.jetty.servlet.ServletHttpRequest.setCharacterEncoding(ServletHttpRequest.java:602) at javax.servlet.ServletRequestWrapper.setCharacterEncoding(ServletRequestWrapper.java:112) at com.opensymphony.webwork.dispatcher.DispatcherUtils.prepare(DispatcherUtils.java:392) at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:160) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) at org.mortbay.http.HttpServer.service(HttpServer.java:909) at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) -- 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] Updated: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-509: --- Fix Version/s: (was: 1.1-beta-1) To Sort Ability to process scheduled builds the same as forced builds. -- Key: CONTINUUM-509 URL: http://jira.codehaus.org/browse/CONTINUUM-509 Project: Continuum Issue Type: Improvement Components: Core system Affects Versions: 1.0.2 Reporter: Shinobu Kawai Fix For: To Sort It would be great if you could configure a build schedule to act like a forced build on the scheduled build. The use case for this is when you have two build definitions: - One will be set to default for a forced, light build. For example, install the artifact. - Another will be set to a scheduled, heavy build. For example, deploy the artifact and the project site. If the default build is triggered, the other build will be skipped since nothing has been updated since the forced build. And we do not want to do heavy stuff in the default build. -- 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] Updated: (CONTINUUM-688) The application.xml file should only specify one component to start up
[ http://jira.codehaus.org/browse/CONTINUUM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-688: --- Fix Version/s: (was: 1.1-beta-1) To Sort The application.xml file should only specify one component to start up -- Key: CONTINUUM-688 URL: http://jira.codehaus.org/browse/CONTINUUM-688 Project: Continuum Issue Type: Improvement Components: Core system Affects Versions: 1.1-alpha-1 Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: To Sort A Plexus application should encapsulate all other components it uses. Right now the load-on-start specifies the continuum application and the task queues. It should only be the continuum application. -- 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] Updated: (CONTINUUM-1163) Flat SCM Structure + Continuum = broken module-links on site
[ http://jira.codehaus.org/browse/CONTINUUM-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1163: Fix Version/s: (was: 1.1-beta-1) To Sort Flat SCM Structure + Continuum = broken module-links on site Key: CONTINUUM-1163 URL: http://jira.codehaus.org/browse/CONTINUUM-1163 Project: Continuum Issue Type: Wish Components: Integration - Maven 2 Affects Versions: 1.0.2 Reporter: Patrick Huber Fix For: To Sort Attachments: continuum-api-patch.txt, continuum-core-patch.txt We have a flat project structure and we're gradually adding maven support. The layout looks like this: /masterproject/trunk/pom.xml /component/trunk/pom.xml /component/trunk/subcomponent1/pom.xml /component/trunk/subcomponent2/pom.xml in out masterproject/trunk/pom.xml, the module is defined like this: module../../component/trunk/module Building locally works fine, but when the build is run in continuum, it can't find the module because continuum has its own layout. The annoying result is, that our menu ref=module/ will print a href and text of ../../component/trunk in the modules menu. The build output contains this: [WARNING] No filesystem module-POM available How do we get this to work locally as well as in continuum? -- 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] Updated: (CONTINUUM-467) observe folder for changes which can trigger a build
[ http://jira.codehaus.org/browse/CONTINUUM-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-467: --- Fix Version/s: (was: 1.1-beta-1) To Sort observe folder for changes which can trigger a build Key: CONTINUUM-467 URL: http://jira.codehaus.org/browse/CONTINUUM-467 Project: Continuum Issue Type: New Feature Components: Core system Environment: all Reporter: yo Priority: Minor Fix For: To Sort It would be nice if another way to trigger a build would be to observe a folder for changes. everytime someone commits something back to the repo a file is created in a folder which continuum observes and triggers the build of the project by the name of the file. That was conitnuum does not have to say query a hundreds svnrepos if something changed. Greetings Yo -- 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] Updated: (CONTINUUM-723) strange trouble on solaris
[ http://jira.codehaus.org/browse/CONTINUUM-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-723: --- Fix Version/s: (was: 1.1-beta-1) To Sort strange trouble on solaris --- Key: CONTINUUM-723 URL: http://jira.codehaus.org/browse/CONTINUUM-723 Project: Continuum Issue Type: Bug Components: Environmental Affects Versions: 1.0.3 Environment: solaris Reporter: Olivier Lamy Priority: Critical Fix For: To Sort Attachments: CONTINUUM-723.tar.gz Hi, I have a junit test with contains the following code : SimpleDateFormat simpleDateFormat = new SimpleDateFormat( -MM-dd, Locale.FRANCE ); // harcoded date due to xmlunit comparaison Date timeStamp = simpleDateFormat.parse( 2001-05-28 ); return DateTools.setNoonHour( timeStamp ); FastDateFormat.getInstance( -MM-dd'T'HH:mm:ss.SSSZZ ).format(date); On windows+cygwin : 2001-05-28T12:00:00.000+02:00 On solaris with same user who start continuum exec junit with cli : 2001-05-28T12:00:00.000+02:00 The same junit with continuum says : 2001-05-28T12:00:00.000+00:00 Error says : Expected attribute value '2001-05-28T12:00:00.000+02:00' but was '2001-05-28T12:00:00.000+00:00' - comparing at /OTA_HotelAvailRS[1]/@TimeStamp to at /OTA_HotelAvailRS[1]/@TimeStamp I start continuum with $CONTINUUM_HOME/bin/plexus.sh /dev/null The .profile contains : ... LANG=en_US.ISO8859-15 export LANG ##opts maven MAVEN_OPTS=-Xmx512m -Xms512m -Dfile.encoding=ISO-8859-1 export MAVEN_OPTS ... I don't change anything on plexus.sh script. Any ideas ?? Thanks, -- Olivier -- 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] Updated: (CONTINUUM-1176) Mail configuration is consistent (registration email vs. build result email)
[ http://jira.codehaus.org/browse/CONTINUUM-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1176: Fix Version/s: (was: 1.1-beta-1) To Sort Mail configuration is consistent (registration email vs. build result email) Key: CONTINUUM-1176 URL: http://jira.codehaus.org/browse/CONTINUUM-1176 Project: Continuum Issue Type: Bug Components: Notifier - Mail Affects Versions: 1.1-alpha-1 Environment: Webapp SNAPSHOT - 20070214.0300 Reporter: Stephane Nicoll Priority: Minor Fix For: To Sort Mail configuration is inconsistent: * Mail sent for build results uses the application.xml configuration (MailNotifier) * Mail sent to validate a new user registration seems to use roughly the JNDI Mail session. It does not set the fromName and fromAddress parameter specified in application.xml -- 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] Updated: (CONTINUUM-358) User Authentication via LDAP
[ http://jira.codehaus.org/browse/CONTINUUM-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-358: --- Fix Version/s: (was: 1.1-beta-1) To Sort User Authentication via LDAP Key: CONTINUUM-358 URL: http://jira.codehaus.org/browse/CONTINUUM-358 Project: Continuum Issue Type: New Feature Components: Web interface Reporter: Frank Zhao Fix For: To Sort Please add LDAP support for the user authentication in Continuum user management function. -- 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] Updated: (CONTINUUM-516) Add a wait page when enqueuing projects
[ http://jira.codehaus.org/browse/CONTINUUM-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-516: --- Fix Version/s: (was: 1.1-beta-1) To Sort Add a wait page when enqueuing projects --- Key: CONTINUUM-516 URL: http://jira.codehaus.org/browse/CONTINUUM-516 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Emmanuel Venisse Fix For: To Sort -- 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] Updated: (CONTINUUM-704) Make columns on the project summary page sortable.
[ http://jira.codehaus.org/browse/CONTINUUM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-704: --- Fix Version/s: (was: 1.1-beta-1) To Sort Make columns on the project summary page sortable. -- Key: CONTINUUM-704 URL: http://jira.codehaus.org/browse/CONTINUUM-704 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Paul Spencer Fix For: To Sort Making the columns on the Project Summary page sortable would be very useful. As an example you could sort by build status, which is the first column of icons, to see all of the failed builds group together. I added an issue requesting the addition of build date column. Sorting by this column will allow the user to see the order projects where build. -- 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] Updated: (CONTINUUM-515) Add a wait page when adding a project
[ http://jira.codehaus.org/browse/CONTINUUM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-515: --- Fix Version/s: (was: 1.1-beta-1) To Sort Add a wait page when adding a project - Key: CONTINUUM-515 URL: http://jira.codehaus.org/browse/CONTINUUM-515 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Emmanuel Venisse Fix For: To Sort Attachments: CONTINUUM-515, CONTINUUM-515 -- 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] Updated: (CONTINUUM-737) Database log contains continuum user passwords in clear text
[ http://jira.codehaus.org/browse/CONTINUUM-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-737: --- Fix Version/s: (was: 1.1-beta-1) To Sort Database log contains continuum user passwords in clear text Key: CONTINUUM-737 URL: http://jira.codehaus.org/browse/CONTINUUM-737 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.0.3 Reporter: Bernhard Wellhöfer Priority: Minor Fix For: To Sort Hello, The database log contains the continuum user passwords in clear text. This is kind of a security issue. Regards, Bernd -- 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] Updated: (CONTINUUM-703) Display of last build date on Project Summary page
[ http://jira.codehaus.org/browse/CONTINUUM-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-703: --- Fix Version/s: (was: 1.1-beta-1) To Sort Display of last build date on Project Summary page -- Key: CONTINUUM-703 URL: http://jira.codehaus.org/browse/CONTINUUM-703 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Paul Spencer Fix For: To Sort Adding the date of the last build to the Project Summary pages would be very useful. At the very least the user can tell how log it has been since a build was attempted for a project without having to view the builds history. -- 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] Updated: (CONTINUUM-458) Trigger scripts ?
[ http://jira.codehaus.org/browse/CONTINUUM-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-458: --- Fix Version/s: (was: 1.1-beta-1) 1.1 Trigger scripts ? -- Key: CONTINUUM-458 URL: http://jira.codehaus.org/browse/CONTINUUM-458 Project: Continuum Issue Type: New Feature Components: Documentation, XMLRPC Interface Affects Versions: 1.0.1 Reporter: Grégory Joseph Fix For: 1.1 http://maven.apache.org/continuum/guides/getting-started/index.html mentions 2 python scripts. However, these are not present in the 1.0.1 tgz distribution. I hope these are useable as on-commit scripts, to trigger builds when commiting. Could be extra nice to have (or others) downloadable as separate artifact, in order to use them as on-commit trigger scripts, for instance when your continuum instance runs remotely from the scm server, you wouldn't necessarily want your scm admin to have to get the 12mb archive ;) -- 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] Updated: (CONTINUUM-1204) Fix permissons on the CONTINUUMUSER space
[ http://jira.codehaus.org/browse/CONTINUUM-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1204: Fix Version/s: (was: 1.1-beta-1) 1.1 Fix permissons on the CONTINUUMUSER space --- Key: CONTINUUM-1204 URL: http://jira.codehaus.org/browse/CONTINUUM-1204 Project: Continuum Issue Type: Task Components: Documentation Reporter: Wendy Smoak Fix For: 1.1 Unlike MAVENUSER, the public Continuum wiki space is not visible unless you're logged in. http://docs.codehaus.org/display/CONTINUUMUSER/Home -- 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] Updated: (CONTINUUM-253) Create a matrix of databases that Continuum can work with
[ http://jira.codehaus.org/browse/CONTINUUM-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-253: --- Fix Version/s: (was: 1.1-beta-1) 1.1 Create a matrix of databases that Continuum can work with - Key: CONTINUUM-253 URL: http://jira.codehaus.org/browse/CONTINUUM-253 Project: Continuum Issue Type: Task Components: Database, Documentation Reporter: Jason van Zyl Fix For: 1.1 t -- 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] Updated: (CONTINUUM-1313) Document changes to XMLRPC
[ http://jira.codehaus.org/browse/CONTINUUM-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1313: Fix Version/s: (was: 1.1-beta-1) 1.1 Document changes to XMLRPC -- Key: CONTINUUM-1313 URL: http://jira.codehaus.org/browse/CONTINUUM-1313 Project: Continuum Issue Type: Bug Components: XMLRPC Interface Affects Versions: 1.1-alpha-2 Reporter: Wendy Smoak Fix For: 1.1 Document the changes made for CONTINUUM-1269, which include a complete refactoring, use of the webapp port, and the addition of security -- 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] Updated: (CONTINUUM-570) Documentation to add for war deployment in several container
[ http://jira.codehaus.org/browse/CONTINUUM-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-570: --- Fix Version/s: (was: 1.1-beta-1) 1.1 Documentation to add for war deployment in several container Key: CONTINUUM-570 URL: http://jira.codehaus.org/browse/CONTINUUM-570 Project: Continuum Issue Type: Task Components: Documentation Reporter: Emmanuel Venisse Fix For: 1.1 - Need doc for Jetty 6 - Need doc for Jetty 5 - Need doc for Tomcat 4 - Need doc for Tomcat 5 - Need doc for Weblogic (if we can access to a server) - Need doc for Websphere (if we can access to a server) - [Add other 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
[jira] Updated: (CONTINUUM-1191) editProject: NoSuchMethodException:
[
http://jira.codehaus.org/browse/CONTINUUM-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated CONTINUUM-1191:
Fix Version/s: (was: 1.1-beta-1)
1.1-beta-2
editProject: NoSuchMethodException:
---
Key: CONTINUUM-1191
URL: http://jira.codehaus.org/browse/CONTINUUM-1191
Project: Continuum
Issue Type: Bug
Components: XMLRPC Interface
Affects Versions: 1.0.3
Reporter: Patrick Huber
Fix For: 1.1-beta-2
I'm writing a small application that's intended to consolidate all build
goals and arguments for all our projects in continuum:
Client:
---
String address = http://continuumhost:8000/continuum;;
ProjectsReader reader = new ProjectsReader(new URL(address));
for (Project project : reader.readProjects()) {
// reader.refreshProject(project);
ListBuildDefinition defs = project.getBuildDefinitions();
if (defs != null defs.size() == 1) {
for (BuildDefinition def : defs) {
def.setGoals(clean deploy site:site site:deploy
eclipse:eclipse scm:checkin);
def.setArguments(--batch-mode --non-recursive
-Dincludes=\.project .classpath .settings\ -Dmessage=\continuum checkin of
generated eclipse files\);
}
}
else {
System.out.println(Project + project.getId() + +
project.getName() + has not exactly one build);
}
reader.editProject(project);
---
Exception:
---
Exception in thread main org.apache.xmlrpc.XmlRpcException:
java.lang.NoSuchMethodException:
org.apache.maven.continuum.xmlrpc.DefaultContinuumXmlRpc.updatenullProject(java.util.Hashtable)
at
org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:102)
at
org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:69)
at
org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:72)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:193)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:184)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:177)
at
org.apache.maven.continuum.rpc.ProjectsReader.editProject(ProjectsReader.java:127)
at SampleClient.main(SampleClient.java:55)
---
It doesn't matter wether or not reader.refreshProject(project); is active.
Am I doing something wrong here or is this a bug? The documentation only
shows how to read a project...
--
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] Updated: (CONTINUUM-774) Better support for multiprojects
[ http://jira.codehaus.org/browse/CONTINUUM-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-774: --- Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Better support for multiprojects Key: CONTINUUM-774 URL: http://jira.codehaus.org/browse/CONTINUUM-774 Project: Continuum Issue Type: Improvement Components: Project Grouping Reporter: Tomasz Pik Priority: Minor Fix For: 1.1-beta-2 Currently when multiproject is being added to continuum, then top project is being registered as 'non-recursive' and all submodules are being added as separate projects. It will be nice to have the possibility to define (during initiial POM loading) if project should be treat that way or as a multiproject with full recursive build and without adding subprojects. I'm doing that manually, by redefining build section for top project and removing subprojects. -- 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] Updated: (CONTINUUM-850) Continuum ignores a new given password for a cvs account until the cvsroot is also changed
[ http://jira.codehaus.org/browse/CONTINUUM-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-850: --- Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Continuum ignores a new given password for a cvs account until the cvsroot is also changed -- Key: CONTINUUM-850 URL: http://jira.codehaus.org/browse/CONTINUUM-850 Project: Continuum Issue Type: Bug Components: SCM, Web interface Affects Versions: 1.0.3 Reporter: Peter Kehren Fix For: 1.1-beta-2 I changed (only!) the password of a cvs account and set this new password in a project definition in continuum by the web interface. The next build of the project did not work, because of a wrong password (no access to cvs was reported). It seems, that continuum uses the old password although a new password was set. After changing the cvsroot (replaced ip number by dns entry; 100% NOT the reason for this error) the cvs system could be accessed; the new password was used. -- 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] Updated: (CONTINUUM-666) Added (Jabber) Notifiers didn't persist
[ http://jira.codehaus.org/browse/CONTINUUM-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-666: --- Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Added (Jabber) Notifiers didn't persist --- Key: CONTINUUM-666 URL: http://jira.codehaus.org/browse/CONTINUUM-666 Project: Continuum Issue Type: Bug Components: Core system, Notifier - Jabber Affects Versions: 1.0.3 Environment: Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX build ca142ifx-20051115 (SR3 + 94164 + 97403 + 97482) (JIT enabled: jitc)) Reporter: ariva Assignee: Rahul Thakur Fix For: 1.1-beta-2 After imported a maven1 project and added a jabber notifier (by web interface) it seems that when a new build starts, the notifier is vanished. I have looked into derby db but it seems that there is no data in project_notifiers table. -- 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] Updated: (CONTINUUM-1167) Patch to add JBoss support
[ http://jira.codehaus.org/browse/CONTINUUM-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1167: Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Patch to add JBoss support -- Key: CONTINUUM-1167 URL: http://jira.codehaus.org/browse/CONTINUUM-1167 Project: Continuum Issue Type: Wish Reporter: Hilco Wijbenga Priority: Minor Fix For: 1.1-beta-2 Attachments: continuum_jboss.patch, continuum_jboss_2.patch, continuum_jboss_2.patch I've been bold enough to prepare a little patch that adds explicit support for JBoss to the Continuum WAR. The patch adds a jboss-web.xml file (this should be totally harmless) and adds two resource-refs to web.xml. I get the impression that this latter change is harmless as well, or would it break other app servers? Anyway, here's the patch. I hope it can get applied, otherwise I'll just keep on doing it by hand. :-) With this applied the only thing left to do is add a derby-ds.xml file to the JBoss deployment directory. And make sure JBoss has a Derby driver, of course. -- 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] Updated: (CONTINUUM-821) The Project.getBuildResults() method returns an empty list
[
http://jira.codehaus.org/browse/CONTINUUM-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated CONTINUUM-821:
---
Fix Version/s: (was: 1.1-beta-1)
1.1-beta-2
The Project.getBuildResults() method returns an empty list
--
Key: CONTINUUM-821
URL: http://jira.codehaus.org/browse/CONTINUUM-821
Project: Continuum
Issue Type: Bug
Components: XMLRPC Interface
Affects Versions: 1.0.3
Environment: JDK 1.5.0_07, Linux (Fedora Core 5)
Reporter: John Smart
Fix For: 1.1-beta-2
The Project.getBuildResults() method returns an empty list. The unit test is
shown here:
@Test
public void testGetProjectBuildResults() throws XmlRpcException,
IOException {
String url = http://localhost:8000/continuum;;
ProjectsReader pr = new ProjectsReader( new URL( url ) );
Project[] projects = projects = pr.readProjects();
//
// Note: All the projects on the localhost server have builds
//
for ( Project project : projects){
ListBuildResult buildResults = project.getBuildResults();
//
// Builds have been defined
//
assertTrue(project.getBuildDefinitions().size() 0);
//
// Builds have been done
//
assertTrue(project.getBuildNumber() 0);
//
// We can access the build results
//
assertNotNull(buildResults);
//
// Test fails here:
//
assertTrue(buildResults.size() 0);
}
}
--
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] Updated: (CONTINUUM-1166) Integration test failures: AccountSecurityTest
[ http://jira.codehaus.org/browse/CONTINUUM-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1166: Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Integration test failures: AccountSecurityTest -- Key: CONTINUUM-1166 URL: http://jira.codehaus.org/browse/CONTINUUM-1166 Project: Continuum Issue Type: Task Components: Testing Affects Versions: 1.1-alpha-1 Environment: WinXP Continuum 1.1-SNAPSHOT r507397 Reporter: Wendy Smoak Fix For: 1.1-beta-2 Attachments: AccountSecurityTest-r507420.txt, org.apache.continuum.web.test.AccountSecurityTest.txt --- Test set: org.apache.continuum.web.test.AccountSecurityTest --- Tests run: 5, Failures: 4, Errors: 1, Skipped: 0, Time elapsed: 107.797 sec FAILURE! When editing a user, effective roles are displayed on the first page, but it is necessary to click the 'Edit Roles' in order to add or delete roles. Full Surefire report attached. -- 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] Updated: (CONTINUUM-1194) Project is stuck in the Build in Progress state if the associated exception has more than 8192 chars
[ http://jira.codehaus.org/browse/CONTINUUM-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1194: Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Project is stuck in the Build in Progress state if the associated exception has more than 8192 chars -- Key: CONTINUUM-1194 URL: http://jira.codehaus.org/browse/CONTINUUM-1194 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.1-alpha-1 Reporter: Stephane Nicoll Fix For: 1.1-beta-2 Attachments: screenshot.png We have added unit tests to one of our project and some of them are crashing from time to time due to a race condition with the database connections. Since then, the project is always in the Build In progress state even if the build is actually terminated in the log (Build failure because one test failed). The project never leaves this state, if we consult the builds summary we have a couple of builds in the Build In progress state (?!) See screenshot. -- 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] Updated: (CONTINUUM-1181) Continuum aborts when running Postgres under JBoss
[ http://jira.codehaus.org/browse/CONTINUUM-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1181: Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Continuum aborts when running Postgres under JBoss -- Key: CONTINUUM-1181 URL: http://jira.codehaus.org/browse/CONTINUUM-1181 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.1-alpha-1 Environment: MS Windows XP Pro SP2 postgres 8.1.4-1 with JDBC Driver postgresql-8.1-408.jdbc3 JBoss 4.0.5.GA Reporter: thierry lach Fix For: 1.1-beta-2 I'm trying to get Continuum to store its data in a postgres database while running under JBoss and I'm getting an exception. It seems that someone is trying to change the transaction isolation during a transaction. Excerpt from JBoss logs follows... 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - Starting Continuum. 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - Continuum 1.1-SNAPSHOT started! 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - --- 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum -\ ^__^ 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - \ (oo)\___ 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum -(__)\ )\/\ 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum -||w | 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum -|| || 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - 2007-02-21 12:56:02,613 [ScannerThread] INFO ContinuumInitializer:default - Continuum initializer running ... 2007-02-21 12:56:02,644 [ScannerThread] WARN LocalManagedConnectionFactory - Error resetting transaction isolation org.postgresql.util.PSQLException: Cannot change transaction isolation level in the middle of a transaction. at org.postgresql.jdbc2.AbstractJdbc2Connection.setTransactionIsolation(AbstractJdbc2Connection.java:733) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.cleanup(BaseWrapperManagedConnection.java:189) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.returnConnection(InternalManagedConnectionPool.java :320) at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.returnConnection(JBossManagedConnectionPool.java:620) at org.jboss.resource.connectionmanager.BaseConnectionManager2.returnManagedConnection (BaseConnectionManager2.java:363) at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:623) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle (BaseWrapperManagedConnection.java:266) at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129) at org.jpox.store.rdbms.adapter.DatabaseAdapter.getConnection(DatabaseAdapter.java :928) at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.begin(RDBMSNonmanagedTransaction.java:324) at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:356) at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached (PlexusJdoUtils.java:346) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1302) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached( JdoContinuumStore.java:1287) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1282) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached (JdoContinuumStore.java:1277) at org.apache.maven.continuum.store.JdoContinuumStore.getSystemConfiguration(JdoContinuumStore.java:1375) at org.apache.maven.continuum.initialization.DefaultContinuumInitializer.initialize (DefaultContinuumInitializer.java:90) at org.apache.maven.continuum.DefaultContinuum.start(DefaultContinuum.java:2281) at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execute(StartPhase.java :33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:130) at
[jira] Updated: (CONTINUUM-837) POM upload screen says file:// URLs are supported but fails if you try one
[ http://jira.codehaus.org/browse/CONTINUUM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-837: --- Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 POM upload screen says file:// URLs are supported but fails if you try one -- Key: CONTINUUM-837 URL: http://jira.codehaus.org/browse/CONTINUUM-837 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.0.3 Reporter: Aaron Mulder Fix For: 1.1-beta-2 The POM upload screen lists file:// among the supported URL types. However, any file:// URL that you try results in a misleading error message. In fact, the file protocol is disabled by default. This screen should explain that file must be manually enabled, and the resulting error message should say that the file protocol is disabled. Ideally it would point you to the correct place to enable it, and mention that until you've started continuum for the first time, the config file you need to edit won't be there (the JAR has to be unpacked first). -- 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] Updated: (CONTINUUM-980) After deleting a project from a group, the UI flow should return to the group summary display.
[ http://jira.codehaus.org/browse/CONTINUUM-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-980: --- Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 After deleting a project from a group, the UI flow should return to the group summary display. -- Key: CONTINUUM-980 URL: http://jira.codehaus.org/browse/CONTINUUM-980 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-alpha-1 Reporter: Christian Gruber Priority: Minor Fix For: 1.1-beta-2 After deleting a project from a group, the UI flow should return to the group summary display. Currently the ui returns to the overall list of groups. -- 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] Updated: (CONTINUUM-1119) Creating a Group with an existing id errors
[ http://jira.codehaus.org/browse/CONTINUUM-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1119: Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Creating a Group with an existing id errors --- Key: CONTINUUM-1119 URL: http://jira.codehaus.org/browse/CONTINUUM-1119 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1-alpha-1 Environment: svn trunk, Tomcat 5.5 Reporter: Henri Yandell Fix For: 1.1-beta-2 If you create a new group with the same group id as another, you get: Error Occurred Show/hide Stack Trace Clicking on the Show/hide doesn't show anything. A plexus user repeated the issue and found this in the log: ERROR Action:addProjectGroup- Error adding project group: Unable to add the requested project group: groupId already exists. -- 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] Updated: (CONTINUUM-1094) Continuum does not build with Sun JDK 6
[
http://jira.codehaus.org/browse/CONTINUUM-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated CONTINUUM-1094:
Fix Version/s: (was: 1.1-beta-1)
1.1-beta-2
Continuum does not build with Sun JDK 6
---
Key: CONTINUUM-1094
URL: http://jira.codehaus.org/browse/CONTINUUM-1094
Project: Continuum
Issue Type: Bug
Components: Environmental
Affects Versions: 1.1-alpha-1
Environment: continuum trunk r490449
linux 2.6.12
Sun JDK 6 (build 1.6.0-b105)
Reporter: Minto van der Sluis
Fix For: 1.1-beta-2
Attachments:
org.apache.maven.continuum.management.DataManagementToolTest.txt
snippet of the build output (mvn clean install).
...
[INFO]
[INFO] Building Continuum Data Management API
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/home/minto/rommel/svn-src/continuum/continuum-data-management/target
[INFO] Deleting directory
/home/minto/rommel/svn-src/continuum/continuum-data-management/target/classes
[INFO] Deleting directory
/home/minto/rommel/svn-src/continuum/continuum-data-management/target/test-classes
[INFO] [plexus:descriptor {execution: generate}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
/home/minto/rommel/svn-src/continuum/continuum-data-management/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 1 source file to
/home/minto/rommel/svn-src/continuum/continuum-data-management/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/minto/rommel/svn-src/continuum/continuum-data-management/target/surefire-reports
---
T E S T S
---
Running org.apache.maven.continuum.management.DataManagementToolTest
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 8.348 sec
FAILURE!
Results :
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
Builds with JDK 5 runs just fine.
--
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] Updated: (CONTINUUM-697) sizes incompatible with mssql (Patch Attached)
[ http://jira.codehaus.org/browse/CONTINUUM-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-697: --- Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 sizes incompatible with mssql (Patch Attached) -- Key: CONTINUUM-697 URL: http://jira.codehaus.org/browse/CONTINUUM-697 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.0.3 Environment: windows/mssql2000 Reporter: Brian Fox Fix For: 1.1-beta-2 Attachments: continuum-697.patch This is my configuration: property namejavax.jdo.option.ConnectionDriverName/name valuenet.sourceforge.jtds.jdbc.Driver/value /property property namejavax.jdo.option.ConnectionURL/name valuejdbc:jtds:sqlserver://cordella.mht.stchome.com:1433/continuum/value /property property namejavax.jdo.option.ConnectionUserName/name valuecontinuum/value /property property namejavax.jdo.option.ConnectionPassword/name valuecontinuum/value /property I get this exception: 3984 [WrapperSimpleAppMain] ERROR JPOX.RDBMS.SCHEMA - An exception was thrown while adding/validating class(es) : The size (8192) given to the column 'COMMENT' exceeds the maximum allowed for any data type (8000). java.sql.SQLException: The size (8192) given to the column 'COMMENT' exceeds the maximum allowed for any data type (8000). 4000 [WrapperSimpleAppMain] ERROR JPOX.RDBMS.SCHEMA - java.sql.SQLException: The size (8192) given to the column 'COMMENT' exceeds the maximum allowed for any data type (8000). -- 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] Updated: (CONTINUUM-709) Runtime error during recording in datanase
[ http://jira.codehaus.org/browse/CONTINUUM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-709: --- Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Runtime error during recording in datanase -- Key: CONTINUUM-709 URL: http://jira.codehaus.org/browse/CONTINUUM-709 Project: Continuum Issue Type: Bug Components: Core system, Database Affects Versions: 1.0.3 Environment: solaris 9 Reporter: Olivier Lamy Fix For: 1.1-beta-2 I have the following strack trace : ERROR 22001: A truncation error was encountered trying to shrink VARCHAR '/OTAReceiver/trunk/ota-rec eiver-parsing/src/main/java/com/ac' to length 255. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown Source) at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) at org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown Source) at org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknown Source) at org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unknown Source) at org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unknown Source) at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source) at org.jpox.store.rdbms.request.Request.executeUpdate(Request.java:78) at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:258) at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) at org.jpox.store.StoreManager.insert(StoreManager.java:739) at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3415) at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3388) at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.jav a:1146) at org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceManager.java:1201) at org.codehaus.plexus.jdo.PlexusJdoUtils.makePersistent(PlexusJdoUtils.java:97) at org.apache.maven.continuum.store.JdoContinuumStore.makePersistent(JdoContinuumStore.java: 524) at org.apache.maven.continuum.store.JdoContinuumStore.addBuildResult(JdoContinuumStore.java: 265) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.makeAndStoreBuildResult (DefaultBuildController.java:443) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildContr oller.java:298) The result is strange : - in the build history the build is marked as succesfull - in the project summary I have the red icon which says failed but no mail received -- Olivier -- 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] Updated: (CONTINUUM-981) Remove button on group actions is ambiguous and should be renamed Delete Group or Remove Group.
[ http://jira.codehaus.org/browse/CONTINUUM-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-981: --- Fix Version/s: (was: 1.1-beta-1) To Sort Remove button on group actions is ambiguous and should be renamed Delete Group or Remove Group. - Key: CONTINUUM-981 URL: http://jira.codehaus.org/browse/CONTINUUM-981 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-alpha-1 Reporter: Christian Gruber Priority: Trivial Fix For: To Sort Remove button on group actions is ambiguous and should be renamed Delete Group or Remove Group. It currently reads as if it would remove some group members. -- 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] Updated: (CONTINUUM-1218) Automatically determine correct POM file location in Build Definition when checking out from SCMs like ClearCase
[ http://jira.codehaus.org/browse/CONTINUUM-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1218: Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Automatically determine correct POM file location in Build Definition when checking out from SCMs like ClearCase Key: CONTINUUM-1218 URL: http://jira.codehaus.org/browse/CONTINUUM-1218 Project: Continuum Issue Type: Improvement Affects Versions: 1.1-alpha-1 Reporter: Arne Degenring Fix For: 1.1-beta-2 SCM-288 has introduced an attribute in CheckoutScmResult that contains the relative path of the project directory, relative to the checkout directory. This is needed for SCMs like ClearCase that do NOT perform the checkout into the checkout directory itself, but into a subdirectory. See SCM-288 for details. This information should be honored by Continuum when adding a new project after checking out the sources. The POM filename of the Build Definition should automatically be set accordingly. In most cases the default pom.xml is sufficient, but in cases like ClearCase it would be e.g. MY_VOB/my/project/dir/pom.xml. -- 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] Updated: (CONTINUUM-1107) Continuum build failes in continuum-core on a clean system
[ http://jira.codehaus.org/browse/CONTINUUM-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1107: Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Continuum build failes in continuum-core on a clean system -- Key: CONTINUUM-1107 URL: http://jira.codehaus.org/browse/CONTINUUM-1107 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.1-alpha-1 Reporter: Roald Bankras Fix For: 1.1-beta-2 Attachments: org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.txt MavenTwoContinuumProjectBuilderTest failes twice: -- 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] Updated: (CONTINUUM-706) XML-RPC Server does not support addition of BuildDefinitions
[ http://jira.codehaus.org/browse/CONTINUUM-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-706: --- Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 XML-RPC Server does not support addition of BuildDefinitions - Key: CONTINUUM-706 URL: http://jira.codehaus.org/browse/CONTINUUM-706 Project: Continuum Issue Type: Bug Components: XMLRPC Interface Affects Versions: 1.0.3 Environment: Win XP SP2 jdk1.5.0_06 Reporter: Adam Leggett Priority: Minor Fix For: 1.1-beta-2 When attempting to add a maven 2 project via ProjectsReader.addProject() it is not possible to add a build definition. This means that subsequent calls to ProjectReader.buildproject fail. -- 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] Updated: (CONTINUUM-990) Pass some continuum information to build tools when executing a build
[ http://jira.codehaus.org/browse/CONTINUUM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-990: --- Fix Version/s: (was: 1.1-beta-1) 1.1-beta-2 Pass some continuum information to build tools when executing a build - Key: CONTINUUM-990 URL: http://jira.codehaus.org/browse/CONTINUUM-990 Project: Continuum Issue Type: New Feature Components: Core system Reporter: John Didion Assignee: Jesse McConnell Priority: Minor Fix For: 1.1-beta-2 Attachments: maven2-build-properties.diff It would be nice to access some information (specifically build numbers) in the build script itself - for example, if I wanted to embed the build number in the jar manifest. I've attached a patch that does this for m2. I'm not sure if you could generalize it to work for all builds, or if you'd have to implement it separately for each build executor. -- 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] Updated: (CONTINUUM-1109) Need a way to override all notifications
[ http://jira.codehaus.org/browse/CONTINUUM-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1109: Fix Version/s: (was: 1.1-beta-1) To Sort Need a way to override all notifications Key: CONTINUUM-1109 URL: http://jira.codehaus.org/browse/CONTINUUM-1109 Project: Continuum Issue Type: New Feature Components: Notifier - AOL, Notifier - IRC, Notifier - Jabber, Notifier - Mail, Notifier - MSN Affects Versions: 1.1-alpha-1 Reporter: Wendy Smoak Fix For: To Sort It is currently possible to override the To: address for all email notifications by setting the to-override element in application.xml. This also needs to be done for IRC notifications, etc. Case in point, if you add Cargo to Continuum, it floods the #cargo channel with notices because there is an IRC notifier configured in Cargo's pom. -- 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] Updated: (CONTINUUM-982) Project Group Actions should be renamed Group Actions to avoid confusion.
[ http://jira.codehaus.org/browse/CONTINUUM-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-982: --- Fix Version/s: (was: 1.1-beta-1) To Sort Project Group Actions should be renamed Group Actions to avoid confusion. - Key: CONTINUUM-982 URL: http://jira.codehaus.org/browse/CONTINUUM-982 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-alpha-1 Reporter: Christian Gruber Priority: Trivial Fix For: To Sort Summary says it all. -- 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] Updated: (CONTINUUM-1192) Ability to disable a project group build definition per project
[ http://jira.codehaus.org/browse/CONTINUUM-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1192: Fix Version/s: (was: 1.1-beta-1) To Sort Ability to disable a project group build definition per project --- Key: CONTINUUM-1192 URL: http://jira.codehaus.org/browse/CONTINUUM-1192 Project: Continuum Issue Type: New Feature Components: Core - Profiles, Web interface Affects Versions: 1.1-alpha-1 Reporter: Stephane Nicoll Fix For: To Sort Project group's build definitions are automatically inherited to any project created within the group which is fine. It would be even better if an administrator had the ability to disable such a build definition per project. For now, the only way is to override the default build definition which is confusing since the group's default build definition is not disabled. -- 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] Updated: (CONTINUUM-605) Add a RecipientSource that derives addresses from the change list
[ http://jira.codehaus.org/browse/CONTINUUM-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-605: --- Fix Version/s: (was: 1.1-beta-1) To Sort Add a RecipientSource that derives addresses from the change list - Key: CONTINUUM-605 URL: http://jira.codehaus.org/browse/CONTINUUM-605 Project: Continuum Issue Type: New Feature Components: Notification Subsystem Reporter: John Didion Fix For: To Sort Attachments: change-list-recipient-source.diff, ChangeListRecipientSource.diff CruiseControl has the nice feature of only sending notification email to those users who submitted the changes in the build. I missed that feature when switching to Continuum, so I implemented it. It compiles a list of scm ids from the change list, then matches them against the developers in the POM to get email addresses. It delegates to the default RecipientSource if there is no change list. -- 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] Updated: (CONTINUUM-1190) Ability to edit nicely a build definition with scope group in a project
[ http://jira.codehaus.org/browse/CONTINUUM-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1190: Fix Version/s: (was: 1.1-beta-1) To Sort Ability to edit nicely a build definition with scope group in a project --- Key: CONTINUUM-1190 URL: http://jira.codehaus.org/browse/CONTINUUM-1190 Project: Continuum Issue Type: New Feature Components: Core - Profiles, Web interface Affects Versions: 1.1-alpha-1 Reporter: Stephane Nicoll Fix For: To Sort When in a particular project, an administrator has the ability to edit a build definition from the GROUP but the current behavior is confusing since the changes is applicable to all projects in the group. Suggestion. When a build definition with scope GROUP is edited within a project, it is transformed automatically in a new build definition with scope PROJECT (with eventually a confirmation message). In general, editing stuff in a project page should only affect the project. -- 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] Updated: (CONTINUUM-774) Better support for multiprojects
[ http://jira.codehaus.org/browse/CONTINUUM-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-774: --- Fix Version/s: (was: 1.1-beta-2) 1.1-beta-1 Better support for multiprojects Key: CONTINUUM-774 URL: http://jira.codehaus.org/browse/CONTINUUM-774 Project: Continuum Issue Type: Improvement Components: Project Grouping Reporter: Tomasz Pik Priority: Minor Fix For: 1.1-beta-1 Currently when multiproject is being added to continuum, then top project is being registered as 'non-recursive' and all submodules are being added as separate projects. It will be nice to have the possibility to define (during initiial POM loading) if project should be treat that way or as a multiproject with full recursive build and without adding subprojects. I'm doing that manually, by redefining build section for top project and removing subprojects. -- 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: (MEV-536) Broken checksums and signature for maven-2.0.7.pom
[ http://jira.codehaus.org/browse/MEV-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101128 ] Max Bowsher commented on MEV-536: - They are not the same issue: - 2.0.6: correct file format, incorrect checksum value - 2.0.7: incorrect file format, correct checksum value Broken checksums and signature for maven-2.0.7.pom -- Key: MEV-536 URL: http://jira.codehaus.org/browse/MEV-536 Project: Maven Evangelism Issue Type: Bug Reporter: Max Bowsher Assignee: Jason van Zyl http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.7/maven-2.0.7.pom .md5 and .sha1 are broken due to being in incorrect format (generated by BSD checksum tools?) .asc is bad signature. -- 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: (DOXIA-123) Create an xdoc dtd for maven 2
[ http://jira.codehaus.org/browse/DOXIA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101130 ] Lukas Theussl commented on DOXIA-123: - A minor point: in m1 an email attribute is required for the author tag, I think this should be relaxed and be made optional. Create an xdoc dtd for maven 2 -- Key: DOXIA-123 URL: http://jira.codehaus.org/browse/DOXIA-123 Project: doxia Issue Type: Task Components: Module - Xdoc Reporter: Lukas Theussl In Maven 1, a valid xdoc was defined to be something that was converted into a valid xhtml document by the m1 xdoc plugin. I guess in m2 the same procedure should be applied to doxia. We need to identify the features that 1) should be added 2) should be removed with respect to the m1 xdoc dtd. -- 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: (MRELEASE-259) Provide a configuration settings for default tag/label to use when releasing
Provide a configuration settings for default tag/label to use when releasing
Key: MRELEASE-259
URL: http://jira.codehaus.org/browse/MRELEASE-259
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Reporter: Wouter Hermeling
Currently the default tag/label proposed is ${artifactId}-${version}
However i would like to only use the version, like this: ${version}
And maybe others would like to use ${project.name$}_${version} or something
else.
This could easily be set via the plugin configuration.
I may provide a patch myself, when i have some more free time.
--
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: (MECLIPSE-290) eclipse:add-maven-repo provides no feedback and can silently fail
eclipse:add-maven-repo provides no feedback and can silently fail - Key: MECLIPSE-290 URL: http://jira.codehaus.org/browse/MECLIPSE-290 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.3 Environment: Windows XP, Cygwin Reporter: Mark Hobson Running eclipse:add-maven-repo with a valid or invalid eclipse.workspace parameter results in a successful build. We should: - display the path of the patched workspace if successful - fail the build if the workspace dir was not found - fail the build if the workspace dir could not be patched (e.g. eclipse is running) -- 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: (MNG-612) implement conflict resolution techniques
[ http://jira.codehaus.org/browse/MNG-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101133 ] Mark Hobson commented on MNG-612: - Wiki: http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers Branch: http://svn.apache.org/repos/asf/maven/components/branches/MNG-612/ implement conflict resolution techniques Key: MNG-612 URL: http://jira.codehaus.org/browse/MNG-612 Project: Maven 2 Issue Type: New Feature Components: Artifacts and Repositories, Design, Patterns Best Practices Reporter: Brett Porter Assignee: Jason van Zyl Priority: Critical Fix For: 2.1.x Attachments: MNG-612-2.patch, MNG-612-3.patch, MNG-612.patch Original Estimate: 8 hours Remaining Estimate: 8 hours currently, the collector only: - selects nearest suggested version in a valid range - latest version from the valid ranges if none suggested - fails if ranges are over-constrained This needs to be configurable: - select newest, even if there is a nearer suggestion - select oldest, even if there is a nearer suggestion - fail if all suggestions don't equate or a range results instead of a single version - ignore over constrained ranges and fallback to some other algorithm - select snapshots even if they weren't explicitly specified -- 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] Updated: (MRELEASE-124) Impossible to depend on a deployed snapshot
[ http://jira.codehaus.org/browse/MRELEASE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tuomas Kiviaho updated MRELEASE-124: Attachment: maven-release-manager-1.0-alpha-4-SNAPSHOT.rev552741.patch Patched against revision 552741 Impossible to depend on a deployed snapshot --- Key: MRELEASE-124 URL: http://jira.codehaus.org/browse/MRELEASE-124 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-4 Reporter: Mike Perham Priority: Critical Attachments: maven-release-manager-1.0-alpha-4-SNAPSHOT.rev552741.patch, maven-release-plugin-2.0-beta-7-SNAPSHOT.rev552741.patch, releasePluginIgnoreSnapshot.patch I have a SNAPSHOT of the war plugin that I built and deployed to fix a blocker for us (MWAR-39) that has not been released. In my POM, I refer to it like this: build plugins plugin artifactIdmaven-war-plugin/artifactId version2.0.1-20060525.222101-1/version I did this specifically so the release plugin would not think it was a SNAPSHOT so I could release the module. But when I do try to release, I get this error: [INFO] Can't release project due to non released dependencies : org.apache.maven.plugins:maven-war-plugin:maven-plugin:2.0.1-SNAPSHOT:runtime in project 'UDDI WAR' (com.webify.fabric:fabric-uddi-web:war:1.1.0-SNAPSHOT) This is because in ArtifactUtils.isSnapshot, it specifically disallows the version pattern created by the deploy plugin. So consider my usecase: I'm Joe Corporate, a user who needs a war bug fix in their build process ASAP. I build and deploy the latest war plugin to my internal repo and reference that explicit timestamp version in my build process. Now I can understand why you disallow this because if I try to build outside of our corporate walls, it will not work. But I can't use the release plugin to release either because it requires me to check the modified POMs into my SCM and the war plugin is in Apache's SCM and I can't check into it. There's only two hack workarounds I can think of: 1) explicitly reversion the jar to not include SNAPSHOT or the specific timestamp pattern. 2) Check the war plugin into our own SCM and release from there, effectively forking the code. Your thoughts? How can we fix bugs in the build process locally and still use the release plugin? -- 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] Updated: (MRELEASE-124) Impossible to depend on a deployed snapshot
[ http://jira.codehaus.org/browse/MRELEASE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tuomas Kiviaho updated MRELEASE-124: Attachment: maven-release-plugin-2.0-beta-7-SNAPSHOT.rev552741.patch Impossible to depend on a deployed snapshot --- Key: MRELEASE-124 URL: http://jira.codehaus.org/browse/MRELEASE-124 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-4 Reporter: Mike Perham Priority: Critical Attachments: maven-release-manager-1.0-alpha-4-SNAPSHOT.rev552741.patch, maven-release-plugin-2.0-beta-7-SNAPSHOT.rev552741.patch, releasePluginIgnoreSnapshot.patch I have a SNAPSHOT of the war plugin that I built and deployed to fix a blocker for us (MWAR-39) that has not been released. In my POM, I refer to it like this: build plugins plugin artifactIdmaven-war-plugin/artifactId version2.0.1-20060525.222101-1/version I did this specifically so the release plugin would not think it was a SNAPSHOT so I could release the module. But when I do try to release, I get this error: [INFO] Can't release project due to non released dependencies : org.apache.maven.plugins:maven-war-plugin:maven-plugin:2.0.1-SNAPSHOT:runtime in project 'UDDI WAR' (com.webify.fabric:fabric-uddi-web:war:1.1.0-SNAPSHOT) This is because in ArtifactUtils.isSnapshot, it specifically disallows the version pattern created by the deploy plugin. So consider my usecase: I'm Joe Corporate, a user who needs a war bug fix in their build process ASAP. I build and deploy the latest war plugin to my internal repo and reference that explicit timestamp version in my build process. Now I can understand why you disallow this because if I try to build outside of our corporate walls, it will not work. But I can't use the release plugin to release either because it requires me to check the modified POMs into my SCM and the war plugin is in Apache's SCM and I can't check into it. There's only two hack workarounds I can think of: 1) explicitly reversion the jar to not include SNAPSHOT or the specific timestamp pattern. 2) Check the war plugin into our own SCM and release from there, effectively forking the code. Your thoughts? How can we fix bugs in the build process locally and still use the release plugin? -- 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: (WAGONSSH-52) scpexe won't honour .ssh/config information
[ http://jira.codehaus.org/browse/WAGONSSH-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101136 ] Jan Torben Heuer commented on WAGONSSH-52: -- Had the same problem, -Duser.name=.. fixed it! This critical bug has not been fixed within one year - is it likely to be fixed in future? If not, will it be honored in the FAQ or the documentation? Other question, can I globaly set this option? (in my pom or in my settings.xml?) scpexe won't honour .ssh/config information --- Key: WAGONSSH-52 URL: http://jira.codehaus.org/browse/WAGONSSH-52 Project: wagon-ssh Issue Type: Bug Affects Versions: 1.0-alpha-6 Reporter: Michael Semb Wever scp test.xml sch-login01.osl.basefarm.net:/www/schibstedsok/data/httpd/dev.schibstedsok.no_443/htdocs/maven2/schibstedsok/commons-log4j/1.3-SNAPSHOT/test.xml from the command line works just fine. My local username is mick, and my login on the sch-login01 machine is mickw. Correspondingly my .ssh/config file contains: Host sch-login01.osl.basefarm.net User mickw My pom.xml specifies: distributionManagement repository urlscpexe://sch-login01.osl.basefarm.net/www/schibstedsok/data/httpd/dev.schibstedsok.no_443/htdocs/maven2/url But when running mvn deploy I get: Uploading: scpexe://sch-login01.osl.basefarm.net/www/schibstedsok/data/httpd/dev.schibstedsok.no_443/htdocs/maven2/schibstedsok/commons-log4j/1.3-SNAPSHOT/commons-log4j-1.3-20060831.163911-1.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Error executing command for transfer Exit code 255 - Permission denied (publickey,password,keyboard-interactive). -- 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] Updated: (CONTINUUM-150) Continuum site needs screenshots
[ http://jira.codehaus.org/browse/CONTINUUM-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-150: --- Fix Version/s: (was: Future) 1.1 Continuum site needs screenshots Key: CONTINUUM-150 URL: http://jira.codehaus.org/browse/CONTINUUM-150 Project: Continuum Issue Type: Improvement Components: Documentation Reporter: Henri Yandell Priority: Minor Fix For: 1.1 The Continuum site needs to show screenshots to better sell Continuum to interested parties. -- 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: (MECLIPSE-291) Upgrade maven-plugin-testing-tools to 1.0-alpha-2-SNAPSHOT to fix tests
Upgrade maven-plugin-testing-tools to 1.0-alpha-2-SNAPSHOT to fix tests --- Key: MECLIPSE-291 URL: http://jira.codehaus.org/browse/MECLIPSE-291 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.3 Environment: Windows XP, Cygwin Reporter: Mark Hobson EclipsePluginTest fails when run in a path with spaces. maven-plugin-testing-tools 1.0-alpha-2-SNAPSHOT should resolve this, and if not, a fix can be added there. -- 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] Closed: (CONTINUUM-1259) Continuum web application is slower than before
[ http://jira.codehaus.org/browse/CONTINUUM-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1259. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-alpha-2 Performance are better in alpha-2 Continuum web application is slower than before --- Key: CONTINUUM-1259 URL: http://jira.codehaus.org/browse/CONTINUUM-1259 Project: Continuum Issue Type: Improvement Affects Versions: 1.1-alpha-1 Environment: Windows XP Reporter: Kristoffer Moum Assignee: Emmanuel Venisse Fix For: 1.1-alpha-2 The Continuum web application is dramatically slower than the released 1.0.3 version. However, I have identified a single process which is really slow, most other actions are a bit slower than 1.0.3. In my case, there is an m2 multi-module project of which contains a total of 34 modules. From the frontpage (i.e. (..)/continuum/groupSummary.action), if I choose my project group from the list of groups, it takes approximately 17 seconds to display the list of modules for that group. This is easy to reproduce as it always takes the same amount of time. For my installation, I haven't modified anything from the standard configuration settings. -- 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] Closed: (CONTINUUM-1212) Improve performance of Project Group Summary page
[ http://jira.codehaus.org/browse/CONTINUUM-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1212. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-alpha-2 Improve performance of Project Group Summary page - Key: CONTINUUM-1212 URL: http://jira.codehaus.org/browse/CONTINUUM-1212 Project: Continuum Issue Type: Improvement Components: Web - UI Environment: processor : 0 model name : AMD Athlon(tm) XP 1800+ cpu MHz : 1538.858 cache size : 256 KB bogomips: 3067.08 Reporter: Stefan Seidel Assignee: Emmanuel Venisse Priority: Minor Fix For: 1.1-alpha-2 The Project Group Summary page for a group with 67 projects takes about 70 seconds to display, this is way too long. Configuring things quickly is also not possible, even the About page takes 6 seconds to load. I don't know if these times are normal with the framework that is used, but I think that is not very user friendly. -- 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] Closed: (CONTINUUM-1224) Ability to set MAVEN_OPTS for Maven2 build definitions
[ http://jira.codehaus.org/browse/CONTINUUM-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1224. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-beta-1 Fixed by CONTINUUM-44 Ability to set MAVEN_OPTS for Maven2 build definitions -- Key: CONTINUUM-1224 URL: http://jira.codehaus.org/browse/CONTINUUM-1224 Project: Continuum Issue Type: Wish Components: Integration - Maven 2 Reporter: Nicholas Daley Assignee: Emmanuel Venisse Priority: Minor Fix For: 1.1-beta-1 It would be useful if build definitions for Maven2 projects had a parameter for setting the MAVEN_OPTS environment variable. The specific case that I'm encountering is one of my build definitions needs to have -Xmx set so that it will have enough memory. The only suggestions I could find online for this was to set MAVEN_OPTS when starting up continuum. I have done this, and it works; but I would prefer it if I could set this on a case by case basis for the build definitions, because only this one build needs the extra heap space. -- 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] Updated: (CONTINUUM-1254) Clarification of Configuring Continuum as a Service in Getting Started Guide
[ http://jira.codehaus.org/browse/CONTINUUM-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1254: Fix Version/s: 1.1 Clarification of Configuring Continuum as a Service in Getting Started Guide -- Key: CONTINUUM-1254 URL: http://jira.codehaus.org/browse/CONTINUUM-1254 Project: Continuum Issue Type: Improvement Components: Documentation Reporter: James Williamson Priority: Minor Fix For: 1.1 I was running the service using the Local System account Log On credentials. I changed the Log On credentials to specify my NT Login and password and now it works fine. Looking back at the Continuum Getting Started Guide, it explicitly states: By default, the service logs on as the Local System account. Be sure to change this to an account where you want the service to start upon login. However, I had supposed this meant change it if you want the service to run in some location other than your local machine. In fact, I discovered that you will need to change it if you want your service to work correctly. This document could be improved by stating: Be sure to change this to an account where you want the service to start upon login. If you are hosting the service on your local machine you still need to specify your login credentials in order for your service to function properly. -- 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] Updated: (CONTINUUM-1320) DefaultBuildController.makeAndStoreBuildResult cannot save build result due to maximum size of COMMAND_LINE
[ http://jira.codehaus.org/browse/CONTINUUM-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1320: Fix Version/s: 1.1-beta-2 DefaultBuildController.makeAndStoreBuildResult cannot save build result due to maximum size of COMMAND_LINE --- Key: CONTINUUM-1320 URL: http://jira.codehaus.org/browse/CONTINUUM-1320 Project: Continuum Issue Type: Bug Affects Versions: 1.1-alpha-2 Environment: Continuum with Perforce SCM Reporter: Matthias Wurm Fix For: 1.1-beta-2 Since the maven perforce scm provider creates temporary client specs with a long name (see below), the checkout command gets quite long, too, and hence cannot be save in the COMMAND_LINE column due to the maximum size of 256. Here is the stack trace: 2007-06-19 13:06:40,122 [Thread-6] ERROR TaskQueueExecutor:build-project - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDOFatalUserException: Attempt to store value p4 -d /home/continuum/local/continuum-1.1-alpha-2/apps/continuum/webapp/WEB-INF/working-directory/1 -p perforce.mycompany.com:1666 -cperforce-host.mycompany.com-MavenSCM-\home\continuum\local\continuum-1.1-alpha-2\apps\continuum\webapp\WEB-INF\working-directory\1 sync in column COMMAND_LINE that has maximum length of 256. Please correct your data! 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: javax.jdo.JDOFatalUserException: Attempt to store value p4 -d /home/continuum/local/continuum-1.1-alpha-2/apps/continuum/webapp/WEB-INF/working-directory/1 -p perforce.mycompany.com:1666 -cperforce-host.mycompany.com-MavenSCM-\home\continuum\local\continuum-1.1-alpha-2\apps\continuum\webapp\WEB-INF\working-directory\1 sync in column COMMAND_LINE that has maximum length of 256. Please correct your data! at org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping.java:214) at org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.java:203) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(ParameterSetter.java:122) at org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.java:2757) at org.apache.maven.continuum.model.scm.ScmResult.jdoProvideField(ScmResult.java) at org.apache.maven.continuum.model.scm.ScmResult.jdoProvideFields(ScmResult.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) at org.jpox.store.StoreManager.insert(StoreManager.java:920) at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198) at org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1243) at org.jpox.store.mapping.PersistenceCapableMapping.setObject(PersistenceCapableMapping.java:450) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeObjectField(ParameterSetter.java:144) at org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2771) at org.apache.maven.continuum.model.project.BuildResult.jdoProvideField(BuildResult.java) at org.apache.maven.continuum.model.project.BuildResult.jdoProvideFields(BuildResult.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) at org.jpox.store.StoreManager.insert(StoreManager.java:920) at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198) at
[jira] Updated: (CONTINUUM-1301) JDO delete failure
[ http://jira.codehaus.org/browse/CONTINUUM-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1301: Fix Version/s: 1.1-beta-2 JDO delete failure -- Key: CONTINUUM-1301 URL: http://jira.codehaus.org/browse/CONTINUUM-1301 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.1-alpha-2 Environment: Linux x64, java5 Reporter: Tim Pizey Fix For: 1.1-beta-2 Attempting to delete a project that has been deleted from CVS: javax.jdo.JDOUserException: One or more instances could not be deleted NestedThrowables: javax.jdo.JDOUserException: One or more instances could not be deleted NestedThrowables: javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM PROJECTDEPENDENCY WHERE PROJECTDEPENDENCY_ID=? NestedThrowables: SQL Exception: DELETE on table 'PROJECTDEPENDENCY' caused a violation of foreign key constraint 'PROJECT_FK2' for key (20189). The statement has been rolled back. javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM PROJECTDEPENDENCY WHERE PROJECTDEPENDENCY_ID=? NestedThrowables: SQL Exception: DELETE on table 'PROJECTDEPENDENCY' caused a violation of foreign key constraint 'BUILDRESULT_H5_FK2' for key (20190). The statement has been rolled back. -- 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] Updated: (CONTINUUM-1322) Attempt to store value with more than 256 chars
[ http://jira.codehaus.org/browse/CONTINUUM-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1322: Fix Version/s: 1.1-beta-2 Attempt to store value with more than 256 chars --- Key: CONTINUUM-1322 URL: http://jira.codehaus.org/browse/CONTINUUM-1322 Project: Continuum Issue Type: Bug Affects Versions: 1.1-beta-1 Reporter: Pavel Halas Fix For: 1.1-beta-2 Using latest snapshot (continuum-20070621.01.war) I get this exception causing the project build not processed at all -- red X on the project page, no build statistics to be found. 690292 [Thread-2] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDOFatalUserException: Attempt to store value /soseco/dev/tahoe/applications/rcp/rcpmanager/src/main/java/biz/wss/rcp/rcpmanager/core/bundle/ManagerPartDelegateConfig.java (from /soseco/dev/tahoe/applications/rcp/rcpmanager/src/main/java/biz/wss/rcp/rcpmanager/parts/ManagerPartDelegateConfig.java:12912) in column NAME that has maximum length of 256. Please correct your data! 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: javax.jdo.JDOFatalUserException: Attempt to store value /soseco/dev/tahoe/applications/rcp/rcpmanager/src/main/java/biz/wss/rcp/rcpmanager/core/bundle/ManagerPartDelegateConfig.java (from /soseco/dev/tahoe/applications/rcp/rcpmanager/src/main/java/biz/wss/rcp/rcpmanager/parts/ManagerPartDelegateConfig.java:12912) in column NAME that has maximum length of 256. Please correct your data! at org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping.java:214) at org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.java:203) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(ParameterSetter.java:122) at org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.java:2757) at org.apache.maven.continuum.model.scm.ChangeFile.jdoProvideField(ChangeFile.java) at org.apache.maven.continuum.model.scm.ChangeFile.jdoProvideFields(ChangeFile.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) at org.jpox.store.StoreManager.insert(StoreManager.java:920) at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198) at org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1243) at org.jpox.store.rdbms.scostore.FKListStore.validateElementForWriting(FKListStore.java:1231) at org.jpox.store.rdbms.scostore.FKListStore.internalAdd(FKListStore.java:772) at org.jpox.store.rdbms.scostore.AbstractListStore.addAll(AbstractListStore.java:386) at org.jpox.store.mapping.CollectionMapping.postInsert(CollectionMapping.java:209) at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:464) at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) at org.jpox.store.StoreManager.insert(StoreManager.java:920) at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198) at org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1243) at org.jpox.store.rdbms.scostore.FKListStore.validateElementForWriting(FKListStore.java:1231) at org.jpox.store.rdbms.scostore.FKListStore.internalAdd(FKListStore.java:772) at org.jpox.store.rdbms.scostore.AbstractListStore.addAll(AbstractListStore.java:386) at
[jira] Updated: (CONTINUUM-1306) templated roles are not added automatically if missing after upgrade
[ http://jira.codehaus.org/browse/CONTINUUM-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1306: Fix Version/s: 1.1-beta-2 templated roles are not added automatically if missing after upgrade Key: CONTINUUM-1306 URL: http://jira.codehaus.org/browse/CONTINUUM-1306 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.1-alpha-2 Reporter: Brett Porter Priority: Critical Fix For: 1.1-beta-2 Fails at the last hurdle deleting a project group on an instance that had been upgraded from an old version: org.apache.maven.continuum.ContinuumException: error removing tempalted role for project Maven at org.apache.maven.continuum.core.action.RemoveAssignableRolesAction.execute(RemoveAssignableRolesAction.java:78) at org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinuum.java:2432) at org.apache.maven.continuum.DefaultContinuum.removeProjectGroup(DefaultContinuum.java:261) at org.apache.maven.continuum.web.action.ProjectGroupAction.remove(ProjectGroupAction.java:184) I suspect this is an indication of a bigger problem that the missing templated roles are not added automatically if they are missing. -- 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] Updated: (CONTINUUM-1308) error moving projects to a new group
[ http://jira.codehaus.org/browse/CONTINUUM-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1308: Fix Version/s: 1.1-beta-2 error moving projects to a new group Key: CONTINUUM-1308 URL: http://jira.codehaus.org/browse/CONTINUUM-1308 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.1-alpha-2 Reporter: Brett Porter Fix For: 1.1-beta-2 javax.jdo.JDODetachedFieldAccessException: You have just attempted to access field projects yet this field was not detached when you detached the object. Either dont access this field, or detach the field when detaching the object. at org.apache.maven.continuum.model.project.ProjectGroup.jdoGetprojects(ProjectGroup.java) at org.apache.maven.continuum.model.project.ProjectGroup.getProjects(ProjectGroup.java:237) at org.apache.maven.continuum.model.project.ProjectGroup.createProjectAssociation(ProjectGroup.java:141) at org.apache.maven.continuum.model.project.Project.setProjectGroup(Project.java:818) at org.apache.maven.continuum.web.action.ProjectGroupAction.save(ProjectGroupAction.java:316) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:364) at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:216) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept(ForceContinuumConfigurationInterceptor.java:73) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:103) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:178) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:58) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.webwork.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:171)
[jira] Updated: (CONTINUUM-1304) cannot un-set deployment repository directory in configuration page
[ http://jira.codehaus.org/browse/CONTINUUM-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1304: Fix Version/s: 1.1-beta-2 cannot un-set deployment repository directory in configuration page --- Key: CONTINUUM-1304 URL: http://jira.codehaus.org/browse/CONTINUUM-1304 Project: Continuum Issue Type: Bug Affects Versions: 1.1-alpha-2 Reporter: Brett Porter Fix For: 1.1-beta-2 once it's set, unsetting it clears it on the next page, but it returns as it is not persisted to the database -- 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
