You are probably going to want to make your open source project
completely separate with its own versions and parent.
If third parties are actually going to file issues, provide updates and
create new minor versions as they fix bugs, you are going to either be
forced to release versions of your private project before you are ready
or have to fork your own open source project to maintain a consistent
version between the 2 parts of your product.
Having a successful open source project requires a new way of thinking
about your baby.
Ron
On 12/10/2015 2:49 AM, Baptiste Mathus wrote:
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" <[email protected]> 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>
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
