wooga / atlas-paket Goto Github PK

From looking at the code it seems that some properties aren't used and others annotated in correct.

Description

When some thing bad TM happens in the installation process of nuget packages we can end up with incomplete installations of libraries.

Goal

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-

Description

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.

Steps to reproduce

1. install dependencies with paketInstall to create a paket.lock file.
2. delete the packages directory
3. run the task paketRestore to restore the packages directory
4. run the task paketRestore again

Expected behavior

The task should be UP-TO-DATE

Actual Behavior

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)

Description

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

• update code style
• introduce and use convention mapping
• mark internal as internal
• configure tasks with project.getTasks().withType for late initialization
• make configuration static
• use static strings

Instead of linking to the tasks, we should link against all tasks of type

• PaketUpdate
• PaketInstall
• PaketRestore

Or just for the update case.

Description

Before version 1.0.0 it was possible to set the version parameter as a groovy Closure or Callable object.

Steps to reproduce

1. Create project with a paket.dependencies, paket.template file and a gradle setup.
2. Set version parameter of the paketPack task to `{ "some version" }

Expected behavior

PaketPack task evaluates closure and uses internal object.toString()

Current behavior

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.

Description

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.

Description

Items with training spaces in paket.unity3d.references are silently ignored

Steps to reproduce

1. Add some whitespace to an entry and run ./gradlew paketInstall ...

Currently we have to wait for afterEvaluate to append dependencies

Example

project.afterEvaluate{ project.tasks['paketPack-WoogaJsonDotNetNode'].dependsOn ':msbuild' }

Possible options:

• create tasks for all dependencies listed in paket.dependencies
• create tasks based on paketOutdated result
• add flag --outdated