Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

missing target task #6

Open
jgrzebyta opened this issue May 26, 2016 · 4 comments
Open

missing target task #6

jgrzebyta opened this issue May 26, 2016 · 4 comments

Comments

@jgrzebyta
Copy link

jgrzebyta commented May 26, 2016

Documentation should be updated regarding boot v 2.6.0 release.

I found that in my project all building tasks required adding target task to the chain. Otherwise final jar was built within temporary ~/.boot/cache/tmp/...... directory and was not synced with the final target.

For example:

(deftask build-standalone
  "Build standalone version" []
  (comp
   (pom)
   (aot)
   (uber)
   (jar :file (format "%s-%s-standalone.jar" (name (get-env :project))
                      (get-env :version)))
   (target)))
@martinklepsch
Copy link
Member

Hey @jgrzebyta! 👋 What documentation are you referring to here? Most of the docs are in the Boot wiki and not on the website.

@micha
Copy link

micha commented May 26, 2016

Sorry yes, documentation and changelog are lagging behind the 2.6.0 release. That is a change that needs to be documented.

@jgrzebyta
Copy link
Author

I look over wiki pages and it seems nothing requires change apart adding
that task to the builts-in list. Also README file needs to be change.

On 26 May 2016 at 16:44, Martin Klepsch [email protected] wrote:

Hey @jgrzebyta https://github.com/jgrzebyta! 👋 What documentation are
you referring to here? Most of the docs are in the Boot wiki
https://github.com/boot-clj/boot and not on the website.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6 (comment)

@burn2delete
Copy link
Contributor

As a note I believe checkout also needs documentation as the task is now deprecated in favour of the env var.

Maybe a community documentation push weekend could be arranged in preparation for v2.6?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants