Menu
▾
▴
springframework-developer — Spring Framework developers list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(55) |
Mar
(100) |
Apr
(203) |
May
(330) |
Jun
(190) |
Jul
(302) |
Aug
(323) |
Sep
(197) |
Oct
(245) |
Nov
(490) |
Dec
(330) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(194) |
Feb
(400) |
Mar
(416) |
Apr
(415) |
May
(359) |
Jun
(381) |
Jul
(491) |
Aug
(311) |
Sep
(291) |
Oct
(273) |
Nov
(355) |
Dec
(266) |
| 2005 |
Jan
(306) |
Feb
(303) |
Mar
(520) |
Apr
(346) |
May
(255) |
Jun
(221) |
Jul
(171) |
Aug
(247) |
Sep
(147) |
Oct
(125) |
Nov
(165) |
Dec
(65) |
| 2006 |
Jan
(90) |
Feb
(53) |
Mar
(121) |
Apr
(103) |
May
(113) |
Jun
(103) |
Jul
(104) |
Aug
(67) |
Sep
(78) |
Oct
(82) |
Nov
(78) |
Dec
(70) |
| 2007 |
Jan
(77) |
Feb
(76) |
Mar
(63) |
Apr
(30) |
May
(47) |
Jun
(41) |
Jul
(44) |
Aug
(44) |
Sep
(49) |
Oct
(33) |
Nov
(25) |
Dec
(21) |
| 2008 |
Jan
(45) |
Feb
(13) |
Mar
(15) |
Apr
(12) |
May
(9) |
Jun
(33) |
Jul
(30) |
Aug
(7) |
Sep
(20) |
Oct
(17) |
Nov
(20) |
Dec
(10) |
| 2009 |
Jan
(8) |
Feb
(5) |
Mar
(12) |
Apr
(17) |
May
(19) |
Jun
(97) |
Jul
(77) |
Aug
(33) |
Sep
(24) |
Oct
(41) |
Nov
(16) |
Dec
(32) |
| 2010 |
Jan
(24) |
Feb
(14) |
Mar
(50) |
Apr
(71) |
May
(70) |
Jun
(64) |
Jul
(45) |
Aug
(62) |
Sep
(32) |
Oct
(4) |
Nov
(12) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(10) |
May
(2) |
Jun
(3) |
Jul
(11) |
Aug
(10) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(1) |
Mar
(9) |
Apr
(1) |
May
(8) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(10) |
Dec
(8) |
| 2014 |
Jan
(3) |
Feb
(12) |
Mar
(9) |
Apr
(12) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2016 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
(5) |
Aug
(4) |
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(7) |
Feb
(8) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Darren D. <da...@sh...> - 2006-01-05 02:42:43
|
1136428675
FAILED
[junit] Testcase: testNaming took 0,005 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,013 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,013 sec
[junit] Testcase: testNaming took 0,003 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,011 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,011 sec
[junit] Testcase: testNaming took 0,001 sec
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,14 sec
[junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,14 sec
[junit] Testcase: testStartupWithLocatedServer took 0,07 sec
[junit] Testcase: testStartupWithSuppliedServer took 0,029 sec
[junit] Testcase: testRegisterWithMBeanServer took 0,017 sec
[junit] Caused an ERROR
[junit] Address already in use
[junit] java.net.BindException: Address already in use
[junit] at java.net.PlainSocketImpl.socketBind(Native Method)
[junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
[junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
[junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
[junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78)
Last CVS updates prior to this build were:
1136427181
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: <al...@in...> - 2006-01-03 23:35:06
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060104001723Lbuild.390 |
|
From: Darren D. <da...@sh...> - 2006-01-03 18:42:28
|
1136313470
FAILED
[junit] Testcase: testNaming took 0,005 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,02 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,02 sec
[junit] Testcase: testNaming took 0,003 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,011 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,011 sec
[junit] Testcase: testNaming took 0,001 sec
[junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,086 sec
[junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,086 sec
[junit] Testcase: testStartupWithLocatedServer took 0,054 sec
[junit] Testcase: testStartupWithSuppliedServer took 0,01 sec
[junit] Caused an ERROR
[junit] Address already in use
[junit] java.net.BindException: Address already in use
[junit] at java.net.PlainSocketImpl.socketBind(Native Method)
[junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
[junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
[junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
[junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:65)
Last CVS updates prior to this build were:
1136311981
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
P src/org/springframework/beans/factory/support/AbstractAutowireCapableBeanFactory.java
P src/org/springframework/beans/factory/xml/XmlBeanDefinitionReader.java
U test/org/springframework/beans/factory/xml/XmlBeanDefinitionReaderTests.java
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Darren D. <da...@sh...> - 2006-01-03 14:56:07
|
1136252773
FAILED
[junit] Testcase: testAutowireWithDefault took 0.058 sec
[junit] Testcase: testAutowireByConstructor took 0.359 sec
[junit] Testcase: testAutowireByConstructorWithSimpleValues took 0.062 sec
[junit] Testcase: testConstructorArgResolution took 0.477 sec
[junit] Testcase: testConstructorArgWithSingleMatch took 0.363 sec
[junit] Testcase: testThrowsExceptionOnTooManyArguments took 0.059 sec
[junit] Testcase: testThrowsExceptionOnAmbiguousResolution took 0.245 sec
[junit] Testcase: testFactoryBeanDefinedAsPrototype took 0.213 sec
[junit] Testcase: testDependsOn took 0.668 sec
[junit] Testcase: testDependsOnInInnerBean took 0.222 sec
[junit] Testcase: testDependenciesThroughConstructorArguments took 0.19 sec
[junit] Testcase: testDependenciesThroughConstructorArgumentAutowiring took 0.04 sec
[junit] Testcase: testDependenciesThroughConstructorArgumentsInInnerBean took 0.315 sec
[junit] Testcase: testDependenciesThroughProperties took 0.052 sec
[junit] Testcase: testDependenciesThroughPropertiesWithInTheMiddle took 0.081 sec
[junit] Testcase: testDependenciesThroughPropertyAutowiringByName took 0.191 sec
[junit] Testcase: testDependenciesThroughPropertyAutowiringByType took 0.182 sec
[junit] Testcase: testDependenciesThroughPropertiesInInnerBean took 0.046 sec
[junit] Testcase: testClassNotFoundWithDefault took 0.242 sec
[junit] Testcase: testClassNotFoundWithNoBeanClassLoader took 0.042 sec
[junit] Testcase: testResourceAndInputStream took 0.949 sec
[junit] Testcase: testClassPathResourceWithImport took 0.347 sec
[junit] Testcase: testUrlResourceWithImport took 0.103 sec
[junit] Testcase: testFileSystemResourceWithImport took 0.236 sec
[junit] Testcase: testLookupOverrideMethodsWithSetterInjection took 2.169 sec
[junit] FAILED
[junit] null
[junit] junit.framework.AssertionFailedError
[junit] at org.springframework.beans.factory.xml.XmlBeanFactoryTests.testLookupOverrideMethodsWithSetterInjection(XmlBeanFactoryTests.java:908)
Last CVS updates prior to this build were:
1136250781
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: <al...@in...> - 2006-01-01 23:33:31
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060102001651Lbuild.389 |
|
From: <al...@in...> - 2005-12-30 23:32:23
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051231001631Lbuild.388 |
|
From: Darren D. <da...@sh...> - 2005-12-30 02:42:41
|
1135910266
FAILED
[junit] Testcase: testNaming took 0,011 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,013 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,013 sec
[junit] Testcase: testNaming took 0,003 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,017 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,017 sec
[junit] Testcase: testNaming took 0 sec
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,119 sec
[junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,119 sec
[junit] Testcase: testStartupWithLocatedServer took 0,054 sec
[junit] Testcase: testStartupWithSuppliedServer took 0,029 sec
[junit] Testcase: testRegisterWithMBeanServer took 0,018 sec
[junit] Caused an ERROR
[junit] Address already in use
[junit] java.net.BindException: Address already in use
[junit] at java.net.PlainSocketImpl.socketBind(Native Method)
[junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
[junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
[junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
[junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78)
Last CVS updates prior to this build were:
1135908781
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: <al...@in...> - 2005-12-29 23:20:23
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051230001612 |
|
From: <al...@in...> - 2005-12-27 23:32:46
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051228001657Lbuild.387 |
|
From: Darren D. <da...@sh...> - 2005-12-26 02:41:49
|
1135564689
FAILED
[junit] Testcase: testNaming took 0,14 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,025 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,025 sec
[junit] Testcase: testNaming took 0,003 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,012 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,012 sec
[junit] Testcase: testNaming took 0,001 sec
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,133 sec
[junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,133 sec
[junit] Testcase: testStartupWithLocatedServer took 0,055 sec
[junit] Testcase: testStartupWithSuppliedServer took 0,026 sec
[junit] Testcase: testRegisterWithMBeanServer took 0,012 sec
[junit] Caused an ERROR
[junit] Address already in use
[junit] java.net.BindException: Address already in use
[junit] at java.net.PlainSocketImpl.socketBind(Native Method)
[junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
[junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
[junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
[junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78)
Last CVS updates prior to this build were:
1135563181
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Ramin F. <aqu...@ya...> - 2005-12-25 04:49:54
|
Dear Spring Team, Merry Christmas. I wish you the best of luck in the forthcoming year. I love J2EE in the Spring team. You guys did a great job...... Regards, Ramin Farhanian spr...@li... wrote: Send Springframework-developer mailing list submissions to spr...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/springframework-developer or, via email, send a message with subject or body 'help' to spr...@li... You can reach the person managing the list at spr...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Springframework-developer digest..." Today's Topics: 1. RE: Re: [Springframework-user] Spring Framework 2.0 M1 released (Herryanto Siatono) 2. FAILED BUILD: x86-solaris1 (last 30 lines included) (Darren Davison) 3. spring Build Failed (al...@in...) 4. Re: Spring Framework 2.0 M1 released (John Lewis) 5. FAILED BUILD: x86-linux2 (last 30 lines included) (Darren Davison) --__--__-- Message: 1 From: "Herryanto Siatono" To: , Subject: RE: [Springframework-developer] Re: [Springframework-user] Spring Framework 2.0 M1 released Date: Fri, 23 Dec 2005 14:44:54 +0800 Reply-To: spr...@li... Yeah indeed it rocks!!=20 Life would have been much tougher as a programmer without Spring.=20 Merry Christmas to all, and looking forward for brighter days next year = with Spring 2.0. :) -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf = Of Dmitriy Kopylenko Sent: 22 December 2005 23:54 To: spr...@li...; spr...@li... Subject: [Springframework-developer] Re: [Springframework-user] Spring Framework 2.0 M1 released Spring 2 rocks! I also would like to wish to the Spring community a Merry Christmas and=20 a very happy and productive 2006 year! Dmitriy. Juergen Hoeller wrote: >Dear Spring community, > >I am pleased to announce that Spring 2.0 M1 has just been released. 2.0 = M1 >is the first milestone of the next generation of Spring: introducing = XML >schema based bean definitions, sophisticated AspectJ support, task = executor >abstraction, asynchronous JMS facilities, portlet support, etc. > >The main sample application in this release is JPetStore, which already >illustrates some basic usage of schema-based bean definitions and = aspects >expressed using AspectJ pointcut language. 2.0 M2 will include further >sample usages and improved documentation of the new configuration = style. > >Spring 2.0 remains fully backwards-compatible with Spring 1.2. Both the = DTD >style and the schema style are supported for XML bean definitions. No >incompatible API changes have been introduced (other than removing >deprecated methods). Furthermore, Spring 2.0 still runs on JDK 1.3+ and J2EE >1.2+. > >Note that Spring has been repackaged: spring.jar contains the entire = core >plus some small extensions; larger extensions such as support for = specific >ORMs have been factored out into separate jar files = (spring-hibernate2.jar, >spring-hibernate3.jar, spring-toplink.jar, etc). See the readme for details. > >Cheers - and Merry Christmas to everybody celebrating Christmas :-) > >Juergen >=20 >----- >Juergen Hoeller >Interface21 Ltd >http://www.springframework.com > > > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >_______________________________________________ >Springframework-user mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-user > =20 > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer --__--__-- Message: 2 Date: Fri, 23 Dec 2005 09:36:16 -0800 From: Darren Davison To: spr...@li... Subject: [Springframework-developer] FAILED BUILD: x86-solaris1 (last 30 lines included) Reply-To: spr...@li... 1135359375 FAILED tests: [mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/x86-solaris1/test-reports [junit] java.io.IOException: Not enough space [junit] at java.lang.UNIXProcess.forkAndExec(Native Method) [junit] at java.lang.UNIXProcess.(UNIXProcess.java:56) [junit] at java.lang.Runtime.execInternal(Native Method) [junit] at java.lang.Runtime.exec(Runtime.java:566) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:324) [junit] at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.java:831) [junit] at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:436) [junit] at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:450) [junit] at org.apache.tools.ant.taskdefs.Execute.getProcEnvironment(Execute.java:166) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeAsForked(JUnitTask.java:782) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:724) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:650) [junit] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) [junit] at org.apache.tools.ant.Task.perform(Task.java:364) [junit] at org.apache.tools.ant.Target.execute(Target.java:341) [junit] at org.apache.tools.ant.Target.performTasks(Target.java:369) [junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1214) [junit] at org.apache.tools.ant.Project.executeTargets(Project.java:1062) [junit] at org.apache.tools.ant.Main.runBuild(Main.java:673) [junit] at org.apache.tools.ant.Main.startAnt(Main.java:188) [junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196) [junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:55) [junit] Running org.springframework.web.util.UrlPathHelperTests Last CVS updates prior to this build were: 1135357981 This is an automated mail from one of the SF Compile Farm machines. The machine name noted in the subject encountered a failure building or running the Spring test suite. The last few lines of the output were included for info. NB: No further mail will be sent from this machine until a successful build occurs on the machine in question. See http://springframework.sourceforge.net/test/ for further information. --__--__-- Message: 3 Date: Sat, 24 Dec 2005 00:19:25 +0100 (CET) From: al...@in... To: spr...@li... Subject: [Springframework-developer] spring Build Failed Reply-To: spr...@li... View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051224001636 --__--__-- Message: 4 To: spr...@li... From: John Lewis Date: Fri, 23 Dec 2005 16:35:12 -0700 Subject: [Springframework-developer] Re: Spring Framework 2.0 M1 released Reply-To: spr...@li... Great job gang! Thanks for all your support in getting Portlet MVC integrated -- especially from Juergen. Is it possible to get the docs from the 2.0 M1 build posted on static.springframework.org? I'm mostly interested in seeing the new Javadocs there. John Lewis Juergen Hoeller wrote: > Dear Spring community, > > I am pleased to announce that Spring 2.0 M1 has just been released. 2.0 M1 > is the first milestone of the next generation of Spring: introducing XML > schema based bean definitions, sophisticated AspectJ support, task executor > abstraction, asynchronous JMS facilities, portlet support, etc. > > The main sample application in this release is JPetStore, which already > illustrates some basic usage of schema-based bean definitions and aspects > expressed using AspectJ pointcut language. 2.0 M2 will include further > sample usages and improved documentation of the new configuration style. > > Spring 2.0 remains fully backwards-compatible with Spring 1.2. Both the DTD > style and the schema style are supported for XML bean definitions. No > incompatible API changes have been introduced (other than removing > deprecated methods). Furthermore, Spring 2.0 still runs on JDK 1.3+ and J2EE > 1.2+. > > Note that Spring has been repackaged: spring.jar contains the entire core > plus some small extensions; larger extensions such as support for specific > ORMs have been factored out into separate jar files (spring-hibernate2.jar, > spring-hibernate3.jar, spring-toplink.jar, etc). See the readme for details. > > Cheers - and Merry Christmas to everybody celebrating Christmas :-) > > Juergen > > ----- > Juergen Hoeller > Interface21 Ltd > http://www.springframework.com > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click --__--__-- Message: 5 Date: Fri, 23 Dec 2005 18:37:48 -0800 From: Darren Davison To: spr...@li... Subject: [Springframework-developer] FAILED BUILD: x86-linux2 (last 30 lines included) Reply-To: spr...@li... 1135391868 FAILED [junit] Testcase: testNaming took 0,005 sec [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,013 sec [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,013 sec [junit] Testcase: testNaming took 0,003 sec [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,011 sec [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,011 sec [junit] Testcase: testNaming took 0 sec [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,112 sec [junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,112 sec [junit] Testcase: testStartupWithLocatedServer took 0,059 sec [junit] Testcase: testStartupWithSuppliedServer took 0,021 sec [junit] Testcase: testRegisterWithMBeanServer took 0,012 sec [junit] Caused an ERROR [junit] Address already in use [junit] java.net.BindException: Address already in use [junit] at java.net.PlainSocketImpl.socketBind(Native Method) [junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331) [junit] at java.net.ServerSocket.bind(ServerSocket.java:318) [junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128) [junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39) [junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235) [junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167) [junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78) Last CVS updates prior to this build were: 1135390381 ? ? ? junit423465713.properties ? junittestcases2136842450.properties ? sandbox/src/org/springframework/core/closure/ElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java ? sandbox/src/org/springframework/core/closure/support/IfBlock.java ? sandbox/src/org/springframework/jms/listener ? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml This is an automated mail from one of the SF Compile Farm machines. The machine name noted in the subject encountered a failure building or running the Spring test suite. The last few lines of the output were included for info. NB: No further mail will be sent from this machine until a successful build occurs on the machine in question. See http://springframework.sourceforge.net/test/ for further information. --__--__-- _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer End of Springframework-developer Digest |
|
From: Darren D. <da...@sh...> - 2005-12-25 02:41:56
|
1135478298
FAILED
[junit] Testcase: testNaming took 0,005 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,022 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,022 sec
[junit] Testcase: testNaming took 0,005 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,014 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,014 sec
[junit] Testcase: testNaming took 0 sec
[junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,084 sec
[junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,084 sec
[junit] Testcase: testStartupWithLocatedServer took 0,051 sec
[junit] Testcase: testStartupWithSuppliedServer took 0,01 sec
[junit] Caused an ERROR
[junit] Address already in use
[junit] java.net.BindException: Address already in use
[junit] at java.net.PlainSocketImpl.socketBind(Native Method)
[junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
[junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
[junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
[junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:65)
Last CVS updates prior to this build were:
1135476781
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: <al...@in...> - 2005-12-24 23:31:52
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051225001637Lbuild.386 |
|
From: Nicolas B. <nb...@pi...> - 2005-12-24 05:08:11
|
I will be out of the office starting 24.12.2005 and will not return until 03.01.2006. I will respond to your message when I return. My teammate Laurent Rolaz (lr...@pi...) can be contacted for WebLogic matters. My teammate Jean Kunz (jk...@pi...) can be contacted for urgent matters. ________________________________________________________________ Pictet & Cie, Banquiers Tel. +41 (0)58 323 2323 29, boulevard Georges-Favon Fax +41 (0)58 323 2324 CH-1204 GENEVE http://www.pictet.com/ ________________________________________________________________ This document should only be read by those persons to whom it is addressed and is not intended to be relied upon by any person without subsequent written confirmation of its contents. If you have received this e-mail message in error, please destroy it and delete it from your computer. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this E-mail message is strictly prohibited. ________________________________________________________________ |
|
From: Darren D. <da...@sh...> - 2005-12-24 02:41:17
|
1135391868
FAILED
[junit] Testcase: testNaming took 0,005 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,013 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,013 sec
[junit] Testcase: testNaming took 0,003 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,011 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,011 sec
[junit] Testcase: testNaming took 0 sec
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,112 sec
[junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,112 sec
[junit] Testcase: testStartupWithLocatedServer took 0,059 sec
[junit] Testcase: testStartupWithSuppliedServer took 0,021 sec
[junit] Testcase: testRegisterWithMBeanServer took 0,012 sec
[junit] Caused an ERROR
[junit] Address already in use
[junit] java.net.BindException: Address already in use
[junit] at java.net.PlainSocketImpl.socketBind(Native Method)
[junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
[junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
[junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
[junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78)
Last CVS updates prior to this build were:
1135390381
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: John L. <jl...@ar...> - 2005-12-23 23:35:42
|
Great job gang! Thanks for all your support in getting Portlet MVC integrated -- especially from Juergen. Is it possible to get the docs from the 2.0 M1 build posted on static.springframework.org? I'm mostly interested in seeing the new Javadocs there. John Lewis Juergen Hoeller wrote: > Dear Spring community, > > I am pleased to announce that Spring 2.0 M1 has just been released. 2.0 M1 > is the first milestone of the next generation of Spring: introducing XML > schema based bean definitions, sophisticated AspectJ support, task executor > abstraction, asynchronous JMS facilities, portlet support, etc. > > The main sample application in this release is JPetStore, which already > illustrates some basic usage of schema-based bean definitions and aspects > expressed using AspectJ pointcut language. 2.0 M2 will include further > sample usages and improved documentation of the new configuration style. > > Spring 2.0 remains fully backwards-compatible with Spring 1.2. Both the DTD > style and the schema style are supported for XML bean definitions. No > incompatible API changes have been introduced (other than removing > deprecated methods). Furthermore, Spring 2.0 still runs on JDK 1.3+ and J2EE > 1.2+. > > Note that Spring has been repackaged: spring.jar contains the entire core > plus some small extensions; larger extensions such as support for specific > ORMs have been factored out into separate jar files (spring-hibernate2.jar, > spring-hibernate3.jar, spring-toplink.jar, etc). See the readme for details. > > Cheers - and Merry Christmas to everybody celebrating Christmas :-) > > Juergen > > ----- > Juergen Hoeller > Interface21 Ltd > http://www.springframework.com > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click |
|
From: <al...@in...> - 2005-12-23 23:19:31
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051224001636 |
|
From: Darren D. <da...@sh...> - 2005-12-23 17:39:43
|
1135359375
FAILED
tests:
[mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/x86-solaris1/test-reports
[junit] java.io.IOException: Not enough space
[junit] at java.lang.UNIXProcess.forkAndExec(Native Method)
[junit] at java.lang.UNIXProcess.<init>(UNIXProcess.java:56)
[junit] at java.lang.Runtime.execInternal(Native Method)
[junit] at java.lang.Runtime.exec(Runtime.java:566)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:324)
[junit] at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.java:831)
[junit] at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:436)
[junit] at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:450)
[junit] at org.apache.tools.ant.taskdefs.Execute.getProcEnvironment(Execute.java:166)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeAsForked(JUnitTask.java:782)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:724)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:650)
[junit] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[junit] at org.apache.tools.ant.Task.perform(Task.java:364)
[junit] at org.apache.tools.ant.Target.execute(Target.java:341)
[junit] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[junit] at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
[junit] at org.apache.tools.ant.Main.runBuild(Main.java:673)
[junit] at org.apache.tools.ant.Main.startAnt(Main.java:188)
[junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
[junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:55)
[junit] Running org.springframework.web.util.UrlPathHelperTests
Last CVS updates prior to this build were:
1135357981
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Herryanto S. <her...@gm...> - 2005-12-23 06:45:01
|
Yeah indeed it rocks!!=20 Life would have been much tougher as a programmer without Spring.=20 Merry Christmas to all, and looking forward for brighter days next year = with Spring 2.0. :) -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf = Of Dmitriy Kopylenko Sent: 22 December 2005 23:54 To: spr...@li...; spr...@li... Subject: [Springframework-developer] Re: [Springframework-user] Spring Framework 2.0 M1 released Spring 2 rocks! I also would like to wish to the Spring community a Merry Christmas and=20 a very happy and productive 2006 year! Dmitriy. Juergen Hoeller wrote: >Dear Spring community, > >I am pleased to announce that Spring 2.0 M1 has just been released. 2.0 = M1 >is the first milestone of the next generation of Spring: introducing = XML >schema based bean definitions, sophisticated AspectJ support, task = executor >abstraction, asynchronous JMS facilities, portlet support, etc. > >The main sample application in this release is JPetStore, which already >illustrates some basic usage of schema-based bean definitions and = aspects >expressed using AspectJ pointcut language. 2.0 M2 will include further >sample usages and improved documentation of the new configuration = style. > >Spring 2.0 remains fully backwards-compatible with Spring 1.2. Both the = DTD >style and the schema style are supported for XML bean definitions. No >incompatible API changes have been introduced (other than removing >deprecated methods). Furthermore, Spring 2.0 still runs on JDK 1.3+ and J2EE >1.2+. > >Note that Spring has been repackaged: spring.jar contains the entire = core >plus some small extensions; larger extensions such as support for = specific >ORMs have been factored out into separate jar files = (spring-hibernate2.jar, >spring-hibernate3.jar, spring-toplink.jar, etc). See the readme for details. > >Cheers - and Merry Christmas to everybody celebrating Christmas :-) > >Juergen >=20 >----- >Juergen Hoeller >Interface21 Ltd >http://www.springframework.com > > > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >_______________________________________________ >Springframework-user mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-user > =20 > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <al...@in...> - 2005-12-22 23:20:30
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051223001626 |
|
From: Dmitriy K. <dko...@ru...> - 2005-12-22 15:53:55
|
Spring 2 rocks! I also would like to wish to the Spring community a Merry Christmas and a very happy and productive 2006 year! Dmitriy. Juergen Hoeller wrote: >Dear Spring community, > >I am pleased to announce that Spring 2.0 M1 has just been released. 2.0 M1 >is the first milestone of the next generation of Spring: introducing XML >schema based bean definitions, sophisticated AspectJ support, task executor >abstraction, asynchronous JMS facilities, portlet support, etc. > >The main sample application in this release is JPetStore, which already >illustrates some basic usage of schema-based bean definitions and aspects >expressed using AspectJ pointcut language. 2.0 M2 will include further >sample usages and improved documentation of the new configuration style. > >Spring 2.0 remains fully backwards-compatible with Spring 1.2. Both the DTD >style and the schema style are supported for XML bean definitions. No >incompatible API changes have been introduced (other than removing >deprecated methods). Furthermore, Spring 2.0 still runs on JDK 1.3+ and J2EE >1.2+. > >Note that Spring has been repackaged: spring.jar contains the entire core >plus some small extensions; larger extensions such as support for specific >ORMs have been factored out into separate jar files (spring-hibernate2.jar, >spring-hibernate3.jar, spring-toplink.jar, etc). See the readme for details. > >Cheers - and Merry Christmas to everybody celebrating Christmas :-) > >Juergen > >----- >Juergen Hoeller >Interface21 Ltd >http://www.springframework.com > > > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >_______________________________________________ >Springframework-user mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-user > > |
|
From: Juergen H. <ju...@in...> - 2005-12-22 15:48:25
|
Dear Spring community, I am pleased to announce that Spring 2.0 M1 has just been released. 2.0 M1 is the first milestone of the next generation of Spring: introducing XML schema based bean definitions, sophisticated AspectJ support, task executor abstraction, asynchronous JMS facilities, portlet support, etc. The main sample application in this release is JPetStore, which already illustrates some basic usage of schema-based bean definitions and aspects expressed using AspectJ pointcut language. 2.0 M2 will include further sample usages and improved documentation of the new configuration style. Spring 2.0 remains fully backwards-compatible with Spring 1.2. Both the DTD style and the schema style are supported for XML bean definitions. No incompatible API changes have been introduced (other than removing deprecated methods). Furthermore, Spring 2.0 still runs on JDK 1.3+ and J2EE 1.2+. Note that Spring has been repackaged: spring.jar contains the entire core plus some small extensions; larger extensions such as support for specific ORMs have been factored out into separate jar files (spring-hibernate2.jar, spring-hibernate3.jar, spring-toplink.jar, etc). See the readme for details. Cheers - and Merry Christmas to everybody celebrating Christmas :-) Juergen ----- Juergen Hoeller Interface21 Ltd http://www.springframework.com |
|
From: <al...@in...> - 2005-12-21 23:20:18
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051222001618 |
|
From: <al...@in...> - 2005-12-20 23:33:14
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051221001655Lbuild.385 |
|
From: Lachezar D. <l.d...@gm...> - 2005-12-20 13:29:58
|
Ummm... Well... That's not a dependancy, rather an 'optional extension'. It is by no means mandatory... And I have not seen any constraints as to whether the ClassPath entries must exist. I have never thought the ClassPath attribute as an expression. It's just included in the CP if it exists. There was a time when commons-logging used this approach to add log4j.jar to the CP transparent to the application. Don't know why it has been missing for some time now... Maybe the same reason that you pointed out :). Anyway. It was just a thought... 2005/12/20, Juergen Hoeller <ju...@in...>: > Well, doesn't such a manifest classpath entry express the wrong direction= of > dependency? spring.jar does not depend on spring-hibernate*.jar at all. I= t's > rather the other way round: spring-hibernate*.jar are extensions that dep= end > on spring.jar > > Juergen > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On Behalf = Of > Lachezar Dobrev > Sent: Tuesday, December 20, 2005 9:23 AM > To: spr...@li... > Subject: Re: [Springframework-developer] orm.hibernate* missing from > spring.jar in nightly builds > > Ahmm... Maybe if Spring uses the Class-Path attribute in the jars' > MANIFEST.MF this problem would be solved by merely dropping a couple of j= ars > into the library directory without mangling a project's class path. > Spring.jar should have in the manifest: > Class-Path: spring-hibernate2.jar spring-hibernate-3.jar ... > > Then the developers would only need to drop the required subset of > sub-jars. > > 2005/12/15, Colin Sampaleanu <col...@ex...>: > > mraible (sent by Nabble.com) wrote: > > > > It's not about splitting it out just to split it out. The problem is > > that having both the Hibernate 2 and Hibernate 3 code together leads > > to a lot of confusion. People end up importing the wrong classes all > > the time. The actual class names are identical, and the packages as > > identical except for one extra char, so it's easy to import the wrong > > one when you do an auto import in Eclipse. I see this over and over > > during trainings, among other places. So back in the summer I > > suggested we split things out to separate jars and have people just > > include whichever one they wanted, but it didn't make sense (for drop > > in compatibility reasons) to do this in a 1.2 point release, but > > rather only now with 2.0... > > > > Colin > > > > -- > > Colin Sampaleanu > > Interface21 Principal Consultant > > Spring Training, Consulting and Support - "From the Source" > > http://www.springframework.com > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&opclick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
1239 messages has been excluded from this view by a project administrator.
