Hi Noel, This was we have now but it has the problems:
* only a project can be in incubation => all project are forced to incubation mode (marked on download-page, the jar-name, ...) * only a project can do a release => all projects have to be released together In eclipse we are by the way not renaming something but the namespace stays stable from the beginning so if you used a incubation-widget you simply drop in the new .jar from the stable widget and if no breaking API change has been introduced you are fine. Tom Noel Grandin schrieb: > Just a suggestion, but why not simply have one project, and enforce > that widgets which are currently experimental have to live in a > special package space? > > e.g. org.eclipse.nebula.experimental.mywidget > > And then do a refactor->rename to move the widget into a normal nebula > package once it reaches maturity. > > e.g. org.eclipse.nebula.mywidget > > That would be pretty low overhead, and also pretty obvious to anyone > using the code. > > Regards, Noel Grandin. > _______________________________________________ > nebula-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/nebula-dev _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
