Am 10.10.2014 um 20:42 schrieb Jesse Glick <[email protected]>: > On Fri, Oct 10, 2014 at 2:23 PM, Ulli Hafner <[email protected]> wrote: >> The workaround > > Sorry, which workaround are you referring to?
specifying version 2.5 explicitly on the command line > >> does not work if your project is not in the root folder of the git project. > > What is the bug then? If you have a multimodule project, normally you > would just run release from the root. This releases all the > components, some of which may be plugins. Does that not work? The release plugin does not work if you have a) two projects at top-level of a git project that are released independently b) a mulit-module project with sub-modules released independently c) if the single project is stored in a sub-folder The problem reported here is of type c) I hit this bug when I want to release the findbugs plugin (b). It is a multi-module build: one module (a library) is changed only about once a year, the plugin itself is released several times a year. So I want to be able to release only the module that actually has been changed. That is not possible anymore, I need to spam our maven repo with a new unchanged library every time I release the plug-in. All of these options are a bug in my opinion…
signature.asc
Description: Message signed with OpenPGP using GPGMail
