[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-263.
Resolution: Fixed
Fix Version/s: 2.1.0
JAXB refactoring fo
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-306.
Resolution: Fixed
Fix Version/s: 2.1.0
Assignee: T
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-302.
Resolution: Fixed
Fix Version/s: 2.1.0
Resolved with the r
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-298.
Resolution: Fixed
Resolved with resolution of GERONIMODEVTOOLS-30
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-301.
Resolution: Fixed
Fix Version/s: 2.1.0
Resolved with the r
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-300.
Resolution: Fixed
Fix Version/s: 2.1.0
Resolved with the r
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-311.
Resolution: Fixed
Fix Version/s: 2.1.0
Assignee: T
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell reopened GERONIMODEVTOOLS-291:
Reopening as needs to be retested after the JAXB refactoring is compl
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-315.
Resolution: Fixed
Fix Version/s: 2.1.0
Resolved with revis
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-304.
Resolution: Fixed
Fix Version/s: 2.1.0
Refactoring no long
Geronimo Revision: 642654 built with tests included
See the full build-2100.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080329/build-2100.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080329
[INFO] BUILD SUCCESSFUL
[INFO
[
https://issues.apache.org/jira/browse/GERONIMO-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583392#action_12583392
]
Erik B. Craig commented on GERONIMO-3937:
-
Committed revision 642673 to 2.1
Comm
[
https://issues.apache.org/jira/browse/GERONIMO-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik B. Craig closed GERONIMO-3937.
---
Resolution: Fixed
Fix Version/s: 2.2
2.1.1
> java.lang.Arithmeti
[
https://issues.apache.org/jira/browse/GERONIMO-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik B. Craig updated GERONIMO-3937:
Affects Version/s: 2.1.1
> java.lang.ArithmeticException: / by zero
> --
[
https://issues.apache.org/jira/browse/GERONIMO-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik B. Craig resolved GERONIMO-3943.
-
Resolution: Fixed
Fix Version/s: 2.2
> Upgrade dojo plugin to dojo version 1.1.
[
https://issues.apache.org/jira/browse/GERONIMO-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583390#action_12583390
]
Erik B. Craig commented on GERONIMO-3943:
-
Committed revision 642662.
> Upgrad
Upgrade dojo plugin to dojo version 1.1.0
-
Key: GERONIMO-3943
URL: https://issues.apache.org/jira/browse/GERONIMO-3943
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular i
Hi, all,
As far as I understand, Yoko is now a Geronimo sub-component, but as
far as I remember, there was an agreement [1] to keep the core ORB a
standalone
component so that it would be usable by, e. g. Harmony.
Harmony now uses a very (more than a year) old version of Yoko and it
causes proble
Geronimo Revision: 642529 built with tests included
See the full build-0800.log file at
http://geronimo.apache.org/maven/server/binaries/2.1/20080329/build-0800.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/2.1/20080329
[INFO] BUILD SUCCESSFUL
[INFO
Oh, ok. I see what's what. The student deadline hasn't passed but the
project deadline has. I'm less confused now. Carry on! ;)
~Jason
On Sat, Mar 29, 2008 at 9:04 AM, Jacek Laskowski <[EMAIL PROTECTED]>
wrote:
> On Sat, Mar 29, 2008 at 2:02 PM, Jason Warner <[EMAIL PROTECTED]> wrote:
> > I
On Sat, Mar 29, 2008 at 2:02 PM, Jason Warner <[EMAIL PROTECTED]> wrote:
> I thought the deadlines had already passed? Didn't they already post the
> list of accepted projects?
Can't be according to the schedule -
http://code.google.com/opensource/gsoc/2008/faqs.html#0.1_timeline.
Jacek
--
Jac
On Sat, Mar 29, 2008 at 7:19 AM, Tim McConnell <[EMAIL PROTECTED]> wrote:
> #3. Remove support altogether for v1.1 in this release of the GEP -- support
> only the v2.0 and v2.1 Geronimo servers (the least expensive in terms of time
> and testing required)
s/althogether/temporarily which means
I thought the deadlines had already passed? Didn't they already post the
list of accepted projects?
~Jason Warner
On Sat, Mar 29, 2008 at 8:59 AM, Jacek Laskowski <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> Just sent an email to various Polish mailing lists about GSoC
> (http://code.google.com/opensou
Hi,
Just sent an email to various Polish mailing lists about GSoC
(http://code.google.com/opensource/gsoc/2008) my willingness to become
a mentor or just to find one (that's about you) and thought about some
ideas for prospect GSoC participants. Why could these ideas be? What
tasks are the low-han
Hi Tim,
Given that we already have a release that supports 1.1, I'd be inclined to
go with #3 as well. It'd make it a little clunkier to go from 2.0 to
2.1(server), though, from what I understand. Correct me if I'm wrong,
but the
process for that would be to port your app to 2.0 server, and then
25 matches
Mail list logo