[GRADLE-2511] Generated POM does not include dependencies if POM is customized before applying Java plugin Created: 08/Oct/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

As per subject says,

build.gradle contains the following declarations
@@@
dependencies {
compile 'com.adobe.blazeds:blazeds-common:4.0.0.14931'
compile 'com.adobe.blazeds:blazeds-core:4.0.0.14931'
testCompile 'junit:junit:4.9'
}
uploadArchives {
repositories {
mavenDeployer {
repository( url: "someURL" ) {
}

pom.project

{ // ... Custom declarations on developers etcs }

}
}
}
}
@@@

Expected result:

  • When @@@gradle upload@@@ is invoked, the expected behavior is to have both my custom declarations (developers, licenses, etcs) and project dependencies to be included in the uploaded pom.xml

Current result:

  • Custom declarations are included, but the project dependencies are not included

Do note that when pom.project declaration is removed, the project dependencies are included in the uploaded pom.xml.

 Comments   
Comment by Gradle Forums [ 08/Oct/12 ]

Usually this works just fine. Can you provide a fully self-contained example that demonstrates the problem? Please use HTML code tags when pasting code. Also please paste the output of `gradle -v`.

Comment by Gradle Forums [ 08/Oct/12 ]

The simplest project can be downloaded from here
[1]https://docs.google.com/open?id=0BwZ5...

$ gradle upload -v

------------------------------------------------------------
Gradle 1.2
------------------------------------------------------------

Gradle build time: Wednesday, September 12, 2012 10:46:02 AM UTC
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.8.4 compiled on May 22 2012
Ivy: 2.2.0
JVM: 1.6.0_32 (Sun Microsystems Inc. 20.7-b02)
OS: Windows 7 6.1 amd64
----------------------------------------------------------------------------------------
[1] https://docs.google.com/open?id=0BwZ5wsZTtnH4SnRJcC14bWpDa2c

Comment by Gradle Forums [ 08/Oct/12 ]

Hi Peter,

Did you manage to reproduce the error in your environment?

Comment by Gradle Forums [ 08/Oct/12 ]

The problem occurs if the POM is customized before the `java` plugin has been applied. I've created a JIRA for this. In the meantime, make sure to first apply the plugin.

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:23:57 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.