Re: [jetty-dev] Re: jetty7 distribution

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

fair enough, I am happy with the proposed changes then!

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Sat, Aug 8, 2009 at 17:19, Greg Wilkins<gregw@xxxxxxxxxxx> wrote:
> Jesse McConnell wrote:
>> How about making a jetty/trunk/jetty-distribution parent and a
>> jetty/trunk/jetty-integration parent?
>
> Not keen.
>
> Currently we've mixed jetty-distribution with jetty-dosomething modules
> and it's not a problem.
>
> Also some distributions (eg jetty-maven-plugin) are half integration
> and half distribution. Besides, it may be (in future) that some simple
> distributions are built before some integrations.
>
> I'd much rather keep it at just two main projects: @eclipse @codehaus
> and we build them in lock step.
>
> cheers
>
>
>> then terracotta and all of those guys build under their respective slots?
>>
>>>  jetty-debian
>>>  jetty-rpm
>>>  jetty-maven-plugin
>>>  jetty-runner
>>>  jetty-hightide
>>>
>>>
>>> Looking at it this way, the jetty-hightide name makes more
>>> sense, since calling it jetty-distribution would crowd out
>>> those other as "distributions".
>>>
>>> Note, for jetty-6 hightide was different because it was patched and
>>> compiled differently.   For jetty-7 the artefacts that will be
>>> in hightide will just be the standard ones from maven.
>>>
>>>
>>>> * henceforth all rpm, deb, tar.gz distro's for jetty7 would come from
>>>> here, jetty6 we keep it the way it is and cleanup the hightide build
>>>> bits
>>> All the rpm, debs, tar.gz distros come from jetty@codehaus trunk
>>>
>>>
>>>> I would also like to suggest that we move anything jetty7 producing
>>>> into jetty/hightide/trunk and move the jetty6 branch back onto
>>>> jetty/trunk so its clear that is where jetty6 lives and we remain in
>>>> maintenance mode...that way it is clear that jetty7 is from eclipse
>>>> except for hightide bits and jetty6 is from codehaus svn...At the same
>>>> time we retire hightide-jetty6 since we haven't updated that recently
>>>> either..unless we have someone that needs it then it is a branch of
>>>> the above hightide location.
>>>>
>>>> Basically I want to get us down to as few active svn trunks and
>>>> branches as possible.
>>> Ditto!
>>>
>>> Going forward I want just to have
>>>
>>>  http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk
>>>  http://svn.codehaus.org/jetty/jetty/trunk
>>>
>>>
>>> But until EoL we have to maintain jetty-6 and hightide-6 in
>>>  http://svn.codehaus.org/jetty/jetty/branches/jetty-6.1
>>>  http://svn.codehaus.org/jetty/hightide/trunk
>>>
>>>
>>>> Greg, some time ago you mentioned having a weekly or fortnightly
>>>> either phone or irc meeting...perhaps we could set something like that
>>>> up to discuss this?
>>> This is a good idea and we should definitely do this... I'll separately
>>> post with a suggestion for a regular time.
>>>
>>> But meanwhile, I want to get 7RC3 out.   We have built the eclipse
>>> project, but there is no runnable distro yet.     I could build
>>> jetty@codehaus, but that currently has jetty-distribution as the
>>> module name.    If we can get some agreement now, then I'd like
>>> to rename that jetty-hightide for the 7RC3 build from codehaus
>>> and this could be ready to run Monday!
>>>
>>>
>>>
>>> cheers
>>>
>>> _______________________________________________
>>> jetty-dev mailing list
>>> jetty-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>>
>> _______________________________________________
>> jetty-dev mailing list
>> jetty-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>