Re: Deploying web applications from one pom file using a simple goal

2012-04-16 Thread Piotr Skawinski
Originally we used ant-run, but I fall into this weblogic-maven-plugin and
thought it would be more clean to ise it instead of ant-run. As I said it
works nice when running it from from every single web project. But I would
like to trigger this plugin from a multi-module pom file, so all web
applications could be deployed in one go.

On Mon, Apr 16, 2012 at 4:05 PM, Ron Wheeler rwhee...@artifact-software.com
 wrote:

 Wouldn't Ant do this for you rather nicely?
 Use the Antrun plug-in in its own maven project.

 Ron
 On 16/04/2012 9:34 AM, Piotr Skawinski wrote:

 Hi,

 Is there a way to deploy all web applications in a project to a servlet
 container (for ex. weblogic) from one pom file?

 I have following project structure:

 project-parent
 |-- project-parent-war
 |-- web-project-war-1
 |-- web-project-war-2
 .
 .
 |-- web-project-war-n
 |-- services

 project-parent is also a multi-module project and is used to build all sub
 projects in one go.

 In the project-parent-war I have defined several profiles that can be used
 to deploy/undeploy applications to/from different environments. I can run
 a
 deploy or an undeploy profile from all single web projects using:

 mvn -P localhost-deploy weblogic:deploy

 but I haven't found a way to run a profile for all applications from one
 pom file (for example from project-parent). Is it possible? If so, how
 should that pom file be defined and how should it be executed as a goal?

 thanks in advance, Piotr



 --
 Ron Wheeler
 President
 Artifact Software Inc
 email: rwhee...@artifact-software.com
 skype: ronaldmwheeler
 phone: 866-970-2435, ext 102




 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



Re: Deploying web applications from one pom file using a simple goal

2012-04-16 Thread Piotr Skawinski
Yeah, I thought of creating a single era file with all war files in it, but
our client's weblogic is not licence to support ear deployments.

On Mon, Apr 16, 2012 at 6:12 PM, Piotr Skawinski
piotr.skawin...@gmail.comwrote:

 Originally we used ant-run, but I fall into this weblogic-maven-plugin and
 thought it would be more clean to ise it instead of ant-run. As I said it
 works nice when running it from from every single web project. But I would
 like to trigger this plugin from a multi-module pom file, so all web
 applications could be deployed in one go.

 On Mon, Apr 16, 2012 at 4:05 PM, Ron Wheeler 
 rwhee...@artifact-software.com wrote:

 Wouldn't Ant do this for you rather nicely?
 Use the Antrun plug-in in its own maven project.

 Ron
 On 16/04/2012 9:34 AM, Piotr Skawinski wrote:

 Hi,

 Is there a way to deploy all web applications in a project to a servlet
 container (for ex. weblogic) from one pom file?

 I have following project structure:

 project-parent
 |-- project-parent-war
 |-- web-project-war-1
 |-- web-project-war-2
 .
 .
 |-- web-project-war-n
 |-- services

 project-parent is also a multi-module project and is used to build all
 sub
 projects in one go.

 In the project-parent-war I have defined several profiles that can be
 used
 to deploy/undeploy applications to/from different environments. I can
 run a
 deploy or an undeploy profile from all single web projects using:

 mvn -P localhost-deploy weblogic:deploy

 but I haven't found a way to run a profile for all applications from one
 pom file (for example from project-parent). Is it possible? If so, how
 should that pom file be defined and how should it be executed as a goal?

 thanks in advance, Piotr



 --
 Ron Wheeler
 President
 Artifact Software Inc
 email: rwhee...@artifact-software.com
 skype: ronaldmwheeler
 phone: 866-970-2435, ext 102




 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org





Re: Generating web project with java, webapp, and resource folder from archtype goal

2011-01-20 Thread Piotr Skawinski
No help on this ?  :)

On Wed, Jan 19, 2011 at 11:30 AM, Anders Hammar and...@hammar.net wrote:

 The list archives (nabble for example) are great for verifying that.

 /Anders

 On Wed, Jan 19, 2011 at 10:47, Piotr Skawinski 
 piotr.skawinski.ma...@gmail.com wrote:

  It wasnt on purpose. I just couldnt see the first mail reaching the
 mailing
  list, so i tried again :)
 
  Sorry for that :)
 
  On Wed, Jan 19, 2011 at 10:38 AM, Anders Hammar and...@hammar.net
 wrote:
 
   One mail to the list per question is enough. We understand that you're
   asking because something is blocking you, but there is no need to spam
  the
   list.
   Give people a few days to respond (although you very often get a
 response
   quicker than that on this list). If nobody responds, it could be that
  there
   is no good answer.
  
   /Anders
  
   On Wed, Jan 19, 2011 at 10:30, Piotr Skawinski 
   piotr.skawinski.ma...@gmail.com wrote:
  
