April 2007 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Migration to maven

by adrian＠jboss.org

"Kevin.Conner(a)jboss.com" wrote : "adrian(a)jboss.org" wrote : Tests are broken again though. | Within eclipse or standalone? | Both. They should all work in eclipse? - except some aop tests which need a change to the classloader or weaving to work properly. Until they work in eclipse, I'm not even going to try to fix the Maven run. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033965#4033965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033965

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Current test failures

by Kevin.Conner＠jboss.com

I am seeing a number of test failures when executed which the command line. Is anyone else seeing these failures? Should all the tests pass? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033964#4033964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033964

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Migration to maven

by Kevin.Conner＠jboss.com

"adrian(a)jboss.org" wrote : Tests are broken again though. Within eclipse or standalone? I have a number of standalone failures/errors at present. Perhaps we could create a new topic to discuss :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033963#4033963 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033963

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Migration to maven

by adrian＠jboss.org

"Kevin.Conner(a)jboss.com" wrote : | Can you give me a specific test which fails to find the resource? Go to the container project and find src/tests/org/jboss/test/ContainerAllTestSuite Right click and run it as a junit test. Example error: | junit.framework.AssertionFailedError: TestInstantiate.xml not found | at junit.framework.Assert.fail(Assert.java:47) | at org.jboss.test.ioc.test.AbstractIoCTest.findXML(AbstractIoCTest.java:87) | at org.jboss.test.ioc.test.AbstractIoCTest.unmarshal(AbstractIoCTest.java:73) | at org.jboss.test.ioc.test.AbstractIoCTest.unmarshal(AbstractIoCTest.java:57) | at org.jboss.test.javabean.test.InstantiateTestCase.testInstantiate(InstantiateTestCase.java:37) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at junit.framework.TestCase.runTest(TestCase.java:154) | at junit.framework.TestCase.runBare(TestCase.java:127) | at junit.framework.TestResult$1.protect(TestResult.java:106) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.framework.TestResult.run(TestResult.java:109) | at junit.framework.TestCase.run(TestCase.java:118) | at junit.framework.TestSuite.runTest(TestSuite.java:208) | at junit.framework.TestSuite.run(TestSuite.java:203) | at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) | at junit.extensions.TestSetup$1.protect(TestSetup.java:19) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.extensions.TestSetup.run(TestSetup.java:23) | at junit.framework.TestSuite.runTest(TestSuite.java:208) | at junit.framework.TestSuite.run(TestSuite.java:203) | at junit.framework.TestSuite.runTest(TestSuite.java:208) | at junit.framework.TestSuite.run(TestSuite.java:203) | at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) | at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) | All the xml parsing tests fail because it cannot find the xml url using getResource(). Now delete src/resources as a source folder and make it a class library, i.e. | - <classpathentry kind="src" path="src/resources" including="schema/**" excluding="**/*.java"/> | + <classpathentry kind="lib" path="src/resources"> | 100% success on tests View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033962#4033962 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033962

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Migration to maven

by adrian＠jboss.org

"Kevin.Conner(a)jboss.com" wrote : "adrian(a)jboss.org" wrote : This doesn't look like it is going to work unless you create your eclipse workspace somewhere else. I guess it wants to copy the project onto itself? | Is your workspace the same as you svn root? | Yes. Always has been in the past. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033960#4033960 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033960

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Migration to maven

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | This doesn't look like it is going to work unless you create your eclipse workspace | somewhere else. I guess it wants to copy the project onto itself? | | The error I get is: | | | Invalid project description. | | /home/ejort/microcontainer/aop-mc-int overlaps the location of another project: aop-mc-int | | | | I guess it wants to copy the project onto itself? | The redundant workspace works. Starting from scratch: 1) Checkout microcontainer 2) build with maven 3) run maven's eclipse:eclipse 4) Create a microcontainer-eclipse workspace 5) Import all the projects and set the M2_REPO variable Tests are broken again though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033959#4033959 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033959

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Migration to maven

by Kevin.Conner＠jboss.com

"adrian(a)jboss.org" wrote : This doesn't look like it is going to work unless you create your eclipse workspace somewhere else. I guess it wants to copy the project onto itself? Is your workspace the same as you svn root? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033958#4033958 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033958

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Migration to maven

by Kevin.Conner＠jboss.com

"adrian(a)jboss.org" wrote : | This doesn't look like it is going to work unless you create your eclipse workspace | somewhere else. I guess it wants to copy the project onto itself? | | The error I get is: | | | Invalid project description. | | /home/ejort/microcontainer/aop-mc-int overlaps the location of another project: aop-mc-int | | | Did you delete these projects first? If they are in the svn location then you should not delete the contents, just the workspace references. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033954#4033954 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033954

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Migration to maven

by Kevin.Conner＠jboss.com

"adrian(a)jboss.org" wrote : Eclipse doesn't either. I currently have to resynch outside eclipse then refresh which is a pain. There is no need for the parent pom to exist in the parent directory, it could be another project pulled in via a parent aggregator. I do not believe that the eclipse plugin will generate project information for it though, but at least you would be able to include it into your eclipse workspace. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033953#4033953 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033953

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Migration to maven

by Kevin.Conner＠jboss.com

"adrian(a)jboss.org" wrote : Ok I will try that, but since I hit the problem with a clean checkout of the | Microcontainer and a build with Maven before creating the new eclipse | projects, I don't know whether this entirely consistent? -) | It should be if you ran the eclipse:eclipse and eclipse:add-maven-repo targets. Let me know how it goes. "adrian(a)jboss.org" wrote : src/resources/schema or src/resources/xml-tests in the container project would be examples. After an eclipse:eclipse these are invisible to tests | run inside eclipse. They have type="src" instead of type="lib' in the .classpath I do not believe that matters. It may be that the path to the resource is different, perhaps because it is embedded. The normal maven structure would keep the test resources separate from the src resources whereas it appears that the MC structure embeds them. I could change the build to fix this if everyone agrees. Can you give me a specific test which fails to find the resource? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033949#4033949 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033949

17 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2007