petros

Support for version ranges.

3

This piggy backs off of issue #45. When passed a maven coordinate with a range of dependencies, it seems that aether stops walking the graph at that node. * Relevant...

The [--no-commit option](https://git-scm.com/docs/git-cherry-pick#Documentation/git-cherry-pick.txt---no-commit) is not supported by git-meta cherry-pick. Here is description of the feature ``` Usually the command automatically creates a sequence of commits. This flag applies the changes...

git meta doesn't respect color.status config

1

git meta status does not respect the `color.status` config. Apparently it is hard coded in the `colors/safe` npm module. Apparently `FORCE_COLOR=0 git meta status` works

output from `npm install -g` was ``` npm WARN deprecated [email protected]: Use mz or fs-extra^3.0 with Promise Support ```

Document usage of BFG and modify usage to be more ergonomic

3

Bouncing off #21, the following changes arose after I tried (and failed) to use Bfg on a simple java project. ### Documentation NOTE: This is a WIP. My primary intent...

In #13, there was a major exception/error we were unable to catch, because there were no e2e tests. Adding this issue as a reminder, for later.

Add support for artifactory and private repositories

8

# Migrating from [issue 498](https://github.com/bazelbuild/bazel/issues/498) in main repository. This is already implemented on the Bazel side, so similar code can probably be used for generate_workspace. It should use all of...

How to add a new maven deps and upgrade old maven deps to WORKSPACE file

2

# Migrated from [issue 989](https://github.com/bazelbuild/bazel/issues/989) in main repository ### Post 1 I see the generate WORKSPACE tool, which is useful. But an ongoing issue is the pain in transitively adding...

generate_workspace should/could choose highest maven version number

7

# Migrated from [issue 1573](https://github.com/bazelbuild/bazel/issues/1573) in main repository If generate_workspace is run with artifacts that depend on a common artifact, it will choose the version from whichever it encounters first....

generate_workspace is generating invalid shas

1

# Migrated from issue [#1131](https://github.com/bazelbuild/bazel/issues/1131) in original repository. generate_workspace seems to be creating invalid sha1 entries of the form: ``` maven_jar( name = "net_java_dev_jets3t_jets3t", artifact = "net.java.dev.jets3t:jets3t:0.6.1", sha1 = "9f95b944ccbbbeedd397e8f62e5690fd735a45e5...