We're updating the issue view to help you get more done. 

Different behaviour between no context tag and empty context tag confusing?

Description

This may be considered to be a Maven issue, but it is confusing that there is a difference in behaviour between no context tag and empty context tag.

eg.

when you configure...

<deployable>
<groupId>${pom.groupId}</groupId>
<artifactId>my-webapp</artifactId>
<type>${pom.packaging}</type>
</deployable>

.. the WAR context is null and parseContext will default to he WAR file name (without the file extension)

when you configure...

<deployable>
<groupId>${pom.groupId}</groupId>
<artifactId>my-webapp</artifactId>
<type>${pom.packaging}</type>
<properties>
<context></context>
</properties>
</deployable>

.. the WAR context is set to "" and the webapp will be configured with an empty context.

Possible solutions:

-> make context property required
-> add an extra property to indicate that the deployable should be deployed as default webapp.
0

Status

Assignee

Unassigned

Reporter

Bram de Kruijff

Components

Fix versions

Affects versions

0.3-maven2

Priority

Minor