tetra 0.54.0 → 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/SPECIAL_CASES.md +36 -1
- data/lib/tetra/version.rb +1 -1
- metadata +2 -2
data/SPECIAL_CASES.md
CHANGED
|
@@ -47,7 +47,42 @@ You can also use system-provided Ant and Maven by simply deleting their director
|
|
|
47
47
|
|
|
48
48
|
## Other build tools
|
|
49
49
|
|
|
50
|
-
Other build tools are currently
|
|
50
|
+
Other build tools are currently not supported out-of-the-box but you can still use them with some manual tweaking. You should basically make sure that:
|
|
51
|
+
|
|
52
|
+
- a copy of their executables and libraries is stored and gets called from `kit/`
|
|
53
|
+
- all files automatically downloaded during the build are also stored in `kit`.
|
|
54
|
+
|
|
55
|
+
Tool-specific instructions for most popular tools follow.
|
|
56
|
+
|
|
57
|
+
### ivy
|
|
58
|
+
|
|
59
|
+
Assuming ivy is used by ant:
|
|
60
|
+
* during your dry-run build, add the `-Divy.default.ivy.user.dir=<PATH_TO_PROJECT>/kit/ivy` commandline option to `ant` in order to download files in the `kit` directory;
|
|
61
|
+
* after your build script is generated, replace the path to your project with `$PROJECT_PREFIX` in `build.sh` to ensure the build will not need Internet access.
|
|
62
|
+
|
|
63
|
+
### sbt
|
|
64
|
+
|
|
65
|
+
Instructions:
|
|
66
|
+
* before starting your dry-run build, copy a binary release to a subdirectory in `kit/`, for example `kit/sbt/`;
|
|
67
|
+
* during your dry-run build, add the `-Dsbt.global.base=../../kit/sbt-global-base` commandline option to `sbt` in order to download files in the `kit` directory;
|
|
68
|
+
* if your build also uses Ivy, add `-Dsbt.ivy.home=../../kit/ivy2` as well;
|
|
69
|
+
* after your build script is generated, add the `"set offline := true"` commandline option to `sbt` to `build.sh` to ensure the build will not need Internet access.
|
|
70
|
+
|
|
71
|
+
### gradle
|
|
72
|
+
|
|
73
|
+
Assuming your project uses the [Gradle Wrapper](http://gradle.org/docs/current/userguide/gradle_wrapper.html);
|
|
74
|
+
|
|
75
|
+
* during your dry-run build, add the `--gradle-user-home /tmp/gradle --project-cache-dir /tmp/gradle-project` commandline options to `gradlew` in order to download files in the `/tmp` directory instead of your home
|
|
76
|
+
* after the build has finished but prior ending the dry-run, copy all files to your kit with:
|
|
77
|
+
|
|
78
|
+
cp -r /tmp/gradle* kit/
|
|
79
|
+
|
|
80
|
+
* after your build script is generated, add the following line to `build.sh` in order to restore files from `kit/` to `/tmp`:
|
|
81
|
+
cp -r /tmp/gradle* kit/
|
|
82
|
+
|
|
83
|
+
* furthermore, add the `--gradle-user-home /tmp/gradle --project-cache-dir /tmp/gradle-project --offline` commandline options to `gradlew` in `build.sh` to ensure the build will not need Internet access.
|
|
84
|
+
|
|
85
|
+
Note that you cannot put files in `kit/` directly because your build would break on relocation, see [GRADLE-2690](https://issues.gradle.org/browse/GRADLE-2690).
|
|
51
86
|
|
|
52
87
|
## [OBS](build.opensuse.org) integration
|
|
53
88
|
|
data/lib/tetra/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: tetra
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 1.0.0
|
|
5
5
|
prerelease:
|
|
6
6
|
platform: ruby
|
|
7
7
|
authors:
|
|
@@ -9,7 +9,7 @@ authors:
|
|
|
9
9
|
autorequire:
|
|
10
10
|
bindir: bin
|
|
11
11
|
cert_chain: []
|
|
12
|
-
date: 2015-04-
|
|
12
|
+
date: 2015-04-17 00:00:00.000000000 Z
|
|
13
13
|
dependencies:
|
|
14
14
|
- !ruby/object:Gem::Dependency
|
|
15
15
|
name: rake
|