Correction: 1.0.0 is available from mvnrepository.com, and from
https://repository.apache.org release repo; but not from maven.org - which
would create the situation I have described earlier, unless extra repos are
explicitely pointed to.
Apache Nexus maven-staging has the artifact:
https://repository.apache.org/content/groups/maven-staging-group/org/apache/ignite/ignite-core/1.0.0/
I wonder if the staging repo on Apache nexus was ever closed?
Cos
On Sat, Apr 11, 2015 at 07:44PM, Konstantin Boudnik wrote:
> It is pretty neat, actually! And quite helpful for something who needs to get
> started. BTW, I tried to the same in Groovy script
>
> <code>
> @Grab ('org.apache.ignite:ignite-core:1.0.0')
> @Grab ('org.apache.ignite:ignite-spring:1.0.0')
>
> import org.apache.ignite.Ignition
>
> Ignition.start('example-ignite.xml')
> <code/>
>
> and found out that release 1.0.0 artifacts aren't published anywhere. As the
> result, the above example fails as it can not find some transitive
> dependencies of ignite-core, e.g. javax.cache.Cache, spring-context.jar, etc.
>
> However, the same works just fine if I only use 1.0.0-RC3, which is clearly
> published on maven.org and other places. I believe there was a missed step in
> the release process, which needs to be documented and fixed during the next
> release. I will also open a JIRA so we can get 1.0.0 artifacts published
> properly.
>
> Cos
>
> On Fri, Apr 10, 2015 at 09:07PM, Dmitriy Setrakyan wrote:
> > https://www.youtube.com/watch?v=pFbDWpOiMOU
> >
> > And in case if you haven't watched the one about compute grid:
> > https://www.youtube.com/watch?v=J775J77_-B8
> >
> > D.
