David,
I was digging through your sandbox code and found the BundleClassLoader
implementation. In order for this to be generally useful, it's going to
need to handle resources as well as classes. Is there some reason why
this is not implemented here? If it's just something that's on your
+1
Guillaume Nodet wrote:
The Aries podling has just been accepted (see
http://incubator.apache.org/aries/) and would be a much better place
for the blueprint implementation that has been developped in Geronimo.
This vote is mainly for donating the code to the Aries project and
maintain it
Guillaume Nodet wrote:
Some time ago, a few Geronimo committers have started an
implementation of the OSGi Blueprint Services spec, which is basically
an OSGi standardized version of Spring-DM (the next version of
Spring-DM being the RI of this spec).
The code was developed at Geronimo mostly
Jarek Gawor wrote:
I'm +1 for the move.
I'm just curious. Is the plan to move the Blueprint trunk and tags? or
just trunk?
I suspect the tags really should remain here for the benefit of anybody
looking for the code for the one version that has been released from the
Geronimo project.
David Jencks wrote:
On Sep 22, 2009, at 10:50 PM, Ivan wrote:
After reading some code changes of the geronimo-kenel in the sanbox,
I found that we keep the Geronimo kenel as an OSGI service, and each
Configuration ( or a bundle) will search it and start the
configuration as we do in the
+1
Guillaume Nodet wrote:
I've uploaded another 1.0.0 release of the blueprint project.
I think I've addressed all the issues raised in the discussion thread.
The staging repository is available at:
https://repository.apache.org/content/repositories/geronimo-staging-005/
The corresponding
David Jencks wrote:
I've made some headway in my sandbox osgi framework. I now have
pretty much all the modules building as bundles and have the
car-maven-plugin working enough to build several plugins. I'm a bit
stuck on a classloading problem in which a bundle appears to be able
to load a
+1
David Jencks wrote:
I've set up a release candidate for the transaction manager and
connector code 2.1.3, needed for geronimo 2.2:
https://repository.apache.org/content/repositories/geronimo-staging-058/
Site staged at:
+1
David Jencks wrote:
I've built a release candidate for the jacc spec jar:
https://repository.apache.org/content/repositories/geronimo-staging-002/
Site is staged here:
http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jacc_1.1_spec/1.0.2/
Along with a bunch of build
+1
David Jencks wrote:
It's time for the first release of our jaspic implementation for
inclusion in g. 2.2.
Release artifacts staged here:
https://repository.apache.org/content/repositories/geronimo-staging-003/
Site staged here:
+1
David Jencks wrote:
I've prepared a release candidate for xbean 3.6:
https://repository.apache.org/content/repositories/geronimo-staging-053/
Site staged at:
http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/
It looks like we fixed 11 issues for 3.6:
There's also the question of whether we should be releasing this before
the blueprint spec is officially released. This should be soon, but I
don't think the voting on the RI and CT has completed yet. There is
always the possibility of a last second change.
Rick
Kevan Miller wrote:
Hi
I think there may be a problem with the NOTICES file for the api jar
files. The sources contained there are the OSGi-developed API files.
The files contain the OSGi copyright, but the NOTICES file only states
that his contains software developed at the Apache Software Foundation.
There's no
David Jencks wrote:
Without some major justification I'm seriously -1 on releasing from
the sandbox. I don't see any problem with moving this code to
components and releasing it from there, whether or not it then moves
somewhere else.
I'm also uncomfortable for the release tag for this being
David Jencks wrote:
I've been working on my sandbox framework copy on converting to use
osgi, and I've made some progress.
My basic strategy has been to replace plugin classloader usage with
Bundle (and BundleContext) use. This looks like it will work out ok.
Most of the code compiles and
I stumbled across the following presentation about Tomcat 7 yesterday,
and I was wondering how much of an impact this will be for Geronimo.
http://people.apache.org/~markt/presentations/2009-04-01-Tomcat7Servlet3.pdf
Here's the list of new items planned for the release.
New for Tomcat 7
2009/8/25 Rick McGuire rick...@gmail.com mailto:rick...@gmail.com
I've been trying to pull together some thoughts about what it
might mean for Geronimo to enable itself for OSGi applications
and what needs to be added to the server beyond just adopting
an OSGi
I've been trying to pull together some thoughts about what it might mean
for Geronimo to enable itself for OSGi applications and what needs to be
added to the server beyond just adopting an OSGi classloading model.
That sort of change would be primarily transparent for most existing
[
https://issues.apache.org/jira/browse/GERONIMO-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4808.
Resolution: Fixed
Committed revision 806491.
Javamail Session constructor
[
https://issues.apache.org/jira/browse/GERONIMO-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4611.
Resolution: Fixed
I never got a response back, but I believe this fix to be the correct
Gurkan Erdogdu wrote:
Hi;
Thanks for kicking discussion David.
As you may already know Java EE 6 will be planned to release on
November. Do you have any plan or roadmap to integrate JSR-299 with
Geronimo?
We have a tentative roadmap for implementing the Web Profile at:
with this, but I was
looking form something more specific, such as the actual areas/functions
where integration assistance is needed.
Rick
Thanks;
--Gurkan
2009/8/20 Rick McGuire rick...@gmail.com mailto:rick...@gmail.com
Gurkan Erdogdu wrote:
Hi;
Thanks for kicking
Guillaume Nodet wrote:
For more informations, see section 121.6.10 and 121.6.11 of the OSGi
compendium spec, but there is a clear different between the service
being enabled or not and the lazy / eager activation.
The lifecycle diagram in section 121.3 and sections 121.3.8 and 121.3.9
are
David Jencks wrote:
Perhaps I can be convinced otherwise but I think the attribute and
reference names should remain case sensitive. Are there other DI
systems that have case insensitive property names? What does
blueprint do?
Blueprint is case sensitive for property names, using the
+1
David Jencks wrote:
This is a vote on two bits:
genesis 2.0, a new build system foundation based on great work by
Jason Dillon and the new apache 6 pom and assembly plugin bits.
geronimo-jaspic_1.0_spec 1.0 a new spec jar for the jsr 196 jaspic
spec. This passes the jaspic signature
)
Components: persistence
Reporter: Rick McGuire
Now that the JEE6 specifications are getting closer to reality and OpenJPA is
getting closer to supporting the JPA 2.0 specification, we should have a plugin
that allows OpenJPA 2.0 to replace the 1.x version so people can start kicking
Security Level: public (Regular issues)
Components: Plugins
Reporter: Rick McGuire
The Web Profile for JEE6 is defined as containing the following JEE6
components:
* Servlet 3.0
* JavaServer Pages (JSP) 2.2
* ExpressionLanguage (EL) 2.2
* Debugging Support
I've been starting to look at what might be required to implement the
JEE6 Web Profile stack on Geronimo. The Web Profile is a fairly small
subset of the JEE6 definition oriented around writing web applications.
This profile defines the minimal set of services the server must provide
to be
Guillaume Nodet wrote:
When trying to implement the dedens-on attribute for blueprint, I had
to find my way in xbean-reflect about constructor recipes and nested
recipes.
In the ObjectRecipe, a factory-method can be set so that the object is
built by calling a static method or an instance
Guillaume Nodet wrote:
I agree that we need to join forces.
Actually, i have started experimenting with xbean-refect after having
seen your code :-)
If we are going to use generics in the implementation, it may be
easier to use the reflect package implementation classes that i wrote.
Anyway, I
Jarek Gawor wrote:
Btw, I checked in under
https://svn.apache.org/repos/asf/geronimo/sandbox/gawor/rfc124 a tiny
bit of code that I was playing around with to better understand RFC
124. I'll keep on working and experimenting with it but anyone is
welcome to join. I'm planning to add some of the
specific features so that we can use
retrotranslator if needed.
On Mon, Apr 13, 2009 at 15:12, Rick McGuire rick...@gmail.com wrote:
Jarek Gawor wrote:
Btw, I checked in under
https://svn.apache.org/repos/asf/geronimo/sandbox/gawor/rfc124 a tiny
bit of code that I was playing around
Jarek Gawor wrote:
Btw, I checked in under
https://svn.apache.org/repos/asf/geronimo/sandbox/gawor/rfc124 a tiny
bit of code that I was playing around with to better understand RFC
124. I'll keep on working and experimenting with it but anyone is
welcome to join. I'm planning to add some of the
[
https://issues.apache.org/jira/browse/GERONIMO-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4584:
--
Assignee: Rick McGuire
Opening an IMAP folder with *logs* of emails is very
[
https://issues.apache.org/jira/browse/GERONIMO-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire updated GERONIMO-4611:
---
Attachment: GERONIMO-4611.patch
Here you go.
Exchange IMAP problem
[
https://issues.apache.org/jira/browse/GERONIMO-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4611:
--
Assignee: Rick McGuire
Exchange IMAP problem
[
https://issues.apache.org/jira/browse/GERONIMO-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12694943#action_12694943
]
Rick McGuire commented on GERONIMO-4611:
Glenn, I've fixed the null pointer
[
https://issues.apache.org/jira/browse/GERONIMO-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12694951#action_12694951
]
Rick McGuire commented on GERONIMO-4611:
Oops, sorry about that. Forgot
Davanum Srinivas wrote:
Folks,
Any interest in support for RFC 124, A Component Model for OSGi?
http://www.osgi.org/download/osgi-4.2-early-draft.pdf
This is in addition to typical J2EE artifacts that we already support.
thanks,
dims
Time, I think, to give this thread a kick.
There are
+1
Joe Bohn wrote:
All,
I've prepared a second release candidate (RC2) of Geronimo Server
2.1.4 for your review and vote.
The only differences from rc1 are:
- addition of a missing license header in
plugins/console/console-filter/src/main/resources/XSRF.js
- removal of an extraneous (TBD)
-bundle is not a workable solution
for (2) ?
Rex.
2009/3/14 David Jencks david_jen...@yahoo.com
mailto:david_jen...@yahoo.com
On Mar 13, 2009, at 9:43 AM, Rick McGuire wrote:
David Jencks wrote:
I read the blog entry
Davanum Srinivas wrote:
Folks,
Any interest in support for RFC 124, A Component Model for OSGi?
http://www.osgi.org/download/osgi-4.2-early-draft.pdf
This is in addition to typical J2EE artifacts that we already support.
thanks,
dims
I think this would be a very cool thing to support. I
It has been reworked much more that just the schema changes in the
standardization process. A lot of the service dynamics have changed,
there have been some fairly signification changes to type conversions
and property injection, a brand-new metadata API, new namespace handler
support, etc.
David Jencks wrote:
I read the blog entry and discussion. The entire discussion is
predicated on the idea that osgi is close to ideal as-is and we have
no need to consider any other point of view. If you step back a bit I
see two things clearly acknowledged by everyone:
1. its useful to be
[
https://issues.apache.org/jira/browse/GERONIMO-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681247#action_12681247
]
Rick McGuire commented on GERONIMO-4529:
Ok, I understand how this fixes
[
https://issues.apache.org/jira/browse/GERONIMO-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681242#action_12681242
]
Rick McGuire commented on GERONIMO-4529:
Could you please comment on why
[
https://issues.apache.org/jira/browse/GERONIMO-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681411#action_12681411
]
Rick McGuire commented on GERONIMO-4585:
This fix looks pretty good to me
Guillaume Nodet wrote:
On Wed, Mar 11, 2009 at 08:57, Gianny Damour
gianny.dam...@optusnet.com.au mailto:gianny.dam...@optusnet.com.au
wrote:
Hi,
FWIW, I believe that improving the configuration style to simplify
the means of creating a bunch of objects in the kernel has more
David Jencks wrote:
So as mentioned below I'm starting to look into the osgi classloading
bit, sort of from the bottom.
Another approach to many of these issues is perhaps from the top,
from the point of view of going from a presumably xml plan to a bunch
of objects.
I've long thought that
The one difficulty I see in moving from the current Geronimo
classloading model to the OSGi model is dealing with the change in
granularity. In the current model, the granularity is at the jar level
and using the one-classloader-per-jar model, you get all of the classes
contained in the jar.
+1
Joe Bohn wrote:
This is a vote for a combined release of the javamail spec and the
javamail provider (+ the uber jar). The provider changes have
dependencies on the spec changes, so these need to be released at the
same time. Geronimo will need the updated uber jar for the Geronimo
+1
David Jencks wrote:
I've been working with the OpenJPA project to develop the jpa 2.0 spec
jar in our spec repository. They are ready for their first early
access milestone release.
I've staged the release here:
Security Level: public (Regular issues)
Components: CORBA
Reporter: Rick McGuire
Assignee: Rick McGuire
In some circumstances, other ORB implementations can return a null value as an
RMI encoded value. This results in a NullPointerException when the null
[
https://issues.apache.org/jira/browse/GERONIMO-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire closed GERONIMO-4447.
--
Resolution: Fixed
Committed revision 723299.
Nullpointer exception reading RMI data
[
https://issues.apache.org/jira/browse/GERONIMO-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4421:
--
Assignee: Rick McGuire
ContentType fails to parse content types with parameters
This sounds like a good thing to me too.
Rick
Guillaume Nodet wrote:
In ServiceMix we have rewritten the JAXB specs jars (2.0 and 2.1)
because we needed to be able to do some modifications for OSGi.
We'd like to move them to the Geronimo Specs subproject as it would be
more consistent and
[
https://issues.apache.org/jira/browse/GERONIMO-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4372:
--
Assignee: Rick McGuire
Wrong DEFAULT_IMAP_PORT in the Geronimo JavaMail 1.4
[
https://issues.apache.org/jira/browse/GERONIMO-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire closed GERONIMO-4372.
--
Resolution: Fixed
Committed revision 707037.
Thanks for reporting this!
Wrong
[
https://issues.apache.org/jira/browse/GERONIMO-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4352:
--
Assignee: Rick McGuire
IMAP provider: accessing parts of a multipart/mixed message
[
https://issues.apache.org/jira/browse/GERONIMO-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire updated GERONIMO-4352:
---
Attachment: GERONIMO-4352.diff
Andreas, the attached patch passes the tests I've managed
+1
Jarek Gawor wrote:
Hi,
This is a vote for SAAJ 1.3 spec jar version 1.0.1. There was only one
change from version 1.0.0:
https://issues.apache.org/jira/browse/GERONIMO-4289
Staging repo:
http://people.apache.org/~gawor/staging-repo/specs/geronimo-saaj_1.3_spec/
Staging site:
[
https://issues.apache.org/jira/browse/GERONIMO-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4344.
Resolution: Fixed
Committed revision 702800.
Thank you once again! Keep up the good
[
https://issues.apache.org/jira/browse/GERONIMO-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4344:
--
Assignee: Rick McGuire
IMAPMessage#updateHeader updates header with wrong value
[
https://issues.apache.org/jira/browse/GERONIMO-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637904#action_12637904
]
Rick McGuire commented on GERONIMO-4342:
Great1 This was largely just
[
https://issues.apache.org/jira/browse/GERONIMO-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4342.
Resolution: Fixed
Committed revision 702800.
Thank you once again! I'm curious, what
[
https://issues.apache.org/jira/browse/GERONIMO-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4342:
--
Assignee: Rick McGuire
MimeMessage#writeTo doesn't flush the encoder stream
[
https://issues.apache.org/jira/browse/GERONIMO-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4340.
Resolution: Fixed
Committed revision 702432.
Thank you for yet another patch
[
https://issues.apache.org/jira/browse/GERONIMO-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4340:
--
Assignee: Rick McGuire
MimePartDataSource incorrectly assumes that MimeMessages
[
https://issues.apache.org/jira/browse/GERONIMO-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4341:
--
Assignee: Rick McGuire
javax.mail.NoSuchProviderException: Unable to locate
[
https://issues.apache.org/jira/browse/GERONIMO-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4341.
Resolution: Fixed
Committed revision 702537. Specs
Committed revision 702543
[
https://issues.apache.org/jira/browse/GERONIMO-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4339:
--
Assignee: Rick McGuire
Calling MimeMessage#setRecipients with empty array causes
[
https://issues.apache.org/jira/browse/GERONIMO-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4339.
Resolution: Fixed
Committed revision 702234.
Thank you Andreas for providing a patch
David,
No answers for you at this point, but I think the first thing I'd do is
verify which thread context classloader is set in the case that's
working. Perhaps the problem is not in setting the thread context
loader, but rather getting it set to the correct one. Are the calls to
C
[
https://issues.apache.org/jira/browse/GERONIMO-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4307:
--
Assignee: Rick McGuire
Base64DecoderStream return int value between -128 and +127
[
https://issues.apache.org/jira/browse/GERONIMO-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire closed GERONIMO-4307.
--
Resolution: Fixed
Committed revision 696241.
Nope, definitely a bug
[
https://issues.apache.org/jira/browse/GERONIMO-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4294.
Resolution: Fixed
Assignee: Rick McGuire
Committed revision 693807.
Thanks
[
https://issues.apache.org/jira/browse/GERONIMO-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4290:
--
Assignee: Rick McGuire
pop3s: java.lang.IllegalArgumentException: hostname can't
[
https://issues.apache.org/jira/browse/GERONIMO-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4290.
Resolution: Fixed
Committed revision 693530.
pop3s
[ X] +1 Release the javamail spec and provider
Joe Bohn wrote:
This is a vote for a combined release of javamail spec and the
javamail provider (+ the uber jar). The provider changes have
depedencies on the spec changes, so these need to be released at the
same time. Geronimo will need the
hate to do this too soon only to have a new problem found right
after we've created a new release. It would be better to hold off on
this until we've got a clear target release date for a Geronimo release
that will include the new version.
Rick
-Donald
Rick McGuire wrote:
Donald Woods
would hate to do this too soon only to have a new problem
found right after we've created a new release. It would be better to
hold off on this until we've got a clear target release date for a
Geronimo release that will include the new version.
Rick
-Donald
Rick McGuire wrote:
Donald
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: mail
Reporter: Rick McGuire
Assignee: Rick McGuire
The MIME specification defines a multipart boundary string as allowing a
sequence of linear white space
[
https://issues.apache.org/jira/browse/GERONIMO-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4270.
Resolution: Fixed
Committed revision 689486.
javamail MimeMultipart not accepting
Donald Woods wrote:
Time to start the discussion on winding down changes and preparing for
a Geronimo 2.1.3 release.
Server fixes/enhancements are listed on the Release Status page -
http://cwiki.apache.org/GMOxPMGT/geronimo-213-release-status.html
Details on included security fixes in
[
https://issues.apache.org/jira/browse/GERONIMO-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4259:
--
Assignee: Rick McGuire
javax.mail.MessagingException: java.io.IOException: Base64
[
https://issues.apache.org/jira/browse/GERONIMO-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4241:
--
Assignee: Rick McGuire
NPE when calling folder.getDeletedMessageCount() for POP3
[
https://issues.apache.org/jira/browse/GERONIMO-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4259.
Resolution: Fixed
Committed revision 689126.
General cleanup of mimepart boundary
[
https://issues.apache.org/jira/browse/GERONIMO-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4241.
Resolution: Fixed
Committed revision 689140.
I was able to redo the connection
[
https://issues.apache.org/jira/browse/GERONIMO-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4260.
Resolution: Fixed
Committed revision 689164.
I was finally able to find a combination
[
https://issues.apache.org/jira/browse/GERONIMO-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4260:
--
Assignee: Rick McGuire
Multipart message from POP3 has spurious attachment
[
https://issues.apache.org/jira/browse/GERONIMO-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12625335#action_12625335
]
Rick McGuire commented on GERONIMO-4260:
I'm not able to reproduce the problem
[
https://issues.apache.org/jira/browse/GERONIMO-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire closed GERONIMO-4174.
--
Resolution: Fixed
Restructure the SMTPTransport class to use the comment MailConnection
[
https://issues.apache.org/jira/browse/GERONIMO-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4261.
Resolution: Fixed
Committed revision 688713.
MimeMessage throws
[
https://issues.apache.org/jira/browse/GERONIMO-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4241.
Resolution: Fixed
Committed revision 686218.
This fixes the NPE, but the likely result
[
https://issues.apache.org/jira/browse/GERONIMO-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire closed GERONIMO-4252.
--
Resolution: Fixed
Assignee: Rick McGuire
Committed revision 686231.
Thank you
Davanum Srinivas wrote:
Hi Rick,
just saw your name on the wiki [1]
JSR 291 OSGi containers ? - Rick McGuire
Where are we starting? Just curious about it as we just added support
in Axis2 to work well in OSGi containers [2]
I'm afraid Don seriously overstated what I'm doing with OSGi right
+1
Joe Bohn wrote:
All,
I've prepared a release candidate of Geronimo Server 2.1.2 for your
review and vote.
The source for the Geronimo Server 2.1.2 release currently resides here:
https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.2
When the release vote is approved, I will svn
is building with OSGi information in
the manifest. Here is the manifest from the jar file:
Manifest-Version: 1.0
Built-By: Rick McGuire
Created-By: Apache Maven Bundle Plugin
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Import-Package: javax.activation,javax.mail;version=1.4
You might want to try moving your m2 repository to someplace other than
the default location. I have mine at c:/.m2, and don't have any
problems building.
Rick
Lin Sun wrote:
Hi,
I have been having probs building trunk on my winxp machine. It
failed at building geronimo-jetty6-javaee5,
David Blevins wrote:
On Jul 15, 2008, at 10:55 AM, Rick McGuire wrote:
I just committed this change. It doesn't look like this is causing
any tck issues.
Guessing a lot of those places you added the 3.1 api were more or less
just in case. You definitely shouldn't need it in any modules
901 - 1000 of 1858 matches
Mail list logo
