[
https://issues.jboss.org/browse/FORGE-796?page=com.atlassian.jira.plugin....
]
Matt Benson commented on FORGE-796:
-----------------------------------
Interested parties please see
https://github.com/forge/java-parser/tree/refactor-hierarchy
where the proposed API for java-parser v2 is under construction; the basic overview of
changes is:
* extract read functionality from {{JavaSource}} to a new {{JavaType}} interface
* {{JavaSource}} moved to package {{org.jboss.forge.parser.java.source}}
* for a given interface {{org.jboss.forge.parser.java.*}}, extract write functionality to
{{org.jboss.forge.parser.java.source.*Source}}
e.g., {{org.jboss.forge.parser.java.JavaClass}} now contains read functionality only and
{{org.jboss.forge.parser.java.source.JavaClassSource}} is now the equivalent of the old RW
interface.
Additionally the {{JavaParserProvider}} interface has been greatly simplified and the
{{JavaParser}} API entry-point has been modified to use {{java.util.ServiceLoader}} and
take over the input overloading duties that were formerly the responsibility of a
{{JavaParserProvider}} implementation.
Refactor JavaParser to distinguish between Mutable and Immutable Type
Models in a typesafe way
----------------------------------------------------------------------------------------------
Key: FORGE-796
URL:
https://issues.jboss.org/browse/FORGE-796
Project: Forge
Issue Type: Feature Request
Components: Parsers / File Manipulation
Reporter: Lincoln Baxter III
Assignee: Matt Benson
Fix For: 2.0.0.Final
The Java Parser Type Hierarchy should support Read-only and writeable Types. Thus we
could implement the Parser using things like Java Reflection for Read-only access, or with
Javassist CtClass / Apache BCEL for reading and writing .class files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira