I'm just starting a new project with a non-trivial source tree, and decided to use 4.0 with the module capabilities. It took over a half hour to set up the project with 6 modules.
I wanted to store the module-files outside the content-root because they are IDE specific and not part of the project source. Everytime I changed the content-root, the default module-file location changed and I had to manually change it back by navigating through directory trees. Then when I went to define the content-root for the next module, I had to navigate away from the module-file location to the new content-root. I had to do this back and forth through the directory tree navigator for each module.
Next I tried the ClearCase integration which caused me to lose files. No blame here. I decided to use a ClearCase snapshot view instead of a dynamic view, but to do this I had to change the location of all the content roots. I decided to edit the XML files. I performed a search and replace on the path names. When I loaded the project again I was informed that the project file was corrupt. Fair enough, that wasn't a documented procedure and I could have screwed up.
No way was I going to go through the previous process of setting up the project again. I decided to configure a new project with a single module. That was easy, however I found some differences from 3.0 that represented a loss in functionality:
- In the 4.0 Packages view, performing a Find in Path searches through all files in the module. I would expect that when in the Packages view, we should only be searching the package directories (i.e. java files). This differs from 3.0 where I can just search through java files by performing a Find in Path on the Project/Source view. In 4.0 I now have to navigate through the Project view to find the source directories, and then do a Find in Path.
- In 3.0 I could easily work with my web files (e.g. jsps, etc.) via the Web view. I could easily jump back and forth between my java source and web files by jumping between views (Web and Project/Source). In 4.0 I have to navigate through the Project view to get to my web files.
At this point I find no advantage to using 4.0 and numerous disadvantages. Given how much I love this product, I find myself disappointed with the new version. I suggest the following features:
- When configuring a multi-module project, facilitate the ability to easily store all module files outside the module root.
- When using Find in Path within the Package view, only search for files that are in the directories within that view. This seems to be common sense.