Skip to content

Maven groupId should be changed for 4.0 #573

@glynn-sigfig

Description

@glynn-sigfig

We're trying to use netty 3.5 and 4.0 alpha in the same project. Since they have separate namespaces this works fine except for maven which evicts 3.5 when you include 4.0 alpha.

Since 4.0 breaks backwards compatibility it is likely that projects will want to be able to use both at once, particularly for 3rd party libraries (play 2.0 in our case).

This is similar to what happened with jMock and hibernate. They both solved it by submitting the new backward incompatible version under a different groupId (see discussion here: http://maven.40175.n5.nabble.com/Dep-to-same-artifact-in-different-versions-td202532.html).

(Or if there's some way to tell maven to just get both versions that would work fine for us as well).

Thanks. We're really enjoying 4.0 so far.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions