[CLJ-1014] Latest Clojure master doesn't build Created: 14/Jun/12 Updated: 20/Jul/12 Resolved: 20/Jul/12 |
|
| Status: | Closed |
| Project: | Clojure |
| Component/s: | None |
| Affects Version/s: | Release 1.5 |
| Fix Version/s: | None |
| Type: | Defect | Priority: | Major |
| Reporter: | Edward Z. Yang | Assignee: | Unassigned |
| Resolution: | Declined | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Ubuntu 10.10 Maverick |
||
| Description |
|
Compile fails with the following error: compile-clojure: |
| Comments |
| Comment by Andy Fingerhut [ 14/Jun/12 11:42 AM ] |
|
What command did you use? From the error message, my guess is that you ran "ant" without first running "./antsetup.sh". If that is the case, run "./antsetup.sh" first. This is a new step added to readme.txt on May 7, 2012, because of the jsr166y.ForkJoinPool class used within Clojure to implement the new parallel reducers feature. |
| Comment by Edward Z. Yang [ 14/Jun/12 2:16 PM ] |
|
Yep, that's exactly it. Can we setup ant to warn people if antsetup.sh hasn't been run? |
| Comment by Andy Fingerhut [ 14/Jun/12 5:12 PM ] |
|
I don't know. I suspect if it could be done and it were a straightforward modification, a patch for that would be accepted. I suspect those who created antsetup.sh would have simply modified the build.xml file for ant, and not created antsetup.sh at all, if it were easy to do so. |
| Comment by Roy Truelove [ 26/Jun/12 3:58 PM ] |
|
It can be done with just the build.xml but requires the Maven Ant Tasks jar to be in the local ant's classpath, which is not ideal. Because a local maven install is anyway required by antsetup.sh, IMHO it would be best to remove the ant build all together and stick with solely with a maven build, no? |
| Comment by Andy Fingerhut [ 27/Jun/12 1:16 PM ] |
|
I can't find the email right now, but I believe in the past Rich Hickey has expressed a preference for continuing to have a way to build Clojure using ant. |
| Comment by Stuart Halloway [ 20/Jul/12 4:49 PM ] |
|
Ant is there for the convenience of various dinosaurs, myself included. In general you should use the maven build, as that is what the CI and release process do. |