jerome lacoste wrote: > Sorry but it's not marked as such in Jira > > http://jira.codehaus.org/browse/MASSEMBLY-19 > > Component/s: None > Affects Version/s: None > Fix Version/s: None >
I know its a pain in the butt, but I will reiterate. We created the JIRA projects *after* the bugs were resolved. We didn't have enough information to go back and figure out which belonged to which version. Nothing wrong with the process, the past data was floored. Sorry, but I can't fix it now. And again, I need to point out the release of your issue has not been delayed. 2.0.1 wasn't originally planned. [snip part based on the assumption we reviewed all 60 assembly issues] > I don't know what else I could do appart from notifying you that it > wasn't included in the forthcoming release. I missed the vote mail > (which maybe shouldn't be on the dev list?). Right. The proposed solution was already given. > WRT to backport, I asked in another mail thread to backport it and > make a 2.0.2. I replied here before reading that, sorry. > I feelt that the longer you stay with this issue in the > code, the more you have a chance to break existing user configurations > who will do the upgrade. I think once its released, the time in between is irrelevant as people don't always upgrade as soon as there is a release. Reviewing the issue, I don't get it. I can see how its a breaking change, but I don't see how anyone would consider the previous behaviour anything but a bug (its ignoring outputDirectory, right?) I don't see this as urgent. We do need to prioritise the 2.1 release anyway. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
