[
https://issues.apache.org/jira/browse/GERONIMO-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guang Zhe Wang updated GERONIMO-5276:
-
Attachment: (was: jira-5276.patch)
JavaEE6 sample - EJB 3.1 - Timer Service
[
https://issues.apache.org/jira/browse/GERONIMO-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guang Zhe Wang updated GERONIMO-5276:
-
Comment: was deleted
(was: GERONIMO-5276:ejbtimer-javaee6 sample)
JavaEE6 sample -
[
https://issues.apache.org/jira/browse/GERONIMO-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-4731:
--
Fix Version/s: Wish List
(was: 2.2.1)
Move to wish list.
Jetty
[
https://issues.apache.org/jira/browse/GERONIMO-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang closed GERONIMO-4329.
-
Resolution: Cannot Reproduce
Neither Rex nor I can recreate this problem in the latest build.
[
https://issues.apache.org/jira/browse/GERONIMO-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864196#action_12864196
]
Forrest Xia commented on GERONIMO-5276:
---
Nice sample!
But this sample is using
Hi,
I found that currently in xbean components, many log apis are used,
slf4j, commons-logging, and log4j. I would like to use slf4j api
everywhere. Also, I think that we could depend on slf4j-api directly, as
not all the components need to run in OSGI environment.
Thoughts ? If no
[
https://issues.apache.org/jira/browse/GERONIMO-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang closed GERONIMO-4238.
-
Fix Version/s: 2.1.5
Resolution: Fixed
#2 #3 were fixed.
#1 is a duplicate of
[
https://issues.apache.org/jira/browse/GERONIMO-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864218#action_12864218
]
Shawn Jiang commented on GERONIMO-4977:
---
Closing this JIRA.
Kan,
Do you still
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tang Yin Qi updated GERONIMO-5273:
--
Attachment: GERONIMO-5273.patch
JavaEE6 sample - EJB 3.1 - Singleton
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tang Yin Qi updated GERONIMO-5273:
--
Attachment: (was: GERONIMO-5273.patch)
JavaEE6 sample - EJB 3.1 - Singleton
[
https://issues.apache.org/jira/browse/GERONIMO-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guang Zhe Wang updated GERONIMO-5276:
-
Attachment: (was: jira-5276.patch)
JavaEE6 sample - EJB 3.1 - Timer Service
[
https://issues.apache.org/jira/browse/GERONIMO-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864222#action_12864222
]
Kan Ogawa commented on GERONIMO-4977:
-
Shawn,
Please close this issue for the time
[
https://issues.apache.org/jira/browse/GERONIMO-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5276.
-
Fix Version/s: 3.0
Resolution: Fixed
Committed revision 941190.
Thank you for this
Geronimo Revision: 941172 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505
[INFO] BUILD
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tang Yin Qi updated GERONIMO-5273:
--
Attachment: (was: GERONIMO-5273.patch)
JavaEE6 sample - EJB 3.1 - Singleton
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tang Yin Qi updated GERONIMO-5273:
--
Attachment: GERONIMO-5273.patch
JavaEE6 sample - EJB 3.1 - Singleton
On 5/5/2010 3:03 AM, Ivan wrote:
Hi,
I found that currently in xbean components, many log apis are used,
slf4j, commons-logging, and log4j. I would like to use slf4j api
everywhere. Also, I think that we could depend on slf4j-api directly,
as not all the components need to run in OSGI
[
https://issues.apache.org/jira/browse/GERONIMO-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-5153:
--
Fix Version/s: 2.2.2
(was: 3.0)
(was: 2.2.1)
Doing some last minute dependency checking on the components. I see
that the txmanager components have a parent pom of
geronimo-txmanager-parent 3.0-SNAPSHOT, but I can't seem to find this
version anywhere in the svn tree. The last version in tags is 2.1.4 and
there is nothing in trunk for
On 5/5/2010 6:45 AM, Rick McGuire wrote:
Doing some last minute dependency checking on the components. I see
that the txmanager components have a parent pom of
geronimo-txmanager-parent 3.0-SNAPSHOT, but I can't seem to find this
version anywhere in the svn tree. The last version in tags is
Geronimo Revision: 941255 built with tests included
See the full build-0800.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/build-0800.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/unit-test-reports
On 5/5/10 6:45 AM, Rick McGuire wrote:
Doing some last minute dependency checking on the components. I see
that the txmanager components have a parent pom of
geronimo-txmanager-parent 3.0-SNAPSHOT, but I can't seem to find this
version anywhere in the svn tree. The last version in tags is 2.1.4
I am working on the ASM-based BundleClassFinder, if possible, I hope to
include it in the coming XBean 3.7 release.
Currently, most codes are done, and I am running some cases against it !
2010/5/5 Rick McGuire rick...@gmail.com
On 5/5/2010 3:03 AM, Ivan wrote:
Hi,
I found that currently
On 5/5/2010 8:12 AM, Joe Bohn wrote:
On 5/5/10 6:45 AM, Rick McGuire wrote:
Doing some last minute dependency checking on the components. I see
that the txmanager components have a parent pom of
geronimo-txmanager-parent 3.0-SNAPSHOT, but I can't seem to find this
version anywhere in the svn
forget my +1 :-)
2010/5/5 Joe Bohn joe.b...@earthlink.net
+1 (assuming the potential license issue mentioned below is not an issue)
I was able to build and run the new tomcat image.
The license issue pointed out last time is now resolved but there is one
other potential issue. I noticed
On May 4, 2010, at 1:56 PM, Joe Bohn wrote:
+1 (assuming the potential license issue mentioned below is not an issue)
I was able to build and run the new tomcat image.
The license issue pointed out last time is now resolved but there is one
other potential issue. I noticed a number
Geronimo Revision: 941274 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505
[INFO] BUILD
[
https://issues.apache.org/jira/browse/GERONIMO-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-5279.
---
Assignee: Jarek Gawor
Fix Version/s: 3.0
Resolution: Fixed
Committed
On Wed, May 5, 2010 at 7:45 PM, Kevan Miller kevan.mil...@gmail.com wrote:
On May 4, 2010, at 1:56 PM, Joe Bohn wrote:
+1 (assuming the potential license issue mentioned below is not an issue)
I was able to build and run the new tomcat image.
The license issue pointed out last time
Joe has already found the parent for you :-)
I'm working on cleaning up the poms here, mostly considering what package
versions we might want on import and export, I hope to call a vote on this and
the jaspi component later today.
thanks
david jencks
On May 5, 2010, at 3:50 AM, Rick McGuire
Many irrelevant build properties end up in the manifest
---
Key: GERONIMO-5286
URL: https://issues.apache.org/jira/browse/GERONIMO-5286
Project: Geronimo
Issue Type: Bug
Security
Someone needs to make all the maven properties start with a lowercase letter so
they don't end up in the generated bundle manifest.
I'm not at all sure that the properties like PlanServerHostname are still used,
in which case they could be removed. If they are still used they could be made
to
On 5/5/2010 1:38 PM, David Jencks wrote:
Someone needs to make all the maven properties start with a lowercase letter so
they don't end up in the generated bundle manifest.
I'm not at all sure that the properties like PlanServerHostname are still used,
in which case they could be removed. If
Geronimo Revision: 941395 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/build-1400.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/unit-test-reports
[
https://issues.apache.org/jira/browse/GERONIMO-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-5286:
--
Assignee: Rick McGuire
Many irrelevant build properties end up in the manifest
Please vote for the geronimo transaction manager component consisting of the
transaction manager and connector framework 3.0.
The main changes in this release are:
- connector 1.6 support
- retry support in the transaction manager (not well tested yet).
Due to the retry support the interfaces
[
https://issues.apache.org/jira/browse/GERONIMO-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864459#action_12864459
]
Jarek Gawor commented on GERONIMO-5213:
---
In revision 941434 I fixed the
[
https://issues.apache.org/jira/browse/GERONIMO-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-5286.
Resolution: Fixed
Committed revision 941475.
Many irrelevant build properties end up
Geronimo Revision: 941430 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505
[INFO] BUILD
After recently updating and building Geronimo to rev. 941434 I'm seeing
an error starting the tomcat javaee6 assembly or the deploy script:
Using JRE_HOME:
/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home
Artifact org/apache/sshd/sshd-core/0.3.0/sshd-core-0.3.0.jar not found
I've recently upgraded karaf to sshd 0.4.0-snaphot, so that may be the
reason.
On Wed, May 5, 2010 at 23:36, Joe Bohn joe.b...@earthlink.net wrote:
After recently updating and building Geronimo to rev. 941434 I'm seeing an
error starting the tomcat javaee6 assembly or the deploy script:
Please vote for the geronimo-jaspi 1.1 component.
The major changes to this release are:
- packaged as an osgi bundle
- fairly non-functional classloading in 1.0 replaced by Rick's ProviderLocator
that actually works in osgi.
- dependencies upgraded to use bundleized dependencies.
I spent some
Geronimo Revision: 941542 built with tests included
See the full build-2000.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/build-2000.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/unit-test-reports
I think that our four version numbers could help us, while Tomcat always has
three version number. In next iteration, we call our version 7.0.0.1, which
means more changes are merged from Tomcat 7 dev tree ..
2010/5/5 Vamsavardhana Reddy c1vams...@gmail.com
On Wed, May 5, 2010 at 7:45 PM,
Yeah, you can ignore for now. Waiting for sshd 0.4 to be released. The
published 0.4-SNAPSHOT has some other issues.
Jarek
On Wed, May 5, 2010 at 5:36 PM, Joe Bohn joe.b...@earthlink.net wrote:
After recently updating and building Geronimo to rev. 941434 I'm seeing an
error starting the tomcat
IIRC I came up with the 4 digits and I was thinking exactly this, we can
release many ports of a given tomcat release this way. Having the same number
of digits as tomcat won't work. If they used 4 we'd be in trouble :-)
thanks
david jencks
On May 5, 2010, at 5:43 PM, Ivan wrote:
I think
Agree, We can just add a comment in its pom, which records the revision our
external tomcat based on.
-Rex
2010/5/6 Ivan xhh...@gmail.com
I think that our four version numbers could help us, while Tomcat always
has three version number. In next iteration, we call our version 7.0.0.1,
which
Geronimo Revision: 941556 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505
[INFO] BUILD
[
https://issues.apache.org/jira/browse/GERONIMO-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chi Runhua resolved GERONIMO-4637.
--
Assignee: Chi Runhua
Resolution: Fixed
Doc is already updated for G2.2.
Need
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864632#action_12864632
]
Forrest Xia commented on GERONIMO-5273:
---
pls make the patch from the root
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tang Yin Qi updated GERONIMO-5273:
--
Attachment: GERONIMO-5273.patch
JavaEE6 sample - EJB 3.1 - Singleton
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864638#action_12864638
]
Tang Yin Qi commented on GERONIMO-5273:
---
OK. It's my new patch form the root
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tang Yin Qi updated GERONIMO-5273:
--
Attachment: (was: GERONIMO-5273.patch)
JavaEE6 sample - EJB 3.1 - Singleton
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5273.
-
Fix Version/s: 3.0
Resolution: Fixed
Committed revision 941569.
Thanks Tang Yin Qi
Hi,
Before the milestone release we might have to figure out what osgi
version (if any) the Geronimo packages should be exported at. I can
think of a few possibilities:
1) No version exported for milestone releases. In the final release
everything would be exported with 3.0.0 version.
2) Use
[
https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864638#action_12864638
]
Tang Yin Qi edited comment on GERONIMO-5273 at 5/6/10 12:48 AM:
56 matches
Mail list logo
