Felipe,
as you seem to use ejb 3.0, you need to make sure your ejb project's pom.xml
is configured accordingly :
<build>
...
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ejb-plugin</artifactId>
<configuration>
<ejbVersion>3.0</ejbVersion>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
</plugins>
Due to a limitation in the current maven embedder, m2e can't read ejb plugin
configuration (or other jee configs for that matter) in the parent pom, so
it *has* to be set in every ejb project
Have you tried to update your project maven configuration? That would set
the ejb project facet to 3.0, then you could delete ejb-jar.xml.
FYI Manifest.mf generation is currently unsupported.
regards,
Fred Bricon
On Mon, Jan 19, 2009 at 10:48 PM, Felipe Kamakura
<[email protected]>wrote:
> Hello everyone,
>
> I currently upgraded to the latest 0.9.7 stable build and realized that it
> now generates a META-INF/ejb-jar.xml automatically. Why does it do it, since
> most of the times Sessions are annotated? This is very bad for me because
> with this file, my application doesn't deploy on weblogic, and I have to
> delete it everytime I import a project or Update Project Configuration.
>
> Also, less critical but also annoying is the automatic generation of the
> META-INF/manifest.mf .
>
> Should m2eclipse generate these files automatically as it do?
>
> Thanks!
>
