Stephanie Haith
,
7:26 AM
,
We need to figure out Pour Stop and it placement in the data directory.

Gary Gustafson
,
7:54 AM
,
@Stephanie Haith Are you hoping it will be moved in development folders or just placed for release (which would be reflected by the non-dev binzip)?

Chris Rodgers
,
9:50 AM
,
It's for testing consideration, so it would need to be in the development folder.

Gary Gustafson
,
9:55 AM
,
are there testing problems where it is at?
there are disagreements about where and how externally maintained plugins should be stored

Chris Rodgers
,
9:59 AM
,
Yes, the code isn't available for tests outside of my local machine.
I am using ln magic to spoof SDS2 tests on my local machine.

Gary Gustafson
,
54 mins
,
@Chris Rodgers have the pour stop repos been cleaned out?  (Dan Hare had replicas of .../plugins/??? stuff inside at least one of the pour stop repos)

Chris Rodgers
,
47 mins
,
Yes. I have combined all of the relevant directories into a single repo in my src folder on lucky2 called poursrop
Pourstop
pourstop
Geez...

Gary Gustafson
,
35 mins
,
This is how the problem grows into a mess. Dan Hare had his own thing going on his bitbucket. Dan Axline took those and created submodules under /src/plugins. Now that has morphed into what you have created. Is pourstop for the toolbox? Does it contain more than 1 toolbox item? Will Dan Hare be asked to work on it again? These last questions are probably for @Stephanie Haith to answer.

Stephanie Haith
,
2 mins
,
The member is not licensed. The tool is licensed. The component, my guess would@be licensed. Does that help?
As far as where the installer located these...I would imaging it needs to be Toolbox due to the license?