[JBoss JIRA] (GTNPORTAL-2931) the portal-testsuite-htmlunit-tests artifact couldn't be deployed properly in release process
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2931?page=com.atlassian.jira.pl... ]
Trong Tran commented on GTNPORTAL-2931:
---------------------------------------
it is because of the portal-testsuite-htmlunit-tests artifact doesn't refer to its parent pom *org.gatein.portal:exo.portal.testsuite* which defines the deployment information.
> the portal-testsuite-htmlunit-tests artifact couldn't be deployed properly in release process
> ---------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2931
> URL: https://issues.jboss.org/browse/GTNPORTAL-2931
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.3.Final, 3.6.0.Beta01
> Reporter: Trong Tran
> Labels: portal-s70
> Fix For: 3.6.0.Beta02
>
>
> There is following failure with portal-testsuite-htmlunit-tests artifact while performing release process :
> [INFO] [INFO] Selenium Sniff Test for GateIn .................... SUCCESS [1.387s]
> [INFO] [INFO] GateIn Portal Examples - WebUI based samples ...... SUCCESS [2.632s]
> [INFO] [INFO] HTMLUnit Tests for GateIn ......................... FAILURE [0.773s]
> [INFO] [INFO] Selenium UI Tests for GateIn ...................... SKIPPED
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 18:05.320s
> [INFO] [INFO] Finished at: Thu Apr 11 12:39:39 CEST 2013
> [INFO] [INFO] Final Memory: 144M/482M
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project portal-testsuite-htmlunit-tests: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [INFO] [ERROR]
> [INFO] [ERROR] After correcting the problems, you can resume the build with the command
> [INFO] [ERROR] mvn <goals> -rf :portal-testsuite-htmlunit-tests
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (GTNPORTAL-2931) the portal-testsuite-htmlunit-tests artifact couldn't be deployed properly in release process
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2931?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2931:
----------------------------------
Labels: portal-s70 (was: )
> the portal-testsuite-htmlunit-tests artifact couldn't be deployed properly in release process
> ---------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2931
> URL: https://issues.jboss.org/browse/GTNPORTAL-2931
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.3.Final, 3.6.0.Beta01
> Reporter: Trong Tran
> Labels: portal-s70
> Fix For: 3.6.0.Beta02
>
>
> There is following failure with portal-testsuite-htmlunit-tests artifact while performing release process :
> [INFO] [INFO] Selenium Sniff Test for GateIn .................... SUCCESS [1.387s]
> [INFO] [INFO] GateIn Portal Examples - WebUI based samples ...... SUCCESS [2.632s]
> [INFO] [INFO] HTMLUnit Tests for GateIn ......................... FAILURE [0.773s]
> [INFO] [INFO] Selenium UI Tests for GateIn ...................... SKIPPED
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 18:05.320s
> [INFO] [INFO] Finished at: Thu Apr 11 12:39:39 CEST 2013
> [INFO] [INFO] Final Memory: 144M/482M
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project portal-testsuite-htmlunit-tests: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [INFO] [ERROR]
> [INFO] [ERROR] After correcting the problems, you can resume the build with the command
> [INFO] [ERROR] mvn <goals> -rf :portal-testsuite-htmlunit-tests
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (GTNPORTAL-2931) the portal-testsuite-htmlunit-tests artifact couldn't be deployed properly in release process
by Trong Tran (JIRA)
Trong Tran created GTNPORTAL-2931:
-------------------------------------
Summary: the portal-testsuite-htmlunit-tests artifact couldn't be deployed properly in release process
Key: GTNPORTAL-2931
URL: https://issues.jboss.org/browse/GTNPORTAL-2931
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.6.0.Beta01, 3.5.3.Final
Reporter: Trong Tran
Fix For: 3.6.0.Beta02
There is following failure with portal-testsuite-htmlunit-tests artifact while performing release process :
[INFO] [INFO] Selenium Sniff Test for GateIn .................... SUCCESS [1.387s]
[INFO] [INFO] GateIn Portal Examples - WebUI based samples ...... SUCCESS [2.632s]
[INFO] [INFO] HTMLUnit Tests for GateIn ......................... FAILURE [0.773s]
[INFO] [INFO] Selenium UI Tests for GateIn ...................... SKIPPED
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 18:05.320s
[INFO] [INFO] Finished at: Thu Apr 11 12:39:39 CEST 2013
[INFO] [INFO] Final Memory: 144M/482M
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project portal-testsuite-htmlunit-tests: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO] [ERROR]
[INFO] [ERROR] After correcting the problems, you can resume the build with the command
[INFO] [ERROR] mvn <goals> -rf :portal-testsuite-htmlunit-tests
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
by Minh Hoang TO (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl... ]
Work on GTNPORTAL-2710 started by Minh Hoang TO.
> Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
> ---------------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2710
> URL: https://issues.jboss.org/browse/GTNPORTAL-2710
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Stian Thorgersen
> Assignee: Minh Hoang TO
> Labels: portal-s70
> Fix For: 3.6.0.Beta02
>
>
> If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the context is not removed from ChromatticLifeCycle#currenctContext. This is caused by AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is thrown.
> This can be reproduced by running test specified in GTNPORTAL-2711. When this test is run the first test fails with the failure specified in that JIRA issue. However, the rest of the tests fails with the failure in this issue.
> Stack trace:
> {code}
> org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: This kind of operation is forbidden after a session.logout().
> at org.chromattic.core.DomainSession.findByPath(DomainSession.java:199)
> at org.chromattic.core.api.ChromatticSessionImpl.findByPath(ChromatticSessionImpl.java:228)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.getGadgetTokenContainer(GadgetTokenInfoService.java:149)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:55)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:1)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.execute(GadgetTokenInfoService.java:165)
> at org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:54)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:59)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testSize(TestGadgetTokenInfoService.java:117)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: javax.jcr.RepositoryException: This kind of operation is forbidden after a session.logout().
> at org.exoplatform.services.jcr.impl.core.SessionImpl.checkLive(SessionImpl.java:917)
> at org.exoplatform.services.jcr.impl.core.SessionImpl.getRootNode(SessionImpl.java:760)
> at org.chromattic.core.DomainSessionImpl._getRoot(DomainSessionImpl.java:809)
> at org.chromattic.core.DomainSessionImpl._findByPath(DomainSessionImpl.java:115)
> at org.chromattic.core.DomainSession.findByPath(DomainSession.java:196)
> ... 29 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
by Minh Hoang TO (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl... ]
Minh Hoang TO reassigned GTNPORTAL-2710:
----------------------------------------
Assignee: Minh Hoang TO (was: Julien Viet)
> Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
> ---------------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2710
> URL: https://issues.jboss.org/browse/GTNPORTAL-2710
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Stian Thorgersen
> Assignee: Minh Hoang TO
> Labels: portal-s70
> Fix For: 3.6.0.Beta02
>
>
> If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the context is not removed from ChromatticLifeCycle#currenctContext. This is caused by AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is thrown.
> This can be reproduced by running test specified in GTNPORTAL-2711. When this test is run the first test fails with the failure specified in that JIRA issue. However, the rest of the tests fails with the failure in this issue.
> Stack trace:
> {code}
> org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: This kind of operation is forbidden after a session.logout().
> at org.chromattic.core.DomainSession.findByPath(DomainSession.java:199)
> at org.chromattic.core.api.ChromatticSessionImpl.findByPath(ChromatticSessionImpl.java:228)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.getGadgetTokenContainer(GadgetTokenInfoService.java:149)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:55)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:1)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.execute(GadgetTokenInfoService.java:165)
> at org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:54)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:59)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testSize(TestGadgetTokenInfoService.java:117)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: javax.jcr.RepositoryException: This kind of operation is forbidden after a session.logout().
> at org.exoplatform.services.jcr.impl.core.SessionImpl.checkLive(SessionImpl.java:917)
> at org.exoplatform.services.jcr.impl.core.SessionImpl.getRootNode(SessionImpl.java:760)
> at org.chromattic.core.DomainSessionImpl._getRoot(DomainSessionImpl.java:809)
> at org.chromattic.core.DomainSessionImpl._findByPath(DomainSessionImpl.java:115)
> at org.chromattic.core.DomainSession.findByPath(DomainSession.java:196)
> ... 29 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (GTNPORTAL-2930) Portal keep session alive property values are confusing
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2930?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration updated GTNPORTAL-2930:
-----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=952274
> Portal keep session alive property values are confusing
> -------------------------------------------------------
>
> Key: GTNPORTAL-2930
> URL: https://issues.jboss.org/browse/GTNPORTAL-2930
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta01
> Reporter: Dominik Pospisil
>
> According to documentation, portal "keep seesion alive" property values meaning are as follows:
> never - The session will never timeout, even if an application requests it.
> On-demand - The session will timeout if an application requests it
> Always - The session will time out after a set period
> This is quite confusing. E.g. keep session alive never actually means to keep session alive forever.
> Keep session alive always means to let the session timeout automatically.
> If the documentation is correct, the name of the property or property values should be changed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (GTNPORTAL-2930) Portal keep session alive property values are confusing
by Dominik Pospisil (JIRA)
Dominik Pospisil created GTNPORTAL-2930:
-------------------------------------------
Summary: Portal keep session alive property values are confusing
Key: GTNPORTAL-2930
URL: https://issues.jboss.org/browse/GTNPORTAL-2930
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.6.0.Beta01
Reporter: Dominik Pospisil
According to documentation, portal "keep seesion alive" property values meaning are as follows:
never - The session will never timeout, even if an application requests it.
On-demand - The session will timeout if an application requests it
Always - The session will time out after a set period
This is quite confusing. E.g. keep session alive never actually means to keep session alive forever.
Keep session alive always means to let the session timeout automatically.
If the documentation is correct, the name of the property or property values should be changed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months