Brian,
         I was able to build the jar with just the templates in it as
resources so dependecy-unpack is exactly what I was looking for.  If I add
the plugin to any pom using these templates during the install phase they
will be unpacked into the local repository as I desire.  Thanks for the
quick response.

Jerry

Brian E Fox wrote:
> 
> You should use the assembly plugin to zip these templates up and deploy
> them and then use the dependency:unpack to take them from the repo and
> drop them in your local build as needed. You can also use the
> remote-resources plugin in a similar way.
> 
> -----Original Message-----
> From: jeeads [mailto:[EMAIL PROTECTED] 
> Sent: Friday, December 07, 2007 6:34 PM
> To: [email protected]
> Subject: Re: deploy goal not copying resources to deployment repository
> 
> 
> When I read about the maven-resources-plugin <outputDirectory> it stated
> that
> it allows you to set this to whatever your needs are.  The extra
> resource
> files under the templates directory are to be used globally by our
> developers to over ride the hibernate templates and spring templates in
> the
> AndroMDA cartridges.  By using the deployment repository to hold these
> we
> can make enterra-templates a project dependency which will be updated
> into
> the developers local repository wherever an update is made to the
> enterra-templates project.  Since each developer has his/her own local
> repository that is predicated on the environmental variable M2_REPO we
> can
> set the mergeLocation for these templates to that directory.
> 
> 
> Wendy Smoak-3 wrote:
>> 
>> On Dec 7, 2007 2:45 PM, jeeads <[EMAIL PROTECTED]> wrote:
>> 
>>>           <outputDirectory>
>>>            
>>> ${env.M2_REPO}/${pom.groupId}/${pom.artifactId}/${pom.version}
>>>           </outputDirectory>
>> 
>> This is unusual.  Normally the output directory is "target/classes"
>> and only the artifact and pom are installed into the local repo.
>> 
>>> When I run mvn deploy none of the templates directory structure is
> copied
>>> to
>>> the deployment repository but the pom and jar are copied? What am I
>>> missing?
>> 
>> That's what is supposed to happen.  Maven doesn't know anything about
>> the extra files that you are copying into the local repo.
>> 
>> -- 
>> Wendy
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> 
> 
> -- 
> View this message in context:
> http://www.nabble.com/deploy-goal-not-copying-resources-to-deployment-re
> pository-tf4964701s177.html#a14222922
> Sent from the Maven - Users mailing list archive at Nabble.com.
> 
> 
> ---------------------------------------------------------------------
> 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]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/deploy-goal-not-copying-resources-to-deployment-repository-tp14221441s177p14240096.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to