@@ -16,7 +16,7 @@ Leiningen is for automating Clojure projects without setting your hair on fire.
## Installation
If your preferred
-[package manager](https://github.com/technomancy/leiningen/wiki/Packaging)
+[package manager](https://codeberg.org/leiningen/leiningen/wiki/Packaging)
offers a recent version of Leiningen, try that first as long as it has version 2.x.
Leiningen installs itself on the first run of the `lein` shell script; there is no
@@ -34,10 +34,16 @@ Windows users can use the above script in the Linux subsystem or try
[Powershell version](https://raw.githubusercontent.com/technomancy/leiningen/stable/bin/lein.ps1)
instead.
+Note: the canonical repository for Leiningen is [on
+Codeberg](https://codeberg.org/leiningen/leiningen) but we maintain [a
+mirror on GitHub](https://github.com/technomancy/leiningen) for the
+time being in order to ease the transition. Please update your links
+and git remotes.
+
## Basic Usage
The
-[tutorial](https://github.com/technomancy/leiningen/blob/stable/doc/TUTORIAL.md)
+[tutorial](https://codeberg.org/leiningen/leiningen/blob/stable/doc/TUTORIAL.md)
has a detailed walk-through of the steps involved in creating a new
project, but here are the commonly-used tasks:
@@ -73,19 +79,19 @@ The `project.clj` file in the project root should look like this:
(defproject myproject "0.5.0-SNAPSHOT"
:description "A project for doing things."
:license "Eclipse Public License 1.0"
- :url "http://github.com/technomancy/myproject"
+ :url "http://codelab.org/technomancy/myproject"
:dependencies [[org.clojure/clojure "1.8.0"]]
:plugins [[lein-tar "3.2.0"]])
```
The `lein new` task generates a project skeleton with an appropriate
starting point from which you can work. See the
-[sample.project.clj](https://github.com/technomancy/leiningen/blob/stable/sample.project.clj)
+[sample.project.clj](https://codeberg.org/leiningen/leiningen/blob/stable/sample.project.clj)
file (also available via `lein help sample`) for a detailed listing of
configuration options.
The `project.clj` file can be customized further with the use of
-[profiles](https://github.com/technomancy/leiningen/blob/stable/doc/PROFILES.md).
+[profiles](https://codeberg.org/leiningen/leiningen/blob/stable/doc/PROFILES.md).
## Documentation
@@ -93,38 +99,38 @@ Leiningen documentation is organized as a number of guides:
### Usage
- * [Tutorial](https://github.com/technomancy/leiningen/blob/stable/doc/TUTORIAL.md) (start here if you are new)
- * [FAQ](https://github.com/technomancy/leiningen/blob/stable/doc/FAQ.md)
- * [Profiles](https://github.com/technomancy/leiningen/blob/stable/doc/PROFILES.md)
- * [Deployment & Distribution of Libraries](https://github.com/technomancy/leiningen/blob/stable/doc/DEPLOY.md)
- * [Sample project.clj](https://github.com/technomancy/leiningen/blob/stable/sample.project.clj)
- * [Polyglot (e.g. Clojure/Java) projects](https://github.com/technomancy/leiningen/blob/stable/doc/MIXED_PROJECTS.md)
+ * [Tutorial](https://codeberg.org/leiningen/leiningen/blob/stable/doc/TUTORIAL.md) (start here if you are new)
+ * [FAQ](https://codeberg.org/leiningen/leiningen/blob/stable/doc/FAQ.md)
+ * [Profiles](https://codeberg.org/leiningen/leiningen/blob/stable/doc/PROFILES.md)
+ * [Deployment & Distribution of Libraries](https://codeberg.org/leiningen/leiningen/blob/stable/doc/DEPLOY.md)
+ * [Sample project.clj](https://codeberg.org/leiningen/leiningen/blob/stable/sample.project.clj)
+ * [Polyglot (e.g. Clojure/Java) projects](https://codeberg.org/leiningen/leiningen/blob/stable/doc/MIXED_PROJECTS.md)
### Development
-* [Writing Plugins](https://github.com/technomancy/leiningen/blob/stable/doc/PLUGINS.md)
-* [Writing Templates](https://github.com/technomancy/leiningen/blob/stable/doc/TEMPLATES.md)
-* [Contributing](https://github.com/technomancy/leiningen/blob/stable/CONTRIBUTING.md)
-* [Building Leiningen](https://github.com/technomancy/leiningen/blob/stable/CONTRIBUTING.md#bootstrapping)
+* [Writing Plugins](https://codeberg.org/leiningen/leiningen/blob/stable/doc/PLUGINS.md)
+* [Writing Templates](https://codeberg.org/leiningen/leiningen/blob/stable/doc/TEMPLATES.md)
+* [Contributing](https://codeberg.org/leiningen/leiningen/blob/stable/CONTRIBUTING.md)
+* [Building Leiningen](https://codeberg.org/leiningen/leiningen/blob/stable/CONTRIBUTING.md#bootstrapping)
## Plugins
Leiningen supports plugins which may introduce new tasks. See
-[the plugins wiki page](https://github.com/technomancy/leiningen/wiki/Plugins)
+[the plugins wiki page](https://codeberg.org/leiningen/leiningen/wiki/Plugins)
for a full list. If a plugin is needed for successful test or build
runs, (such as `lein-tar`) then it should be added to `:plugins` in
project.clj, but if it's for your own convenience (such as
`lein-pprint`) then it should be added to the `:plugins` list in the
`:user` profile in `~/.lein/profiles.clj`. See the
-[profiles guide](https://github.com/technomancy/leiningen/blob/stable/doc/PROFILES.md)
+[profiles guide](https://codeberg.org/leiningen/leiningen/blob/stable/doc/PROFILES.md)
for details on how to add to your `:user` profile. The
-[plugin guide](https://github.com/technomancy/leiningen/blob/stable/doc/PLUGINS.md)
+[plugin guide](https://codeberg.org/leiningen/leiningen/blob/stable/doc/PLUGINS.md)
explains how to write plugins.
## License
-Source Copyright © 2009-2021 Phil Hagelberg, Alex Osborne, Dan Larkin, and
-[contributors](https://github.com/technomancy/leiningen/contributors).
+Source Copyright © 2009-2022 Phil Hagelberg, Alex Osborne, Dan Larkin, and
+contributors.
Distributed under the Eclipse Public License, the same as Clojure
uses. See the file COPYING.
diff --git a/bin/release b/bin/release
index 5d918eac8..9e95ca113 100755
--- a/bin/release
+++ b/bin/release
@@ -78,7 +78,7 @@ cd $LEIN_ROOT
git commit -a -m "Release $RELEASE_VERSION"
git tag -s $RELEASE_VERSION -m "Release $RELEASE_VERSION"
-git push && git push --tags && git push origin master:stable
+git push && git push --tags && git push origin main:stable
echo "Upload $SELF_INSTALL_JAR and $SELF_INSTALL_JAR.asc to GitHub:"
echo "https://github.com/technomancy/leiningen/releases/new?tag=$RELEASE_VERSION"
diff --git a/doc/DEPLOY.md b/doc/DEPLOY.md
index 44f8f23c1..2e43f1c31 100644
--- a/doc/DEPLOY.md
+++ b/doc/DEPLOY.md
@@ -25,7 +25,7 @@
Getting your library into [Clojars](https://clojars.org) is fairly
straightforward as is documented near the end of
-[the Leiningen tutorial](https://github.com/technomancy/leiningen/blob/stable/doc/TUTORIAL.md).
+[the Leiningen tutorial](https://codeberg.org/leiningen/leiningen/blob/stable/doc/TUTORIAL.md).
However, deploying elsewhere is not always that straightforward.
## Private Repositories
@@ -137,7 +137,7 @@ haven't set up credentials, but it's convenient to set it so you don't have to
re-enter it every time you want to deploy. You will need
[gpg](https://www.gnupg.org/) installed and a key pair configured. If
you need help with either of those, see the
-[GPG guide](https://github.com/technomancy/leiningen/blob/stable/doc/GPG.md).
+[GPG guide](https://codeberg.org/leiningen/leiningen/blob/stable/doc/GPG.md).
### GPG
diff --git a/doc/FAQ.md b/doc/FAQ.md
index fbfbb25f3..b2ccf42cd 100644
--- a/doc/FAQ.md
+++ b/doc/FAQ.md
@@ -13,7 +13,7 @@
**Q:** What's a group ID? How do snapshots work?
**A:** See the
- [tutorial](https://github.com/technomancy/leiningen/blob/stable/doc/TUTORIAL.md)
+ [tutorial](https://codeberg.org/leiningen/leiningen/blob/stable/doc/TUTORIAL.md)
for background.
**Q:** How should I pick my version numbers?
@@ -25,7 +25,7 @@
**Q:** What if my project depends on jars that aren't in any repository?
**A:** You will need to get them in a repository. The
- [deploy guide](https://github.com/technomancy/leiningen/blob/stable/doc/DEPLOY.md)
+ [deploy guide](https://codeberg.org/leiningen/leiningen/blob/stable/doc/DEPLOY.md)
explains how to set up a private repository. In general it's easiest
to deploy them to a static HTTP server or a private S3 bucket. Once
the repo is set up, `lein deploy private-repo com.mycorp/somejar
@@ -38,7 +38,7 @@
**Q:** I want to hack a project and one of its dependencies, but it's annoying to switch between them.
**A:** Leiningen provides a feature called *checkout dependencies* to
make this smoother. See the
- [tutorial](https://github.com/technomancy/leiningen/blob/stable/doc/TUTORIAL.md)
+ [tutorial](https://codeberg.org/leiningen/leiningen/blob/stable/doc/TUTORIAL.md)
to learn more.
**Q:** Is it possible to exclude indirect dependencies?
@@ -119,7 +119,7 @@
**Q:** Still too slow; what else can make startup faster?
**A:** The wiki has a page covering
- [ways to improve startup time](https://github.com/technomancy/leiningen/wiki/Faster).
+ [ways to improve startup time](https://codeberg.org/leiningen/leiningen/wiki/Faster).
**Q:** What if I care more about long-term performance than startup time?
**A:** Leiningen 2.1.0 onward get a speed boost by disabling optimized
@@ -239,7 +239,7 @@ happens it is strongly recommended to add an `:exclusion` and report a
bug with the dependency which does this.
**Q:** `lein`/`lein.bat` won't download `leiningen-x.y.z-SNAPSHOT.jar`
-**A:** You probably downloaded `lein`/`lein.bat` from the [master branch](https://github.com/technomancy/leiningen/tree/master/bin). Unless you plan to build leiningen yourself or help develop it, we suggest you use the latest stable version: [lein](https://raw.githubusercontent.com/technomancy/leiningen/stable/bin/lein)/[lein.bat](https://raw.githubusercontent.com/technomancy/leiningen/stable/bin/lein.bat)
+**A:** You probably downloaded `lein`/`lein.bat` from the [main branch](https://codeberg.org/leiningen/leiningen/tree/main/bin). Unless you plan to build leiningen yourself or help develop it, we suggest you use the latest stable version: [lein](https://raw.githubusercontent.com/technomancy/leiningen/stable/bin/lein)/[lein.bat](https://raw.githubusercontent.com/technomancy/leiningen/stable/bin/lein.bat)
**Q:** I have a dependency whose group ID and/or artifact ID starts with a
number (which is invalid for symbols in Clojure). How can I add it to my
diff --git a/doc/GPG.md b/doc/GPG.md
index 8f432b913..e8ae60a2f 100644
--- a/doc/GPG.md
+++ b/doc/GPG.md
@@ -183,7 +183,7 @@ Leiningen uses GPG for three things: decrypting credential files,
signing release artifacts, and signing tags. We'll focus on artifact
signing here; for information on credentials encryption/decryption,
see the
-[deploy guide](https://github.com/technomancy/leiningen/blob/stable/doc/DEPLOY.md). Once
+[deploy guide](https://codeberg.org/leiningen/leiningen/blob/stable/doc/DEPLOY.md). Once
you are configured to sign releases, signing tags should be
straightforward.
diff --git a/doc/PLUGINS.md b/doc/PLUGINS.md
index c6b9979bc..d22afa472 100644
--- a/doc/PLUGINS.md
+++ b/doc/PLUGINS.md
@@ -76,7 +76,7 @@ on that argument.
However, if you need to call other Leiningen functions or have no need
to run anything inside the context of the project's own process,
-making a plugin might be the right choice if one doesn't [exist already](https://github.com/technomancy/leiningen/wiki/plugins),
+making a plugin might be the right choice if one doesn't [exist already](https://codeberg.org/leiningen/leiningen/wiki/plugins),
## Writing a Plugin
@@ -87,11 +87,11 @@ has `:eval-in-leiningen true`, which causes all tasks to operate
inside the leiningen process rather than starting a subprocess to
isolate the project's code. Plugins need not declare a dependency on
Clojure itself; in fact
-[all of Leiningen's own dependencies](https://github.com/technomancy/leiningen/blob/stable/project.clj)
+[all of Leiningen's own dependencies](https://codeberg.org/leiningen/leiningen/blob/stable/project.clj)
will be available.
See the `lein-pprint` directory
-[in the Leiningen source](https://github.com/technomancy/leiningen/tree/stable/lein-pprint)
+[in the Leiningen source](https://codeberg.org/leiningen/leiningen/tree/stable/lein-pprint)
for a sample of a very simple plugin.
When emitting output, please use `leiningen.core.main/info`,
@@ -542,7 +542,7 @@ the argument list so that the `-main` function running inside the
project code gets access to it.
The vast majority of these cases are already covered by
-[existing plugins](https://github.com/technomancy/leiningen/wiki/plugins),
+[existing plugins](https://codeberg.org/leiningen/leiningen/wiki/plugins),
but if you have a case that doesn't exist and for some reason can't
spin it off into its own separate plugin, you can enable this behavior
by placing the `foo.clj` file defining the new task in
@@ -569,7 +569,7 @@ proper plugin.
## Have Fun
Please add your plugin to [the list on the
-wiki](https://github.com/technomancy/leiningen/wiki/plugins) once it's ready.
+wiki](https://codeberg.org/leiningen/leiningen/wiki/plugins) once it's ready.
Hopefully the plugin mechanism is simple and flexible enough to let
you bend Leiningen to your will.
diff --git a/doc/PROFILES.md b/doc/PROFILES.md
index bef12a2a6..0315fd6f7 100644
--- a/doc/PROFILES.md
+++ b/doc/PROFILES.md
@@ -252,7 +252,7 @@ Here is an example of such a case:
## Debugging
To see how a given profile affects your project map, use the
-[lein-pprint](https://github.com/technomancy/leiningen/tree/stable/lein-pprint)
+[lein-pprint](https://codeberg.org/leiningen/leiningen/tree/stable/lein-pprint)
plugin:
$ lein with-profile 1.4 pprint
diff --git a/doc/TEMPLATES.md b/doc/TEMPLATES.md
index 93e2f5d71..bcbea1376 100644
--- a/doc/TEMPLATES.md
+++ b/doc/TEMPLATES.md
@@ -67,7 +67,7 @@ you wish to be part of your template. For everything you add, make sure the
`liquid_cool.clj` file receives corresponding entries in that `->files`
call. For examples to follow, have a look inside [the \*.clj files for the
built-in
-templates](https://github.com/technomancy/leiningen/tree/stable/resources/leiningen/new).
+templates](https://codeberg.org/leiningen/leiningen/tree/stable/resources/leiningen/new).
## Testing Your Template
diff --git a/doc/TUTORIAL.md b/doc/TUTORIAL.md
index 51d397f1f..54d0f78b9 100644
--- a/doc/TUTORIAL.md
+++ b/doc/TUTORIAL.md
@@ -37,7 +37,7 @@
Leiningen is for automating Clojure projects without setting your hair
on fire. If you experience your hair catching on fire or any other
frustrations while following this tutorial, please
-[let us know](https://github.com/technomancy/leiningen/issues/new).
+[let us know](https://codeberg.org/leiningen/leiningen/issues/new).
It offers various project-related tasks and can:
@@ -102,7 +102,7 @@ Next let's take a look at how projects are created.
## Creating a Project
We'll assume you've got Leiningen installed as per the
-[README](https://github.com/technomancy/leiningen/blob/stable/README.md).
+[README](https://codeberg.org/leiningen/leiningen/blob/stable/README.md).
Generating a new project is easy:
$ lein new app my-stuff
@@ -271,7 +271,7 @@ wider JVM community.
You can add third-party repositories by setting the `:repositories` key
in project.clj. See the
-[sample.project.clj](https://github.com/technomancy/leiningen/blob/stable/sample.project.clj)
+[sample.project.clj](https://codeberg.org/leiningen/leiningen/blob/stable/sample.project.clj)
for examples on how to do so. This sample uses additional repositories such as the Sonatype
repository which gives access to the latest SNAPSHOT development version of a library (Clojure or Java).
It also contains other relevant settings regarding repositories such as update frequency.
@@ -672,7 +672,7 @@ Leiningen's own JVM will stay up and consume unnecessary memory.
In addition it's very important to ensure you take steps to freeze all
the dependencies before deploying, otherwise it could be easy to end
up with
-[unrepeatable deployments](https://github.com/technomancy/leiningen/wiki/Repeatability).
+[unrepeatable deployments](https://codeberg.org/leiningen/leiningen/wiki/Repeatability).
Consider including `~/.m2/repository` in your unit of deployment
(tarball, .deb file, etc) along with your project code. It's
recommended to use Leiningen to create a deployable artifact in a
@@ -703,7 +703,7 @@ Given these pitfalls, it's best to use an uberjar if possible.
If your project is a library and you would like others to be able to
use it as a dependency in their projects, you will need to get it into
a public repository. While it's possible to [maintain your own private
-repository](https://github.com/technomancy/leiningen/blob/stable/doc/DEPLOY.md)
+repository](https://codeberg.org/leiningen/leiningen/blob/stable/doc/DEPLOY.md)
or get it into [Central](https://search.maven.org), the easiest way is
to publish it at [Clojars](https://clojars.org). Once you have
[created an account](https://clojars.org/register) there, publishing
@@ -749,7 +749,7 @@ they don't have to be re-entered every time, see `lein help
deploying`. When deploying a release that's not a snapshot, Leiningen
will attempt to sign it using [GPG](https://gnupg.org) to prove your
authorship of the release. See the
-[deploy guide](https://github.com/technomancy/leiningen/blob/stable/doc/DEPLOY.md)
+[deploy guide](https://codeberg.org/leiningen/leiningen/blob/stable/doc/DEPLOY.md)
for details of how to set that up. The deploy guide includes
instructions for deploying to other repositories as well.
diff --git a/doc/ja/PLUGINS_ja.md b/doc/ja/PLUGINS_ja.md
index 2d9e7303d..a458bb7f7 100644
--- a/doc/ja/PLUGINS_ja.md
+++ b/doc/ja/PLUGINS_ja.md
@@ -36,9 +36,9 @@ Leiningenのタスクはleiningen.$TASK名前空間にある$TASKという名前
## プラグインを書く
`lein new plugin myplugin`でプロジェクトを作成するところからはじめ、`leiningen.myplugin`名前空間の`myplugin`関数を編集してください。`project.clj`内にある`:eval-in-leningen true`によって、タスクはサブプロセスではなく、leiningenプロセス内部で動作します。プラグインは、clojureそのものへの依存関係を宣言する必要はありません。
-[Leiningen本体の依存関係全て](https://github.com/technomancy/leiningen/blob/stable/project.clj)がプラグインから利用可能です。
+[Leiningen本体の依存関係全て](https://codeberg.org/leiningen/leiningen/blob/stable/project.clj)がプラグインから利用可能です。
-非常に単純なプラグインの例として、 [ソースコード内の](https://github.com/technomancy/leiningen/tree/stable/lein-pprint)
+非常に単純なプラグインの例として、 [ソースコード内の](https://codeberg.org/leiningen/leiningen/tree/stable/lein-pprint)
`lein-pprint`ディレクトリを参照してください。
プラグインの開発中、プロジェクト内で`lein install`を再実行し、それからテストプロジェクトに切り替えるのは非常に手間がかかります。一度プラグインをインストールすれば、テストプロジェクト内の`.lein-classpath`ファイルに、プラグインの`src`ディレクトリのパスを記述しておくことでこの手間を省くことができます。そのプラグインが別の開発中のライブラリに依存している場合は、`.lein-classpath`にUNIXでは`:`、Windowsでは`;`のクラスパスセパレータで区切ってライブラリのディレクトリを追加することができます。
@@ -285,7 +285,7 @@ Leiningenタスクを記述する必要があるのは、例えば`eval-in-proje
この例ではプロジェクトマップの`:version`フィールドを引数リストに渡すことで、プロジェクト内で実行される`-main`関数が値にアクセスできるようにしています。
-こういった例の多くは[既存のプラグイン](https://github.com/technomancy/leiningen/wiki/plugins)でカバーされているはずですが、もし類似の例が見つからず、何らかの理由で別のブラグインに分離できない場合、`tasks/leiningen/`の下に新しいタスクを定義した`foo.clj`ファイルを作成し、`tasks`を`.lein-classpath`に追加することでこのふるまいを実現することができます。
+こういった例の多くは[既存のプラグイン](https://codeberg.org/leiningen/leiningen/wiki/plugins)でカバーされているはずですが、もし類似の例が見つからず、何らかの理由で別のブラグインに分離できない場合、`tasks/leiningen/`の下に新しいタスクを定義した`foo.clj`ファイルを作成し、`tasks`を`.lein-classpath`に追加することでこのふるまいを実現することができます。
```
$ ls
@@ -304,7 +304,7 @@ Hello, Foo!
## 楽しんでください
-あなたのプラグインができあがったら、[Wiki上のリスト](https://github.com/technomancy/leiningen/wiki/plugins)に追加してください。
+あなたのプラグインができあがったら、[Wiki上のリスト](https://codeberg.org/leiningen/leiningen/wiki/plugins)に追加してください。
このプラグインシステムが、あなたの思いのままにLeiningenをカスタマイズするための簡単で、柔軟なシステムを提供していることを願っています。
diff --git a/doc/ja/TUTORIAL_ja.md b/doc/ja/TUTORIAL_ja.md
index f9c84a276..50043ceaa 100644
--- a/doc/ja/TUTORIAL_ja.md
+++ b/doc/ja/TUTORIAL_ja.md
@@ -38,7 +38,7 @@
Leiningen は Clojure プロジェクトを、髪の毛が燃え上がるような思いをせずに、
自動化するためのものです。もしこのチュートリアルにしたがっていて、
髪の毛が燃え上がるような思いをしたり何かイライラするようなことがあった場合は、
-ぜひ[私達に知らせてください](https://github.com/technomancy/leiningen/issues/new)。
+ぜひ[私達に知らせてください](https://codeberg.org/leiningen/leiningen/issues/new)。
Leiningen は様々なプロジェクトに関連するタスクを提案します:
@@ -109,7 +109,7 @@ Leiningen は*プロジェクト*とともに動作します。
## プロジェクトの作成
わたしたちは、あなたが
-[README](https://github.com/technomancy/leiningen/blob/stable/README.md)
+[README](https://codeberg.org/leiningen/leiningen/blob/stable/README.md)
にしたがって Leiningen をインストールしたと仮定します。
この時新しいプロジェクトを生成することは簡単です:
@@ -282,7 +282,7 @@ maven レポジトリで、 [Central](https://search.maven.org/) は
サードパーティのレポジトリは `:repositories` キーを project.clj に指定することで追加出来ます。
どのようにすれば良いのか
-[sample.project.clj](https://github.com/technomancy/leiningen/blob/stable/sample.project.clj)
+[sample.project.clj](https://codeberg.org/leiningen/leiningen/blob/stable/sample.project.clj)
を見てみましょう。このサンプルは追加のレポジトリとして Sonatype レポジトリを使っていますが、
これは(Clojure や Java の)ライブラリの、最新のスナップショット開発バージョンへのアクセスを提供します。
このサンプルには同様に、レポジトリに関連する更新頻度などの設定が含まれています。
@@ -690,7 +690,7 @@ uberjar 以上のことをしようとした場合、サーバサイドデプロ
Leiningen の自分自身の JVM は実行され続け、不必要なメモリを消費します。
加えて非常に重要なこととして、デプロイする前に全ての依存関係を凍結するステップを踏まなければなりません。
-そうしなければ[繰り返せないデプロイ](https://github.com/technomancy/leiningen/wiki/Repeatability)
+そうしなければ[繰り返せないデプロイ](https://codeberg.org/leiningen/leiningen/wiki/Repeatability)
問題によって止まってしまいます。一つのデプロイ(tar ファイル, .deb ファイルなど)にプロジェクトのコードに加えて、
`~/.m2/repository` を含むことを検討すべきです。継続インテグレーションを設定する際には、
デプロイ可能なアーティファクトを作るために Leiningen を使う事が推奨されます。
@@ -716,7 +716,7 @@ Leiningen の自分自身の JVM は実行され続け、不必要なメモリ
もしプロジェクトがライブラリで、他の人がプロジェクトの中で
依存関係としてそのライブラリを使えるようにしたいときは、
そのライブラリをパブリックレポジトリに置く必要が出てきます。
-自分自身の[プライベートレポジトリを運用する](https://github.com/technomancy/leiningen/blob/stable/doc/DEPLOY.md)
+自分自身の[プライベートレポジトリを運用する](https://codeberg.org/leiningen/leiningen/blob/stable/doc/DEPLOY.md)
こともできますし、
[Central](https://search.maven.org)に置くことも出来ますが、
最も簡単なのは[Clojars](https://clojars.org)で公開する方法でしょう。
@@ -749,7 +749,7 @@ Leiningen の自分自身の JVM は実行され続け、不必要なメモリ
スナップショット版ではなくリリース版をデプロイするときは、
Leiningen は [GPG](https://gnupg.org) を使って署名を行い、
リリースの著作権を証明します。どのように設定を行うかの詳細については、
-[デプロイガイド](https://github.com/technomancy/leiningen/blob/stable/doc/DEPLOY.md)を参考にしてください。
+[デプロイガイド](https://codeberg.org/leiningen/leiningen/blob/stable/doc/DEPLOY.md)を参考にしてください。
デプロイガイドでは他のレポジトリへのデプロイ方法の説明もしています。
## おわり!
diff --git a/doc/ja/lein_ja.1 b/doc/ja/lein_ja.1
index 9f949ad6c..9e22d68e9 100644
--- a/doc/ja/lein_ja.1
+++ b/doc/ja/lein_ja.1
@@ -173,7 +173,7 @@ Leiningen はその設定ファイルとして、プロジェクトのルート
.SH バグ
-https://github.com/technomancy/leiningen/issues を見て、
+https://codeberg.org/leiningen/leiningen/issues を見て、
あなたの問題が既知のものかどうか確認してください。
その際には、
diff --git a/doc/lein.1 b/doc/lein.1
index f66fe2b89..5c1175fcc 100644
--- a/doc/lein.1
+++ b/doc/lein.1
@@ -172,7 +172,7 @@ You can customize your project map further with profiles; see
.SH BUGS
-Check https://github.com/technomancy/leiningen/issues to see if your
+Check https://codeberg.org/leiningen/leiningen/issues to see if your
problem is a known issue. If not, please open a new issue on that site.
Please include the output of
.B lein version
diff --git a/lein-pprint/project.clj b/lein-pprint/project.clj
index 92dea4ffa..6e0cbe7c5 100644
--- a/lein-pprint/project.clj
+++ b/lein-pprint/project.clj
@@ -1,6 +1,6 @@
(defproject lein-pprint "1.3.2"
:description "Pretty-print a representation of the project map."
- :url "https://github.com/technomancy/leiningen"
+ :url "https://codeberg.org/leiningen/leiningen"
:license {:name "Eclipse Public License"
:url "http://www.eclipse.org/legal/epl-v10.html"}
:eval-in-leiningen true)
diff --git a/leiningen-core/README.md b/leiningen-core/README.md
index fa2c30d4d..43aa34a14 100644
--- a/leiningen-core/README.md
+++ b/leiningen-core/README.md
@@ -5,9 +5,6 @@ consists of the task execution implementation, project configuration,
and helper functions. The built-in tasks and the launcher scripts are
kept in the main `leiningen` project.
-More detailed [API reference](https://leiningen.org/reference.html) is
-available.
-
## Namespaces
* **leiningen.core.main** contains the `-main` entry point along with
@@ -32,7 +29,7 @@ it looks up the task which was invoked. Tasks are just functions named
after the task they implement and defined in the `leiningen.the-task`
namespace. They usually take a project map as their argument, but can
also run outside the context of a project. See the
-[plugin guide](https://github.com/technomancy/leiningen/blob/stable/doc/PLUGINS.md)
+[plugin guide](https://codeberg.org/leiningen/leiningen/blob/stable/doc/PLUGINS.md)
for more details on how tasks are written. The `apply-task` function
looks up the task function, checks to make sure it can be applied to
the provided arguments, and then calls it.
@@ -69,7 +66,6 @@ itself, there's no need to enforce this isolation.
## License
-Copyright © 2011-2021 Phil Hagelberg and
-[contributors](https://github.com/technomancy/leiningen/graphs/contributors).
+Copyright © 2011-2022 Phil Hagelberg and contributors.
Distributed under the Eclipse Public License, the same as Clojure.
diff --git a/leiningen-core/dev-resources/leiningen/downloads.clj b/leiningen-core/dev-resources/leiningen/downloads.clj
deleted file mode 100644
index 107e8933d..000000000
--- a/leiningen-core/dev-resources/leiningen/downloads.clj
+++ /dev/null
@@ -1,110 +0,0 @@
-(use '[cemerick.pomegranate :only (add-dependencies)])
-
-(add-dependencies :coordinates '[[clj-aws-s3 "0.3.6"]
- [tentacles "0.2.4"]]
- :repositories (merge cemerick.pomegranate.aether/maven-central
- {"clojars" "https://clojars.org/repo"}))
-
-(ns leiningen.downloads
- "Calculate download statistics from logs."
- (:require [aws.sdk.s3 :as s3]
- [clojure.java.io :as io]
- [tentacles.repos :as repo]
- [clojure.pprint :refer [pprint]]
- [leiningen.core.main :as main])
- (:import (java.io File)))
-
-(defn ^:internal aws-cred []
-
- ;; in order to run, you need to define a map with the appropriate AWS
- ;; credentials in ~/.secrets/leiningen_downloads_aws_cred.clj:
-
- ;; {:access-key "AWS_ACCESS_KEY"
- ;; :secret-key "AWS_SECRET_KEY"}
- (let [f (File. (System/getenv "HOME")
- "/.secrets/leiningen_downloads_aws_cred.clj")]
- (if (.exists f)
- (read-string (slurp f))
- (main/abort "Missing credentials file:" f))))
-
-(defn- list-all-objects
- [bucket & [objects next-marker]]
- (let [response (s3/list-objects (aws-cred) bucket {:marker next-marker})
- truncated? (:truncated? response)
- next-marker (:next-marker response)
- objects (concat objects (:objects response))]
- (if (not truncated?)
- objects
- (recur bucket [objects next-marker]))))
-
-(defn- fetch-all-objects
- [bucket]
- (for [object (list-all-objects bucket)]
- (do
- (println (str "Processing: " (:key object)))
- (s3/get-object (aws-cred) bucket (:key object)))))
-
-(defn- file-for-line
- [line]
- (let [[_ file] (re-find #"\"GET ([^ ]+) " line)]
- (if file
- (last (.split file "/")))))
-
-(defn- ip-for-line
- [line]
- (re-find #"\b(?:[0-9]{1,3}\.){3}[0-9]{1,3}\b" line))
-
-(defn- status-for-line
- [line]
- (second (re-find #"\" (\d\d\d)" line)))
-
-(defn- parse-files
- [content]
- (with-open [rdr (io/reader content)]
- (doall (for [line (line-seq rdr)]
- {:file (file-for-line line)
- :status (status-for-line line)
- :ip (ip-for-line line)}))))
-
-(defn- s3-downloads
- []
- (flatten
- (for [logfile (map :content (fetch-all-objects "leiningen-logs"))]
- (filter #(and (get % :file) ;; file is present
- (re-find #"\.jar\b" (get % :file)) ;; file is a jar
- (= "200" (get % :status))) ;; and only HTTP 200 responses
- (parse-files logfile)))))
-
-(defn- github-downloads
- []
- (reverse
- (sort-by #(first (vals %))
- (filter #(re-find #"\.jar$" (first (keys %)))
- (let [downloads {}]
- (for [download (repo/downloads "technomancy" "leiningen")]
- (assoc downloads
- (:name download)
- (:download_count download))))))))
-
-(defn ^:no-project-needed downloads [project]
- (let [s3-downloads (s3-downloads)
- s3-download-count (count s3-downloads)
- github-downloads (github-downloads)
- github-download-count
- (reduce + (map #(first (vals %)) github-downloads))]
- (println (str "GitHub Downloads: " github-download-count))
- (println (str "S3 Downloads: " s3-download-count))
- (println (str "Unique IP Addresses (S3 Downloads Only): "
- (count (distinct (map :ip s3-downloads)))))
- (println (str "Total Downloads: "
- (+ github-download-count s3-download-count)))
- (print "\n\n")
- (println "GitHub downloads by file:")
- (print "\n\n")
- (pprint github-downloads)
- (print "\n\n")
- (println "S3 downloads by file:")
- (print "\n\n")
- (pprint (frequencies (map :file s3-downloads)))
- (println ""))) ;; need this last println for some reason or else
- ;; the above doesn't print out using lein run...
diff --git a/leiningen-core/project.clj b/leiningen-core/project.clj
index 52f4fb745..908eb7fef 100644
--- a/leiningen-core/project.clj
+++ b/leiningen-core/project.clj
@@ -1,5 +1,5 @@
(defproject leiningen-core "2.9.9-SNAPSHOT"
- :url "https://github.com/technomancy/leiningen"
+ :url "https://codeberg.org/leiningen/leiningen"
:license {:name "Eclipse Public License"
:url "http://www.eclipse.org/legal/epl-v10.html"}
:description "Library for core functionality of Leiningen."
diff --git a/leiningen-core/src/leiningen/core/main.clj b/leiningen-core/src/leiningen/core/main.clj
index 72a3c0a10..1b199377e 100644
--- a/leiningen-core/src/leiningen/core/main.clj
+++ b/leiningen-core/src/leiningen/core/main.clj
@@ -434,7 +434,7 @@ Get the latest version of Leiningen at https://leiningen.org or by executing
(abort "Tried to use insecure HTTP repository without TLS:\n"
(str (.getId @repo) ": " (.getUrl @repo) "\n " resource) "\n"
"\nThis is almost certainly a mistake; for details see"
- "\nhttps://github.com/technomancy/leiningen/blob/master/doc/FAQ.md")))))
+ "\nhttps://codeberg.org/leiningen/leiningen/blob/main/doc/FAQ.md")))))
(defn -main
"Command-line entry point."
diff --git a/leiningen-core/src/leiningen/core/project.clj b/leiningen-core/src/leiningen/core/project.clj
index 59f981920..029df99ae 100644
--- a/leiningen-core/src/leiningen/core/project.clj
+++ b/leiningen-core/src/leiningen/core/project.clj
@@ -701,7 +701,7 @@
(not (System/getenv "LEIN_SUPPRESS_USER_LEVEL_REPO_WARNINGS")))
(warn-once ":repositories detected in user-level profiles!"
(vec (map first repo-profiles)) "\nSee"
- "https://github.com/technomancy/leiningen/wiki/Repeatability"))))
+ "https://codeberg.org/leiningen/leiningen/wiki/Repeatability"))))
(defn- warn-user-profile [root profiles]
(when (and root (contains? profiles :user))
diff --git a/project.clj b/project.clj
index 9a3769f15..3ae08c697 100644
--- a/project.clj
+++ b/project.clj
@@ -3,7 +3,7 @@
(defproject leiningen "2.9.9-SNAPSHOT"
:description "Automate Clojure projects without setting your hair on fire."
- :url "https://github.com/technomancy/leiningen"
+ :url "https://codeberg.org/leiningen/leiningen"
:license {:name "Eclipse Public License"
:url "http://www.eclipse.org/legal/epl-v10.html"}
;; If you update these, update resources/leiningen/bootclasspath-deps.clj too
diff --git a/sample.project.clj b/sample.project.clj
index 6404be22e..6c7996c63 100644
--- a/sample.project.clj
+++ b/sample.project.clj
@@ -520,7 +520,7 @@
;; Dictate which git branches deploys should be allowed from. When set,
;; `lein deploy` will only work from the git branches included and will
;; abort otherwise.
- :deploy-branches ["master"]
+ :deploy-branches ["main"]
;;; Artifact Classifers Installation
;; Option to install classified maven artifacts. A map where keys
diff --git a/src/leiningen/plugin.clj b/src/leiningen/plugin.clj
index 444fbc5e7..028e05d6c 100644
--- a/src/leiningen/plugin.clj
+++ b/src/leiningen/plugin.clj
@@ -8,4 +8,4 @@
(main/abort "The plugin task has been removed.\n"
"\nPlease see the upgrade guide for instructions on how to use"
"the user profile to\nspecify plugins instead:"
- "https://github.com/technomancy/leiningen/wiki/Upgrading"))
+ "https://codeberg.org/leiningen/leiningen/wiki/Upgrading"))
diff --git a/src/leiningen/pom.clj b/src/leiningen/pom.clj
index 3a9f346f3..a523ce6eb 100644
--- a/src/leiningen/pom.clj
+++ b/src/leiningen/pom.clj
@@ -110,7 +110,7 @@
"\n\n")
+ https://codeberg.org/leiningen/leiningen -->\n")
(defn- camelize [string]
(s/replace string #"[-_](\w)" (comp s/upper-case second)))
diff --git a/web/grench.html b/web/grench.html
index ccb206b07..262b53b4c 100644
--- a/web/grench.html
+++ b/web/grench.html
@@ -53,10 +53,8 @@ Please report - issues on - GitHub or - the Leiningen mailing - list.
+ issues on + GitLab or on IRC.Source - and issues + and issues are - tracked on - GitHub.
+ tracked on + GitLab.You can check - your package + your package manager as well depending on your operating system.
@@ -97,7 +97,7 @@The tutorial +
The tutorial is the best place to start. If you have Leiningen installed, you can read the tutorial by running lein help tutorial. It does not cover learning the @@ -107,18 +107,18 @@
Running lein help faq will get you the - FAQ. + FAQ. Documentation for each individual task is available via lein help $TASK. You can also - see the + see the sample project.clj file containing a reference of most project settings by running lein help sample.
More: - profiles | - deploying libraries | - writing plugins | - plugin list + profiles | + deploying libraries | + writing plugins | + plugin list
@@ -132,22 +132,22 @@Discussion occurs primarily in - the #leiningen channel on Libera.Chat.
+ the #leiningen channel + on Libera.Chat.Issues should - be reported - on the GitHub issue tracker.
+ be reported + on the issue tracker.