On 17/08/11 08:32, Paolo Castagna wrote:
[email protected] wrote:
ARQ build: now uses maven respository artifacts, not local copies.
Yeah. Finally! :-)
Paolo
So beware how it does it! m2eclipse and eclipse:eclipse both assume
(you can reconfigure with arguments - mostly works) that the project is
building into the maven target area. And also that the whole project is
included in the release.
These don't work for me - or rather, it will take some extra work to
rearrange the project to make them work and it's time I don't have at
the moment.
1/ Eclipse compiling to target/classes : why? Seems better to have the
release build to be entirely clean and separate (I do "mvn clean deploy"
each time) from the development area. Different compiler setups for one.
2/ I have extra source folders for development code, either
work-in-progress stuff that isn't ready for the main code base, or
experimental ramblings, or code that drives the system to aid
development (test setups, bug reports, ...)
In ARQ and related projects I've put scripts ./mvn-update that vary
according to the current project setup. Needs to be run to pick up
latest snapshots.
Version change of a dependency still means editing the .classpath file
but I have found that a lot less work than fixing up autogenerated files
that have lost project specific settings.
Andy
