>>>>> On Wed, 26 Nov 2003 00:34:10 +1000, Ben Walding <[EMAIL PROTECTED]> said:
> Basically, for what we do, I have all inter-project dependencies set
> to snapshot versions and then just have an external tool setup in
> eclipse to build the active project with jar:install-snapshot. I
> tried the mevenide plugin today, but it didn't work. It looks like
> it will simplify running goals in much the same way as we do now.
Does eclipse loose the ability to refactor across the project code in
this setup? Or perform searches across the workspace?
> If this is too slow, you'll need to switch the project dependencies
> in eclipse from being the jar in the repo to being the other project
> in eclipse. I try not to change my apis too frequently, but its only
> about a 30second turn around time when I absolutely must get the
> latest code / apis into a project. (select changed project,
> jar:install-snapshot, wait, refresh master project)
> Once I'm reasonably happy with all the code / other developers need
> access, I check it in, run an integration build on the server (fully
> mavenised build using reactors) and then let them know the code is
> good to go.
> I'm also looking at using a continuous integration system to build
> snapshots in our repository whenever a piece of code is committed.
> This will hopefully show up integration errors sooner.
I've been planning on setting up similar to this, having a succesful
cruisecontrol build install into a shared corporate repo that all our
maven projects would look at. Sounds reasonable.
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
