The benefit of webstart is updates are automatically downloaded and installed. The link actually tries to check jars each time you start the app and will update automatically if there are new ones.
On Wed, Jun 20, 2012 at 4:31 PM, Scott Deboy <firstname.lastname@example.org> wrote:Is there something speaking against downloading an exe/dmg/zip via the
> I think the gotcha there had something to do with making sure the jnlp file mapping was correctly supported. It has been about eight years, but that is my recollection.
> That and the stupid maven template support would not allow us to use an image as the link (a 'launch' webstart graphical button as the link)
usual download system?
Or is webstart the killer feature for chainsaw? :-)
> On Jun 20, 2012, at 2:46 AM, Christian Grobmeier <email@example.com> wrote:
>> On Wed, Jun 20, 2012 at 7:07 AM, Ralph Goers <firstname.lastname@example.org> wrote:
>>> I believe all the hard work on the logging site is completed however some of the sub projects are yet to be published. I would like to have infra convert loggingtest.apache.org to logging.apache.org but I don't want to get 404s on those sub projects.
>>> I looked at chainsaw and the download page will certainly break if I were to just copy the content. I'm not sure about the others.
>>> Any ideas?
>> Just added log4cxx to loggingtest.a.o. Its using the download script
>> which generates a list of mirrors so no problem here. In addition I
>> completed the branding requirements for log4cxx so we can leave that
>> untouched for a while now.
>> I am not sure on the chainsaw one. It seems to bypass the mirroring
>> system which is kind a bad. Instead we should change the site to use
>> the download script imho. Maybe Scott can comment here.
>> That being said, the chainsaw site needs an appropriate footer.
>> Basically the maven.vm template could be used in chainsaw too. So we
>> have 2 tasks here, update to branding and use the mirror system.