[
https://issues.apache.org/jira/browse/GERONIMO-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia updated GERONIMO-5266:
--
Attachment: GERONIMO-5266.patch
This is a sample to demo new criteria API of JPA 2.0, the
[
https://issues.apache.org/jira/browse/GERONIMO-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5266.
-
Fix Version/s: 3.0
Resolution: Fixed
Committed revision 937938.
JavaEE6 sample - JPA
Yoko looks ok if I can get the checksum issues fixed.
I've talked with the amq guys and we are going to try to get a 5.3.2 out this
week.
My codehaus credentials stopped working (presumably due to jira problems there
as well as here) and I'm not getting password reset emails will need to
Geronimo Revision: 937941 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100426/build-0300.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100426/unit-test
I also noticed that some pages are created on wiki page but not copied to
Geronimo web site. Not sure if it's the same cause??
For example: https://cwiki.apache.org/GMOxDOC21/configuring-security.html
Click the pages shown linkage broken, the link leads to
the wiki page with
[
https://issues.apache.org/jira/browse/GERONIMO-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia updated GERONIMO-5235:
--
Attachment: GERONIMO-5235_mod.patch
Thank you, Lu Jiang for this patch.
Basically, it's
[
https://issues.apache.org/jira/browse/GERONIMO-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5235.
-
Fix Version/s: 3.0
Resolution: Fixed
Committed revision 937949.
JavaEE6 sample -
[
https://issues.apache.org/jira/browse/GERONIMO-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5236.
-
Fix Version/s: 3.0
Resolution: Fixed
The target feature has been demonstrated via the
We have had a couple of fixes in the 2.2 branch since the Geronimo 2.2 was
released. Maybe it's time to release Geronimo 2.2.1 to bring all the
available fixes to Geronimo users.
If everybody agree to release the new 2.2.1 release. I'd like to volunteer
to be the release mananger of this
Sounds like a good idea, since some users are expecting more frequent
updates. We need to go through the open JIRA list to see what remaining ones
should be fixed in v2.2.1.
-Jack
On Mon, Apr 26, 2010 at 5:22 PM, Shawn Jiang genspr...@gmail.com wrote:
We have had a couple of fixes in the 2.2
JavaEE6 sample - JSF 2.0 - AJAX interaction
---
Key: GERONIMO-5272
URL: https://issues.apache.org/jira/browse/GERONIMO-5272
Project: Geronimo
Issue Type: Sub-task
Security Level: public (Regular
JavaEE6 sample - EJB 3.1 - Singleton
Key: GERONIMO-5273
URL: https://issues.apache.org/jira/browse/GERONIMO-5273
Project: Geronimo
Issue Type: Sub-task
Security Level: public (Regular issues)
Forgot my +1 too.
On 4/25/2010 4:04 PM, Kevan Miller wrote:
Looks good. Thanks Rick! Here's my +1
--kevan
On Apr 22, 2010, at 8:07 AM, Rick McGuire wrote:
To support the upcoming Geronimo milestone release, I would like to
release Java EE 6 versions of the geronimo specifications. This
The 5.3.2 snapshot release still seems to be looking for the annotation
1.0 classes, which is breaking the trunk build.
Rick
On 4/26/2010 2:58 AM, djen...@apache.org wrote:
Author: djencks
Date: Mon Apr 26 06:58:38 2010
New Revision: 937940
URL:
The vote to release the new Geronimo Java EE 6 spec versions has passed
with 6 +1 votes and no 0 or -1 votes. The new versions will be released
to central today.
Donald Woods
Kevan Miller
Jarek Gawor
Joe Bohn
David Jencks
Rick McGuire
Rick
On 4/22/2010 8:07 AM, Rick McGuire wrote:
To
[
https://issues.apache.org/jira/browse/GERONIMO-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Jain closed GERONIMO-4892.
-
Resolution: Fixed
Farm Deployment Error if deploy more than one applications
[
https://issues.apache.org/jira/browse/GERONIMO-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12860909#action_12860909
]
Ashish Jain commented on GERONIMO-4892:
---
Applied @rev 938021 to 2.2 branch.
Farm
Geronimo Revision: 938027 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100426/build-0900.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100426/unit-test
On 4/26/2010 8:09 AM, Rick McGuire wrote:
The 5.3.2 snapshot release still seems to be looking for the
annotation 1.0 classes, which is breaking the trunk build.
This patch fixes up the activemq build so it will work with either the
1.0 or 1.1 versions of the annotations.
Rick
Rick
On
Sounds good! Thanks for volunteering.
-Donald
On 4/26/10 5:22 AM, Shawn Jiang wrote:
We have had a couple of fixes in the 2.2 branch since the Geronimo 2.2
was released. Maybe it's time to release Geronimo 2.2.1 to bring all
the available fixes to Geronimo users.
If everybody agree to
On Apr 26, 2010, at 5:22 AM, Shawn Jiang wrote:
We have had a couple of fixes in the 2.2 branch since the Geronimo 2.2 was
released. Maybe it's time to release Geronimo 2.2.1 to bring all the
available fixes to Geronimo users.
If everybody agree to release the new 2.2.1 release. I'd
Any thoughts on upgrading MyFaces from 1.2.6 - 1.2.8?
-Donald
On 4/26/10 5:22 AM, Shawn Jiang wrote:
We have had a couple of fixes in the 2.2 branch since the Geronimo 2.2
was released. Maybe it's time to release Geronimo 2.2.1 to bring all
the available fixes to Geronimo users.
If
Looks like GERONIMO-5148, GERONIMO-5180 and GERONIMO-5258 need to get
applied to 2.2.1 and trunk before we can resolve those issues and mark
2.1.5 as released.
-Donald
On 4/21/10 2:52 PM, Ashish Jain wrote:
I merged the patch that made amq trunk work to the 5.3 branch and the result
worked for me w/geronimo. Did you try building amq from source before applying
this patch? I thought amq had a pretty efficient system for pushing snapshots
but it might not be set up to build the 5.3 branch...
I wonder if anyone would have time to think about fixing GERONIMO-5256? (WADI
clustering deserializes session contents with the wrong thread context
classloader)
thanks
david jencks
On Apr 26, 2010, at 2:22 AM, Shawn Jiang wrote:
We have had a couple of fixes in the 2.2 branch since the
I started this in xbean, rev 937957, see XBEAN-148.
Basically I copied all of
framework/modules//geronimo-kernel/src/main/java/org/apache/geronimo/kernel/osgi/
into a new xbean-bundleutils except for the two geronimo specific activators
and except for moving the BundleAnnotationFinder to
On 4/26/2010 12:32 PM, David Jencks wrote:
I merged the patch that made amq trunk work to the 5.3 branch and the result
worked for me w/geronimo. Did you try building amq from source before applying
this patch? I thought amq had a pretty efficient system for pushing snapshots
but it might
Deploy New/Install New Application portlet needs some love to help out newbies
--
Key: GERONIMO-5274
URL: https://issues.apache.org/jira/browse/GERONIMO-5274
Project:
My +1
Installed plugins using staging repo at -
http://people.apache.org/~dwoods/geronimo/openjpa2/
Built and installed Daytrader 2.1.3 as a EAR from -
https://svn.apache.org/repos/asf/geronimo/daytrader/branches/2.1.3/
-Donald
On 4/23/10 4:15 PM, Donald Woods wrote:
I've created a
On Apr 26, 2010, at 10:02 AM, Rick McGuire wrote:
On 4/26/2010 12:32 PM, David Jencks wrote:
I merged the patch that made amq trunk work to the 5.3 branch and the result
worked for me w/geronimo. Did you try building amq from source before
applying this patch? I thought amq had a pretty
On 4/26/2010 1:30 PM, David Jencks wrote:
On Apr 26, 2010, at 10:02 AM, Rick McGuire wrote:
On 4/26/2010 12:32 PM, David Jencks wrote:
I merged the patch that made amq trunk work to the 5.3 branch and the result
worked for me w/geronimo. Did you try building amq from source before
Geronimo Revision: 938198 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100426/build-1500.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100426/unit-test
Kevan,
I've talked with Brian Fox and he says the checksums are recalculated when a
staging repo is promoted. So, fixing them in the staging repo would have no
lasting effect.
Based on this would you be interested in revising your -1?
thanks
david jencks
On Apr 25, 2010, at 4:27 PM, David
On Apr 26, 2010, at 5:51 PM, David Jencks wrote:
Kevan,
I've talked with Brian Fox and he says the checksums are recalculated when a
staging repo is promoted. So, fixing them in the staging repo would have no
lasting effect.
Based on this would you be interested in revising your
I think our build is still perhaps more unwieldy than it needs to be. I wonder
if using the pom import scope more would help:
1. put some large sets of dependencies in dependency management such as in
particular specs into separate management only poms
2. put versions of all the subprojects
Hi,
I've staged a release candidate for ActiveMQ 5.3.2. The main driver for this
is to get the osgi version range fixes into a release usable by the upcoming
geronimo 3.0 milestone.
The changes since the recent 5.3.1:
merging 881433 - jaxb plugin problem
changing activemq.version to match
Just wanted to pull the status of these items together so we know where
things stand and what's being worked on by who.
1) Get the specs released (up for vote now) -- Vote concluded today,
specs promoted to releases, and trunk updated to new version numbers.
2) Release the various Geronimo
On Mon, Apr 26, 2010 at 5:04 PM, David Jencks david_jen...@yahoo.com wrote:
Hi,
I've staged a release candidate for ActiveMQ 5.3.2. The main driver for this
is to get the osgi version range fixes into a release usable by the upcoming
geronimo 3.0 milestone.
The changes since the recent
I am just waiting for the release of Geronimo specs, and I would prepare a
vote for Tomcat today or tomorrow.
I think that I might need to run some simple cases in TCK to make sure that
it would not bring new issues ...
2010/4/27 Rick McGuire rick...@gmail.com
Just wanted to pull the status of
I wasn't planning to look into the felix dependencies, but I can if no one else
wants to. It will be a couple of days...
I don't think we can use the last released jdt-core at least not without some
pain.
The juddi release we are using is not currently a problem - uddi doesn't work
now and
Geronimo Revision: 938281 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100426/build-2100.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100426/unit-test
Vote passes with 4 +1 PMC votes and no other votes.
Rick McGuire
Donald Woods
David Jencks
Kevan Miller
I've promoted the staging repo and Brian Fox did something to fix the checksums.
thanks
david jencks
On Apr 22, 2010, at 7:38 PM, David Jencks wrote:
Please vote on yoko 1.1, yoko with osgi
Nice stuff Rick. This obviously took some time to prepare the licensing
information properly. Thanks!
One minor comment -- I notice that some of the new files do not have
svn:eol-style=native (i.e. LICENSE.vm). Probably because we don't define the
file type in our recommended client
JavaEE6 sample - RESTful service
Key: GERONIMO-5275
URL: https://issues.apache.org/jira/browse/GERONIMO-5275
Project: Geronimo
Issue Type: Sub-task
Security Level: public (Regular issues)
JavaEE6 sample - EJB 3.1 - Timer Service
Key: GERONIMO-5276
URL: https://issues.apache.org/jira/browse/GERONIMO-5276
Project: Geronimo
Issue Type: Sub-task
Security Level: public (Regular
45 matches
Mail list logo
