Maven creates jar for a project without java sources

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: 2.1
  • Component/s: None
  • Labels:
    None

Description

A jar file is generated even for projects with no java sources (ie: no src/main/java directory) - this creates some problems with the current assembly implementation, since an horrible near-empty jar gets into the assembly.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MJAR-105 Regression: Build fails for an empty main jar with 2.2

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

that's not a bug. It's valid to have a jar with no sources (eg, just resources).

IT does print a warning

Show
Brett Porter added a comment - that's not a bug. It's valid to have a jar with no sources (eg, just resources). IT does print a warning
Hide
Permalink
Giorgio Gallo added a comment -

I'm very sorry to insist...

I didn't explained well: a jar file is generated even if there are no sources or resources in the project.

Show
Giorgio Gallo added a comment - I'm very sorry to insist... I didn't explained well: a jar file is generated even if there are no sources or resources in the project.
Hide
Permalink
Giorgio Gallo added a comment -

Attached a .zip containing a maven project wich should not (IMHO) generate any jar

Show
Giorgio Gallo added a comment - Attached a .zip containing a maven project wich should not (IMHO) generate any jar
Hide
Permalink
Brett Porter added a comment -

it doesn't matter.

If you don't want to produce a jar, set the packaging to something other than JAR (which is the default). For example: "pom".

I'm not sure what type of project you have that doesn't produce anything?

Show
Brett Porter added a comment - it doesn't matter. If you don't want to produce a jar, set the packaging to something other than JAR (which is the default). For example: "pom". I'm not sure what type of project you have that doesn't produce anything?
Hide
Permalink
Giorgio Gallo added a comment -

I have a general-purpose project to create patches for Saba LMS (http://saba.com) and theese patches may or may not consist of a few classes and a bunch on cocoon xml files which are to be run by a saba-provided utility to be merged into the main .ear.

I created a custom assembly to pakage the patch contents into a jar following saba patch expected format and wished I could use the same assembly descriptor whether or not the patch has classes. (Also, I don't like m2 to put unsolicited information in META-INF)

No problem anyway - i will just stick to ant

Thank you for the great job developing m2!

Show
Giorgio Gallo added a comment - I have a general-purpose project to create patches for Saba LMS (http://saba.com) and theese patches may or may not consist of a few classes and a bunch on cocoon xml files which are to be run by a saba-provided utility to be merged into the main .ear. I created a custom assembly to pakage the patch contents into a jar following saba patch expected format and wished I could use the same assembly descriptor whether or not the patch has classes. (Also, I don't like m2 to put unsolicited information in META-INF) No problem anyway - i will just stick to ant Thank you for the great job developing m2!

People

  • Assignee:
    Brett Porter
    Reporter:
    Giorgio Gallo
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: