[webbeans-dev] Help running tck in eclipse?
Pete Muir
pmuir at redhat.com
Wed Jun 3 08:09:26 EDT 2009
On 2 Jun 2009, at 13:59, Pete Muir wrote:
> I win ;-)
>
> I moved the tck-impl into a profile in tck-runner, so that m2eclipse
> doesn't pick it up as a dependency. You can now just add the tck-
> runner project as a imported project to tck-impl.
>
> I would also suggest adding process-resources to the "Goals to
> invoke after project clean" in the maven tab of the project, making
> sure that m2eclipse copies the relevant properties file across.
>
> I'll verify i/c soon.
I can't get this to work with m2eclipse, reverting to using the maven-
eclipse-plugin to generate eclipse files works perfectly. Essentially,
m2eclipse constant fiddling with stuff (coupled with not running
process-resources properly) seems to be the problem.
I'm now working through the i/c failures we've picked up over the last
few weeks.
>
> On 1 Jun 2009, at 18:40, Pete Muir wrote:
>
>> Hmm, so I guess this trick doesn't work with m2eclipse, unless you
>> replace the generated dependencies. It's a race to find a solution...
>>
>> On 1 Jun 2009, at 18:38, Clint Popetz wrote:
>>
>>> m2eclipse doesn't generate jar dependencies, it generates project-
>>> to-project dependencies if the dependent artifact is already a
>>> project in the workspace. So it generates a project-to-project
>>> dependency between the runner and tck-impl in both directions, and
>>> eclipse refuses to build either.
>>>
>>> -Clint
>>>
>>> On Mon, Jun 1, 2009 at 12:34 PM, David Allen <drallendc at gmail.com>
>>> wrote:
>>> On Mon, 2009-06-01 at 12:16 -0500, Clint Popetz wrote:
>>> > Does eclipse:eclipse not generate a dependency from the runner to
>>> > tck-impl? Because m2eclipse does, based on the pom, and then I
>>> have a
>>> > circular dependency in eclipse.
>>>
>>> Yes it does generate that dependency, but the JAR dep is later
>>> after the
>>> project itself (My test runners are always based in the tck-impl
>>> project).
>>>
>>> Yeah, I vaguely remember having problems with the automatic setup
>>> from
>>> m2eclipse too. But I usually modify the Java build path directly in
>>> Eclipse even with m2eclipse. This usually works fine until a
>>> change in
>>> the POM conflicts with your manual change...but that's not all that
>>> likely today.
>>>
>>>
>>> > I can modify the runner's pom to not have that dependency, which
>>> makes
>>> > eclipse happy, but keeps one from running tests with mvn out of
>>> the
>>> > runner's directory on the command line.
>>> >
>>> > -Clint
>>> >
>>> >
>>> > On Mon, Jun 1, 2009 at 12:08 PM, David Allen <drallendc at gmail.com>
>>> > wrote:
>>> > On Mon, 2009-06-01 at 12:00 -0500, Clint Popetz wrote:
>>> > > Hi,
>>> > >
>>> > > I've tried running the tck from within eclipse by
>>> following
>>> > the
>>> > > instructions here:
>>> > >
>>> > > http://seamframework.org/WebBeans/JSR299TCKHarness
>>> > >
>>> > > but I'm having no luck; it can't find an
>>> implementation of
>>> > > StandaloneContainers, although I've manually added the
>>> > runner to the
>>> > > tck-impl project's dependencies.
>>> > >
>>> > > Before I dive deeper, are those directions up to date?
>>> >
>>> >
>>> > I think they are up to date, but we can certainly
>>> improve them
>>> > too. It
>>> > varies a bit depending on what tools are actually used.
>>> >
>>> > > Is anyone running the tck from within eclipse? If
>>> so, are
>>> > you
>>> > > generating projects with eclipse:eclipse or with
>>> m2eclipse?
>>> >
>>> >
>>> > Most of us are currently using eclipse:eclipse right
>>> now. But
>>> > here are
>>> > a couple things I usually do to get any TCK test (not an
>>> > in-container
>>> > only test) running:
>>> >
>>> > 1. Modify the build path of the jboss-tck-runner
>>> project so
>>> > that all of
>>> > its dependent projects/libraries are exported (select
>>> all).
>>> >
>>> > 2. Choose "Run as TNG test" to get most of the runner
>>> setup
>>> > correctly,
>>> > but the tests will fail to run at first.
>>> >
>>> > 3. Modify the runner by going to the Classpath tab and
>>> press
>>> > "Add
>>> > projects" button and add the jboss-tck-runner project.
>>> With 1
>>> > above,
>>> > this should include everything else that is needed too
>>> > automatically.
>>> >
>>> > 4. Run it again...this time it should work.
>>> >
>>> > >
>>> > > Thanks,
>>> > > -Clint
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > Clint Popetz
>>> > > http://42lines.net
>>> > > Scalable Web Application Development
>>> >
>>> >
>>> > > _______________________________________________
>>> > > webbeans-dev mailing list
>>> > > webbeans-dev at lists.jboss.org
>>> > > https://lists.jboss.org/mailman/listinfo/webbeans-dev
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Clint Popetz
>>> > http://42lines.net
>>> > Scalable Web Application Development
>>>
>>>
>>>
>>>
>>> --
>>> Clint Popetz
>>> http://42lines.net
>>> Scalable Web Application Development
>>> _______________________________________________
>>> webbeans-dev mailing list
>>> webbeans-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>>
>> _______________________________________________
>> webbeans-dev mailing list
>> webbeans-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20090603/e3a9d537/attachment.html
More information about the weld-dev
mailing list