Re: [mojo-dev] verify.groovy going insane?

[Jörg Hohwiller]

Hi there,

unfortunately there seems to be no other idea and I am lost with this.



Cheers
  Jörg

Am 04.09.2014 22:24, schrieb Jörg Hohwiller:

As the result of the Mojo is correct and only groovy is nuts here, I would tend to comment out the assertion so we can go for the next release.

Hi Robert,




roject.repositories.repository.id)
                |      |               |            |          |
                false  |               |            | no-one
                       |               | no-onehttp://localhost:54391

                       | no-onehttp://localhost:54391
4.0.0org.codehaus.mojo.flatten.itsexternal-parent0.0.1-SN

thanks for the hint. I always thought that the nice this about groovy is that a == b is the same as a null-safe a.equals(b). If I got it corrently what you are telling then it seems not to make any difference: [INFO] The post-build script did not succeed. assert 'no-one'.equals(flattendP APSHOTApache License, Version 2.0http://www.apache.org/licenses/LICENSE-2.0org.s

pringframeworkspring-core4.0.5.RELEASEcompileno-onehttp://localhost:54391



Cheers
  Jörg

I also copied the no-one string from the resulting .flattened-pom.xml in case it only looks like ascii but contains some wild unicode character. So I am loosing my sanity here...

smime.p7s
Description: S/MIME Cryptographic Signature