harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sian January (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HARMONY-5886) The well known policytool tool for Harmony
Date Wed, 02 Jul 2008 08:22:45 GMT

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

Sian January resolved HARMONY-5886.

       Resolution: Fixed
    Fix Version/s: 5.0M7

> The well known policytool tool for Harmony
> ------------------------------------------
>                 Key: HARMONY-5886
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5886
>             Project: Harmony
>          Issue Type: New Feature
>          Components: JDK
>         Environment: Should run in all environments.
>            Reporter: AndrĂ¡s Belicza
>            Assignee: Sian January
>            Priority: Minor
>             Fix For: 5.0M7
>         Attachments: modules 2008.06.28.patch, screenshot-1.jpg
>   Original Estimate: 672h
>  Remaining Estimate: 672h
> As part of the GSoC2008 I'm developing a new tool for Harmony: policytool
> My mentors are Sian January and Mark Hindess, probably they will handle this patch.
> This initial patch contains the first files of policytool.
> I checked out a part of Harmony project from the SVN repository from here:
> http://svn.apache.org/repos/asf/harmony/enhanced/jdktools/trunk
> Inside this I went into the modules/samsa folder, and added a new entry in the build.xml
so a new policytool.exe will be generated in the bin folder of the JDK/JRE.
> I put the files of policytool in a new package: org.apache.harmony.tools.policytool
> I created a Main.java file as needed for all tools which is the entry point of policytool.
> Much needs to be done until policytool can be used, but the version contained the attached
patch can be built and can be run.
> If we start it, it's main frame will appear with a menubar and a tabbed pane with 2 tabs:
the 2 editor panels. The first one will be the graphical editor panel which is yet to be implemented.
The second panel is the direct text editing which is basically done. We can use a text area
to edit the policy text and we can save it using the appropriate menu items. We can load existing
> During the development process I keep it important that the sources must be very easily
readable and well documented. For that I use rather small, understandable classes and I write
javadoc for all entity: to all classes, attributes, methods, method params, return values
> I'm just about to continue coding but wanted to submit a patch as soon as possible.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message