On Sun, Feb 27, 2011 at 12:06 PM, Peter Niederwieser <[email protected]> wrote:
>
> Niclas Hedhman wrote:
>>
>> Am I facing a bug, or is there something I might be doing incorrectly?
>>
>
> I don't understand from your post what works and what doesn't. Also, what's
> that "baseName" property? Do you mean "archivesBaseName"?
baseName is 'forwarded' to the jar, such as
jar {
group = subProject.group
// baseName = subProject.baseName
manifest {
So, the issue is that the Maven generator correctly sees the JAR with
the baseName and put it into the generated POM, but that is not
'carried forward' to the Maven dependencies elsewhere in the multi
project build.
Sorry for not being totally clear.
I am also going to suggest to the community to become artifactId
incompatible to resolve this and do more by convention instead of
tailored.
Cheers
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/3xugrbk
I work here; http://tinyurl.com/24svnvk
I relax here; http://tinyurl.com/2cgsug
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
