I'm pretty sure you can't. At least on Central who IIRC checks that kind of
things.
It's indeed needed for the dependency resolution mechanism to work.
Cheers
Le 11 oct. 2015 11:50 PM, "Kevin Burton" <bur...@spinn3r.com> a écrit :

> I'm trying to open source a bunch of code in our stack.
>
> Is it possible to have a parent module private, and the child module
> public?
>
> The problem I have now is that if our customers or the open source
> community imports our modules, it needs to fetch the parent, which is
> private.
>
> I assume this is required due to maven inheritance because it needs to
> determine dependencies.
>
> I can just not specify a <parent> but that causes other problems like the
> maven versions problem skipping it for some reason (though maybe this is a
> bug).
>
>
>
> --
>
> We’re hiring if you know of any awesome Java Devops or Linux Operations
> Engineers!
>
> 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>
>

Reply via email to