Resource filtering on Release Perform

The double backslashed have been eaten by JIRA. Should read

kerberos.krb5Config=${project.build.outputDirectory}\\krb5.config

kerberos.krb5Config=D\:\\project\\trunk\\module\\target\\classes\\krb5.config

kerberos.krb5Config=D:\project\trunk\target\checkout\module\target\generated-classes\cobertura\\krb5.config

Same problem with version 2.3

I don't see what this has to do with cobertura at all. PLease expand.

The problems is not directly related to Cobertura, but to the resource filtering done (or triggered) by Maven Cobertura Plugin.

To say i differently, it's the conjunction of

• Release Perform + Cobertura + Resource Filtering (from target\checkout\module\src\main\resources to target\checkout\module\target\generated-classes\cobertura)
  which seams to be the source of the problem.
  Removing one of them:
• Release Perform + Resource Filtering (from target\checkout\module\src\main\resources to target\checkout\module\target\classes)
  or
• Cobertura + Resource Filtering (from module\src\main\resources to module\target\generated-classes\cobertura)
  work well.

I have, really, no idea whatsoever how the release plugin could be interacting here, but I'm looking into it. You're sure that you don't have a release profile that is intefering with the situation here?

Gérald,

I'm going to have to ask you to attach a complete test case, or at least a POM.

the cobertura plugin doesn't have any knowledge of the release process. I started to set up a horrendously complex scheme for testing this myself, and before I travel any further down this path I really wonder if you have a parent profile that is messing with your value of escapeWindowsPaths to the resource plugin when running the release, or backing up to an old resources plugin, or something. I recommend looking at -X from maven in the perform run to see if you see any clues.