Maven 2.x Ear Plugin

Add createEarFile property

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.3.2
  • Fix Version/s: None
  • Labels:
    None
  • Patch Submitted:
    Yes
  • Number of attachments :
    2

Description

When directory deploying an ear project often a majority of the time is spent unnecessarily building the ear archive i.e. "Building jar: ...". Since it isn't needed during development it'd be nice if the ear plugin could be configured to stop short of actually building the archive file.

The attahced patch adds a createEarFile property to the EarMojo class to control whether to create the .ear file archive or not.

All changes in this patch are in the EarMojo.java file which is also attached.

  1. Java Source File
    EarMojo.java
    25/Sep/08 5:52 PM
    16 kB
    Kem Elbrader
  2. Text File
    EarMojo.patch
    25/Sep/08 5:52 PM
    3 kB
    Kem Elbrader

Issue Links

is related to

New Feature - A new feature of the product, which has yet to be developed. MEAR-51 Exploded (unpacked) ear

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Kem Elbrader added a comment -

See
http://mail-archives.apache.org/mod_mbox/maven-users/200809.mbox/<e4fe0c450809220941i65f505aal68fa5fdf48e56912@mail.gmail.com>
for mailing list discussion.

Show
Kem Elbrader added a comment - See http://mail-archives.apache.org/mod_mbox/maven-users/200809.mbox/ <e4fe0c450809220941i65f505aal68fa5fdf48e56912@mail.gmail.com> for mailing list discussion.
Hide
Permalink
Kem Elbrader added a comment -

Note: link above must be copied. Jira didn't like me pasting it

Show
Kem Elbrader added a comment - Note: link above must be copied. Jira didn't like me pasting it
Hide
Permalink
Kem Elbrader added a comment -

Something to consider is that when using createEarFile = false the install phase will break. With

[ERROR]The following mojo encountered an error while executing:
[ERROR]Group-Id: org.apache.maven.plugins
[ERROR]Artifact-Id: maven-install-plugin
[ERROR]Version: 2.2
[ERROR]Mojo: install
[ERROR]brought in via: packaging: ear
[ERROR]While building project:
[ERROR]Group-Id:

{groupid}

[ERROR]Artifact-Id:

{artifactid}

[ERROR]Version:

{version}

[ERROR]From file:

{fromfile}

[ERROR]Reason: The packaging for this project did not assign a file to the build artifact

Show
Kem Elbrader added a comment - Something to consider is that when using createEarFile = false the install phase will break. With [ERROR] The following mojo encountered an error while executing: [ERROR] Group-Id: org.apache.maven.plugins [ERROR] Artifact-Id: maven-install-plugin [ERROR] Version: 2.2 [ERROR] Mojo: install [ERROR] brought in via: packaging: ear [ERROR] While building project: [ERROR] Group-Id: {groupid} [ERROR] Artifact-Id: {artifactid} [ERROR] Version: {version} [ERROR] From file: {fromfile} [ERROR] Reason: The packaging for this project did not assign a file to the build artifact
Hide
Permalink
Stéphane Nicoll added a comment -

That's why I am against it. I understand the need but the true answer to your request is to have a separate goal to build the ear and a separate goal to actually build the archive which we don't have for the moment.

Show
Stéphane Nicoll added a comment - That's why I am against it. I understand the need but the true answer to your request is to have a separate goal to build the ear and a separate goal to actually build the archive which we don't have for the moment.
Hide
Permalink
Kem Elbrader added a comment -

Executing a separate goal wouldn't perform the work done by goals in earlier phases e.g. ear:generate-application-xml.

Seems that the standard life cycle will often result in significant and unnecessary work being done. Makes me wonder whether there should be a life cycle devoted to situations where the resulting jar file isn't needed.

Show
Kem Elbrader added a comment - Executing a separate goal wouldn't perform the work done by goals in earlier phases e.g. ear:generate-application-xml. Seems that the standard life cycle will often result in significant and unnecessary work being done. Makes me wonder whether there should be a life cycle devoted to situations where the resulting jar file isn't needed.
Hide
Permalink
Stéphane Nicoll added a comment - - edited

It's called prepare-package. We should consider changing the lifecycle, indeed.

Show
Stéphane Nicoll added a comment - - edited It's called prepare-package. We should consider changing the lifecycle, indeed.

People

  • Assignee:
    Unassigned
    Reporter:
    Kem Elbrader
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: