OpenSAML user discussion

[Brent Putman <>]

I think I already mentioned this awhile back, but some/all of the build 
errors here were due to the presence of the removed ElementProxy stuff 
in one of those configs and some other isssues, now since corrected.  I 
just wanted to note that you shouldn't have to modify the build.xml any 
more (unless you  just want to).

I did take your suggestion and modify the java-xmltooling build.xml to 
include logback jars in the "test-path" class path.

I believe the only thing outstanding is cross project dependencies, I'll 
follow up on that in a second.

--Brent


Clifford Johnson wrote:
> I'm trying to build a recent checkout of the OpenSAML2 libraries and am
> having difficulties getting most of the JUnit tests to run on
> java-xmltooling.  I'm not using Eclipse to run this - I'm relying solely
> on ANT.  It would appear that most (if not all) of the failures are the
> result of having an incomplete xmltooling configuration.  Since I'm
> making no modifications to xmltooling, I was expecting the
> xmltooling-config.xml file under trunk\test (and its cohorts) to have
> everything needed to run the JUnit tests -- appears not to be the case.
>
> In an attempt to get things working, I made a few changes to the
> build.xml file in an attempt to get what I believe I need:
>
> 1) To the "compile-test" target, I added:
>
>      <copy todir="${test-classes.dir}/data">
>          <fileset dir="${test-src.dir}/data"/>
>      </copy>
>
>      <copy toDir="${test-classes.dir}">
>          <fileset dir="${test-src.dir}">
>              <include name="*.xml"/>
>          </fileset>
>      </copy>
>
>    which (I hope) copies all of the test configuration data files to the
>    test classes directory
>
>
> 2) I changed "test-path" to read: 
>
>     <path id="test-path">
>         <pathelement location="${core-classes.dir}" />
>         <!--<pathelement location="${core-src.dir}" />-->
>         <pathelement location="${test-classes.dir}" />
>         <pathelement location="${classpathres.dir}" />
>         <!--<pathelement location="${test-classes.dir}/data" />-->
>         <!--<pathelement location="${test-classes.dir}/log4j.xml" />-->
>         <!--<pathelement location="${test-src.dir}" />-->
>         <path refid="build-path" />
>         <fileset dir="${thirdpaty-lib.dir}">
>             <include name="slf4j/logback-classic-0.9.8.jar"/>
>             <include name="slf4j/logback-core-0.9.8.jar"/>
>         </fileset>
>     </path>
>
>    This more closely reflects what appears in the Eclipse .classpath 
>    Configuration file.  (The above gives me a CLASSPATH that contains:
>
>       build\core;
>       build\test;
>       resources\classpath;
>       build-lib\ant-1.6.5-junit.jar;
>       build-lib\ant-1.6.5-launcher.jar;
>       build-lib\ant-1.6.5-nodeps.jar;
>       build-lib\ant-1.6.5.jar;
>       build-lib\ant-contrib-1.0b2.jar;
>       build-lib\checkstyle-all-4.2.jar;
>       build-lib\junit-3.8.1.jar;
>       build-lib\xmlunit-1.0.jar;
>       lib\bcprov-jdk14-138.jar;
>       lib\jcl104-over-slf4j-1.4.3.jar;
>       lib\joda-time-1.5.1.jar;
>       lib\log4j-over-slf4j-1.4.3.jar;
>       lib\not-yet-commons-ssl-0.3.9.jar;
>       lib\slf4j-api-1.4.3.jar;
>       lib\xmlsec-1.4.1.jar;
>       thirdparty-lib\slf4j\logback-classic-0.9.8.jar;
>       thirdparty-lib\slf4j\logback-core-0.9.8.jar
>
>    and build\test contains the logback.xml and xmltooling-config.xml
> files
>    as well as the data directory from src\test.
>
>
> Where am I going wrong?  Does anyone have the configuration required to
> get the JUnit tests for java-xmltooling to run?  Are the JUnit tests
> even runnable at this point?
>
> Thanks.
>
> Clifford
>