Skip to content

Conversation

@cstamas
Copy link
Member

@cstamas cstamas commented Jun 4, 2024

The least we can do: check is "language" of current project packaging is "java" or not (all jar-like outputs are using language="java", only pom and bom packaging uses language="none"), and emit a WARN to user to reconsider.

The least we can do is compare two language: one of known 'pom'
type and other of project artifact: if both equal, and jar
plugin is "aware" it creates JAR that is "java" language,
emit a warning.
@cstamas

This comment was marked as outdated.

.getArtifactHandler(getProject().getPackaging())
.getLanguage())) {
getLog().warn(
"The project packaging language is NOT 'java'; this is most probably not what you want");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think to add a packaging name ... like:
The project packaging <packaging> language ...

@michael-o
Copy link
Member

Groovy, Kotlin?

@slawekjaranowski
Copy link
Member

Groovy, Kotlin?

Do Groovy or Kotlin use a custom packaging?

@michael-o
Copy link
Member

Groovy, Kotlin?

Do Groovy or Kotlin use a custom packaging?

I have no clue, was just hinting whether the restricition is complete.

@slawekjaranowski
Copy link
Member

ok, m-jar-p is not the best place to check it ... the same will be with:

 mvn -N ejb:ejb install:install  

Copy link
Member

@slawekjaranowski slawekjaranowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.

@michael-o michael-o removed their request for review November 20, 2024 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants