Tim Ellison wrote:
I think the immediate goal should be to make the 'security2' code a
replacement for 'security'.
Since security is part of the componentized-build bootstrapping code
(i.e. required to run the compiler in self-hosting mode) then we need
to
integrate the security2 build script with the classlib/make/build.xml.
I did the following 'quick integration' for my experiments (crypto and
x-net code go to security.jar and we don't compile native code for login
modules)
1) substitute code in modules/security/src/main with code from security2
2) update make/build-java.xml to compile all source files
3) append to depends/patternsets/security.txt
com/openintel/**/*
javax/crypto/*
javax/crypto/interfaces/*
javax/crypto/spec/*
javax/net/*
javax/net/ssl/*
4) cd make; ant
I couldn't run the test suites (the junit fork fails) so still
playing
with that.
To build and run unit tests I used the script from security2.
1) add to classpath jars: JUnit, BouncyCastle, JDT compiler
2) add to INCLUDE path to jni header files or exclude building native
libraries
3) update build.xml:
- specify Eclipse JDT compiler with "build.compiler" property
- do you 'minor tweak' for building tests (i.e. add
${java.home}/lib/boot to bootclasspath)
- uncomment exclude clause for tests that requires java.util.logging
package to be compiled
- for junit task: set timeout (cause some tests hang VM)and remove
prepending bootclasspath with security_alt.jar, crypto.jar and x_net.jar
4) set JAVA_HOME to %HY_DEPLOY%\jre
5) ant tests.run
If something unclear or you need more detailed info please let me know.
Thanks,
Stepan Mishura
Intel Middleware Products Division
-----Original Message-----
From: Tim Ellison [mailto:[EMAIL PROTECTED]
Sent: Friday, January 13, 2006 7:33 PM
To: harmony-dev@incubator.apache.org
Subject: Re: Experiments building security2
I think the immediate goal should be to make the 'security2' code a
replacement for 'security'.
Since security is part of the componentized-build bootstrapping code
(i.e. required to run the compiler in self-hosting mode) then we need
to
integrate the security2 build script with the classlib/make/build.xml.
Once that is building we can use the security2 code exclusively, and
merge across anything else from 'security' that is worth keeping,
before
retiring that module.
Some of the other issues below are interesting, but not blockers for
making the code usable:
Here's my prioritised list:
2. Resolving http://mail-archives.apache.org...
The security2 code contains more than the security component calls for
(there is some crypto and x-net code in there too!) This is great!
Let's split it up so that they build separately.
6. Something else
Then fix up the classlib/make/build.xml to build security2 code into
the
deploy layout, ensuring that the result passes all the tests.
4. Binding Jar verification to security2
5. Selecting one of Base64 de/encoders and ASN.1 de/encoders
Merging the code and getting to an integrated runtime.
1. Closing the issue with Javadocs and updating the sources
3. Renaming com.openintel packages
These are good to keep going, but not critical to ensuring we get the
best of both class library contributions workig together.
What do you think?
Regards,
Tim
Loenko, Mikhail Y wrote:
That is really good news. For the remaining issues we will try to
reproduce them and provide a fix.
The next steps could be:
1. Closing the issue with Javadocs and updating the sources according
to
the decision. (There might be both short-term and long-term
decisions,
like remove tags and provide something else)
2. Resolving
http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200512.mb
ox/[EMAIL PROTECTED]
om%3e
3. Renaming com.openintel packages to whatever we decide
4. Binding Jar verification to security2
5. Selecting one of Base64 de/encoders and ASN.1 de/encoders
6. Something else
Please let me know where my help would be useful.
Thanks,
Mikhail Loenko
Intel Middleware Products Division
-----Original Message-----
From: Tim Ellison [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 12, 2006 8:30 PM
To: harmony-dev
Subject: Experiments building security2
FYI I just tried using the Harmony classlib code (and IBM VM) to
build
'security2' with the existing security2 build scripts.
With a minor tweak(*) to the security2/make/build.xml to reflect the
layout of our deployment, I was able to successfully build security2
using only the class library code from Harmony.
This is good news, since it shows that the security2 component will
fit
into the existing classlib builds and maintain our 'self-hosting'
status
(i.e. no dependencies on another Java implementations after the
initial
bootstrap build).
This is what I ran:
set HY_DEPLOY=/harmony/enhanced/classlib/trunk/deploy
set HY_LIB=%HY_DEPLOY%/jre/lib/boot
set ANT_HOME=/apache-ant-1.6.5
set CLASSPATH=%HY_LIB%/kernel-stubs.jar;%HY_LIB%/luni.jar
set INCLUDE=%HY_DEPLOY%/include;%INCLUDE%
%HY_DEPLOY%\jre\bin\java.exe -cp %ANT_HOME%/lib/ant-launcher.jar
-Dant.home=%ANT_HOME%/lib/ant-launcher.jar
org.apache.tools.ant.launch.Launcher -lib %ANT_HOME%/lib
-Dbuild.compiler=org.eclipse.jdt.core.JDTCompilerAdapter
and it all built successfully :-)
I couldn't run the test suites (the junit fork fails) so still
playing
with that.
(*) Minor tweak was adding /boot to the end of the jre/lib directory
Index: build.xml
===================================================================
--- build.xml (revision 367403)
+++ build.xml (working copy)
@@ -298,7 +298,7 @@
<patternset refid="api.src.all"/>
<bootclasspath>
<pathelement path="${build.path}/classes"/>
- <fileset dir="${java.home}/lib">
+ <fileset dir="${java.home}/lib/boot">
<include name="*.jar"/>
</fileset>
</bootclasspath>
--
Tim Ellison ([EMAIL PROTECTED])
IBM Java technology centre, UK.
--
Tim Ellison ([EMAIL PROTECTED])
IBM Java technology centre, UK.
