You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Kevin Burton <bu...@spinn3r.com> on 2015/10/11 23:49:30 UTC
publishing sub-modules without requiring the parent module to be published?
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>
Re: publishing sub-modules without requiring the parent module to be published?
Posted by Curtis Rueden <ct...@wisc.edu>.
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
-- privateProjectB
?
Regards,
Curtis
On Mon, Oct 12, 2015 at 1:31 PM, Kevin Burton <bu...@spinn3r.com> wrote:
> 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.
>
> The problem with this is that releases get cascaded as libs move up the
> dependency tree. We have about 150 modules so this could get confusing if
> we're not careful.
>
> On Mon, Oct 12, 2015 at 5:00 AM, Ron Wheeler <
> rwheeler@artifact-software.com
> > wrote:
>
> > 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" <bu...@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>
> >>>
> >>>
> >
> > --
> > Ron Wheeler
> > President
> > Artifact Software Inc
> > email: rwheeler@artifact-software.com
> > skype: ronaldmwheeler
> > phone: 866-970-2435, ext 102
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
>
> 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>
>
Re: publishing sub-modules without requiring the parent module to be published?
Posted by Kevin Burton <bu...@spinn3r.com>.
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.
The problem with this is that releases get cascaded as libs move up the
dependency tree. We have about 150 modules so this could get confusing if
we're not careful.
On Mon, Oct 12, 2015 at 5:00 AM, Ron Wheeler <rwheeler@artifact-software.com
> wrote:
> 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" <bu...@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>
>>>
>>>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
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>
Re: publishing sub-modules without requiring the parent module to be
published?
Posted by Ron Wheeler <rw...@artifact-software.com>.
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" <bu...@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>
>>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: publishing sub-modules without requiring the parent module to be published?
Posted by Baptiste Mathus <ml...@batmat.net>.
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" <bu...@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>
>