To be complete on this subject, the pack200 algorithm has been implemented to
be able to resolve artifacts in an Eclipse updatesite. I don’t know how
nowadays artifacts are packaged on a « p2 repository », but some documentation
still exists and doesn’t contain any warnings:
https://wiki.eclipse
Github user asfgit commented on the issue:
https://github.com/apache/ant/pull/69
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/81/
---
--
Github user asfgit commented on the issue:
https://github.com/apache/ant/pull/69
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/87/
---
Github user jaikiran commented on the issue:
https://github.com/apache/ant/pull/69
The build actually caught a genuine issue that this build.xml was meant to
catch. I have now added a 3rd commit to this PR which fixes that issue. I'll be
squashing these commits before merging, if/when
Github user jaikiran commented on the issue:
https://github.com/apache/ant/pull/69
The build.xml changes that I committed look a bit wrong. Fixing them to a
working version.
---
-
To unsubscribe, e-mail: dev-unsubsc
Github user asfgit commented on the issue:
https://github.com/apache/ant/pull/69
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/80/
---
--
Github user asfgit commented on the issue:
https://github.com/apache/ant/pull/69
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/86/
---
GitHub user jaikiran opened a pull request:
https://github.com/apache/ant/pull/69
Allow more control over JUnit libraries and Ant runtime libraries for users
of junitlauncher
I've been sitting on these changes for a while now trying to complete this
work and then get some inputs. B
