Well commands you say ... hmm ... just doing: mvn clean install
and since that assembly:single goal should tie me into the maven
lifecycle, I suppose I felt this command was good enough?

In addition, in the .m2 repo I see exactly:
./m2/repository/parent/artifact-generating-child/artifact-xx.ABC
./m2/repository/parent/artifact-generating-child/artifact-xx.pom
./m2/repository/parent/assembly-based-artifact-generating-child/artifact-xx.jar
./m2/repository/parent/assembly-based-artifact-generating-child/artifact-xx.pom
./m2/repository/parent/assembly-based-artifact-generating-child/artifact-xx-from-assembler.DEF

Yes, there's no pom for artifact-xx.DEF

I'll try and figure this out on my own, the main questions around
structure have been answered for me. .. I'm sure at this point it will
take my effort and not any additional info from the users to get it
done

Thanks for the head start and good advice :)

On Thu, Sep 2, 2010 at 5:04 PM, Wendy Smoak <[email protected]> wrote:
> On Thu, Sep 2, 2010 at 4:59 PM, Pulkit Singhal <[email protected]> 
> wrote:
>>        <fileSet>
>>            <directory>../artifact-generating-child/target</directory>
> ...
>>            
>> <directory>../assembly-based-artifact-generating-child/target</directory>
>
> Bad idea.  Maven modules are intended to stand alone, not go wandering
> around the filesystem picking up stuff.
>
> Figure out why it can't get the artifacts from the repository like
> it's supposed to.  My guess is that you are not using an assembly
> plugin goal that "attaches" the artifacts to the build, so they are
> not getting installed/deployed.
>
> You said you're using assembly:single.  What commands are you
> executing and exactly do you see in your local repo after that?
>
> --
> 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]

Reply via email to