[Glass] Sixx problematic
Locked
12
12
Re: [Glass] Sixx problematic
 
|
Okay ... SIXX is refrencing the #stable version of XML Support which
means that Monty's new stuff gets loaded and that is just wrong ...
now that Know what we know, the SIXX baseline can be adjusted to
reference XMLSupport 1.2.2.1 and we can be off to the races I think
...
I've submitted a SIXX issue[1] and when the tests[2] are passing, I will commit my changes to the master branch and you should be good to go ... Dale [1] https://github.com/glassdb/SIXX/issues/3 [2] https://travis-ci.org/glassdb/SIXX/builds/54913047 On 03/18/2015 11:06 AM, Dario Trussardi
via Glass wrote:
Dale, _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Sixx problematic
|
|
Ciao Dale,
I do load SIXX support now, but report the hold problematic. I need to wait for load a new version ? How i can understand when it's ready for loading? Thanks, Dario
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Sixx problematic
|
|
Dario,
You can look at the issue that I reported[1] and look at the test results for SIXX on travis[2]. When the issue is closed and tests are green, you should then take a look at the SIXX project on github. Personally I prefer to look at the "network view"[3] to see the status of the project ... a recent commit on the master branch (or whatever branch you may be using) is a clue that a new release has been made ... You can also look at the "commit view"[4] on the master branch, again looking for recent commits ... with this view it is easier to tell what has just happened, i.e., the Issue #3 in commit comment. If I don't happen to have closed the Issue that you are interested in, you can add a comment and ask a question ... I get a read all of my email from github so that is a reliable means of pinging me ... You can subscribe to the SIXX project by clicking on the "Watch" drop down on the SIXX project page ... then you will receive notifications for actions in the project. Under you personal Settings>>Notification Center page, you can control whether or not you want email and/or web notifications ... As it happens I just merged my work into the master branch about 15 minutes ago ... Dale [1] https://github.com/glassdb/SIXX/issues/3 [2] https://travis-ci.org/glassdb/SIXX [3] https://github.com/glassdb/SIXX/network [4] https://github.com/glassdb/SIXX/commits/master On 03/18/2015 12:29 PM, Dario Trussardi
via Glass wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Sixx problematic
|
|
Dale,
(A) i load the SIXX support with: GsDeployer bulkMigrate: [ Metacello new baseline: 'SIXX'; repository: '<a href="github://glassdb/SIXX:master/repository'">github://glassdb/SIXX:master/repository'; load ]. The SixxExamples example2 works fine. After i load:
Now the SixxExamples example2 don't works and open a error. The system now report: ConfigurationOfXMLParser (ConfigurationOfXMLParser-monty.119)
ConfigurationOfXMLSupport (ConfigurationOfXMLSupport-dkh.71)
ConfigurationOfXMLWriter (ConfigurationOfXMLWriter-dkh.23) I think to add: #( 'XMLSupport' '1.2.2' 'http://seaside.gemtalksystems.com/ss/MetacelloRepository'). as first package to load. Can it's a solutions ? How i can lock the SIXX package and relative XML package after load it at the begin (A) ? Thanks, Dario
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Sixx problematic
|
|
Dario,
You can lock a project at any time ... So you might do the following in the beginning of your load script: GsDeployer
bulkMigrate: [
Metacello new
baseline: 'SIXX';
repository: '<a moz-do-not-send="true"
href="github://glassdb/SIXX:master/repository%27">github://glassdb/SIXX:master/repository';
load;
lock. Metacello image configuration: 'XMLSupport'; lock ]. FWIW, the combined GsDevKitHome/tODE release that I've been slaving away at for months ... (documentation is hard for me) will make the management of projects, with respect to where the projects are located (github vs. git clone) and whether or not they are locked, a lot easier with project entries[1] that are very similar to a Metacello load expressions: ^ TDProjectSpecEntryDefinition new baseline: 'Seaside3' repository: 'github://GsDevKit/Seaside31:3.1.?/repository' loads: #('Development' 'Zinc' 'FastCGI' 'Examples' 'Tests'); locked: true; yourself. and are stored on disk so they can be shared between stones[2]. So when you've decided to lock a particular project, you only need to specify that decision in one place and all future loads for "all stones" will use the same locked project. ProjectEntries can be customized on a stone by stone basis, as well ... By default, I am providing a set of default project entries[3] for "all of the projects ported to GemStone" (currently the list is not complete ... but it's already taking long enough to get the release together:)... Dale [1] https://github.com/dalehenrich/tode/blob/dev/docs/releaseNotes/releaseNotes0.1.0.md#project-entries [3] https://github.com/GsDevKit/gsDevKitHome/tree/dev/tode/sys/default/projects On 03/18/2015 01:56 PM, Dario Trussardi
via Glass wrote:
Dale, _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
«
Return to GLASS
|
1 view|%1 views
| Free forum by Nabble | Edit this page |