Hi Christian,

yes, contribution maintainers should avoid listing "trunk" as a 
compatible qooxdoo version since there's no way to ensure compatibility 
with a moving target.

There's no logic that implicitly replaces "1.2pre" with "trunk". One 
thing to keep in mind is that the contribDemobrowser's "build" job 
ignores the "qooxdoo-versions" entry of the *demo*'s manifest and the 
"QOOXDOO_PATH" macro of the demo's config.json. Instead, demos are 
linked against each qooxdoo version listed in the *contribution* 
manifest. That's why you'll see multiple lines like "Generating build 
version of demo variant X...". Maybe that explains why you're not 
getting any errors.

We're busy with the 1.1.1/1.2 releases right now but once they're out 
the door we'll focus on getting the contribDemobrowser online.


Regards,
Daniel

panyasan schrieb:
> Hi,
> 
> as the demo browser for contributions is being finalized, I wonder about one
> thing in the demo Manifest files. When I build the contribDemoBrowser now,
> it will complain about non-existent qooxdoo versions and skip the demos that
> are flagged to work with these versions, such as, for example "1.0", because
> there is no "1.0" symlink in the qooxdoo/ folder of my local qooxdoo-contrib
> working copy. However, it does not complain about "1.2pre" which does not
> exist, either (although "trunk" does exist). Does that mean we're supposed
> to use "1.2pre" rather than "trunk" in the Manifest files and it will
> automatically figure out that this is a trunk version (and complain if the
> trunk version has changed?). That would make sense and would be much smarter
> than "trunk" since the trunk is a moving target. 
> 
> Just let us know so we can update the Manifest files accordingly. 
> 
> I am looking forward to the contribDemoBrowser be published and I hope this
> will motivate people to update their qooxdoo-contrib projects and
> publish/update demos for them!
> 
> Christian


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to