No fixture found message when using plugins

[keetron]

This seems similar to #33 which was closed as being fixed, which might be the case for a lot but not for everything. It still does not include plugins, such as HSAC which is a shame as we build just about all our tests in that and it gives me a ton of red squiggly lines and removes the ability to check what is going on when using this fixture.

[amolenaar]

I'll need to have a look then. I suppose the plugins are listed under 'External libraries' (project view).

[amolenaar]

I have junit-4.12.jar in my list of external libraries. If I create a table

| base test runner |

The Go to Declaration command (cmd/ctrl-b) jumps to the class in the JUnit jar file.

[keetron]

A bit more information: The plugin .jar is in the $FITNESSE_HOME/plugins folder the pom.xml contains the following

<dependency>
   <groupId>org.fitnesse</groupId>
   <artifactId>fitnesse</artifactId>
   <version>${fitnesse.version}</version>
   <scope>provided</scope>
</dependency>

<dependency>
   <groupId>nl.hsac</groupId>
   <artifactId>hsac-fitnesse-fixtures</artifactId>
   <version>2.10.0</version>
</dependency>

It can find a lot of other java stuff, just not this fixture, not sure why, but it gives me a ton of red squigglies and I can do without those :-)

[keetron]

Okee, after a lot of searching we found out what the issue was and it is very possible it was my/our fault.

The fitnesse folder was not part of a maven project, which is why the plugins were not indexed. Now that we included the folder in the maven profile, most of my squiggly worries are gone.

[amolenaar]

Cool. Thanks for the update.

[keetron]

For future readers and my future self: add your pom.xml to maven by right-clicking and select "add maven project" Reload the open wiki files and your squigglies should be gone.

Another thing is that a table without a script or scenario declaration will not have a fixture to choose from and will give errors by default.

In hindsight, this is all very logical.