Re: Writing Installer for James

[Stefano Bagnara <ap...@bago.org>]

I checked httpd people to understand how they do this.

The fact is that what they care is about sources: they release sources.
The installer they ship is simply something they do "unrelated to the 
release" and is done by some committer having windows and a license for 
the tool.

In this case we'll not be able to publish a windows installer from 
apache james because none of the active committers have access to this 
commercial tool.

I've got pointers to the WIX project (microsoft sponsored open source 
project for creating installers starting from XML files) but this would 
require a releaser using windows to publish it.

Otherwise there are java installers, that are crossplatform.

 From what I understood the only solution to create native windows 
installers from both unixes and window is to use NSIS because their 
compiler is crossplatform.

That's all I found by now,
Stefano

Athar Shiraz Siddiqui ha scritto:
> If you look at apache web server's windows installer :
> http://ftp.wayne.edu/apache/httpd/binaries/win32/apache_2.2.9-win32-x86-no_ssl-r2.msi
> 
> Click on "next" after opening the file... you will see that they are
> using Installshield.
> 
> That is go to http://www.installshield.com/
> that is also a commercial product just like setupbuilder.
> 
> 
> 
> On Sun, Jul 20, 2008 at 11:12 AM, Stefano Bagnara <ap...@bago.org> wrote:
>> Athar Shiraz Siddiqui ha scritto:
>>> Ok I wrote this depicting automation of some aspects of the install for
>>> james:
>>>
>>>
>>> http://techpanacea.blogspot.com/2008/07/writing-install-utility-for-james-java.html
>>>
>>> It needs to be refined but any help from all would be great!!
>> If I understant if you are using SetupBuilder. It is a commercial product
>> and I'm not sure we can really use it to prepare our Apache Licensed
>> distribution or that we can use it as part of our release process :-(
>>
>> Maybe other legal/policy issues expert here can help us understanding this.
>>
>> Stefano
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org