I wouldn't have an issue with it in a branch repo - but unless you created one we didn't really have a separate branch repo. Putting it in the standard repo though does cause problems, as Mirko noted.
I think the best approach though is to not worry about all that and just get your stuff merged into the trunk. We can discuss that in email. On Jan 4, 3:38 pm, Mark <[email protected]> wrote: > > who loosely define plugin version in their projects. But I don't > > understand why to remove this version from branch repo? Naming it as a > > "release" was really confusing (sorry x2), but in fact it's only > > development version that (maybe) somebody would like to try out. Is > > that a problem that this is visible for people when it's clear that > > it's version from branch (another repo)? > > After longer time I think it may be a problem. As I've written to > Charlie in private post I'll remove this version even from branch > repo. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
