--- [EMAIL PROTECTED] wrote: > There is a third option: > > 3) Remove graph2 from commons.
I wouldn't presume to do that on my own recognizance, but if all the graph2 developers decided to go that way, that would be fine. Seems like overkill for the sake of two classes, but I have no idea how important they are to Maven or other dependant projects not tracked by GUMP. Removing graph2 from Commons still may mean that it can't be used in other Jakarta software, depending on how the board decides to interpret the LGPL and viral licensing. Don't shoot the messenger, I don't care one whit about the holy wars. In fact, the only reason I know what license nsUML uses is because last week I researched the project so I could have an informed opinion on how to fix the GUMP build for graph, so we could make some progress on Maven nightlies. If after all the discussions are over, LGPL imports turn out to be OK, then yay for us. But a few months ago somebody on the board mistakenly implicated the Commons repository as a source of copyright infringment. At that time, we all discussed the issue and agreed to be AS PROACTIVE AS POSSIBLE: http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=103533740906927&w=2 This is me being proactive. - Morgan ===== Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
