Again sorry for the late reply... 2009/2/6 Matthew Fudge <[email protected]>
> Hi Levi, > > Thanks for answering (Even though I managed to post in entirely the wrong > thread (thank you Lotus Notes :( ). However I think I was unclear about my > question. The > problem is not the actual name of the jar but the "module" element of the > upload path that is produced. > > I have > // organization > group="com.sita.ats-core" > archivesBaseName="ats-core" > > in my build.gradle and this does cause the correctly named jar file to be > produced. However when this is uploaded to maven or ivy repositories using > an artifact pattern > of: > artifactPatterns = > [ > "artifact-repository/[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" > ] > > the module name comes out as: > com.sita.ats-core/ats_core/3.50/jars/ats-core.jar > in the repository (note the underscore for the module name) This looks like a bug to me, would you file a JIRA for this? > > > any other depot (that depends on it via jars) using the dependency > "com.sita.ats-core:ats-core:3.50" > > fails to find it claiming it is looking for > com.sita.ats-core/ats-core/3.50/jars/ats-core.jar > > so the actual question is how do I change the "module" name used in the > artifact patterns. > > > Sorry to mislead you. > > > Cheers > > Matt > Thx, Tom > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
