)
This requires a peer integration at the classloader and security
level.
--
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
getAttribute(String name);
}
ModuleDefinition still refers to exported and member classes.
Although this is probably more of an issue for 294/291 interoperation,
I don't think 291 has such notions?
--
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
sense to be able to do this by hand.
This proposal is an attempt to maintain the convenience while adding the
crucial ability to safely refactor: step 1b is the central idea.
// Bryan
--
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
is an attempt to maintain the convenience while adding the
crucial ability to safely refactor: step 1b is the central idea.
// Bryan
--
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
obviously enables new subtypes, an extensibility point
that may come in handy in the future.
// Bryan
--
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
On Wed, 2008-06-11 at 22:31 -0700, Stanley M. Ho wrote:
Hi Adrian,
Adrian Brock wrote:
My critisms of using the JSR277 repositories to do the integration
included:
I want to better understand your concerns around developing
repositories, since I believe some of your concerns have
it otherwise it might be stale.
This is all so I can enable use the tools that come with the
JDK repository implementation and possibly other behaviour
like Bryan's resolving Module imports to Package imports.
--
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
with tooling.
The old, A tool will solve the complexity problem opt out. ;-)
--
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
--
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
