On May 19, 2010, at 10:50 AM, Walter Di Carlo wrote:
>
>
> On 19 May 2010 16:31, Spencer Allain <[email protected]> wrote:
> compile "myjar:myjar:jar"
> says that you want organization "myjar", module "myjar" and revision "jar"
> (and since it's a compile dependency, it automatically assumes "jar" as the
> extension)
>
> I assume you really want either:
>
> compile "myjar:myjar"
> or
> compile "myjar:my...@jar"
>
> affected by needs of raw artifact versus potential transitive dependencies.
>
> Thank you for your suggenstion.
>
> I have played with such examples, but in both cases I am getting a jar with
> filename myjar-.jar containing a wrong dash
>
> As workaround I will try to copy the jars directly from the lib folders of
> the projects
>
I think you really do have the revision set wrong. It's possible that when you
re-ran your build to try these suggestions, the jar step was optimized out
since your source didn't change. You might try retesting with the --no-opt
option. It sounds like you are having problems with the filename of your own
jars (from a different subproject), not the name of external dependencies. In
that case, it would be typical that you would refer to them with a project
dependency like "compile project('projb')" and not "compile 'myproj:projb'".
Did you set project.version in each project?
Also, if you are only trying to copy out the jars, then the bulk of your
CopySpec is not needed - you don't need the first from and all the excludes.
