[jira] Commented: (FELIX-1601) Can't run in m2eclipse 0.9.9
[ https://issues.apache.org/jira/browse/FELIX-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781088#action_12781088 ] Fernando Ribeiro commented on FELIX-1601: - Fixed in 0.9.9_200911171109. > Can't run in m2eclipse 0.9.9 > > > Key: FELIX-1601 > URL: https://issues.apache.org/jira/browse/FELIX-1601 > Project: Felix > Issue Type: Bug >Affects Versions: maven-bundle-plugin-2.0.0, maven-bundle-plugin-2.0.1 >Reporter: Fernando Ribeiro > > When running on m2eclipse 0.9.9, I get java.lang.NoSuchMethodError: > org.apache.maven.project.MavenProject.getGoalConfiguration(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Lorg/codehaus/plexus/util/xml/Xpp3Dom. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1601) Can't run in m2eclipse 0.9.9
[ https://issues.apache.org/jira/browse/FELIX-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fernando Ribeiro updated FELIX-1601: Comment: was deleted (was: Asked for confirmation in the M2Eclipse Developers list.) > Can't run in m2eclipse 0.9.9 > > > Key: FELIX-1601 > URL: https://issues.apache.org/jira/browse/FELIX-1601 > Project: Felix > Issue Type: Bug >Affects Versions: maven-bundle-plugin-2.0.0, maven-bundle-plugin-2.0.1 >Reporter: Fernando Ribeiro > > When running on m2eclipse 0.9.9, I get java.lang.NoSuchMethodError: > org.apache.maven.project.MavenProject.getGoalConfiguration(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Lorg/codehaus/plexus/util/xml/Xpp3Dom. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Continuous build updated to Maven 2.2.1
Hey Toni, On Nov 21, 2009, at 18:31 , Toni Menzel wrote: > This is actually "home made" by placing integration tests in the component > under test. > This way you create a chicken egg problem. The tests (executed before bundle > is being packaged, see maven lifecycle) grabs any older version of the > component it finds (matching the group+artifact+version) wich usually not > what you want to test. Good point, I wasn't aware of that. > Solution: put the integration tests into its own projects. Sounds nuts but > is just logical. Would have been nice if it was possible to run the tests after the bundle has been compiled, packaged and installed, but I'll move my integration tests to a separate project. We can also group all integration tests into one big integration test project, which saves us some pom.xml files, but might pose some restrictions as to the testing frameworks people want to use. > Also it would be good to upgrade to exam 1.2.0 (currently 0.6). I did that for the dependencymanager module, but did not want to do it for any of the other projects as I am not sure if everything should still work after a migration. Greetings, Marcel
Re: Continuous build updated to Maven 2.2.1
This is actually "home made" by placing integration tests in the component under test. This way you create a chicken egg problem. The tests (executed before bundle is being packaged, see maven lifecycle) grabs any older version of the component it finds (matching the group+artifact+version) wich usually not what you want to test. Solution: put the integration tests into its own projects. Sounds nuts but is just logical. Also it would be good to upgrade to exam 1.2.0 (currently 0.6). Toni On Sat, Nov 21, 2009 at 5:52 PM, Marcel Offermans < marcel.offerm...@luminis.nl> wrote: > I just updated the continuous build, running on Bamboo, to Maven 2.2.1 > because I needed a feature (compiling tests against a different > source/target JVM than the bundle itself) which seemed to be broken in > earlier versions. > > Initially, after going to the new Maven, a test case failed, but running > the build again made it succeed, so I'm assuming there is some kind of race > condition in the test. See: > > > http://opensource.bamboo.atlassian.com/build/viewTestCaseHistory.action?buildKey=FELIX-DEF&testClassName=org.apache.felix.scr.integration.ServiceBindTest&testCaseName=test_optional_single_static > > Perhaps one of the SCR guys could have a look at this? > > Greetings, Marcel > > -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com t...@okidokiteam.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
Continuous build updated to Maven 2.2.1
I just updated the continuous build, running on Bamboo, to Maven 2.2.1 because I needed a feature (compiling tests against a different source/target JVM than the bundle itself) which seemed to be broken in earlier versions. Initially, after going to the new Maven, a test case failed, but running the build again made it succeed, so I'm assuming there is some kind of race condition in the test. See: http://opensource.bamboo.atlassian.com/build/viewTestCaseHistory.action?buildKey=FELIX-DEF&testClassName=org.apache.felix.scr.integration.ServiceBindTest&testCaseName=test_optional_single_static Perhaps one of the SCR guys could have a look at this? Greetings, Marcel
