melting-pot: what to do about multi-module builds?

[hinerm]

When we create the mega-melt pom.xml we create a multi-module build where each dependency is a module.

If any of those dependencies are themselves modules of a multi-module build, where their aggregator is also their parent pom (i.e. https://github.com/axtimwalde/mpicbg), the now-orphaned modules appear to be unable to find their parents.

A heavy-handed suggestion: all child modules should include scijava repository blocks:

	<repositories>
		<repository>
			<id>scijava.public</id>
			<url>https://maven.scijava.org/content/groups/public</url>
		</repository>
	</repositories>

This way, the children will always know how to find their parents.

[hinerm]

@axtimwalde any feelings about this?

[axtimwalde]

Sure, anything you need me to do?

[ctrueden]

We don't use a multi-module approach with the melting pot anymore. So I believe this issue is now moot.

There is still some weirdness with multi-module sources (try tests/run.sh in pom-scijava and look at what happens with mpicbg and mpicbg_), but they do build, so it's not exactly the problem described by this issue anymore.