RE: InvocationtargetException

You realize this is the Maven users group (vs. Axis) or am I missing something? -Original Message- From: Alicia Sánchez-Mora [mailto:[EMAIL PROTECTED] Sent: Friday, March 02, 2007 8:32 AM To: users@maven.apache.org Subject: InvocationtargetException I forgot atach the code :P Hello,

RE: M2 EJB plugin

Which version of the plugin? I think you have to use 2.1 which I believe is still a SNAPSHOT. -Original Message- From: alonso [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 27, 2006 4:23 AM To: users@maven.apache.org Subject: M2 EJB plugin Hi there, I'm trying to package an

RE: Java EE 5 available on central repository soon!

Outstanding - thanks for following up with them on that. -Original Message- From: Markus KARG [mailto:[EMAIL PROTECTED] Sent: Saturday, September 16, 2006 4:13 AM To: Maven Users List Subject: Java EE 5 available on central repository soon! Dear Maven Community, Today I asked the Glass

RE: EJB Client JAR

Markus, No problem. I think because of transitive dependencies, the only way they could make it work would be to qualify the dependencies which would introduce problems elsewhere. Even if the plugin did provide this feature, unfortunately for me, I don't think it would be able to accommodate m

RE: EJB Client JAR

One other concern would be that in general, the EJB client generation from the same EJB module violates Maven's principle of one artifact per project/module. As I understand it today, the only benefit of using it is that it will generate a separate JAR file in the repo that can be referenced by a

RE: EJB Client JAR

Not necessarily the maven-ejb-plugin way, but you can create a separate module for the EJB client and then add a compile dependency on the that project in your EJB project's pom. We did this to get around the fact that using the generateClient option on the maven-ejb-plugin generates a pom for the

RE: Can't release due to SNAPSHOT dependencies

The only way around it that we found was to modify the POM for the snapshot plugin under question and release it into our team repository. There is a good reason for not releasing code that has a snapshot dependency on a plugin, though - the behavior of the plugin could change resulting in the inab

RE: How to know/specify version of plugin?

I believe it uses the latest released plugin. You can always specify the version, though. When you release your project w/the release plugin, all plugin versions will be fixed so that subsequent builds of the released version of your project always have the same plugin behavior. -Daryl -Or

RE: xref not generating class html docs

I'd reach out to the plugin developer(s). Be prepared to provide your project/module structure, your POM(s), and the output from running your mvn site... command. This is never much of a consolation, but we run Maven 2.x for several projects and haven't had a problem with XREF before (other than

RE: Modify the generated report site in Maven 2

Create a site.xml file under /src/site similar to this and add your entry in the element... Maven http://maven.apache.org/images/apache-maven-project.png http://maven.apache.org/ http://maven.apache.org/images/maven-small.gif http://www.apache.org/"; /

RE: Unable to find the mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run'

We have the same problem but if we execute 'clean' on the same line as 'package|install|deploy|etc.', the problem goes away. -Daryl -Original Message- From: Graham Leggett [mailto:[EMAIL PROTECTED] Sent: Thursday, July 06, 2006 1:37 PM To: Maven Users List Subject: Re: Unable to find th

RE: EJB Client dependencies

The EJB 2.1-SNAPSHOT (not sure if it's been released) includes a 'clientExcludes' directive that can be added as a subelement of the generateClient element... ... true **/appversion.properties **/test/**/*.* ... -Original Message-

RE: Compiling sub-modules/artifacts in different jdks...

Thank you, both - will try and let you know. I was hoping there was a way to compile the EJB in 1.5 but fork the process to compile the client with a different JDK (1.4) within the generateClient portion of the EJB plugin (vs. a separate custom module for the EJB client), though. Thanks, Daryl

RE: ejb-client and transitive dependencies

If your client is itself an EAR, one solution, albeit ugly is to explicitly exclude those jars from the client-side EAR... In the client-side EAR's POM... ... maven-ear-plugin my-db-lib my-db-lib t

Compiling sub-modules/artifacts in different jdks...

Is anyone aware of a way to compile artifacts or even sub-modules under different JDKs? I have an EJB that I compile under 1.5 but I want to generate the ejb-client compiled under 1.4 (there's nothing in the interfaces or DTOs that are 1.4-incompatible) so that 1.4-based clients can call it. Any

RE: Plugin versions and JDK

You should (unless I misunderstood you) be able to set your JAVA_HOME to 1.5 and still compile in 1.4. In your pom, you would need something like... ... org.apache.maven.plugins maven-compiler-plugin 1.4 1.4 ...