On 09/27/2011 11:42 AM, John Spackman wrote: > Hi, > > So as I understand it, if we want to continue to use the old "source" > job we will have to edit our config.json to add "source-each" to the > exports and change any scripts or code that run generate.py to now > call "source-each"?
That's right. Alternatively to adding 'source-each' to the "export" section you can just remove that; it is only a filter for jobs available through your config.json. > And trying to use the the "source-hybrid" job will cause an error? No, like with other deprecations it will continue to work until the next minor version. > > For my two cents, I think it's debatable which would be the more > natural for a newbie but for existing developers changing the names of > the jobs is annoying because it was not necessary and it requires > existing developers to edit their config.json to maintain the same > functionality (in my case there is code outside Qooxdoo to change too). We have similar projects, and there it is just changing one line in an Ant file. What I find more interesting here is your interest in the old, every-file-from-its-file-location semantics. Why is that attractive to you? Why wouldn't you just have a hybrid symantics for the source build and just get on with it? > It's great that you're highlighting the change in a blog post, but if > someone does not happen to read that blog post or accidentally tries > to use an out of date config.json or a script, the generator will not > work as expected. It won't give an error or a warning – it will just > silently produce different code. That's right, but the blog posts are mainly for trunk users, and users of released versions will learn all they need to know from the release notes (which they have to check anyway when upgrading to a new version). > If the user or script tries to use "source-hybrid" it will not be able > to complete. Yes, it will, see above. > > IMHO the better solution would be to use the already available > default-job to set the default to "source-hybrid" and change the > getting started documentation to tell users to just "./generate.py" -- > existing developers probably already know about source-hybrid and are > making an explicit choice, newbies can find out about full source > builds later, and nothing is silently broken. Yep, that's a valid alternative which is in the discussion. Thanks, T. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
