JAR resources without an existing metadata file were not imported into compiled NSF

[adiXSG]

In my project, the NSF compiler is just one of several Maven modules. A build artefact from a preceding module is a JAR file that is to be included in the compiled NSF. However, since the JAR file is not part of the ODP, there is no existing corresponding metadata file. If the metadata file is missing, the JAR file will not be imported into the compiled NSF.

[adiXSG]

If you're interested, I can create a pull request with the necessary changes to solve the issue.

[jesse-gallagher]

Hmm, I'll take a look. I have a phase in the Maven process to generate missing metadata for several file types, and it could be that I just missed JARs, which should be straightforward.

[jesse-gallagher]

Looking at it, this may be a Maven lifecycle thing. I tried putting a JAR in Code/Jars without an associated .metadata file, but the generate-metadata mojo took care of it before handing it off to the compiler. This happens during the generate-sources phase of compilation - what phase do you have your copy step in? It might make sense to put it in initialize in this workaround: #221 (comment) . That said, I'd also like to implement a feature to natively include Maven dependencies in the plugin so that the workaround isn't needed.