|Re: [tigerstripe-dev] Critical bug for JOSIF|
Thanks for the investigation.
If you fixed a bug, then please yes, push the fix to the josif update site.
It took me quite a bit of investigation but I don't think there is an issue here:
In order to get $all* collections of the TS Velocity context populated the user needs to uncheck the "Run All Rules as Local" checkbox in the Generation section of the Advanced tab of the tigerstripe.xml or the model project. This is probably a new feature since you last updated (it was new to me).
Please can you give this a try?
However, when I was looking at this I found it was not possible to add a new Module Dependency to a Tigerstripe model project. This bug has now been fixed. Do you want us to push another release to the JOSIF update site with this fix?
Hi Tigerstripe team,
In our current version of JOSIF, we are using an old version of Tigerstripe from Feb 2011.
We are testing the new Tigerstripe version you made for us, which corresponds to I53 for integration in our new JOSIF version and we have found a critical bug that xose has filled in bugzilla: Bug 383728
We are using dependency modules systematically in our projects and the behavior has changed from the version we use in the previous version of JOSIF,
When trying to get all the artifacts inside the project with the variable $allPackages we got different responses in the two versions of Tigerstripe. In the new version, only the model packages are shown.
Is there now a different way of getting model and dependency packages all together?
This is a show-stopper for us.
Thanks for your support,