Reusable Assets Registration new version / overwrite version

[PeterHeintz]

When first started with reusable assets, it was ok for me to overwrite the old version.

After the assets got more mature I managed to hold different versions of an asset within the same storage. But now I have overwritten an old version by mistake, and by that I realized that it is not really clear to me what I have to do to over right a version and how to create a new version.

I have done both already but honestly I have no glue how.

[PeterHeintz]

I would appreciate any feedback from Sparx about this.

[PeterHeintz]

Now I am able to answer this myself.
What I use as assets are several packages I hold in subversion. Before I publish those assets to the asset server I check those packages out somewhere in an EAP file. What I published to the asset service was the package containing the packages from subversion. Several times I build the “package containers” from scratch but with the same name what caused the package (package name) to be shown with different versions in the “Registry Browser”.
This I thought, is the intended behavior to show package versions.
But it is not. A package and its version are shown as one row only, and the version you can select in the version selection field.

I just came to another assumption just because I created the “container packages” often from scratch (->new guid->other package with same name).