Hi, Seems to me that each m2 plugin should reside in its own project, or, create more *versions* in JIRA that pertain to plugin-issues only.
Currently, it's impossible to track the roadmap/changelog for plugin releases. Quickest route imo: leave everything as is, but create more versions in the MNG project, like "maven-2.0.1", "compile-plugin-2.0", "compile-plugin-2.1", etc. On 10/23/05, Brett Porter <[EMAIL PROTECTED]> wrote: > I think this was a jira miscommunication. It's just waiting for a > release of the plugin for a fix, these have their own release cycles. > We're still trying to determine the most useful technique for doing > this in JIRA. > > - Brett > > On 10/23/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote: > > The issue in JIRA (http://jira.codehaus.org/browse/MNG-1216) states that it > > has been fixed in 2.0, but I was running the released 2.0 of Maven. Is the > > fix version of the bug wrong in JIRA? > > > > regards, > > > > Wim > > > > 2005/10/22, Brett Porter <[EMAIL PROTECTED]>: > > > > > > It is in JIRA, we'll try and get a fix out as soon as possible. > > > > > > On 10/21/05, Bernd Mau <[EMAIL PROTECTED]> wrote: > > > > Yes, it really seems to be a bug and I coud not find an issue in the > > > > JIRA concerning this problem. > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
