Maven 1.x Ear Plugin

Deploy error because of display name

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.5
  • Fix Version/s: 1.6
  • Component/s: None
  • Labels:
    None
  • Environment:
    IONA Orbix Application Server Platform, Windows
  • Number of attachments :
    0

Description

The IONA Orbix J2EE server uses the display name as root directory for the exploaded EAR. Unfortunately this contains by default a colon ("${pom.groupId}:${pom.artifactId}") for a generated application.xml which is obviously not an allowed character for files in Windows. This default value should be set to something, that does not break any app server. Proposal: dot

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
dion gillard added a comment -

If we do this, make it a property rather than hard coding a dot.

Show
dion gillard added a comment - If we do this, make it a property rather than hard coding a dot.
Hide
Permalink
Joerg Schaible added a comment -

Well, the display name can be set anyway, but it should work for as many J2EE servers as possible OOTB.

Show
Joerg Schaible added a comment - Well, the display name can be set anyway, but it should work for as many J2EE servers as possible OOTB.
Hide
Permalink
Felipe Leme added a comment -

I agree with Joerg that it should work out-of-the box in the most app servers possible, but I think defining a property for the separator is a n overkill.

So, what about simply using only the artifactId as the display-name?

Show
Felipe Leme added a comment - I agree with Joerg that it should work out-of-the box in the most app servers possible, but I think defining a property for the separator is a n overkill. So, what about simply using only the artifactId as the display-name?
Hide
Permalink
Joerg Schaible added a comment -

Personally I don't care. The artifactId only should rarely conflict with other apps as long as the default for the display name not just breaks the deployment.

Show
Joerg Schaible added a comment - Personally I don't care. The artifactId only should rarely conflict with other apps as long as the default for the display name not just breaks the deployment.
Hide
Permalink
Felipe Leme added a comment -

Fixed - the default value is now ${pom.artifactId}

Show
Felipe Leme added a comment - Fixed - the default value is now ${pom.artifactId}

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.