[
https://jira.jboss.org/jira/browse/DNA-62?page=com.atlassian.jira.plugin....
]
Randall Hauch commented on DNA-62:
----------------------------------
Nice work.
On first blush, it could sense to put both the classfile and source sequencers in the same
project. However, that would mean that if you just wanted a Java classfile sequencer,
you'd have to depend on the Eclipse Java parser (which has more than a few
dependencies). It's not horrible, and I wonder how many people would use one
sequencer and not the other.
Another option is to have the Java source sequencer depend on the Java classfile
sequencer, since the former has a lot more (transitive) dependencies, and since the latter
only has a few.
A third option is to move the general reader code to a separate module, and to have both
sequencer depend on it. This is my least favorite.
Sequence Java class files to extract the class structure with
annotations
-------------------------------------------------------------------------
Key: DNA-62
URL:
https://jira.jboss.org/jira/browse/DNA-62
Project: DNA
Issue Type: Feature Request
Components: Sequencers
Reporter: Randall Hauch
Assignee: Brian Carothers
Fix For: 1.1
Attachments: DNA-62_draft.patch
This use case comes from a discussion about starting up the Microcontainer, and the
desire to have a single processor of the JAR files to extract into a centralized
repository the runtime annotations. Right now the annotations are scanned by each
component/service that needs them. This feature would obviate the scanning being done by
each component/service.
Consider using
http://scannotation.sourceforge.net/ for doing the actual scanning.
--
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