Surely, and would provide a common language when talking about issues. No need to ask if this is set up this way or if that is installed. Everybody would have a common ground.
Angelo Em 10/09/2012, às 12:59, Jesse Tayler escreveu: > > Pascal makes a really good point! > > If we, > > as a community, > > were able to standardize the workspace to INCLUDE WOnder and the frameworks > and install setup, so that one could indeed build->deploy reliably etc. that > would be amazingly useful. > > we would all be using the same developer setup core which would provide tons > of reliability and visibility benefits to everyone. > > We could call it ... > > fluffy monkey. > > > > > On Sep 10, 2012, at 11:48 AM, Pascal Robert <[email protected]> wrote: > >> +1. And I'm willing to give $75 to anyone who back extend Golipse so that it >> also install Wonder and the core WO frameworks along Eclipse, WOLips and >> Workspace Mechanics. Bonus points if your solution also work on Windows and >> Linux. It doesn't have to be Golipse, but it have to install Workspace >> Mechanics. >> >>> I submit that if folks have troubles with golips or its configuration >>> somehow, >>> >>> we put in the community-wide effort to ensure that whatever fixes or >>> workarounds might be required are reflected in golips. >>> >>> for example -- if we have troubles with a release of Eclipse, >>> >>> or anything like that -- the best and safest place for the whole community >>> has got to be golips. >>> >>> besides, people have already put a ton of great work into golips, >>> >>> reliably creating a new developer environment is __KEY__ >>> >>> if go lips doesn't work for you, be sure at least to post to the list so we >>> can take a look, because we're all doing the same stuff here -- using >>> golips, we're watching out for each other. >>> >>> just my two cents there -- >>> >>> >>> >>> On Sep 10, 2012, at 11:03 AM, "Ângelo Andrade Cirino" <[email protected]> >>> wrote: >>> >>>> Hi Pascal, >>>> >>>> Em 10/09/2012, às 11:23, Pascal Robert escreveu: >>>>> >>>>> What do you have in the EO_PK_TABLE table? And this part of a migration? >>>> >>>> The EO_PK_TABLE isn't part of the migration and is correctly created after >>>> the first inserts in the database. Interesting enough, the PK table is >>>> updated even for the failed attachment insert attempts. For instance, the >>>> ERAttachments PKs are ERAttachment = 5 and ERAttachmentData = 5 after my >>>> attempts to insert new images, but the database only holds one image so >>>> far for the first and only successful insert. All the other PKs are >>>> correct. >>>> >>>>> >>>>> Do you have the JDBC properties set with the same values in all 3 apps? >>>> >>>> Yes, the three applications use exactly the same JDBC properties from one >>>> single and shared framework. I set up this framework to hold the models >>>> and the JDBC connections. I've played with the JDBC properties being >>>> loaded by three different methods: the model, the properties file and from >>>> a notification. The three methods give the same outcome. >>>> >>>> I am clueless. >>>> >>>> Regards, >>>> >>>> Angelo >>>> _______________________________________________ >>>> Do not post admin requests to the list. They will be ignored. >>>> Webobjects-dev mailing list ([email protected]) >>>> Help/Unsubscribe/Update your Subscription: >>>> https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com >>>> >>>> This email sent to [email protected] >>> >> > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
