[jira] Updated: (CONTINUUM-872) Project Build Definition Errors
[ http://jira.codehaus.org/browse/CONTINUUM-872?page=all ] Henry S. Isidro updated CONTINUUM-872: -- Attachment: CONTINUUM-872-continuum-webapp.patch File Attached: CONTINUUM-872-continuum-webapp.patch This fixes the problems. > Project Build Definition Errors > --- > > Key: CONTINUUM-872 > URL: http://jira.codehaus.org/browse/CONTINUUM-872 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > Assigned To: Henry S. Isidro > Fix For: 1.1 > > Attachments: CONTINUUM-872-continuum-webapp.patch > > > There are a number of problems with trying to Edit or Add Build Definitions > for a project: > 1) If you create a new schedule and the project uses the DEFAULT_SCHEDULE, > the wrong schedule is selected by default when you edit the current build > definition. In my project, even though it should use DEFAULT_SCHEDULE, the > new schedule called EVERY_MINUTE is selected by default in the pull down menu. > 2) When I try to submit changes to the Build Definition such as the goal from > "clean install" to "clean install site-deploy" and select DEFAULT_SCHEDULE, I > get the following error: > 2006-09-13 20:28:22,437 [btpool0-0] INFO Interceptor:exceptionLogging - > Error ocurred during execution > org.apache.maven.continuum.ContinuumException: failed update, build > definition didn't exist in project group > at > org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumAction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction.java:179) > at > org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectAction.execute(UpdateBuildDefinitionFromProjectAction.java:45) > at > org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinuum.java:2269) > at > org.apache.maven.continuum.DefaultContinuum.updateBuildDefinitionForProject(DefaultContinuum.java:1390) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject_aroundBody148(AcegiContinuum.java:507) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum$AjcClosure149.run(AcegiContinuum.java:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0cproceed(SecurityAspect.aj:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect$1.proceedWithObject(SecurityAspect.aj:59) > at > org.acegisecurity.intercept.method.aspectj.AspectJSecurityInterceptor.invoke(AspectJSecurityInterceptor.java:67) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0c(SecurityAspect.aj:62) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject(AcegiContinuum.java:1) > at > org.apache.maven.continuum.web.action.BuildDefinitionAction.saveToProject(BuildDefinitionAction.java:139) > 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 > 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(DefaultA
[jira] Created: (CONTINUUM-903) In groupSummary, put build status icons on the same line
In groupSummary, put build status icons on the same line Key: CONTINUUM-903 URL: http://jira.codehaus.org/browse/CONTINUUM-903 Project: Continuum Issue Type: Improvement Reporter: Marvin King -- 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-902) 'Manage' tabs is wrong in projectGroupBuildDefinition
'Manage' tabs is wrong in projectGroupBuildDefinition - Key: CONTINUUM-902 URL: http://jira.codehaus.org/browse/CONTINUUM-902 Project: Continuum Issue Type: Bug Reporter: Marvin King -- 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-901) Add a link in projectView to projectGroupSummary
Add a link in projectView to projectGroupSummary Key: CONTINUUM-901 URL: http://jira.codehaus.org/browse/CONTINUUM-901 Project: Continuum Issue Type: Improvement Reporter: Marvin King -- 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-900) Replace Build/Remove links by buttons in projectGroupSummary
Replace Build/Remove links by buttons in projectGroupSummary Key: CONTINUUM-900 URL: http://jira.codehaus.org/browse/CONTINUUM-900 Project: Continuum Issue Type: Improvement Reporter: Marvin King -- 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-899) Add build icon in projectGroupBuildDefinition
Add build icon in projectGroupBuildDefinition - Key: CONTINUUM-899 URL: http://jira.codehaus.org/browse/CONTINUUM-899 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Marvin King -- 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-898) Replace links by icons in projectGroupBuildDefinition
Replace links by icons in projectGroupBuildDefinition - Key: CONTINUUM-898 URL: http://jira.codehaus.org/browse/CONTINUUM-898 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Marvin King -- 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-888) Merge all fixes done in acegi branch with trunk without the acegi security features
[ http://jira.codehaus.org/browse/CONTINUUM-888?page=all ] Brett Porter reopened CONTINUUM-888: Assignee: Carlos Sanchez actually, Carlos has said that there are some of these so they need to be merged back. > Merge all fixes done in acegi branch with trunk without the acegi security > features > --- > > Key: CONTINUUM-888 > URL: http://jira.codehaus.org/browse/CONTINUUM-888 > Project: Continuum > Issue Type: Bug >Reporter: Marvin King > Assigned To: Carlos Sanchez > -- 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-897) Remove ':' before 'OR' in add maven* screens
Remove ':' before 'OR' in add maven* screens Key: CONTINUUM-897 URL: http://jira.codehaus.org/browse/CONTINUUM-897 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Marvin King -- 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-896) Add something in project groups page when continuum is empty
Add something in project groups page when continuum is empty - Key: CONTINUUM-896 URL: http://jira.codehaus.org/browse/CONTINUUM-896 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Marvin King -- 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-894) Users must have a default group
Users must have a default group --- Key: CONTINUUM-894 URL: http://jira.codehaus.org/browse/CONTINUUM-894 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Marvin King - admin for the user that initialize continuum - guest for others -- 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-895) Add a delete confirmation screen for user
Add a delete confirmation screen for user - Key: CONTINUUM-895 URL: http://jira.codehaus.org/browse/CONTINUUM-895 Project: Continuum Issue Type: New Feature Components: Web interface Reporter: Marvin King -- 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-893) Add a delete confirmation screen for user group
Add a delete confirmation screen for user group --- Key: CONTINUUM-893 URL: http://jira.codehaus.org/browse/CONTINUUM-893 Project: Continuum Issue Type: New Feature Components: Web interface Reporter: Marvin King -- 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-892) Add a description on all fields
Add a description on all fields --- Key: CONTINUUM-892 URL: http://jira.codehaus.org/browse/CONTINUUM-892 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Marvin King -- 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-891) Remove empty links on all table headers because they generate a 404
Remove empty links on all table headers because they generate a 404 --- Key: CONTINUUM-891 URL: http://jira.codehaus.org/browse/CONTINUUM-891 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Marvin King -- 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-890) passwords fields in user edition screen aren't html password fields
passwords fields in user edition screen aren't html password fields --- Key: CONTINUUM-890 URL: http://jira.codehaus.org/browse/CONTINUUM-890 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Marvin King -- 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-888) Merge all fixes done in acegi branch with trunk without the acegi security features
[ http://jira.codehaus.org/browse/CONTINUUM-888?page=all ] Marvin King closed CONTINUUM-888. - Resolution: Won't Fix > Merge all fixes done in acegi branch with trunk without the acegi security > features > --- > > Key: CONTINUUM-888 > URL: http://jira.codehaus.org/browse/CONTINUUM-888 > Project: Continuum > Issue Type: Bug >Reporter: Marvin King > -- 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-889) passwords fields in configuration screen aren't html password fields
passwords fields in configuration screen aren't html password fields Key: CONTINUUM-889 URL: http://jira.codehaus.org/browse/CONTINUUM-889 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Marvin King -- 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-888) Merge all fixes done in acegi branch with trunk without the acegi security features
Merge all fixes done in acegi branch with trunk without the acegi security features --- Key: CONTINUUM-888 URL: http://jira.codehaus.org/browse/CONTINUUM-888 Project: Continuum Issue Type: Bug Reporter: Marvin King -- 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: (MNG-2562) expose current time as a property for POM interpolation
expose current time as a property for POM interpolation --- Key: MNG-2562 URL: http://jira.codehaus.org/browse/MNG-2562 Project: Maven 2 Issue Type: New Feature Components: Inheritence and Interpolation Reporter: Brett Porter it is useful to have the current time, for example to write out a manifest entry for the build time or to filter into another file. I'm not sure of the best way to make the format of the time configurable - perhaps another POM element/property. See the related issue for a current example of how this can be done, but it would be nice to have a built-in. -- 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: (MNG-2561) cookbook example: adding build time to a manifest
cookbook example: adding build time to a manifest - Key: MNG-2561 URL: http://jira.codehaus.org/browse/MNG-2561 Project: Maven 2 Issue Type: Task Components: Documentation: Guides Reporter: Brett Porter Attachments: cookbook-generate-build-time.zip -- 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-887) After saving project details the top tab doesn't work, missing projectId parameter
[ http://jira.codehaus.org/browse/CONTINUUM-887?page=comments#action_74819 ] Carlos Sanchez commented on CONTINUUM-887: -- We have to do redirect after save instead of forward, that may solve the problem > After saving project details the top tab doesn't work, missing projectId > parameter > -- > > Key: CONTINUUM-887 > URL: http://jira.codehaus.org/browse/CONTINUUM-887 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Fix For: 1.1 > > -- 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-887) After saving project details the top tab doesn't work, missing projectId parameter
After saving project details the top tab doesn't work, missing projectId parameter -- Key: CONTINUUM-887 URL: http://jira.codehaus.org/browse/CONTINUUM-887 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez Fix For: 1.1 -- 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-887) After saving project details the top tab doesn't work, missing projectId parameter
[ http://jira.codehaus.org/browse/CONTINUUM-887?page=all ] Carlos Sanchez updated CONTINUUM-887: - Fix Version/s: 1.1 > After saving project details the top tab doesn't work, missing projectId > parameter > -- > > Key: CONTINUUM-887 > URL: http://jira.codehaus.org/browse/CONTINUUM-887 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Fix For: 1.1 > > -- 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-369) Stop button to cancel the "in progress" of a project.
[ http://jira.codehaus.org/browse/CONTINUUM-369?page=all ] Carlos Sanchez updated CONTINUUM-369: - Comment: was deleted > Stop button to cancel the "in progress" of a project. > - > > Key: CONTINUUM-369 > URL: http://jira.codehaus.org/browse/CONTINUUM-369 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Affects Versions: 1.0-beta-1 > Environment: Linux and Windows >Reporter: Fritz Oconer > Assigned To: Kenney Westerhof > Fix For: 1.1 > > > Request feature that will enable a user to cancel the "build" of a particular > project. Kinda like hitting "ctrl c" when maven is executed. There are times > when a project is "stuck indefinitely" in "in progress" state (e.g. when > running a broken testcase that executes "indefinitely"). This affects other > projects because it has to wait for the previous one to finish. Restarting > continuum is not much help because it just goes back to the original state or > you cannot delete the project itself because "delete" link is disable. The > only solution now is to redeploy continuum. Now, having a cancel button would > definitely help. -- 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-369) Stop button to cancel the "in progress" of a project.
[ http://jira.codehaus.org/browse/CONTINUUM-369?page=all ] Carlos Sanchez reopened CONTINUUM-369: -- Assignee: Kenney Westerhof (was: Carlos Sanchez) > Stop button to cancel the "in progress" of a project. > - > > Key: CONTINUUM-369 > URL: http://jira.codehaus.org/browse/CONTINUUM-369 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Affects Versions: 1.0-beta-1 > Environment: Linux and Windows >Reporter: Fritz Oconer > Assigned To: Kenney Westerhof > Fix For: 1.1 > > > Request feature that will enable a user to cancel the "build" of a particular > project. Kinda like hitting "ctrl c" when maven is executed. There are times > when a project is "stuck indefinitely" in "in progress" state (e.g. when > running a broken testcase that executes "indefinitely"). This affects other > projects because it has to wait for the previous one to finish. Restarting > continuum is not much help because it just goes back to the original state or > you cannot delete the project itself because "delete" link is disable. The > only solution now is to redeploy continuum. Now, having a cancel button would > definitely help. -- 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-369) Stop button to cancel the "in progress" of a project.
[ http://jira.codehaus.org/browse/CONTINUUM-369?page=all ] Carlos Sanchez closed CONTINUUM-369. Assignee: Carlos Sanchez (was: Kenney Westerhof) Resolution: Fixed Merged continuum-release into trunk > Stop button to cancel the "in progress" of a project. > - > > Key: CONTINUUM-369 > URL: http://jira.codehaus.org/browse/CONTINUUM-369 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Affects Versions: 1.0-beta-1 > Environment: Linux and Windows >Reporter: Fritz Oconer > Assigned To: Carlos Sanchez > Fix For: 1.1 > > > Request feature that will enable a user to cancel the "build" of a particular > project. Kinda like hitting "ctrl c" when maven is executed. There are times > when a project is "stuck indefinitely" in "in progress" state (e.g. when > running a broken testcase that executes "indefinitely"). This affects other > projects because it has to wait for the previous one to finish. Restarting > continuum is not much help because it just goes back to the original state or > you cannot delete the project itself because "delete" link is disable. The > only solution now is to redeploy continuum. Now, having a cancel button would > definitely help. -- 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-872) Project Build Definition Errors
[ http://jira.codehaus.org/browse/CONTINUUM-872?page=comments#action_74816 ] Carlos Sanchez commented on CONTINUUM-872: -- I think ww:set or c:set instead of ww:url will solve the problem > Project Build Definition Errors > --- > > Key: CONTINUUM-872 > URL: http://jira.codehaus.org/browse/CONTINUUM-872 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > Assigned To: Henry S. Isidro > Fix For: 1.1 > > > There are a number of problems with trying to Edit or Add Build Definitions > for a project: > 1) If you create a new schedule and the project uses the DEFAULT_SCHEDULE, > the wrong schedule is selected by default when you edit the current build > definition. In my project, even though it should use DEFAULT_SCHEDULE, the > new schedule called EVERY_MINUTE is selected by default in the pull down menu. > 2) When I try to submit changes to the Build Definition such as the goal from > "clean install" to "clean install site-deploy" and select DEFAULT_SCHEDULE, I > get the following error: > 2006-09-13 20:28:22,437 [btpool0-0] INFO Interceptor:exceptionLogging - > Error ocurred during execution > org.apache.maven.continuum.ContinuumException: failed update, build > definition didn't exist in project group > at > org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumAction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction.java:179) > at > org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectAction.execute(UpdateBuildDefinitionFromProjectAction.java:45) > at > org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinuum.java:2269) > at > org.apache.maven.continuum.DefaultContinuum.updateBuildDefinitionForProject(DefaultContinuum.java:1390) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject_aroundBody148(AcegiContinuum.java:507) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum$AjcClosure149.run(AcegiContinuum.java:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0cproceed(SecurityAspect.aj:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect$1.proceedWithObject(SecurityAspect.aj:59) > at > org.acegisecurity.intercept.method.aspectj.AspectJSecurityInterceptor.invoke(AspectJSecurityInterceptor.java:67) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0c(SecurityAspect.aj:62) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject(AcegiContinuum.java:1) > at > org.apache.maven.continuum.web.action.BuildDefinitionAction.saveToProject(BuildDefinitionAction.java:139) > 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 > 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.FileUpload
[jira] Commented: (CONTINUUM-872) Project Build Definition Errors
[ http://jira.codehaus.org/browse/CONTINUUM-872?page=comments#action_74815 ] Carlos Sanchez commented on CONTINUUM-872: -- The problem is that ww:url adds the context and ww:form too in buildDefinitionEdit.jsp If you deploy the war in the root context you may not see the issue, but if it's in continuum context you see that ww:url saves /continuum/save... and then ww:form generates /continuum/continuum/save... > Project Build Definition Errors > --- > > Key: CONTINUUM-872 > URL: http://jira.codehaus.org/browse/CONTINUUM-872 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > Assigned To: Henry S. Isidro > Fix For: 1.1 > > > There are a number of problems with trying to Edit or Add Build Definitions > for a project: > 1) If you create a new schedule and the project uses the DEFAULT_SCHEDULE, > the wrong schedule is selected by default when you edit the current build > definition. In my project, even though it should use DEFAULT_SCHEDULE, the > new schedule called EVERY_MINUTE is selected by default in the pull down menu. > 2) When I try to submit changes to the Build Definition such as the goal from > "clean install" to "clean install site-deploy" and select DEFAULT_SCHEDULE, I > get the following error: > 2006-09-13 20:28:22,437 [btpool0-0] INFO Interceptor:exceptionLogging - > Error ocurred during execution > org.apache.maven.continuum.ContinuumException: failed update, build > definition didn't exist in project group > at > org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumAction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction.java:179) > at > org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectAction.execute(UpdateBuildDefinitionFromProjectAction.java:45) > at > org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinuum.java:2269) > at > org.apache.maven.continuum.DefaultContinuum.updateBuildDefinitionForProject(DefaultContinuum.java:1390) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject_aroundBody148(AcegiContinuum.java:507) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum$AjcClosure149.run(AcegiContinuum.java:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0cproceed(SecurityAspect.aj:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect$1.proceedWithObject(SecurityAspect.aj:59) > at > org.acegisecurity.intercept.method.aspectj.AspectJSecurityInterceptor.invoke(AspectJSecurityInterceptor.java:67) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0c(SecurityAspect.aj:62) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject(AcegiContinuum.java:1) > at > org.apache.maven.continuum.web.action.BuildDefinitionAction.saveToProject(BuildDefinitionAction.java:139) > 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 > com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) > at > com.opensymphony.xwork.DefaultActionInvocation.in
[jira] Updated: (CONTINUUM-886) On the Delete user confirmation page there should be a "Cancel" button
[ http://jira.codehaus.org/browse/CONTINUUM-886?page=all ] Maria Odea Ching updated CONTINUUM-886: --- Due Date: 19/Sep/06 Remaining Estimate: 3 hours Original Estimate: 3 hours > On the Delete user confirmation page there should be a "Cancel" button > -- > > Key: CONTINUUM-886 > URL: http://jira.codehaus.org/browse/CONTINUUM-886 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > Assigned To: Maria Odea Ching >Priority: Trivial > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > When the admin attempts to delete a user, they are prompted whether they > really wish to delete the user. On this page there should be a Cancel button. -- 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-885) Can't delete user
[ http://jira.codehaus.org/browse/CONTINUUM-885?page=all ] Maria Odea Ching updated CONTINUUM-885: --- Due Date: 18/Sep/06 Remaining Estimate: 10 hours Original Estimate: 10 hours > Can't delete user > - > > Key: CONTINUUM-885 > URL: http://jira.codehaus.org/browse/CONTINUUM-885 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > Assigned To: Maria Odea Ching > Original Estimate: 10 hours > Remaining Estimate: 10 hours > > When the admin user tries to delete a user, a message pops up that says: > Are you sure you want to delete the user ""? > regardless of the name of the user selected for deletion. When you click > Delete, the following exception is printed to the console: > :WARN: /continuum/user/delete.action > java.lang.RuntimeException: Could not find object. Type > 'org.apache.maven.user.model.User'. Id: '0'. > at > org.apache.maven.user.model.store.impl.DefaultUserStore.getObjectById(DefaultUserStore.java:375) > at > org.apache.maven.user.model.store.impl.DefaultUserStore.getObjectById(DefaultUserStore.java:362) > at > org.apache.maven.user.model.store.impl.DefaultUserStore.getUser(DefaultUserStore.java:83) > at > org.apache.maven.user.model.store.impl.DefaultUserStore.removeUser(DefaultUserStore.java:251) > at > org.apache.maven.user.model.impl.DefaultUserManager.removeUser(DefaultUserManager.java:293) > at > org.apache.maven.user.acegi.AcegiUserManager.removeUser(AcegiUserManager.java:174) > at > org.apache.maven.user.controller.action.DeleteUserAction.execute(DeleteUserAction.java:45) > 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 > 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) > 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.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:147) > 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.I18nInterceptor.intercept(I18nInterceptor.java:151) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) > at > com
[jira] Commented: (CONTINUUM-369) Stop button to cancel the "in progress" of a project.
[ http://jira.codehaus.org/browse/CONTINUUM-369?page=comments#action_74813 ] Brett Porter commented on CONTINUUM-369: is this completed then? > Stop button to cancel the "in progress" of a project. > - > > Key: CONTINUUM-369 > URL: http://jira.codehaus.org/browse/CONTINUUM-369 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Affects Versions: 1.0-beta-1 > Environment: Linux and Windows >Reporter: Fritz Oconer > Assigned To: Kenney Westerhof > Fix For: 1.1 > > > Request feature that will enable a user to cancel the "build" of a particular > project. Kinda like hitting "ctrl c" when maven is executed. There are times > when a project is "stuck indefinitely" in "in progress" state (e.g. when > running a broken testcase that executes "indefinitely"). This affects other > projects because it has to wait for the previous one to finish. Restarting > continuum is not much help because it just goes back to the original state or > you cannot delete the project itself because "delete" link is disable. The > only solution now is to redeploy continuum. Now, having a cancel button would > definitely help. -- 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-667) need a way to limit the mount of time a unit test runs for
[ http://jira.codehaus.org/browse/CONTINUUM-667?page=comments#action_74814 ] Brett Porter commented on CONTINUUM-667: I think this is complete - Kenney, can you confirm? > need a way to limit the mount of time a unit test runs for > -- > > Key: CONTINUUM-667 > URL: http://jira.codehaus.org/browse/CONTINUUM-667 > Project: Continuum > Issue Type: Bug > Components: Core system, Web interface >Affects Versions: 1.0.3 >Reporter: james strachan > Assigned To: Kenney Westerhof >Priority: Blocker > Fix For: 1.1 > > > We get lots of builds hanging in CI due to test cases with timing issues on > different platforms. (You'd be amazed how easy that is to do). We need a way > to put in a maximum amount of time (say 5 minutes) for a single unit test - > or a max time per entire test run (say 1 hour) so that we can be alerted if a > test hangs. > If a test hangs it normally hoses the entire CI server. The worst thing is > this makes the entire CI useless since it does no more builds and we don't > know its failed. > I understand there are complications in killing stuff in Java. (Though > java.lang.Process.destroy() works for most things). One option is to just > have a status XML file we can poll for on a canoncial URL > http;//serverhost/module/status.xml > then we can look to see if any of the builds are blocked and if they are we > can get nagios or something to reboot the box / restart the CI server etc. -- 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-872) Project Build Definition Errors
[ http://jira.codehaus.org/browse/CONTINUUM-872?page=comments#action_74812 ] Henry S. Isidro commented on CONTINUUM-872: --- I can't seem to replicate your problem with issue number 2. I tried doing everything as you described and issues 1 to 3 seem to be fixed. > Project Build Definition Errors > --- > > Key: CONTINUUM-872 > URL: http://jira.codehaus.org/browse/CONTINUUM-872 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > Assigned To: Henry S. Isidro > Fix For: 1.1 > > > There are a number of problems with trying to Edit or Add Build Definitions > for a project: > 1) If you create a new schedule and the project uses the DEFAULT_SCHEDULE, > the wrong schedule is selected by default when you edit the current build > definition. In my project, even though it should use DEFAULT_SCHEDULE, the > new schedule called EVERY_MINUTE is selected by default in the pull down menu. > 2) When I try to submit changes to the Build Definition such as the goal from > "clean install" to "clean install site-deploy" and select DEFAULT_SCHEDULE, I > get the following error: > 2006-09-13 20:28:22,437 [btpool0-0] INFO Interceptor:exceptionLogging - > Error ocurred during execution > org.apache.maven.continuum.ContinuumException: failed update, build > definition didn't exist in project group > at > org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumAction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction.java:179) > at > org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectAction.execute(UpdateBuildDefinitionFromProjectAction.java:45) > at > org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinuum.java:2269) > at > org.apache.maven.continuum.DefaultContinuum.updateBuildDefinitionForProject(DefaultContinuum.java:1390) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject_aroundBody148(AcegiContinuum.java:507) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum$AjcClosure149.run(AcegiContinuum.java:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0cproceed(SecurityAspect.aj:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect$1.proceedWithObject(SecurityAspect.aj:59) > at > org.acegisecurity.intercept.method.aspectj.AspectJSecurityInterceptor.invoke(AspectJSecurityInterceptor.java:67) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0c(SecurityAspect.aj:62) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject(AcegiContinuum.java:1) > at > org.apache.maven.continuum.web.action.BuildDefinitionAction.saveToProject(BuildDefinitionAction.java:139) > 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 > 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(DefaultActionInvocatio
[jira] Closed: (MRM-150) add field validations for forms
[ http://jira.codehaus.org/browse/MRM-150?page=all ] Maria Odea Ching closed MRM-150. Resolution: Fixed > add field validations for forms > --- > > Key: MRM-150 > URL: http://jira.codehaus.org/browse/MRM-150 > Project: Archiva > Issue Type: Task > Components: web application >Reporter: Brett Porter > Assigned To: Maria Odea Ching > Fix For: 1.0-beta-1 > > Original Estimate: 20 hours > Time Spent: 1 day, 4 hours > Remaining Estimate: 0 minutes > > these are documented in the validation files by todos -- 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: (MNG-1678) missing element does not trigger any warning
[ http://jira.codehaus.org/browse/MNG-1678?page=all ] Maria Odea Ching updated MNG-1678: -- Due Date: 19/Sep/06 > missing element does not trigger any warning > > > Key: MNG-1678 > URL: http://jira.codehaus.org/browse/MNG-1678 > Project: Maven 2 > Issue Type: Improvement >Affects Versions: 2.0, 2.0.4 >Reporter: Jorg Heymans > Assigned To: Maria Odea Ching > Fix For: 2.0.5 > > > spot the subtle error in below pom : > > > 4.0.0 > org.my.project > myProject > 0.1 > The Project > jar > > > apache-maven2-snapshot > Apache Maven2 Snapshot Repository > http://cvs.apache.org/maven-snapshot-repository > > > > org.apache.cocoon > cocoon-core > 2.2.0-SNAPSHOT > > > The dependency element is missing inside . Maven did not give > any warning or error though. > Note that in my actual project, the dependency was not needed for compilation -- 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: (MNG-1678) missing element does not trigger any warning
[ http://jira.codehaus.org/browse/MNG-1678?page=all ] Maria Odea Ching updated MNG-1678: -- Due Date: 18/Sep/06 (was: 19/Sep/06) Remaining Estimate: 12 hours (was: 15 hours) Original Estimate: 12 hours (was: 15 hours) > missing element does not trigger any warning > > > Key: MNG-1678 > URL: http://jira.codehaus.org/browse/MNG-1678 > Project: Maven 2 > Issue Type: Improvement >Affects Versions: 2.0, 2.0.4 >Reporter: Jorg Heymans > Assigned To: Maria Odea Ching > Fix For: 2.0.5 > > Original Estimate: 12 hours > Remaining Estimate: 12 hours > > spot the subtle error in below pom : > > > 4.0.0 > org.my.project > myProject > 0.1 > The Project > jar > > > apache-maven2-snapshot > Apache Maven2 Snapshot Repository > http://cvs.apache.org/maven-snapshot-repository > > > > org.apache.cocoon > cocoon-core > 2.2.0-SNAPSHOT > > > The dependency element is missing inside . Maven did not give > any warning or error though. > Note that in my actual project, the dependency was not needed for compilation -- 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: (MNG-1678) missing element does not trigger any warning
[ http://jira.codehaus.org/browse/MNG-1678?page=all ] Maria Odea Ching updated MNG-1678: -- Remaining Estimate: 15 hours Original Estimate: 15 hours > missing element does not trigger any warning > > > Key: MNG-1678 > URL: http://jira.codehaus.org/browse/MNG-1678 > Project: Maven 2 > Issue Type: Improvement >Affects Versions: 2.0, 2.0.4 >Reporter: Jorg Heymans > Assigned To: Maria Odea Ching > Fix For: 2.0.5 > > Original Estimate: 15 hours > Remaining Estimate: 15 hours > > spot the subtle error in below pom : > > > 4.0.0 > org.my.project > myProject > 0.1 > The Project > jar > > > apache-maven2-snapshot > Apache Maven2 Snapshot Repository > http://cvs.apache.org/maven-snapshot-repository > > > > org.apache.cocoon > cocoon-core > 2.2.0-SNAPSHOT > > > The dependency element is missing inside . Maven did not give > any warning or error though. > Note that in my actual project, the dependency was not needed for compilation -- 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-886) On the Delete user confirmation page there should be a "Cancel" button
On the Delete user confirmation page there should be a "Cancel" button -- Key: CONTINUUM-886 URL: http://jira.codehaus.org/browse/CONTINUUM-886 Project: Continuum Issue Type: Bug Affects Versions: 1.1 Environment: Windows Reporter: David Schwartz Priority: Trivial When the admin attempts to delete a user, they are prompted whether they really wish to delete the user. On this page there should be a Cancel button. -- 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: (MRELEASE-130) Create a model for a release
[ http://jira.codehaus.org/browse/MRELEASE-130?page=all ] Brett Porter closed MRELEASE-130. - Resolution: Fixed Fix Version/s: 2.0 ok, this is working now > Create a model for a release > > > Key: MRELEASE-130 > URL: http://jira.codehaus.org/browse/MRELEASE-130 > Project: Maven 2.x Release Plugin > Issue Type: New Feature >Reporter: Jason van Zyl > Assigned To: Jeremy Whitlock > Fix For: 2.0 > > Attachments: MRELEASE-130.refactor.patch > > > Use modello to create a model for a release. Something that could be sent to > a release mechanism for an official release. -- 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-885) Can't delete user
Can't delete user - Key: CONTINUUM-885 URL: http://jira.codehaus.org/browse/CONTINUUM-885 Project: Continuum Issue Type: Bug Affects Versions: 1.1 Environment: Windows Reporter: David Schwartz When the admin user tries to delete a user, a message pops up that says: Are you sure you want to delete the user ""? regardless of the name of the user selected for deletion. When you click Delete, the following exception is printed to the console: :WARN: /continuum/user/delete.action java.lang.RuntimeException: Could not find object. Type 'org.apache.maven.user.model.User'. Id: '0'. at org.apache.maven.user.model.store.impl.DefaultUserStore.getObjectById(DefaultUserStore.java:375) at org.apache.maven.user.model.store.impl.DefaultUserStore.getObjectById(DefaultUserStore.java:362) at org.apache.maven.user.model.store.impl.DefaultUserStore.getUser(DefaultUserStore.java:83) at org.apache.maven.user.model.store.impl.DefaultUserStore.removeUser(DefaultUserStore.java:251) at org.apache.maven.user.model.impl.DefaultUserManager.removeUser(DefaultUserManager.java:293) at org.apache.maven.user.acegi.AcegiUserManager.removeUser(AcegiUserManager.java:174) at org.apache.maven.user.controller.action.DeleteUserAction.execute(DeleteUserAction.java:45) 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 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) 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.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:147) 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.I18nInterceptor.intercept(I18nInterceptor.java:151) 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.xwor
[jira] Created: (CONTINUUM-884) svn metadata not properly shown in Build Result or Email Notification
svn metadata not properly shown in Build Result or Email Notification - Key: CONTINUUM-884 URL: http://jira.codehaus.org/browse/CONTINUUM-884 Project: Continuum Issue Type: Bug Affects Versions: 1.1 Environment: Windows Reporter: David Schwartz When you do a build the webpage and the email that is sent show what files have been changed. The correct file(s) are shown but the following info is missing for each file: author, date, comment, revision Here is an example from an email: Changes: Changed: no author @ no date Comment: no comment Files changed: src\main\java\org\codehaus\mojo\websphere\tasks\utils\ValidationUtils.java ( no revision ) Also, on the webpage for that shows the Build Result there is a table called "Changes" that is missing Author, Date, Comment -- 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: (MNG-2294) If /project/parent/relativePath fails to resolve, no error is reported.
[ http://jira.codehaus.org/browse/MNG-2294?page=all ] Maria Odea Ching updated MNG-2294: -- Due Date: 19/Sep/06 (was: 18/Sep/06) > If /project/parent/relativePath fails to resolve, no error is reported. > --- > > Key: MNG-2294 > URL: http://jira.codehaus.org/browse/MNG-2294 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: David Smiley > Assigned To: Maria Odea Ching > Fix For: 2.0.5 > > Original Estimate: 15 hours > Remaining Estimate: 15 hours > > If I have a bad /project/parent/relativePath specified, maven does not tell > me. Instead the build proceeds as if there is no parent. The build should > fail if the parent can't be resolved. -- 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-727) Allow Continuum to work with the release plugin to perform the official release
[ http://jira.codehaus.org/browse/CONTINUUM-727?page=all ] Carlos Sanchez closed CONTINUUM-727. Assignee: Carlos Sanchez (was: Jeremy Whitlock) Resolution: Fixed Merged continuum release branch into trunk > Allow Continuum to work with the release plugin to perform the official > release > --- > > Key: CONTINUUM-727 > URL: http://jira.codehaus.org/browse/CONTINUUM-727 > Project: Continuum > Issue Type: New Feature > Components: Core system >Reporter: Jason van Zyl > Assigned To: Carlos Sanchez > Fix For: 1.1 > > > This might eventually be a little tool for release management but it could > start in Continuum. So the release plugin would do a release:prepare and > store the information in a descriptor (maybe use modello to describe the > release) and the descriptor could be sent to Continuum via a Web Service and > Continuum could do the official release. -- 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-831) Continuum Release white site pages
[ http://jira.codehaus.org/browse/CONTINUUM-831?page=all ] Carlos Sanchez closed CONTINUUM-831. Assignee: Carlos Sanchez (was: Edwin Punzalan) Resolution: Fixed > Continuum Release white site pages > -- > > Key: CONTINUUM-831 > URL: http://jira.codehaus.org/browse/CONTINUUM-831 > Project: Continuum > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.1 >Reporter: Edwin Punzalan > Assigned To: Carlos Sanchez > Fix For: 1.1 > > Attachments: CONTINUUM-831-continuum-uml.patch > > -- 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: (MNG-2294) If /project/parent/relativePath fails to resolve, no error is reported.
[ http://jira.codehaus.org/browse/MNG-2294?page=all ] Maria Odea Ching updated MNG-2294: -- Due Date: 18/Sep/06 (was: 13/Sep/06) > If /project/parent/relativePath fails to resolve, no error is reported. > --- > > Key: MNG-2294 > URL: http://jira.codehaus.org/browse/MNG-2294 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: David Smiley > Assigned To: Maria Odea Ching > Fix For: 2.0.5 > > Original Estimate: 15 hours > Remaining Estimate: 15 hours > > If I have a bad /project/parent/relativePath specified, maven does not tell > me. Instead the build proceeds as if there is no parent. The build should > fail if the parent can't be resolved. -- 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-878) Changing password that's invalid will result to a blank page.
[ http://jira.codehaus.org/browse/CONTINUUM-878?page=all ]
Carlos Sanchez closed CONTINUUM-878.
Assignee: Carlos Sanchez (was: Lester Ecarma)
Resolution: Fixed
Fix Version/s: 1.1
> Changing password that's invalid will result to a blank page.
> -
>
> Key: CONTINUUM-878
> URL: http://jira.codehaus.org/browse/CONTINUUM-878
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
>Reporter: Teodoro Cue Jr.
> Assigned To: Carlos Sanchez
> Fix For: 1.1
>
>
> After changing to an invalid password, a blank page is loaded. An exception
> occured and below is the stacktrace.
> 2006-09-14 20:49:12,515 [btpool0-2] ERROR Component -
> tag 'select', field 'list', name 'groups': The requested list key 'allGroups'
> could not be resolved as a collection/array/map/enumeration/iterator type.
> Example: people or people.{name}
> 2006-09-14 20:49:12.515::WARN: EXCEPTION
> org.apache.jasper.JasperException: tag 'select', field 'list', name 'groups':
> The requested list key 'allGroups' could not be resolved as a
> collection/array/map/enumeration/iterator type. Example: people or
> people.{name}
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:440)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:335)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:442)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:615)
> at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:189)
> at
> com.opensymphony.webwork.components.Include.include(Include.java:227)
> at com.opensymphony.webwork.components.Include.end(Include.java:136)
> at
> com.opensymphony.webwork.views.jsp.ComponentTagSupport.doEndTag(ComponentTagSupport.java:21)
> at
> org.apache.jsp.user.edit_jsp._jspx_meth_ww_include_0(org.apache.jsp.user.edit_jsp:438)
> at
> org.apache.jsp.user.edit_jsp._jspx_meth_ww_i18n_0(org.apache.jsp.user.edit_jsp:164)
> at
> org.apache.jsp.user.edit_jsp._jspService(org.apache.jsp.user.edit_jsp:108)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:358)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:440)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:335)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:442)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:615)
> at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:262)
> at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:124)
> at
> com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:114)
> at
> com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkResultSupport.java:143)
> at
> com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:311)
> at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:206)
> 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.i
[jira] Commented: (CONTINUUM-883) Ordinary user can't change their password
[ http://jira.codehaus.org/browse/CONTINUUM-883?page=comments#action_74807 ] Carlos Sanchez commented on CONTINUUM-883: -- I think this was fixed in the last revisions > Ordinary user can't change their password > - > > Key: CONTINUUM-883 > URL: http://jira.codehaus.org/browse/CONTINUUM-883 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > > I have tested the admin changing a password and it seems to work fine but if > I'm in the "users" group and try to change my password as an ordinary user I > get the following exception: > :WARN: /continuum/user/saveAccount.action > java.lang.RuntimeException: Could not find object. Type > 'org.apache.maven.user.model.User'. Id: '0'. > at > org.apache.maven.user.model.store.impl.DefaultUserStore.getObjectById(DefaultUserStore.java:375) > at > org.apache.maven.user.model.store.impl.DefaultUserStore.getObjectById(DefaultUserStore.java:362) > at > org.apache.maven.user.model.store.impl.DefaultUserStore.getUser(DefaultUserStore.java:83) > at > org.apache.maven.user.model.impl.DefaultUserManager.getUser(DefaultUserManager.java:246) > at > org.apache.maven.user.acegi.AcegiUserManager.getUser(AcegiUserManager.java:124) > at > org.apache.maven.user.controller.action.EditUserAction.execute(EditUserAction.java:124) > 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 > 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) > 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.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:147) > 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.I18nInterceptor.intercept(I18nInterceptor.java:151) > 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
[jira] Created: (CONTINUUM-883) Ordinary user can't change their password
Ordinary user can't change their password - Key: CONTINUUM-883 URL: http://jira.codehaus.org/browse/CONTINUUM-883 Project: Continuum Issue Type: Bug Affects Versions: 1.1 Environment: Windows Reporter: David Schwartz I have tested the admin changing a password and it seems to work fine but if I'm in the "users" group and try to change my password as an ordinary user I get the following exception: :WARN: /continuum/user/saveAccount.action java.lang.RuntimeException: Could not find object. Type 'org.apache.maven.user.model.User'. Id: '0'. at org.apache.maven.user.model.store.impl.DefaultUserStore.getObjectById(DefaultUserStore.java:375) at org.apache.maven.user.model.store.impl.DefaultUserStore.getObjectById(DefaultUserStore.java:362) at org.apache.maven.user.model.store.impl.DefaultUserStore.getUser(DefaultUserStore.java:83) at org.apache.maven.user.model.impl.DefaultUserManager.getUser(DefaultUserManager.java:246) at org.apache.maven.user.acegi.AcegiUserManager.getUser(AcegiUserManager.java:124) at org.apache.maven.user.controller.action.EditUserAction.execute(EditUserAction.java:124) 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 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) 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.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:147) 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.I18nInterceptor.intercept(I18nInterceptor.java:151) 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.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:186) at com.opensymphony.xwork.DefaultA
[jira] Closed: (MRM-171) Make the registerUser and registerAdminUser pages share the same form
[ http://jira.codehaus.org/browse/MRM-171?page=all ] Maria Odea Ching closed MRM-171. Resolution: Fixed > Make the registerUser and registerAdminUser pages share the same form > - > > Key: MRM-171 > URL: http://jira.codehaus.org/browse/MRM-171 > Project: Archiva > Issue Type: Improvement > Components: web application >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > Original Estimate: 3 hours > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > The pages look different, but have the same elements. Use <[EMAIL PROTECTED] > %> for the form elements. -- 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: (MJAVADOC-91) Update Javadoc Plugin Documentation (more examples for manifest customization)
Update Javadoc Plugin Documentation (more examples for manifest customization) -- Key: MJAVADOC-91 URL: http://jira.codehaus.org/browse/MJAVADOC-91 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Reporter: Franz Allan Valencia See Priority: Minor The current javadoc plugin documentations has an example on how to customize the manifest to be generated. Furthermore, it provides a link to the javadoc of MavenArchiveConfiguration, which implies under configurations aside from the one shown there (manifest entries). IMHO, we can remove the link to the javadoc and replace that with actual examples of those configurations. -- 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-872) Project Build Definition Errors
[ http://jira.codehaus.org/browse/CONTINUUM-872?page=comments#action_74805 ] David Schwartz commented on CONTINUUM-872: -- This URL is the one that shows HTTP ERROR: 404 http://localhost:9090/continuum/continuum/saveGroupBuildDefinition.action?projectId=0&buildDefinitionId=1&projectGroupId=2 > Project Build Definition Errors > --- > > Key: CONTINUUM-872 > URL: http://jira.codehaus.org/browse/CONTINUUM-872 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > Assigned To: Henry S. Isidro > Fix For: 1.1 > > > There are a number of problems with trying to Edit or Add Build Definitions > for a project: > 1) If you create a new schedule and the project uses the DEFAULT_SCHEDULE, > the wrong schedule is selected by default when you edit the current build > definition. In my project, even though it should use DEFAULT_SCHEDULE, the > new schedule called EVERY_MINUTE is selected by default in the pull down menu. > 2) When I try to submit changes to the Build Definition such as the goal from > "clean install" to "clean install site-deploy" and select DEFAULT_SCHEDULE, I > get the following error: > 2006-09-13 20:28:22,437 [btpool0-0] INFO Interceptor:exceptionLogging - > Error ocurred during execution > org.apache.maven.continuum.ContinuumException: failed update, build > definition didn't exist in project group > at > org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumAction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction.java:179) > at > org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectAction.execute(UpdateBuildDefinitionFromProjectAction.java:45) > at > org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinuum.java:2269) > at > org.apache.maven.continuum.DefaultContinuum.updateBuildDefinitionForProject(DefaultContinuum.java:1390) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject_aroundBody148(AcegiContinuum.java:507) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum$AjcClosure149.run(AcegiContinuum.java:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0cproceed(SecurityAspect.aj:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect$1.proceedWithObject(SecurityAspect.aj:59) > at > org.acegisecurity.intercept.method.aspectj.AspectJSecurityInterceptor.invoke(AspectJSecurityInterceptor.java:67) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0c(SecurityAspect.aj:62) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject(AcegiContinuum.java:1) > at > org.apache.maven.continuum.web.action.BuildDefinitionAction.saveToProject(BuildDefinitionAction.java:139) > 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 > 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
[jira] Commented: (CONTINUUM-872) Project Build Definition Errors
[ http://jira.codehaus.org/browse/CONTINUUM-872?page=comments#action_74804 ] David Schwartz commented on CONTINUUM-872: -- Issue number 1) seems to be resolved. It now selects the correct schedule for the current project I get a different error for issue number 2). Now when I click submit I get the following error: :WARN: PWC6117: File "C:\usr\local\jetty\jetty-6.0.0rc1\webapps\continuum\continuum\projectGroupBuildDefinition.jsp" not found > Project Build Definition Errors > --- > > Key: CONTINUUM-872 > URL: http://jira.codehaus.org/browse/CONTINUUM-872 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > Assigned To: Henry S. Isidro > Fix For: 1.1 > > > There are a number of problems with trying to Edit or Add Build Definitions > for a project: > 1) If you create a new schedule and the project uses the DEFAULT_SCHEDULE, > the wrong schedule is selected by default when you edit the current build > definition. In my project, even though it should use DEFAULT_SCHEDULE, the > new schedule called EVERY_MINUTE is selected by default in the pull down menu. > 2) When I try to submit changes to the Build Definition such as the goal from > "clean install" to "clean install site-deploy" and select DEFAULT_SCHEDULE, I > get the following error: > 2006-09-13 20:28:22,437 [btpool0-0] INFO Interceptor:exceptionLogging - > Error ocurred during execution > org.apache.maven.continuum.ContinuumException: failed update, build > definition didn't exist in project group > at > org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumAction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction.java:179) > at > org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectAction.execute(UpdateBuildDefinitionFromProjectAction.java:45) > at > org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinuum.java:2269) > at > org.apache.maven.continuum.DefaultContinuum.updateBuildDefinitionForProject(DefaultContinuum.java:1390) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject_aroundBody148(AcegiContinuum.java:507) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum$AjcClosure149.run(AcegiContinuum.java:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0cproceed(SecurityAspect.aj:1) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect$1.proceedWithObject(SecurityAspect.aj:59) > at > org.acegisecurity.intercept.method.aspectj.AspectJSecurityInterceptor.invoke(AspectJSecurityInterceptor.java:67) > at > org.codehaus.plexus.acegi.intercept.method.aspectj.SecurityAspect.ajc$around$org_codehaus_plexus_acegi_intercept_method_aspectj_SecurityAspect$1$6563cc0c(SecurityAspect.aj:62) > at > org.apache.maven.continuum.security.acegi.AcegiContinuum.updateBuildDefinitionForProject(AcegiContinuum.java:1) > at > org.apache.maven.continuum.web.action.BuildDefinitionAction.saveToProject(BuildDefinitionAction.java:139) > 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 > com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) >
[jira] Created: (MNG-2560) (patch) no useful error message when M2_HOME is misconfigured during bootstrap
(patch) no useful error message when M2_HOME is misconfigured during bootstrap -- Key: MNG-2560 URL: http://jira.codehaus.org/browse/MNG-2560 Project: Maven 2 Issue Type: Bug Components: Bootstrap & Build Affects Versions: 2.1 Reporter: Dan Fabulich Attachments: patch.txt Run the bootstrap build, but configure M2_HOME to be some random directory "foo". The tests will fail as maven will be installed into foo/../maven-2.1-SNAPSHOT, but then configured to actually use "foo" as the execution directory. The attached patch modifies the BootstrapInstaller to accept a "destDir" instead of a "prefix", and then double-checks that the destDir is a validly named destination before actually running the build. This allows the build to fail clearly and fast when this common configuration error is made. The README is also updated to highlight more clearly that you *must* M2_HOME correctly in order for the build to work. -- 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-847) add a friendly cron editor for editSchedule
[ http://jira.codehaus.org/browse/CONTINUUM-847?page=all ] Carlos Sanchez reopened CONTINUUM-847: -- Assignee: Maria Odea Ching (was: Carlos Sanchez) There are problems with table elements and the ones that ww generate. Already fixed the extra loop in svn. > add a friendly cron editor for editSchedule > --- > > Key: CONTINUUM-847 > URL: http://jira.codehaus.org/browse/CONTINUUM-847 > Project: Continuum > Issue Type: Improvement >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > Fix For: 1.1 > > Attachments: CONTINUUM-847-continuum-uml.patch, > CONTINUUM-847-continuum-webapp.patch, CONTINUUM-847-continuum-webapp.patch > > Original Estimate: 10 hours > Time Spent: 15 hours, 30 minutes > Remaining Estimate: 0 minutes > -- 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-847) add a friendly cron editor for editSchedule
[ http://jira.codehaus.org/browse/CONTINUUM-847?page=all ] Carlos Sanchez closed CONTINUUM-847. Assignee: Carlos Sanchez (was: Maria Odea Ching) Resolution: Fixed Fix Version/s: 1.1 Applied > add a friendly cron editor for editSchedule > --- > > Key: CONTINUUM-847 > URL: http://jira.codehaus.org/browse/CONTINUUM-847 > Project: Continuum > Issue Type: Improvement >Reporter: Maria Odea Ching > Assigned To: Carlos Sanchez > Fix For: 1.1 > > Attachments: CONTINUUM-847-continuum-uml.patch, > CONTINUUM-847-continuum-webapp.patch, CONTINUUM-847-continuum-webapp.patch > > Original Estimate: 10 hours > Time Spent: 15 hours, 30 minutes > Remaining Estimate: 0 minutes > -- 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-882) Exception during shutdown
Exception during shutdown - Key: CONTINUUM-882 URL: http://jira.codehaus.org/browse/CONTINUUM-882 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.1 Environment: continuum-acegi tomcat 5.5 Reporter: Carlos Sanchez Sep 14, 2006 2:05:55 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO: Failed shutdown of Apache Portable Runtime Exception in thread "Thread-1" javax.jdo.JDOUserException: Can't access or use PersistenceManagerFactory after it has been closed. at org.jpox.AbstractPersistenceManagerFactory.assertIsOpen(AbstractPersistenceManagerFactory.java:153) at org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:145) at org.apache.maven.continuum.store.JdoContinuumStore.getPersistenceManager(JdoContinuumStore.java:1382) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoContinuumStore.java:661) at org.apache.maven.continuum.store.JdoContinuumStore.updateSystemConfiguration(JdoContinuumStore.java:1132) at org.apache.maven.continuum.configuration.DefaultConfigurationService.store(DefaultConfigurationService.java:279) at org.apache.maven.continuum.DefaultContinuum.stopContinuum(DefaultContinuum.java:2195) at org.apache.maven.continuum.DefaultContinuum$1.run(DefaultContinuum.java:170) -- 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-874) Continuum does not seem to be trying to send email to the notifier
[ http://jira.codehaus.org/browse/CONTINUUM-874?page=all ] Emmanuel Venisse closed CONTINUUM-874. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1 Fixed. > Continuum does not seem to be trying to send email to the notifier > -- > > Key: CONTINUUM-874 > URL: http://jira.codehaus.org/browse/CONTINUUM-874 > Project: Continuum > Issue Type: Bug > Components: Mail Notifier >Affects Versions: 1.1 > Environment: Windows >Reporter: David Schwartz > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > > I have configure a mail notification in the POM using the following: > > continuum > > > mail > [EMAIL PROTECTED] > > > > I then tried to build this project twice. The first time it was a success > and the log did not seem to show any attempt to send an email. The second > time I changed a file so it would fail and there still did not seem to be an > attempt to send an email. Here is the output to the console: > 2006-09-13 21:42:36,234 [pool-1-thread-1] INFO ContinuumScm > - Updated 1 files. > 2006-09-13 21:42:36,281 [pool-1-thread-1] INFO BuildController > - Merging SCM results > 2006-09-13 21:42:36,296 [pool-1-thread-1] INFO BuildController > - Changes found, building > 2006-09-13 21:42:36,296 [pool-1-thread-1] INFO BuildController > - Performing action update-project-from-working-directory > 2006-09-13 21:42:36,328 [pool-1-thread-1] INFO > Action:update-project-from-working-directory - Updating project 'Websphere > Maven Plugin' from checkout. > 2006-09-13 21:42:36,406 [pool-1-thread-1] INFO JDO > - >> JoinMapStore.put key=address [EMAIL PROTECTED] > 2006-09-13 21:42:36,500 [pool-1-thread-1] WARN SQL > - Object with id > "6[OID]org.apache.maven.continuum.model.project.ProjectDependency" not found ! > 2006-09-13 21:42:36,500 [pool-1-thread-1] WARN SQL > - Object with id > "8[OID]org.apache.maven.continuum.model.project.ProjectDeveloper" not found ! > 2006-09-13 21:42:36,500 [pool-1-thread-1] WARN SQL > - Object with id > "7[OID]org.apache.maven.continuum.model.project.ProjectDependency" not found ! > 2006-09-13 21:42:36,515 [pool-1-thread-1] WARN SQL > - Object with id "2" not found ! > 2006-09-13 21:42:36,515 [pool-1-thread-1] WARN SQL > - Object with id > "8[OID]org.apache.maven.continuum.model.project.ProjectDependency" not found ! > 2006-09-13 21:42:36,515 [pool-1-thread-1] WARN SQL > - Object with id > "6[OID]org.apache.maven.continuum.model.project.ProjectDeveloper" not found ! > 2006-09-13 21:42:36,515 [pool-1-thread-1] WARN SQL > - Object with id > "7[OID]org.apache.maven.continuum.model.project.ProjectDeveloper" not found ! > 2006-09-13 21:42:36,515 [pool-1-thread-1] WARN SQL > - Object with id > "5[OID]org.apache.maven.continuum.model.project.ProjectDeveloper" not found ! > 2006-09-13 21:42:36,515 [pool-1-thread-1] INFO BuildController > - Performing action execute-builder > 2006-09-13 21:42:36,578 [pool-1-thread-1] WARN ContinuumBuildExecutor:maven2 > - Could not find the executable 'mvn' in this path: > 2006-09-13 21:42:36,609 [pool-1-thread-1] INFO ShellCommandHelper > - Executing: mvn --batch-mode --non-recursive clean install > 2006-09-13 21:42:36,609 [pool-1-thread-1] INFO ShellCommandHelper > - Working directory: > C:\usr\local\jetty\jetty-6.0.0rc1\webapps\continuum\WEB-INF\working-directory\1 > 2006-09-13 21:42:44,390 [pool-1-thread-1] INFO ContinuumBuildExecutor:maven2 > - Exit code: 1 > 2006-09-13 21:42:44,546 [pool-1-thread-1] INFO BuildController > - Performing action deploy-artifact -- 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-881) Multiple changesets can produce failure
[ http://jira.codehaus.org/browse/CONTINUUM-881?page=all ] Andrew Williams updated CONTINUUM-881: -- Attachment: ct38.patch newer patch - applies from continuum root :) (trunk) > Multiple changesets can produce failure > --- > > Key: CONTINUUM-881 > URL: http://jira.codehaus.org/browse/CONTINUUM-881 > Project: Continuum > Issue Type: Bug > Components: XMLRPC Interface >Affects Versions: 1.0.3 > Environment: Debian GNU Linux >Reporter: Andrew Williams >Priority: Minor > Attachments: ct38.patch, ct38.patch > > > There have been reports > (http://dev.rectang.com/projects/continutrac/ticket/38) that the author, > comment and revision fields are not always present so this patch was created > to work happily if this is the case... -- 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: (MAVENUPLOAD-1131) upload vraptor 2.2
upload vraptor 2.2 -- Key: MAVENUPLOAD-1131 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1131 Project: maven-upload-requests Issue Type: Task Reporter: Guilherme Silveira VRaptor 2.2 framework update with many improvements and loads of new docs. VRaptor 2 is a mvc controller based on the idea (stolen) from Rails that configuration should be minimal and conventions should be maximized. -- 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-881) Multiple changesets can produce failure
Multiple changesets can produce failure --- Key: CONTINUUM-881 URL: http://jira.codehaus.org/browse/CONTINUUM-881 Project: Continuum Issue Type: Bug Components: XMLRPC Interface Affects Versions: 1.0.3 Environment: Debian GNU Linux Reporter: Andrew Williams Priority: Minor Attachments: ct38.patch There have been reports (http://dev.rectang.com/projects/continutrac/ticket/38) that the author, comment and revision fields are not always present so this patch was created to work happily if this is the case... -- 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: (MAVENUPLOAD-1126) Upload request for SLF4J 1.1.0-beta0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1126?page=comments#action_74780 ] Ceki Gulcu commented on MAVENUPLOAD-1126: - My comment above was intended for Carlos, not for Sebastien. To recap, do you need anything else from our end to automatically sync with our project (SLF4J) repository with iiblio? Thanks in advance, > Upload request for SLF4J 1.1.0-beta0 > > > Key: MAVENUPLOAD-1126 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1126 > Project: maven-upload-requests > Issue Type: Task >Reporter: Sebastien Pennec > Attachments: jcl104-over-slf4j-1.1.0-beta0-bundle.jar, > log4j-over-slf4j-1.1.0-beta0-bundle.jar, slf4j-api-1.1.0-beta0-bundle.jar, > slf4j-archetype-1.1.0-beta0-bundle.jar, slf4j-jcl-1.1.0-beta0-bundle.jar, > slf4j-jdk14-1.1.0-beta0-bundle.jar, slf4j-log4j12-1.1.0-beta0-bundle.jar, > slf4j-nop-1.1.0-beta0-bundle.jar, slf4j-parent.jar, > slf4j-simple-1.1.0-beta0-bundle.jar > > > Thank you for adding these jars to the repository -- 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: (MAVENUPLOAD-1125) Upload jxls-core-0.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1125?page=comments#action_74772 ] Leonid Vysochyn commented on MAVENUPLOAD-1125: -- Hi guys! Could you let me know please how much time it is required to process a request like this? This module is required for the other project development so it is important for me to plan all the work in advance. And if I need to wait another week our project plans need to be shifted. I plan to make releases for this module rather often so it would be helpful if I know the time that is required to upload it to ibiblio after the release is done. Because it is actually can't be used until then in other projects. Thanks Leo > Upload jxls-core-0.9 bundle > --- > > Key: MAVENUPLOAD-1125 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1125 > Project: maven-upload-requests > Issue Type: Task >Reporter: Leonid Vysochyn > > This a bundle for a new release of jxls-core module of jXLS library. > The last related uploading request was > http://jira.codehaus.org/browse/MAVENUPLOAD-1115 -- 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: (MASSEMBLY-147) In multi project assembly, parent pom.xml not included in tar assembly
In multi project assembly, parent pom.xml not included in tar assembly
--
Key: MASSEMBLY-147
URL: http://jira.codehaus.org/browse/MASSEMBLY-147
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Dominic Zaza
Priority: Minor
I'm trying to create a source bundle for a multi module project.
I followed steps in
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-source-inclusion-simple.html
and was able to product a tar file.
However, my parent pom.xml is not included in the result tar file.
Additionally, I would like to "not" include my tests. I attempted to use the
following
${artifactId}
**/src/test/**
However, didn't work
--
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: (MPMULTIPROJECT-71) CLONE -goal multiproject:create-nav seems to have lost pom.id
[
http://jira.codehaus.org/browse/MPMULTIPROJECT-71?page=comments#action_74767 ]
Rupert Smith commented on MPMULTIPROJECT-71:
I attached a note to MPMULTIPROJECT-64 to say that this is caused by upgrading
checkstyle plugin. Everything worked fine before I upgraded my checkstyle, but
I needed to do that to get checktyle working properly on Java 1.5 syntax.
Workarounds: don't use checkstyle reports. Stick with older versions on
checkstyle.
This may be a bug with the checkstyle plugin and not the multiproject plugin,
suggest that once the culprit is identified the bug report be moved to the
appropriate plugin for fixing.
Rupert
> CLONE -goal multiproject:create-nav seems to have lost pom.id
> -
>
> Key: MPMULTIPROJECT-71
> URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-71
> Project: maven-multiproject-plugin
> Issue Type: Bug
>Affects Versions: 1.4.1
> Environment: maven 1.0.2 but with a couple of plugins upgraded to
> latest HEAD.
>Reporter: Rupert Smith
> Assigned To: Lukas Theussl
> Attachments: test.zip
>
>
> Today I have upgraded the checkstyle plugin to 3.0 from 2.6
> This seems to have downloaded a couple of libraries and I now have a strange
> behaviour for multiproject.
> I have also upgraded PMD to 1.8-SNAPSHOT but the following issue appeared
> before:
> When I run "maven multiproject:site", the reactor goes through all
> sub-projects ok BUT when it reaches the call to name="multiproject:create-nav"/>, it seems to lose the pom.id and declares
> that I must exclude the (the top level project" (see line 140 in th
> eplugin.jelly).
> , which is the pom.id, is replaced by the LAST project contained in the
> variable ${multiprojects}.
> the pom.id seems to have changed between the line just BEFORE the call to
> multiproject:create-nav and the FIRST line inside create-nav.
> If I modify the code to add some log:
> POM.id before calling create-nav ${pom.id}
>
> ...
>
>prereqs="multiproject:site-init">
>
> POM.id INSIDE create-nav ${pom.id} and multi ${multiprojects}
>
> POM.id INSIDE LOOP create-nav ${pom.id} and current
> ${reactorProject.id}
>
>
>
>
>
> The pom.id has changed between the first 2 echos. it then matches the last
> reactorProject.id and th ewhole process fails.
> I do not understand why the pom.id is changed somewhere in
> multiproject:site-init...
> My current workaround is to change the process can finish (but it does not generate a proper navigation.xml)
> There is obviously something wrong introduced by the latest download of a
> couple of plugin, I still have maven 1.0.2
> Is there a way I could list all plugins and version? I would post it here...
> Thanks for looking into it.
> Benoit
--
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: (MPMULTIPROJECT-71) CLONE -goal multiproject:create-nav seems to have lost pom.id
CLONE -goal multiproject:create-nav seems to have lost pom.id
-
Key: MPMULTIPROJECT-71
URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-71
Project: maven-multiproject-plugin
Issue Type: Bug
Affects Versions: 1.4.1
Environment: maven 1.0.2 but with a couple of plugins upgraded to
latest HEAD.
Reporter: Rupert Smith
Assigned To: Lukas Theussl
Today I have upgraded the checkstyle plugin to 3.0 from 2.6
This seems to have downloaded a couple of libraries and I now have a strange
behaviour for multiproject.
I have also upgraded PMD to 1.8-SNAPSHOT but the following issue appeared
before:
When I run "maven multiproject:site", the reactor goes through all sub-projects
ok BUT when it reaches the call to , it seems to lose the pom.id and declares that
I must exclude the (the top level project" (see line 140 in th
eplugin.jelly).
, which is the pom.id, is replaced by the LAST project contained in the
variable ${multiprojects}.
the pom.id seems to have changed between the line just BEFORE the call to
multiproject:create-nav and the FIRST line inside create-nav.
If I modify the code to add some log:
POM.id before calling create-nav ${pom.id}
...
POM.id INSIDE create-nav ${pom.id} and multi ${multiprojects}
POM.id INSIDE LOOP create-nav ${pom.id} and current
${reactorProject.id}
The pom.id has changed between the first 2 echos. it then matches the last
reactorProject.id and th ewhole process fails.
I do not understand why the pom.id is changed somewhere in
multiproject:site-init...
My current workaround is to change the http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPMULTIPROJECT-71) CLONE -goal multiproject:create-nav seems to have lost pom.id
[
http://jira.codehaus.org/browse/MPMULTIPROJECT-71?page=comments#action_74764 ]
Rupert Smith commented on MPMULTIPROJECT-71:
I re-opened this issue because MPMULTIPROJECT-64 was closed due to not being
reproducable.
I am attaching a test.zip file containing a sample project to reproduce it.
There are two sub-projects in this test.zip, dummy and mavenbuild. The
mavenbuild project is the master POM and dummy is a trivial project with just
one java class in it. Run multiproject:site form the mavenbuild directory to
reproduce the bug. Note that the maven-checkstyle-plugin-3.0.1.jar supplied in
the root of the test.zip file must be installed too.
To see it working without the bug, comment out the checkstyle report entry from
the project.xml in the mavenbuild directory.
Hope this helps.
P.S. I looked into the checkstyle plugin.jelly but I can't see where that would
change pom.id?
> CLONE -goal multiproject:create-nav seems to have lost pom.id
> -
>
> Key: MPMULTIPROJECT-71
> URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-71
> Project: maven-multiproject-plugin
> Issue Type: Bug
>Affects Versions: 1.4.1
> Environment: maven 1.0.2 but with a couple of plugins upgraded to
> latest HEAD.
>Reporter: Rupert Smith
> Assigned To: Lukas Theussl
>
> Today I have upgraded the checkstyle plugin to 3.0 from 2.6
> This seems to have downloaded a couple of libraries and I now have a strange
> behaviour for multiproject.
> I have also upgraded PMD to 1.8-SNAPSHOT but the following issue appeared
> before:
> When I run "maven multiproject:site", the reactor goes through all
> sub-projects ok BUT when it reaches the call to name="multiproject:create-nav"/>, it seems to lose the pom.id and declares
> that I must exclude the (the top level project" (see line 140 in th
> eplugin.jelly).
> , which is the pom.id, is replaced by the LAST project contained in the
> variable ${multiprojects}.
> the pom.id seems to have changed between the line just BEFORE the call to
> multiproject:create-nav and the FIRST line inside create-nav.
> If I modify the code to add some log:
> POM.id before calling create-nav ${pom.id}
>
> ...
>
>prereqs="multiproject:site-init">
>
> POM.id INSIDE create-nav ${pom.id} and multi ${multiprojects}
>
> POM.id INSIDE LOOP create-nav ${pom.id} and current
> ${reactorProject.id}
>
>
>
>
>
> The pom.id has changed between the first 2 echos. it then matches the last
> reactorProject.id and th ewhole process fails.
> I do not understand why the pom.id is changed somewhere in
> multiproject:site-init...
> My current workaround is to change the process can finish (but it does not generate a proper navigation.xml)
> There is obviously something wrong introduced by the latest download of a
> couple of plugin, I still have maven 1.0.2
> Is there a way I could list all plugins and version? I would post it here...
> Thanks for looking into it.
> Benoit
--
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-2551) pom metadata file gets truncated during install into local repository
[ http://jira.codehaus.org/browse/MNG-2551?page=comments#action_74763 ] Sharmarke Aden commented on MNG-2551: - Yes, I should have also mentioned that I'm using Continuum as well. This problem occurs when a project depends on another project. If we build the main project, the sub project is built first and during the build of the sub project is when a truncated pom file is installed into the local repository. Now an attempt is made to build the main project, and of course this is when everything comes crashing down because the sub project pom is not a valid/complete XML. I wasn't sure if this is a continuum bug or a artifact, but looking at the continuum code, I saw nothing whacking or bizarre. > pom metadata file gets truncated during install into local repository > - > > Key: MNG-2551 > URL: http://jira.codehaus.org/browse/MNG-2551 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Artifacts >Affects Versions: 2.0.4 > Environment: Win XP, JDK 1.4 >Reporter: Sharmarke Aden > Attachments: pom.xml, shared-1.9.0.pom > > > When I attempt to install my project artifact to my local repository it seems > that sometimes an incomplete/truncated ".pom" is deployed to my local > repository. It's kind of weird because sometimes it happens and sometimes it > doesn't. Any thoughts as to what could cause this? Attached is my pom.xml and > the truncated pom meta data artifact deployed to my local repository. One > thing I found that's odd is that the size of the truncated pom generated is > consistently 4096 bytes. > p.s. my pom.xml is UTF-8 encoded and uses Unix style line delimiters. -- 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: (MPMULTIPROJECT-71) CLONE -goal multiproject:create-nav seems to have lost pom.id
[ http://jira.codehaus.org/browse/MPMULTIPROJECT-71?page=all ]
Rupert Smith updated MPMULTIPROJECT-71:
---
Attachment: test.zip
Here's the test project to reproduce the bug with.
> CLONE -goal multiproject:create-nav seems to have lost pom.id
> -
>
> Key: MPMULTIPROJECT-71
> URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-71
> Project: maven-multiproject-plugin
> Issue Type: Bug
>Affects Versions: 1.4.1
> Environment: maven 1.0.2 but with a couple of plugins upgraded to
> latest HEAD.
>Reporter: Rupert Smith
> Assigned To: Lukas Theussl
> Attachments: test.zip
>
>
> Today I have upgraded the checkstyle plugin to 3.0 from 2.6
> This seems to have downloaded a couple of libraries and I now have a strange
> behaviour for multiproject.
> I have also upgraded PMD to 1.8-SNAPSHOT but the following issue appeared
> before:
> When I run "maven multiproject:site", the reactor goes through all
> sub-projects ok BUT when it reaches the call to name="multiproject:create-nav"/>, it seems to lose the pom.id and declares
> that I must exclude the (the top level project" (see line 140 in th
> eplugin.jelly).
> , which is the pom.id, is replaced by the LAST project contained in the
> variable ${multiprojects}.
> the pom.id seems to have changed between the line just BEFORE the call to
> multiproject:create-nav and the FIRST line inside create-nav.
> If I modify the code to add some log:
> POM.id before calling create-nav ${pom.id}
>
> ...
>
>prereqs="multiproject:site-init">
>
> POM.id INSIDE create-nav ${pom.id} and multi ${multiprojects}
>
> POM.id INSIDE LOOP create-nav ${pom.id} and current
> ${reactorProject.id}
>
>
>
>
>
> The pom.id has changed between the first 2 echos. it then matches the last
> reactorProject.id and th ewhole process fails.
> I do not understand why the pom.id is changed somewhere in
> multiproject:site-init...
> My current workaround is to change the process can finish (but it does not generate a proper navigation.xml)
> There is obviously something wrong introduced by the latest download of a
> couple of plugin, I still have maven 1.0.2
> Is there a way I could list all plugins and version? I would post it here...
> Thanks for looking into it.
> Benoit
--
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: (MPMULTIPROJECT-64) goal multiproject:create-nav seems to have lost pom.id
[
http://jira.codehaus.org/browse/MPMULTIPROJECT-64?page=comments#action_74761 ]
Lukas Theussl commented on MPMULTIPROJECT-64:
-
As I said above, please attach a test case and reopen the issue, if you can't
reopen it, create a new one.
I have spent quite some time on this issue and couldn't reproduce it anymore.
Don't forget to specify your environment settings as well. Thanks!
> goal multiproject:create-nav seems to have lost pom.id
> --
>
> Key: MPMULTIPROJECT-64
> URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-64
> Project: maven-multiproject-plugin
> Issue Type: Bug
>Affects Versions: 1.4.1
> Environment: maven 1.0.2 but with a couple of plugins upgraded to
> latest HEAD.
>Reporter: Benoit Xhenseval
> Assigned To: Lukas Theussl
>
> Today I have upgraded the checkstyle plugin to 3.0 from 2.6
> This seems to have downloaded a couple of libraries and I now have a strange
> behaviour for multiproject.
> I have also upgraded PMD to 1.8-SNAPSHOT but the following issue appeared
> before:
> When I run "maven multiproject:site", the reactor goes through all
> sub-projects ok BUT when it reaches the call to name="multiproject:create-nav"/>, it seems to lose the pom.id and declares
> that I must exclude the (the top level project" (see line 140 in th
> eplugin.jelly).
> , which is the pom.id, is replaced by the LAST project contained in the
> variable ${multiprojects}.
> the pom.id seems to have changed between the line just BEFORE the call to
> multiproject:create-nav and the FIRST line inside create-nav.
> If I modify the code to add some log:
> POM.id before calling create-nav ${pom.id}
>
> ...
>
>prereqs="multiproject:site-init">
>
> POM.id INSIDE create-nav ${pom.id} and multi ${multiprojects}
>
> POM.id INSIDE LOOP create-nav ${pom.id} and current
> ${reactorProject.id}
>
>
>
>
>
> The pom.id has changed between the first 2 echos. it then matches the last
> reactorProject.id and th ewhole process fails.
> I do not understand why the pom.id is changed somewhere in
> multiproject:site-init...
> My current workaround is to change the process can finish (but it does not generate a proper navigation.xml)
> There is obviously something wrong introduced by the latest download of a
> couple of plugin, I still have maven 1.0.2
> Is there a way I could list all plugins and version? I would post it here...
> Thanks for looking into it.
> Benoit
--
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: (MPMULTIPROJECT-64) goal multiproject:create-nav seems to have lost pom.id
[
http://jira.codehaus.org/browse/MPMULTIPROJECT-64?page=comments#action_74760 ]
Rupert Smith commented on MPMULTIPROJECT-64:
Please re-open this issue. The problem seems to be caused by using a the newer
checkstyle plugin. Before I upgraded my checkstyle plugin it worked fine, now
with checkstyle plugin version 3.0.1 I get this error.
As a workaround, I am able to make the problem go away by not generating the
checkstyle report.
Rupert
> goal multiproject:create-nav seems to have lost pom.id
> --
>
> Key: MPMULTIPROJECT-64
> URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-64
> Project: maven-multiproject-plugin
> Issue Type: Bug
>Affects Versions: 1.4.1
> Environment: maven 1.0.2 but with a couple of plugins upgraded to
> latest HEAD.
>Reporter: Benoit Xhenseval
> Assigned To: Lukas Theussl
>
> Today I have upgraded the checkstyle plugin to 3.0 from 2.6
> This seems to have downloaded a couple of libraries and I now have a strange
> behaviour for multiproject.
> I have also upgraded PMD to 1.8-SNAPSHOT but the following issue appeared
> before:
> When I run "maven multiproject:site", the reactor goes through all
> sub-projects ok BUT when it reaches the call to name="multiproject:create-nav"/>, it seems to lose the pom.id and declares
> that I must exclude the (the top level project" (see line 140 in th
> eplugin.jelly).
> , which is the pom.id, is replaced by the LAST project contained in the
> variable ${multiprojects}.
> the pom.id seems to have changed between the line just BEFORE the call to
> multiproject:create-nav and the FIRST line inside create-nav.
> If I modify the code to add some log:
> POM.id before calling create-nav ${pom.id}
>
> ...
>
>prereqs="multiproject:site-init">
>
> POM.id INSIDE create-nav ${pom.id} and multi ${multiprojects}
>
> POM.id INSIDE LOOP create-nav ${pom.id} and current
> ${reactorProject.id}
>
>
>
>
>
> The pom.id has changed between the first 2 echos. it then matches the last
> reactorProject.id and th ewhole process fails.
> I do not understand why the pom.id is changed somewhere in
> multiproject:site-init...
> My current workaround is to change the process can finish (but it does not generate a proper navigation.xml)
> There is obviously something wrong introduced by the latest download of a
> couple of plugin, I still have maven 1.0.2
> Is there a way I could list all plugins and version? I would post it here...
> Thanks for looking into it.
> Benoit
--
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: (MSUREFIRE-165) Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest method
Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest method
---
Key: MSUREFIRE-165
URL: http://jira.codehaus.org/browse/MSUREFIRE-165
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Components: TestNG support
Affects Versions: 2.2, 2.3
Environment: Windows XP, JDK 1.5, Maven 2.0.4, TestNG 5.1
Reporter: Manish Shah
Create a TestNG test with a method as follows:
@BeforeTest
public void beforeTest() {
throw new RuntimeException("Simulate an exception from a beforeTest
method");
}
When surefire attempts to run this test, the plugin fails with the following
stack trace:
org.apache.maven.surefire.booter.SurefireExecutionException: null; nested
exception is java.lang.NullPointerException: n
ull
java.lang.NullPointerException
at
org.apache.maven.surefire.report.AbstractTextReporter.testFailed(AbstractTextReporter.java:106)
at
org.apache.maven.surefire.report.ReporterManager.testFailed(ReporterManager.java:299)
at
org.apache.maven.surefire.report.ReporterManager.testFailed(ReporterManager.java:281)
at
org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:97)
at org.testng.internal.Invoker.runTestListeners(Invoker.java:1164)
at org.testng.internal.Invoker.runTestListeners(Invoker.java:1149)
at
org.testng.internal.Invoker.handleConfigurationFailure(Invoker.java:191)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:170)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:236)
at org.testng.SuiteRunner.run(SuiteRunner.java:145)
at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:901)
at org.testng.TestNG.runSuitesLocally(TestNG.java:863)
at
org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:64)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75)
at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)
--
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-880) Non-manageConfiguration roles/permissions needs an index page.
Non-manageConfiguration roles/permissions needs an index page. -- Key: CONTINUUM-880 URL: http://jira.codehaus.org/browse/CONTINUUM-880 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Teodoro Cue Jr. Sample: A user that only has a manageUser role has an "Access is denied" page after logging in. Although he can perform his roles/duties by typing http://.../user/list.action. Also, the Show Project link is visible from the menu but "Access is denied" after clicking. A more general description with this is that all users without a manageConfiguration role/permission doesn't have an index page. -- 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-877) Can add a userGroup with same name as an existing userGroup.
[ http://jira.codehaus.org/browse/CONTINUUM-877?page=all ] Teodoro Cue Jr. updated CONTINUUM-877: -- Component/s: Web interface > Can add a userGroup with same name as an existing userGroup. > > > Key: CONTINUUM-877 > URL: http://jira.codehaus.org/browse/CONTINUUM-877 > Project: Continuum > Issue Type: Bug > Components: Web interface >Reporter: Teodoro Cue Jr. > > The system allows the addition of a new userGroup with the same name as an > existing userGroup. -- 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-878) Changing password that's invalid will result to a blank page.
Changing password that's invalid will result to a blank page.
-
Key: CONTINUUM-878
URL: http://jira.codehaus.org/browse/CONTINUUM-878
Project: Continuum
Issue Type: Bug
Components: Web interface
Reporter: Teodoro Cue Jr.
After changing to an invalid password, a blank page is loaded. An exception
occured and below is the stacktrace.
2006-09-14 20:49:12,515 [btpool0-2] ERROR Component - tag
'select', field 'list', name 'groups': The requested list key 'allGroups' could
not be resolved as a collection/array/map/enumeration/iterator type. Example:
people or people.{name}
2006-09-14 20:49:12.515::WARN: EXCEPTION
org.apache.jasper.JasperException: tag 'select', field 'list', name 'groups':
The requested list key 'allGroups' could not be resolved as a
collection/array/map/enumeration/iterator type. Example: people or people.{name}
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:440)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:335)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:442)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:615)
at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:189)
at com.opensymphony.webwork.components.Include.include(Include.java:227)
at com.opensymphony.webwork.components.Include.end(Include.java:136)
at
com.opensymphony.webwork.views.jsp.ComponentTagSupport.doEndTag(ComponentTagSupport.java:21)
at
org.apache.jsp.user.edit_jsp._jspx_meth_ww_include_0(org.apache.jsp.user.edit_jsp:438)
at
org.apache.jsp.user.edit_jsp._jspx_meth_ww_i18n_0(org.apache.jsp.user.edit_jsp:164)
at
org.apache.jsp.user.edit_jsp._jspService(org.apache.jsp.user.edit_jsp:108)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:358)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:440)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:335)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:442)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:615)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:262)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:124)
at
com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:114)
at
com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkResultSupport.java:143)
at
com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:311)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:206)
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.i
[jira] Created: (CONTINUUM-879) Users list page needs authorization.
Users list page needs authorization. Key: CONTINUUM-879 URL: http://jira.codehaus.org/browse/CONTINUUM-879 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Teodoro Cue Jr. A user that only has a manageConfig role can view the users list after changing password. Although he can't perform anything. -- 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-877) Can add a userGroup with same name as an existing userGroup.
Can add a userGroup with same name as an existing userGroup. Key: CONTINUUM-877 URL: http://jira.codehaus.org/browse/CONTINUUM-877 Project: Continuum Issue Type: Bug Reporter: Teodoro Cue Jr. The system allows the addition of a new userGroup with the same name as an existing userGroup. -- 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-876) Can add a user with same username as an existing user.
Can add a user with same username as an existing user. -- Key: CONTINUUM-876 URL: http://jira.codehaus.org/browse/CONTINUUM-876 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Teodoro Cue Jr. The system allows the addition of a new user with the same username as an existing user. -- 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: (MANTLR-10) Build should fail if antlr fails
[ http://jira.codehaus.org/browse/MANTLR-10?page=all ] Vincent Siveton closed MANTLR-10. - Resolution: Fixed fixed > Build should fail if antlr fails > > > Key: MANTLR-10 > URL: http://jira.codehaus.org/browse/MANTLR-10 > Project: Maven 2.x Antlr Plugin > Issue Type: Bug >Reporter: Vincent Siveton > Assigned To: Vincent Siveton > > We need to handle System.err used by antlr > See the antlr.Tool#main() implementation -- 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: (MANTLR-10) Build should fail if antlr fails
Build should fail if antlr fails Key: MANTLR-10 URL: http://jira.codehaus.org/browse/MANTLR-10 Project: Maven 2.x Antlr Plugin Issue Type: Bug Reporter: Vincent Siveton Assigned To: Vincent Siveton We need to handle System.err used by antlr See the antlr.Tool#main() implementation -- 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-734) Can't use continuum behind https proxy
[ http://jira.codehaus.org/browse/CONTINUUM-734?page=comments#action_74745
]
Richard van der Hoff commented on CONTINUUM-734:
No; the Base URL is used when generating error report emails and so on, but not
when generating the page content.
> Can't use continuum behind https proxy
> --
>
> Key: CONTINUUM-734
> URL: http://jira.codehaus.org/browse/CONTINUUM-734
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
>Affects Versions: 1.0.3
>Reporter: Richard van der Hoff
> Fix For: 1.1
>
>
> As noted in CONTINUUM-240, it's not currentlyy possible to run the continuum
> webapp behind an https proxy, as all the links are http://...
> My apache setup is something along the lines of:
> {code:xml}
>
> SSLEngine on
> ProxyPass / http://localhost:8080/
> ProxyPassReverse / http://localhost:8080/
> ProxyPreserveHost On
>
> {code}
> and my jetty config:
> {code:xml}
>
>
> 8080
>
>
> {code}
> The links are correct, except that they have s/https/http/.
> Why does the webapp need to use absolute links anyway?
--
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-847) add a friendly cron editor for editSchedule
[ http://jira.codehaus.org/browse/CONTINUUM-847?page=all ] Maria Odea Ching updated CONTINUUM-847: --- Attachment: CONTINUUM-847-continuum-webapp.patch Attached patch file with the revised editSchedule.jsp page, ScheduleAction class and Continuum.properties. > add a friendly cron editor for editSchedule > --- > > Key: CONTINUUM-847 > URL: http://jira.codehaus.org/browse/CONTINUUM-847 > Project: Continuum > Issue Type: Improvement >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > Attachments: CONTINUUM-847-continuum-uml.patch, > CONTINUUM-847-continuum-webapp.patch, CONTINUUM-847-continuum-webapp.patch > > Original Estimate: 10 hours > Time Spent: 11 hours > Remaining Estimate: 0 minutes > -- 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-875) projectEdit page validates before submit
[ http://jira.codehaus.org/browse/CONTINUUM-875?page=all ] Napoleon Esmundo C. Ramirez closed CONTINUUM-875. - Resolution: Fixed > projectEdit page validates before submit > > > Key: CONTINUUM-875 > URL: http://jira.codehaus.org/browse/CONTINUUM-875 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Napoleon Esmundo C. Ramirez > Fix For: 1.1 > > > projectEdit (linked from projectView) shows the validation errors with empty > fields, is the same as another error that Nap Ramirez solved this week -- 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-875) projectEdit page validates before submit
[ http://jira.codehaus.org/browse/CONTINUUM-875?page=comments#action_74741 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-875: --- projectEdit.doEdit() is invoked in this link. Added doEdit() in the list of methods that do not need validation the first time the page is loaded > projectEdit page validates before submit > > > Key: CONTINUUM-875 > URL: http://jira.codehaus.org/browse/CONTINUUM-875 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Napoleon Esmundo C. Ramirez > Fix For: 1.1 > > > projectEdit (linked from projectView) shows the validation errors with empty > fields, is the same as another error that Nap Ramirez solved this week -- 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: (MNG-2559) Module Selection From Command Line Argument Broken
Module Selection From Command Line Argument Broken -- Key: MNG-2559 URL: http://jira.codehaus.org/browse/MNG-2559 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.0.4 Environment: Linux 2.6.16-gentoo-r7 #3 SMP PREEMPT i686 Intel(R) Xeon(TM) CPU 3.40GHz GNU/Linux Java HotSpot(TM) Server VM (build 1.5.0_07-b03, mixed mode) Maven 2.0.4 Reporter: Gus Power Hi, I am unable to specify which modules to include in the reactor build from the command line when invoking maven on the parent POM. Having searched around on Google I have seen references to invoking maven using the following syntax: 'mvn -Dmodule=moduleName goal' but it does not appear to have any effect. My solution is to define different module combinations in different parent POM profiles but this is clunky and inflexible. This has been a key annoyance in setting up different cruisecontrol configurations for our continuous build. Regards, Gus. -- 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-687) Option to trigger the SCM system to tag successful builds with a build number or timestamp.
[ http://jira.codehaus.org/browse/CONTINUUM-687?page=comments#action_74740 ] Roald Bankras commented on CONTINUUM-687: - the labeling can already be done by calling the scm plugin with goal tag. The problem lies in the fact that continuum doesn't pass the build-nummer to maven. > Option to trigger the SCM system to tag successful builds with a build number > or timestamp. > --- > > Key: CONTINUUM-687 > URL: http://jira.codehaus.org/browse/CONTINUUM-687 > Project: Continuum > Issue Type: New Feature > Components: Core system, SCM >Reporter: Christian Gruber > > This is complex, because it would be different for each type. For maven2, > for example, it would be potentially compled on its own, insofar as tagging > is handled quite differently between CVS and SVN (to pick two). I could see > a potential workaround, if build defs were independent within a project, by > using a specific goal (say on a nightly build) and therefor "manually" > invoking scm:tag or something. > In short, I'm not sure if it's better to do this within the build system, or > continuum. Suggestions? Best practices anyone? -- 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: (MSUREFIREREP-31) Add a window and a document title plus a document description (like made in javadoc and jxr plugin)
Add a window and a document title plus a document description (like made in javadoc and jxr plugin) --- Key: MSUREFIREREP-31 URL: http://jira.codehaus.org/browse/MSUREFIREREP-31 Project: Maven 2.x Surefire report Plugin Issue Type: New Feature Affects Versions: 2.0 Environment: WinXp, Java5 Reporter: Martin Zeltner Attachments: patch_maven-surefire-report-plugin_add-window-and-doc-title-plus-doc-description.patch Add a window and a document title plus a document description (like made in javadoc and jxr plugin). By default the windowTitle, docTitle and docDescription are taken from the resource bundle but if one likes to use a specific (like made in javadoc and jxr plugin) these three parameters can be personalized. 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] Commented: (CONTINUUM-734) Can't use continuum behind https proxy
[ http://jira.codehaus.org/browse/CONTINUUM-734?page=comments#action_74730
]
David Roussel commented on CONTINUUM-734:
-
Can't you just go into
http://localhost:8080/continuum/continuum/target/EditContinuumConfiguration.vm
and change the Base URL to the https version?
> Can't use continuum behind https proxy
> --
>
> Key: CONTINUUM-734
> URL: http://jira.codehaus.org/browse/CONTINUUM-734
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
>Affects Versions: 1.0.3
>Reporter: Richard van der Hoff
> Fix For: 1.1
>
>
> As noted in CONTINUUM-240, it's not currentlyy possible to run the continuum
> webapp behind an https proxy, as all the links are http://...
> My apache setup is something along the lines of:
> {code:xml}
>
> SSLEngine on
> ProxyPass / http://localhost:8080/
> ProxyPassReverse / http://localhost:8080/
> ProxyPreserveHost On
>
> {code}
> and my jetty config:
> {code:xml}
>
>
> 8080
>
>
> {code}
> The links are correct, except that they have s/https/http/.
> Why does the webapp need to use absolute links anyway?
--
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: (MPJAVA-46) Provide support for Java 6
Provide support for Java 6 -- Key: MPJAVA-46 URL: http://jira.codehaus.org/browse/MPJAVA-46 Project: maven-java-plugin Issue Type: New Feature Environment: N/A Reporter: Dominique Jean-Prost Please provide support for java 1.6 -- 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-875) projectEdit page validates before submit
projectEdit page validates before submit Key: CONTINUUM-875 URL: http://jira.codehaus.org/browse/CONTINUUM-875 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez Fix For: 1.1 projectEdit (linked from projectView) shows the validation errors with empty fields, is the same as another error that Nap Ramirez solved this week -- 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: (MSUREFIREREP-30) Use lowercase html anchor names, else these links will not work
Use lowercase html anchor names, else these links will not work --- Key: MSUREFIREREP-30 URL: http://jira.codehaus.org/browse/MSUREFIREREP-30 Project: Maven 2.x Surefire report Plugin Issue Type: Bug Affects Versions: 2.0 Environment: WinXp, Java5 Reporter: Martin Zeltner Attachments: patch_maven-surefire-report-plugin_html-anchor-ids-must-be-lowercase.patch The class *org.apache.maven.plugins.surefire.report.SurefireReportGenerator* does generate html anchors with upper cases. With the newest version of the XhtmlSink of doxia created uppercase anchor ids will be automatically made lowercase. In Mozilla browsers links with upper cases in anchors and lower cases in anchor ids will not work. The Internet Explorer doesn't care about cases. In appended patch I've corrected this issue by lowercasing every link anchor. 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] Updated: (CONTINUUM-875) projectEdit page validates before submit
[ http://jira.codehaus.org/browse/CONTINUUM-875?page=all ] Carlos Sanchez updated CONTINUUM-875: - Fix Version/s: 1.1 > projectEdit page validates before submit > > > Key: CONTINUUM-875 > URL: http://jira.codehaus.org/browse/CONTINUUM-875 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Fix For: 1.1 > > > projectEdit (linked from projectView) shows the validation errors with empty > fields, is the same as another error that Nap Ramirez solved this week -- 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: (MASSEMBLY-146) Including -javadoc.jars in a package
Including -javadoc.jars in a package Key: MASSEMBLY-146 URL: http://jira.codehaus.org/browse/MASSEMBLY-146 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Reporter: Frank Cornelis Via the maven-javadoc-plugin it's very easy to construct secundary artifact -javadoc.jars. How can I include these javadoc JARs in my assembly? -- 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-873) Clicking "Add" in the Notifiers section of a project causes an exception
[ http://jira.codehaus.org/browse/CONTINUUM-873?page=all ]
Carlos Sanchez closed CONTINUUM-873.
Assignee: Carlos Sanchez (was: Henry S. Isidro)
Resolution: Fixed
> Clicking "Add" in the Notifiers section of a project causes an exception
>
>
> Key: CONTINUUM-873
> URL: http://jira.codehaus.org/browse/CONTINUUM-873
> Project: Continuum
> Issue Type: Bug
>Affects Versions: 1.1
> Environment: Windows
>Reporter: David Schwartz
> Assigned To: Carlos Sanchez
> Fix For: 1.1
>
> Attachments: CONTINUUM-873-continuum-webapp.patch
>
>
> When I click on the "Add" button in the Notifiers section of a project I get
> the following exception:
> 2006-09-13 20:36:14,828 [btpool0-0] INFO Action:addNotifier -
> checking the continuum configuration
> :WARN: EXCEPTION
> org.apache.jasper.JasperException: /notifierSelectType.jsp(17,16) PWC6038:
> "#{ 'mail' : 'Mail', 'irc' : 'IRC', 'jabber' : 'Jabber', 'msn' : 'MSN'}"
> contains invalid expression(s): javax.el.ELException: Error Parsing: #{
> 'mail' : 'Mail', 'irc' : 'IRC', 'jabber' : 'Jabber', 'msn' : 'MSN'}
> at
> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:49)
> at
> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:461)
> at
> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:211)
> at
> org.apache.jasper.compiler.JspUtil.validateExpressions(JspUtil.java:629)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.getJspAttribute(Validator.java:1261)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1037)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:820)
> at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1469)
> at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
> at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2294)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
> at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1469)
> at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
> at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2294)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
> at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1469)
> at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
> at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2294)
> at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2300)
> at org.apache.jasper.compiler.Node$Root.accept(Node.java:468)
> at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
> at org.apache.jasper.compiler.Validator.validate(Validator.java:1759)
> at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:278)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:620)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:602)
> at
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:618)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:329)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:440)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:335)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:442)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:357)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:615)
> at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:263)
> at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:125)
> at
> com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:114)
> at
> com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkResultSupport.java:143)
> at
> com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:311)
> at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:206)
> at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168)
> at
> com.opensymphony.xwork.interceptor.MethodFilterIntercept
[jira] Closed: (CONTINUUM-867) User edit page is missing fields
[ http://jira.codehaus.org/browse/CONTINUUM-867?page=all ] Napoleon Esmundo C. Ramirez closed CONTINUUM-867. - Resolution: Fixed > User edit page is missing fields > > > Key: CONTINUUM-867 > URL: http://jira.codehaus.org/browse/CONTINUUM-867 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Napoleon Esmundo C. Ramirez >Priority: Critical > Fix For: 1.1 > > > It needs other fields like user name and specially the feature to unlock an > user account -- 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-2551) pom metadata file gets truncated during install into local repository
[ http://jira.codehaus.org/browse/MNG-2551?page=comments#action_74725 ] Joost den Boer commented on MNG-2551: - I have the exact same problem on a continuum buildserver on linux using Maven 2.0.4 and JDK 1.5_06. The problem occurs only on some project. Not on all. > pom metadata file gets truncated during install into local repository > - > > Key: MNG-2551 > URL: http://jira.codehaus.org/browse/MNG-2551 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Artifacts >Affects Versions: 2.0.4 > Environment: Win XP, JDK 1.4 >Reporter: Sharmarke Aden > Attachments: pom.xml, shared-1.9.0.pom > > > When I attempt to install my project artifact to my local repository it seems > that sometimes an incomplete/truncated ".pom" is deployed to my local > repository. It's kind of weird because sometimes it happens and sometimes it > doesn't. Any thoughts as to what could cause this? Attached is my pom.xml and > the truncated pom meta data artifact deployed to my local repository. One > thing I found that's odd is that the size of the truncated pom generated is > consistently 4096 bytes. > p.s. my pom.xml is UTF-8 encoded and uses Unix style line delimiters. -- 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-867) User edit page is missing fields
[ http://jira.codehaus.org/browse/CONTINUUM-867?page=comments#action_74722 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-867: --- The Full Name and lock fields were added in the add/edit user form. The lock of the user's account can be toggled--using a checkbox. > User edit page is missing fields > > > Key: CONTINUUM-867 > URL: http://jira.codehaus.org/browse/CONTINUUM-867 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Napoleon Esmundo C. Ramirez >Priority: Critical > Fix For: 1.1 > > > It needs other fields like user name and specially the feature to unlock an > user account -- 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-869) From build result top tabs don't work
[ http://jira.codehaus.org/browse/CONTINUUM-869?page=all ] Carlos Sanchez closed CONTINUUM-869. Assignee: Carlos Sanchez (was: Henry S. Isidro) Resolution: Fixed Fixed in other way, just including projectMenu > From build result top tabs don't work > - > > Key: CONTINUUM-869 > URL: http://jira.codehaus.org/browse/CONTINUUM-869 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Carlos Sanchez > Fix For: 1.1 > > Attachments: CONTINUUM-869-continuum-webapp.patch, > CONTINUUM-869-continuum-webapp.patch2 > > > They don't set the projectId parameter probably -- 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-873) Clicking "Add" in the Notifiers section of a project causes an exception
[ http://jira.codehaus.org/browse/CONTINUUM-873?page=all ]
Henry S. Isidro updated CONTINUUM-873:
--
Attachment: CONTINUUM-873-continuum-webapp.patch
File Attached: CONTINUUM-873-continuum-webapp.patch
This fixes the problem.
> Clicking "Add" in the Notifiers section of a project causes an exception
>
>
> Key: CONTINUUM-873
> URL: http://jira.codehaus.org/browse/CONTINUUM-873
> Project: Continuum
> Issue Type: Bug
>Affects Versions: 1.1
> Environment: Windows
>Reporter: David Schwartz
> Assigned To: Henry S. Isidro
> Fix For: 1.1
>
> Attachments: CONTINUUM-873-continuum-webapp.patch
>
>
> When I click on the "Add" button in the Notifiers section of a project I get
> the following exception:
> 2006-09-13 20:36:14,828 [btpool0-0] INFO Action:addNotifier -
> checking the continuum configuration
> :WARN: EXCEPTION
> org.apache.jasper.JasperException: /notifierSelectType.jsp(17,16) PWC6038:
> "#{ 'mail' : 'Mail', 'irc' : 'IRC', 'jabber' : 'Jabber', 'msn' : 'MSN'}"
> contains invalid expression(s): javax.el.ELException: Error Parsing: #{
> 'mail' : 'Mail', 'irc' : 'IRC', 'jabber' : 'Jabber', 'msn' : 'MSN'}
> at
> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:49)
> at
> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:461)
> at
> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:211)
> at
> org.apache.jasper.compiler.JspUtil.validateExpressions(JspUtil.java:629)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.getJspAttribute(Validator.java:1261)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1037)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:820)
> at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1469)
> at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
> at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2294)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
> at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1469)
> at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
> at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2294)
> at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
> at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1469)
> at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
> at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2294)
> at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2300)
> at org.apache.jasper.compiler.Node$Root.accept(Node.java:468)
> at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
> at org.apache.jasper.compiler.Validator.validate(Validator.java:1759)
> at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:278)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:620)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:602)
> at
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:618)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:329)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:440)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:335)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:442)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:357)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:615)
> at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:263)
> at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:125)
> at
> com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:114)
> at
> com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkResultSupport.java:143)
> at
> com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:311)
> at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:206)
> at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168)
> at
[jira] Updated: (CONTINUUM-869) From build result top tabs don't work
[ http://jira.codehaus.org/browse/CONTINUUM-869?page=all ] Henry S. Isidro updated CONTINUUM-869: -- Attachment: CONTINUUM-869-continuum-webapp.patch2 File Attached: CONTINUUM-869-continuum-webapp.patch2 New patch using nested ww:param in ww:url > From build result top tabs don't work > - > > Key: CONTINUUM-869 > URL: http://jira.codehaus.org/browse/CONTINUUM-869 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Henry S. Isidro > Fix For: 1.1 > > Attachments: CONTINUUM-869-continuum-webapp.patch, > CONTINUUM-869-continuum-webapp.patch2 > > > They don't set the projectId parameter probably -- 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
