> In other words, you can keep using your toplevel pom.xml as an _aggregator_ without it being the _parent_ of your OSS module.
Ha. That works. But the versions plugin now won’t update the version of the sub-module… This is super fun! :) On Fri, Sep 12, 2014 at 9:33 AM, Curtis Rueden <[email protected]> wrote: > Hi Kevin, > > > I want to post this to a public repo… it’s open source. > > > > The problem is that the parent module is not OSS. > > Child modules of a multi-module build do not need to use the toplevel > module as parent. > > In other words, you can keep using your toplevel pom.xml as an _aggregator_ > without it being the _parent_ of your OSS module. > > http://rostislav-matl.blogspot.com/2011/12/maven-aggregator-vs-parent.html > > Regards, > Curtis > > On Thu, Sep 11, 2014 at 10:25 PM, Kevin Burton <[email protected]> wrote: > > > I have an OSS module in a multi-module maven project. > > > > I want to post this to a public repo… it’s open source. > > > > The problem is that the parent module is not OSS. > > > > When I setup a <dependency> it pulls in my OSS module just fine, but then > > it tries to pull down the parent module, which isn’t in the repo, and > > breaks. > > > > The parent pom isn’t really a dependency… so I’d like it to not need it > > > > is this possible? > > > > -- > > > > Founder/CEO Spinn3r.com > > Location: *San Francisco, CA* > > blog: http://burtonator.wordpress.com > > … or check out my Google+ profile > > <https://plus.google.com/102718274791889610666/posts> > > <http://spinn3r.com> > > > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
