Hi, Stian Soiland-Reyes wrote:
> I think I'll tend towards agreeing with Jochen here, rather get half the > modules out early than fight ourselves with versioning workarounds if the > rest of the modules are not ready for prime time. > > However I see concerns of selective "part releases" and reproducible > builds, so I would do this using Maven profiles - the release profile can > have a smaller <modules> set. > > I then think all the modules that appear in the src release should also go > to Nexus as binaries, even if they are more exotic "internal" modules. I > would not mess around with selective deployment as it is a recipe for > maintenance nightmare and manual mistakes. > > It only gets tricky if the leftover modules get a release cycle of their > own. > > It is OK if the -bin release don't have all modules, that is more of a > convenience of jars that are useful out of the box. The -src artifact is a different case. It should contain anything independent of the published modules' artifacts (and it can, because it depends on the file patterns in the assembly). It is always a hassle if you have no direct possibility to fetch the matching source of the examples (and even the JMH stuff) for an individual release. Directing users to GIT is not very convenient. Cheers, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
