The sub-module is using the following goal for the assembler:
<execution>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
But I think perhaps my artifact is being installed locally
(/.m2/repository) and then for some strange reason the
fake-assembly-put-my-product-together project decides that it should
look at real repositories when looking for dependencySets and not my
local .m2 repo, I wonder why that could be. Perhaps I should switch
over to using fileSets tag?
- Pulkit
On Thu, Sep 2, 2010 at 4:36 PM, Wendy Smoak <[email protected]> wrote:
> On Thu, Sep 2, 2010 at 4:26 PM, Pulkit Singhal <[email protected]>
> wrote:
>> Thank You Anders & Wendy, that was a very educational link.
>>
>> But by moving the product assembler from the parent to a child
>> project, I've now run into a problem because i also have some of the
>> children of the parent pom building some packages using assemblers ...
>> their assembled stuff is not published in the repository (i wonder
>> why) ... and the fake-assembly-put-my-product-together project can't
>> download it from the repo so it chokes :(
>
> What assembly plugin goal are you using? You probably need to use one
> that 'attach'es those assemblies to the project so they get
> installed/deployed.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
