Re: [jetty-dev] Re: jetty7 distribution

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

Personally I am not keen on a jetty-distribution from eclipse that
contains artifacts or dependencies, whatever anyone wants to call
them, that are not publicly available from a durable maven repository.
 I can handle it for osgi consumers that would consume jetty from a p2
update site type location as those artifacts/dependencies have been
run through the eclipse bundling process such they can be consumed
into that environment.  That is a completely different type of
distribution so I am all good with that.

I will note that we can perhaps use the dependency maven plugin to
grab the artifact out of Orbit through a hard coded URL but I am also
not really keen on that approach either.

As for the jetty distribution idea...+1

http://svn.codehaus.org/jetty/hightide/trunk produces a jetty7 hightide distro

* 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

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.  So moving the jetty7 bits @ codehaus under
hightide would make it clear that jetty7 is at eclipse, and anything
else is part of hightide....now I am wondering about the
org/mortbay/hightide artifacts...does hightide continue to go under
there for jetty7 or does it go under org/mortbay/jetty/jetty-hightide
now?

Alternately we create a hightide project at codehaus and put the two
distro's there, which would make sense since we are producing
org/mortbay/hightide artifacts anyway...

Thirdly we could look at the eclipse distribution approach but have a
little webapp that deploys that lets you configure jetty, downloading
the required bits and pieces from maven repos..kinda a long shot :P

So my summary is:

nay on the anemic eclipse jetty distro
yah on standardizing behind a hightide distro (though discussion is
needed on the format and location imo)

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?

cheers,
Jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Fri, Aug 7, 2009 at 04:01, Chad La Joie<chad.lajoie@xxxxxxxxx> wrote:
> Yeah, I understand that you could end up with quite a plethora of options.
>  For me, personally, I don't so much care because my first "real" use of
> Jetty is going to be bundling it with other software so I'm going to have to
> create a custom distribution anyways.  I was more just thinking out loud.
>  If the IP issues around the JSP support are soon to be resolved then I
> would probably just go with what you originally proposed, if it were my
> call.
>
> Greg Wilkins wrote:
>>
>> Chad La Joie wrote:
>>>
>>> Hey Greg,
>>>
>>> For what it's worth, it seems like there would be a number of
>>> individuals who would want JSP support but not the additional things
>>> included in Jetty 6 Hightide.  But I may be biased because I fall in to
>>> the group just described.  Until the IP issues around the JSP support
>>> get worked out, would you consider building a jetty-distirbution@eclipse
>>> + JSP@codehaus version?
>>
>> Chad,
>>
>> and there is the rub!
>>
>>
>> Once you consider external dependencies, there are so many combinations:
>>
>> jetty
>> jetty+jsp
>> jetty+jndi
>> jetty+jsp+jndi
>> jetty+slf4j
>> jetty+jsp+slf4j
>> jetty+jndi+slf4j
>> jetty+jsp+jndi+slf4j
>> jetty+annotations
>> jetty+jsp+annotations
>> jetty+jndi+annotations
>> jetty+jsp+jndi+annotations
>> jetty+slf4j+annotations
>> jetty+jsp+slf4j+annotations
>> jetty+jndi+slf4j+annotations
>> jetty+jsp+jndi+slf4j+annotations
>> etc.
>>
>>
>> We are never going to make a distro that is exactly right for everybody.
>>
>> What we did in jetty-6 was to have 2 distro's one close to simplest
>> possible
>> and hightide which is moderately optioned up.
>>
>> I think that gives a good starting point for most.
>>
>>
>> So the question is, do we go for
>>
>>  minimal @ eclipse
>>  moderate @ codehaus
>>  maximal @ codehaus
>>
>>
>> or just go for
>>
>>  moderate @ eclipse
>>  maximal @ codehaus
>>
>>
>> I admit that the moderate@eclipse might initially be a little more
>> of a minimal@eclipse. But the IP issue around JSP is solvable and just
>> work/time.
>>
>> So do we create a new moderate @ codehaus distro to fill in the
>> short term gap - and then have to support that for the long term,
>> or do we stick with 2 distros because we know the solution is
>> not that far away?
>>
>> cheers
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> jetty-dev mailing list
>> jetty-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
> --
> SWITCH
> Serving Swiss Universities
> --------------------------
> Chad La Joie, Software Engineer, Net Services
> Werdstrasse 2, P.O. Box, 8021 Zürich, Switzerland
> phone +41 44 268 15 75, fax +41 44 268 15 68
> chad.lajoie@xxxxxxxxx, http://www.switch.ch
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>