Hmm,
MvnRepository has not picked up the changes yet. It's strange. Filed a
ticket:
https://issues.apache.org/jira/browse/INFRA-16198
--
Denis
On Wed, Mar 14, 2018 at 5:34 AM, aaksenov wrote:
> it was uploaded to maven central no 05.03 and it seems it was most
it was uploaded to maven central no 05.03 and it seems it was most probably
just a local maven issue with cached metadata. Just not having it in
mvnrepository become confusing, sorry
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
just yesterday it couldn't be found (in http://repo.maven.apache.org) by
running mvn. Now that's there and ok! thank you!
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
That's not a maven central but rather a 3rd party portal that enlists maven
dependencies. We had a conversation about this with INFRA before:
https://issues.apache.org/jira/browse/INFRA-13073
I see that Ignite is already in maven central:
Thank you for noticing that.
Vladimir, is it expected for current release stage?
Sincerely,
Dmitriy Pavlov
вт, 13 мар. 2018 г. в 15:34, aaksenov :
> hello, it seems that 2.4 jars are missing in maven central
>
hello, it seems that 2.4 jars are missing in maven central
https://mvnrepository.com/artifact/org.apache.ignite/ignite-core
but the version has been released.
could you please upload them?
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/