Hi,
   
Is there a way in maven to generate a web project with java,
 resources,
   and
webapp folders running the archtype goal. Maven suggest to create a
  multi
project module with:
   
multi-project
 |-- pom.xml
 |-- my-app
 |-- my-web-app
   
by creating a multi project pom file and then running:
   
mvn archetype:create \
 -DgroupId=some-group-id \
 -DartifactId=my-app
   
which generates:
   
my-app
|-- pom.xml
|--src
  '-- main
 '-- java
   
and then:
   
mvn archetype:create \
 -DarchetypeArtifactId=maven-
archetype-webapp \
 -DgroupId=some-group-id \
 -DartifactId=my-web-app
   
which generates:
   
my-web-app
|-- pom.xml
|-- src
   '--main
 '-- resources
 '-- webapp
   
But i would like to get this structure
   
web-app
|-- pom.xml
|-- src
   '--main
 '-- java
 '-- resources
 '-- webapp
   
from running the archtype goal on.
   
   
   
cheers, Piotr
   
  
 



Generating web project with java, webapp, and resource folder from archtype goal

2011-01-19 Thread Piotr Skawinski
Hi,

Is there a way in maven to generate a web project with java, resources, and
webapp folders running the archtype goal. Maven suggest to create a multi
project module with:

multi-project
 |-- pom.xml
 |-- my-app
 |-- my-web-app

by creating a multi project pom file and then running:

mvn archetype:create \
  -DgroupId=some-group-id \
  -DartifactId=my-app

which generates:

my-app
|-- pom.xml
|--src
   '-- main
  '-- java

and then:

mvn archetype:create \
  -DarchetypeArtifactId=maven-archetype-webapp \
  -DgroupId=some-group-id \
  -DartifactId=my-web-app

which generates:

my-web-app
|-- pom.xml
|-- src
'--main
  '-- resources
  '-- webapp

But i would like to get this structure

web-app
|-- pom.xml
|-- src
'--main
  '-- java
  '-- resources
  '-- webapp

from running the archtype goal on.



cheers, Piotr


Generating web project with java, webapp, and resource folder from archtype goal

2011-01-19 Thread Piotr Skawinski
Hi,

Is there a way in maven to generate a web project with java, resources, and
webapp folders running the archtype goal. Maven suggest to create a multi
project module with:

multi-project
 |-- pom.xml
 |-- my-app
 |-- my-web-app

by creating a multi project pom file and then running:

mvn archetype:create \
  -DgroupId=some-group-id \
  -DartifactId=my-app

which generates:

my-app
|-- pom.xml
|--src
   '-- main
  '-- java

and then:

mvn archetype:create \
  -DarchetypeArtifactId=maven-
archetype-webapp \
  -DgroupId=some-group-id \
  -DartifactId=my-web-app

which generates:

my-web-app
|-- pom.xml
|-- src
'--main
  '-- resources
  '-- webapp

But i would like to get this structure

web-app
|-- pom.xml
|-- src
'--main
  '-- java
  '-- resources
  '-- webapp

from running the archtype goal on.



cheers, Piotr


Re: Generating web project with java, webapp, and resource folder from archtype goal

2011-01-19 Thread Piotr Skawinski
It wasnt on purpose. I just couldnt see the first mail reaching the mailing
list, so i tried again :)

Sorry for that :)

On Wed, Jan 19, 2011 at 10:38 AM, Anders Hammar and...@hammar.net wrote:

 One mail to the list per question is enough. We understand that you're
 asking because something is blocking you, but there is no need to spam the
 list.
 Give people a few days to respond (although you very often get a response
 quicker than that on this list). If nobody responds, it could be that there
 is no good answer.

 /Anders

 On Wed, Jan 19, 2011 at 10:30, Piotr Skawinski 
 piotr.skawinski.ma...@gmail.com wrote:

  Hi,
 
  Is there a way in maven to generate a web project with java, resources,
 and
  webapp folders running the archtype goal. Maven suggest to create a multi
  project module with:
 
  multi-project
   |-- pom.xml
   |-- my-app
   |-- my-web-app
 
  by creating a multi project pom file and then running:
 
  mvn archetype:create \
   -DgroupId=some-group-id \
   -DartifactId=my-app
 
  which generates:
 
  my-app
  |-- pom.xml
  |--src
