Bug 171892 - parameterize ldapjdk and crimson jar locations
Summary: parameterize ldapjdk and crimson jar locations
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: 389
Classification: Retired
Component: Directory Server
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-27 15:17 UTC by Rich Megginson
Modified: 2015-01-04 23:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-06 19:49:26 UTC
Embargoed:


Attachments (Terms of Use)
List of files in fix (193 bytes, text/plain)
2005-10-27 15:17 UTC, Rich Megginson
no flags Details
diffs for fix (9.35 KB, text/plain)
2005-10-27 15:18 UTC, Rich Megginson
no flags Details

Description Rich Megginson 2005-10-27 15:17:42 UTC
Allow the use of other than dist/classes for the ldapjdk and crimson jar files.  
This is needed for gar and other autoconf like build systems.

Comment 1 Rich Megginson 2005-10-27 15:17:42 UTC
Created attachment 120466 [details]
List of files in fix

Comment 2 Rich Megginson 2005-10-27 15:18:16 UTC
Created attachment 120467 [details]
diffs for fix

Comment 3 Rich Megginson 2005-10-29 02:21:12 UTC
Reviewed by: Noriko, Nathan (Thanks!)
Branch: HEAD
Fix Description: This is also needed for GAR.  The xmltools also 
ldapjdk.jar, and needs crimson.jar.  DSMLGW does not need crimson.jar.  
It makes sense to separate these out of the dsmlgw jars.  I changed the 
dsmlgw build.xml to be able to pickup ldapjdk.jar from a different 
location - defaults to the usual dist/classes.
Platforms tested: RHEL4
Flag Day: no
Doc impact: no
QA impact: should be covered by regular nightly and manual testing
New Tests integrated into TET: none

Checking in ldapserver/buildpaths.mk;
/cvs/dirsec/ldapserver/buildpaths.mk,v  <--  buildpaths.mk
new revision: 1.8; previous revision: 1.7
done
Checking in ldapserver/components.mk;
/cvs/dirsec/ldapserver/components.mk,v  <--  components.mk
new revision: 1.34; previous revision: 1.33
done
Checking in ldapserver/internal_buildpaths.mk;
/cvs/dirsec/ldapserver/internal_buildpaths.mk,v  <--  internal_buildpaths.mk
new revision: 1.8; previous revision: 1.7
done
Checking in ldapserver/ldap/clients/dsmlgw/Makefile;
/cvs/dirsec/ldapserver/ldap/clients/dsmlgw/Makefile,v  <--  Makefile
new revision: 1.10; previous revision: 1.9
done
Checking in ldapserver/ldap/clients/dsmlgw/build.xml;
/cvs/dirsec/ldapserver/ldap/clients/dsmlgw/build.xml,v  <--  build.xml
new revision: 1.7; previous revision: 1.6
done
Checking in ldapserver/ldap/cm/Makefile;
/cvs/dirsec/ldapserver/ldap/cm/Makefile,v  <--  Makefile
new revision: 1.39; previous revision: 1.38
done


Comment 4 Jenny Severance 2011-06-06 18:40:24 UTC
Please add steps to reproduce and verify thanks


Note You need to log in before you can comment on or make changes to this bug.