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,
I am developig a web service in Java. I use axis 1.4 and tomcat 5.5. From the
Client (Client.java) side I have to call some services in the class (
SDMInterfaceImpl.java). All was working correctly but now I have to add a GUI.
Every time I call I service in a graphical window should appear a message. When
I add to my application the new code to run the GUI I have the following error
in the client side:
Exception in thread main AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
http://schemas.xmlsoap.org/soap/envelope/%7DServer.userException
faultSubcode:
faultString: java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{ http://xml.apache.org/axis/}hostname:kif.mwrl.net
http://xml.apache.org/axis/%7Dhostname:kif.mwrl.net
java.lang.reflect.InvocationTargetException
at org.apache.axis.message.SOAPFaultBuilder.createFault(
SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement (
SOAPFaultBuilder.java :129)
at org.apache.axis.encoding.DeserializationContext.endElement(
DeserializationContext.java:1087)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement (
AbstractSAXParser.java :633)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement
(XMLNSDocumentScannerImpl.java:713)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(
XMLDocumentFragmentScannerImpl.java:1685)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument
(XMLDocumentFragmentScannerImpl .java:368)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (
XML11Configuration.java:834)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(
XMLParser.java :148)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(
AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at org.apache.axis.encoding.DeserializationContext.parse (
DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke (
MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke (Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at org.ambientnetworks.sd_sde.client.Client.main(Client.java:55)
I attach here the service and the client code too. Could someone tell me where
the error comes from? And is it correct the way I create the GUI?
package org.ambientnetworks.sd_sde;
import java.awt.*;
import java.awt.event.*;
public class SDMInterfaceImpl extends Thread implements SDMInterface{
private String hit = hit;
private String dummy_result = ok;
private int result;
private int puzzle;
private List listOptions;
private static SDMInterfaceImpl instance; private Frame f; private TextField
txtResults;
//public SDMInterfaceImpl() {
public void init() {
//init the GUI
f = new Frame();
txtResults = new TextField();
listOptions = new List();
f.add(listOptions);
f.pack();
f.setVisible(true);
}
public static SDMInterfaceImpl getInstance () {
if(instance == null) {
instance = new SDMInterfaceImpl ();
}
return instance;
}
public String reqConn(String src, String dst){
final String sourceHIT = src;
final String destinationHIT = dst;
new Thread (){
public void run (){
try {
if (sourceHIT.equals(hit)) {
String res = ok;
result = new Integer (1);
puzzle =1;
}
else {
String res = notOK
result= new Integer (0);
puzzle = 10;
}
init();
listOptions.addItem(reqConn);
}catch (Exception e) {
e.printStackTrace();
}
}
}.start();
return dummy_result;
}
}
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 EJB 3.0 module using the maven-ejb-plugin for Maven 2.x. The problem is that when the plugin tries to package the jar archive, it fails because it can't find the META-INF/ejb-jar.xml file. The point is that I'm using EJB 3.0 and I don't need that file. Here is an extract from my pom.xml file: nameERS Platform - Model Layer/name artifactIdersplatform-model/artifactId groupIdcom.social_labs.ers.platform/groupId packagingejb/packaging . build plugins plugin artifactIdmaven-ejb-plugin/artifactId groupIdorg.apache.maven.plugins/groupId configuration ejbVersion3.0/ejbVersion /configuration /plugin /plugins /build The mvn's output when I run mvn install is as follows: [INFO] [ejb:ejb] [INFO] Building ejb ersplatform-model-1.0-SNAPSHOT [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error assembling EJB Embedded error: C:\fuentes\projects\ERS\platform\model\target\classes\META-INF\e jb-jar.xml isn't a file. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 9 seconds [INFO] Finished at: Wed Sep 27 10:50:42 CEST 2006 [INFO] Final Memory: 5M/11M [INFO] Does anyone know where is the problem? Regards, Alonso - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 Glassfish community (= Java EE 5 Reference Implementation) to publish a j2ee.jar (= Java EE 5 APIs) on the Maven 2 central repository to allow coders to easily use the Java EE technology with Maven, without the need to download the complete SDK manually. A few minutes later Bill SHANNON (= Java EE 5 Specification Lead) answered me that in fact they are working on this issue and he will try to speed up this process! :-) So soon the days will be gone where we all need to download the Java EE 5 SDK just to get the APIs. Soon it will be possible to just add a dependency on Sun's MVN2 repository to get the complete Java EE 5 APIs downloaded automatically when compiling an EJB3 project... :-) Have lots of fun! Markus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 client with way too many dependencies (includes all of the EJBs dependencies) and so that we could compile the EJB in 1.5 but compile the client under 1.4. -Original Message- From: Markus KARG [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 4:23 AM To: Maven Users List Subject: EJB Client JAR Using Maven2's ejb package, I was able to create an ejb-jar from my sources. But not I want Maven to create an EJB Client JAR, that only contains the interfaces, and make another JAR dependent of that EJB Client JAR (by means of Class-Path: entry in MANIFEST.MF). How to do that? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 client as an EJB client dependency and that you can selectively filter out classes (bean classes, etc.) from the client jar (but not dependencies carried over from the EJB or any of its transitive dependencies). -Daryl -Original Message- From: Markus KARG [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 11:51 AM To: Maven Users List Cc: [EMAIL PROTECTED] Subject: Re: EJB Client JAR Daryl, thanks a lot for your answer once again. Indeed we managed to let the ejb packager create the client jar and now understand why you have not been using it. Actually it is scary to see all the Class-Path entries in the client... Maybe we should file a feature request. Thanks again Markus [EMAIL PROTECTED] wrote: 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 client with way too many dependencies (includes all of the EJBs dependencies) and so that we could compile the EJB in 1.5 but compile the client under 1.4. -Original Message- From: Markus KARG [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 4:23 AM To: Maven Users List Subject: EJB Client JAR Using Maven2's ejb package, I was able to create an ejb-jar from my sources. But not I want Maven to create an EJB Client JAR, that only contains the interfaces, and make another JAR dependent of that EJB Client JAR (by means of Class-Path: entry in MANIFEST.MF). How to do that? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 my team's requirement for compiling the client at a different JRE target level, though. -Daryl -Original Message- From: Markus KARG [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 11:51 AM To: Maven Users List Cc: [EMAIL PROTECTED] Subject: Re: EJB Client JAR Daryl, thanks a lot for your answer once again. Indeed we managed to let the ejb packager create the client jar and now understand why you have not been using it. Actually it is scary to see all the Class-Path entries in the client... Maybe we should file a feature request. Thanks again Markus [EMAIL PROTECTED] wrote: 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 client with way too many dependencies (includes all of the EJBs dependencies) and so that we could compile the EJB in 1.5 but compile the client under 1.4. -Original Message- From: Markus KARG [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 4:23 AM To: Maven Users List Subject: EJB Client JAR Using Maven2's ejb package, I was able to create an ejb-jar from my sources. But not I want Maven to create an EJB Client JAR, that only contains the interfaces, and make another JAR dependent of that EJB Client JAR (by means of Class-Path: entry in MANIFEST.MF). How to do that? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 inability to reproduce the exact same build down the road. -Original Message- From: Douglas Ferguson [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 8:38 AM To: users Subject: Can't release due to SNAPSHOT dependencies I am using some snapshot plugins so it won't let me release. I can understand not wanting to release because of a dependency on code or library snapshots, but for I don't have any issues with releasing something that is dependent on a snapshot of a tool, like cargo. Is there a way around this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 -Original Message- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Monday, August 28, 2006 10:26 PM To: Maven Users List Subject: How to know/specify version of plugin? I seem to notice that plugin versions are typically not specified in the project's pom, is this correct? How do you know what version it will look for if the version is not specified? Is the version dependent on the specified pluginRepositories? -dh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 we wish it would aggregate content in a multi-module project). I'd guess it's either something with the version of the plugin, your project structure, or your distribution mgmt. I've never done this before but have you tried running the xref plugin independently via the command line? -Daryl -Original Message- From: Jeff Mutonho [mailto:[EMAIL PROTECTED] Sent: Friday, August 18, 2006 2:46 AM To: Maven Users List Subject: xref not generating class html docs The xref reports generated for my project are broken.I can see the packages frame(on the top left hand corner) and the list of packages in the module.Underneath the packages frame there also is classes frame with a list of all the classes(as hyperlinks) in the module.Clicking on the these class links , I get a Not Found error.Eg for a class called CpeManager , I get : Not Found The requested URL /websites/eportal/eportal-services/xref/za/co/pragmaticus/portal/service s/CpeManager.html was not found on this server. This is happening for all the classes in all my modules.Why isn't the xref plugin generating the html docs for my classes? Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Modify the generated report site in Maven 2
Create a site.xml file under module/src/site similar to this and add
your item entry in the menu element...
?xml version=1.0 encoding=ISO-8859-1?
project name=Maven
bannerLeft
nameMaven/name
srchttp://maven.apache.org/images/apache-maven-project.png/src
hrefhttp://maven.apache.org//href
/bannerLeft
bannerRight
srchttp://maven.apache.org/images/maven-small.gif/src
/bannerRight
body
links
item name=Apache href=http://www.apache.org/; /
item name=Maven 1.0 href=http://maven.apache.org//
item name=Maven 2 href=http://maven.apache.org/maven2//
/links
menu name=Maven 2.0
item name=Introduction href=index.html/
item name=Download href=download.html/
item name=Release Notes href=release-notes.html /
item name=General Information href=about.html/
item name=For Maven 1.0 Users href=maven1.html/
item name=Road Map href=roadmap.html /
/menu
${reports}
...
/body
/project
See http://maven.apache.org/guides/getting-started/index.html
-Original Message-
From: Per Bondesson (KA/EAB) [mailto:[EMAIL PROTECTED]
Sent: Friday, August 04, 2006 4:19 AM
To: users@maven.apache.org
Subject: Modify the generated report site in Maven 2
Hi!
How can you add a link in the left menu och the generated report site?
Is it possible to modify it for your own needs?
Thanks!
/Per
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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 the mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run' Jeff Mutonho wrote: It looks like maven-antrun-plugin and xdoclet-maven-plugin are having issues with each other.I'm using maven-antrun-plugin in the web module , and xdoclet-maven-plugin in the services module.The services module gets built first.I took out the xdoclet-maven-plugin from my pom and the error disappeared , the build succeeded and my war was created.Does this mean maven-antrun-plugin and xdoclet-maven-plugin can not co-exist? I have the same problem in a build here. Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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... ... generateClienttrue/generateClient clientExcludes clientExclude**/appversion.properties/clientExclude clientExclude**/test/**/*.*/clientExclude /clientExcludes ... -Original Message- From: Todd Nine [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 07, 2006 11:49 AM To: users@maven.apache.org Subject: EJB Client dependencies Hi all, I'm declaring an EJB client with the following decencies in a webapp, and the common interfaces and beans for parameters and return values dependency groupIdata.partnership/groupId artifactIdpartnershipCommon/artifactId version1.0.0-SNAPSHOT/version /dependency dependency groupIdata.partnership/groupId artifactIdpartnershipEJB/artifactId version1.0.0-SNAPSHOT/version typeejb-client/type /dependency This works for requiring the EJB client, however, I'm also receiving partnershipBusiness, partnershipDataAccess, etc etc. These are all required in my EJB, but I don't want these transitive dependencies to be deployed on the remote client (The webapp). Short of an excludes directive in the webapp when I declare the ejb client dependency, is there any parameter I can use in the EJB plugin to exclude all decencies of the EJB on the client side when I build the ejb client? Thanks, Todd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 8:38 AM To: Maven Users List Subject: Re: Compiling sub-modules/artifacts in different jdks... On 5/24/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 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 thoughts? I assume you've configured the compiler plugin to target 1.5 at the top level of your project [1], so (as Tim mentioned) you can override the configuration to target 1.4 in the sub-module. Something that Jakarta Commons does (with Maven 1) is add X-Compile-Target: 1.4 to the manifest, to reassure people since it will otherwise just say Build-Jdk: 1.5.0_06. I haven't figured out how to do this with m2 yet. [1] http://maven.apache.org/plugins/maven-compiler-plugin/howto.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 thoughts? Thanks, Daryl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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... ... build plugins plugin artifactIdmaven-ear-plugin/artifactId configuration modules javaModule groupIdmy-db-lib/groupId artifactIdmy-db-lib/artifactId excludedtrue/excluded /javaModule ... /modules /configuration /plugin /plugins /build ... There are similar ways to explicitly exclude artifacts from other forms of packaging. The downside is that each client has to explicitly exclude the jar(s) making this an ugly approach (or conversely, explicitly include only what is wanted). I'd love to hear about a better solution if anyone knows of one. -Daryl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 4:45 AM To: users@maven.apache.org Subject: ejb-client and transitive dependencies Hi, I habe a problem with transitive dependencies when a project depends on a ejb artifact (ejb-client). My system consists of a client application (i.e. a rich client) which uses a ejb server application. The ejb server application needs some other artifacts for the server side processing (i.e. a DB access library). The client needs nothing else than the client-jar of the ejb artifact. My project structure with some pom.xml snippets looks as follows: myclient artifactIdmyclient/artifactId dependencies dependency artifactIdmyserver-ejb/artifactId typeejb-client/type /dependency /dependencies myserver myserver-ear artifactIdpv-ear/artifactId packagingear/packaging myserver-ejb artifactIdmyserver-ejb/artifactId packagingejb/packaging dependencies dependency artifactIdmy-db-lib/artifactId /dependency /dependencies It works almos fine. My problem is that the the client application (myclient) does not only inherit the ejb-client-jar of the server project. It inherits also the dependencies which are only used for server side processing (my-db-lib). Is there a way to suppress this dependeny inheritation (i.e. by setting a special scope on the my-db-lib dependency)? Setting the scope of the my-db-lib dependency to provided did not work because the dependency was also excluded from the generated ear file. The only way, i got it to work was by adding a exclusion to the client's pom.xml: artifactIdmyclient/artifactId dependency artifactIdmyserver-ejb/artifactId typeejb-client/type exclusions exclusion artifactIdmy-db-lib/artifactId /exclusion /exclusions /dependency I don't like this solution because i have to change the client's pom every time i add a internal library to the server project. Isn't there another solution for controlling the exported dependencies of a ejb artifact? Thanks for your help. Regards, Matthias -- Matthias Germann DV Bern AG mailto:[EMAIL PROTECTED] http://www.dvbern.ch Postadresse: Nussbaumstrasse 21, Postfach 106, 3000 Bern 22 Direktwahl: +41 31 378 24 60 Telefonzentrale: +41 31 378 24 24, Telefax: +41 31 378 24 74 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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... ... build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.4/source target1.4/target /configuration /plugin ... /plugins /build ... -Original Message- From: Fisher, Michael (IT) [mailto:[EMAIL PROTECTED] Sent: Monday, May 22, 2006 11:23 AM To: 'Maven Users List' Subject: Plugin versions and JDK Hello, Quick question regarding JDK versions and running Maven2 plugins... Maven requires a JAVA_HOME system property to be set in order to run, when I set this to point to a 1.4.2_06 JDK, I get an UnsupportedClassVersion exception when I get to the surefire test cycle (Using version 2.0 of Surefire). When looking at the JAR, it seems to have been built with 1.5.2_05. Does this mean I need to be running a 1.5+ JDK in order to use the latest version of such plugins? The reason I ask, is because even though I could build my software on 1.5+, I cannot deploy it to an environment running above 1.4.2. What is the suggested work around for this? Thanks, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
