Re: ContinuumStore refactoring
I'll create some examples asap. Emmanuel On Thu, Feb 28, 2008 at 4:07 AM, Rahul Thakur [EMAIL PROTECTED] wrote: Hi, Some code using a couple of Entities as examples would be nice :-) I still think the API would be verbose. Thanks, Rahul On Fri, Feb 22, 2008 at 11:06 PM, Emmanuel Venisse [EMAIL PROTECTED] wrote: On Fri, Feb 22, 2008 at 10:45 AM, Rahul Thakur [EMAIL PROTECTED] wrote: 2) Criteria vs Named Queries: I am not convinced (yet) that Named queries are the way to go. I did some digging around, they are indeed best practices for JPA but I think the decision merits other consideration(s). I still believe the Criteria Queries will help us define a cleaner Store interface. I'm always in favor of named queries. An other point about them that I haven't explain in previous threads (I think) is that with named queries, it is possible to modify queries externally with xml files so if with a DB we have some performance issues, it will be possible to override queries by a modified JPQL query or a native query. How do you see the refactored ContinuumStore interface using Named Queries? I suspect it will be just as verbose again. I don't want to see a new time a big class for the store part. it must be splitted in few domains. All named queries related to Project would be defined in the Project class, all named queries related to ProjectGroup would be defined in the ProjectGroup class... And we can add some more classes for particular results that aren't entities objects (we won't have a lot) With this, all concerns are separated and linked to a specific entity. Easy to code, easy to read, easy to understand. It's my opinion. Sorry, still not convinced ;-) I hope you are now ;-) Emmanuel Rahul
Re: CI Server Poll
thx Rahul for this link. We are #2 now :) On Thu, Feb 28, 2008 at 4:51 AM, Rahul Thakur [EMAIL PROTECTED] wrote: Hi, Any one seen this: http://www.wakaleo.com/polls/18-what-continuous-integration-server-are-you-using-in-2008 Another 5 steps to get to #1 :-) Rahul
Re: svn commit: r632127 - /maven/continuum/branches/continuum-1.x/pom.xml
The users one seems to be missing the users. prefix in both - is there a reason for that? - Brett On 29/02/2008, at 8:58 AM, [EMAIL PROTECTED] wrote: Author: evenisse Date: Thu Feb 28 13:58:44 2008 New Revision: 632127 URL: http://svn.apache.org/viewvc?rev=632127view=rev Log: Update markmail addresses Modified: maven/continuum/branches/continuum-1.x/pom.xml Modified: maven/continuum/branches/continuum-1.x/pom.xml URL: http://svn.apache.org/viewvc/maven/continuum/branches/continuum-1.x/pom.xml?rev=632127r1=632126r2=632127view=diff = = = = = = = = == --- maven/continuum/branches/continuum-1.x/pom.xml (original) +++ maven/continuum/branches/continuum-1.x/pom.xml Thu Feb 28 13:58:44 2008 @@ -41,22 +41,48 @@ inceptionYear2003/inceptionYear mailingLists mailingList - nameContinuum Dev List/name - subscribe[EMAIL PROTECTED]/subscribe - unsubscribe[EMAIL PROTECTED]/ unsubscribe - archivehttp://mail-archives.apache.org/mod_mbox/maven-continuum-dev/ /archive -/mailingList -mailingList nameContinuum User List/name + post[EMAIL PROTECTED]/post subscribe[EMAIL PROTECTED]/ subscribe unsubscribe[EMAIL PROTECTED]/ unsubscribe archivehttp://mail-archives.apache.org/mod_mbox/maven-continuum-users/ /archive + otherArchives +otherArchivehttp://www.mail-archive.com/[EMAIL PROTECTED] /otherArchive +otherArchivehttp://www.nabble.com/Continuum---Users-f13868.html /otherArchive +otherArchivehttp://continuum.markmail.org//otherArchive + /otherArchives +/mailingList +mailingList + nameContinuum Developer List/name + postcontinuum-dev@maven.apache.org/post + subscribe[EMAIL PROTECTED]/subscribe + unsubscribe[EMAIL PROTECTED]/ unsubscribe + archivehttp://mail-archives.apache.org/mod_mbox/maven-continuum-dev/ /archive + otherArchives +otherArchivehttp://www.mail-archive.com/continuum-dev@maven.apache.org /otherArchive +otherArchivehttp://www.nabble.com/Continuum---Dev-f13867.html /otherArchive +otherArchivehttp://dev.continuum.markmail.org// otherArchive + /otherArchives /mailingList mailingList - nameContinuum Commit List/name + nameContinuum Commits List/name subscribe[EMAIL PROTECTED]/ subscribe unsubscribe[EMAIL PROTECTED]/ unsubscribe archivehttp://mail-archives.apache.org/mod_mbox/maven-continuum-commits/ /archive + otherArchives +otherArchivehttp://www.mail-archive.com/[EMAIL PROTECTED] /otherArchive +otherArchivehttp://maven.continuum.commits.markmail.org// otherArchive + /otherArchives +/mailingList +mailingList + nameContinuum Issues List/name + subscribe[EMAIL PROTECTED]/ subscribe + unsubscribe[EMAIL PROTECTED]/ unsubscribe + archivehttp://mail-archives.apache.org/mod_mbox/maven-continuum-issues/ /archive + otherArchives +otherArchivehttp://www.mail-archive.com/[EMAIL PROTECTED] /otherArchive +otherArchivehttp://www.nabble.com/Continuum---Issues-f29618.html /otherArchive + /otherArchives /mailingList /mailingLists scm @@ -781,6 +807,11 @@ groupIdorg.codehaus.plexus.redback/groupId artifactIdredback-data-management/artifactId version${redback.version}/version + /dependency + dependency +groupIdcommons-httpclient/groupId +artifactIdcommons-httpclient/artifactId +version3.1/version /dependency /dependencies /dependencyManagement -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: svn move (was: Re: Apache Continuum is now an Apache top level project)
This has been done (and switch works just fine). No other changes should be needed on your end. - Brett On 26/02/2008, at 12:02 PM, Wendy Smoak wrote: On Mon, Feb 25, 2008 at 4:39 PM, Emmanuel Venisse [EMAIL PROTECTED] wrote: I created the svn group with all pmc members. The next step will be the svn move to the new location. I'd like to see the move done for the end of the week, so if you have some changes to commit, you must do it asap. If you have local changes you don't want to commit, I think 'svn switch' will work afterwards to point an existing working copy at a new url. -- Wendy -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: svn commit: r632127 - /maven/continuum/branches/continuum-1.x/pom.xml
yes, it is an error. Emmanuel On Thu, Feb 28, 2008 at 11:13 PM, Brett Porter [EMAIL PROTECTED] wrote: The users one seems to be missing the users. prefix in both - is there a reason for that? - Brett On 29/02/2008, at 8:58 AM, [EMAIL PROTECTED] wrote: Author: evenisse Date: Thu Feb 28 13:58:44 2008 New Revision: 632127 URL: http://svn.apache.org/viewvc?rev=632127view=rev Log: Update markmail addresses Modified: maven/continuum/branches/continuum-1.x/pom.xml Modified: maven/continuum/branches/continuum-1.x/pom.xml URL: http://svn.apache.org/viewvc/maven/continuum/branches/continuum-1.x/pom.xml?rev=632127r1=632126r2=632127view=diff = = = = = = = = == --- maven/continuum/branches/continuum-1.x/pom.xml (original) +++ maven/continuum/branches/continuum-1.x/pom.xml Thu Feb 28 13:58:44 2008 @@ -41,22 +41,48 @@ inceptionYear2003/inceptionYear mailingLists mailingList - nameContinuum Dev List/name - subscribe[EMAIL PROTECTED]/subscribe - unsubscribe[EMAIL PROTECTED]/ unsubscribe - archive http://mail-archives.apache.org/mod_mbox/maven-continuum-dev/ /archive -/mailingList -mailingList nameContinuum User List/name + post[EMAIL PROTECTED]/post subscribe[EMAIL PROTECTED]/ subscribe unsubscribe[EMAIL PROTECTED]/ unsubscribe archive http://mail-archives.apache.org/mod_mbox/maven-continuum-users/ /archive + otherArchives +otherArchive http://www.mail-archive.com/[EMAIL PROTECTED] /otherArchive +otherArchive http://www.nabble.com/Continuum---Users-f13868.html /otherArchive +otherArchivehttp://continuum.markmail.org//otherArchive + /otherArchives +/mailingList +mailingList + nameContinuum Developer List/name + postcontinuum-dev@maven.apache.org/post + subscribe[EMAIL PROTECTED]/subscribe + unsubscribe[EMAIL PROTECTED]/ unsubscribe + archive http://mail-archives.apache.org/mod_mbox/maven-continuum-dev/ /archive + otherArchives +otherArchive http://www.mail-archive.com/continuum-dev@maven.apache.org /otherArchive +otherArchivehttp://www.nabble.com/Continuum---Dev-f13867.html /otherArchive +otherArchivehttp://dev.continuum.markmail.org// otherArchive + /otherArchives /mailingList mailingList - nameContinuum Commit List/name + nameContinuum Commits List/name subscribe[EMAIL PROTECTED]/ subscribe unsubscribe[EMAIL PROTECTED]/ unsubscribe archive http://mail-archives.apache.org/mod_mbox/maven-continuum-commits/ /archive + otherArchives +otherArchive http://www.mail-archive.com/[EMAIL PROTECTED] /otherArchive +otherArchivehttp://maven.continuum.commits.markmail.org// otherArchive + /otherArchives +/mailingList +mailingList + nameContinuum Issues List/name + subscribe[EMAIL PROTECTED]/ subscribe + unsubscribe[EMAIL PROTECTED]/ unsubscribe + archive http://mail-archives.apache.org/mod_mbox/maven-continuum-issues/ /archive + otherArchives +otherArchive http://www.mail-archive.com/[EMAIL PROTECTED] /otherArchive +otherArchive http://www.nabble.com/Continuum---Issues-f29618.html /otherArchive + /otherArchives /mailingList /mailingLists scm @@ -781,6 +807,11 @@ groupIdorg.codehaus.plexus.redback/groupId artifactIdredback-data-management/artifactId version${redback.version}/version + /dependency + dependency +groupIdcommons-httpclient/groupId +artifactIdcommons-httpclient/artifactId +version3.1/version /dependency /dependencies /dependencyManagement -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: svn move (was: Re: Apache Continuum is now an Apache top level project)
Thanks Brett. Emmanuel On Thu, Feb 28, 2008 at 11:27 PM, Brett Porter [EMAIL PROTECTED] wrote: This has been done (and switch works just fine). No other changes should be needed on your end. - Brett On 26/02/2008, at 12:02 PM, Wendy Smoak wrote: On Mon, Feb 25, 2008 at 4:39 PM, Emmanuel Venisse [EMAIL PROTECTED] wrote: I created the svn group with all pmc members. The next step will be the svn move to the new location. I'd like to see the move done for the end of the week, so if you have some changes to commit, you must do it asap. If you have local changes you don't want to commit, I think 'svn switch' will work afterwards to point an existing working copy at a new url. -- Wendy -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Confused about the branches
Hi, I'm a bit confused about the current branch scenarios, we have 1.2 on a branch and 2.0 on trunk. Several changes have been made on each, and none merged to the other. Can I suggest we merge all branch changes to trunk, rename trunk to 1.2-SNAPSHOT, and the branch to continuum-1.1.x (1.1.1-SNAPSHOT) and use that for bugfixes only? WDYT? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Confused about the branches
why 1.1.x? On Thu, Feb 28, 2008 at 11:45 PM, Brett Porter [EMAIL PROTECTED] wrote: Hi, I'm a bit confused about the current branch scenarios, we have 1.2 on a branch and 2.0 on trunk. Several changes have been made on each, and none merged to the other. Can I suggest we merge all branch changes to trunk, rename trunk to 1.2-SNAPSHOT, and the branch to continuum-1.1.x (1.1.1-SNAPSHOT) and use that for bugfixes only? WDYT? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Confused about the branches
On 29/02/2008, at 9:52 AM, Emmanuel Venisse wrote: why 1.1.x? in case there was a bugfix release on 1.1? I thought that was what the branch was for... maintenance of 1.1. or is there going to be 2 completely different strands of development? - Brett On Thu, Feb 28, 2008 at 11:45 PM, Brett Porter [EMAIL PROTECTED] wrote: Hi, I'm a bit confused about the current branch scenarios, we have 1.2 on a branch and 2.0 on trunk. Several changes have been made on each, and none merged to the other. Can I suggest we merge all branch changes to trunk, rename trunk to 1.2-SNAPSHOT, and the branch to continuum-1.1.x (1.1.1-SNAPSHOT) and use that for bugfixes only? WDYT? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Confused about the branches
On Thu, Feb 28, 2008 at 11:55 PM, Brett Porter [EMAIL PROTECTED] wrote: On 29/02/2008, at 9:52 AM, Emmanuel Venisse wrote: why 1.1.x? in case there was a bugfix release on 1.1? I thought that was what the branch was for... maintenance of 1.1. or is there going to be 2 completely different strands of development? I thought to do 1.x in the branch instead of only maintenance in 1.1.xbecause I don't know how many time we'll need for the first 2.0 release. User will probably need some new small feature before the 2.0release and not only maintenance. - Brett On Thu, Feb 28, 2008 at 11:45 PM, Brett Porter [EMAIL PROTECTED] wrote: Hi, I'm a bit confused about the current branch scenarios, we have 1.2 on a branch and 2.0 on trunk. Several changes have been made on each, and none merged to the other. Can I suggest we merge all branch changes to trunk, rename trunk to 1.2-SNAPSHOT, and the branch to continuum-1.1.x (1.1.1-SNAPSHOT) and use that for bugfixes only? WDYT? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/