Interesting, I hadn't noticed this was only a warning.

The main problem I have is the moment you start relying on these fake reactors you end up breaking C.I. builds with dependant changes.

This is my main beef with multiple git repositories for projects - if you have a pairing of dependant changes ( an API change and an Implementation change ) - without specific tooling about sharing local-repos for discreet dependent change sets you end up with false-negative build failures.

I believe this is an area that Jason's new continuous deliver system does not even try to address (yet), I think I saw it mentioned that it requires simple-repo to work.

Mark

On 16 Jun 2014, at 20:00, Stephen Connolly wrote:

That's it... and also note that while Maven complains if the pom at the specified <relativePath> is not the parent, it will build correctly ... just resolving the parent from the local repository and not from the disk.


On 16 June 2014 06:05, Barrie Treloar <[email protected]> wrote:

On 16 June 2014 14:12, Stephen Connolly <[email protected]>
wrote:

On Sunday, 15 June 2014, Mark Derricutt <[email protected]> wrote:

So if I have two modules that are interdependent on in-progress
changes,
how does one build/test the dependant one.

Note - reactor builds and multi-modules builds are out of the question
-
the above modules are in separate git repositories and there's no way
to
create a "fake reactor" setup - i.e. a separate pom.xml just listing <module/> elements ( maven complains when that pom is not the parent ).


Even if the local aggregator does something like

<module>../foo</module>


A link to a blog post or more detail might be useful for those still
learning.

I'm pretty sure I know this to look like
ROOT/
- aggregator
- pom.xml (reference modules ../projectA and ../projectB)
- projectA
- projectB

But its not something I do, and I'm hoping I got it right from Maven
experience :)

This is where the vaoporware "Magic Checkout" plugin that Kristian has
mentioned would be useful.
This plugin would automatically change a released dependency to its
snapshot version, check it out, and update/create the aggregator project to
reference the checked out version.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to