]
Jess Sightler commented on FURNACE-140:
---------------------------------------
I don't see how that can be the case. We generally work around the problem by running
a command to create the empty stub directories:
find . -name target -exec mkdir {}/classes \;
It works fine after that. We also have no issues with the built jars themselves.
FileNotFoundException: Source '/path/to/addon/target/classes'
does not exist
----------------------------------------------------------------------------
Key: FURNACE-140
URL:
https://issues.jboss.org/browse/FURNACE-140
Project: Forge: Furnace
Issue Type: Bug
Reporter: Jess Sightler
When I run forge tests within the IDE, it will use the classes directory for loading
add-on classes. This is great, however, some of the add-on modules do not have source
files and do not necessarily generate a classes folder. For example, I may have a
multimodule addon (addon/, api/, impl/, tests/, etc) that doesn't have any sources
inside of addon/.
In this case, Forge fails to load the classes and I end up with a FileNotFoundException.