filetree icon indicating copy to clipboard operation
filetree copied to clipboard

Monticello repository for directory-based Monticello packages enabling the use of git, svn, etc. for managing Smalltalk source code.

Results 49 filetree issues
Sort by recently updated
recently updated
newest added

The code of the parser looks almost exactly the same as the one of NeoJSON. (copy of [issue 16875 on FogBugz](https://pharo.fogbugz.com/f/cases/16875/Let-Monticello-FileTree-use-NeoJSON))

``` Validation Report: 15456 Load latest version of metacello Failure 8 Errors 9 Warnings Validation Setup Image Version 50212 OS Version an UnixPlatform VM Version NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr...

This seems related to #62, and definitely to CampSmalltalk/Cypress#18 FileTree expects method files to look like ``` category selector: arg and: arg ^ body ``` But STIG starts the file...

Monticello files have a dependency mechanism and there appears to be code in FileTree that is supposed to preserve package dependencies, but I don't believe that I have a test...

See [this page](http://apple.stackexchange.com/questions/14980/why-are-dot-underscore-files-created-and-how-can-i-avoid-them) for Apples excuse:) and [this message](http://forum.world.st/Glass-Metacello-support-tp4786297p4789521.html) for the diagnosis. Here's a proposed bugfix for MCFileTreeStCypressReader>>addMethodDefinitionsForClass:methodProperties:in:: ``` Smalltalk ((self fileUtils directoryFromEntry: entry) entries select: [ :each | each...

You cannot save a method with length > 255 to filetree, because NTFS limits file name length to 255. Example method from Monticello: ![image](https://cloud.githubusercontent.com/assets/4451364/3317293/98e82d14-f70b-11e3-9398-ffcab353c70c.png) Error: ![image](https://cloud.githubusercontent.com/assets/4451364/3317297/a4cf6ad4-f70b-11e3-9e8a-d2d8f3b2263b.png)

Trying to backport issue #124 in the pharo2_dev branch. Will try a merge by Monticello :)

When reading a package, gitfiletree skips monticello.meta/version and methodProperties.json, so those files could be removed (and then we would get rid of git merge conflicts !). However FileTree is not...

enhancement

After a git merge, some `.class` and `.extension` can be left without their required contents (like the properties.ston file in a `.extension` dir) and FileTree chokes on attempting to process...

For each package in a file tree repo, from the image perspective, only the current commit is shown. Ideally, it would show all the versions in the repo, just like...