'-- main
   '-- java
 
  and then:
 
  mvn archetype:create \
   -DarchetypeArtifactId=maven-
  archetype-webapp \
   -DgroupId=some-group-id \
   -DartifactId=my-web-app
 
  which generates:
 
  my-web-app
  |-- pom.xml
  |-- src
 '--main
   '-- resources
   '-- webapp
 
  But i would like to get this structure
 
  web-app
  |-- pom.xml
  |-- src
 '--main
   '-- java
   '-- resources
   '-- webapp
 
  from running the archtype goal on.
 
 
 
  cheers, Piotr
 



Re: release:prepare does not inherit plugins from the parent project?

2010-12-22 Thread Piotr Skawinski
The error occurs while using generateReleasePoms=true as configuration
within maven-release-plugin. The maven-release-plugin will generate a
release-pom.xml for the release and it is being used by maven for the build.
Looking into release-pom.xml I dont see any reference to java 1.6 version
which is defined within the plugins part in the parent project, so it is not
strange why it fails on building java code with annotations, since maven
uses java 1.3 version as default. My question is why release-pom.xml is not
getting plugins from the parent project? Could it be that this is a bug
inside maven-release-plugin? The release works fine with
generateReleasePoms=false.

Piotr

On Tue, Dec 21, 2010 at 5:31 PM, Ron Wheeler rwhee...@artifact-software.com
 wrote:

 On 21/12/2010 6:40 AM, Piotr Skawinski wrote:

 Hi Ron,

 There's actually no reference to 1.3, that is what what makes it strange
 :)
 The m-compiler-p is defined in the parent pom to use version 1.6, but
 somehow seems to be ignored by release:prepare. Maven is using version 1.3
 to compile with per default, unless you define the java version through
 m-compiler-p, which I actually do. Though, it seems to be ignored by
 release:prepare. When running clean install it works fine. I don't quite
 understand what you mean by using effective-pom. I thought it was intented
 to be used especially in this cas to see the real pom seen by maven :)

 Never seen any reference to 1.3 in anything that we have done with Maven
 over the last 3 years.
 We use Eclipse/STS as our IDE so we have GUI controls to set to control
 Maven and it is pretty easy to see what compiler is being requested, what
 JRE is being used for Maven tasks, etc.

 What IDE are you using and how do you build with Maven?

 I really like the Eclipse/STS from Springsource and everyone in the forum
 is probably tired of hearing me mention it but it makes Eclipse a pleasure
 to install (biggest reason we moved from standard eclipse) and it makes
 Maven very easy to use.

 I am also a big fan of Sonotype's Nexus and really recommend getting a repo
 as quickly as possible if you are going to use Maven.
 Other repos also exist but I only know Nexus.

 Ron



  Piotr

 On Mon, Dec 20, 2010 at 5:04 PM, Ron Wheeler
 rwhee...@artifact-software.com

 wrote:
 Where is the reference to 1.3 coming from?
 I think that was what the effective-pom was for, not to see if the
 plug-ins
 were there but to find out who is asking for 1.3.

 Ron



 On 20/12/2010 10:05 AM, Piotr Skawinski wrote:

  Hi again,

 Actually when running mvn help:effective-pom I can see all plugins from
 the
 parent as expected, but when running it after release:prepare (which
 actually faills) they are not there anymore. It seems that
 release:prepare
 ignores the parent's plugins for the project it runs the release for.
 Though, when plugins are defined in the project's scope and not the
 parent's
 the release:prepare works as expected. The plugin in the parent is
 defines
 parent as follows:

 project
  .
  .
  .
  build
   plugins
plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-compiler-plugin/artifactId
 version2.0.2/version
 configuration
  source1.6/source
  target1.6/target
  encodingUTF-8/encoding
 /configuration
