[
https://issues.apache.org/jira/browse/GERONIMO-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645424#action_12645424
]
Jack Cai commented on GERONIMO-4395:
I guess this is just a convention. Ivan's
Hi all,
Recently we have seen updates to the Geronimo 2.2 doc.
We have been studying the Geronimo 2.2 release roadmap and analyzing
what should be added/changed to the doc. We'll soon add some skeleton
topics based on our understanding and analysis of the new/changed
features. We'll definitely
Geronimo Revision: 711789 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081106/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081106
[INFO] BUILD
Not worth a JIRA: I think, the default log4j ConversionPattern in
server-log4j.properties should be changed from ABSOLUTE to ISO8601 to have
complete dates in the log.
Hm, was it today or yesterday this happened?
Thanks a lot Donald!
So if we make this as a plugin (well, it's really a windows exe), we will
not be able to install it to the bin directory, right? If this is the case,
then it might not be conveniet for the users to control the service using
command line.
Another option is to create different
[
https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645446#action_12645446
]
Vincent MATHON commented on GERONIMO-3907:
--
I agree that exceptions on the
Fail to remote deploy war file using command: deploy --uri
deployer:geronimo:jmx://Remote_Machine_IP deploy
location_of_cviewer_war_module/cviewer.war
[
https://issues.apache.org/jira/browse/GERONIMO-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645486#action_12645486
]
Lin Sun commented on GERONIMO-4395:
---
I think I like the current impl better. Having
On Nov 6, 2008, at 3:45 AM, Jack Cai wrote:
Thanks a lot Donald!
So if we make this as a plugin (well, it's really a windows exe), we
will not be able to install it to the bin directory, right? If this
is the case, then it might not be conveniet for the users to control
the service
Investigate removing older versions of the GEP plugins/features from our
Eclipse update site on Apache
--
Key: GERONIMODEVTOOLS-529
URL:
[
https://issues.apache.org/jira/browse/GERONIMO-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645499#action_12645499
]
Jarek Gawor commented on GERONIMO-4396:
---
Did you modify the
[
https://issues.apache.org/jira/browse/GERONIMO-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn reassigned GERONIMO-3316:
--
Assignee: Joe Bohn (was: David Jencks)
warn but don't prevent deployment if an ear's
Looks like discussion on this thread has died down a bit but the clock
is still ticking ... New Years will be here all too soon and IIUC we're
trying to beat that clock!!
Some things in addition to what you've listed (I'll update the wiki with
these too):
- There are a number of snapshots
Over the past days, I've been working on a implementing a SSH server
in java to replace to gshell remoting bits.
The project is currently hosted at google code:
http://code.google.com/p/sshd/
This project is based on Mina and the current status is that the ssh
protocol is in a working state,
On Nov 4, 2008, at 9:58 AM, Donald Woods wrote:
BTW - Since you have a CLA on file, I just added your 2 ids
(caijunj, greensight) to the geronimo-contributor group in JIRA,
which will allow you to assign items to yourself to work on.
Minor point of law -- an ICLA need not be a
[
https://issues.apache.org/jira/browse/GERONIMO-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645678#action_12645678
]
viola.lu commented on GERONIMO-4396:
yes, i modify the local machine:
2. Edit
[
https://issues.apache.org/jira/browse/GERONIMO-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645681#action_12645681
]
Jarek Gawor commented on GERONIMO-4396:
---
If server A is the remote machine and
Thanks for chiming in. If you can start removing some of the snapshots,
that would be great.
I hadn't volunteered to be the RM yet, as I'll only have about 2 days a
week to focus on a 2.2 release and I don't have TCK access (which is
going to be a major factor for when we can get 2.2 out),
The time has come to make the hard decision -
Do we only build and certify Geronimo 2.2 on the Sun 1.6.0 JDK and drop
support for running on Java SE 5?
Pros:
- Reduce testing effort to one version of Java
- Allows us to use the JAXB 2.1, JAX-WS 2.1 and wsgen tools in the JDK,
instead of
Thanks for the update, but please try to keep everyone in the loop (like
by creating a Doc Plan roadmap/todos/status under the 2.2 Roadmap
page) and work towards incremental updates, instead of infrequent drops
of large changes. By keeping everyone involved in planned doc changes,
you'll get
If you don't want this request to get lost, please open a JIRA and
assign the Fix versions to 2.1.4 and 2.2.
-Donald
Juergen Weber wrote:
Not worth a JIRA: I think, the default log4j ConversionPattern in
server-log4j.properties should be changed from ABSOLUTE to ISO8601 to have
complete
Yes, a random artifact id may be less readable.But giving an error message
may make the uesr feel confusion, actually, the database pool name is OK, it
is different from any existing one, but the deployment failure is caused by
that an unique artifact id is needed.
I have another suggestion, after
22 matches
Mail list logo
