|
||||||||
|
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-137) Option to use invari... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-137) Option to use i... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-137) Option to use i... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-137) Option to use i... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-137) Option to use i... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-137) Option to use i... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-137) Option to use i... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-137) Option to use i... Milos Kleint (JIRA)

in what way will the release plugin problems with it? when performing a release you cannot depend on any snapshots anyway, no matter if coming from reactor or not. And any projects you depend on in the same reactor are built first.
I agree the library descriptor problem is not solved. But that would only be solved if the artifact's in-module name remains the same eg ext/groupid/artifactid.jar all the time. But why then check for the same groupid then at all, why not just use this pattern for all dependencies?