On Mar 1, 2008, at 8:31 PM, Vasily Zakharov wrote:
I have no idea what's going on with it. It really ticks me off as
that's the kind of feature you should have to enable in a parser not
disable.
Is it? I thought the engine should first check if the necessary scheme
is present locally and onl
This is the one i ve received...
Hey.. may be my registration to usrlist is not done properly... I will do
it..
and let u know if i need any thing required...
On 03/03/2008, Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
>
> Test dev mail - please ignore.
>
--
Regards,
Praveena Chalamcha
Jarek's statements reflect my own sentiments as well.
To address your concern about key collisions, I don't think that it
will happen if modules get their own resource file. It was never a
problem for me.
Regards,
Alan
On Feb 27, 2008, at 7:57 AM, B.J. Reed wrote:
Thanks, each plugin/mo
On Feb 26, 2008, at 7:30 AM, B.J. Reed wrote:
I have written a patch to get Geronimo messages from a common set of
resource bundles. Included in the patch is the
GeronimoMessageBundle.java, GeronimoMessageBundleTest.java, and the
start of the geronimo-messages.properties file.
Neat!
2
:-) Good news.
On Tue, Mar 4, 2008 at 4:05 AM, Hernan Cunico <[EMAIL PROTECTED]> wrote:
> Hi All,
> I'm normally the one making the requests for contributions to the doc,
> asking for your help and usually not too happy with the content we end up
> having.
>
> Well, today it's a totally different
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-291.
Resolution: Fixed
Fix Version/s: 2.1.0
Resolved with revis
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-287.
Resolution: Fixed
Resolved with revision 633359
> Unable to
I thought about this some more and think that I am firmly in favor of A.
1. anything else is going to result in changing the directory name of
the plugin build project using svn cp foo-1.1 foo-1.2 or svn mv
foo-1.1 foo-1.2 when either the source project or geronimo version
changes. This i
Hi:
I've tried to load the same jsp (plain jsp) in both geronimo 1.1.1 and
2.0, ends up 2.0 is very very slow. It takes around 1 min just to load a
login page. Is there any way I can speed this up? It seems it isn't the
problem when I"m using geronimo 1.1.1
I've set the geronimo_opts
Hi All,
I'm normally the one making the requests for contributions to the doc, asking
for your help and usually not too happy with the content we end up having.
Well, today it's a totally different scenario. I wanted to truly thank all of
you contributing to the project's documentation. There i
[
https://issues.apache.org/jira/browse/GERONIMO-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574752#action_12574752
]
David Jencks commented on GERONIMO-3878:
bq.Yes, that's right. It works if you d
Maybe I should have said before why I'm inclined to go for B then C
in this order: My understanding is that by convention the geronimo
version is encoded in the plugin repository URI. So, when a user
browses the plugins within a repository, he already does know which
Geronimo version is tar
On Mar 3, 2008, at 8:33 AM, Joe Bohn wrote:
David Jencks wrote:
We've previously discussed and I think agreed that the documented
release process is seriously out of date with the current
capabilities of maven.
I'm proposing we update the documented release process to rely
primarily on th
Yep, there are a couple questions that Kevan had on 11/12/2007 (license
headers and assembly file permissions) that need to be addressed.
Hopefully, I can break away from other work this week and try to look at
it again
If you have time to help, that would be great. I'm using SUSE to buil
[
https://issues.apache.org/jira/browse/GERONIMO-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574698#action_12574698
]
Sangjin Lee commented on GERONIMO-3888:
---
Thanks for the great find, Alex... Someh
[
https://issues.apache.org/jira/browse/GERONIMO-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3889:
--
Attachment: GERONIMO-3889.patch
A suggested fix.
Essentially it is adopting the same owners
[
https://issues.apache.org/jira/browse/GERONIMO-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-3891.
---
Resolution: Fixed
Committed a fix to trunk (revision 633242) and branches/2.1 (revision 63
[
https://issues.apache.org/jira/browse/GERONIMO-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reassigned GERONIMO-3891:
-
Assignee: Jarek Gawor
> Derby Log Viewer portlet - ignores all search criteria
> -
[
https://issues.apache.org/jira/browse/GERONIMO-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn resolved GERONIMO-3866.
Resolution: Fixed
Fix Version/s: 2.2
2.1.1
> Export Plugin from web co
[
https://issues.apache.org/jira/browse/GERONIMO-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3880.
--
Resolution: Fixed
trunk rev 633225
2.1 rev 633227
2.0 rev 633229
> PersistenceUnitInfo.getJ
[
https://issues.apache.org/jira/browse/GERONIMO-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks reopened GERONIMO-3880:
similar null managedClassNames that toplink essentials complains about.
> PersistenceUnitIn
[
https://issues.apache.org/jira/browse/GERONIMO-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Leong updated GERONIMO-3893:
---
Description: In the administration console->plugin installer. When trying
to install plug
When installing plugins, exception thrown when no plugins selected
--
Key: GERONIMO-3893
URL: https://issues.apache.org/jira/browse/GERONIMO-3893
Project: Geronimo
Issue Type: B
Good point! I agree that these portlets are easily broken. We'll
need to come up with some plans to automate them.
I'll look into possibilities of automating them along with the
Selenium IDE that David J suggested.
Lin
On Fri, Feb 29, 2008 at 9:42 AM, Vamsavardhana Reddy
<[EMAIL PROTECTED]> w
I'm for A. The geronimo version and external app version are already
provided in the plugin descriptor so no need to duplicate this info in
the plugin version.
Jarek
On Sat, Mar 1, 2008 at 8:18 PM, David Jencks <[EMAIL PROTECTED]> wrote:
> How are we going to name plugins for external apps, such
On Mar 1, 2008, at 8:18 PM, David Jencks wrote:
How are we going to name plugins for external apps, such as roller
or apache directory?
There are three versions involved:
1. geronimo version
2. external app version
3. plugin version
I figure if we're developing/releasing it the groupId is g
David Jencks wrote:
We've previously discussed and I think agreed that the documented
release process is seriously out of date with the current capabilities
of maven.
I'm proposing we update the documented release process to rely primarily
on the maven-release-plugin.
I've written this up h
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-262:
---
Summary: Update 2.1.0 update site (was: Create 2.1.0 update site)
Create 2.1.0 staging site
-
Key: GERONIMODEVTOOLS-291
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-291
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter: Tim McConnell
Ass
Geronimo Revision: 633072 built with tests included
See the full build-0800.log file at
http://geronimo.apache.org/maven/server/binaries/2.1/20080303/build-0800.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/2.1/20080303
[INFO] BUILD SUCCESSFUL
[INFO
I'm leaning to either A or C. A seems neater and less confusing to a user,
but it requires more effort to learn what you're actually dealing with. C
makes all that version information readily available and is very handy to
have, but all those version numbers in one identifier can be confusing.
Pl
[
https://issues.apache.org/jira/browse/GERONIMO-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574539#action_12574539
]
Kevan Miller commented on GERONIMO-3890:
Do you see similar problems with the St
Persistence.CreateEntityManagerFactory leads to an JNDI Exception in EJB
Container
--
Key: GERONIMO-3892
URL: https://issues.apache.org/jira/browse/GERONIMO-3892
Project:
David Jencks wrote:
How are we going to name plugins for external apps, such as roller or
apache directory?
There are three versions involved:
1. geronimo version
2. external app version
3. plugin version
I figure if we're developing/releasing it the groupId is going to be
o.a.g.plugins
Tha
[
https://issues.apache.org/jira/browse/GERONIMO-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574508#action_12574508
]
Ralf Baumhof commented on GERONIMO-3878:
Yes, that's right. It works if you donw
[
https://issues.apache.org/jira/browse/GERONIMO-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-3888.
Resolution: Fixed
Committed revision 633081. Mina 1.1.5 version.
Committed revision 63
Test dev mail - please ignore.
[
https://issues.apache.org/jira/browse/GERONIMO-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-3888:
--
Assignee: Rick McGuire
> AsyncHttpClient does not handle Set-Cookie directive with a
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YunFeng Ma updated GERONIMODEVTOOLS-285:
Attachment: GEP-JAXB.patch
A prototype of the JAXB in GEP, the sections o
Derby Log Viewer portlet - ignores all search criteria
--
Key: GERONIMO-3891
URL: https://issues.apache.org/jira/browse/GERONIMO-3891
Project: Geronimo
Issue Type: Bug
Security Level:
40 matches
Mail list logo
