|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MNBMODULE-190) *.external not suppo... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-190) *.external not ... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-190) *.external not ... Jesse Glick (JIRA)

If nbmResources cannot be used for this purpose, I suppose a new parameter would need to be introduced that also creates NBM resources but does so from GAVs: it would download the actual artifact into the right spot in the target directory, then also create the matching *.external file. (The *.nbm packing would as usual ignore the JAR and pack only the external marker.) Something like