[
https://issues.apache.org/jira/browse/IO-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673495#action_12673495
]
Jukka Zitting commented on IO-125:
----------------------------------
{quote}
Properly moving to org.apache.commons means a bunch of redirects being put in
the maven repository.
{quote}
Do we need those redirects? I think the 1.x releases could well remain at their
current location at commons-io, and we'd just put new 2.x releases in
org/apache/commons. An upgrade from 1.4 to 2.0 would require changing the
dependency setting from
{code:xml}
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>1.4</version>
</dependency>
{code}
to
{code:xml}
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-io</artifactId>
<version>2.0</version>
</dependency>
{code}
> wrong groupId value in pom.xml
> ------------------------------
>
> Key: IO-125
> URL: https://issues.apache.org/jira/browse/IO-125
> Project: Commons IO
> Issue Type: Bug
> Reporter: Piotr Czerwinski
> Fix For: 2.x
>
>
> groupId for the project is set to commons-io. I believe it should be
> org.apache.commons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
