The address of httpbinding port in the WSDL query is not updated
Key: GERONIMO-4436
URL: https://issues.apache.org/jira/browse/GERONIMO-4436
Project: Geronimo
Issue Type: Bug
[
https://issues.apache.org/jira/browse/GERONIMO-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated GERONIMO-4436:
---
Attachment: Geronimo-4436.patch
Please help to review it, thanks !
The address of httpbinding port in
Geronimo Revision: 722333 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081202/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081202
[INFO] BUILD
David Jencks wrote:
In order to get the build to work with my use of nexus I've added the
trunk svn repo (server/trunk/repository) to the nexus repositories.
This makes me wonder if we should just set up a single repo in svn and
put all our private builds there rather than having
[
https://issues.apache.org/jira/browse/GERONIMO-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-4229:
---
Fix Version/s: 2.2
2.1.4
Assignee: Jarek Gawor
Added fix
[
https://issues.apache.org/jira/browse/GERONIMO-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652364#action_12652364
]
Donald Woods commented on GERONIMO-4415:
We need to resolve this before we
+1 to not include Monitoring in the default server assemblies for 2.2.
+0 for moving to geronimo/plugins, as leaving it in the server branch
would be fine for now (wondering if we'll need a new version of the
plugin for every major release, due to newer levels of OpenEJB and/or
OpenJPA.)
[
https://issues.apache.org/jira/browse/GERONIMO-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated GERONIMO-4343:
Attachment: helloworld-jsf.diff
The helloworld-jsf.diff patch adds the start of a JSF sample
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652369#action_12652369
]
Jason Dillon commented on GSHELL-81:
Why was this reopened?
Depdendency on sun.*
There are some code and configuration changes to use the latest gshell.
--jason
On Dec 1, 2008, at 10:31 PM, Jarek Gawor wrote:
Jason,
Will the existing gshell commands need to be updated to work with the
latest gshell?
Jarek
On Fri, Nov 28, 2008 at 4:59 AM, Jason Dillon [EMAIL PROTECTED]
Donald Woods wrote:
David Jencks wrote:
In order to get the build to work with my use of nexus I've added the
trunk svn repo (server/trunk/repository) to the nexus repositories.
This makes me wonder if we should just set up a single repo in svn and
put all our private builds there rather
Our track record on releasing independent plugins isn't very good. It
seems to add a lot of overhead and process for little value.
How about the following:
- Keep the monitoring console in the server svn branch
- Release the monitoring console plugin when the server is released
(versioned to
I agree
Joe
Donald Woods wrote:
If it is no longer used, then #1 sounds like the right approach.
-Donald
Jarek Gawor wrote:
Hi,
I was looking at GERONIMO-4229 today (please see the bug and my
comments for details). There is a remaining issue with the
GERONIMO_BASE property and what it
comments inline...
--- On Mon, 12/1/08, Jarek Gawor [EMAIL PROTECTED] wrote:
From: Jarek Gawor [EMAIL PROTECTED]
Subject: GERONIMO-4229
To: Geronimo Dev dev@geronimo.apache.org
Date: Monday, December 1, 2008, 5:33 PM
Hi,
I was looking at GERONIMO-4229 today (please see the bug and my
comments
Hi JS,
Vamsi generated some doc --
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Installing+the+Tuscany+Plugin+for+Geronimo
Although it's not working for me, at the moment... Vamsi, do those
instructions work for you?
More comments below...
On Dec 1, 2008, at 12:40 PM, mobyjobs
If it is no longer used, then #1 sounds like the right approach.
-Donald
Jarek Gawor wrote:
Hi,
I was looking at GERONIMO-4229 today (please see the bug and my
comments for details). There is a remaining issue with the
GERONIMO_BASE property and what it does. The Java system property that
[
https://issues.apache.org/jira/browse/GERONIMO-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-4436.
---
Resolution: Fixed
Fix Version/s: 2.2
2.1.4
Assignee:
Joe Bohn wrote:
Donald Woods wrote:
David Jencks wrote:
In order to get the build to work with my use of nexus I've added the
trunk svn repo (server/trunk/repository) to the nexus repositories.
This makes me wonder if we should just set up a single repo in svn
and put all our private
[
https://issues.apache.org/jira/browse/GERONIMO-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652419#action_12652419
]
Jeff Lu commented on GERONIMO-3316:
---
I will test it this week and let you know. Thank
Hi Jarek,
It looks like the Axis2 1.5 release didn't happen yet. Is there a new
target?
Also, my offer still stands to help with the concurrent spec release if
you want. Let me know.
Thanks,
Joe
Jarek Gawor wrote:
Axiom, XmlSchema, and Woden are all dependencies of Axis2. There is a
As many of you already know from the Geronimo dev list - we're looking to
release Geronimo 2.2 by mid January. However, we need a number of snapshots
released prior to that and xBean trunk (3.5-SNAPSHOT) is among them for
xbean-finder, xbean-naming, and xbean-reflect. Any possibility we could
Upgrade to Jetty 6.1.14
---
Key: GERONIMO-4437
URL: https://issues.apache.org/jira/browse/GERONIMO-4437
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components:
Sounds good to me.
On Tue, Dec 2, 2008 at 6:12 PM, Joe Bohn [EMAIL PROTECTED] wrote:
As many of you already know from the Geronimo dev list - we're looking to
release Geronimo 2.2 by mid January. However, we need a number of snapshots
released prior to that and xBean trunk (3.5-SNAPSHOT) is
[
https://issues.apache.org/jira/browse/GERONIMO-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods closed GERONIMO-4437.
--
Resolution: Fixed
Rev722538 in trunk (2.2-SNAPSHOT)
Upgrade to Jetty 6.1.14
On Dec 2, 2008, at 5:41 AM, Donald Woods wrote:
David Jencks wrote:
In order to get the build to work with my use of nexus I've added
the trunk svn repo (server/trunk/repository) to the nexus
repositories.
This makes me wonder if we should just set up a single repo in svn
and put all
I delete my local m2 repo at least once a week (usually when switching
between 2.1.4 and 2.2 builds to ensure truly clean builds.)
Also, the automated 2.0/2.1/trunk builds that run several times a day
always use a clean m2 repo.
Seems that we would be increasing the load on svn.apache.org
Thanks for help. The issue with my setup turned out was wrong tuscany-core
version. I was using latest tuscany-core.1.4-SNAPSHOT.jar. As I thought the
fix in tuscany-core.1.3.jar submitted in the Jira was also applied to the
tuscany branch. But it looks like I needed to change version from
Prevent geronimo contamination from deployments from multiple workspaces
Key: GERONIMODEVTOOLS-540
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540
Project:
[
https://issues.apache.org/jira/browse/GERONIMO-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652489#action_12652489
]
Donald Woods commented on GERONIMO-4295:
Rev722599 in trunk (2.2-SNAPSHOT)
I'm working on updating the daytrader/branches/2.1 for a 2.1.3 release
(will rename it to branches/2.1.3 shortly.) Once everything is ready,
I'll put it up for a vote.
BTW - I'm not creating a branches/2.1 for on-going maintenance, as if it
is ever needed, we can copy over the 2.1.3 tag to
TransactionSynchronizationRegistry.getTransactionKey should return null when
transaction is not associated with the current thread
--
Key:
Add MTOM feature testing in the webservice testsuite
Key: GERONIMO-4439
URL: https://issues.apache.org/jira/browse/GERONIMO-4439
Project: Geronimo
Issue Type: Test
Security Level:
[
https://issues.apache.org/jira/browse/GERONIMO-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Sun resolved GERONIMO-4438.
---
Resolution: Fixed
Fix Version/s: 2.2
fixed in txmanager 2.2-snapshot and 2.1.1 branch (see
I think this could become reality if we have a geronimo/repository in
svn, then have it automatically exported to our zone for access by
builds. I still don't think that accessing the svn tree directly from
maven is a good idea.
--jason
On Dec 2, 2008, at 9:08 PM, Joe Bohn wrote:
Hi Lin,
A few questions:
- Why modify branches/2.1.1? I'm not sure, but it looks like this is an
old branch that was subsequently copied to tags/2.1.1 (rather than moved
to tags).
- Where is the new testTransactionKey() method used that was added here
and in trunk?
- Is this something that
I'm not sure which recent changes are causing this but I'm getting the
following build error in trunk now:
[ERROR] FATAL ERROR
[INFO]
[INFO]
Never mind. I got things going again after doing rm -rf
~/.m2/repository/org/apache/tomcat
Jarek
On Tue, Dec 2, 2008 at 10:50 PM, Jarek Gawor [EMAIL PROTECTED] wrote:
I'm not sure which recent changes are causing this but I'm getting the
following build error in trunk now:
[ERROR] FATAL
I've been working on the Genesis 2.0 site muck for the upcoming GShell
release, and I have the site generation bits work, but not the custom
skin. I think the entire skin needs to be re-crafted. I don't think
I am going to have time to do this for the first Genesis 2.0 release,
maybe
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Delos Dai updated GERONIMODEVTOOLS-521:
---
Attachment: 521.patch
Sign features so the eclipse update manager
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652692#action_12652692
]
Delos Dai commented on GERONIMODEVTOOLS-521:
I think you mean we
On Tue, Dec 2, 2008 at 9:14 PM, Kevan Miller [EMAIL PROTECTED] wrote:
Hi JS,
Vamsi generated some doc --
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Installing+the+Tuscany+Plugin+for+Geronimo
Although it's not working for me, at the moment... Vamsi, do those
instructions work
Hi,
I'm interested with Geronimo development and already had Apache CLA
signed. I want to subscribe mail list [EMAIL PROTECTED]
Thanks!
Best regard,
Han Hong Fang
Geronimo Revision: 722714 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081203/build-2100.log
See the unit test reports at
Send mail to [EMAIL PROTECTED] .
++Vamsi
On Wed, Dec 3, 2008 at 11:23 AM, han hongfang [EMAIL PROTECTED] wrote:
Hi,
I'm interested with Geronimo development and already had Apache CLA
signed. I want to subscribe mail list [EMAIL PROTECTED]
Thanks!
Best regard,
Han Hong Fang
--
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-81.
--
Resolution: Won't Fix
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
[
https://issues.apache.org/jira/browse/GSHELL-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-82:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Defer until next release.
[
https://issues.apache.org/jira/browse/GSHELL-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-47:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Defer until next release.
Add
[
https://issues.apache.org/jira/browse/GSHELL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-69:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Defer until next release.
gsh
[
https://issues.apache.org/jira/browse/GSHELL-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-68:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Defer until next release.
CLP
[
https://issues.apache.org/jira/browse/GSHELL-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-67:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Defer until next release.
Thanks for fixing this, I ran out of time after realizing it caused a
problem. I made a couple more tweaks to get the dependencies.xml back
to where they were in rev 722795
david jencks
On Dec 2, 2008, at 7:03 PM, [EMAIL PROTECTED] wrote:
Author: dwoods
Date: Tue Dec 2 19:03:40 2008
New
[
https://issues.apache.org/jira/browse/GSHELL-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-43:
---
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
Add role-based layout selection
[
https://issues.apache.org/jira/browse/GSHELL-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-23.
--
Resolution: Fixed
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
I guess we could even run a Nexus on our zone too...
--jason
On Dec 2, 2008, at 8:12 AM, David Jencks wrote:
In order to get the build to work with my use of nexus I've added
the trunk svn repo (server/trunk/repository) to the nexus
repositories.
This makes me wonder if we should just
54 matches
Mail list logo
