[jira] [Closed] (ACE-56) Cross IDE debugging solution

["Marcel Offermans (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Offermans closed ACE-56.
-------------------------------

    Resolution: Won't Fix

With the migration to Bndtools, we can use the Eclipse debugger without any extra effort. Just set breakpoints and debug the application.
                
> Cross IDE debugging solution
> ----------------------------
>
>                 Key: ACE-56
>                 URL: https://issues.apache.org/jira/browse/ACE-56
>             Project: ACE
>          Issue Type: Improvement
>            Reporter: Toni Menzel
>         Attachments: ACE-56-2.patch
>
>
> Ace is a complex system where short buid/test cycles are important.
> I have a small "instantlauncher" part that makes it possible to use dev-targets directly IDE. Because they are standalone Main Class, they can be started right away in any IDE.
> Benefits:
> - short dev cycle because it uses core/conf/<targetname>/ and its configuration information directly via inspection.
> So, for example a complete dev-server-webui launcher looks like this
> {code}
> public class DevServerWebUI
> {
>     public static void main( String[] args )
>         throws Exception
>     {
>         new DevelopmentLauncher().launch( new AceReactor( new TargetDescriptor()
>         {
>             public String targetName()
>             {
>                 return "dev-server-webui";
>             }
>             public String[] settingsOverwrite()
>             {
>                 return new String[]{
>                     "org.apache.ace.configurator.CONFIG_DIR=core/conf/" + targetName()
>                 };
>             }
>         }
>         )
>         );
>     }
> }
> {code}
> Because it uses bundles from core/deploy/bundles directly, redeploy cycle is minimal.
> Question: Is this of general use in ace or should i keep it for myself.
> The solution builds on top of the FrameworkFactory API from OSGI Core R4.2. So it does not contain any framework relevant compile references.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira