[
https://issues.apache.org/jira/browse/CONFIGURATION-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700105#comment-14700105
]
Oliver Heger commented on CONFIGURATION-606:
--------------------------------------------
Okay, I understand that the current situation can be confusing.
The release has deliberately not be published to Maven central because breaking
changes cannot be excluded until the final release. Having multiple binary
incompatible versions in central with the same group and artifact IDs is very
problematic.
OTOH, the _Dependency Information_ page you are referring to is automatically
generated. I guess, it is possible to override it temporarily, but do you think
a corresponding note on the main page would be sufficient?
> Version 2.0-beta1 not published to maven repository as documented
> -----------------------------------------------------------------
>
> Key: CONFIGURATION-606
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-606
> Project: Commons Configuration
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 2.0
> Reporter: Jeremy Norris
> Fix For: 2.0
>
>
> The webpage at
> https://commons.apache.org/proper/commons-configuration/dependency-info.html
> documents the following maven dependency snippet for version 2.0-beta1, but
> it does not work since this version has not actually been published to the
> maven repos:
> <dependency>
> <groupId>org.apache.commons</groupId>
> <artifactId>commons-configuration2</artifactId>
> <version>2.0-beta1</version>
> </dependency>
> Please consider either correctly publish the jars as documented, or remove
> this documentation from the website, as it is misleading to users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
