New files are added as derived although they should not be

[Ginbob]

Hi Johan,

first of all thanks for this plug in, good work.
The only issue i have is the following:

I adjusted the .derived files in all my maven projects and files that should be derived are marked as derived. So that perfectly works. But whenever I add a new file, it is automatically marked as derived, although it should not be...

Is this a side effect or am I just missing a simple property somewhere?

Best regards

[nodj]

Hello Ginbob,

This is not expected, there is no hidden property about this :)
Can you paste here the content of your .derived file ?

Le 16 sept. 2016 06:58, "Ginbob" notifications@github.com a écrit :

Hi Johan,

first of all thanks for this plug in, good work.
The only issue i have is the following:

I adjusted the .derived files in all my maven projects and files that
should be derived are marked as derived. So that perfectly works. But
whenever I add a new file, it is automatically marked as derived, although
it should not be...

Is this a side effect or am I just missing a simple property somewhere?

Best regards

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHlsYW84WJLnnwbCvQhE6xPaiTfTWJ26ks5qqnZmgaJpZM4J-0mJ
.

[Ginbob]

Hello Johan,

thanks for your quick answer.
I think I found the problem here... We have a project hierarchy with maven projects nested in other maven projects - up to 3 levels.
So, project A (level 1) has sub projects AA, AB, AC, ...
AA has sub projects AAA and AAB
AB has sub projects ABA and ABB
AC --> ACA, ACB, ...
and so on

Our goal is to set everything to derived but the "last level projects" (like AAA, AAB, ...) and the target folder for all maven projects. Another problem regarding this, is the fact that not every last level project is a level 3 project, it could also be a level 2 project like AA.

Now that I write about it and see a .derived file like this for project A: ...

*
!pom.xml
!.project
!AA\pom.xml
!AB\pom.xml
!AC\pom.xml

... it is clear to me that the * activates autoDeriv for all files and folders in folder A, its sub folders and all files in them except for the files specified...

We just need to find a way to work this out without having a .derived file in every single project because of maintenance reasons.

We also configured working sets in eclipse. I don't know if this plugin is applicable for eclipse working sets... My guess is that this is not (yet? ;) ) the case.

[Finomosec]

Hello,

i have a very similar problem.

I have a folder: builds/mapping and in there are *.map files.

I have tried several things but, the derived rule seems to work only sometimes.
I want these files to be NOT derived.

I have one .derived file in my project root (next to builds):

# Config for eclipse plugin: https://nodj.github.io/AutoDeriv/
!builds/mapping/*.map

and because it did not work, i have another one inside the mapping folder:

# Config for eclipse plugin: https://nodj.github.io/AutoDeriv/
!*.map

These map-files are being generated by an external (to eclipse) tool.
And sometimes they are marked as derived and sometimes they are not.

But it is very frustrating, since i go through this process every couple of days and sometimes even several times per day. And each time i need to manually go into the folder and mark 2 files as not derived...

Is there any way to get debug logs in order to analyze this further?

And can you please fix this?

[nodj]

Unfortunately I don't have more time allocated on this project. I'd accept PR but I'm no longer setup to improve workflows on eclipse. A *guess* for a possible cause of your issue: - new version of eclipse with different file handling - file not 'seen' by eclipse for a path config reason - files handled by an other plugin that affects their states I'm sorry to let you down there, and clearly understand your frustration... My apologies, nodj

…

On Wed, Jul 17, 2019, 06:21 Finomosec ***@***.***> wrote: Hello, i have a very similar problem. I have a folder: builds/mapping and in there are *.map files. I have tried several things but, the derived rule seems to work only sometimes. I want these files to be NOT derived. I have one .derived file in my project root (next to builds): # Config for eclipse plugin: https://nodj.github.io/AutoDeriv/ !builds/mapping/*.map and because it did not work, i have another one inside the mapping folder: # Config for eclipse plugin: https://nodj.github.io/AutoDeriv/ !*.map These map-files are being generated by an external (to eclipse) tool. And sometimes they are marked as derived and sometimes they are not. But it is very frustrating, since i go through this process every couple of days and sometimes even several times per day. And each time i need to manually go into the folder and mark 2 files as not derived... Is there any way to get debug logs in order to analyze this further? And can you please fix this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12?email_source=notifications&email_token=AB4WYYPPJVUE23SXRKB6B4LP73XCHA5CNFSM4CP3JGE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2DXXGY#issuecomment-512195483>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB4WYYK4CLAX7JCZAFTZOLTP73XCHANCNFSM4CP3JGEQ> .