Nathan Coast Vincent Massol Upgrade maven-model to version 3.0.2. Java sources are not compiled when used with maven-test-plugin-1.8 and maven.test.skip=true. Update dependencies to match ones in maven 1.1 core and to unify them between plugins. The following dependencies are updated :

• commons-logging v1.0.3 -> v1.0.4
• maven v1.0 -> v1.0.2
• maven-model v3.0.0 -> v3.0.1

Update dependency to Maven Model v3.0.0 final (it was previously depending on 3.0.0 SNAPSHOT). By default do not generate client EJB. I believe this is a more common default that generating as generation of client EJBs is only required for distributed apps which are not so common. Make the ejb creation work even if there are not sources. Fixed default property values in the web site documentation. EJB client jar can now be generated and deployed/installed automatically by the standard goals ( ejb, ejb:ejb, ejb:installand ejb:deploy). Previous goals dedicated to ejb client have been deprecated. There is a new property maven.ejb.client.generatewhich decides whether or not to generate the ejb client jar. It defaults to true. Added new EJB type handler that supports ejband ejb-clienttypes. This fixes the bug with ejb:install/deploy-clientnot uploading the client jar. Added new maven.ejb.build.dirproperty that specifies the location where the EJBs are generated. Modified existing maven.ejb.final.nameproperty (and exposed it as a public property) so that it doesn't include the path (the path is now provided by the new maven.ejb.build.dirproperty). This allows aligning the WAR and EJB plugin properties. Note: This is a breaking change for all those using the maven.ejb.final.nameproperty (which was not a public property). Made the maven.ejb.final.nameproperty public as it is required by several other plugins and before this change the only way is for these plugins was to call the non-public ejb:initgoal. Replace Apache Jakarta Maven by Apache Maven in Manifest Add ejb:install-client and ejb:deploy-client goals. Don't generate a Class-Path manfiest entry if there are no jars with ejb.manifest.classpath set to true Only include maven.ejb.src if it exists Synchronize ejb and jar plugin usage of: Specification-Title/Vendor/Version and Implementation-Title/Vendor/Version Added maven.ejb.index, maven.ejb.client.index properties. Added maven.ejb.excludes and maven.ejb.includes properties. Added deploy, deploy-snapshot and install-snapshot goals Artifact processing in the plugin was slightly changed and now it supports jar overriding mechanism property ejb.bundle.jar was renamed to ejb.bundle (old property is still supported, but deprecated) Initial plugin created