Reorganise security module layout
---------------------------------
Key: HARMONY-147
URL: http://issues.apache.org/jira/browse/HARMONY-147
Project: Harmony
Type: Improvement
Components: Classlib
Environment: All
Reporter: George Harley
Priority: Minor
Lay out the modules/security contents to look more like the other peer modules
such as archive, luni etc. In particular, place the source into a layout like
below to clearly distinguish implementation code from test code and common code
from native code ...
<SECURITY ROOT>
|
|
+---src
| |
| +---main
| | |
| | +---java
| | | |
| | | +---common
| | | |
| | | +---linux
| | | |
| | | \---win
| | |
| | +---native
| | | |
| | | +---linux
| | | |
| | | \---win
| | |
| | \---resources
| | |
| | \---common
| |
| +---test
| |
| +---java
| |
| +---common
| |
| +---linux
| |
| \---win
|
+---doc
| |
| \---images
|
+---make
| |
| \---native
| |
| +---linux
| |
| \---windows
|
+---META-INF
I've previously asked for comments about this proposal on the list and adopted
some changes to the original naming convention. No one objected in principle to
the objective of bringing the layout into line with the other modules.
In addition, this layout lends itself very nicely to importing the
modules/security folder into an IDE such as Eclipse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
