wooga / atlas-paket Goto Github PK
View Code? Open in Web Editor NEWPaket plugin for gradle
Home Page: https://wooga.github.io/atlas-paket/
License: Apache License 2.0
Paket plugin for gradle
Home Page: https://wooga.github.io/atlas-paket/
License: Apache License 2.0
From looking at the code it seems that some properties aren't used and others annotated in correct.
When some thing bad TM happens in the installation process of nuget packages we can end up with incomplete installations of libraries.
We want to introduce a validation step that the content tree that is installed in Assets/Paket.Unity3D
corresponds to what was built on Jenkins. One idea could be some sort of manifest file with checksums of files with normalised line endings.
Paket restore creates cache files in these folders. After a clean it can happen that paket is thinking it's still up to date even though it is not.
One of the use cases for ./gradlew publishLocal
is to be able to test dependencies with other wdks or projects before commiting / pushing.
It would be nice if publishLocal would support some auto bumping of the version so that ./gradlew paketUpdate
can be run on the other side without deleting the lock file all the time.
Something along the lines of:
./gradlew publishLocal -Prelease.stage=snapshot -Prelease.version=0.0.1-master`date +%s | cut -c6-
The paketRestore
UP-TO-DATE
check is broken due to a change in the latest paket versions (The version is unknown because this issue just popped up). The content of the restore cache file used to be a copy of the lock file. The content is now a json
payload with multiple hashes.
paketInstall
to create a paket.lock
file.paketRestore
to restore the packages directorypaketRestore
againThe task should be UP-TO-DATE
The task is not UP-TO-DATE
Paket developed a few more version since atlas-paket came to be. Add a version support constraint and update the commandline arguments.
is missing a setter for --endpoint
from paket push docs:
--endpoint <path> API endpoint to push to (default: /api/v2/package)
The paketBootstrap
task constantly fails with gradle > 4.5
. The executed command works without problems when executed from the commandline.
Use Class and Project structure like atlas-unity
project.getTasks().withType
for late initializationInstead of linking to the tasks, we should link against all tasks of type
PaketUpdate
PaketInstall
PaketRestore
Or just for the update case.
Before version 1.0.0
it was possible to set the version
parameter as a groovy Closure
or Callable
object.
version
parameter of the paketPack
task to `{ "some version" }PaketPack
task evaluates closure and uses internal object.toString()
PaketPack
fails because version passed to the paket tool is Closure.toString()
output.
The README.md file is quite long. Move the documentation to the wiki and provide only a minimal usage and support overview.
The paketBootstrap
task was written two years ago with a complete different version of gradle in mind. Back then gradle did not invalidate the build output based on it's own build history. This is no real issue in everyday work with this plugin but makes considerable issues during test runs. Github rate limits the URL calls to the bootstrapper binary which results in a lot of test failures. These tests could work with a cached version of the paket.bootstrapper.exe
and paket.exe
. But in the current form each test run will redownload and setup both paket.bootstrapper.exe
and paket.exe
for every test spec example. This needs to be adressed as the offical linux support #50 is untestable at the moment.
We generate dedicated paketUpdate
tasks for each dependency listed in paket.dependencies
We should instead use the paket.lock
file instead and create update tasks for all dependencies.
All paket
tasks will skip
when paket.dependencies
is not located in the project root.
This is not a desired logic for paketPack
and paketPush
tasks.
Running paketOutdated
without --info
nothing will be printed to the console. We should print the relevant output directly to the console.
Items with training spaces in paket.unity3d.references are silently ignored
Currently we have to wait for afterEvaluate
to append dependencies
Example
project.afterEvaluate{ project.tasks['paketPack-WoogaJsonDotNetNode'].dependsOn ':msbuild' }
Possible options:
paket.dependencies
paketOutdated
result--outdated
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.