Unfortunately I don't have the answers to making it easy for a new user to get started
(over and above an all-in-one archive).
The way I see the Eclipse architecture is that each feature should principally be
distrubuted in isolatation first. "Runtime only" version that is the way nature
intended.
You are already in no-mans-land when you start distributing anything between an all-in-one
and runtime only and thats a hiding to nothing in the future with with permutations of
platform and feature sets and to this I can't really offer anything.
There maybe suggestions that can be made to update manager development team on this, for
example if after a platform restart (or -clean) a new feature/plugin is detected and it
can not be activated (due to missing dependancies) then they get a prompt on screen
offering was to resolve that problem by locating and downloading those missing
dependancies.
The way I see the new user problem at the moment is that the platform does not help them
enough when a pre-requisite problem occurs. When I think that issue should be in their
face to deal with (or ignored) as soon as its detected, even little things like
notification confirming a new plugin was detected and is activated giving the user
positive feedback their unzip worked correctly.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962269#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...