By default, the CI-Application property is set to the artefactId and the Name property for a file.Folder is set to the folder name.

If you look at the generated manifest, the Name property will indeed be the name of the folder; that's required by the JAR format specification.

Deployit, however, uses the CI-Name property to determine the name of the deployable when importing the package; you should be able to specify this by the <name>...</name> tag as in your example. See the packaging manual for more information.

Does your manifest contain a section like:

Name: classes

Type: file.Folder

CI-Name: Reference

?

Setting the CI-Application property to a value different from the artifact ID is currently an open feature request. Are you packaging the DAR as part of an EAR or WAR build (i.e. one with <packaging>ear</packaging> or <packaging>war</packaging>) or do you have a separate build for the DAR (<packaging>dar</packaging>).

If you have a separate DAR build, is there anything that would prevent you from setting the artifactId for that build to the CI-Application property that you're trying to use?

This is currently still on the list. Once Deployit 3.9 is released in the coming weeks, we'll be reviewing these kind of improvement requests to make a selection for the next version. Your vote for this feature has been noted! ;-)

Regards

Andrew

XebiaLabs

PS: If this is critical or presenting a significant business challenge to you please indicate that, as it will help us correctly prioritize requests. Thanks!

If you create a separate Maven project (POM) with the packaging dar, you can give that a different name from the name of the jar project. The dar project would have a dependency on the jar project and would package it (along with the file.Folder deployable) into a DAR and optionally import and deploy it.

We would have to create many new POMs for this to work. Moreover, we'd like to deploy artifacts when they are built. Using a different POM, we'd have to build this specific POM to get the artifact deployed. As we're using Jenkins CI server, we'd also have to create new jobs to build these dar POMs.

You'll hopefully be glad to hear that the 3.9.0 release of the plugin should now support an <applicationName> configuration parameter which defaults to the artifact ID but allows you to override the CI-Application manifest attribute.