Re: [Pharo-users] Loading Seaside and Magritte in Pharo8 - baseline load conflicts

[Sebastijan Kaplar]

Thanks everyone, I guess I’ll go with it. 
However, I can say #onConflict or #onConflictUseIncoming when loading the 
project, 

eg. 

Metacello new
 baseline: #NewWave;
 repository: 'github://skaplar/NewWave:development 
';
 onConflictUseIncoming;
 load.

I’m interested to know can I do something like that in my baseline 
configuration, so that the build does not fail?

Sebastijan 



> On Apr 15, 2020, at 08:57, Johan Brichau  wrote:
> 
> 
> 
>> On 14 Apr 2020, at 11:35, Sven Van Caekenberghe  wrote:
>> 
>> Hi,
>> 
>>> On 14 Apr 2020, at 11:23, Sebastijan Kaplar  wrote:
>>> 
>>> MetacelloConflictingProjectError: Load Conflict between existing 
>>> BaselineOfGrease [baseline] from 
>>> github://SeasideSt/Grease:v1.4.x/repository and BaselineOfGrease [baseline] 
>>> from github://SeasideSt/Grease:v1.4.3/repository
>> 
>> Yes I have seen that also before in other situations, and it is super 
>> annoying.
>> 
>> Apparently, v1.4.x and v1.4.3 are considered different/conflicting.
> 
> Yes, because Metacello does not recognise this naming convention. 
> Instead, Metacello has/had the question mark as a notation (e.g. v1.4.?) to 
> allow this but it also means that it will try to detect the latest version 
> which was blowing up the GitHub rate api and thus it became unusable :(
> 
> There is a need to fix package versioning and dependencies, but I am not 
> following enough to know if there are efforts going on to improve package 
> management.
> 
>> I don't know if this is a bug or by design.
> 
> By design because it considers these versions different since it does not 
> know about the naming convention.
> 
>> I believe you can solve this with #onConflict directives on the Metacello 
>> class, but this also feels like a hack.
> 
> Yes, you should solve them yourself.
> 
> Johan

[Pharo-users] Loading Seaside and Magritte in Pharo8 - baseline load conflicts

[Sebastijan Kaplar]

Hello everyone,

so I can’t resolve the problem in my project, which emerged when something 
happened in one of those repositories (it was working fine previously). 
When I try to load the project using metacello 

Metacello new
baseline: #NewWave;
repository: 'github://skaplar/NewWave:development';
load.

I get 

MetacelloConflictingProjectError: Load Conflict between existing 
BaselineOfGrease [baseline] from github://SeasideSt/Grease:v1.4.x/repository 
and BaselineOfGrease [baseline] from 
github://SeasideSt/Grease:v1.4.3/repository 

More info here (https://travis-ci.org/github/skaplar/NewWave/jobs/671515073 
)

My baseline looks something like this:

…Seaside

seaside: spec
spec 
baseline: 'Seaside3'
with: [ 
spec repository: 
'github://SeasideSt/Seaside:master/repository'
 ]

…Magrite

magritte: spec
spec 
baseline: 'Magritte'
with: [ 
spec 
loads: #( Seaside );
repository: 
'github://magritte-metamodel/magritte:v3.6’ ]

If someone cares for a deeper look 
(https://github.com/skaplar/NewWave/tree/development/BaselineOfNewWave 
)

Any help would be appreciated!

Thanks,
Sebastijan

Re: [Pharo-users] NewWave - WorkflowEngine

[Sebastijan Kaplar]

Hello as Norbert I'm also interested. To provide a little more context I'm 
working on a NewWave as a part of my PhD. The new and interesting side that is 
supported is that the NewWave integrates with TaskIT for tasks executions, with 
now added support for boundary events and task scheduling. I haven't used 
Workflow from NetStyle, but as I can tell from the GitHub only part of the 
engine remains, without any examples or user interfaces, and it didn't support 
mentioned? Is there any chance that the original netstyle workflow is to be 
found and checked out?

Best regards,
Sebastijan


From: Pharo-users  on behalf of Norbert 
Hartl 
Sent: Friday, April 19, 2019 7:14 PM
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] NewWave - WorkflowEngine

I think you should flood the mailing list. I‘m interested, too

Am 19.04.2019 um 18:40 schrieb Smalltalk 
mailto:smallt...@adinet.com.uy>>:


Serge,

Yes, we can work together.

Send me a private mail so we do not flood the Pharo list.

Tell me what you have in mind...

regards,

bruno

El 19/04/2019 a las 9:55, Serge Stinckwich escribió:


On Wed, Apr 17, 2019 at 4:32 PM BrunoBB 
mailto:smallt...@adinet.com.uy>> wrote:
Hi Sebastijan,

Excellent work !!!

I have something similar (a BPM engine) but developed with GemStone
Smalltalk:
Code:
https://github.com/brunobuzzi/BpmFlow
Documentation:
https://bpmflow.gitbook.io/project/introduction

It can be ported to Pharo, from the top of my head i see a couple of issues
with the port:
- GemStone/S special indexes collection must be changed for regular Pharo
collections.
- GsQuery should be implemented in Pharo (maybe already is i do not know) or
remove GsQuery references and so regular collection queries (select:,
collect: anySatisfy and so on)

The project is totally open source.



There is also the BPMN engine that we build with Alvaro Peralta:
https://github.com/A4BP
Maybe we can work together ?

Regards,
--
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroun
"Programs must be written for people to read, and only incidentally for 
machines to execute."
https://twitter.com/SergeStinckwich

[Pharo-users] NewWave - WorkflowEngine

[Sebastijan Kaplar]

Hello everyone,

we've been working on a workflow engine written in Pharo. You can check it out 
at: https://github.com/skaplar/NewWave
It is still in the early development and we discussed about making it public so 
everyone interested can join, take a look or provide any kind of feedback. I'm 
also at discord so you can contact me @skaplar.

Best regards,
Sebastijan Kaplar