I've added the direct path to the .m2/repository runner jar in the tck-impl libraries path in eclipse, which resolves the circularity issue without modifying a file that svn knows. However, I'm still not able to run. Closer, though :)<br>
<br>-Clint<br><br><div class="gmail_quote">On Mon, Jun 1, 2009 at 1:03 PM, David Allen <span dir="ltr"><<a href="mailto:drallendc@gmail.com">drallendc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, 2009-06-01 at 12:53 -0500, Clint Popetz wrote:<br>
> Ahh, but under m2eclipse (at least under the version I'm running,<br>
> 0.9.8.200905041414), the project dependency isn't under the project<br>
> tab. It's under Libraries -> Maven Dependencies, and it's not<br>
> editable. So AFAICT the only way to eliminate the runner -> tck-impl<br>
> dependency is to keep a local edit to the pom.<br>
<br>
</div>Oh, sorry to hear that. Somehow it was editable a few months back. I<br>
quit using it due to a bug, so it's been a while now.<br>
<br>
Hmm, ok, you could do the following, albeit not very elegant.<br>
<br>
1. Copy the original POM to some new file name of your choice.<br>
2. Edit pom.xml and remove the tck-impl dependency and use Eclipse.<br>
3. Use the POM saved in (1) with the command line "mvn -f<br>
<my-saved-pom>.xml" when you want to run all the tests.<br>
4. And never check-in the edited POM in (2). :)<br>
<div><div></div><div class="h5"><br>
><br>
> -Clint<br>
><br>
> On Mon, Jun 1, 2009 at 12:50 PM, David Allen <<a href="mailto:drallendc@gmail.com">drallendc@gmail.com</a>><br>
> wrote:<br>
> If it helps, I do have IM too. :)<br>
><br>
> But basically:<br>
><br>
> 1. Keep m2eclipse.<br>
> 2. Don't modify any POM.<br>
> 3. Modify the Java Build Path for jboss-tck-runner -- delete<br>
> the<br>
> tck-impl from the Projects tab.<br>
><br>
><br>
> On Mon, 2009-06-01 at 12:38 -0500, Clint Popetz wrote:<br>
><br>
><br>
> > m2eclipse doesn't generate jar dependencies, it generates<br>
> > project-to-project dependencies if the dependent artifact is<br>
> already a<br>
> > project in the workspace. So it generates a<br>
> project-to-project<br>
> > dependency between the runner and tck-impl in both<br>
> directions, and<br>
> > eclipse refuses to build either.<br>
> ><br>
> > -Clint<br>
> ><br>
> > On Mon, Jun 1, 2009 at 12:34 PM, David Allen<br>
> <<a href="mailto:drallendc@gmail.com">drallendc@gmail.com</a>><br>
> > wrote:<br>
> > On Mon, 2009-06-01 at 12:16 -0500, Clint Popetz<br>
> wrote:<br>
> > > Does eclipse:eclipse not generate a dependency<br>
> from the<br>
> > runner to<br>
> > > tck-impl? Because m2eclipse does, based on the<br>
> pom, and<br>
> > then I have a<br>
> > > circular dependency in eclipse.<br>
> ><br>
> ><br>
> > Yes it does generate that dependency, but the JAR<br>
> dep is later<br>
> > after the<br>
> > project itself (My test runners are always based in<br>
> the<br>
> > tck-impl<br>
> > project).<br>
> ><br>
> > Yeah, I vaguely remember having problems with the<br>
> automatic<br>
> > setup from<br>
> > m2eclipse too. But I usually modify the Java build<br>
> path<br>
> > directly in<br>
> > Eclipse even with m2eclipse. This usually works<br>
> fine until a<br>
> > change in<br>
> > the POM conflicts with your manual change...but<br>
> that's not all<br>
> > that<br>
> > likely today.<br>
> ><br>
> ><br>
> ><br>
> > > I can modify the runner's pom to not have that<br>
> dependency,<br>
> > which makes<br>
> > > eclipse happy, but keeps one from running tests<br>
> with mvn out<br>
> > of the<br>
> > > runner's directory on the command line.<br>
> > ><br>
> > > -Clint<br>
> > ><br>
> > ><br>
> > > On Mon, Jun 1, 2009 at 12:08 PM, David Allen<br>
> > <<a href="mailto:drallendc@gmail.com">drallendc@gmail.com</a>><br>
> > > wrote:<br>
> > > On Mon, 2009-06-01 at 12:00 -0500, Clint<br>
> Popetz<br>
> > wrote:<br>
> > > > Hi,<br>
> > > ><br>
> > > > I've tried running the tck from within<br>
> eclipse by<br>
> > following<br>
> > > the<br>
> > > > instructions here:<br>
> > > ><br>
> > > ><br>
> <a href="http://seamframework.org/WebBeans/JSR299TCKHarness" target="_blank">http://seamframework.org/WebBeans/JSR299TCKHarness</a><br>
> > > ><br>
> > > > but I'm having no luck; it can't find an<br>
> > implementation of<br>
> > > > StandaloneContainers, although I've<br>
> manually added<br>
> > the<br>
> > > runner to the<br>
> > > > tck-impl project's dependencies.<br>
> > > ><br>
> > > > Before I dive deeper, are those<br>
> directions up to<br>
> > date?<br>
> > ><br>
> > ><br>
> > > I think they are up to date, but we can<br>
> certainly<br>
> > improve them<br>
> > > too. It<br>
> > > varies a bit depending on what tools are<br>
> actually<br>
> > used.<br>
> > ><br>
> > > > Is anyone running the tck from within<br>
> eclipse?<br>
> > If so, are<br>
> > > you<br>
> > > > generating projects with eclipse:eclipse<br>
> or with<br>
> > m2eclipse?<br>
> > ><br>
> > ><br>
> > > Most of us are currently using<br>
> eclipse:eclipse right<br>
> > now. But<br>
> > > here are<br>
> > > a couple things I usually do to get any<br>
> TCK test<br>
> > (not an<br>
> > > in-container<br>
> > > only test) running:<br>
> > ><br>
> > > 1. Modify the build path of the<br>
> jboss-tck-runner<br>
> > project so<br>
> > > that all of<br>
> > > its dependent projects/libraries are<br>
> exported<br>
> > (select all).<br>
> > ><br>
> > > 2. Choose "Run as TNG test" to get most<br>
> of the<br>
> > runner setup<br>
> > > correctly,<br>
> > > but the tests will fail to run at first.<br>
> > ><br>
> > > 3. Modify the runner by going to the<br>
> Classpath tab<br>
> > and press<br>
> > > "Add<br>
> > > projects" button and add the<br>
> jboss-tck-runner<br>
> > project. With 1<br>
> > > above,<br>
> > > this should include everything else that<br>
> is needed<br>
> > too<br>
> > > automatically.<br>
> > ><br>
> > > 4. Run it again...this time it should<br>
> work.<br>
> > ><br>
> > > ><br>
> > > > Thanks,<br>
> > > > -Clint<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > --<br>
> > > > Clint Popetz<br>
> > > > <a href="http://42lines.net" target="_blank">http://42lines.net</a><br>
> > > > Scalable Web Application Development<br>
> > ><br>
> > ><br>
> > > ><br>
> _______________________________________________<br>
> > > > webbeans-dev mailing list<br>
> > > > <a href="mailto:webbeans-dev@lists.jboss.org">webbeans-dev@lists.jboss.org</a><br>
> > > ><br>
> ><br>
> <a href="https://lists.jboss.org/mailman/listinfo/webbeans-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/webbeans-dev</a><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > > Clint Popetz<br>
> > > <a href="http://42lines.net" target="_blank">http://42lines.net</a><br>
> > > Scalable Web Application Development<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Clint Popetz<br>
> > <a href="http://42lines.net" target="_blank">http://42lines.net</a><br>
> > Scalable Web Application Development<br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> Clint Popetz<br>
> <a href="http://42lines.net" target="_blank">http://42lines.net</a><br>
> Scalable Web Application Development<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Clint Popetz<br><a href="http://42lines.net">http://42lines.net</a><br>Scalable Web Application Development<br>