You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by ra...@jpmchase.com on 2007/02/14 19:08:56 UTC

manifestFile problem

Hi All,

before i ask my problem, quick check on one thing, is new ear plugin 2.3 
doesn't include implementation details in manifest ?

I'm having problemin using manifetFile attribute in ear plugin

                        <plugin>
                                <groupId>org.apache.maven.plugins
</groupId>
                                <artifactId>maven-ear-plugin</artifactId>
                                        <configuration>
 <manifestFile>${basedir}/MANIFEST.MF</manifestFile> 
                                        </configuration>
                        </plugin>


in my MANIFEST.MF  lets say i have

name: ${pom.artifactId}


but when my ear created and when i look into my manifest.mf i don't see 
the property  ${pom.artifactId} subsitiuted with the value of artifactId??

Is that something i'm doing wrong?

the other options i tried are

- I tried to include my manifest File as resources, but as a default 
manifest created from ear plugin that overwrites the manifest.mf at 
META-INF directory
- i tried to have src\main\application\META-INF\MANIFEST.MF, no use still 
my properties are not subsituted

any help appreciated





Thanks,
Raghurajan Gurunathan




-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law.  If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED.  Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.