CODEWITHSUNDEEP
javamavenapache-commons
JonasB
JonasB

Reputation: 141

Maven commons-configuration2

I am using Apache commons-configuration2 in one of my projects. Recently, I decided to let Maven manage my projects. Which works fine, except for commons-configuration2; I am not able to find that dependency on the Maven repo. Even when looking just for commons-configuration, not commons-configuration2, none of the results I am getting are org.apache.commons.

What am I doing wrong?

Upvotes: 5

Views: 6513

Answers (5)

AndroidTank
AndroidTank

Reputation: 364

commons-configuration2-2.1 is now available in the Maven repository.

Upvotes: 1

Kohei Nozaki
Kohei Nozaki

Reputation: 1152

commons-configuration2 now available on Maven Central: http://mvnrepository.com/artifact/org.apache.commons/commons-configuration2

Upvotes: 2

ankit s.
ankit s.

Reputation: 93

Current workaround solution:

  1. Download Apache Commons Configuration 2.0 and got the commons-configuration2-2.0-beta2.jar
  2. Add the commons-configuration2-2.0-beta2.jar to external library

  3. Add the needed dependency in maven.

    <dependency>
    <groupId>org.apache.commons</groupId>
    <artifactId>commons-lang3</artifactId>
    <version>3.3.2</version>
</dependency>

<dependency>
    <groupId>commons-logging</groupId>
    <artifactId>commons-logging</artifactId>
    <version>1.1.3</version>
</dependency>

<dependency>
    <groupId>commons-beanutils</groupId>
    <artifactId>commons-beanutils</artifactId>
    <version>1.9.2</version>
</dependency>

<dependency>
    <groupId>commons-codec</groupId>
    <artifactId>commons-codec</artifactId>
    <version>1.9</version>
</dependency>

<dependency>
    <groupId>commons-jxpath</groupId>
    <artifactId>commons-jxpath</artifactId>
    <version>1.3</version>
</dependency>

<dependency>
    <groupId>org.apache.commons</groupId>
    <artifactId>commons-jexl</artifactId>
    <version>2.1.1</version>
</dependency>

<dependency>
    <groupId>org.apache.commons</groupId>
    <artifactId>commons-vfs2</artifactId>
    <version>2.0</version>
</dependency>

<dependency>
    <groupId>xml-resolver</groupId>
    <artifactId>xml-resolver</artifactId>
    <version>1.2</version>
</dependency>

Upvotes: 2

Maarten
Maarten

Reputation: 11

A bug has been filed against the documentation (or against the repo, depending on your view). Apparently, commons-configuration2 will not be pushed to Maven central until final release, but the documentation on their website is automatically generated and points you to a non-existent repository. This will be fixed when a final release is done.

Upvotes: 1

mystarrocks
mystarrocks

Reputation: 4088

That's because, version 1.x of the artifact commons-configuration was really under the commons-configuration group. You can find the latest release version, 1.10, of that artifact in the repo.

It was only after it became commons-configuration2 (technically an entirely different Maven artifact of the same project), it was grouped under org.apache.commons. You don't see them in the maven repo (the RELEASE repo that is) probably because it's still a SNAPSHOT. You can still find the artifact in the SNAPSHOT repo.

See the project summary and release history for more information.

Upvotes: 6

Related Questions