Smalltalk › Frameworks & Tools › Monticello, Metacello ... › Metacello

release 1.0.0-beta.32.16

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 3 messages Options
Dale Henrichs-3
Reply | Threaded
Open this post in threaded view
♦
♦
|

release 1.0.0-beta.32.16

Dale Henrichs-3
Pull request #304 marks the release of 1.0.0-beta.32.16[2] with the following bugfixes:

 - Issue #302: package-cache is probably source of some test failures
 - Issue #298: Builds on Pharo2.0 are failing in MetacelloPharo20Platform>>downloadFile:to:
 - Issue #296: no toolbox validation for BaselineOf?
 - Issue #295: Should be able to use Group in `includes:` or `requires:`
 - Issue #294: `get` should honor `cacheRepository:`
 - Issue #292: 'ALL' and `import:` do not play well together
 - Issue #290: `onConflictUseIncoming:useLoaded:` or something similar as helper methods for conflict handling (and perhaps updgrade/downgrade, etc. handling)
 - Issue #286: random failures for MetacelloGithubIssue175TestCase>>testIssue175 Squeak4.5 and Squeak Trunk
 - Issue #283: Symbolic versions might need to force reload of Configuration ....
 - Issue #280: MetacelloMCProjectSpec>>hasConflictWithProjectSpec: needs to double dispatch
 - Issue #278: Metacello should no longer depend upon GsCore and GsMonticello
 - Issue #277: wild card characters supported in version field of github:: URL
 - Issue #241: rewrite getting started docs - clarify role of `lock` command
 - Issue #236: Clarify platform default repository locations
 - Issue #230: command chaining
 - Issue #200: default configuration repositories exist for Pharo/Pharo2.0/Pharo3.0
 - Issue #196: test validation of MetacelloScriptingAPI examples

I want to highlight some of the new features:

 - shortCuts for onUpdate*, onDowngrade*, onConflict*[4], onLock*[5] and onWarning*[6].
 - use names of groups in includes: and requires: clauses[7]. Prior to this bugfix, group names
   were silently ignored. A side effect of ignoring names is that is was possible to use a name
   that was not defined in a requires: or includes: ... Now a resumable error is thrown. See this
   comment[8] if you hit a MetacelloNameNotDefinedError...
 - you may use wildcard characters in github (or bitbucket) repository url[9]. The wildcard
   matching is applied to the list of tags associated with a repository. You may use
   *, # and ? but the most useful is ? which allows you to form a github repo url that looks like
   the following:

      github://GsDevKit/Seaside31:v3.?/repository

   and is equivalent to a #release3 symbolic version for Seaside. The following url:

      github://GsDevKit/Seaside31:v3.1.?/repository

   is equivalent to a #release3.1 symbolic version for Seaside. The leading v character is optional
   on tag names.
 - command chaining[10] means that you can use cascades for actions in addition to options
   and write commands like the following:

    Metacello new
      configuration: 'Seaside3';
      repository: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
      get;
      load

The Metacello User Guide[11] was also updated ...

See the installation instructions[12] if you want to start using the new features or pick up the bugfixes.

Dale

[1] https://github.com/dalehenrich/metacello-work/pull/304
[2] https://github.com/dalehenrich/metacello-work/releases/tag/1.0.0-beta.32.16
[3] https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUserGuide.md
[4] https://github.com/dalehenrich/metacello-work/issues/290#issuecomment-58722043
[5] https://github.com/dalehenrich/metacello-work/issues/290#issuecomment-58918880
[6] https://github.com/dalehenrich/metacello-work/issues/194
[7] https://github.com/dalehenrich/metacello-work/issues/295
[8] https://github.com/dalehenrich/metacello-work/issues/295#issuecomment-59590800
[9] https://github.com/dalehenrich/metacello-work/issues/277
[10] https://github.com/dalehenrich/metacello-work/issues/230
[11] https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUserGuide.md
[12] https://github.com/dalehenrich/metacello-work#install-preview-version

--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Johan Brichau-3
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: release 1.0.0-beta.32.16

Johan Brichau-3

On 21 Oct 2014, at 02:44, Dale Henrichs <[hidden email]> wrote:

>  - Issue #277: wild card characters supported in version field of github:: URL

Hurray!
Let's test semantic versioning for the github repos :)

thx Dale!
Johan

--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Dale Henrichs-3
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: release 1.0.0-beta.32.16

Dale Henrichs-3
Haha, I knew you'd be happy:)

On Tue, Oct 21, 2014 at 7:40 AM, Johan Brichau <[hidden email]> wrote:

On 21 Oct 2014, at 02:44, Dale Henrichs <[hidden email]> wrote:

>  - Issue #277: wild card characters supported in version field of github:: URL

Hurray!
Let's test semantic versioning for the github repos :)

thx Dale!
Johan

--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Free forum by Nabble Edit this page