[ http://jira.jboss.com/jira/browse/JBBUILD-69?page=comments#action_12356928 ]
Paul Gier commented on JBBUILD-69:
----------------------------------
Can I close this issue? It seems to be out of date.
> Decompose apache-commons component
> ----------------------------------
>
> Key: JBBUILD-69
> URL: http://jira.jboss.com/jira/browse/JBBUILD-69
> Project: JBoss Build System
> Issue Type: Task
> Components: Repository
> Reporter: Ryan Campbell
> Assigned To: Scott M Stark
> Fix For: JBossBuild-1.1.3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> The apache-commons module contains several independently versioned artifacts which should really be tracked as seperate components. Split up each artifact into its own component and move all projects away from the "mixed" legacy version. Once this is complete, delete the "mixed" version from the repository.
--
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/JBAOP-44?page=all ]
Kabir Khan updated JBAOP-44:
----------------------------
Fix Version/s: 2.0.0.alpha5
(was: 2.0.0.alpha4)
> document new ARGS features
> --------------------------
>
> Key: JBAOP-44
> URL: http://jira.jboss.com/jira/browse/JBAOP-44
> Project: JBoss AOP
> Issue Type: Task
> Affects Versions: 2.0.0.alpha1
> Reporter: Bill Burke
> Assigned To: Flavia Rainone
> Fix For: 2.0.0.alpha5
>
>
> Document typed argument access within aspects as well as the CurrentInvocation class.
--
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/JBAOP-43?page=all ]
Kabir Khan updated JBAOP-43:
----------------------------
Fix Version/s: 2.0.0.alpha5
(was: 2.0.0.alpha4)
> ThreadMetadata serialization
> ----------------------------
>
> Key: JBAOP-43
> URL: http://jira.jboss.com/jira/browse/JBAOP-43
> Project: JBoss AOP
> Issue Type: Feature Request
> Affects Versions: 2.0.0.alpha1
> Reporter: Bill Burke
> Assigned To: Bill Burke
> Fix For: 2.0.0.alpha5
>
>
> ThreadMetadata should be serialized separately and merged with remote ThreadMetaData.
--
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/JBAOP-6?page=all ]
Kabir Khan updated JBAOP-6:
---------------------------
Fix Version/s: 2.0.0.alpha5
(was: 2.0.0.alpha4)
> Compile time reweaving
> ----------------------
>
> Key: JBAOP-6
> URL: http://jira.jboss.com/jira/browse/JBAOP-6
> Project: JBoss AOP
> Issue Type: Feature Request
> Affects Versions: 2.0.0.alpha1
> Reporter: Bill Burke
> Assigned To: Bill Burke
> Fix For: 2.0.0.alpha5
>
>
> Support for compile time reweaving. Currently AOPC ignores a class that implements Advised
--
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/JBAOP-209?page=all ]
Kabir Khan updated JBAOP-209:
-----------------------------
Fix Version/s: 2.0.0.alpha5
(was: 2.0.0.alpha4)
> Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent.
> ------------------------------------------------------------------------------------
>
> Key: JBAOP-209
> URL: http://jira.jboss.com/jira/browse/JBAOP-209
> Project: JBoss AOP
> Issue Type: Feature Request
> Affects Versions: 1.3.5
> Reporter: Bill Burke
> Assigned To: Bill Burke
> Fix For: 2.0.0.alpha5
>
>
--
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/JBAOP-48?page=all ]
Kabir Khan updated JBAOP-48:
----------------------------
Fix Version/s: 2.0.0.alpha5
(was: 2.0.0.alpha4)
> serialization and Aspect scoping
> --------------------------------
>
> Key: JBAOP-48
> URL: http://jira.jboss.com/jira/browse/JBAOP-48
> Project: JBoss AOP
> Issue Type: Feature Request
> Affects Versions: 2.0.0.alpha1
> Reporter: Bill Burke
> Assigned To: Bill Burke
> Fix For: 2.0.0.alpha5
>
>
> Resolve rules when aspects are serialized that are attached on a per-instance basis.
--
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/JBAOP-226?page=all ]
Kabir Khan updated JBAOP-226:
-----------------------------
Fix Version/s: 2.0.0.alpha5
(was: 2.0.0.alpha4)
> Memory leaks (advanced)
> -----------------------
>
> Key: JBAOP-226
> URL: http://jira.jboss.com/jira/browse/JBAOP-226
> Project: JBoss AOP
> Issue Type: Task
> Affects Versions: 1.3.6
> Reporter: Kabir Khan
> Fix For: 2.0.0.alpha5
>
>
> Need to resolve memory leaks for
> * AOP with generated weaving (domain per class)
> * AOP in scoped deployments (domain per scoped classloader)
> * standalone jboss-aop.xml files deployed in jboss (we will probably need to make the advisor clear itself from the woven class if "empty" following a rebind, and have something in the woven code to repopulate the classadvisor when executing the joinpoints)
--
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/JBAOP-69?page=all ]
Kabir Khan updated JBAOP-69:
----------------------------
Fix Version/s: 2.0.0.alpha5
(was: 2.0.0.alpha4)
> InvocationResponse should catch/wrap exceptions
> -----------------------------------------------
>
> Key: JBAOP-69
> URL: http://jira.jboss.com/jira/browse/JBAOP-69
> Project: JBoss AOP
> Issue Type: Feature Request
> Affects Versions: 2.0.0.alpha1
> Reporter: Bill Burke
> Assigned To: Bill Burke
> Fix For: 2.0.0.alpha5
>
>
> InvocationResponse in dynamicInvoke should catch all thrown exceptions and stuff them into InvocationResponse.
> The "client" of dynamicInvoke should look in IR to see if an exception is in there and rethrow it. It should also set the response attachments of the invocation as well.
--
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