Re: Automatically remove version overrides from child POMs
Hello Robert, you could use the enforcer-plugin to enforce specific versions, then at least you have an easy way to identify those projects. We exclude all versions of spring and then include the latest version again, e.g. Regards Mirko -- Sent from my mobile On May 4, 2013 12:54 AM, "Enyedi, Robert" wrote: > Hi, > > We're using a parent POM which manages the versions of tens of > dependencies. I occasionally encounter modules within my group that > override some of those managed versions. > > Assuming the overrides are not legit, is there an automatic way to remove > them from the child POMs? I was hoping that the > versions:update-child-modules mojo would help, but it doesn't seem to do > what I need. > > Thanks, > Robert > >
Maven-nar-plugin Issue
I am trying to build C++ files and when i create my pom.xml, i am getting the following error *"Project build error: Unknown packaging: nar"* *My pom.xml* http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 nar Module: example narexample com.exmaple 0.1-SNAPSHOT org.apache.maven.plugins maven-nar-plugin 2.1-SNAPSHOT true shared bruch_test static -- View this message in context: http://maven.40175.n5.nabble.com/Maven-nar-plugin-Issue-tp5754838.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven-release-plugin AND IBM RTC build engine...
OK, now I see. Well you have gone further than I have with Jazz. I hope
you find a suitable solution as I would like to use Jazz again someday.
While it is a lot of work, I might suggest setting up your own Jazz
environment to experiment with, perhaps in a virtual machine. I have
done the complete Jazz install myself, but it is a lot of work. It may
have improved since then.
Cheers, Eric
On 2013-05-03 2:31 PM, Zanzerkia, Robert wrote:
Hi Eric,
I am using Jazz SCM.
It's even more painful as I don't have direct access to the build
server (I have to go through support to even do simple experiments).
If you see my later emails it's been narrowed down to scm status
command on the build server.
Nothing to do with the release-plugin itself.
Thanks,
Robert
-Original Message-
From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
Sent: Friday, May 03, 2013 4:48 PM
To: users@maven.apache.org
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
Doing a Maven release can be tricky if you are having problems with your
SCM plugin. It took me a long time to get release to work with Perforce
(but it still does not work properly), and you would think that would
just work.
Are you using the Jazz SCM or something else?
Cheers, Eric
On 2013-05-03 9:34 AM, Zanzerkia, Robert wrote:
I did few more experiments...
1) Renamed the RTC component so there is no space in the name.
2) Made sure directory has permission for build account etc.
3) Experimented by replacing maven command to just mvn scm:status and that
works without error.
So it's only via release-plug-in we get the error on scm status command.
Since replease-plug-in works on my laptop this is an issue on interaction between
maven, release-plugin and "Jazz build engine"
I re-ran the RTC build with -X switch in maven to get detailed log so
we can compare against release.log (one from my laptop).
Thanks,
Robert
PS: I have attached RTC_JAZZ-Build.log from build server.
Working release.log
[DEBUG] repositoryWorkspace - EI_9.05_Release_Snapshot
[DEBUG] Executing status command...
[INFO] Executing: cmd.exe /X /C "scm status --username a408072 --password *
--wide"
[INFO] Working directory: C:\Documents and
Settings\a408072.DMN1\workspace301-EI-9.05_Rel\EI AS-ITAM uCMDB Pattern DEV
[DEBUG] Consumed line :Workspace: (1189) "EI_9.05_Release_Snapshot" <-> (1001) "EI
AS-ITAM uCMDB 9.02 EI Stream"
NOT working RTC build lines.
[DEBUG] repositoryWorkspace - srvrtcbuild-EI-AS-ITAM-PatternDEV-DEV_Release_WS
[DEBUG] Executing status command...
[INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password *
--wide"
[INFO] Working directory: D:\RTCBuildWorkspace\EI-ITAMTEST\uCMDBPackages
[DEBUG] ErrorConsumer.consumeLine: Problem running 'status':
[DEBUG] ErrorConsumer.consumeLine: Current directory is not shared. Run from a
shared directory.
[ERROR] Error: Problem running 'status':
Current directory is not shared. Run from a shared directory.
-Original Message-
From: Zanzerkia, Robert
Sent: Tuesday, April 30, 2013 11:56 AM
To: Maven Users List
Subject: RE: Maven-release-plugin AND IBM RTC build engine...
Hi,
Actually it was Chris who helped me... Thanks Chris.
When I said NO access to RTC Build engine I meant for the physical server
where the build runs.
We have a support group that manages these servers which is why I don't have
the direct access.
(Yes that makes it more difficult to trouble shoot).
I am working with the local person to trouble shoot the issue.
The issue comes down to the scm -status command where on my laptop it works
fine but on the RTC build engine it gives below error.
We have defined
-DworkingDirectory = D:\temp\Maven (for the plugin working directory).
repository local directory =
D:\data\mavenrepo\ei_itam_discovery
RTC load directory: load directory = ${BUILDWORKSPACE}\EI-Discovery2
[INFO] --- maven-release-plugin:2.4.1:prepare (default-cli) @ uCMDB-PatternDev ---
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: **\pom.xml.tag, **\pom.xml.branch,
**\pom.xml.releaseBackup, **\pom.xml.backup, **\release.properties,
**\pom.xml.next
[INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password *
--wide"
[INFO] Working directory: D:\RTCBuildWorkspace\EI-Discovery2\EI AS-ITAM uCMDB
Pattern DEV
[ERROR] Error: Problem running 'status':
Current directory is not shared. Run from a shared directory.
Thanks,
Robert
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, April 29, 2013 11:25 AM
To: Maven Users List
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
Perhaps Chris Graham might be able to help... given that from what I
understand IBM decided not to let him go!!! Of course that assumes he has
access to the toolchain!
On 29 April 2013 16:07, Wayne Fay wrote:
Automatically remove version overrides from child POMs
Hi, We're using a parent POM which manages the versions of tens of dependencies. I occasionally encounter modules within my group that override some of those managed versions. Assuming the overrides are not legit, is there an automatic way to remove them from the child POMs? I was hoping that the versions:update-child-modules mojo would help, but it doesn't seem to do what I need. Thanks, Robert
RE: Maven-release-plugin AND IBM RTC build engine...
Hi Eric,
I am using Jazz SCM.
It's even more painful as I don't have direct access to the build
server (I have to go through support to even do simple experiments).
If you see my later emails it's been narrowed down to scm status
command on the build server.
Nothing to do with the release-plugin itself.
Thanks,
Robert
-Original Message-
From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
Sent: Friday, May 03, 2013 4:48 PM
To: users@maven.apache.org
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
Doing a Maven release can be tricky if you are having problems with your
SCM plugin. It took me a long time to get release to work with Perforce
(but it still does not work properly), and you would think that would
just work.
Are you using the Jazz SCM or something else?
Cheers, Eric
On 2013-05-03 9:34 AM, Zanzerkia, Robert wrote:
> I did few more experiments...
> 1) Renamed the RTC component so there is no space in the name.
> 2) Made sure directory has permission for build account etc.
> 3) Experimented by replacing maven command to just mvn scm:status and that
> works without error.
> So it's only via release-plug-in we get the error on scm status command.
>
> Since replease-plug-in works on my laptop this is an issue on
> interaction between maven, release-plugin and "Jazz build engine"
> I re-ran the RTC build with -X switch in maven to get detailed log so
> we can compare against release.log (one from my laptop).
>Thanks,
> Robert
> PS: I have attached RTC_JAZZ-Build.log from build server.
>
> Working release.log
> [DEBUG] repositoryWorkspace - EI_9.05_Release_Snapshot
> [DEBUG] Executing status command...
> [INFO] Executing: cmd.exe /X /C "scm status --username a408072 --password
> * --wide"
> [INFO] Working directory: C:\Documents and
> Settings\a408072.DMN1\workspace301-EI-9.05_Rel\EI AS-ITAM uCMDB Pattern DEV
> [DEBUG] Consumed line :Workspace: (1189) "EI_9.05_Release_Snapshot" <->
> (1001) "EI AS-ITAM uCMDB 9.02 EI Stream"
>
>
> NOT working RTC build lines.
> [DEBUG] repositoryWorkspace - srvrtcbuild-EI-AS-ITAM-PatternDEV-DEV_Release_WS
> [DEBUG] Executing status command...
> [INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password
> * --wide"
> [INFO] Working directory: D:\RTCBuildWorkspace\EI-ITAMTEST\uCMDBPackages
> [DEBUG] ErrorConsumer.consumeLine: Problem running 'status':
> [DEBUG] ErrorConsumer.consumeLine: Current directory is not shared. Run from
> a shared directory.
> [ERROR] Error: Problem running 'status':
> Current directory is not shared. Run from a shared directory.
>
>
> -Original Message-
> From: Zanzerkia, Robert
> Sent: Tuesday, April 30, 2013 11:56 AM
> To: Maven Users List
> Subject: RE: Maven-release-plugin AND IBM RTC build engine...
>
> Hi,
> Actually it was Chris who helped me... Thanks Chris.
>
> When I said NO access to RTC Build engine I meant for the physical server
> where the build runs.
> We have a support group that manages these servers which is why I don't
> have the direct access.
> (Yes that makes it more difficult to trouble shoot).
>
> I am working with the local person to trouble shoot the issue.
>
> The issue comes down to the scm -status command where on my laptop it works
> fine but on the RTC build engine it gives below error.
>
> We have defined
> -DworkingDirectory = D:\temp\Maven (for the plugin working directory).
> repository local directory =
> D:\data\mavenrepo\ei_itam_discovery
> RTC load directory: load directory = ${BUILDWORKSPACE}\EI-Discovery2
>
>
> [INFO] --- maven-release-plugin:2.4.1:prepare (default-cli) @
> uCMDB-PatternDev ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **\pom.xml.tag, **\pom.xml.branch,
> **\pom.xml.releaseBackup, **\pom.xml.backup, **\release.properties,
> **\pom.xml.next
> [INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password
> * --wide"
> [INFO] Working directory: D:\RTCBuildWorkspace\EI-Discovery2\EI AS-ITAM uCMDB
> Pattern DEV
> [ERROR] Error: Problem running 'status':
> Current directory is not shared. Run from a shared directory.
>
> Thanks,
> Robert
>
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Monday, April 29, 2013 11:25 AM
> To: Maven Users List
> Subject: Re: Maven-release-plugin AND IBM RTC build engine...
>
> Perhaps Chris Graham might be able to help... given that from what I
> understand IBM decided not to let him go!!! Of course that assumes he has
> access to the toolchain!
>
>
> On 29 April 2013 16:07, Wayne Fay wrote:
>
>>>I still DO NOT have the release plug-in working with RTC build engine.
>> ...
>>> work as well, unfortunately I don't have access to RTC build engine...
>> And this is exactly the reason why the release plugin does not work
>> with RTC build engine.
>>
>> If you don't have access to RT
Re: Can Maven recover from OutOfMemoryErrors during JUnit test runs?
I don't know about newer jdk versions. If you google-fu tokenPollerProtection I'm sure you'll end up with the original tomcat issue, which may contain more details and references to sun bug reports. As far as I can understand, it mostly applies to unloading of applications; which would seem to indicate you're going to have memory issues if doing hot redeployment etc, probably nothing significant on a production server with conservative redeployment routines. Kristian 2013/5/3 laredotornado-3 > Thanks for the replies. > > Andreas, I added the reuseForks option and combined wiht an increased heap > size everything runs great. > > Kristian, We'll eventually be running our app on Jboss 7.1.1 with Java 6. > Is the bug you mention somethign Sun addressed in newer JDKs? - Dave > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Can-Maven-recover-from-OutOfMemoryErrors-during-JUnit-test-runs-tp5754845p5754872.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven-release-plugin AND IBM RTC build engine...
Doing a Maven release can be tricky if you are having problems with your
SCM plugin. It took me a long time to get release to work with Perforce
(but it still does not work properly), and you would think that would
just work.
Are you using the Jazz SCM or something else?
Cheers, Eric
On 2013-05-03 9:34 AM, Zanzerkia, Robert wrote:
I did few more experiments...
1) Renamed the RTC component so there is no space in the name.
2) Made sure directory has permission for build account etc.
3) Experimented by replacing maven command to just mvn scm:status and that
works without error.
So it's only via release-plug-in we get the error on scm status command.
Since replease-plug-in works on my laptop this is an issue on interaction between
maven, release-plugin and "Jazz build engine"
I re-ran the RTC build with -X switch in maven to get detailed log so
we can compare against release.log (one from my laptop).
Thanks,
Robert
PS: I have attached RTC_JAZZ-Build.log from build server.
Working release.log
[DEBUG] repositoryWorkspace - EI_9.05_Release_Snapshot
[DEBUG] Executing status command...
[INFO] Executing: cmd.exe /X /C "scm status --username a408072 --password *
--wide"
[INFO] Working directory: C:\Documents and
Settings\a408072.DMN1\workspace301-EI-9.05_Rel\EI AS-ITAM uCMDB Pattern DEV
[DEBUG] Consumed line :Workspace: (1189) "EI_9.05_Release_Snapshot" <-> (1001) "EI
AS-ITAM uCMDB 9.02 EI Stream"
NOT working RTC build lines.
[DEBUG] repositoryWorkspace - srvrtcbuild-EI-AS-ITAM-PatternDEV-DEV_Release_WS
[DEBUG] Executing status command...
[INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password *
--wide"
[INFO] Working directory: D:\RTCBuildWorkspace\EI-ITAMTEST\uCMDBPackages
[DEBUG] ErrorConsumer.consumeLine: Problem running 'status':
[DEBUG] ErrorConsumer.consumeLine: Current directory is not shared. Run from a
shared directory.
[ERROR] Error: Problem running 'status':
Current directory is not shared. Run from a shared directory.
-Original Message-
From: Zanzerkia, Robert
Sent: Tuesday, April 30, 2013 11:56 AM
To: Maven Users List
Subject: RE: Maven-release-plugin AND IBM RTC build engine...
Hi,
Actually it was Chris who helped me... Thanks Chris.
When I said NO access to RTC Build engine I meant for the physical server
where the build runs.
We have a support group that manages these servers which is why I don't have
the direct access.
(Yes that makes it more difficult to trouble shoot).
I am working with the local person to trouble shoot the issue.
The issue comes down to the scm -status command where on my laptop it works
fine but on the RTC build engine it gives below error.
We have defined
-DworkingDirectory = D:\temp\Maven (for the plugin working directory).
repository local directory =
D:\data\mavenrepo\ei_itam_discovery
RTC load directory: load directory = ${BUILDWORKSPACE}\EI-Discovery2
[INFO] --- maven-release-plugin:2.4.1:prepare (default-cli) @ uCMDB-PatternDev ---
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: **\pom.xml.tag, **\pom.xml.branch,
**\pom.xml.releaseBackup, **\pom.xml.backup, **\release.properties,
**\pom.xml.next
[INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password *
--wide"
[INFO] Working directory: D:\RTCBuildWorkspace\EI-Discovery2\EI AS-ITAM uCMDB
Pattern DEV
[ERROR] Error: Problem running 'status':
Current directory is not shared. Run from a shared directory.
Thanks,
Robert
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, April 29, 2013 11:25 AM
To: Maven Users List
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
Perhaps Chris Graham might be able to help... given that from what I
understand IBM decided not to let him go!!! Of course that assumes he has
access to the toolchain!
On 29 April 2013 16:07, Wayne Fay wrote:
I still DO NOT have the release plug-in working with RTC build engine.
...
work as well, unfortunately I don't have access to RTC build engine...
And this is exactly the reason why the release plugin does not work
with RTC build engine.
If you don't have access to RTC build engine, yet you are a customer
of IBM's and use their tools etc, how can any random open source
developer be granted the necessary access to these tools (Jazz, RTC,
etc) so the release plugin can be adapted as needed to work along with
it?
This is why Maven plugins for proprietary tools will ALWAYS lag in
functionality behind open source tools. For all intents, it
practically requires the VENDOR to put in the effort to build/adapt
the plugin for their products. If you have the ability to do so, I'd
open a bug/ticket with IBM and ask them to support the Maven release
plugin, otherwise I doubt this functionality will ever be added by
anyone else.
Wayne
-
To unsu
Re: Can Maven recover from OutOfMemoryErrors during JUnit test runs?
Thanks for the replies. Andreas, I added the reuseForks option and combined wiht an increased heap size everything runs great. Kristian, We'll eventually be running our app on Jboss 7.1.1 with Java 6. Is the bug you mention somethign Sun addressed in newer JDKs? - Dave -- View this message in context: http://maven.40175.n5.nabble.com/Can-Maven-recover-from-OutOfMemoryErrors-during-JUnit-test-runs-tp5754845p5754872.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven-release-plugin AND IBM RTC build engine...
Wayne, Ok this proves that it has nothing to do with release-plug-in. D:\RTCBuildWorkspace\EI-ITAMTEST\uCMDBPackages>scm status --username srvrtcbuild -password --wide Problem running 'status': Current directory is not shared. Run from a shared directory. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Friday, May 03, 2013 2:24 PM To: Maven Users List Subject: Re: Maven-release-plugin AND IBM RTC build engine... > [INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password > * --wide" > [INFO] Working directory: D:\RTCBuildWorkspace\EI-ITAMTEST\uCMDBPackages > [DEBUG] ErrorConsumer.consumeLine: Problem running 'status': > [DEBUG] ErrorConsumer.consumeLine: Current directory is not shared. Run from > a shared directory. Go to that working directory. Type that command "scm status --username svrtcbuild --password (whatever) --wide". Then come back here and tell us what the output was. I still think this is a local SCM issue (Jazz) and all evidence you've provided supports that. Wayne - 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: Can Maven recover from OutOfMemoryErrors during JUnit test runs?
Generally, "no" - we do not recover from memory leaks. The specific memory leak you're referring to here is actually one of the well-known jdk memory leaks. I've seen this solved in tomcat with 'tokenPollerProtection'. Surefire will have the same kind of leak if you're using forkmode=never; we don't have the kind of protection tomcat has (and probably don't need it!) Any other forkmode should be immune from this problem, apart from what can leak inside the fork itself. Also remember to tweak memory settings with either MAVEN_OPTS or within the forked process by -Xmx1024m -XX:MaxPermSize=256m Kristian 2013/5/3 laredotornado-3 > Hi, > > I'm using Maven 3.0.3. Is it possible to configure Maven or the Surefire > plugin to recover from OutOfMemoryErrors? I notice with my JUnit tests, if > one test from file A fails with an "OutOfMemoryError," all subsequent tests > in my Maven Junit run (even those from different files) fail with > OutOfMemoryErrors. When I run the files in isolation (e.g. > "-Dtest=FileATest"), the test runs fine. > > I'm using the Surefire 2.14.1: > > > org.apache.maven.plugins > > maven-surefire-plugin > 2.14.1 > > > Thanks for any wisdom, - Dave > > > Here's an example of one of the OutOfMemoryErrors … > > Exception in thread "Poller SunPKCS11-Darwin" java.lang.OutOfMemoryError: > Java heap space > at sun.security.pkcs11.wrapper.PKCS11.C_GetSlotInfo(Native Method) > at sun.security.pkcs11.SunPKCS11.initToken(SunPKCS11.java:767) > at sun.security.pkcs11.SunPKCS11.access$100(SunPKCS11.java:42) > at > sun.security.pkcs11.SunPKCS11$TokenPoller.run(SunPKCS11.java:700) > at java.lang.Thread.run(Thread.java:680) > > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Can-Maven-recover-from-OutOfMemoryErrors-during-JUnit-test-runs-tp5754845.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven-release-plugin AND IBM RTC build engine...
> [INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password > * --wide" > [INFO] Working directory: D:\RTCBuildWorkspace\EI-ITAMTEST\uCMDBPackages > [DEBUG] ErrorConsumer.consumeLine: Problem running 'status': > [DEBUG] ErrorConsumer.consumeLine: Current directory is not shared. Run from > a shared directory. Go to that working directory. Type that command "scm status --username svrtcbuild --password (whatever) --wide". Then come back here and tell us what the output was. I still think this is a local SCM issue (Jazz) and all evidence you've provided supports that. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Can Maven recover from OutOfMemoryErrors during JUnit test runs?
Hi, The safest option is to configure surefire to spawn a new JVM for each test class: false [1]. That will of cause give you some considerable bump in the execution time. Good luck, Andreas [1] http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html 2013/5/3 laredotornado-3 > Hi, > > I'm using Maven 3.0.3. Is it possible to configure Maven or the Surefire > plugin to recover from OutOfMemoryErrors? I notice with my JUnit tests, if > one test from file A fails with an "OutOfMemoryError," all subsequent tests > in my Maven Junit run (even those from different files) fail with > OutOfMemoryErrors. When I run the files in isolation (e.g. > "-Dtest=FileATest"), the test runs fine. > > I'm using the Surefire 2.14.1: > > > org.apache.maven.plugins > > maven-surefire-plugin > 2.14.1 > > > Thanks for any wisdom, - Dave > > > Here's an example of one of the OutOfMemoryErrors … > > Exception in thread "Poller SunPKCS11-Darwin" java.lang.OutOfMemoryError: > Java heap space > at sun.security.pkcs11.wrapper.PKCS11.C_GetSlotInfo(Native Method) > at sun.security.pkcs11.SunPKCS11.initToken(SunPKCS11.java:767) > at sun.security.pkcs11.SunPKCS11.access$100(SunPKCS11.java:42) > at > sun.security.pkcs11.SunPKCS11$TokenPoller.run(SunPKCS11.java:700) > at java.lang.Thread.run(Thread.java:680) > > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Can-Maven-recover-from-OutOfMemoryErrors-during-JUnit-test-runs-tp5754845.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
RE: Maven-release-plugin AND IBM RTC build engine...
What if ... the directory is not actually shared ... In the windows sense.
On the command line of the build server type "net share" and see if the
directory is on the share list.
From: "Zanzerkia, Robert"
To: Maven Users List ,
Date: 05/03/2013 09:35 AM
Subject:RE: Maven-release-plugin AND IBM RTC build engine...
I did few more experiments...
1) Renamed the RTC component so there is no space in the name.
2) Made sure directory has permission for build account etc.
3) Experimented by replacing maven command to just mvn scm:status and that
works without error.
So it's only via release-plug-in we get the error on scm
status command.
Since replease-plug-in works on my laptop this is an
issue on interaction between maven, release-plugin and "Jazz build engine"
I re-ran the RTC build with -X switch in maven to get
detailed log so we can compare against release.log (one from my laptop).
Thanks,
Robert
PS: I have attached RTC_JAZZ-Build.log from build server.
Working release.log
[DEBUG] repositoryWorkspace - EI_9.05_Release_Snapshot
[DEBUG] Executing status command...
[INFO] Executing: cmd.exe /X /C "scm status --username a408072 --password
* --wide"
[INFO] Working directory: C:\Documents and
Settings\a408072.DMN1\workspace301-EI-9.05_Rel\EI AS-ITAM uCMDB Pattern
DEV
[DEBUG] Consumed line :Workspace: (1189) "EI_9.05_Release_Snapshot" <->
(1001) "EI AS-ITAM uCMDB 9.02 EI Stream"
NOT working RTC build lines.
[DEBUG] repositoryWorkspace -
srvrtcbuild-EI-AS-ITAM-PatternDEV-DEV_Release_WS
[DEBUG] Executing status command...
[INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild
--password * --wide"
[INFO] Working directory: D:\RTCBuildWorkspace\EI-ITAMTEST\uCMDBPackages
[DEBUG] ErrorConsumer.consumeLine: Problem running 'status':
[DEBUG] ErrorConsumer.consumeLine: Current directory is not shared. Run
from a shared directory.
[ERROR] Error: Problem running 'status':
Current directory is not shared. Run from a shared directory.
-Original Message-
From: Zanzerkia, Robert
Sent: Tuesday, April 30, 2013 11:56 AM
To: Maven Users List
Subject: RE: Maven-release-plugin AND IBM RTC build engine...
Hi,
Actually it was Chris who helped me... Thanks Chris.
When I said NO access to RTC Build engine I meant for the physical server
where the build runs.
We have a support group that manages these servers which is why I don't
have the direct access.
(Yes that makes it more difficult to trouble shoot).
I am working with the local person to trouble shoot the issue.
The issue comes down to the scm -status command where on my laptop it
works fine but on the RTC build engine it gives below error.
We have defined
-DworkingDirectory = D:\temp\Maven (for the plugin working directory).
repository local directory =
D:\data\mavenrepo\ei_itam_discovery
RTC load directory: load directory = ${BUILDWORKSPACE}\EI-Discovery2
[INFO] --- maven-release-plugin:2.4.1:prepare (default-cli) @
uCMDB-PatternDev ---
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: **\pom.xml.tag, **\pom.xml.branch,
**\pom.xml.releaseBackup, **\pom.xml.backup, **\release.properties,
**\pom.xml.next
[INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild
--password * --wide"
[INFO] Working directory: D:\RTCBuildWorkspace\EI-Discovery2\EI AS-ITAM
uCMDB Pattern DEV
[ERROR] Error: Problem running 'status':
Current directory is not shared. Run from a shared directory.
Thanks,
Robert
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, April 29, 2013 11:25 AM
To: Maven Users List
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
Perhaps Chris Graham might be able to help... given that from what I
understand IBM decided not to let him go!!! Of course that assumes he has
access to the toolchain!
On 29 April 2013 16:07, Wayne Fay wrote:
> > I still DO NOT have the release plug-in working with RTC build
engine.
> ...
> > work as well, unfortunately I don't have access to RTC build engine...
>
> And this is exactly the reason why the release plugin does not work
> with RTC build engine.
>
> If you don't have access to RTC build engine, yet you are a customer
> of IBM's and use their tools etc, how can any random open source
> developer be granted the necessary access to these tools (Jazz, RTC,
> etc) so the release plugin can be adapted as needed to work along with
> it?
>
> This is why Maven plugins for proprietary tools will ALWAYS lag in
> functionality behind open source tools. For all intents, it
> practically requires the VENDOR to put in the effort to build/adapt
> the plugin for their products. If you have the ability to do so, I'd
> open a bug/ticket with IBM and ask them to support the Maven release
> plugin, otherwise I doubt this functionality will ever be added by
> anyone else.
>
> Wayne
>
> ---
Can Maven recover from OutOfMemoryErrors during JUnit test runs?
Hi, I'm using Maven 3.0.3. Is it possible to configure Maven or the Surefire plugin to recover from OutOfMemoryErrors? I notice with my JUnit tests, if one test from file A fails with an "OutOfMemoryError," all subsequent tests in my Maven Junit run (even those from different files) fail with OutOfMemoryErrors. When I run the files in isolation (e.g. "-Dtest=FileATest"), the test runs fine. I'm using the Surefire 2.14.1: org.apache.maven.plugins maven-surefire-plugin 2.14.1 Thanks for any wisdom, - Dave Here's an example of one of the OutOfMemoryErrors … Exception in thread "Poller SunPKCS11-Darwin" java.lang.OutOfMemoryError: Java heap space at sun.security.pkcs11.wrapper.PKCS11.C_GetSlotInfo(Native Method) at sun.security.pkcs11.SunPKCS11.initToken(SunPKCS11.java:767) at sun.security.pkcs11.SunPKCS11.access$100(SunPKCS11.java:42) at sun.security.pkcs11.SunPKCS11$TokenPoller.run(SunPKCS11.java:700) at java.lang.Thread.run(Thread.java:680) -- View this message in context: http://maven.40175.n5.nabble.com/Can-Maven-recover-from-OutOfMemoryErrors-during-JUnit-test-runs-tp5754845.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven-release-plugin AND IBM RTC build engine...
I did few more experiments...
1) Renamed the RTC component so there is no space in the name.
2) Made sure directory has permission for build account etc.
3) Experimented by replacing maven command to just mvn scm:status and that
works without error.
So it's only via release-plug-in we get the error on scm status command.
Since replease-plug-in works on my laptop this is an issue on
interaction between maven, release-plugin and "Jazz build engine"
I re-ran the RTC build with -X switch in maven to get detailed log so
we can compare against release.log (one from my laptop).
Thanks,
Robert
PS: I have attached RTC_JAZZ-Build.log from build server.
Working release.log
[DEBUG] repositoryWorkspace - EI_9.05_Release_Snapshot
[DEBUG] Executing status command...
[INFO] Executing: cmd.exe /X /C "scm status --username a408072 --password *
--wide"
[INFO] Working directory: C:\Documents and
Settings\a408072.DMN1\workspace301-EI-9.05_Rel\EI AS-ITAM uCMDB Pattern DEV
[DEBUG] Consumed line :Workspace: (1189) "EI_9.05_Release_Snapshot" <-> (1001)
"EI AS-ITAM uCMDB 9.02 EI Stream"
NOT working RTC build lines.
[DEBUG] repositoryWorkspace - srvrtcbuild-EI-AS-ITAM-PatternDEV-DEV_Release_WS
[DEBUG] Executing status command...
[INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password
* --wide"
[INFO] Working directory: D:\RTCBuildWorkspace\EI-ITAMTEST\uCMDBPackages
[DEBUG] ErrorConsumer.consumeLine: Problem running 'status':
[DEBUG] ErrorConsumer.consumeLine: Current directory is not shared. Run from a
shared directory.
[ERROR] Error: Problem running 'status':
Current directory is not shared. Run from a shared directory.
-Original Message-
From: Zanzerkia, Robert
Sent: Tuesday, April 30, 2013 11:56 AM
To: Maven Users List
Subject: RE: Maven-release-plugin AND IBM RTC build engine...
Hi,
Actually it was Chris who helped me... Thanks Chris.
When I said NO access to RTC Build engine I meant for the physical server
where the build runs.
We have a support group that manages these servers which is why I don't have
the direct access.
(Yes that makes it more difficult to trouble shoot).
I am working with the local person to trouble shoot the issue.
The issue comes down to the scm -status command where on my laptop it works
fine but on the RTC build engine it gives below error.
We have defined
-DworkingDirectory = D:\temp\Maven (for the plugin working directory).
repository local directory =
D:\data\mavenrepo\ei_itam_discovery
RTC load directory: load directory = ${BUILDWORKSPACE}\EI-Discovery2
[INFO] --- maven-release-plugin:2.4.1:prepare (default-cli) @ uCMDB-PatternDev
---
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: **\pom.xml.tag, **\pom.xml.branch,
**\pom.xml.releaseBackup, **\pom.xml.backup, **\release.properties,
**\pom.xml.next
[INFO] Executing: cmd.exe /X /C "scm status --username srvrtcbuild --password
* --wide"
[INFO] Working directory: D:\RTCBuildWorkspace\EI-Discovery2\EI AS-ITAM uCMDB
Pattern DEV
[ERROR] Error: Problem running 'status':
Current directory is not shared. Run from a shared directory.
Thanks,
Robert
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, April 29, 2013 11:25 AM
To: Maven Users List
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
Perhaps Chris Graham might be able to help... given that from what I
understand IBM decided not to let him go!!! Of course that assumes he has
access to the toolchain!
On 29 April 2013 16:07, Wayne Fay wrote:
> > I still DO NOT have the release plug-in working with RTC build engine.
> ...
> > work as well, unfortunately I don't have access to RTC build engine...
>
> And this is exactly the reason why the release plugin does not work
> with RTC build engine.
>
> If you don't have access to RTC build engine, yet you are a customer
> of IBM's and use their tools etc, how can any random open source
> developer be granted the necessary access to these tools (Jazz, RTC,
> etc) so the release plugin can be adapted as needed to work along with
> it?
>
> This is why Maven plugins for proprietary tools will ALWAYS lag in
> functionality behind open source tools. For all intents, it
> practically requires the VENDOR to put in the effort to build/adapt
> the plugin for their products. If you have the ability to do so, I'd
> open a bug/ticket with IBM and ask them to support the Maven release
> plugin, otherwise I doubt this functionality will ever be added by
> anyone else.
>
> Wayne
>
> -
> 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.ap
Re: cannot resolve POM with classifier?
Thanks a lot for your suggestions Stephen, that's priceless help! :)
Have a nice day, all the best!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, May 3, 2013 at 12:32 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Another solution is the maven-shade-plugin can publish the shaded pom to a
> different GAV
>
>
> On 3 May 2013 11:31, Stephen Connolly >wrote:
>
> > I'd either do it something like
> >
> >
> > maven-deploy-plugin
> >
> >
> > public-artifact
> > deploy
> >
> > deploy-file
> >
> >
> > ${project.build.directory}/public-pom.xml
> > ${project.build.directory}/some.jar
> >
> >
> ${project.build.directory}/some-javadoc.jar,${project.build.directory}/some-sources.jar
> > jar,jar
> > javadoc,sources
> >
> >
> >
> >
> >
> > Or I would use the non-maven-jar maven plugin and the dependency:copy
> > plugins keeping the public pom as part of the reactor (for the case where
> > you need to use the public pom as a dependency within your reactor
> >
> >
> > On 3 May 2013 11:25, Stephen Connolly >wrote:
> >
> >> yep
> >>
> >>
> >> On 3 May 2013 11:18, Simone Tripodi wrote:
> >>
> >>> Thanks for the suggestion, Stephen!
> >>>
> >>> so you mean that rather than attaching the new pom to the original
> >>> project,
> >>> I should use the deployer to deploy a separated artifact, right?
> >>>
> >>> TIA, all the best,
> >>> -Simo
> >>>
> >>>
> >>> http://people.apache.org/~simonetripodi/
> >>> http://simonetripodi.livejournal.com/
> >>> http://twitter.com/simonetripodi
> >>> http://www.99soft.org/
> >>>
> >>>
> >>> On Thu, May 2, 2013 at 2:21 PM, Stephen Connolly <
> >>> stephen.alan.conno...@gmail.com> wrote:
> >>>
> >>> > Deploy at a different GAV.
> >>> >
> >>> > Used do this at a former employers. Internally we'd use one GA and
> the
> >>> > publish externally at a different GA (same V)
> >>> >
> >>> > On Thursday, 2 May 2013, Simone Tripodi wrote:
> >>> >
> >>> > > Hi all,
> >>> > >
> >>> > > I am in the scenario where a POM is generated and attached in the
> >>> main
> >>> > > project, then will be deployed on the repo; that POM contains all
> >>> > required
> >>> > > dependencies my users need when developing custom applications.
> >>> > >
> >>> > > The issue comes when I would like to resolve the generated prom in
> an
> >>> > > external project, becauee IIUC there is no way to:
> >>> > >
> >>> > > * inherit from a parent pom with a classifier;
> >>> > >
> >>> > > * declare its dependency in `dependencyManagement` with scope
> >>> `import`.
> >>> > >
> >>> > > Does that mean that POM cannot have classifiers? Do you have any
> >>> > > alternative solution?
> >>> > > TIA!
> >>> > > -Simo
> >>> > >
> >>> > > http://people.apache.org/~simonetripodi/
> >>> > > http://simonetripodi.livejournal.com/
> >>> > > http://twitter.com/simonetripodi
> >>> > > http://www.99soft.org/
> >>> > >
> >>> >
> >>> >
> >>> > --
> >>> > Sent from my phone
> >>> >
> >>>
> >>
> >>
> >
>
Re: cannot resolve POM with classifier?
Another solution is the maven-shade-plugin can publish the shaded pom to a
different GAV
On 3 May 2013 11:31, Stephen Connolly wrote:
> I'd either do it something like
>
>
> maven-deploy-plugin
>
>
> public-artifact
> deploy
>
> deploy-file
>
>
> ${project.build.directory}/public-pom.xml
> ${project.build.directory}/some.jar
>
> ${project.build.directory}/some-javadoc.jar,${project.build.directory}/some-sources.jar
> jar,jar
> javadoc,sources
>
>
>
>
>
> Or I would use the non-maven-jar maven plugin and the dependency:copy
> plugins keeping the public pom as part of the reactor (for the case where
> you need to use the public pom as a dependency within your reactor
>
>
> On 3 May 2013 11:25, Stephen Connolly wrote:
>
>> yep
>>
>>
>> On 3 May 2013 11:18, Simone Tripodi wrote:
>>
>>> Thanks for the suggestion, Stephen!
>>>
>>> so you mean that rather than attaching the new pom to the original
>>> project,
>>> I should use the deployer to deploy a separated artifact, right?
>>>
>>> TIA, all the best,
>>> -Simo
>>>
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>> On Thu, May 2, 2013 at 2:21 PM, Stephen Connolly <
>>> stephen.alan.conno...@gmail.com> wrote:
>>>
>>> > Deploy at a different GAV.
>>> >
>>> > Used do this at a former employers. Internally we'd use one GA and the
>>> > publish externally at a different GA (same V)
>>> >
>>> > On Thursday, 2 May 2013, Simone Tripodi wrote:
>>> >
>>> > > Hi all,
>>> > >
>>> > > I am in the scenario where a POM is generated and attached in the
>>> main
>>> > > project, then will be deployed on the repo; that POM contains all
>>> > required
>>> > > dependencies my users need when developing custom applications.
>>> > >
>>> > > The issue comes when I would like to resolve the generated prom in an
>>> > > external project, becauee IIUC there is no way to:
>>> > >
>>> > > * inherit from a parent pom with a classifier;
>>> > >
>>> > > * declare its dependency in `dependencyManagement` with scope
>>> `import`.
>>> > >
>>> > > Does that mean that POM cannot have classifiers? Do you have any
>>> > > alternative solution?
>>> > > TIA!
>>> > > -Simo
>>> > >
>>> > > http://people.apache.org/~simonetripodi/
>>> > > http://simonetripodi.livejournal.com/
>>> > > http://twitter.com/simonetripodi
>>> > > http://www.99soft.org/
>>> > >
>>> >
>>> >
>>> > --
>>> > Sent from my phone
>>> >
>>>
>>
>>
>
Re: cannot resolve POM with classifier?
I'd either do it something like
maven-deploy-plugin
public-artifact
deploy
deploy-file
${project.build.directory}/public-pom.xml
${project.build.directory}/some.jar
${project.build.directory}/some-javadoc.jar,${project.build.directory}/some-sources.jar
jar,jar
javadoc,sources
Or I would use the non-maven-jar maven plugin and the dependency:copy
plugins keeping the public pom as part of the reactor (for the case where
you need to use the public pom as a dependency within your reactor
On 3 May 2013 11:25, Stephen Connolly wrote:
> yep
>
>
> On 3 May 2013 11:18, Simone Tripodi wrote:
>
>> Thanks for the suggestion, Stephen!
>>
>> so you mean that rather than attaching the new pom to the original
>> project,
>> I should use the deployer to deploy a separated artifact, right?
>>
>> TIA, all the best,
>> -Simo
>>
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Thu, May 2, 2013 at 2:21 PM, Stephen Connolly <
>> stephen.alan.conno...@gmail.com> wrote:
>>
>> > Deploy at a different GAV.
>> >
>> > Used do this at a former employers. Internally we'd use one GA and the
>> > publish externally at a different GA (same V)
>> >
>> > On Thursday, 2 May 2013, Simone Tripodi wrote:
>> >
>> > > Hi all,
>> > >
>> > > I am in the scenario where a POM is generated and attached in the main
>> > > project, then will be deployed on the repo; that POM contains all
>> > required
>> > > dependencies my users need when developing custom applications.
>> > >
>> > > The issue comes when I would like to resolve the generated prom in an
>> > > external project, becauee IIUC there is no way to:
>> > >
>> > > * inherit from a parent pom with a classifier;
>> > >
>> > > * declare its dependency in `dependencyManagement` with scope
>> `import`.
>> > >
>> > > Does that mean that POM cannot have classifiers? Do you have any
>> > > alternative solution?
>> > > TIA!
>> > > -Simo
>> > >
>> > > http://people.apache.org/~simonetripodi/
>> > > http://simonetripodi.livejournal.com/
>> > > http://twitter.com/simonetripodi
>> > > http://www.99soft.org/
>> > >
>> >
>> >
>> > --
>> > Sent from my phone
>> >
>>
>
>
Re: cannot resolve POM with classifier?
yep On 3 May 2013 11:18, Simone Tripodi wrote: > Thanks for the suggestion, Stephen! > > so you mean that rather than attaching the new pom to the original project, > I should use the deployer to deploy a separated artifact, right? > > TIA, all the best, > -Simo > > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > > On Thu, May 2, 2013 at 2:21 PM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > Deploy at a different GAV. > > > > Used do this at a former employers. Internally we'd use one GA and the > > publish externally at a different GA (same V) > > > > On Thursday, 2 May 2013, Simone Tripodi wrote: > > > > > Hi all, > > > > > > I am in the scenario where a POM is generated and attached in the main > > > project, then will be deployed on the repo; that POM contains all > > required > > > dependencies my users need when developing custom applications. > > > > > > The issue comes when I would like to resolve the generated prom in an > > > external project, becauee IIUC there is no way to: > > > > > > * inherit from a parent pom with a classifier; > > > > > > * declare its dependency in `dependencyManagement` with scope > `import`. > > > > > > Does that mean that POM cannot have classifiers? Do you have any > > > alternative solution? > > > TIA! > > > -Simo > > > > > > http://people.apache.org/~simonetripodi/ > > > http://simonetripodi.livejournal.com/ > > > http://twitter.com/simonetripodi > > > http://www.99soft.org/ > > > > > > > > > -- > > Sent from my phone > > >
Re: cannot resolve POM with classifier?
Thanks for the suggestion, Stephen! so you mean that rather than attaching the new pom to the original project, I should use the deployer to deploy a separated artifact, right? TIA, all the best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Thu, May 2, 2013 at 2:21 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Deploy at a different GAV. > > Used do this at a former employers. Internally we'd use one GA and the > publish externally at a different GA (same V) > > On Thursday, 2 May 2013, Simone Tripodi wrote: > > > Hi all, > > > > I am in the scenario where a POM is generated and attached in the main > > project, then will be deployed on the repo; that POM contains all > required > > dependencies my users need when developing custom applications. > > > > The issue comes when I would like to resolve the generated prom in an > > external project, becauee IIUC there is no way to: > > > > * inherit from a parent pom with a classifier; > > > > * declare its dependency in `dependencyManagement` with scope `import`. > > > > Does that mean that POM cannot have classifiers? Do you have any > > alternative solution? > > TIA! > > -Simo > > > > http://people.apache.org/~simonetripodi/ > > http://simonetripodi.livejournal.com/ > > http://twitter.com/simonetripodi > > http://www.99soft.org/ > > > > > -- > Sent from my phone >
Re: Building selected projects with nested aggregators
Hi,
You may actually want to check out the difference between -am ("also make
dependencies") and -amd ("also make dependents"). In conjunction with -pl
called from your topmost aggregator directory, you should pretty much get
what you need. I guess. ;-)
Am Freitag, 3. Mai 2013 schrieb spoots :
> Oops, just realised this scenario doesn't quite reflect my situation.
>
> Please also imagine in the attached image that there is no parent/child
> relationship between "webapps" and it's sub-modules, i.e. it's purely an
> aggregator POM
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Building-selected-projects-with-nested-aggregators-tp5753572p5754823.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: Executing tests in a newer JVM version than the one used to build project.
You can also use the property "jvm" in the surefire configuration to specify the path to the jvm you want to use to execute your tests. http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#jvm Am Donnerstag, 2. Mai 2013 schrieb Stephen Connolly : > On Thursday, 2 May 2013, Jean Tremblay wrote: > > > Hi, > > > > I have a bit of a complicated setup. I need to build my jar file using > > java 1.6, but I need to execute my tests using Java 1.7, as my library > need > > to connect to other libraries built for Java V1.7. > > How can I do that? > > > > I currently set my pom.xml with the following entries: > > > > > > UTF-8 > > 1.6 > > 1.6 > > > > > > > > > > Unfortunately when my test is executed it is also running using v1.6 but > I > > would like to use version 1.7. > > > > Is there a way to tell sure fire (I guess this is the plugin I should > look > > at) to use v1.7 when executing the tests? > > What is exactly choosing the target version of the Java being used for > > testing? > > > > I develop my project library using eclipse. I have set this project to > use > > java 1.6 for this eclipse project. If I tell eclipse to use V1.7 my tests > > are executed in Maven using V1.7 and then my test are all fine. The > problem > > is then that when I build my jar files there are conflicts between the > java > > used by eclipse and the java used by Maven, and it can happen that > suddenly > > the jar file is built with java classes being 1.7 instead of 1.6. > > > > Does anyone have an idea what I should do here? > > > See my answer here: > > http://stackoverflow.com/questions/12414209/compile-maven-module-with-different-java-version/12419643#12419643 > > IIRC you then need to bind a second execution of tool chains after the > compile phase but before the test phase to switch to 1.7 > > > > > Thanks for your help. > > > > Jean > > > > > -- > Sent from my phone >
