You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "András Belicza (JIRA)" <ji...@apache.org> on 2008/06/28 20:59:45 UTC
[jira] Created: (HARMONY-5886) The well known policytool tool for
Harmony
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
Priority: Minor
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 files.
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 etc.
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.
[jira] Commented: (HARMONY-5886) The well known policytool tool for
Harmony
Posted by "András Belicza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609279#action_12609279 ]
András Belicza commented on HARMONY-5886:
-----------------------------------------
Yes that's right. I've found out about that too after I made the patch. It's already fixed on my computer. Next patch will contain the fix.
> 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
> 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 files.
> 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 etc.
> 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.
[jira] Updated: (HARMONY-5886) The well known policytool tool for
Harmony
Posted by "András Belicza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
András Belicza updated HARMONY-5886:
------------------------------------
Attachment: modules 2008.06.28.patch
This is the initial patch for policytool.
> 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
> Priority: Minor
> Attachments: modules 2008.06.28.patch
>
> 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 files.
> 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 etc.
> 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.
[jira] Updated: (HARMONY-5886) The well known policytool tool for
Harmony
Posted by "András Belicza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
András Belicza updated HARMONY-5886:
------------------------------------
Attachment: screenshot-1.jpg
This is how policytool looked like on June 15, 2008.
> 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
> Priority: Minor
> 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 files.
> 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 etc.
> 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.
[jira] Resolved: (HARMONY-5886) The well known policytool tool for
Harmony
Posted by "Sian January (JIRA)" <ji...@apache.org>.
[ 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 files.
> 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 etc.
> 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.
[jira] Closed: (HARMONY-5886) The well known policytool tool for
Harmony
Posted by "Sian January (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sian January closed HARMONY-5886.
---------------------------------
> 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 files.
> 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 etc.
> 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.
[jira] Assigned: (HARMONY-5886) The well known policytool tool for
Harmony
Posted by "Sian January (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sian January reassigned HARMONY-5886:
-------------------------------------
Assignee: Sian January
> 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
> 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 files.
> 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 etc.
> 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.
[jira] Commented: (HARMONY-5886) The well known policytool tool for
Harmony
Posted by "Sian January (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609259#action_12609259 ]
Sian January commented on HARMONY-5886:
---------------------------------------
Initial patch applied at r672793.
Andras - your code looks good and I tried the tool out and it's a good start, but at the moment it only works for me if you specify a file name on the command line. I've applied the patch because I think it's fine given that it's a work in progress, but the error I see if I don't specify a filename is as follows:
Exception in thread "main" java.lang.NullPointerException
at java.io.File.fixSlashes(File.java:262)
at java.io.File.<init>(File.java:124)
at org.apache.harmony.tools.policytool.control.Controller.<init>(Control
ler.java:66)
at org.apache.harmony.tools.policytool.view.MainFrame.<init>(MainFrame.j
ava:53)
at org.apache.harmony.tools.policytool.view.MainFrame.<init>(MainFrame.j
ava:42)
at org.apache.harmony.tools.policytool.Main.main(Main.java:40)
> 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
> 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 files.
> 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 etc.
> 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.