[
https://issues.apache.org/jira/browse/GERONIMO-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy updated GERONIMO-3767:
--
Affects Version/s: 2.0.x
Fix Version/s: 2.0.x
I have noticed this wh
I don't mind seeing this from time to time... just not happy to get in
every hour... every day :-)
Thanks,
--jason
On Jan 19, 2008, at 1:16 PM, Jarek Gawor wrote:
Btw, from time to time you still might see these messages since the
testsuite build scripts fix the permissions after the files
Folks,
As some of you may have noticed, the locations of the testsuite
reports and snapshot binaries have changed recently. They were moved
from Prasad's home directory to:
Binaries:
http://geronimo.apache.org/maven/server/binaries
Testsuite reports:
http://geronimo.apache.org/maven/server/tests
[
https://issues.apache.org/jira/browse/GERONIMO-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3607.
--
Resolution: Fixed
Rev 613462 makes the gshell assemble command work again and adds a console
Btw, from time to time you still might see these messages since the
testsuite build scripts fix the permissions after the files are
uploaded. So there is a little bit of time where the files exist
without the right permissions and in which your cron job might run.
Also, if somebody knows how to con
deploy process never completed after a failed deploy
Key: GERONIMO-3767
URL: https://issues.apache.org/jira/browse/GERONIMO-3767
Project: Geronimo
Issue Type: Bug
Security Level: pub
t with tests included
> >
> > See the full build-0900.log file at
> > http://geronimo.apache.org/maven/server/binaries/trunk/20080119/build-0900.log
>
> Has it ever been announced that we have this new repo for our daily
> builds? I think it's not. It would be very useful to
Let me know if it is still complaining. I assume it was complaining
about the 20080118 directory but not 20080119?
Jarek
On Jan 19, 2008 1:20 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:
> Still getting these hourly...
>
> Shall I update the cron job to spam dev@ ?
>
>
[
https://issues.apache.org/jira/browse/GERONIMO-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik B. Craig reassigned GERONIMO-3766:
---
Assignee: Erik B. Craig (was: Viet Hung Nguyen)
> monitoring agent should be sepa
On 19 Jan 2008 16:14:14 -, <[EMAIL PROTECTED]> wrote:
> Geronimo Revision: 613393 built with tests included
>
> See the full build-0900.log file at
> http://geronimo.apache.org/maven/server/binaries/trunk/20080119/build-0900.log
Has it ever been announced that we have thi
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Laskowski updated GERONIMODEVTOOLS-257:
-
Description:
As reported by Tomasz Mazan, the following error o
On Jan 19, 2008 7:20 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:
> Shall I update the cron job to spam dev@ ?
No, definitely not. Redirect it to Jarek ;-)
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
[
https://issues.apache.org/jira/browse/GERONIMO-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen updated GERONIMO-3766:
---
Attachment: geronimo-3766.patch
this patch needs the following commands to be exec
[
https://issues.apache.org/jira/browse/GERONIMO-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen updated GERONIMO-3765:
---
Description: When someone adds a server (that does not exist) and he/she
tries to
Still getting these hourly...
Shall I update the cron job to spam dev@ ?
--jason
Begin forwarded message:
From: [EMAIL PROTECTED] (Cron Daemon)
Date: January 19, 2008 10:17:13 AM PST
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync
chmod: /www/geronimo.
On Jan 18, 2008 3:15 AM, Kevan Miller <[EMAIL PROTECTED]> wrote:
> I agree with Jason. We shouldn't be carrying forward the current structure.
> And, I think we have enough time to fix this problem while we are fixing
> other issues with the release.
Even though I tend to agree I understand the p
[
https://issues.apache.org/jira/browse/GERONIMO-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560705#action_12560705
]
Kevan Miller commented on GERONIMO-3762:
Right. That's the more intuitive approa
monitoring agent should be separated into mejb, jmx, and jar utility classes
Key: GERONIMO-3766
URL: https://issues.apache.org/jira/browse/GERONIMO-3766
Project: Geronimo
monitoring console throws IllegalArgumentException when editting a bad server
-
Key: GERONIMO-3765
URL: https://issues.apache.org/jira/browse/GERONIMO-3765
Project: Geronimo
[
https://issues.apache.org/jira/browse/GERONIMO-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen updated GERONIMO-3765:
---
Component/s: monitoring
> monitoring console throws IllegalArgumentException when
[
https://issues.apache.org/jira/browse/GERONIMO-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy closed GERONIMO-3763.
-
Resolution: Fixed
Completed: At revision: 613391 in branches\2.0 and trunk (2
[
https://issues.apache.org/jira/browse/GERONIMO-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy closed GERONIMO-3764.
-
Resolution: Fixed
Completed: At revision: 613388 in branches\2.0 and trunk (2
DeployerReaper fails to cleanup the temp directories left behind by deployer
Key: GERONIMO-3764
URL: https://issues.apache.org/jira/browse/GERONIMO-3764
Project: Geronimo
Deploy New portlet does not cleanup the temp files
--
Key: GERONIMO-3763
URL: https://issues.apache.org/jira/browse/GERONIMO-3763
Project: Geronimo
Issue Type: Bug
Security Level: public
24 matches
Mail list logo
