[tycho-user] Default <Finalname> not working?

[Eric Gwin <eric.gwin@xxxxxxxxxx>]

Hi,

I'm generating a runtime bundle, with features and repository using 0.13.0... basically along the lines of the Tycho Demo. However, in order to get the component bundle to generate with the proper naming convention I have to set finalName.
The demo doesn't, and other examples I find don't seem to (in order to get <artifactID>_<version>.v${timestamp}.jar and <artifactID>.source_<version>.v${timestamp}.jar).

Without <finalName> defined in the parent POM, eclipse shows in the Effective POM (as expected):
<finalName>org.eclipse.persistence.oracleddlparser_1.0.0.v${maven.build.timestamp}</finalName>

yet 'mvn verify' still generates:
[INFO] --- tycho-source-plugin:0.13.0:plugin-source (plugin-source) @ org.eclipse.persistence.oracleddlparser ---
[INFO] Building jar: D:\__git_repositories\oracleddlparser\oracleddlparser\target\org.eclipse.persistence.oracleddlparser-1.0.0-SNAPSHOT-sources.jar
[INFO]
[INFO] --- tycho-packaging-plugin:0.13.0:package-plugin (default-package-plugin) @ org.eclipse.persistence.oracleddlparser ---
[INFO] Building jar: D:\__git_repositories\oracleddlparser\oracleddlparser\target\org.eclipse.persistence.oracleddlparser-1.0.0-SNAPSHOT.jar
[INFO] META-INF already added, skipping

A side-effect of setting the <Final name> seems to be that the source bundle generates as:
[INFO] --- tycho-source-plugin:0.13.0:plugin-source (plugin-source) @ org.eclipse.persistence.oracleddlparser ---
[INFO] Building jar: D:\__git_repositories\oracleddlparser\oracleddlparser\target\org.eclipse.persistence.oracleddlparser_1.0.0.v201201110821-sources.jar

unless I also setup a configuration in tycho-source-plugin specifying otherwise. Even then source generates as:
[INFO] --- tycho-source-plugin:0.13.0:plugin-source (plugin-source) @ org.eclipse.persistence.oracleddlparser ---
[INFO] Building jar: D:\__git_repositories\oracleddlparser\oracleddlparser\target\org.eclipse.persistence.oracleddlparser.source_1.0.0.v201201110825-sources.jar

I'm wondering if this is a known issue, or a known side-effect of something.. (defining <forceContextQualifier> maybe?)

Thanks.

-Eric