Maven 2.x Ear Plugin

Support new 'no-version-for-ejb' file name mapping

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.7
  • Fix Version/s: 2.8
  • Labels:
    None
  • Testcase included:
    yes
  • Patch Submitted:
    Yes
  • Number of attachments :
    1

Description

JBoss 7 has a new remote lookup naming stragety. The name of the ejb-jar is not part of remote name. If that includes the version this is obviously going to cause problems. Using 'no-version' would fix this but I would like to keep version of the library jars as a quick way of verifying the ears contents. What this name mapping does is essentially 'no-version' for ejb-jars, 'standard' for library jars.

Activity

Ascending order - Click to sort in descending order
Stéphane Nicoll made changes -
Field Original Value New Value
Fix Version/s 2.8 [ 18269 ]
Hide
Permalink
Stéphane Nicoll added a comment -

thanks for the patch!

Show
Stéphane Nicoll added a comment - thanks for the patch!
Stéphane Nicoll made changes -
Assignee Stéphane Nicoll [ sni ]
Stéphane Nicoll made changes -
Status Open [ 1 ] In Progress [ 3 ]
Stéphane Nicoll made changes -
Summary [patch] support new 'no-version-for-ejbs' file name mapping Support new 'no-version-for-ejb' file name mapping
Hide
Permalink
Stéphane Nicoll added a comment -

Applied, thanks. I used 'no-version-for-ejb' for the name to be consistent.

Also deployed a 2.8-SNAPSHOT with the change.

Show
Stéphane Nicoll added a comment - Applied, thanks. I used 'no-version-for-ejb' for the name to be consistent. Also deployed a 2.8-SNAPSHOT with the change.
Stéphane Nicoll made changes -
Status In Progress [ 3 ] Closed [ 6 ]
Resolution Fixed [ 1 ]

People

  • Assignee:
    Stéphane Nicoll
    Reporter:
    Philippe Marschall
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: