Interesting. My company was evaluating releasing some Maven artifacts on some of the nonprofit open source projects we manage. I think I'll hold off on that, since it seems like a small mistake could get us in a lot of hot water. I don't understand Maven that well and probably oughtn't to participate unless/until I do.
I wonder what could be done to make the system less brittle and detect this kind of mistake proactively? On Wed, Feb 25, 2009 at 1:17 PM, <[email protected]> wrote: > http://twitter.com/jvanzyl/status/1249869568 > > Never good when the creator of the technology your using calls out your > project as an example of bad practices. > > On the bright side, it did make me aware of your project though. No > publicity is bad publicity. > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1228010 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1228178
