Hi Kevin,
Having a public project extend a private one seems fundamentally
broken/impossible to me.
Presumably your "parent project" is just a POM and not a JAR, right?
Can you use a structure like:
toplevelPublicPOM
- publicProject1
- publicProject2
- privateParentPOM
-- privateProjectA
That's a good point. It's a tough call because we're trying to move as
fast as possible but this means that the code can bitrot and not get
updates from the community.
The other thing I was thinking about was using the maven updates plugin to
automatically detect when new versions are released.
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 yo
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" a écrit :
> I'm trying to open source a bunch of code in our stack.
>
> Is it possible to have a
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
