-
Notifications
You must be signed in to change notification settings - Fork 13
Home
The projects are set up to be built via binary references to artifacts ( e.g. slatekit-app depends on slatekit-common ) via an package/artifact reference from github packages. However, this approach loads all sub-projects as sources so any changes in one sub-project can be easily tested in another sub-project in the same multi-project solution without publishing artifacts.
- Root source code is at
root/src/lib/kotlin
- Set env variable
SLATEKIT_PROJECT_MODE=sources
( instead ofbinary
) to load project references as sources. - Open intellij main project from
root/src/lib/kotlin/slatekit
- Search replace
version "$kotlin_version"
with//version "$kotlin_version"
( commented out ) - Only enable
version "$kotlin_version"
in build.gradle for the main slatekit project. - Comment out the jar task in the main slatekit build.gradle file
- Tests located at
root/src/lib/kotlin/slatekit-tests
- Move master -> main https://stevenmortimer.com/5-steps-to-change-github-default-branch-from-master-to-main/
- Ensure you have gradle 3.5 gradle --version
- Download Slate Kit source git clone git@github.com:code-helix/slatekit.git
Refer to http://www.slatekit.com/kotlin-setup.html for more info on compiling NOTE This will also deploy to bintray
- Upgrade the version number in
/src/lib/kotlin/version.txt
- Upgrade the version number in
/src/ext/kotlin/version.txt
- Ensure following env ( if it exists ) is set to binary
export SLATEKIT_PROJECT_MODE=binary
- Open terminal and go to
/src/lib/kotlin/
- Run bash script
./build-all.sh
to build all projects
Gradle unit-tests automation is not yet ready. The tests have be to run using IntellJ
- Open the project(s) in intellij
- Right-click the test projects and select (Run all tests)
- About ~350 tests should pass
- There may be 4 failures - to fix soon
Use bintray to upload the jars/poms. Gradle automation is not yet setup
- Ensure environment variables setup as
BINTRAY_USER
andBINTRAY_API_KEY
- Get the username/api key from kishore
- Open terminal to root directory of
src/lib/kotlin
- Run command gradle build and then gradle bintrayUpload
- Note: You can run both commands via gradle build bintrayUpload
This is not needed, but docs are here just in case )
- Login to bintray
- For each project create new version e..g 0.9.7
- For the new version, upload jar file
- Publish the files at the prompt/option
- From list of files, select the jar file to be shown in downloads
- Upload the pom file
- Do same for the other 6 projects
gh release create v2.11.1 --generate-notes
Drafting a new release involves a few various steps in git, dropbox, bintray and updating the website
- Deploy the binaries to bintray ( refer to section deploy above )
- Package the project for distribution ( sample apps, binaries etc ) - refer to package
- Upload the compressed zipped release file to dropbox ( in public folder )
- Share the dropbox link ( create link/copy it for link in webpage below )
- Update the slatekit website in branch gh-pages
- Update the webpage releases.html and add a new entry
- Finally, create a release in git