[Jboss-dev-forums] [Design of Mail Services] - Re: JBoss Mail Server M3-pre1

[<aco...@jb...>]

modules limit directories, you still need the tag

cvs co -r Branch_4_0 jboss-4.0

anonymous wrote : 
  | Choosing between a new or existing jboss install is a little clumsy. On the Installation location page it would nice to have 3 radio button options:
  | 
  | - New install, with text field and browse button.
  | - Existing install, with text field, browse button and select box indicating with server configuration to use (we could produce a list once the directory is selected). We could also default the jboss installation from the JBOSS_HOME environment variable if it exists.
  | - Create deployable EAR. Useful for deploying to headless servers/clusters. 
  | 

I think you're on to something, but we'll have to defer that to a later milestone because it involves changes to izPack and probably coordination with the overall JBoss Build project.  I'm sure scott/clan would be ameniable to this (since it has larger uses), but it involves too many touch points to get out for M3.  (The installation panel is more or less a fixed panel)

anonymous wrote : 
  | In the longer term it would be nice to support more advanced configurations and be able to set all of the options on all of the MBeans. E.g. being able to set options for performance tuning would be nice. Perhaps an "Advanded" button on some of the pages which shows more detailed options.
  | 

Yes.  I vacillate on this.  We're going to need an admin tool so should the installer let you do that or require you to do that in the admin tool?  My present thinking is that it should once automated install works properly so that you can install consistantly accross an organization.  Though I have more sinsiter plans for MBeans and all.

anonymous wrote : 
  | I also noticed that if you reinstall it over an existing install it fails. Something to do with keystore generation. 
  | 

I'll probably cover this in the readme.  I don't want to mindlessly clobber an ssh key.  It should work if you don't generate a new key.

=======

That stuff aside, are you cool with the dev and dev-deploy targets?  I wanted to find a way to keep the install working consistantly.  This will probably mean everyone has to grok just a little bit about izPack.  I don't think groking the velocity templates is that hard (if one understands if statements and ant basically ;-) ).  There are minor gotchas but one figures them out quickly (no ${foo.bar} type variable names mostly because it thinks the dot means class member)



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888454#3888454

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3888454