[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-ui-dev] New builder error in JDT?
|
Great. I will use Darin's suggestion to have our plugin define additional
filters, and enter a bugzilla request to have the filter support entire
folders.
Thanks guys.
Stef
Daniel_Megert@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/16/2002 03:08
AM
Please respond to
jdt-ui-dev
2.0 JAR Packager takes non-class files from source.
Dani
Stef_van_Dijk@xxxxxxx
Sent by: To: jdt-ui-dev@xxxxxxxxxxx
jdt-ui-dev-admin@xxxxxxxxxxx
cc:
Subject: Re: [jdt-ui-dev]
04/15/02 07:45 PM New builder error in JDT?
Please respond to jdt-ui-dev
I saw that (in the Java->Builder Preferences), but had two concerns that
maybe you could address.
First, I would prefer to be able to filter a directory, namely META-INF,
rather than individual files. We currently support/manage at least 5 unique
file names from that directory and the list is growing.
Second, what happens if the file is not copied to the output location but
the user requests it be in the jar? From past experience, it seems the jar
packager takes files from the output location. So if it's not there, will
it use the one from the source folder, or simply not output it at all?
Either way won't impact our plugin as we handle the META-INF files
ourselves and in fact take them from the source folder. However, since the
filter is a global setting, I'm concerned as to what would happen for
projects that are not handled by our plugin support. I'm particularly
sensitive about this since one of the files involved would be manifest.mf.
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
Stef_van_Dijk@xxxxxxx
Sent by: To:
jdt-ui-dev-admin@xxxxxxxxxxx jdt-ui-dev@xxxxxxxxxxx
cc:
Subject: [jdt-ui-dev] New
04/15/02 10:29 AM builder error in JDT?
Please respond to jdt-ui-dev
Not sure how new this is, but I never noticed this in Eclipse 1.0, and only
just saw it with the 4/12 Integration Build.
Our plugin allows a project structure where files (specifically files
contained in the META-INF directory (ie, non-java files)) can overlap by
having them in separate source folders. We "manage" the overlap with our
submit (jar-like) operation which will package up the files from the
correct source folder. This is a significant feature for our plugin and is
currently used by WSDD developers. The problem is that in the current
Eclipse builds, I now get the following error for all the overlapping
files:
"This resource is a duplicate and was not copied to the output folder"
This is placing red error markers on these files, while in our context,
these are not errors at all. I'm at a loss as to how to cope with this
change. I don't see any way of surpressing or filtering this error for our
customers. Does anyone have any suggestions on how to deal with this?
Stef
_______________________________________________
jdt-ui-dev mailing list
jdt-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev
_______________________________________________
jdt-ui-dev mailing list
jdt-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev
