MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013161CMakeCMakepublic2012-04-23 13:282012-09-09 10:45
ReporterFrank Glinka 
Assigned ToRolf Eike Beer 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformWindowsOSWindowsOS Version7
Product VersionCMake 2.8.8 
Target VersionFixed in Version 
Summary0013161: Java support can violate the command-line string limitation
DescriptionCurrently, the add_jar function composes a single command-line expression which invokes javac and passes all java files as command-line arguments.

As soon as the number of Java files gets bigger and/or the files are placed in folders with long path names, the system limit for command-line expressions is easily reached.
Steps To ReproduceCreate a medium-sized java project with long path names to the Java files.
Additional InformationThe Java compiler allows to provide a file as a program argument which lists the source files to be compiled. This might be the better choice:

http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.html [^]
TagsNo tags attached.
Relationships
duplicate of 0013028closed Brad King UseJava.cmake add_jar generated command line too long for nmake 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-04-23 13:28Frank GlinkaNew Issue
2012-04-25 05:26Nils GladitzNote Added: 0029332
2012-04-25 05:30Frank GlinkaNote Added: 0029333
2012-08-11 21:35David ColeStatusnew => backlog
2012-08-11 21:35David ColeNote Added: 0030411
2012-09-09 10:44Rolf Eike BeerRelationship addedduplicate of 0013028
2012-09-09 10:45Rolf Eike BeerStatusbacklog => closed
2012-09-09 10:45Rolf Eike BeerAssigned To => Rolf Eike Beer
2012-09-09 10:45Rolf Eike BeerResolutionopen => duplicate

Notes
(0029332)
Nils Gladitz   
2012-04-25 05:26   
duplicate of 0013028 ?
(0029333)
Frank Glinka   
2012-04-25 05:30   
Correct! So this one can be closed as being a duplicate, sorry.
(0030411)
David Cole   
2012-08-11 21:35   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.