DeploymentInfo.getManifest() does close the JarFile it uses to read the Manifest of a jarred deployment
-------------------------------------------------------------------------------------------------------
Key: JBAS-6266
URL: https://jira.jboss.org/jira/browse/JBAS-6266
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.2.3.GA
Reporter: Ian Springer
Priority: Minor
This is bad because if getManifest() is called on a Windows system, the deployment jarfile will end up locked. A patch to fix this is attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Change cache factory tests to better handle cache instances
-----------------------------------------------------------
Key: JBMDR-54
URL: https://jira.jboss.org/jira/browse/JBMDR-54
Project: JBoss MetaData Repository
Issue Type: Task
Components: MetaData
Reporter: Ales Justin
Assignee: Ales Justin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Track jboss and thirdparty dependencies upgrades for JBoss 5.0.0.GA
-------------------------------------------------------------------
Key: JBAS-5597
URL: http://jira.jboss.com/jira/browse/JBAS-5597
Project: JBoss Application Server
Issue Type: Thirdparty Change
Security Level: Public (Everyone can see)
Components: Other
Reporter: Dimitris Andreadis
Assigned To: Dimitris Andreadis
Priority: Critical
Fix For: JBossAS-5.0.0.GA
Track AS5.0.0.GA component updates
--
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
Add tests for restart of server to validate profileservice overrides are applied
--------------------------------------------------------------------------------
Key: JBAS-6036
URL: https://jira.jboss.org/jira/browse/JBAS-6036
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Deployers, ProfileService
Affects Versions: JBossAS-5.0.0.CR2
Reporter: Scott M Stark
Assignee: Emanuel Muckenhuber
Fix For: JBossAS-5.0.0.GA
We need a ProfileServiceOverridesTestCase test that validates that admin changes made to deployments are seen when the server is restarted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Restore ProfileService attachments persistence
----------------------------------------------
Key: JBAS-6037
URL: https://jira.jboss.org/jira/browse/JBAS-6037
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Scott M Stark
Assignee: Emanuel Muckenhuber
Fix For: JBossAS-5.0.0.GA
Somewhere during refactorings we lost the aspects there were intercepting ManagedObject/ManagedProperty updates and writing out the attachments to the profile service repository. This needs to be restored.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Release JBoss Deployers 2.0.3.GA
--------------------------------
Key: JBDEPLOY-148
URL: https://jira.jboss.org/jira/browse/JBDEPLOY-148
Project: JBoss Deployers
Issue Type: Release
Components: release
Affects Versions: JBDEPLOY-2.0.1.GA
Reporter: Ales Justin
Assignee: Ales Justin
Fix For: JBDEPLOY-2.0.3.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
AbstractDeploymentClassLoaderPolicyModule is not removing alias
---------------------------------------------------------------
Key: JBDEPLOY-137
URL: https://jira.jboss.org/jira/browse/JBDEPLOY-137
Project: JBoss Deployers
Issue Type: Bug
Components: classloading
Reporter: Ales Justin
Assignee: Ales Justin
Fix For: JBDEPLOY-2.0.0.GA
We should remove alias from Controller if it was added.
Aliases only get unwind when original is uninstalled,
they must be explicitly uninstalled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Update to jboss-microcontainer 2.0.2.GA
---------------------------------------
Key: JBDEPLOY-149
URL: https://jira.jboss.org/jira/browse/JBDEPLOY-149
Project: JBoss Deployers
Issue Type: Thirdparty Change
Components: release
Affects Versions: JBDEPLOY-2.0.1.GA
Reporter: Ales Justin
Assignee: Ales Justin
Fix For: JBDEPLOY-2.0.3.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Create version of GenericBeanFactory that allows overriding the classloader used by createBean
----------------------------------------------------------------------------------------------
Key: JBMICROCONT-400
URL: https://jira.jboss.org/jira/browse/JBMICROCONT-400
Project: JBoss Microcontainer
Issue Type: Feature Request
Components: AOP
Reporter: Kabir Khan
Assignee: Kabir Khan
Fix For: JBossMC-2.0.2.GA , JBossMC-2.2.0.Beta1
This is needed since the classloader required to create the aspect instances may be different from the classloader used to deploy the bean factory
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira