Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-ui-dev] New builder error in JDT?

Actually Darin, your code example (which is the same as the 4/12
Integration build code) has a couple of problems.
First, you need to check the filters string for null after the
optionsMap.get(). In my workspace, the result of your method causes the
filter to be set to "null,*.launcher" because the filter had no initial
setting.
Second, your map key isn't quite right. It's "Filter" (singular), not
"Filters". Would have been nice if there were reusable constants defined
for the options somewhere.

   Stef



                                                                                                                                         
                      Darin_Swanson@oti                                                                                                  
                      .com                      To:      jdt-ui-dev@xxxxxxxxxxx                                                          
                      Sent by:                  cc:                                                                                      
                      jdt-ui-dev-admin@         Subject: Re: [jdt-ui-dev] New builder error in JDT?                                      
                      eclipse.org                                                                                                        
                                                                                                                                         
                                                                                                                                         
                      04/15/2002 01:19                                                                                                   
                      PM                                                                                                                 
                      Please respond to                                                                                                  
                      jdt-ui-dev                                                                                                         
                                                                                                                                         
                                                                                                                                         




Stef,

You can specifically restrict which files are copied to the output
location.
@see JavaCore.getOptions() and the example below from the launching plugin
which excludes all files with the launch configuration file extension:

Hashtable optionsMap = JavaCore.getOptions();
                String filters= (String)optionsMap.get(
"org.eclipse.jdt.core.builder.resourceCopyExclusionFilters"); //$NON-NLS-1$

                filters= filters + ",*." +
ILaunchConfiguration.LAUNCH_CONFIGURATION_FILE_EXTENSION; //$NON-NLS-1$
                optionsMap.put(
"org.eclipse.jdt.core.builder.resourceCopyExclusionFilters", filters);
//$NON-NLS-1$
                JavaCore.setOptions(optionsMap);

Darins





Back to the top