/plugin
   plugins
  build
 project


 Piotr



 On Mon, Dec 20, 2010 at 2:57 PM, Anders Hammarand...@hammar.net
 wrote:

  Check the project's effective pom.

 mvn help:effective-pom

 Most likely what you think should be inherited isn't. How is
 m-compiler-p
 declared in the parent?

 /Anders

 On Mon, Dec 20, 2010 at 14:50, Piotr Skawinski
 piotr.skawinski.ma...@gmail.com   wrote:

  Hi,

 I'm having problems using release:prepare plugin on a project that

  inherits

  from a parent project. It seems that it cannot see the plugins from
 the
 parent project and fails on compiling java vesion 1.6 classes claiming

  that

  1.3 version does not support annotations. It works fine with clean

  install.

  The maven-compiler-plugin is defined in the parent project. What can
 be

  the

  problem?

 thanks in advance,

 Piotr


  -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




Re: release:prepare does not inherit plugins from the parent project?

2010-12-21 Thread Piotr Skawinski
Hi Ron,

There's actually no reference to 1.3, that is what what makes it strange :)
The m-compiler-p is defined in the parent pom to use version 1.6, but
somehow seems to be ignored by release:prepare. Maven is using version 1.3
to compile with per default, unless you define the java version through
m-compiler-p, which I actually do. Though, it seems to be ignored by
release:prepare. When running clean install it works fine. I don't quite
understand what you mean by using effective-pom. I thought it was intented
to be used especially in this cas to see the real pom seen by maven :)

Piotr

On Mon, Dec 20, 2010 at 5:04 PM, Ron Wheeler rwhee...@artifact-software.com
 wrote:

 Where is the reference to 1.3 coming from?
 I think that was what the effective-pom was for, not to see if the plug-ins
 were there but to find out who is asking for 1.3.

 Ron



 On 20/12/2010 10:05 AM, Piotr Skawinski wrote:

 Hi again,

 Actually when running mvn help:effective-pom I can see all plugins from
 the
 parent as expected, but when running it after release:prepare (which
 actually faills) they are not there anymore. It seems that release:prepare
 ignores the parent's plugins for the project it runs the release for.
 Though, when plugins are defined in the project's scope and not the
 parent's
 the release:prepare works as expected. The plugin in the parent is defines
 parent as follows:

 project
  .
  .
  .
  build
   plugins
plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-compiler-plugin/artifactId
 version2.0.2/version
 configuration
  source1.6/source
  target1.6/target
  encodingUTF-8/encoding
 /configuration
/plugin
   plugins
  build
 project


 Piotr



 On Mon, Dec 20, 2010 at 2:57 PM, Anders Hammarand...@hammar.net  wrote:

  Check the project's effective pom.
 mvn help:effective-pom

 Most likely what you think should be inherited isn't. How is m-compiler-p
 declared in the parent?

 /Anders

 On Mon, Dec 20, 2010 at 14:50, Piotr Skawinski
 piotr.skawinski.ma...@gmail.com  wrote:

  Hi,

 I'm having problems using release:prepare plugin on a project that

 inherits

 from a parent project. It seems that it cannot see the plugins from the
 parent project and fails on compiling java vesion 1.6 classes claiming

 that

 1.3 version does not support annotations. It works fine with clean

 install.

 The maven-compiler-plugin is defined in the parent project. What can be

 the

 problem?

 thanks in advance,

 Piotr



 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




release:prepare does not inherit plugins from the parent project?

2010-12-20 Thread Piotr Skawinski
Hi,

I'm having problems using release:prepare plugin on a project that inherits
from a parent project. It seems that it cannot see the plugins from the
parent project and fails on compiling java vesion 1.6 classes claiming that
1.3 version does not support annotations. It works fine with clean install.
The maven-compiler-plugin is defined in the parent project. What can be the
problem?

thanks in advance,

Piotr


Re: release:prepare does not inherit plugins from the parent project?

2010-12-20 Thread Piotr Skawinski
Hi again,

Actually when running mvn help:effective-pom I can see all plugins from the
parent as expected, but when running it after release:prepare (which
actually faills) they are not there anymore. It seems that release:prepare
ignores the parent's plugins for the project it runs the release for.
Though, when plugins are defined in the project's scope and not the parent's
the release:prepare works as expected. The plugin in the parent is defines
parent as follows:

project
 .
 .
 .
 build
  plugins
   plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
 source1.6/source
 target1.6/target
 encodingUTF-8/encoding
/configuration
   /plugin
  plugins
 build
project


Piotr



