[ http://jira.jboss.com/jira/browse/JBAS-1768?page=all ]
Ryan Campbell reassigned JBAS-1768:
-----------------------------------
Assignee: Pavel Tsekov (was: Ryan Campbell)
> Isolating the test harness
> --------------------------
>
> Key: JBAS-1768
> URL: http://jira.jboss.com/jira/browse/JBAS-1768
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Reporter: Adrian Brock
> Assigned To: Pavel Tsekov
> Fix For: JBossAS-4.2.1.CR1
>
>
> Since some projects are already using the test harness
> org.jboss.test (from the testsuite)
> this needs to be isolated to break the circular build dependency.
> Additionally, we should look at making this available to users
> 1) For their own use
> 2) When reporting problems
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Testsuite failures for MalformedTestCase testMalformed test with a 1.5.0 JVM
----------------------------------------------------------------------------
Key: JBAS-3549
URL: http://jira.jboss.com/jira/browse/JBAS-3549
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.0.4.GA
Environment: Sun 1.5.0_08 JVM
RHEL 4, Linux Kernel 2.6.9
Reporter: Matt Wringe
The org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase testMalformed test fails when using the Sun 1.5.0 JVM.
>From the test report:
"invalid object name: domain:=,foo=bar
junit.framework.AssertionFailedError: invalid object name: domain:=,foo=bar
at org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase$FullNameTEST.testMalformed(MalformedTestCase.java:152)"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBAS-2831?page=all ]
Anil Saldhana updated JBAS-2831:
--------------------------------
JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=88989&start=10
> Allow run-as indentity propagation across servers with configurable trust
> -------------------------------------------------------------------------
>
> Key: JBAS-2831
> URL: http://jira.jboss.com/jira/browse/JBAS-2831
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: JBossAS-4.0.4RC1
> Reporter: Scott M Stark
> Assigned To: Anil Saldhana
> Fix For: JBossAS-5.0.1.CR1
>
>
> Look to provide propagation of the run-as identity across server calls with control over how the target server trusts this call is correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Document CMS Security in User Guide
-----------------------------------
Key: JBPORTAL-1165
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1165
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal Documentation
Affects Versions: 2.6.Alpha1
Reporter: Roy Russo
Assigned To: Roy Russo
Fix For: 2.6.Alpha1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Need to expand the jmx console tests to validate accessing the jdk mbeans
-------------------------------------------------------------------------
Key: JBAS-3951
URL: http://jira.jboss.com/jira/browse/JBAS-3951
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Scott M Stark
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBAS-1770?page=all ]
Ryan Campbell reassigned JBAS-1770:
-----------------------------------
Assignee: Pavel Tsekov
> Enabling the testsuite to be used by users
> ------------------------------------------
>
> Key: JBAS-1770
> URL: http://jira.jboss.com/jira/browse/JBAS-1770
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Reporter: Adrian Brock
> Assigned To: Pavel Tsekov
>
> The testsuite should be available for users to use.
> e.g. by including it in JBOSS_DIST/client or JBOSS_DIST/test???
> Other enhancements might include:
> * Using JSR88 for deployment
> * Using JSR160 for the MBeanServerConnection
> * Exposing functionality available on the admin console
> To help users provide better bug reports we should also
> provide skeleton tests that the user can "extend".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBAS-2823?page=all ]
Dimitris Andreadis updated JBAS-2823:
-------------------------------------
Summary: Upgrade commons-logging to v1.1 (was: Upgrade commons-logging to Release 1.1.0)
> Upgrade commons-logging to v1.1
> -------------------------------
>
> Key: JBAS-2823
> URL: http://jira.jboss.com/jira/browse/JBAS-2823
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Logging
> Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1
> Environment: Windows XP Professional, JDK 1.5.0
> Reporter: Martin Lui
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-4.2.0.CR1
>
>
> The Apache commons-logging package has release version 1.1.0.
> Please upgrade this library to take advantage of items listed in the release notes:
> http://jakarta.apache.org/commons/logging/RELEASE-NOTES.txt
> It would be helpful if this upgrade can be done to upgrade the server libraries since individual EAR files cannot overwrite this particular library.
> Also, looking through the notes and searching for information on the 1.0.4 patch, it appears that the WeakHashTables memory-leak fix is included in 1.1.0. (Bug 31286: http://issues.apache.org/bugzilla/show_bug.cgi?id=31286)
> Depending on how JBoss uses this package, upgrading should be as simple as replacing the current package (though I admit I had not try doing so yet).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBAS-2823?page=all ]
Dimitris Andreadis closed JBAS-2823.
------------------------------------
Resolution: Done
Upgraded on Branch_4_2.
If there are any issues, please re-open the task.
> Upgrade commons-logging to v1.1
> -------------------------------
>
> Key: JBAS-2823
> URL: http://jira.jboss.com/jira/browse/JBAS-2823
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Logging
> Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1
> Environment: Windows XP Professional, JDK 1.5.0
> Reporter: Martin Lui
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-4.2.0.CR1
>
>
> The Apache commons-logging package has release version 1.1.0.
> Please upgrade this library to take advantage of items listed in the release notes:
> http://jakarta.apache.org/commons/logging/RELEASE-NOTES.txt
> It would be helpful if this upgrade can be done to upgrade the server libraries since individual EAR files cannot overwrite this particular library.
> Also, looking through the notes and searching for information on the 1.0.4 patch, it appears that the WeakHashTables memory-leak fix is included in 1.1.0. (Bug 31286: http://issues.apache.org/bugzilla/show_bug.cgi?id=31286)
> Depending on how JBoss uses this package, upgrading should be as simple as replacing the current package (though I admit I had not try doing so yet).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira