Re: [VOTE] Apache Cayenne, release 3.0RC1

+1 on the new artifacts, works well. regards Malcolm Edgar On Mon, Dec 28, 2009 at 12:08 AM, Andrus Adamchik wrote: > Fixed. I posted the new artifacts. > > Andrus > > > On Dec 27, 2009, at 1:09 PM, Andrus Adamchik wrote: > > Good catch. I missed this one and I want to see in in RC1. Let me fix

Build failed in Hudson: Cayenne-tr unk » HSQLDB,JDK 1.6 (latest) #136

See Changes: [aadamchik] CAY-1251 Memorize user-selected column widths in preferences second patch by Ksenia Khailenko. The Jira is done --

Re: maven dependency issues

On Dec 28, 2009, at 5:38 PM, Andrey Razumovsky wrote: Not sure this will be of help, but is it OK that tutorial POM does not have a parent while it is referenced by "tutorials"? It has no parent intentionally for the reason that I mentioned, and yes, it is one possible cause why it fails

Re: maven dependency issues

2009/12/28 Andrus Adamchik > > 6. >> /zonestorage/hudson/home/hudson/hudson/jobs/Cayenne-30/workspace/cayenneTestConnection/HSQLDB/jdk/JDK >> 1.6 >> (latest)/STABLE-3.0/tutorials/tutorial/src/main/java/org/apache/cayenne/tutorial/persistent/auto/_Painting.java:[3,25] >> cannot find symbol >> Is

Re: [jira] Created: (CAY-1349) SelectQuery 'fetchSize' setting is not propagated to disjoint prefetches

I've no idea what performance hit we'll take by enabling this setting. Looking at MySQL driver code I have a suspicion it may slow down smaller queries, as it switches to the "streaming mode" if the fetch size is enabled.. So one size may not fit all here. I'd say this needs to be researche

Re: [jira] Created: (CAY-1349) SelectQuery 'fetchSize' setting is not propagated to disjoint prefetches

Would not it be better if we also had application-scoped statement fetch size? After all, this is a way to decrease memory payload 2009/12/28 Andrus Adamchik (JIRA) > SelectQuery 'fetchSize' setting is not propagated to disjoint prefetches > --

Re: svn commit: r893766 - /cayenne/main/trunk/framework/cayenne-modeler/src/main/java/org/apache/cayenne/modeler/editor/datanode/MainDataNodeEditor.java

It is the same error. 2009/12/25 Ольга Ткачева > Maybe, it is bug. I still didn't finish migration to API Preferences.I will > see it in Monday. Thank you for comment > > > 2009/12/25 Andrey Razumovsky > > I'm not sure this is same error, but now comboboxes in mirgate/generate >> schema dialog

Build failed in Hudson: Cayenne-tr unk » HSQLDB,JDK 1.6 (latest) #135

See Changes: [andrey] reverting pom changes [aadamchik] CAY-1251 Memorize user-selected column widths in preferences patch by Ksenia Khailenko - memorizes both width an

Re: svn commit: r894141 - /cayenne/main/trunk/tutorials/tutorial/pom.xml

OK, I'll revert. just wanted to see if scopes affect maven build 2009/12/28 Andrus Adamchik > Andrey, > > The tutorial project is special, and I intentionally defined all the > versions explicitly, as it has to look as a standalone module to the end > user once packaged in a distro. > > Andrus >

Re: svn commit: r894141 - /cayenne/main/trunk/tutorials/tutorial/pom.xml

Andrey, The tutorial project is special, and I intentionally defined all the versions explicitly, as it has to look as a standalone module to the end user once packaged in a distro. Andrus On Dec 28, 2009, at 11:05 AM, and...@apache.org wrote: Author: andrey Date: Mon Dec 28 09:05:49 2

Re: maven dependency issues

On Dec 28, 2009, at 11:19 AM, Aristedes Maniatis wrote: No, I think we need install because none of the modules are able to build against other modules since they can't 'find' each other. Since the parent references are fictional, maven is unable to traverse the build tree and figure out h

Build failed in Hudson: Cayenne-tr unk » HSQLDB,JDK 1.6 (latest) #134

See Changes: [andrey] playing with maven dependencies -- [...truncated 72009 lines...] [INFO] [resources:testResources] [INFO] Us

Re: maven dependency issues

On 28/12/09 7:41 PM, Andrus Adamchik wrote: IIRC the only reason install is needed is because we have maven plugins built, that are themselves used during the build (build-tools). For everything else install is not needed. So the problems are likely elsewhere. No, I think we need install becau

Re: maven dependency issues

On Dec 28, 2009, at 10:41 AM, Andrus Adamchik wrote: On Dec 28, 2009, at 3:55 AM, Aristedes Maniatis wrote: 2. If we want to avoid some ongoing pain and hassle, we need to remove the need to 'install' every module. That will probably fix Clover as well. To me that seems straightforward an

Re: maven dependency issues

On Dec 28, 2009, at 3:55 AM, Aristedes Maniatis wrote: 2. If we want to avoid some ongoing pain and hassle, we need to remove the need to 'install' every module. That will probably fix Clover as well. To me that seems straightforward and if that means some people need to add one more pom t

Re: maven dependency issues

Or we can actually delete the 1.6 module on 3.0 branch all together, as it doesn't contain anything useful (or anything at all for that matter). (same for 3.1 I guess, but I was hoping we'll start using 1.6 features at some point). On Dec 28, 2009, at 10:08 AM, Andrey Razumovsky wrote:

Re: maven dependency issues

2009/12/28 Aristedes Maniatis > > 1. If we want Javadocs for 3.0 then we need to hack that branch to work > around the fact that maven can't build javadocs properly. Maybe we need to > add this to the appropriate modules: > > > org.apache.maven.plugins > maven-javadoc-plugin > > > tru