Jenkins build is back to stable : torque4-test-project-derby » Torque Test Project #409

2015-09-06 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.o

Jenkins build is back to stable : torque4-test-project-derby #409

2015-09-06 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org

svn commit: r1701510 - /db/torque/torque4/trunk/torque-runtime/src/main/java/org/apache/torque/criteria/PreparedStatementPart.java

2015-09-06 Thread tfischer
Author: tfischer Date: Sun Sep 6 18:45:05 2015 New Revision: 1701510 URL: http://svn.apache.org/r1701510 Log: improve javadoc, add final modifier Modified: db/torque/torque4/trunk/torque-runtime/src/main/java/org/apache/torque/criteria/PreparedStatementPart.java Modified: db/torque/torque

svn commit: r1701509 - /db/torque/torque4/trunk/torque-test/pom.xml

2015-09-06 Thread tfischer
Author: tfischer Date: Sun Sep 6 18:37:17 2015 New Revision: 1701509 URL: http://svn.apache.org/r1701509 Log: try fix derby build in jenkins by correcting the url Modified: db/torque/torque4/trunk/torque-test/pom.xml Modified: db/torque/torque4/trunk/torque-test/pom.xml URL: http://svn.apa

Jenkins build is still unstable: torque4-test-project-derby » Torque Test Project #408

2015-09-06 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org

Jenkins build is still unstable: torque4-test-project-derby #408

2015-09-06 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org

[jira] [Resolved] (TORQUE-339) Correct the order of outlet and mergepoint in the last example of the configuration section of the code generation documentation

2015-09-06 Thread Thomas Fox (JIRA)
[ https://issues.apache.org/jira/browse/TORQUE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-339. --- Resolution: Fixed Assignee: (was: Thomas Fox) Fix Version/s: 4.1 > Correct the ord

[jira] [Assigned] (TORQUE-339) Correct the order of outlet and mergepoint in the last example of the configuration section of the code generation documentation

2015-09-06 Thread Thomas Fox (JIRA)
[ https://issues.apache.org/jira/browse/TORQUE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-339: - Assignee: Thomas Fox > Correct the order of outlet and mergepoint in the last example of the > c

svn commit: r1701508 - /db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml

2015-09-06 Thread tfischer
Author: tfischer Date: Sun Sep 6 18:17:31 2015 New Revision: 1701508 URL: http://svn.apache.org/r1701508 Log: TORQUE-339 Correct the order of outlet and mergepoint in the last example of the configuration section of the code generation documentation. Thanks to Helge Weissig for the patch Modifi

svn commit: r1701507 - /db/torque/torque4/trunk/torque-test/pom.xml

2015-09-06 Thread tfischer
Author: tfischer Date: Sun Sep 6 18:11:13 2015 New Revision: 1701507 URL: http://svn.apache.org/r1701507 Log: try fix derby build in jenkins by adding a profile which is running from project root Modified: db/torque/torque4/trunk/torque-test/pom.xml Modified: db/torque/torque4/trunk/torque

Re: Change JDK requirements for Torque 4.1

2015-09-06 Thread Thomas Vandahl
On 05.09.15 03:41, Thomas Fox wrote: > Hi, > > for fixing https://issues.apache.org/jira/browse/TORQUE-226, a version of > jgit must be included which requires JDK 1.7 for the generator. > I suggest to raise the required JDK version for the Torque 4.1 generator to > JDK 1.7 > > Also, it has bec

Re: Upgrade to JCS-20-beta1

2015-09-06 Thread Thomas Vandahl
On 05.09.15 07:51, Thomas Fox wrote: > We have an open ticket > https://issues.apache.org/jira/browse/TORQUE-327 > which suggests to upgrade to JCS 2.0. Now JCS-2.0-beta1 is available. Does > anyone have an idea how stable this version ist and whether we should try to > use it ? I guess it is we