[
https://issues.apache.org/jira/browse/LABS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676924#action_12676924
]
Simone Gianni commented on LABS-281:
------------------------------------
Investigate the use if JCI for this and it's reloading classloader, wether it's
possible to use it to pipeline different enhancement steps triggered by
just-in-time recompilation of java and aspectj files.
> [build] RAD for java files
> --------------------------
>
> Key: LABS-281
> URL: https://issues.apache.org/jira/browse/LABS-281
> Project: Labs
> Issue Type: New Feature
> Components: Magma
> Affects Versions: Current
> Reporter: Simone Gianni
> Assignee: Simone Gianni
> Fix For: Future
>
>
> While for resources, during a magma:run, it is possible to use magma.locals
> to have them automatically taken from their folder, and avoid rebuilding, no
> such a system is in place for java files. Moreover, LTW does not support
> debug class replacement.
> If Eclipse was able to build packages correctly (including weaving etc..)
> then it would be enough to load classes from there, similarly to
> magma.locals, scan for changes and reload if necessary (which is already
> built in with jetty).
> Since that is not the case yet, we could apply magma.locals to target/classes
> folders and scan those folders instead, so that rebuilding the target package
> could be enough. But still this method would require a different shell.
> Monitoring .java class changes and triggering Maven compile could also be
> possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
