[vwnc] VisualWorks Base bundle not in order?

The instructions to publish the VW Base into Store doesn't seem to
anticipate the trouble that may occur when publishing it--it's out of
order.  Even validating the bundle specifications pours warnings onto
the screen.

What would be really cool is if there were a tool to rearrange the
bundles so they could be properly published.

Has anyone else published Base Visualworks successfully?

--
Visit <http://tggagne.blogspot.com/> for more great reading.

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Thomas Gagné wrote: I tried a few times and gave up -- we now publish our own code and any
modifications to base classes.

--
Dennis Smith                         +1 416.798.7948
Cherniak Software Development Corporation   Fax: +1 416.798.0948
509-2001 Sheppard Avenue East        [hidden email]
Toronto, ON M2J 4Z8              sip:[hidden email]
Canada         http://www.CherniakSoftware.com
Entrance off Yorkland Blvd south of Sheppard Ave east of the DVP

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

> > Has anyone else published Base Visualworks successfully?
> >
> I tried a few times and gave up -- we now publish our own code and any
> modifications to base classes.

We do the same. It would be great if VisualWorks was improved in this area.

Runar
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Dennis Smith schrieb:
unfortunately, when not publishing Base VisualWorks, its packages will
always be shown as modified, so it's impossible to notice if a base
class/method has been (accidentally) modified.
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

In past versions I have published base VW. I don't recall
having problems doing so. However, I may not have done
bundle validation, but I don't see that as an issue because
you never load it into an empty image.

Terry
 
===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

After being warned the bundle is out of order, the next error I get is:

System-Name Spaces contains values in Undeclared.  Please correct before
publishing.

This is with a fresh vwnc 7.6 (after loading StoreForMySQL).

--
Visit <http://tggagne.blogspot.com/> for more great reading.

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

I don't know about checking with Validate, but you have to at least check by reconciling the published base with a second, clean visual.im. That's the only way of knowing that your publish worked properly (or more precisely, that the Store bugs and mistakes in base package ordering, overrides, prereqs etc. didn't affect things visibly this time). In the past there have been significant problems, mostly with the integration of PDP (sorry Terry, it just happened to be that way). By reconciling I've been able to correct them (where Store has just messed up), or at least pass the information on to Cincom. Things seemed to be mostly better by 7.4.1, so it's a shame if they're slipping back now.

For us, having the base under version control, along with other Cincom packages we deliver as part of our product, is a fundamental requirement. I suppose if all I wanted to see was whether I've made a change to a base package, I could just hack the pundle info in the image to make it believe it is published. That wouldn't solve the question of _what_ I'd changed - you can't trust the change sets 100% - nor does it help you see what has changed between VW versions. Even if the new VW version contains zero bugs, a change can certainly mess up something my overrides, extensions or even normal code was expecting.

Steve

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

>> The instructions to publish the VW Base into Store doesn't seem to
>> anticipate the trouble that may occur when publishing it--it's out of
>> order.  Even validating the bundle specifications pours warnings onto
>> the screen.
>>

>> Has anyone else published Base Visualworks successfully?
>>

The Base VisualWorks bundle was never intended to be consistent wrt.  
load order and probably never will be.

This is a case of 'using Packages as categories'. However fixing that  
would imply that most of the base will need to be moved into a single  
package, I'm sure we wouldn't appreciate that happening that either.


So click through all those dialogs and publish base as you would  
usually do.


> I tried a few times and gave up -- we now publish our own code and any
> modifications to base classes.


Does that mean you want to create your own versions of Base VW?
If so: don't do that. The preferred (and supported!) way to publish  
alterations to base is to create separate patch packages and load  
those over the base (making use of overrides where needed). I'm pretty  
sure this is mentioned in the documentation somewhere but I'm too lazy  
to look it up for you now ;-)
Of course you can gather your patches packages into a single bundle  
and publish that (without those annoying dialogs popping up).


Theoretically you should be able to gather the base bundle and your  
patches bundle together in a single bundle too (since VW 7.6 now  
supports bundles with intra-bundle overrides), unfortunately publish-
time validation fails on such bundles so you keep getting those  
dialogs. This has been reported to WV-dev after code-freeze of 7.6 so  
unfortunately it is broken in this release.



>>
>> What would be really cool is if there were a tool to rearrange the
>> bundles so they could be properly published.
>



Sure, but I higher priority for me would be have a 'publish base and  
all parcels' tool supplied with VW. Such a tool should work around the  
validation problem of the base bundle and manage other peculiarities  
too (like not being able to publish Boss unless some other parcels are  
loaded).




HTH,

Reinout
-------


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Thomas Gagné wrote:
> After being warned the bundle is out of order, the next error I get is:
>
> System-Name Spaces contains values in Undeclared.  Please correct before
> publishing.
>
> This is with a fresh vwnc 7.6 (after loading StoreForMySQL).
>  
OK.  It wasn't /that/ fresh.  To publish it I had to load a pre-release
StoreForMySQL parcel that had an undeclared.  After fixing that things
seem to be publishing fine into MySQL.

--
Visit <http://tggagne.blogspot.com/> for more great reading.

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Reinout Heeck wrote:

The instructions to publish the VW Base into Store doesn't seem to
anticipate the trouble that may occur when publishing it--it's out of
order.  Even validating the bundle specifications pours warnings onto
the screen.

      

Has anyone else published Base Visualworks successfully?

      

The Base VisualWorks bundle was never intended to be consistent wrt.  
load order and probably never will be.

This is a case of 'using Packages as categories'. However fixing that  
would imply that most of the base will need to be moved into a single  
package, I'm sure we wouldn't appreciate that happening that either.


So click through all those dialogs and publish base as you would  
usually do.


  

I tried a few times and gave up -- we now publish our own code and any
modifications to base classes.
    

Does that mean you want to create your own versions of Base VW?
  

No -- just have a package which contains our modifications to base classes and we load that
prior to loading our own code (in a new image).

If so: don't do that. The preferred (and supported!) way to publish  
alterations to base is to create separate patch packages and load  
those over the base (making use of overrides where needed). I'm pretty  
sure this is mentioned in the documentation somewhere but I'm too lazy  
to look it up for you now ;-)
Of course you can gather your patches packages into a single bundle  
and publish that (without those annoying dialogs popping up).


Theoretically you should be able to gather the base bundle and your  
patches bundle together in a single bundle too (since VW 7.6 now  
supports bundles with intra-bundle overrides), unfortunately publish- 
time validation fails on such bundles so you keep getting those  
dialogs. This has been reported to WV-dev after code-freeze of 7.6 so  
unfortunately it is broken in this release.



  

What would be really cool is if there were a tool to rearrange the
bundles so they could be properly published.
      

Sure, but I higher priority for me would be have a 'publish base and  
all parcels' tool supplied with VW. Such a tool should work around the  
validation problem of the base bundle and manage other peculiarities  
too (like not being able to publish Boss unless some other parcels are  
loaded).




HTH,

Reinout
-------


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
  

-- 
Dennis Smith                 		         +1 416.798.7948
Cherniak Software Development Corporation   Fax: +1 416.798.0948
509-2001 Sheppard Avenue East        [hidden email]
Toronto, ON M2J 4Z8              <a class="moz-txt-link-freetext" href="sip:dennis@CherniakSoftware.com">sip:dennis@...
Canada			         http://www.CherniakSoftware.com
Entrance off Yorkland Blvd south of Sheppard Ave east of the DVP

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc