Apache's Maven repository missing commons-io, most versions

Discussion:

Russell Bateman

2017-03-29 23:31:14 UTC

As I attempt to build, I find

https://repo.maven.apache.org/maven2/org/apache/commons/commons-io/2.5/commons-io-2.5.jar

to yield a 404. When I go look there, only 1.3.2 exists and even that,
though there are JARs galore, has a /pom.xml/ that basically refers
Maven to Maven Central. Must I then put something into my /pom.xml/ that
deters Maven from ever looking for anything in /repo.maven.apache.org/?
It seems strange that Apache would offer a Maven repository that's
missing an important library (for me, at least). Until now, I haven't
had this experience with other Apache Commons libraries.

Please advise, thank you!

Russ

sebb

2017-03-30 00:20:31 UTC

Permalink

Try

http://repo.maven.org/maven2/commons-io/commons-io/

IO used to have a different group id.

Post by Russell Bateman
As I attempt to build, I find
https://repo.maven.apache.org/maven2/org/apache/commons/commons-io/2.5/commons-io-2.5.jar
to yield a 404. When I go look there, only 1.3.2 exists and even that,
though there are JARs galore, has a /pom.xml/ that basically refers Maven to
Maven Central. Must I then put something into my /pom.xml/ that deters Maven
from ever looking for anything in /repo.maven.apache.org/? It seems strange
that Apache would offer a Maven repository that's missing an important
library (for me, at least). Until now, I haven't had this experience with
other Apache Commons libraries.
Please advise, thank you!
Russ

---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@commons.apache.org
For additional commands, e-mail: user-***@commons.apache.org

sebb

2017-03-30 00:24:15 UTC

Permalink

Post by sebb
Try
http://repo.maven.org/maven2/commons-io/commons-io/
IO used to have a different group id.

I mean, still has a different gid.

The entry under
https://repo.maven.apache.org/maven2/org/apache/commons/commons-io/1.3.2

is a relocation pom. Probably that version was accidentally released
with the wrong gid.

Post by sebb

---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@commons.apache.org
For additional commands, e-mail: user-***@commons.apache.org

Russell Bateman

2017-03-30 14:09:05 UTC

Permalink

Sebb,

Thanks for responding, but I probably need some help here making your
suggestion(s) work. To begin with,

http://repo.maven.org/maven2/commons-io/commons-io/

yields nothing in the browser or using curl:

~/Downloads $ curl http://repo.maven.org/maven2/commons-io/commons-io/
curl: (6) Could not resolve host: repo.maven.org

