Since updating to 6.3.2, newly uploaded packages are given a random name and path such as "pack_9596c422-dbeb-4ae3-8d41-69cf96181ef6.zip" rather than using the file name of the zip file. Very easy to reproduce: just go into package manager and upload a package.
We use a lot of curl scripts to manage and replicate packages and needless to say, they are all broken.
Is this a bug? Is there a workaround?
Views
Replies
Total Likes
Resolved: It seems there was an undocumented change in 6.3.2 where if a package name and group are not defined in the vault/properties.xml, it will give the package a random name and path.
Views
Replies
Total Likes
We have updated to 6.3.3 and we still are seeing the same issue. Is it really resolved?
If not, Any suggestions on how to update the vault/properties.xml as we are seeing this issue with only one of the artifacts being deployed.
Views
Replies
Total Likes
You need to add a name and group to that xml.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies