mark contents of "target" directory as derived

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 2.2
  • Fix Version/s: 2.2
  • Component/s: None
  • Labels:
    None

Description

Eclipse has the notion of "derived resources", which are normally excluded from many dialogs like the "Open Resource" dialog (Ctrl-Shift-R). Without this marker, all those dialogs would be cluttered with unrelevant files (which can't be edited anyway because they will be overwritten on the next build).

Unfortunately, unlike Eclipse itself, "mvn eclipse:eclipse" does not mark generated files as derived. A good candidate would be the entire contents of the "target" directory.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MECLIPSE-469 CLONE -mark contents of "target" directory as derived

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
fabrizio giustina added a comment -

the "derived resource" marker is not applied by eclipse on the output directory. Such marker is added by eclipse itself when a java file is compiled to a class file or any file is copied from the src to the target directory.
This means that project resources are marked as derived when compiling from eclipse, but not when the project is built by maven (since maven would have to mark each single file, and this has to be done in the .metadata directory in the eclipse workspace).

Show
fabrizio giustina added a comment - the "derived resource" marker is not applied by eclipse on the output directory. Such marker is added by eclipse itself when a java file is compiled to a class file or any file is copied from the src to the target directory. This means that project resources are marked as derived when compiling from eclipse, but not when the project is built by maven (since maven would have to mark each single file, and this has to be done in the .metadata directory in the eclipse workspace).
Hide
Permalink
Joris Verschoor added a comment -

Please reopen.
It IS annoying when you're presented duplicate files, which are copies of the originals.

You might not notice with .classfiles if your eclipse output dir is the same as the maven classes dir, but that can be overridden by setting the buildOutputDirectory option)
Also, when working with webapplications, people tend to have a lot of non-java files (jsps, configurations, images etc)

the derived flag SHOULD be set for derived resources, which everything under 'target' is

Show
Joris Verschoor added a comment - Please reopen. It IS annoying when you're presented duplicate files, which are copies of the originals. You might not notice with .classfiles if your eclipse output dir is the same as the maven classes dir, but that can be overridden by setting the buildOutputDirectory option) Also, when working with webapplications, people tend to have a lot of non-java files (jsps, configurations, images etc) the derived flag SHOULD be set for derived resources, which everything under 'target' is
Hide
Permalink
Richard Bondi added a comment -

+1
Please reopen.

Show
Richard Bondi added a comment - +1 Please reopen.
Hide
Permalink
Thomas Ferris Nicolaisen added a comment -

+1 on the re-open.

Perhaps it's not correct to use target/derived technique directly if this is hard to achieve by manipulating Eclipse's meta-data.

What we want is simply not to encounter build directory resources when (1) opening resources, and (2) while searching (optionally).

Show
Thomas Ferris Nicolaisen added a comment - +1 on the re-open. Perhaps it's not correct to use target/derived technique directly if this is hard to achieve by manipulating Eclipse's meta-data. What we want is simply not to encounter build directory resources when (1) opening resources, and (2) while searching (optionally).
Hide
Permalink
Arnaud Heritier added a comment -

I reopen to mark that the need is always here. It's not because we will fix it (we have to find how to do it easily)

Show
Arnaud Heritier added a comment - I reopen to mark that the need is always here. It's not because we will fix it (we have to find how to do it easily)
Hide
Permalink
Arnaud Heritier added a comment -

reclose it. I'll clone it

Show
Arnaud Heritier added a comment - reclose it. I'll clone it
Hide
Permalink
Karl Pietrzak added a comment - - edited

I just wanted to let everyone know that this is a much-requested Eclipse feature.

Basically, you can only set resources in Eclipse as Derived programaticly, i.e., there is no project setting. In fact, it's stored in the workspace metadata.

Show
Karl Pietrzak added a comment - - edited I just wanted to let everyone know that this is a much-requested Eclipse feature. Basically, you can only set resources in Eclipse as Derived programaticly, i.e., there is no project setting. In fact, it's stored in the workspace metadata.
Hide
Permalink
Karl Pietrzak added a comment -

For the interested, we will finally be able to add mark 'target' and others are derived because of Eclipse bug 207510, which creates a org.eclipse.core.resources.prefs.

Unfortunately, it won't make it before Eclipse 3.7 M3, but I'm gonna start working on this.

Show
Karl Pietrzak added a comment - For the interested, we will finally be able to add mark 'target' and others are derived because of Eclipse bug 207510, which creates a org.eclipse.core.resources.prefs. Unfortunately, it won't make it before Eclipse 3.7 M3, but I'm gonna start working on this.

People

  • Assignee:
    Unassigned
    Reporter:
    Andreas Schildbach
Vote (0)
Watch (5)

Dates

  • Created:
    Updated:
    Resolved: