Re: [VOTE] Release Apache Empire-db 2.0.6-incubating (rc4)
Thanks for correcting me, Craig and Francis. I should have asked first before issuing the -1. This changes my vote to +1. Thomas Optional dependencies can have any license. In some cases, even required dependencies can have incompatible licenses. The hard rule is that Apache projects must not ship code with incompatible licenses. So I'm +1 for release of these artifacts. Good job. Craig On May 8, 2010, at 11:59 PM, Francis De Brabandere wrote: First of all thanks for the thorough review. These are all optional dependencies and we don't package them. All our code is written against the JDBC api, we don't need any driver implementation for compilation. So I don't see the problem. It seems we forgot to comment the mysql dependency in the codegen which is the only place and it will cause the mysql driver to be downloaded to your local maven repository when using it... is this blocking for the release? (just fixed this in trunk) Cheers, Francis On Sun, May 9, 2010 at 5:05 AM, Thomas Fischer fisc...@seitenbau.net wrote: rat report looks good signatures are ok maven jars are the same as in other distribution - good work ! source builds However, I found various dependencies which are not compatible with the ASF license. These dependencies are NOT included in any distribution file. However, as I read [1] (which licenses are acceptable for use with an Apache product), dependencies must also comply with the 3rd party license policy. Please correct me if I'm wrong. mysql-connector-java is released under GPL, according to [2] . GPL dependencies are not ok according to [3] Not sure about hsqldb. It is not explicitly listed on [4], but as it is a MIT style license, I presume it's ok, but IANAL. The h2database is dual-licensed under a modified mpl and epl. Both need to be appropriately labeled, see [5]. I do not see such prominent labelling in the distribution. The postgresql license is also not listed in [4]. I presume it's ok, but IANAL. So I'm afraid this is a -1. Thomas P.S. Sorry for waiting so long with the review, but I have been very busy personally and now finally managed to find a time slice for this. [1] http://www.apache.org/legal/3party.html [2] http://dev.mysql.com/downloads/connector/j/ [3] http://www.apache.org/legal/resolved.html#category-x [4] http://www.apache.org/legal/resolved.html#category-a [5] http://www.apache.org/legal/resolved.html#category-b Francis De Brabandere wrote: re: [VOTE] Release Apache Empire-db 2.0.6-incubating (rc4) Hi, We have just prepared the fourth 2.0.6-incubating release candidate and we are now looking for approval of the IPMC to publish the release. PMC vote thread: http://mail-archives.apache.org/mod_mbox/incubator-empire-db- dev/201004.mbox/browser We already have one binding vote. These are the major change from our previous 2.0.5-incubating release: - Code-Generator allows generation of Data Model code files for existing databases - Maven plugin for DB-Code-Generator - New example to demonstrate interoperability between Empire-db and Spring - Provided jars are now OSGi compatible Changelog: http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-db- 2.0.6-incubating-rc4/CHANGELOG.txt?view=co Subversion tag: https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache- empire-db-2.0.6-incubating-rc4 Maven staging repository: https://repository.apache.org/content/repositories/orgapacheempire-db- 020/ Distribution files are located here http://people.apache.org/~francisdb/empire-db/ Rat report for the tag is available here: http://people.apache.org/~francisdb/empire-db/rat.txt Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.somatik.be Microsoft gives you windows, Linux gives you the whole house. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Assistant Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Empire-db 2.0.6-incubating (rc4)
rat report looks good signatures are ok maven jars are the same as in other distribution - good work ! source builds However, I found various dependencies which are not compatible with the ASF license. These dependencies are NOT included in any distribution file. However, as I read [1] (which licenses are acceptable for use with an Apache product), dependencies must also comply with the 3rd party license policy. Please correct me if I'm wrong. mysql-connector-java is released under GPL, according to [2] . GPL dependencies are not ok according to [3] Not sure about hsqldb. It is not explicitly listed on [4], but as it is a MIT style license, I presume it's ok, but IANAL. The h2database is dual-licensed under a modified mpl and epl. Both need to be appropriately labeled, see [5]. I do not see such prominent labelling in the distribution. The postgresql license is also not listed in [4]. I presume it's ok, but IANAL. So I'm afraid this is a -1. Thomas P.S. Sorry for waiting so long with the review, but I have been very busy personally and now finally managed to find a time slice for this. [1] http://www.apache.org/legal/3party.html [2] http://dev.mysql.com/downloads/connector/j/ [3] http://www.apache.org/legal/resolved.html#category-x [4] http://www.apache.org/legal/resolved.html#category-a [5] http://www.apache.org/legal/resolved.html#category-b Francis De Brabandere wrote: re: [VOTE] Release Apache Empire-db 2.0.6-incubating (rc4) Hi, We have just prepared the fourth 2.0.6-incubating release candidate and we are now looking for approval of the IPMC to publish the release. PMC vote thread: http://mail-archives.apache.org/mod_mbox/incubator-empire-db- dev/201004.mbox/browser We already have one binding vote. These are the major change from our previous 2.0.5-incubating release: - Code-Generator allows generation of Data Model code files for existing databases - Maven plugin for DB-Code-Generator - New example to demonstrate interoperability between Empire-db and Spring - Provided jars are now OSGi compatible Changelog: http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-db- 2.0.6-incubating-rc4/CHANGELOG.txt?view=co Subversion tag: https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache- empire-db-2.0.6-incubating-rc4 Maven staging repository: https://repository.apache.org/content/repositories/orgapacheempire-db- 020/ Distribution files are located here http://people.apache.org/~francisdb/empire-db/ Rat report for the tag is available here: http://people.apache.org/~francisdb/empire-db/rat.txt Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [IP Clearance] Db Torque Generator
The vote passed by lazy consesus. No votes were cast. Thomas I have written a replacement for some DB Torque modules that I would like to donate to the ASF. The code base can be found at http://people.apache.org/~tfischer/torque-generator-4-0-proposal.zip The IP clearance form is available at http://incubator.apache.org/ip-clearance/db-torque-generator.html. If anybody thinks it is inappropriate that the person who wrote the code also does the IP clearance, please vote -1 and I'll find someone else. The vote closes at Wednesday 10th Feb 18:00 MEZ Thomas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP Clearance] Db Torque Generator
I have written a replacement for some DB Torque modules that I would like to donate to the ASF. The code base can be found at http://people.apache.org/~tfischer/torque-generator-4-0-proposal.zip The IP clearance form is available at http://incubator.apache.org/ip-clearance/db-torque-generator.html. If anybody thinks it is inappropriate that the person who wrote the code also does the IP clearance, please vote -1 and I'll find someone else. The vote closes at Wednesday 10th Feb 18:00 MEZ Thomas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
incubator group membership for tfischer
Can someone please add me (tfischer) to the incubator group so I can update the incubator's webste from svn ? I am member of the incubator PMC. Thanks in advance, Thomas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: incubator group membership for tfischer
Can someone please add me (tfischer) to the incubator group so I can update the incubator's webste from svn ? I am member of the incubator PMC. You are already in the incubator group, I'm not sure what goes wrong. Hm, not on minotaur: [tfisc...@minotaur:~]$ groups tfischer tfischer apcvs member apsite db Thomas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release Apache Empire-db 2.0.5-incubating (rc6)
+1 (binding) Thomas [VOTE] Release Apache Empire-db 2.0.5-incubating (rc6) Here we go again :-) Hi, We just created an other release candidate for 2.0.5-incubating (rc6). Our community approved the release so we now have a second binding voting round for IPMC Members/Mentors. fixes since previous rc5: - examples not uploaded to the maven repository any more - tutorial fixed - KEYS file updated I tried having identical archives in the dist and the maven repo but failed to do so (meta inf build dates diff). But we might be able to fix this in a next release. Further this was not a blocking issue. Change log: http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire- db-2.0.5-incubating-rc6/CHANGELOG.txt?view=markup Subversion tag: https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache- empire-db-2.0.5-incubating-rc6 Maven staging repository: https://repository.apache.org/content/repositories/empire-db-staging-015 Distribution files are located here http://people.apache.org/~francisdb/empire-db/rc6/ Rat report for the tag is available here: http://people.apache.org/~francisdb/empire-db/rc6/rat.txt Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- http://www.somatik.be Microsoft gives you windows, Linux gives you the whole house. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release Apache Empire-db 2.0.5-incubating (rc5)
I have checked the release and I have found the following issues: - jar files in the maven2 repo and the distribution differ. No idea how this can happen. (see below)) - francis' signature is not in the KEYS.txt on the website. (see below)) Everything else looks good, except the issues sebb found. If these issues are fixed, an rc will get a +1 from me Thomas I have checked the following: staging repo: - empire-db - jar contains NOTICE and LICENSE -empire-db-struts2 - jar contains NOTICE and LICENSE -empire-db-example-advanced - jar contains NOTICE and LICENSE -empire-db-example-basic - jar contains NOTICE and LICENSE -empire-db-example-cxf - jar contains NOTICE and LICENSE rat report looks good distribution: - NOTICE, LICENSE and DISCLAIMER look good - javadoc looks good - sources look good - sources build - unit tests pass - all required dependencies are available from central repository, - docs (README.txt, tutorial.pdf) look good - md5 and sha1 sums are correct - signatures are correct, however, francis' key is not in the KEYS.txt. This needs to be fixed. compare maven repo and distribution: - empire-db-2.0.5-incubating.jar in staging repo and in zip/tgz differ binaryly. The file size in the staging repository is 269.663 bytes, whereas in the sistribution, it is 269.664 bytes. empire-db-struts2-2.0.5-incubating.jar also seems to be different, but has same file size. Regards, Thomas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Empire-db 2.0.5-incubating (rc5)
Francis De Brabandere franci...@gmail.com schrieb am 13.09.2009 20:38:26: ... the keys on the website points to http://www.apache.org/dist/incubator/empire-db/KEYS I suggest it points to a location in the repo where it is kept so we don't have to update two copies each time. I am not sure this is feasible. Locating it in the dist site seems standard to me, though I do not know whether it is an absolute must. If there is no compelling reason to move it, please keep the file there, but make sure your public key is contained in it. We should at least update the dist/incubator/empire-db/KEYS file when the release is accepted (if we keep it) Francis, you can simply add your key, no matter whether the release is accepted or not, and preferably before the release is voted on. It is no problem if there is no release for a key in the KEYS file. I added myself a while ago to the keys in our repo/trunk/tools/KEYS.txt. Should we move that file to trunk and publish it in the dist? I'm not sure whether I understand you correctly, but the file repo/trunk/tools/KEYS.txt is fine as KEYS file. Just make sure the file in the dist directory has the same content. ... further my public key is available here: http://pgp.mit.edu:11371/pks/lookup?search=francisdb Yes, I checked that. But everybody can upload keys to a keyserver and call themselves Francis De Brabandere, so this is no real protection, just convenience. Thomas On Sun, Sep 13, 2009 at 1:20 PM, Thomas Fischer fisc...@seitenbau.net wrote: I have checked the release and I have found the following issues: ... - francis' signature is not in the KEYS.txt on the website. (see below)) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] apache-empire-db-2.0.4-incubating and apache-empire-struts2-ext-1.0.4-incubating release, 2nd round
+1 Good work. Thomas On Thu, 2 Oct 2008, J?rg Reiher wrote: Hello, the community has approved a release of apache-empire-db-2.0.4-incubating and apache-empire-struts2-ext-1.0.4-incubating. Pursuant to the Releases section of the Incubation Policy we would now like to request the approval of the Incubator PMC to make the release. Release proposal apache-empire-db-2.0.4-incubating: http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL PROTECTED] Vote result apache-empire-db-2.0.4-incubating: http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL PROTECTED] Release proposal apache-empire-struts2-ext-1.0.4-incubating: http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL PROTECTED] Vote result apache-empire-struts2-ext-1.0.4-incubating: http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200810.mbox/[EMAIL PROTECTED] My vote is +1 (non binding) Joerg J?rg Reiher Softwareentwickler Tel. +49 7531 / 45716-14 E-Mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ESTEAM Software GmbH Blarerstra?e 56 D-78462 Konstanz Gesch?ftsf?hrer: David Matthew Bond, Rainer D?bele Sitz: Konstanz, Amtsgericht Freiburg HRB 381845 Internet: www.esteam.de http://www.esteam.de/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]apache-empire-db-2.0.4-incubatingandapache-empire-struts2-ext-1.0.4-incubatingrelease
On Fri, 19 Sep 2008, Henning Schmiedehausen wrote: Well, IMHO you simply erred on the servlet-api / jsp-api thing (empire-db, as an AL 2.0 licensed project is obviously free to include the jars from Apache tomcat, an AL 2.0 licensed project. The LICENSE and NOTICE files from Tomcat state that these files are under AL 2.0). True. I did not realize the jars are from tomcat, sorry for that. But, on the other hand, nobody told me. And, BTW, according to http://www.apache.org/legal/resolved.html, the CDDL 1.0 is part of the B list, which means, you can even bundle the unmodified binary archives, as long as you put appropriate documentation into LICENSE and NOTICE. This is also required by the license. But it was not done in the release candidate in question. I'd reckon that we all now agree that the tomcat jars can be included. Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]apache-empire-db-2.0.4-incubatingandapache-empire-struts2-ext-1.0.4-incubatingrelease
I'd reckon that we all now agree that the tomcat jars can be included. Assuming that they have not included the jars incorrectly. I will check that the jars in question are those released by tomcat. Perhaps it would be better to double-check with legal? If the jars are ASL licensed, I do not see the need. Correct me if I'm wrong. Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]apache-empire-db-2.0.4-incubatingandapache-empire-struts2-ext-1.0.4-incubatingrelease
On Mon, 22 Sep 2008, sebb wrote: On 22/09/2008, Thomas Fischer [EMAIL PROTECTED] wrote: I'd reckon that we all now agree that the tomcat jars can be included. Assuming that they have not included the jars incorrectly. I will check that the jars in question are those released by tomcat. Perhaps it would be better to double-check with legal? If the jars are ASL licensed, I do not see the need. Correct me if I'm wrong. What I meant was - just because the jars are part of another Apache product does not necessarily mean that they are ASL licensed. One would hope that they are, but given some of the other postings in this thread I though it would be prudent to double-check this. I just checked the jsp-api and servlet-api jars from Tomcat 5.5.27 and 6.0.18; unfortunately the jars themselves do not contain NOTICE or LICENSE files, and the jar manifests are no help either - it's not clear where the jars originated. However, looking at the source archives for Tomcat, one can see that the sources for the two jars are present, so it looks like the jars are indeed created from Tomcat sources, not copies of the Sun jars. I looked a a few of the source files, and these have standard AL2.0 headers. So it looks OK to use the jars from Tomcat, as they don't appear to be the Sun jars. It's a pity that the Tomcat jars don't contain proper manifests + N L files; I'll see about raising that with the Tomcat developers. Thanks for checking. I was assuming that the tomcat people know what they are doing. Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]apache-empire-db-2.0.4-incubatingandapache-empire-struts2-ext-1.0.4-incubatingrelease
In fact the jars we had in our struts2-ext 1.0.3 release candidate were taken from Tomcat 5.5. The manifest says: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.6.5 Created-By: 1.4.2_11-b06 (Sun Microsystems Inc.) Name: javax/servlet/ Specification-Title: Java API for Servlets Specification-Version: 2.4 Specification-Vendor: Sun Microsystems, Inc. Implementation-Title: javax.servlet Implementation-Version: 2.4.public_draft Implementation-Vendor: Apache Software Foundation Thomas investigated this and said it was not permitted to distribute those. This was the main reason why he rejected the release. Martijn agreed with that too. @Thomas: since Tomcat is distributing them, why can't we? I was not aware that Tomcat is distributing the libraries under ASL. I was under the impression that only Sun is distributing those and as such I looked at Sun for the license, and found CDDL there. Sorry for that. @Henning: the thread is http://mail-archives.apache.org/mod_mbox/incubator-general/200809.mbox/[EMAIL PROTECTED] Thomas
Re: [VOTE] [POLICY] Allow extra release distribution channels like the central Maven repository
0. There were good reasons for both sides. Regards, Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] apache-empire-db-2.0.4-incubating andapache-empire-struts2-ext-1.0.4-incubating release
On Wed, 17 Sep 2008, Rainer Döbele wrote: With the struts-extentions we're in a dilemma. It won't build without servlet-api.jar and jsp-api.jar. There is an info file that informs the user about the requirement for these two jars. Can you point this file out to me ? I am too stupid to find it in apache-empire-struts2-ext-1.0.4-incubating.tar.gz Cheers, Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: [VOTE] apache-empire-db-2.0.3-incubating and apache-empire-struts2-ext-1.0.3-incubating release
On Mon, 8 Sep 2008, Jörg Reiher wrote: Hello, I've got the following questions regarding the KEYS file and the md5+sha hashes for a release: There is actually a KEYS file located at http://people.apache.org/~reiher/Empire-db-incubating/KEYS Is there something wrong with it or do we have to put it in any other place? Oops, missed that. Sorry. I used gpg to generate the MD5 and SHA hashes. The output of gpg differs from what would be produced by md5sum, because gpg formats the values with blanks between each HEX-String, md5sum doesn't. Is this a problem? If so, the Apache guideline should take this into account (http://www.apache.org/dev/release-signing.html#md5) I am not sure whether it is a real problem, but in my opinion it is more convenient to have the standard format. And as most people are in a hurry nowadays, convenience is important. Regards, Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] apache-empire-db-2.0.3-incubating and apache-empire-struts2-ext-1.0.3-incubating release
On Mon, 8 Sep 2008, Rainer D?bele wrote: ... As far as I understand it, there are two major problems with the empire-struts2-ext-1.0.3 release: 1. the missing freemarker info in the NOTICE file (we'll add HSQLDB as well) 2. the inclusion of servlet-api.jar and jsp-api.jar. Plus the status page (about which you cannot do anything, but as I understand it, it is a requirement that it is up to date when a release is done). Maybe I can spare some time tomorrow evening to update it. We can leave the servlet-api.jar and jsp-api.jar out of the distribution but only for the price that it won't compile off the shelf, and this will make it more difficult for beginners to run the sample. Does anyone have a suggestion how to deal with that (given that we use maven only for a forthcoming release)? I am no ant expert, but there seems to be a tool named ivy which can pull it from the maven replository. Since all issues concern the empire-struts2-ext-1.0.3 distribution, does this mean that the -1 is for this part only? And would you give a +1 for the empire-db-2.0.3 release? (Just want to make sure, we're on the right track). As soon as the status page is up to date, I'd give a +1 to the db 2.0.3 release; if you think it makes sense to release it without the struts extension. Since we built the 2.0.3 / 1.0.3 release we have made some improvemets and bugfixes. I suggest skipping these releases and continuing with the 2.0.4 and 1.0.4 release. Hm, the 2.0.3 release is not released yet. You can still call the new release 2.0.3. However, to avoid naming confusion, I'd suggest to call a release candidate e.g. RC1 in the future, and rename it when the voting is through (in the docs etc the final name can be used, but in the release file names the rc part should be in. So you can just rename the files and copy the tag once the voting is done.) But calling the new release candidate 1.0.4 and 2.0.4 is also fine with me. Regards, Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] apache-empire-db-2.0.3-incubating and apache-empire-struts2-ext-1.0.3-incubating release
I checked the Release candidate against the incubator release check list [1] and found the following: - All Files unpack correctly. - The code builds from source. - the status page is not up to date. - All files have a valid md5 sum, sha hash and are signed properly. However, the format of the md5 and sha sum files is not linux standard, making automatic checks more difficult. I am not sure whether that causes mirroring problems. - There is not yet a KEYS file. - The NOTICE and various LICENSE files are ok, except the following: -- The asf part is not the first part of the /NOTICE file in the db and the struts2 extension. See [2] -- freemarker is not in the /NOTICE file of the struts2 extension. However, the freemarker License requires it. The appropriate passage from the Freemarker license needs to be copied into the NOTICE file. -- The HSQLDB library is not mentioned in the /NOTICE file of the db part. Ihe HSQL License does not require it, but I'd add it anyway. - The Servlet API and JSP API are contained in the struts 2 extension distribution. The Source code is not included; neither there is a prominent notice to where it can be obtained. This is against the CDDL License [3] and apache licensing policy [4]. - The README Files are ok except the following: -- The README File of the struts2 extension is misleading. It is said there that This Extension works with the Sysdeo-DevLoader. I'd hope it works in a standalone servlet container as well ? -- The README should contain information how the code can be built from source. In the db part it should say where the build.xml is located; in the struts2 extension this part misses. - The documentation of the struts2 extension is a bit sparse. It contains javadocs and a small Readme. Perhaps the documentation from the web site can be included ? - There is a file apache-empire-struts2-ext-1.0.3-incubating.tar.gzmd5, which content does not fit its name. Probably it is there by error. - The example applications contain all the libraries in the /lib directory again. For bandwith reasons, it would be better to supply an ant script which compiles and packages the examples by using the /lib files. - The RAT reports look good. [1] http://incubator.apache.org/guides/releasemanagement.html [2] http://www.apache.org/legal/src-headers.html [3] http://www.sun.com/cddl/cddl.html [4] http://www.apache.org/legal/resolved.html Regarding the license issues, I regret that I am forced to vote -1 on this Release Candidate. I am sorry that I could not check the RC while the vote was on the dev list, but I had a lot of work to do this week. Regards, Thomas P.S. Who is responsible for updating the status page ? Should that be done by the mentor, or can I as IPMC member also do that ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] JDO out of incubation and into the DB project ( was Re: [discussion] JDO out of incubation)
+1 Thomas On Mon, 5 Dec 2005, Geir Magnusson Jr. wrote: I repurposed the discussion thread for continuity to call for a vote. There has been no concern or objection noted in the last two weeks, so I'll assume that people are comfortable with this. So what say ye? [ ] +1 Graduate JDO from the Apache Incubator to be a part of the DB TLP [ ] -1 Do not graduate at this time because : I'd like to ask that this vote run 72 hours so that in the event of a successful vote, we can flip the project over to DB in time for ApacheCon. geir - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
