Return-Path: Delivered-To: apmail-incubator-empire-db-dev-archive@minotaur.apache.org Received: (qmail 78483 invoked from network); 23 Feb 2009 22:30:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Feb 2009 22:30:52 -0000 Received: (qmail 89365 invoked by uid 500); 23 Feb 2009 22:30:52 -0000 Delivered-To: apmail-incubator-empire-db-dev-archive@incubator.apache.org Received: (qmail 89348 invoked by uid 500); 23 Feb 2009 22:30:52 -0000 Mailing-List: contact empire-db-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: empire-db-dev@incubator.apache.org Delivered-To: mailing list empire-db-dev@incubator.apache.org Received: (qmail 89337 invoked by uid 99); 23 Feb 2009 22:30:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Feb 2009 14:30:52 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of francisdb@gmail.com designates 72.14.220.154 as permitted sender) Received: from [72.14.220.154] (HELO fg-out-1718.google.com) (72.14.220.154) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Feb 2009 22:30:42 +0000 Received: by fg-out-1718.google.com with SMTP id d23so21993fga.26 for ; Mon, 23 Feb 2009 14:30:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=1Yohw5WGRV8xpMFzwfHoT9scjhV2mMguNtB+SBXHDGM=; b=Pz/uUyaCovK1k7So6GxBPVO7TZJHFV9aC6QxOHWU9rjxyOHuhH02H16XLWiUVVsvS8 bqJiXZipg9rqackdXDSZRAO43eLBqqQcnQlnUOfmeWckfCyZMiGB4pynxzgQT9x/Ea21 PVdsaQhq8MAM1kHVP9wiCDQuIcTEQ6VkDJyjI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=I0sEYiIkB1znYD5h/5qRgwvxkP3zffKHtdAs56effuSsKjBv5LjorUUT7Se58PDPLh 6PFXnRNy7QOzwMCkocdnFyXBJhydkhtPumxp0xL52lunnVnTnvy6mij1GYdjRUT/ekLZ rspKG1L1pZYRgOBRPhrwGwrbTHou5Yo6UnLiE= MIME-Version: 1.0 Received: by 10.86.70.3 with SMTP id s3mr3271806fga.25.1235428219766; Mon, 23 Feb 2009 14:30:19 -0800 (PST) In-Reply-To: References: <3ab983230902220734q691954bbq36a80f3079057feb@mail.gmail.com> <3ab983230902221446o757c71c9j52b2443263cc9931@mail.gmail.com> Date: Mon, 23 Feb 2009 23:30:19 +0100 Message-ID: <3ab983230902231430j6a038f7dma8b72eed4df37a79@mail.gmail.com> Subject: Re: merging to maven layout From: Francis De Brabandere To: empire-db-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org >> some things to discuss: >> - keep release of struts2 extension on different version numbers? > > Good question. Technically yes, since are only loosely coupled and not ev= ery change in one of them requires a change of the other one. And if one da= y we have another component for connecting Wicket or RCP we don't want them= to have the same version number from the start, do we? It's a lot more work to split things up, in the end you'll have a lot of projects to release. In wicket they perform a release on the parent pom and all modules are released automatically. I don't see a problem in starting a component on a non-1.0 version. >> Wicket for example releases all main extensions together and has a >> wicketstuff project for other (external) extensions... >> - see what extra files need to be moved from the old structure (old >> folder) > > The svn has been really slow today, I could hardly browse the repo. > We surely need the readme files (I will move them when svn is quicker aga= in). > I am missing the tutorial.pdf. Any idea where it has gone? > in the samples examples project >> - I set up a temporary non-official snapshot maven repo at: >> http://people.apache.org/~francisdb/empire-db/repo (daily snapshot >> release in my CI server but the machine is not always powered on...) >> - The maven generated website is uploaded to: >> http://people.apache.org/~francisdb/empire-db/site but there still are >> some problems, the site is handy for code coverage info and other >> stuff: >> eg: http://people.apache.org/~francisdb/empire-db/site/empire- >> db/project-reports.html > > Looks great. But how do we combine that with our official project home pa= ge (that is unfortunately harder to update and in many ways out of date). once we have real releases we can push them to the apache incubator maven repo: http://people.apache.org/repo/m2-incubating-repository/ for the site, we'll have to update it manually, we need a release procedure anyway >> I think that we should now think about having everything set up for a >> 'correct' release. I'll add some more stuff later this week like >> checking for apache headers, more unit tests,... > > Absolutely. > Don't underestimate the legal stuff. The mentors and the incubator PMC wi= ll have a very close look that everything is in the right place, all licens= e information is given and apache headers are present everywhere. > About the testing: In theory automated unit testing is great but I am alw= ays a bit skeptical that you get enough bangs for the buck. In our case, we= need to make sure, that all three sample applications run as provided plus= we need to make sure that both the basic and the advanced sample run corre= ctly with every database driver we supply. It should be possible to write a= unit test for that, but it requires an environment where all database are = installed. > Since an official release is really a major thing, I could live (for now)= with manual testing of the above and concentrate our efforts on other thin= gs. Are there any tools available to test the validity? Do you have an export of the eclipse formatter available (empire-db code style)? Testing the embedded drivers is not that hard and I can set up mysql/postge tests as well on my CI server here at home but indeed this is not crucial. On the other hand it doesn't hurt to have everything covered by tests. > BTW: Have you tested your new Drivers (postgree, h2 and derby) with both = examples? I only tested the main example, I'll test them again using both examples later this week. > I saw you have excluded those drivers from using the reverse function in = the SampleApp class. > Maybe we should find another example to show people how to perform comple= x column transformations. I think we need a test/demo app that uses all available functions (or at least the ones that work on all servers) >> >> So in fact empire-db can already be tested by maven users, all they >> need to do is add the snapshot repository in their projects's >> pom/settings file. >> > > I think we need an official release and a registration in the central Mav= en repository to really get things moving. incubator releases can not be pushed to central as far as I know > > I would like to add two more examples to the project. > One is a WebService that provided data from the database. > The other one is a Stuts2 Web Application similar to the one we already h= ave, but that uses the WebService rather than direcly accessing the databas= e. It shows that Empire-db's metadata management facilities can even be use= d without a database. > Is it OK if I just check the new projects in below the empire-db examples= branch? yep, you can copy the pom from the struts2 example and adjust the artifact-id and name + put the module (module folder name) in the examples parent pom > P.S. Thanks again for your great work. no problem, I'll be glad when we reach a release --=20 http://www.somatik.be Microsoft gives you windows, Linux gives you the whole house.