Make automated test suites standalone #136
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…office. updated smoketestdoc build where most of the dependencies were. Added a modified copy of main/solenv/ant/aoo-ant.xml to smoketestdoc for importing to build as well as idl.xml to import into aoo-ant.xml.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New branch based on trunk for this for now.
This change breaks the dependency on needing to have built the office to have access to the Java UNO jars and other tools like javamaker, regmerge, and idlc, and changes it to depend on the ones in the office under test which is passed as the openoffice.home env variable to ant compile and the run scripts.
This allows anyone to run the QA test suites against any office directory as long is it has an SDK installed in it without needing the office build environment setup.
Another breaking change is that running it against a just-built "installed" office requires the sdk be copied into the office first.