Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,393
Community Members
 
Community Events
176
Community Groups

How could we analyze this problem with the Maven Dependencies Processor?

Hello,

some weeks ago we've updated to Bamboo 8.1.1

It looks like since then we're getting a problem with the Maven Dependencies Processor after a successful build Task.

The Maven Dependencies Processor task throws the problem

simple	19-Jan-2022 09:33:38	Starting task 'Automatic Dependencies' of type 'com.atlassian.bamboo.plugins.maven:task.mvn.dependencies.processor'
error	19-Jan-2022 09:33:38	Automatic Maven plan dependencies processing failed: org.apache.maven.settings.building.SettingsBuildingException: 1 problem was encountered while building the effective settings[ERROR] Failed to interpolate settings: UTF-8 BOM plus xml decl of ISO-8859-1 is incompatible (position: START_DOCUMENT seen <?xml version="1.0" encoding="ISO-8859-1"... @1:41)  @ line 1, column 41
simple	19-Jan-2022 09:33:38	Finished task 'Automatic Dependencies' with result: Failed

We've checked a bunch of POM files including settings.xml but could not find an UTF-8 BOM file so far.

Maybe another XML file is the problem, but since the message does not show the name of the file - how can we find it?

Regards,
Gunnar

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events