Do I need something special in /~/.m2/settings.xml/? (I don't have one.)
or in my /pom.xml/ file(s)? If it's only that the groupIdhas changed,
what is it? Can you give me a Maven replacement for what's at:

https://mvnrepository.com/artifact/commons-io/commons-io/2.5

I don't understand why this page exists since it clearly doesn't lead to
fulfilling my build's need for /commons-io-2.5.jar/. I use Maven a lot
and have for a long time, but I'm completely stumped by this issue.

Thanks.

Post by sebb

Post by sebb
Try
http://repo.maven.org/maven2/commons-io/commons-io/
IO used to have a different group id.

I mean, still has a different gid.
The entry under
https://repo.maven.apache.org/maven2/org/apache/commons/commons-io/1.3.2
is a relocation pom. Probably that version was accidentally released
with the wrong gid.

Post by sebb

---------------------------------------------------------------------

sebb

2017-03-30 14:27:31 UTC

Permalink

Post by Russell Bateman
Sebb,
Thanks for responding, but I probably need some help here making your
suggestion(s) work. To begin with,
http://repo.maven.org/maven2/commons-io/commons-io/
~/Downloads $ curl http://repo.maven.org/maven2/commons-io/commons-io/
curl: (6) Could not resolve host: repo.maven.org

Sorry, that should be

http://repo.maven.apache.org/maven2/commons-io/commons-io/

or
http://repo1.maven.org/maven2/commons-io/commons-io/
seems to work

But you should not need the URL if you are using Maven to build.

Post by Russell Bateman
Do I need something special in /~/.m2/settings.xml/? (I don't have one.) or
in my /pom.xml/ file(s)?

<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.5</version>
</dependency>

Post by Russell Bateman
If it's only that the groupIdhas changed, what is
it?

As above.
[It's not really changed - the one you mention at the start of this
thread is not currently used.]

Post by Russell Bateman
https://mvnrepository.com/artifact/commons-io/commons-io/2.5
I don't understand why this page exists since it clearly doesn't lead to
fulfilling my build's need for /commons-io-2.5.jar/. I use Maven a lot and
have for a long time, but I'm completely stumped by this issue.

You just need to include the correct dependency as above.

Post by Russell Bateman
Thanks.

Post by sebb

Post by sebb
Try
http://repo.maven.org/maven2/commons-io/commons-io/
IO used to have a different group id.

I mean, still has a different gid.
The entry under
https://repo.maven.apache.org/maven2/org/apache/commons/commons-io/1.3.2
is a relocation pom. Probably that version was accidentally released
with the wrong gid.

Post by sebb

---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@commons.apache.org
For additional commands, e-mail: user-***@commons.apache.org

Dave Newton

2017-03-30 14:35:34 UTC

Permalink

Post by sebb
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.5</version>
</dependency>

This worked fine for me; I guess I'm not understanding the issue.

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@commons.apache.org
For additional commands, e-mail: user-***@commons.apache.org

Russell Bateman

2017-03-30 15:26:25 UTC

Permalink

Wow. I believe the problem is that I'm a blind idiot. I had been trying
to use:

<dependency>
<groupId>*org.apache.commons*</groupId>
<artifactId>commons-io</artifactId>
<version>2.5</version>
</dependency>

The groupIdwas wrong and I just wasn't seeing it. (In my defence, there
are some Apache groupIds that include "apache" in path elements, like
Apache /commons-csv/, I'm used to looking at.)

Many thanks to sebb for his patience.

Post by Dave Newton

Post by sebb
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.5</version>
</dependency>

This worked fine for me; I guess I'm not understanding the issue.
Dave
---------------------------------------------------------------------

Matt Sicker

2017-03-30 15:29:37 UTC

Permalink

A lot of old artifacts uses the groupId == artifactId convention. I don't
know when that changed to using org.apache.foo as the groupId, but I'm
guessing it was sometime around the advent of Maven Central.

Wow. I believe the problem is that I'm a blind idiot. I had been trying to
<dependency>
<groupId>*org.apache.commons*</groupId>
<artifactId>commons-io</artifactId>
<version>2.5</version>
</dependency>
The groupIdwas wrong and I just wasn't seeing it. (In my defence, there
are some Apache groupIds that include "apache" in path elements, like
Apache /commons-csv/, I'm used to looking at.)
Many thanks to sebb for his patience.

Post by sebb

Post by sebb
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.5</version>
</dependency>

This worked fine for me; I guess I'm not understanding the issue.

Dave
---------------------------------------------------------------------

--
Matt Sicker <***@gmail.com>

sebb

2017-03-30 16:28:26 UTC

Permalink

Post by Matt Sicker
A lot of old artifacts uses the groupId == artifactId convention. I don't
know when that changed to using org.apache.foo as the groupId, but I'm
guessing it was sometime around the advent of Maven Central.

Possibly.

Commons components are gradually moving from commons-abc to
org.apache.commons.abc.
However that can only be done if the Java package name is also changed.
As that is disruptive, it's only done when an API breakage is essential.

https://wiki.apache.org/commons/MavenAndClasspath

Post by Matt Sicker

Post by sebb

Post by sebb
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.5</version>
</dependency>

This worked fine for me; I guess I'm not understanding the issue.

Dave
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@commons.apache.org
For additional commands, e-mail: user-***@commons.apache.org

Jörg Schaible

2017-03-30 17:12:21 UTC

Permalink

Post by sebb

Possibly.
Commons components are gradually moving from commons-abc to
org.apache.commons.abc.
However that can only be done if the Java package name is also changed.
As that is disruptive, it's only done when an API breakage is essential.
https://wiki.apache.org/commons/MavenAndClasspath

And for commons-io we had one wrongly published version (the one you were
referencing initially). After that we finalized the rule above.

Cheers,
Jörg

---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@commons.apache.org
For additional commands, e-mail: user-***@commons.apache.org