[GRADLE-2741] maven install: Multiproject references not obeying jar baseName in pom files Created: 09/Apr/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.5
Fix Version/s: None

Type: Bug
Reporter: Tjad Clark Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Known Issue Of:
1.5

 Description   

project structure:

rootProject

  • subProjectA
    build.gradle
  • subProjectB
    build.gradle
    build.gradle
    settings.gradle

When I reference subProjectA from subProjectB as a dependency, i.e
dependencies

{ compile project(':subProjectA') }

and subProjectA has its jar baseName configured i.e
jar

{ baseName = 'some-other-name-for-subProjectA' }

calling gradle install (with the maven plugin enabled), both jars are named correctly and installed correctly with correct artifactIds, however the pom created for subProjectB is incorrect. The pom dependency for subProjectA uses the project name as the artifactId instead of the baseName as the artifactId. i.e the following

subProjectB's pom (dependencies section)
<dependencies>
<dependency>
<artifactId>subProjectA</artifactId>
<groupId>my.group.id</groupId>
<version>1.0</version>
<scope>compile</scope>
</dependency>
</dependencies>

 Comments   
Comment by Tjad Clark [ 09/Apr/13 ]

The expected output for the pom's dependency would be

<dependencies>
  <dependency>
    <artifactId>some-other-name-for-subProjectA</artifactId>
    <groupId>my.group.id</groupId>
    <version>1.0</version>
    <scope>compile</scope>
  </dependency>
</dependencies>

Edit: Sorry for the bad formatting in the description

Comment by Tjad Clark [ 09/Apr/13 ]

This is probably not a bug - possibly more a convenience and improvement.

The below configuration allows me to override the definition for the dependency's artifactId.

uploadArchives {
    repositories {
        mavenDeployer {
            pom.artifactId = 'some-other-name-for-subProjectA'
        }
    }
}

It's still a bit unintuitive that everything is installed as per the jar baseName except the dependency artifactId - i.e in my maven repo, the installed artifact for subProjectA is 'some-other-name-for-subProjectA'.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:30:14 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.