Administrator
|
Hi,
I recently suggested that to no be encumbered with Gradle build and bin folder in Eclipse you can set them as derived (folder attribute in its properties). This works well for bin, but, each time we do a clean, the build folder loses its attributes because it's deleted and regenerated. Could we not empty it rather than delete? Thanks Jacques |
Hi Jacques,
Usually for all Java projects in common build systems (Gradle, Maven) the build directory is deleted. What is the problem? I'm not getting any thing wrong on eclipse? Please note we can modify the .project properties in build.gradle for whatever you need. On Sat, Jul 30, 2016 at 3:18 PM, Jacques Le Roux < [hidden email]> wrote: > Hi, > > I recently suggested that to no be encumbered with Gradle build and bin > folder in Eclipse you can set them as derived (folder attribute in its > properties). > > This works well for bin, but, each time we do a clean, the build folder > loses its attributes because it's deleted and regenerated. > > Could we not empty it rather than delete? > > Thanks > > Jacques > > |
Administrator
|
Le 30/07/2016 à 14:42, Taher Alkhateeb a écrit :
> Hi Jacques, > > Usually for all Java projects in common build systems (Gradle, Maven) the > build directory is deleted. What is the problem? I'm not getting any thing > wrong on eclipse? The problem is to hide search results, etc. (ie to ignore the build folder) in Eclipse by setting the build folder in Eclipse as derived (folder attribute in folder properties). By deleting the build folder and regenerating it you lose the setting Jacques > > Please note we can modify the .project properties in build.gradle for > whatever you need. > > On Sat, Jul 30, 2016 at 3:18 PM, Jacques Le Roux < > [hidden email]> wrote: > >> Hi, >> >> I recently suggested that to no be encumbered with Gradle build and bin >> folder in Eclipse you can set them as derived (folder attribute in its >> properties). >> >> This works well for bin, but, each time we do a clean, the build folder >> loses its attributes because it's deleted and regenerated. >> >> Could we not empty it rather than delete? >> >> Thanks >> >> Jacques >> >> |
Ahhh, I believe this is fixable by resource filters on the project. This
would not only allow you to exclude the build directory but other ones as well (for example .svn should be ignored right?) I think the code could probably be something like: eclipse.project.file.whenMerged { projectFile -> //Apply resource filters here } This would have the added value of customizing the project however you like without the need to touch the directory structure. On Sat, Jul 30, 2016 at 8:34 PM, Jacques Le Roux < [hidden email]> wrote: > Le 30/07/2016 à 14:42, Taher Alkhateeb a écrit : > >> Hi Jacques, >> >> Usually for all Java projects in common build systems (Gradle, Maven) the >> build directory is deleted. What is the problem? I'm not getting any thing >> wrong on eclipse? >> > > The problem is to hide search results, etc. (ie to ignore the build > folder) in Eclipse by setting the build folder in Eclipse as derived > (folder attribute in folder properties). > By deleting the build folder and regenerating it you lose the setting > > Jacques > > > >> Please note we can modify the .project properties in build.gradle for >> whatever you need. >> >> On Sat, Jul 30, 2016 at 3:18 PM, Jacques Le Roux < >> [hidden email]> wrote: >> >> Hi, >>> >>> I recently suggested that to no be encumbered with Gradle build and bin >>> folder in Eclipse you can set them as derived (folder attribute in its >>> properties). >>> >>> This works well for bin, but, each time we do a clean, the build folder >>> loses its attributes because it's deleted and regenerated. >>> >>> Could we not empty it rather than delete? >>> >>> Thanks >>> >>> Jacques >>> >>> >>> > |
Free forum by Nabble | Edit this page |