On Thu, Apr 9, 2009 at 7:58 AM, Arnaud HERITIER aherit...@gmail.com wrote:
1) The Maven convention and good practice is to put ressources files like
*.txt in src/main/resources.
But *FORCING* this 'convention' on the world is a whole other thing.
One of the benefits of using maven is that you
On Thu, Apr 16, 2009 at 12:20 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
On Thu, Apr 9, 2009 at 7:58 AM, Arnaud HERITIER aherit...@gmail.com wrote:
1) The Maven convention and good practice is to put ressources files like
*.txt in src/main/resources.
But *FORCING* this
Convention is convention because it's not a rule :) This also means you
don't have to follow it but then it will cost you time/effort/extra
configuration (you name it)...
And this is valid everywhere where 'convention over configuration' exists
(it's kinda by definition)...
Best regards,
Siarhei
Once you force a convention the convention stops being convention and
becomes a rule/law. So no, in case of maven it is still a convention :)
So it's still possible to have resources along with the source code (if it
happens that the convention isn't suitable for you).
I beleived I had to do it a
On Thu, Apr 16, 2009 at 3:29 PM, Siarhei Dudzin
siarhei.dud...@gmail.com wrote:
Convention is convention because it's not a rule :) This also means you
don't have to follow it but then it will cost you time/effort/extra
configuration (you name it)...
Thanks for clarifying! :)
Hi,
The Maven convention and good practice is to put ressources files like
*.txt in src/main/resources.
This is a bit troublesome for those of us using the AspectJ plugin.
We need to place *.aj files in the src/main/java (and test) directory.
However, these files are excluded from the build.
On Thu, Apr 16, 2009 at 1:39 AM, Andrew Eisenberg
andrew.eisenb...@gmail.com wrote:
Hi,
The Maven convention and good practice is to put ressources files like
*.txt in src/main/resources.
This is a bit troublesome for those of us using the AspectJ plugin.
We need to place *.aj files in the
Hi,
On Wed, Apr 8, 2009 at 11:28 PM, Zach Cox zcox...@gmail.com wrote:
While I realize that technically only .java files should exist in
src/main/java, it's a pain to create a duplicate package hierarchy in
src/main/resources and this greatly reduces visibility of these .txt
files.
This is
1) The Maven convention and good practice is to put ressources files like
*.txt in src/main/resources.
I totally agree - long-term we will move everything that's not a .java
file there. We're still adjusting to doing everything the Maven way.
2) The change you have is due to the new version
Before this week, running mvn eclipse:eclipse would put a line like
this in .classpath:
classpathentry kind=src path=src/main/java/
Now this week it is putting this line in .classpath instead:
classpathentry kind=src path=src/main/java including=**/*.java/
We have some .txt files that sit
1) The Maven convention and good practice is to put ressources files like
*.txt in src/main/resources.
2) The change you have is due to the new version 2.6 of the plugin which was
released few days ago. To avoid such a surprise in the future, the good
practice is to set the version of each plugin
11 matches
Mail list logo
