Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM 6.3.2 package manager file names replaced with random UUID

Avatar

Avatar
Boost 5
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
View profile

Avatar
Boost 5
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
View profile
jonnow
Level 2

19-04-2018

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?

Replies

Avatar

Avatar
Boost 5
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
View profile

Avatar
Boost 5
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
View profile
jonnow
Level 2

25-04-2018

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.

Avatar

Avatar
Level 1
rameshm25791974
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
rameshm25791974
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
rameshm25791974
Level 1

28-11-2018

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.

Avatar

Avatar
Boost 5
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
View profile

Avatar
Boost 5
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
View profile
jonnow
Level 2

28-11-2018

You need to add a name and group to that xml.