I guess that the easier way to resolve this issue is to create a ant
script which might be started after this build under the maven-ant-plugin .
Alexandre
Farrukh S. Najmi a écrit :
Alexander Sack wrote:
Can you give an example? Also, why can't you change where the target is
produced?
Hi Alexander,
There is a complex dependency on various plugin and underlying libraries
that does not offer much flexibility in where the file is produced.
The example is the one I gave earlier. The generate-sources phase produces:
target/jaxws/wsimport/java/META-INF/somefile
I need the resulting war to have:
META-INF/somefile
Thanks for any suggestions.
-aps
On 6/14/07, Farrukh S. Najmi <[EMAIL PROTECTED]> wrote:
Thanks Alexandre, but I do not have the option to change the directory
where my file is produced (it is under target tree).
This must be a common need to include META-INF files from target tree?
Any other suggestions?
Alexandre Touret wrote:
Hello,
probably, you could add the directory META-INF in your resource
directory like
src/main/resources/META-INF
It should work
Alexandre
Farrukh S. Najmi a écrit :
Dear colleagues,
My maven2 war project produces a file under the target tree as
part of
the generate-source phase:
target/somedirectory/META-INF/somefile
How can I include this file under the META-INF directory of the
packaged
war as follows:
META-INF/somefile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
