You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Neale Upstone (Commented) (JIRA)" <ji...@apache.org> on 2011/10/12 14:47:11 UTC
[jira] [Commented] (VALIDATOR-253) Change groupId to
org.apache.commons
[ https://issues.apache.org/jira/browse/VALIDATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125791#comment-13125791 ]
Neale Upstone commented on VALIDATOR-253:
-----------------------------------------
I think you guys are being too cautious about this issue, and getting 1.4 out in general.
For those of us who just want rid of the dependency on ORO, releasing 1.4 as it has been since May would suffice.
I disagree with the comment about changing the package name as well. We've had both oro and jakarta-oro in a prod build without problems (admittedly at the same version). This gets detected when we use tooling to check the classpath for multiple implementations of the same class. Changing the package name would just mean that we can have the both in and not see it!
If you *keep* the package names as they are, then not only will this sort of tooling work (including things like mvn dependency:analyse), but also, it'll make life easier for people to migrate.
As for what remains outstanding for 1.4, I'd suggest descoping some items to a possible 1.4.1 release if needed. You'd earn some beer :)
> Change groupId to org.apache.commons
> ------------------------------------
>
> Key: VALIDATOR-253
> URL: https://issues.apache.org/jira/browse/VALIDATOR-253
> Project: Commons Validator
> Issue Type: Task
> Reporter: Paul Benedict
> Assignee: Nick Burch
> Fix For: 1.4
>
>
> Some existing Commons projects have made the POM move to org.apache.commons with their new releases.
> http://repo.mergere.com/maven2/org/apache/commons/
> I think a 1.4 release is a good time to change the groupId as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira