[ http://issues.apache.org/jira/browse/GERONIMO-1189?page=all ]
erik daughtrey updated GERONIMO-1189:
-
Summary: [PATCH] Installer should be built from its own module in
assemblies. (was: Installer should be built from its own module in assemblies
Hey David, I'll start working on these items.
erik
On Wednesday 16 November 2005 03:24, David Jencks wrote:
It would be good if we could get the installer working well for 1.0.
Here are some of the things I think need to happen.
1. The necessary izpack jars need to get into some maven
worked with IzPack for a while now so my
information may be a little out of date. :)
Aaron
On 11/16/05, Erik Daughtrey [EMAIL PROTECTED] wrote:
Hey David, I'll start working on these items.
erik
On Wednesday 16 November 2005 03:24, David Jencks wrote:
It would be good if we could get
button
functionality.
Then again, I haven't worked with IzPack for a while now so my
information may be a little out of date. :)
Aaron
On 11/16/05, Erik Daughtrey [EMAIL PROTECTED] wrote:
Hey David, I'll start working on these items.
Excellent
david jencks
erik
/reference/repository-upload.html
And as for the radios, I think we should definitely enforce only 1 web
container through the installer. That will save us a whole world of
pain. If people want 2 web containers, let them take some manual
steps!
Aaron
On 11/16/05, Erik Daughtrey [EMAIL
Components: installer
Versions: 1.0
Environment: maven and maven repository
Reporter: erik daughtrey
As Aaron points out, there's probably only one jar needed. David J would like
to see this in a public repository such as ibiblio.
--
This message is automatically generated by JIRA
Versions: 1.0
Environment: Maven
Reporter: erik daughtrey
It would be best to build using a Maven plugin. Otherwise, if impractical, use
jelly. There seems to be an installer plugin for Maven 2, but not for the
current build.
--
This message is automatically generated by JIRA.
-
If you
Type: Improvement
Components: installer
Versions: 1.0
Environment: installer runtime on all platforms
Reporter: erik daughtrey
It's possible that the createForPack element, when properly leveraged, may
allow this capability.
--
This message is automatically generated
Versions: 1.0
Environment: Installer runtime -- all platfoms
Reporter: erik daughtrey
Currently, the installer does not verify that conflicting ports may have been
configured by the operator. Fixing this problem requires encoding of the
potential field conflicts on an inter-panel
Versions: 1.0
Environment: Installer runtime
Reporter: erik daughtrey
DJ - This could be done by adding bits associated with each configuration, or
by removing chunks from a 'universal' config.xml for the configuations we
didn't install.
--
This message is automatically generated by JIRA
: New Feature
Components: installer
Versions: 1.0
Environment: Maven, installer runtime
Reporter: erik daughtrey
DJ: This should proceed by fixing the xmlbeans plugin to put schemas in the
same place the xmlbeans ant task does, and by extracting all such schemas from
our
Do I have enough Karma to have JIRAs assigned to me?
Specifically, I'm interested in 1188-1193 for the installer.
Regards,
erik
On Tuesday 01 November 2005 18:24, Dain Sundstrom wrote:
Since on one objected, I added a geronimo-contributers group that can
assign, resolve and be assigned
: installer
Versions: 1.0
Environment: Maven, installer runtime
Reporter: erik daughtrey
DJ: The installer currently works by installing everything in a full
geronimo install, and not starting the pieces you don't want. This is
rather unsatisfactory unless you sell disk space
101 - 113 of 113 matches
Mail list logo