Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-core-dev] Poll about new Java builder setting

Questions:

1. Does this setting apply to both Full & Incremental builds?

2. When exactly is the build aborted? Is the project's bin folder scrubbed 
before aborting the build? Is the project's build state deleted (causing 
Full builds next time)?

3. What's the point in building dependent projects if a prereq project's 
build was aborted because of class path problems? What's in the prereq 
project's bin folder?

4. Do ALL types of classpath problems abort the build (Unbound variables, 
closed/missing projects, missing jar files, etc.)? Or are some problems 
ignored?





Philippe_Mulet@xxxxxxx
Sent by: jdt-core-dev-admin@xxxxxxxxxxx
05/03/2002 07:59 AM
Please respond to jdt-core-dev

 
        To:     jdt-core-dev@xxxxxxxxxxx
        cc: 
        Subject:        Re: [jdt-core-dev] Poll about new Java builder setting


When building several projects, only the one with the classpath problem
would be aborted.



  
                      Daniel_Megert@oti.c   
                      om                          To: 
jdt-core-dev@xxxxxxxxxxx 
                      Sent by:                    cc:    
                      jdt-core-dev-admin@         Subject: Re: 
[jdt-core-dev] Poll about new Java builder setting 
                      eclipse.org   
  
  
                      05/03/2002 06:50 AM   
                      Please respond to   
                      jdt-core-dev   
  
  




For me it depends on what I'm doing:
- if I choose to rebuild all then I would like to really get the full job
done (maybe it's just one out of 20 projects that has a wrong build path)
- if I build one project (with its required stuff) then it would probably
be better to stop.

Dani

 
   Philippe_Mulet@xxxxxxx 
   Sent by:                            To: 
   jdt-core-dev-admin@eclipse. jdt-core-dev@xxxxxxxxxxx 
   org                                 cc: 
                                       Subject:        [jdt-core-dev] 
                               Poll about new Java builder setting 
   05/02/02 07:56 PM 
   Please respond to 
   jdt-core-dev 
 




We are adding a new Java builder setting for aborting in presence of an
invalid project classpath.
Currently, the builder doesn't abort under such circumstances, and might
generate a huge number of errors.

Question is: what should the default be ?


     JavaCore option added, to allow build to abort in presence of invalid
     classpath.
                   * BUILDER / Abort if Invalid Classpath
                   *    Allow to toggle the builder to abort if the
     classpath is invalid
                   *     - option id:
     "org.eclipse.jdt.core.builder.invalidClasspath"
                   *     - possible values:  { "abort", "ignore" }
                   *     - default:          "ignore"


_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev





_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev





Back to the top