[
https://issues.apache.org/jira/browse/GERONIMO-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5542.
-
Resolution: Fixed
Committed to trunk at revision 987382. thanks!
Add tests about new
Geronimo Revision: 987390 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100820/build-0300.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100820/unit-test
[
https://issues.apache.org/jira/browse/GERONIMO-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia reassigned GERONIMO-5528:
-
Assignee: Forrest Xia
Add test cases for JSF2.0 new features into the Geronimo
Geronimo Revision: 987381 built with tests included
See the full build-0200.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100820/build-0200.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100820
[INFO] BUILD
[
https://issues.apache.org/jira/browse/GERONIMO-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lu Jiang updated GERONIMO-5538:
---
Attachment: webbean-servlet-test.patch
Add testsuite for webbean 1.0 in Java EE 6
[
https://issues.apache.org/jira/browse/GERONIMO-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12900634#action_12900634
]
Forrest Xia commented on GERONIMO-5538:
---
Committed webbean+servlet test to trunk
[
https://issues.apache.org/jira/browse/GERONIMO-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhen Zhang updated GERONIMO-5528:
-
Attachment: jsf2.0_test.patch
this is a testsuite for two main new features of JSF2.0-- Ajax
[
https://issues.apache.org/jira/browse/GERONIMO-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5528.
-
Resolution: Fixed
Committed to trunk at revision 987411. thank you Zhen Zhang for this
2010/8/18 Ivan xhh...@gmail.com
Agree to use some professional tools ...
I have to say sorry to ApplicationJNDI gbeans, the root cause of startup
time is due to the jaxb unmarshall of the web.xml file :-(
Due to the Servlet 3.0, we need to calculate the security constraints while
starting
Kevan raised an issue in the vote for the Common Annotations spec vote
for something he'd like to get corrected for the next release. The
issue involves a difference between the description in the source NOTICE
file and what is getting placed in the NOTICE file in the binary jar.
For
On Aug 20, 2010, at 6:07 AM, Rick McGuire wrote:
This version of the file appears to be generated automatically by the build
(not sure what plugin does this). The descriptive name Annotation 1.1 is
taken directly from the project pom. Note that all of the Geronimo specs
have this same
On Aug 20, 2010, at 6:07 AM, Rick McGuire wrote:
2) Should the source NOTICE file be kept as is or changed to match the
generated NOTICE file? Keeping these the same is definitely a manual
process, so there's a good chance there will be drift over time. I suspect
there's also a good
On 8/20/2010 9:03 AM, Kevan Miller wrote:
On Aug 20, 2010, at 6:07 AM, Rick McGuire wrote:
2) Should the source NOTICE file be kept as is or changed to match the generated NOTICE
file? Keeping these the same is definitely a manual process, so there's a good chance
there will be drift over
The vote to release geronimo-annotation_1.1_spec-1.0.1 and
geronimo-jaxb_2.2_spec-1.0.1 passes with 4 +1 votes and no 0 or -1
votes. Voting +1 were
Rick McGuire
David Blevins
Donald Woods
Kevan Miller
The new jars will be promoted to maven central today.
Rick
On 8/18/2010 7:08 AM, Rick
On 8/20/2010 8:55 AM, Kevan Miller wrote:
On Aug 20, 2010, at 6:07 AM, Rick McGuire wrote:
This version of the file appears to be generated automatically by the build (not sure
what plugin does this). The descriptive name Annotation 1.1 is taken
directly from the project pom. Note that
I'm hoping we'll have things lined up for 2.2.x release in mid-September.
branches/2.2 is currently 2.2.2-SNAPSHOT. As we were preparing for a minimal
2.2.1 release. Given where we are, I think we discard the thoughts of this
minimal update, and change branches/2.2 back to 2.2.1-SNAPSHOT. This
If we could resolve the maven issue easily, I am +1 for changing the branch
to 2.2.1-SNAPSHOT. Or I guess that we will be always asked where is 2.2.1 in
the future :-)
2010/8/20 Kevan Miller kevan.mil...@gmail.com
I'm hoping we'll have things lined up for 2.2.x release in mid-September.
On 8/20/2010 9:25 AM, Kevan Miller wrote:
I'm hoping we'll have things lined up for 2.2.x release in mid-September.
branches/2.2 is currently 2.2.2-SNAPSHOT. As we were preparing for a minimal
2.2.1 release. Given where we are, I think we discard the thoughts of this
minimal update, and
Geronimo Revision: 987495 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100820/build-0900.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100820/unit-test
Hi
I am checking at our web profile assemblies to ensure it met the
requirements for Java EE 6 web profile and prune the unnecessary
artifacts. I've been mainly look at the tomcat7-javaee6-web and I
have some comments/questions:
felix core: i assume we'll always ship 2 osgi runtime?
connector
On 8/20/2010 10:09 AM, Lin Sun wrote:
Hi
I am checking at our web profile assemblies to ensure it met the
requirements for Java EE 6 web profile and prune the unnecessary
artifacts. I've been mainly look at the tomcat7-javaee6-web and I
have some comments/questions:
felix core: i assume
For the OpenEJB, I do not see that it is possible to have only ejb lite
function
For those spec jars, if they are there, I think that they should be required
by other components. Like Jaxws, some classes are refered by OpenEJB.
BTW, we might search the dependencies.xml for the jar dependency, e.g.
On Fri, Aug 20, 2010 at 10:09 AM, Lin Sun linsun@gmail.com wrote:
Hi
I am checking at our web profile assemblies to ensure it met the
requirements for Java EE 6 web profile and prune the unnecessary
artifacts. I've been mainly look at the tomcat7-javaee6-web and I
have some
Hi,
Thanks Rick/Ivan/Jarek much for the comments so far. I agree with
most of the comments. I think these are what we agreed on -
1. keep extra spec jars instead of spending time to sort them out.
2. mina, yoko are needed.
3. pluto/portal are needed.
4. openejb: going to be hard to break down
Ok, regarding tranql RAs, the derby ones are pulled in by
system-database. The other RAs are pulled in as part of the
db-connectors plugin which is part of the eba-tomcat plugin group.
I think we are fine to keep these RAs in, if we want to support these
different dbs like db2, oracle, sql
Geronimo Revision: 987603 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100820/build-1500.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100820/unit-test
It seems hard to remove javamail given openejb depends on it. At
least for the javamail schema for JNDI, which is used by the
openejb-client.
Also, I don't quite understand this comment in G roomt pom.xml -
!-- Use org.apache.geronimo.javamail/geronimo-javamail_1.4_mail
Geronimo Revision: 987681 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100820/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100820
[INFO] BUILD
28 matches
Mail list logo
