Clojurians Log v2
clojure-dev
I can make a jar with mvn package -Dmaven.test.skip and test with mvn test when screening tickets. But I see there’s a build.xml that seems to have lots of useful stuff in it, but that seems to not construct a classpath that includes clojure spec. Is build.xml outdated or am I not setting it up correctly?
what problem are you trying to solve?
The proper way to run tests and make a jar which includes changes. I saw that mvn test was listed in the documentation about screening tickets but not how to properly create a jar.
mvn test and mvn package are the proper way to run tests and package the jar
that is what CI does during build and release
oh i see it now in
the Ant build.xml is used (by the Maven build) but I would not recommend running it directly. there is a lot of history about how it ended up here. I have spiked a full Maven replacement (ow) and we've more recently looked at replacing it with tools.build, but hard to prioritize replacing a thing that works, however tortured it may be
> hard to prioritize replacing a thing that works, however tortured it may be the saddest truth
Makes sense. I just didn’t quickly notice how to make a jar and saw a “build.xml” which seemed to invite me to use its tasks. And wanted to know if I was doing it wrong. Thanks for the information.
https://clojure.atlassian.net/browse/CLJ-2617 bit me again when doing a seemingly non-breaking update of a java dependency's version. While reify is recommended over proxy in most cases, proxy remains the only solution for extending classes which doesn't require AOT (as per https://puredanger.github.io/tech.puredanger.com/2011/08/12/subclassing-in-clojure/ )
https://ask.clojure.org/index.php/10383/using-proxy-might-make-otherwise-additive-change-breaking has just one vote, so would be interested to know if anyone else has encountered this
Perhaps others have found a way to avoid this problem, I'd be interested in solutions if that's the case