Sean,
Without looking closely or thinking hard .... the leading cause of a "second load failure" is when you are using a metadataless repository without having defined the "metadataless" project class MetacelloCypressBaselineProject in your baseline with the #projectClass method like the following:
projectClass Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | ^ cl ]. ^ super projectClass
For standard Monticello repositories, packages are not loaded unless the version of the package is later than the version of the currently loaded package ... when using metadataless repositories the version of the package is always 1, so the first load succeeds and subsequent loads do not succeed ...
Dale
--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to metacello+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/metacello/00408dce-9f14-4119-9023-8e193f015aa8n%40googlegroups.com.
the leading cause of a "second load failure" is...
On 11/19/20 9:44 AM, Sean DeNigris wrote:
I can't quite figure out a reproducible case, but sometimes when I do a load script like the following, only the baseline gets loaded and re-running doesn't help.
[ EpMonitor current disable.Metacello newbaseline: 'ComputerWorld';repository: 'github://seandenigris/Computer-World';onConflict: [ :ex |ex projectName = 'XMLParser'ifTrue: [ ex useLoaded ] ];load.EpMonitor current enable
] fork
--You received this message because you are subscribed to the Google Groups "Metacello" group.To unsubscribe from this group and stop receiving emails from it, send an email to metacello+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/metacello/02d984cf-ea6b-4a01-b712-14d98c44c19an%40googlegroups.com.
I'd be inclined to send an explicit message in the ifFalse: case