[jira] Created: (CONTINUUM-1633) release using mvn release plugin
release using mvn release plugin Key: CONTINUUM-1633 URL: http://jira.codehaus.org/browse/CONTINUUM-1633 Project: Continuum Issue Type: Improvement Components: Release Affects Versions: 1.1 Reporter: Benoit Decherf I think that the release process should use the release plugin rather than the maven-release classes directly. Actually, it's possible to choose the maven installation to execute the compilation in continuum, BUT the maven version used to release a project can't be changed because of the compilation/runtime dependency of continuum-release. Also, if I configure the release plugin in pom.xml (for default values or to use a specific version of the plugin), this is ignored by continuum. What do you think about externalize the release execution using external command line as you do to execute scheduled goals ? Is there any blocker issue so that it's not possible ? -- 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-1634) Normal build output should not be replaced by timeout stacktrace when build is timed out
Normal build output should not be replaced by timeout stacktrace when build is
timed out
Key: CONTINUUM-1634
URL: http://jira.codehaus.org/browse/CONTINUUM-1634
Project: Continuum
Issue Type: Bug
Affects Versions: 1.1
Reporter: Damien Lecan
When a build timeout is thrown, normal build output is replaced by an ugly and
unuseful stacktrace (see below).
Is it possible to keep the normal build output ? Is it available somewhere ?
Thanks
Stacktrace :
{code}
org.apache.maven.continuum.execution.ContinuumBuildCancelledException:
The build was cancelled
at
org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand(AbstractBuildExecutor.java:214)
at
org.apache.maven.continuum.execution.maven.m1.MavenOneBuildExecutor.build(MavenOneBuildExecutor.java:106)
at
org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute(ExecuteBuilderContinuumAction.java:118)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:408)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:147)
at
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error
while executing external command, process killed.
at
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:164)
at
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:89)
at
org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand(DefaultShellCommandHelper.java:114)
at
org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand(DefaultShellCommandHelper.java:59)
at
org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand(AbstractBuildExecutor.java:202)
... 11 more
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at java.lang.UNIXProcess.waitFor(UNIXProcess.java:165)
at
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:128)
{code}
--
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-1611) Continuum 1.1 won't authenticate a new issued user
[ http://jira.codehaus.org/browse/CONTINUUM-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121181 ] Wendy Smoak commented on CONTINUUM-1611: Another workaround is to click the 'Resend Validation' button, and have the user click the link in the resulting email. After that, they will be able to log in. > Continuum 1.1 won't authenticate a new issued user > -- > > Key: CONTINUUM-1611 > URL: http://jira.codehaus.org/browse/CONTINUUM-1611 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 > Environment: Windows 2003 Server, Maven 2.0.8, svn 1.4.3, Continuum > 1.1 Standalone >Reporter: Daniele De Francesco >Priority: Critical > Attachments: continuum.log, wrapper.20071220.log > > > When I create, as administrator, a new user and give him roles, if I logout > and then login back with the fresh created user I cannot access continuum, > because it complains that user/password are incorrect(!). I try then to > create a less powerful user, because I've read that in the past there was an > issue related to authentication and user profiles, but nothing, I then > decided to open the issue. > application log attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
