rename project to vaadin-cdi-utils #9
Description
I am very glad to see that you decided to use the "official" cdi integration addon. Now the scope is clearly separated.
Could you consider moving the vaadin7 branch to org.vaadin.addons.vaadin-cdi-utils? Currently I find the name-mismatch between repository name/filesystem folder and maven artifactId confusing. And using the default addon-package-namespace would make it easier to integrate the project in "enterprise"-environment, where every new 3rd party library must be negotiated, it just feels better if the package name does not include the single developers name.
What do you think? I would gladly help and contribute to migrate ....