Support exclude=* in order to just include some package in current project
--------------------------------------------------------------------------
Key: JBAOP-516
URL: http://jira.jboss.com/jira/browse/JBAOP-516
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.CR3
Reporter: Carlos XXXXX
It's a common use case to exclude everything from being adviced except for the classes in my current project. I can't see a simple way to do this with a combination of exclude/include, because exclude must explicitly list packages to be excluded, which are the majority. I think that if exclude is not given but include is, or if exclude is given an * value, only packages and classes listed under include should be taken into account.
--
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
maven-jbossaop-plugin to run java with aop options
--------------------------------------------------
Key: JBAOP-520
URL: http://jira.jboss.com/jira/browse/JBAOP-520
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Aspect Library
Reporter: Stale Pedersen
Assigned To: Stale Pedersen
Fix For: 2.0.0.GA
we need a plugin that can easily run aop apps with the proper settings
--
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
Use MetaData.isMetaDataPresent() instead of MetaData.isAnnotationPresent()
--------------------------------------------------------------------------
Key: JBAOP-526
URL: http://jira.jboss.com/jira/browse/JBAOP-526
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Kabir Khan
Assigned To: Kabir Khan
Fix For: 2.0.0.GA
--
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
Fix bug when double-weaving existing javaassist proxies
-------------------------------------------------------
Key: JBAOP-528
URL: http://jira.jboss.com/jira/browse/JBAOP-528
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Stale Pedersen
Assigned To: Stale Pedersen
Fix For: 2.0.0.GA
Weaved classes thats proxied with javassist and then again transformed with aop fails.
--
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
Increase performance of annotation parsing
------------------------------------------
Key: JBAOP-532
URL: http://jira.jboss.com/jira/browse/JBAOP-532
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Stale Pedersen
Assigned To: Stale Pedersen
Fix For: 2.0.0.GA
--
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
JBoss AOP ignore classes packaged in org.jboss.aop, it should be org.jboss.aop.
-------------------------------------------------------------------------------
Key: JBAOP-534
URL: http://jira.jboss.com/jira/browse/JBAOP-534
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Stale Pedersen
Assigned To: Stale Pedersen
Fix For: 2.0.0.GA
--
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
Restricting scanning for ejbs
-----------------------------
Key: EJBTHREE-1208
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1208
Project: EJB 3.0
Issue Type: Feature Request
Components: core
Affects Versions: AS 5.0.0.Beta4
Reporter: Scott M Stark
Fix For: AS 5.0.0.CR1
The Ejb3Deployment needs a flag to control whether wars are scanned in deployUrl
--
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
SVN Work for 2.0.0.CR1
----------------------
Key: JBREFLECT-20
URL: http://jira.jboss.com/jira/browse/JBREFLECT-20
Project: JBoss Reflection
Issue Type: Sub-task
Components: Release
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossReflection.2.0.0.Beta11
**Move** the metadata repository code from the Microcontainer project to its own top level project.
Create a branch for 2.0.x and tag 2.0.0.CR1
--
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