Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change groupId to io.netty #103

Closed
trustin opened this issue Dec 7, 2011 · 5 comments
Closed

Change groupId to io.netty #103

trustin opened this issue Dec 7, 2011 · 5 comments
Assignees
Labels
Milestone

Comments

@trustin
Copy link
Member

trustin commented Dec 7, 2011

Both 3.2 and master should change their groupId to io.netty. From the next release, we are going to deploy to the Sonatype OSS repository.

@normanmaurer
Copy link
Member

What do we do with the packages ?

@trustin
Copy link
Member Author

trustin commented Dec 7, 2011

Last time I talked to Red Hat, they were fine with using the old package
name for 3.2, but let me ask again. Even if they want us to change the
package name, it should be relatively easy for a user to change their
code because org.jboss.netty is such a unique string for regex replacement.

Because 3.2.7 in our new web site still contains some reference to Red
Hat because 3.2.7 was released before the new web site is ready, I think
it's better release a new version as soon as possible after updating
copyright headers, etc. If necessary, we might have to change the
package name and release it as 3.3.0 for example.

Norman Maurer wrote:

What do we do with the packages ?


Reply to this email directly or view it on GitHub:
#103 (comment)

@grovedc
Copy link

grovedc commented Dec 8, 2011

I would expect that this can be addressed along with issue #60 - Make the project multi-module. I currently use the dependency:

org.jboss.netty netty 3.2.7.Final pom

Pulling in netty as a pom is far from ideal.

I'd be very happy to contribute to this effort. I'm very good with maven.

@normanmaurer
Copy link
Member

@trustin: Can we close this ?

@trustin
Copy link
Member Author

trustin commented Jan 19, 2012

Yes, of course.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants