Hi Levi,

Thanks for answering. 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)

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


Analyist/Programmer
email: [email protected]
phone: +44(0) 1483 521213



                                                                           
             Levi Hoogenberg                                               
             <levihoogenb...@g                                             
             mail.com>                                                  To 
                                       [email protected]            
             06/02/2009 13:15                                           cc 
                                                                           
                                                                   Subject 
             Please respond to         Re: [gradle-user] sub-projects in a 
             [email protected]         multiproject build need a           
                  aus.org              different name to thier directory   
                                       name                                
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




That's archivesBaseName, sorry.

On Fri, Feb 6, 2009 at 2:13 PM, Levi Hoogenberg <[email protected]>
wrote:
  Hi Matt,

  you can set the subprojects' archiveBaseName properties.

  Regards,
    Levi


  On Fri, Feb 6, 2009 at 1:08 PM, <[email protected]> wrote:
   Hi all,


   I have a hierarchical multiproject build which has names such as
   "foo_barr"
   for the sub project directories. I would like the produced artifacts to
   be
   "foo-bar.ext" (hyphen rather then underscore). However I cannot change
   the
   baseName in the subprojects as it is read only. I can change the
   basenames
   of subprojects  from the top level settings.gradle but then the build
   fails
   as it seems to assume that the directory name is the same as the base
   name
   (and it isn't). I can have a settings.gradle in each subproject but that
   stops me being able to simply do partial builds.

   What am I missing here?



   Cheers

   Matt




   Matthew Fudge
   Analyist/Programmer
   email: [email protected]
   phone: +44(0) 1483 521213


   ---------------------------------------------------------------------
   To unsubscribe from this list, please visit:

      http://xircles.codehaus.org/manage_email






---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to