I’m having issues with loading Java resources in one of the dependency I use in my Pulumi stack code. I tried to fine tune the Maven exec plugin, but I’m not getting anywhere. What’s the best way to debug how the Pulumi CLI calls Maven? Can I pass some extra flags, like

-X

?

good to know

I couldn’t figure that out. I don’t know Maven well enough

You may share pom.xml.

I’m not sure if I can, but I can describe it in more detail. I’ve got a class in module A that loads a property file from resources:

URL resource = Resources.getResource("values.properties");

Then I reference this class in my Pulumi app (module B), pulling it as a regular dependency:

<dependency>
            <groupId>${project.groupId}</groupId>
            <artifactId>moduleA</artifactId>
        </dependency>

and

pulumi up

throws this:

Caused by: java.lang.IllegalArgumentException: resource values.properties not found.
        at com.google.common.base.Preconditions.checkArgument(Preconditions.java:218)
        at com.google.common.io.Resources.getResource(Resources.java:196)
        at packageA.ClassA.<clinit>(ClassA.java:39)

I tried a few things, like: • copying this property to moduleB, under the same path • enabling

<addResourcesToClasspath>

for the exec-maven-plugin • different values for

<classpathScope>

• adding it explicitly to the class path by adding it to

<additionalClasspathElements>

, confirmed with

mvn -X

that it’s set I don’t think it’s an issue with Pulumi itself, just exec-maven-plugin, but I wonder if Pulumi has to use it, or could it run the program from a jar