Finally I was able to resolve this issue On DOS if number of source files or classpath entries are too many we get an error "Line too Long" and this breaks compiling using jdk1.3 using fork.
To shorten the options and source files to javac command we can use javac @options @class <other options) in my solution file options contain list of all the classpath entries and @class contains list of all .java files that needs to be compiled. I made changes to AbstractCompilerMojo.java in maven-compiler-plugin ( 2.0.1-SNAPSHOT) and JavacCompiler in plexus-compiler-java (1.6-SNAPSHOT). These changes will kick into play only if fork = true. After this change I was able to compile project with over 2000 java files Now questions, 1. How can I share my code with maven group, this will enable us to close bug http:/jira/codehaus.org/browse/MCCOMPILER-22? 2. How can I share these maven jars with my other team members?(need to do tomorrow morning . I will hate to email them these new versions of jars. Is there a way I can install them in my companies snapshot repository? (This will involve adding distribution entries in POM.xml for both the projects. Is it OK?). Any suggestions/ideas. Please advice. Cheers, Sanjay On 3/11/06, Sanjay Choudhary <[EMAIL PROTECTED]> wrote: > On Windows XP ( haven't tried it on unix or linux as yet) I get "line too > long" error. This only happens for the projects that have more than 40 > files or classpath entries are too many. > > Is there a way I can fix this? Please advice. > > cheers, > Sanjay >
