The "resource" statement used when publishing should support some wildcards. These wildcards would act like ant-style file globs.
Given the following wildcards and their descriptions:
* Match zero or more characters for files in the directory.
\ Match zero or more directories.
? Match one character
And the following jar files in my project:
output/
├── bar.jar
└── baz.jar
When I have a wildcard of foo/.jar in my resource statement
fig --publish foo/1.0 --resource="output/.jar" --append="CLASSPATH=@/output/bar.jar"
Then both "bar.jar" and "baz.jar" will be published to the fig repository, and downloaded when a user includes the foo/1.0 package in their project.
The "resource" statement used when publishing should support some wildcards. These wildcards would act like ant-style file globs.
Given the following wildcards and their descriptions: * Match zero or more characters for files in the directory. \ Match zero or more directories. ? Match one character And the following jar files in my project: output/ ├── bar.jar └── baz.jar When I have a wildcard of foo/.jar in my resource statement fig --publish foo/1.0 --resource="output/.jar" --append="CLASSPATH=@/output/bar.jar"
Then both "bar.jar" and "baz.jar" will be published to the fig repository, and downloaded when a user includes the foo/1.0 package in their project.