Hi Reudiger
Interesting, thanks for the link. So it looks like the key might be to make
sure the sources jar is uploaded to the ivy repository as an artifact
type='source'. Sadly I don't have control of this as in TeamCity the gradle
build finishes at the point where all the artifacts have been created. The
mapping then to it's internal ivy representation is done with artifact path
mapping. E.g. on a project you set "build/libs/MessagingCommon-*.jar=>./" So
there isn't actually a gradle task for uploading archives where I'd set the
artifact type as far as I can tell.
So in the end the teamcity-ivy.xml that it generates looks like this, which
is where the problem presumably lies:
<ivy-module version="1.4">
<info organisation="org" module="bt544" revision="91951"/>
<publications>
<artifact name="MessagingCommon-91951-sources" type="jar"
ext="jar"/>
<artifact name="MessagingCommon-91951" type="jar" ext="jar"/>
</publications>
</ivy-module>
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Attaching-source-jar-with-eclipse-plugin-tp5490090p5492379.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
