Importing "wildcard" Maven project dependencies?

Question

I have quite a situation here: another team is building a Flex SDK and delivers it as a huge set of separate SWC files. At this point I cannot make them build a single SWC file library.

I'm trying to use these files as Maven dependencies to pass to Flexmojos but they are like 40 files and I don't want to manage each of them as a separate dependency (after all they are parts of the same thing).

Is there a way to:

1. Install all of the SWC files as artifacts in the local repo? (with the same groupId and version and auto-generated artifactId I guess)
2. Import these as dependencies using a "wildcard" or plugin that generates dependencies at runtime or something?

Answer 1

this won't work that way. Dependency declarations can't be dynamic, this would break the build. What you can do is have your deployers create a rollup pom with packaging pom containing all of the SWC dependencies and deploy that pom into your nexus repository. You'd be able to use that pom dependency. The benefit would be that the pom is maintained in a single central location.

Answer 2

You can use the build-helper-maven-plugin to add artifacts to the Flex SDK project. As a result you can use the SDK project as a dependency and got all files which you can use.