Last change
on this file was 35325, checked in by davidb, 3 years ago |
README file to explain the purpose of this new sub-directory area of the GS3 code base
|
File size:
1.1 KB
|
Line | |
---|
1 |
|
---|
2 |
|
---|
3 | As a result of Greenstone3 working with 'ant', jar dependencies
|
---|
4 | essentially need to be worked out manually. Because the code base is
|
---|
5 | largely static, then this is not typically a significant burden.
|
---|
6 | The purpose of the directory area of the code base is to provide
|
---|
7 | some scripts that assist in the process of working out what
|
---|
8 | jar files need to be added when a new 'jar stack' is added in.
|
---|
9 |
|
---|
10 | For example, to support Google Signin to Greenstone3, code
|
---|
11 | as been added to the code base that makes use of the Java
|
---|
12 | 'google-api-client' jar. This in turn requires various
|
---|
13 | other supporting jar files. Inside the subdirectory:
|
---|
14 |
|
---|
15 | google-api-client-jars
|
---|
16 |
|
---|
17 | you will find scripts that help automate this process.
|
---|
18 |
|
---|
19 | In this subdirectory you will only find Unix scripts,
|
---|
20 | which is OK. The list of jar files needed only needs to
|
---|
21 | be worked out once and then added to the Greenstone jar/lib
|
---|
22 | area. With the necessary jar files install, subsequent
|
---|
23 | 'ant compile-core' commands -- whenever and whereever in
|
---|
24 | terms of the OS being used -- are run, the jar files needed
|
---|
25 | to successfully compile will be found.
|
---|
Note:
See
TracBrowser
for help on using the repository browser.