On Mon, Dec 20, 2010 at 2:57 PM, Anders Hammar and...@hammar.net wrote:

 Check the project's effective pom.
 mvn help:effective-pom

 Most likely what you think should be inherited isn't. How is m-compiler-p
 declared in the parent?

 /Anders

 On Mon, Dec 20, 2010 at 14:50, Piotr Skawinski 
 piotr.skawinski.ma...@gmail.com wrote:

  Hi,
 
  I'm having problems using release:prepare plugin on a project that
 inherits
  from a parent project. It seems that it cannot see the plugins from the
  parent project and fails on compiling java vesion 1.6 classes claiming
 that
  1.3 version does not support annotations. It works fine with clean
 install.
  The maven-compiler-plugin is defined in the parent project. What can be
 the
  problem?
 
  thanks in advance,
 
  Piotr
 



RE: UnsupportedClassVersionError on unit test using java 1.5

2007-06-01 Thread Piotr Skawinski

It works now fine thanks a lot !!! -:))) Subject: RE: 
UnsupportedClassVersionError on unit test using java 1.5 Date: Thu, 31 May 
2007 18:16:36 +0200 From: [EMAIL PROTECTED] To: users@maven.apache.org  
Check out the options on the Surefire plugin. The jvm parameter seems to be 
what you want. See 
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#jvm .   
-Original Message- From: Piotr Skawinski [mailto:[EMAIL PROTECTED]  
Sent: Thursday, May 31, 2007 12:09 PM To: Maven Users List Subject: RE: 
UnsupportedClassVersionError on unit test using java 1.5   I still get the 
same error -:( Date: Thu, 31 May 2007 08:49:33 -0700 From: [EMAIL 
PROTECTED] To: users@maven.apache.org Subject: Re: 
UnsupportedClassVersionError on unit test using java 1.5  On 5/31/07, Piotr 
Skawinski [EMAIL PROTECTED] wrote:   Is it possible to specify in the 
pom.xml that unit test should also be executed by jdk  1.5 even though my 
JAVA_HOME points to jdk 1.4??  This might help... 
http://docs.codehaus.org/display/MAVENUSER/Compile+and+Test+with+Differe 
nt+JDK+Versions  --  Wendy  
- To 
unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: 
[EMAIL PROTECTED] 
_ Connect to 
the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-ussour 
ce=wlmailtagline  
- To 
unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL 
PROTECTED] 
_
With Windows Live Hotmail, you can personalize your inbox with your favorite 
color.
www.windowslive-hotmail.com/learnmore/personalize.html?locale=en-usocid=TXT_TAGLM_HMWL_reten_addcolor_0607

RE: Building files with different jdk versions

2007-06-01 Thread Piotr Skawinski

This is what I did, thanks a lot -:)) Date: Thu, 31 May 2007 20:44:01 -0500 
From: [EMAIL PROTECTED] To: users@maven.apache.org Subject: Re: Building 
files with different jdk versions  You probably should separate your project 
into different projects each containing the set of files you want, allowing 
each one to use it's own compiler:  
http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html
  Or if you can get away with it (which most people can), just using the 
higher version compiler and setting the lower target/source for the lower 
projects (eg, use javac 1.5 always, but set target as 1.4 when necessary).  
http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
  However  if you raallly need to keep the files in a single project, put 
the set of some files you described into a separate directory - and include 
that directory using this:  
http://mojo.codehaus.org/build-helper-maven-plugin/howto.html  Called under a 
profile:  http://sonatype.com/book/profiles.html  Isn't diverging from the 
standard fun?  ;-P  Eric  On 5/31/07, Piotr Skawinski [EMAIL PROTECTED] 
wrote:Hi,I need to build my project with the jdk1.5, but some of the 
 files also need to be build with jdk1.4. Is it possible in a single  
pom.xml to specify the jdk version to be used to build the whole  project and 
at the same time to specify other jdk version to be used to  build only some 
files? If not is then there any other solution for it?  Regarsds, Piotr  
_  Invite 
your mail contacts to join your friends list with Windows Live  Spaces. It's 
easy!   
http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us
   --  Eric Redmond http://www.sonatype.com
_
With Windows Live Hotmail, you can personalize your inbox with your favorite 
color.
www.windowslive-hotmail.com/learnmore/personalize.html?locale=en-usocid=TXT_TAGLM_HMWL_reten_addcolor_0607

Building files with different jdk versions

2007-05-31 Thread Piotr Skawinski

Hi,

I need to build my project with the jdk1.5, but some of the files also need
to be build with jdk1.4. Is it possible in a single pom.xml to specify the
jdk version to be used to build the whole project and at the same time to
specify other jdk version to be used to build only some files? If not is
then there any other solution for it?

