>I also respect the conventions, but in this particular case the >convention became counter-productive: I externalized all the messages >into Messages.properties file per package and have to modify this file >all the time.
>If this file sits in the src/main/java/... package - it's one mouse >click in Eclipse to open it. If I move it to src/main/resources/.. - it >becomes a multi-click - one has to click as many times as there are >members in the package name, because Eclipse does not respect "flatten >packages" preference for "empty" packages, and folder without java files >in it is treated as "empty". So it's 5-8 code clicks instead on one. Oleg, I don't agree here. Resources belong in src/main/resources and not in java code. We can go round and round about good or bad conventions, but that's the maven convention and we should adhere to it.
