Here is a Gradle script modification that uses relative paths to fix the issue. This link is a reference to the issue in the old forums. I have encountered a similar issue with the generated start up scripts from the Application plugin and in particular the Spring Boot plugin where the classpath created results in an “Input too long” error. But at the moment, I feel that its not viable in its current state as even adding few extra command line arguments is going to break this in Windows. Ideally I would love to use Gradle to just run my app gradle run. For e.g I could see that classpath is pointing to a cached folder \fontbox\1.8.1` 32879bb6bb87b15c6d53bc358e83ede40fc729ae`\fontbox-1.8.1.jar Is there a way to shorten some paths that gradle adds. ( I think what I’m working on is relatively small considering other big java apps I have seen). What’s the prescribed way to run applications that have a huge dependency graph.I worked around it by shortening the path to my code and java executable location, While this was Ok for sometime, I hit that limit again today when I added few command line argument. I ran in to an error java.io.IOException: CreateProcess error=206, The filename or extension is too long because of a really long classpath dependencies. I am beginning to move my maven based project to a gradle based java application that runs on Windows 7.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |