3:08 p.m.
Integration tests require one more folder to be on the classpath for the
test runner. This folder can be added using the Advanced... button.
jboss-tck-runner/src/test/debug-resources
Other than that, you'll need to copy the jboss-as/build.properties file
to jboss-as/local.build.properties and edit the appropriate entries to
match your environment (you can delete those properties which you want
to come from the svn copy in build.properties).
On Mon, 2009-06-01 at 14:11 -0500, Clint Popetz wrote:
On Mon, Jun 1, 2009 at 1:15 PM, David Allen <drallendc(a)gmail.com>
wrote:
On Mon, 2009-06-01 at 13:07 -0500, Clint Popetz wrote:
> 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 :)
OK, as long as everything builds, the test runner is a little
easier to
deal with since you can control exactly what is on the
classpath.
In this case, the jboss-tck-runner project itself must be on
the
classpath, and each of the JARs and other projects it depends
on should
also be on the test runner classpath (except for tck-impl
since that is
already the project for the test). That should be enough to
run
it...that's all I have on mine.
Yay, I was able to get standalone tck tests running in eclipse by
adding the following manually to the tck-impl project in eclipse:
tck-runner and porting package as straight jar references to
the .m2 repo
webbeans-core and webbeans-core-test as project references
Now to try integration tests.
-Clint
>
> -Clint
>
> On Mon, Jun 1, 2009 at 1:03 PM, David Allen
<drallendc(a)gmail.com>
> wrote:
> On Mon, 2009-06-01 at 12:53 -0500, Clint Popetz
wrote:
> > Ahh, but under m2eclipse (at least under the
version I'm
> running,
> > 0.9.8.200905041414), the project dependency isn't
under the
> project
> > tab. It's under Libraries -> Maven Dependencies,
and it's
> not
> > editable. So AFAICT the only way to eliminate the
runner ->
> tck-impl
> > dependency is to keep a local edit to the pom.
>
>
> Oh, sorry to hear that. Somehow it was editable a
few months
> back. I
> quit using it due to a bug, so it's been a while
now.
>
> Hmm, ok, you could do the following, albeit not very
elegant.
>
> 1. Copy the original POM to some new file name of
your
> choice.
> 2. Edit pom.xml and remove the tck-impl dependency
and use
> Eclipse.
> 3. Use the POM saved in (1) with the command line
"mvn -f
> <my-saved-pom>.xml" when you want to run all the
tests.
> 4. And never check-in the edited POM in (2). :)
>
>
> >
> > -Clint
> >
> > On Mon, Jun 1, 2009 at 12:50 PM, David Allen
> <drallendc(a)gmail.com>
> > wrote:
> > If it helps, I do have IM too. :)
> >
> > But basically:
> >
> > 1. Keep m2eclipse.
> > 2. Don't modify any POM.
> > 3. Modify the Java Build Path for
jboss-tck-runner
> -- delete
> > the
> > tck-impl from the Projects tab.
> >
> >
> > On Mon, 2009-06-01 at 12:38 -0500, 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(a)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(a)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(a)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
> >
> >
> >
> >
> >
> > --
> > Clint Popetz
> > http://42lines.net
> > Scalable Web Application Development
>
>
>
>
>
> --
> Clint Popetz
> http://42lines.net
> Scalable Web Application Development
--
Clint Popetz
http://42lines.net
Scalable Web Application Development
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev