I was suspecting something like that....
I will try your suggestion tomorrow at work.
Thanks
Luca
Brian E Fox wrote:
>
> If these resources are one of these:
>
> <resources>
> −
> <resource>
> <filtering>false</filtering>
> <directory>${basedir}/conf</directory>
> </resource>
> −
> <resource>
> <filtering>false</filtering>
> <directory>${basedir}/src/main/resources</directory>
> </resource>
> </resources>
>
> Then you have a problem. Basedir is the folder of the pom being built. If
> these files are not in your scm, then naturally they won't be in the
> target/checkout folder. Rather than relying on something not in scm and on
> your local file system, you should use assembly:single in a pom project to
> make a zip of these files. Deploy that to the repository and then use
> dependency:unpack to pull these down and put them somewhere you can pick
> them up.
>
> -----Original Message-----
> From: Luca Tagliani [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 11, 2008 4:16 AM
> To: [email protected]
> Subject: RE: Release process
>
>
> To be more precise I will describe more in detail.
>
> I have some resources located on the filesystem of my PC that isn't inside
> my scm, because they are platform dependent (i.e.: configuratoin files for
> db connection).
> When I release the project these resources should be copied into the
> released war as "template" for the customer. In fact once the application
> is
> deployed, they have to be taylored to the customer's configuration.
>
> Attached to this message you will find the pom.xml of my project.
>
> http://www.nabble.com/file/p15975686/pom.xml pom.xml
>
> I would expect that if I specify the resource in the pom they will be
> copied
> during the release process.
> Or am I wrong and doesn't understand nothing at all :-)
>
> Luca
>
>
> Brian E Fox wrote:
>>
>> Are these resources not inside your scm? Why would they not be picked up
>> from the checkout folder? Are you using absolute paths or something?
>> Something is fishy here because the build shouldn't care where it is.
>>
>> -----Original Message-----
>> From: Luca Tagliani [mailto:[EMAIL PROTECTED]
>> Sent: Monday, March 10, 2008 6:48 PM
>> To: [email protected]
>> Subject: RE: Release process
>>
>>
>> I mean that during the release:perform the war is built using the
>> content of
>> the target/checkout directory and the resources placed outside the
>> src/main/resources directory (but specified in the resources tag of the
>> pom.xml) isn't copied into the war.
>>
>>
>> Brian E Fox wrote:
>>>
>>> What do you mean the release plugin doesn't copy them? The resources
>> are
>>> in the war and the war gets deployed. You may also be getting a
>> sources
>>> jar and the resources should be in there. Is this what you're missing?
>>>
>>> -----Original Message-----
>>> From: Luca Tagliani [mailto:[EMAIL PROTECTED]
>>> Sent: Monday, March 10, 2008 11:37 AM
>>> To: [email protected]
>>> Subject: Release process
>>>
>>>
>>> Hi all,
>>> I'm using the release plugin with a subversion SCM to release a war.
>>> I want to perform a release including the resources specified in the
>>> <resource> tag of my pom, but the plugin doesn't copy them.
>>>
>>> When I do a normal deploy, obviously, the resources are copied in the
>>> war.
>>>
>>> There's a way to do this?
>>>
>>> Thanks in advance
>>>
>>> Luca
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Release-process-tp15950826s177p15950826.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]
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Release-process-tp15950826s177p15964745.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]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Release-process-tp15950826s177p15975686.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]
>
>
>
--
View this message in context:
http://www.nabble.com/Release-process-tp15950826s177p15990991.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]
