Autoderiving multiple nested Maven projects

[eaaltonen]

I am having trouble configuring AutoDeriv rules for a nested multi-module Maven project. The project is structured like.

parent0
+-parent1
¦ +-moduleA
¦ +-moduleB
+-root1

The rules I want should be roughly as follows:

• Mark all 'target' directories derived everywhere
• For directories 'parent0' and 'parent1', mark all subdirectories as derived

I made a quick sketch of the structure at https://github.com/eaaltonen/autoderiv-nested-modules/tree/master

[tchegito]

I'm interested in that feature too. I tried to add "*" in .derived file on the parent project. It quite works, but sometimes when I save a ".derived" file Eclipse hangs and I'm forced to shut it down badly. This is surely not the best approach but I can't figure it out.

Rumor has it that Eclipse Mars has the feature "hide folders of physically nested module" not experimental anymore and really working. But I haven't checked right now.

[jebeaudet]

Also interested in this feature. The solution provided by @tchegito (thanks!) works in my case, I've put a .derived file in the pom project with this :

*
!pom.xml

This marks all the folders as derived but keep the parent pom so I can modify it.

[thomasschuerger]

I have a similar problem. I have a parent project with multiple child projects. The parent project also contains some additional files/folders.

The project hierarchy is like this:

parentproject

• childproject1
• childproject2

Each child project has a .derived file. This makes the Open Resource dialog in Eclipse hide the derived files from these projects. However, the derived files still show up as part of the parent project.

To fix this I have to create a .derived file for the parent project, which contains the same contents of both child projects, each prefixed with the child project folder name.

For example, if child project 1 and 2 both contain "target" in their .derived file, the parent .derived file must contain "childproject1/target" and "childproject2/target" to make Open Resource behave as expected.

Pretty silly that this is necessary. Or am I doing something wrong?