Regarsds, Piotr


Building files with different jdk versions

2007-05-31 Thread Piotr Skawinski

Hi,I need to build my project with the jdk1.5, but some of the
files also need to be build with jdk1.4. Is it possible in a single
pom.xml to specify the jdk version to be used to build the whole
project and at the same time to specify other jdk version to be used to
build only some files? If not is then there any other solution for it?
Regarsds, Piotr
_
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vistamkt=en-USform=QBRE

Building files with different jdk versions

2007-05-31 Thread Piotr Skawinski

Hi,I need to build my project with the jdk1.5, but some of the
files also need to be build with jdk1.4. Is it possible in a single
pom.xml to specify the jdk version to be used to build the whole
project and at the same time to specify other jdk version to be used to
build only some files? If not is then there any other solution for it?
Regarsds, Piotr
_
Invite your mail contacts to join your friends list with Windows Live Spaces. 
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us

UnsupportedClassVersionError on unit test using java 1.5

2007-05-31 Thread Piotr Skawinski

Hi,I'm using java 1.4 for general build (and so my JAVA_HOME points to the jdk 
1.4). But one subproject is build with java 1.5 and this is specified in its 
pom.xml file:plugingroupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactIdconfiguration   
 verbosetrue/verboseforktrue/fork
executableC:\Program Files\Java\jdk1.5.0_06\bin\javac/executable
compilerVersion1.5/compilerVersionsource1.5/source  
  target1.5/target/configuration  /pluginWhen I run my unit 
test I get UnsupportedClassVersionError with follwing stack 
trace:[INFO]
 Surefire report directory: 
F:\CC_Work\isk_SI-Main\si-serviceinfrastructure\cb-mob-proj\si-to-mainframe-bean\target\surefire-reportsorg.apache.maven.surefire.booter.SurefireExecutionException:
 dk/pfa/si/adapter/bs2000/bc/BS2000IsDownTest (Unsupported major.minor version 
49.0); nested exception is java.lang.UnsupportedClassVersionError: 
dk/pfa/si/adapter/bs2000/bc/BS2000IsDownTest (Unsupported major.minor version 
49.0)java.lang.UnsupportedClassVersionError: 
dk/pfa/si/adapter/bs2000/bc/BS2000IsDownTest (Unsupported major.minor version 
49.0)at 
java.lang.ClassLoader.defineClass(Ljava/lang/String;[BIILjava/security/ProtectionDomain;)Ljava/lang/Class;(Unknown
 Source)at 
java.security.SecureClassLoader.defineClass(Ljava/lang/String;[BIILjava/security/CodeSource;)Ljava/lang/Class;(SecureClassLoader.java:123)
at 
java.net.URLClassLoader.defineClass(Ljava/lang/String;Lsun/misc/Resource;)Ljava/lang/Class;(URLClassLoader.java:251)
at 
java.net.URLClassLoader.access$100(Ljava/net/URLClassLoader;Ljava/lang/String;Lsun/misc/Resource;)Ljava/lang/Class;(URLClassLoader.java:55)
at 
java.net.URLClassLoader$1.run()Ljava/lang/Object;(URLClassLoader.java:194)  
  at 
jrockit.vm.AccessController.do_privileged_exc(Ljava/security/PrivilegThis
 is somehow also understandable, as I expect that unit test is executed by jdk
1.4 while the class file is compiled with jdk 1.5. Is it possible to
specify in the pom.xml that unit test should also be executed by jdk 1.5 even 
though
my JAVA_HOME points to jdk 1.4??



Any help will be appreciated.Best regards, Piotr


_
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+worldmkt=en-USform=QBRE

RE: UnsupportedClassVersionError on unit test using java 1.5

2007-05-31 Thread Piotr Skawinski

I still get the same error -:( Date: Thu, 31 May 2007 08:49:33 -0700 From: 
[EMAIL PROTECTED] To: users@maven.apache.org Subject: Re: 
UnsupportedClassVersionError on unit test using java 1.5  On 5/31/07, Piotr 
Skawinski [EMAIL PROTECTED] wrote:   Is it possible to specify in the 
pom.xml that unit test should also be executed by jdk  1.5 even though my 
JAVA_HOME points to jdk 1.4??  This might help... 
http://docs.codehaus.org/display/MAVENUSER/Compile+and+Test+with+Different+JDK+Versions
  --  Wendy  
- To 
unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL 
PROTECTED] 
_
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-ussource=wlmailtagline