ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Toni Menzel (JIRA)" <j...@apache.org>
Subject [jira] Created: (ACE-56) Cross IDE debugging solution
Date Fri, 16 Oct 2009 19:11:31 GMT
Cross IDE debugging solution
----------------------------

                 Key: ACE-56
                 URL: https://issues.apache.org/jira/browse/ACE-56
             Project: Ace
          Issue Type: Improvement
            Reporter: Toni Menzel


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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message