Bug 751027 - maven build is failing - wrong tests
Summary: maven build is failing - wrong tests
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: RHQ Project
Classification: Other
Component: Build System
Version: 4.2
Hardware: x86_64
OS: Linux
medium
unspecified vote
Target Milestone: ---
: RHQ 4.3.0
Assignee: Heiko W. Rupp
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-03 09:41 UTC by trash
Modified: 2011-11-30 16:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-04 15:07:55 UTC


Attachments (Terms of Use)
maven output (648.19 KB, text/plain)
2011-11-03 09:41 UTC, trash
no flags Details

Description trash 2011-11-03 09:41:46 UTC
Created attachment 531529 [details]
maven output

Description of problem:

I want to install RHQ for developing. I got an exception "The system-service element is only supported on Red Hat Linux systems". I have a ubuntu server.

my system: 
#uname -a
Linux return0 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 11.10 oneiric

I'm using maven3.
#mvn -version
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)

How reproducible:

I used

mvn -Penterprise,dev -Ddbsetup -DDatabaseTest.nofail  install

for maven. I got 

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on project rhq-ant-bundle-common: There are test failures.

The exception is

java.lang.RuntimeException: Failed to execute bundle deploy file [/home/zendem/projects/rhq/modules/common/ant-bundle/target/test-classes/test-bundle-v1.xml]. Cause: /home/zendem/projects/rhq/modules/common/ant-bundle/target/test-classes/test-bundle-v1.xml:6: The system-service element is only supported on Red Hat Linux systems.
	at org.rhq.bundle.ant.AntLauncher.executeBundleDeployFile(AntLauncher.java:118)
	at org.rhq.bundle.ant.AntLauncherTest.testInstall(AntLauncherTest.java:122)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:158)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:98)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
	at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
	at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
Caused by: /home/seeburger/projects/rhq/modules/common/ant-bundle/target/test-classes/test-bundle-v1.xml:6: The system-service element is only supported on Red Hat Linux systems.
	at org.rhq.bundle.ant.type.SystemServiceType.init(SystemServiceType.java:91)
	at org.rhq.bundle.ant.type.DeploymentUnitType.init(DeploymentUnitType.java:81)
	at org.rhq.bundle.ant.task.BundleTask.execute(BundleTask.java:144)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
	at org.apache.tools.ant.Task.perform(Task.java:348)
	at org.apache.tools.ant.Target.execute(Target.java:390)
	at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:179)
	at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:80)
	at org.rhq.bundle.ant.AntLauncher.executeBundleDeployFile(AntLauncher.java:111)
	... 36 more
... Removed 30 stack frames

  
In attachment is the my maven output

Comment 1 John Mazzitelli 2011-11-03 14:06:58 UTC
that ability for the ant recipe to start the system service (on RH related systems only) was never a feature that was fully designed/baked. We should consider removing it entirely.

The way people do this today is they write their own post-install target in teh ant recipe and start things using normal ant tasks.

Comment 2 Heiko W. Rupp 2011-11-04 14:28:02 UTC
d1e85ac in master checks for presence of RHEL


Note You need to log in before you can comment on or make changes to this bug.