Adam Murdoch wrote: > > The problem is, in IDEA at least, that the exclusion of build/ also > excludes the generated source directories under build/. >
Yes, generating into the build folder does have some consequences which is why my first reaction was to generate them into a separate top level folder. However, it seems like there is a consensus that generating to the build folder is better and more in-line with what users expect especially if they are coming from Maven. It also makes the clean operation more straight-forward. Adam Murdoch wrote: > > Anyone have any suggestions for how we might configure IDEA to make this > work? How about Eclipse? > I can speak a little to Eclipse. There are two different levels of "hiding" folders from Eclipse. The first level can be achieved by setting the "Derived" attribute to "true" on the folder. This has the nice effect of hiding the resources in that folder from resource lookups (Ctrl+Shift+R). However, this does not cause the folder to disappear from the different views (such as Project Explorer). With this approach Eclipse will still allow you to add a folder from the "Derived" folder to the project's build path. The second level can be achieved by adding a Resource Filter to the project (Preferences -> Resource -> Resource Filter). I think this might only be available in later versions of Eclipse...it works in Helios at least. When you filter a folder in this fashion it becomes completely invisible to Eclipse and doesn't show up on any views. However, Eclipse will not allow you to add the folder to the project's build path. -- View this message in context: http://gradle.1045684.n5.nabble.com/using-generated-resources-in-the-IDE-tp4363800p4386435.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
