| Issue 118: | JMesa Build Fails on Groovy 1.5 | |
| 1 person starred this issue and may be notified of changes. | Back to list |
What steps will reproduce the problem? 1. Install Groovy 1.5 2. Checkout JMesa trunk 3. in jmesa directory, run - $ groovy build.groovy -a dist The build tries to create a directory called dist/['jmesa']-snapshot/... I guess an older version of groovy coerced the ['jmesa'] structure into a string when the Artifact is created. It looks groovy 1.5 does not do this (I'm not a groovy expert though). The attached patch adds some type safety to the Artifact constructor to make sure that this does not happen. What version of the product are you using? On what operating system? `groovy -v` = Groovy Version: 1.5.6 JVM: 1.5.0_14-b03
Jul 17, 2008
#1
extremec...@gmail.com
Jul 18, 2008
Here is the output from the build:
C:\bgould\jmesa\trunk\jmesa>build -a dist
Enter a revision number: [snapshot]
[delete] Deleting directory C:\bgould\jmesa\trunk\jmesa\target
[mkdir] Created dir: C:\bgould\jmesa\trunk\jmesa\target
[mkdir] Created dir: C:\bgould\jmesa\trunk\jmesa\target\classes
[mkdir] Created dir: C:\bgould\jmesa\trunk\jmesa\target\docs
Caught: : Directory C:\bgould\jmesa\trunk\jmesa\target\dist\["jmesa"]-snapshot c
reation was not successful for an unknown reason
at Build.init(build.groovy:42)
at Build.dist(build.groovy:196)
at Build.invokeMethod(build.groovy)
at Build.main(build.groovy:240)
C:\bgould\jmesa\trunk\jmesa>
Jul 18, 2008
I wonder if its a windows problem... I can try it at home too. The problem still occurs in MSYS though
Jul 19, 2008
I verified that this problem occurs on Windows XP, but not on Linux.
Jul 21, 2008
Thanks for the verification! It would nice to figure out why this fails on Windows. I do not have a Windows box accessible right now. Maybe I could borrow a co-workers box some night. If you get it to work can you let me know?
Status:
Accepted
Jul 22, 2008
Adding 'String' to the signature of the Artifact constructor solved the problem. It is perplexing why it failed though. Also, the javadoc task failed on jdk1.5.0_14 because of a missing resource bundle (probably a JDK bug), but worked fine when I upgrade to 1.6.0_07. I think this is safe to close, as the build file in trunk seems to work fine now.
Jul 22, 2008
Thanks for your help!
Status:
Fixed
|