MeFisto94
|
70626cd22c
Fix 3.3 related build breakage
|
5 anos atrás |
MeFisto94
|
4b11793b89
Workaround for jMonkeyEngine/#1260 - Manually trigger an engine build
|
5 anos atrás |
MeFisto94
|
4221ce9b9f
Build: Fix a design problem. Before this we used to install the engine into the local maven repository. This had several flaws: Apart from spamming the developers mavenLocal repository with thousands(!) of engine versions, it was hard to predict the actual engine version to use. This is because with Pull Requests or Tags and different Branches the names changed, especially when both the engine and the sdk had a tag. Controlling the engine version is now only controlled by the TRAVIS_TAG ENV-Var or manually on the engine repo (where usually master is cloned otherwise)
|
5 anos atrás |
grizeldi
|
f424d292b4
Version bump and build_engine.sh fixes for existing installs
|
6 anos atrás |
MeFisto94
|
8cbbdadc2c
Fix build_engine.sh: The Engine GIT Tags are "v3.2.0-stable", whereas the POM Version is 3.2.0-stable
|
7 anos atrás |
MeFisto94
|
04a283818d
build_engine.sh: Automatically extract the engine version from the travis tag. if no travis tag is specified, then use master. The behavior for manual builds will stay unchanged.
|
7 anos atrás |
MeFisto94
|
541870eb84
Try to release v3.2.0-stable-sdk1
|
7 anos atrás |
MeFisto94
|
089a21a700
Initial step towards Engine Version 3.2
|
8 anos atrás |
MeFisto94
|
7b814fb81e
Update SDK Engine Version to v3.1.0-stable
|
8 anos atrás |
MeFisto94
|
be909565af
Update BuildEngine to also build the Beta3 Version
|
8 anos atrás |
MeFisto94
|
bace2bd40c
Travis: Build the specific tag instead of the branch head.
|
8 anos atrás |
MeFisto94
|
9c5d7d371a
Try to fix building the wrong engine version
|
8 anos atrás |
MeFisto94
|
7c047893d6
Try to build the correct engine version
|
8 anos atrás |
MeFisto94
|
b73d0a99a2
Make Travis Work again and stick to 3.1.0-beta2 as engine version instead of a master Snapshot.
|
8 anos atrás |
MeFisto94
|
b2be180edf
Build: Remove HW Skinning Patch as it has been merged into the engine
|
9 anos atrás |
MeFisto94
|
f517917f96
Workaround: Don't rely on Engine Deployment but build from source into a local maven repo.
|
9 anos atrás |