FEST

Checksum failed for fest-1.0.1.pom

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: FEST-Swing 1.2.1
  • Fix Version/s: None
  • Component/s: General
  • Labels:
    None
  • Number of attachments :
    0

Description

Hey everyone,

I'm trying to use fest-swing-1.2.1 in our project. Maven handles dependencies for us. When building the project, the build fails in consequence of ...

[WARNING] Unable to get resource 'org.easytesting:fest:pom:1.0.1' from repository atlassian-m1-repository (https://m2proxy.atlassian.com/repository/m1/): Checksum failed on download: local = 'b6383e6c6d7291b70f84ccf6f6566d85de27bf99'; remote = '883346b7b848d06c9f3b389da2f16c0502a8c3fb'

Quick look on the fest-1.0.1.pom tells me it contains an xml syntax error.

Thanks,
Marek

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Marek Handl added a comment -

Is there nobody using FEST while using Maven? If there is, how do you do it?

Afaik, the only change that is needed to resolve this issue is to use a newer parent POM. Versions 1.0.1 and 1.0.2 are broken, anything else should do.

Show
Marek Handl added a comment - Is there nobody using FEST while using Maven? If there is, how do you do it? Afaik, the only change that is needed to resolve this issue is to use a newer parent POM. Versions 1.0.1 and 1.0.2 are broken, anything else should do.
Hide
Permalink
Joseph Hirn added a comment -

Yes. Same problem here. Causing major headache. I'm not even sure if you can exclude a parent.

Going to have to upload the jar files independently to our Nexus Repo but this is a glaring oversight to not be addressed by now.

How is anyone using this?

Show
Joseph Hirn added a comment - Yes. Same problem here. Causing major headache. I'm not even sure if you can exclude a parent. Going to have to upload the jar files independently to our Nexus Repo but this is a glaring oversight to not be addressed by now. How is anyone using this?
Hide
Permalink
Fernando Boucquez added a comment - - edited

Hi there, I had the same problem. We are using Ivy, Nexus and the external Maven repositories. I worked-around the problem fixing the POM myself. I downloaded the broken fest 1.0.1 pom.xml, fixed and uploaded it into our Nexus Repo. The dependencies manager (Ivy or Maven) bypassed the broken POM using the fixed one. No need to upload any other fest jar.

This solution may be used for any other broken artefact (POM, JAR, etc.).

Hope it helps.
Cheers
Fer

Show
Fernando Boucquez added a comment - - edited Hi there, I had the same problem. We are using Ivy, Nexus and the external Maven repositories. I worked-around the problem fixing the POM myself. I downloaded the broken fest 1.0.1 pom.xml, fixed and uploaded it into our Nexus Repo. The dependencies manager (Ivy or Maven) bypassed the broken POM using the fixed one. No need to upload any other fest jar. This solution may be used for any other broken artefact (POM, JAR, etc.). Hope it helps. Cheers Fer
Hide
Permalink
Joel Costigliola added a comment -

I'm planning to release, in the next weeks, a fest swing version compatible with fest assertions 1.4, this new version should get rid of this problem.

Regards,

Joel

Show
Joel Costigliola added a comment - I'm planning to release, in the next weeks, a fest swing version compatible with fest assertions 1.4, this new version should get rid of this problem. Regards, Joel

People

  • Assignee:
    Unassigned
    Reporter:
    Marek Handl
Vote (1)
Watch (2)

Dates

  • Created:
    Updated: