Martin Klepsch
Martin Klepsch
I think I pronounce it quite similarly, it's pretty close to how you'd pronounce it if you'd say it "in German".
I was just thinking that if perun encourages people to extend it with other tasks there probably should be some convention about how/where they store task related data. Given we...
> E.x. now renderer task function should be aware of markdown/html. I see your general point but doesn't the renderer function now equally need to be aware of `:content`? >...
@podviaznikov I'll think about this a bit more but one thing to keep in mind is that the `render` task does not directly use `:content`, only the function supplied as...
@Deraen do you have thoughts on establishing some sort of convention for tasks and the keys in metadata they're writing to?
Reproduction snippet: ``` boot -d hiccup pom -p testing.org/xxx -v 0.0.1 uber jar push --repo "clojars" --file "project.jar" ```
If you fix the above snippet by using the `target` task you still run into the issue that there most likely will be multiple `pom.xml` ``` boot -d hiccup -C...
This in turn means that you will need to supply the path to the `pom.xml` manually. If you make a typo this is the error: ``` clojure.lang.ExceptionInfo: entry data: {:file...
So currently what you need to do is this: ``` boot -d hiccup -C \ pom -p foo/bar -v 0.0.1 \ uber \ jar \ target \ push --repo "clojars"...
The push task is able to properly find the jar so supplying `:file` isn't needed as often. If you build uberjars you will need to supply the pom.xml path however....