New module

[Juan Carlos Fiorenzano]

Hello everybody I wan to create a new module to integrate Ignite with
Spring data, I was to the developer guide to see if there specific steps to
build a module but I only saw the notice about the README and the license,
but I have a very silly doubt but I want to do everything perfect, when you
create a new module the module's version has to be the same that the
project [1.6.0-SNAPSHOT] or the module can has its own version?, I ask this
because when you write the dependencies for your module you write this in
the POM:

<dependency>
<groupId>org.apache.ignite</groupId>
<artifactId>ignite-core</artifactId>
* <version>**${project.version}**</version>*
</dependency>

If the module doesn't have to have the same version than the core what
alternative I have to
*${project.version}* for always have the lastest version of the core?

Thanks in advance.

[Valentin Kulichenko]

Hi Juan,

All our modules have the same version. So when you create a new one, simply
specify the same version that ignite-core has.

-Val

On Wed, May 25, 2016 at 9:44 AM, Juan Carlos Fiorenzano <
[hidden email]> wrote:

> Hello everybody I wan to create a new module to integrate Ignite with
> Spring data, I was to the developer guide to see if there specific steps to
> build a module but I only saw the notice about the README and the license,
> but I have a very silly doubt but I want to do everything perfect, when you
> create a new module the module's version has to be the same that the
> project [1.6.0-SNAPSHOT] or the module can has its own version?, I ask this
> because when you write the dependencies for your module you write this in
> the POM:
>
> <dependency>
> <groupId>org.apache.ignite</groupId>
> <artifactId>ignite-core</artifactId>
> * <version>**${project.version}**</version>*
> </dependency>
>
> If the module doesn't have to have the same version than the core what
> alternative I have to
> *${project.version}* for always have the lastest version of the core?
>
> Thanks in advance.
>

[Juan Carlos Fiorenzano]

Ok thank you

On Wednesday, May 25, 2016, Valentin Kulichenko <
[hidden email]> wrote:

> Hi Juan,
>
> All our modules have the same version. So when you create a new one, simply
> specify the same version that ignite-core has.
>
> -Val
>
> On Wed, May 25, 2016 at 9:44 AM, Juan Carlos Fiorenzano <
> [hidden email] <javascript:;>> wrote:
>
> > Hello everybody I wan to create a new module to integrate Ignite with
> > Spring data, I was to the developer guide to see if there specific steps
> to
> > build a module but I only saw the notice about the README and the
> license,
> > but I have a very silly doubt but I want to do everything perfect, when
> you
> > create a new module the module's version has to be the same that the
> > project [1.6.0-SNAPSHOT] or the module can has its own version?, I ask
> this
> > because when you write the dependencies for your module you write this in
> > the POM:
> >
> > <dependency>
> > <groupId>org.apache.ignite</groupId>
> > <artifactId>ignite-core</artifactId>
> > * <version>**${project.version}**</version>*
> > </dependency>
> >
> > If the module doesn't have to have the same version than the core what
> > alternative I have to
> > *${project.version}* for always have the lastest version of the core?
> >
> > Thanks in advance.
> >
>