Hi!
it seems that the version ID in your pom.xml is missing -incubating label. Am I missing something? Thanks, |
Yup, good catch. The tag is missed.
Created https://issues.apache.org/jira/browse/IGNITE-853 On Fri, May 01, 2015 at 10:40AM, Roman Shaposhnik wrote: > Hi! > > it seems that the version ID in your pom.xml > is missing -incubating label. Am I missing something? > > Thanks, |
Guys,
Ticket says only about top-level pom, but how about all our modules (e.g., ignite-spring, ignite-logj4, ...)? Should they have -incubating label as well? On Fri, May 1, 2015 at 4:55 PM, Konstantin Boudnik <[hidden email]> wrote: > Yup, good catch. The tag is missed. > > Created https://issues.apache.org/jira/browse/IGNITE-853 > > On Fri, May 01, 2015 at 10:40AM, Roman Shaposhnik wrote: > > Hi! > > > > it seems that the version ID in your pom.xml > > is missing -incubating label. Am I missing something? > > > > Thanks, > |
On Tue, May 5, 2015 at 12:33 AM, Valentin Kulichenko <
[hidden email]> wrote: > Guys, > > Ticket says only about top-level pom, but how about all our modules (e.g., > ignite-spring, ignite-logj4, ...)? Should they have -incubating label as > well? > I will let others respond, but my initial guess would be No. I think only the main ignite module should have artifact-id called "ignite-incubating", not the optional dependencies that it brings. By the way, is this documented anywhere? > > On Fri, May 1, 2015 at 4:55 PM, Konstantin Boudnik <[hidden email]> wrote: > > > Yup, good catch. The tag is missed. > > > > Created https://issues.apache.org/jira/browse/IGNITE-853 > > > > On Fri, May 01, 2015 at 10:40AM, Roman Shaposhnik wrote: > > > Hi! > > > > > > it seems that the version ID in your pom.xml > > > is missing -incubating label. Am I missing something? > > > > > > Thanks, > > > |
In reply to this post by Valentin Kulichenko
Yes, it is only about the pom artifact - not the binary ones.
Cos On Tue, May 05, 2015 at 12:33AM, Valentin Kulichenko wrote: > Guys, > > Ticket says only about top-level pom, but how about all our modules (e.g., > ignite-spring, ignite-logj4, ...)? Should they have -incubating label as > well? > > On Fri, May 1, 2015 at 4:55 PM, Konstantin Boudnik <[hidden email]> wrote: > > > Yup, good catch. The tag is missed. > > > > Created https://issues.apache.org/jira/browse/IGNITE-853 > > > > On Fri, May 01, 2015 at 10:40AM, Roman Shaposhnik wrote: > > > Hi! > > > > > > it seems that the version ID in your pom.xml > > > is missing -incubating label. Am I missing something? > > > > > > Thanks, > > |
As a matter of fact all artifacts that are expected to be deployed
have to have an incubating tag. Btw, most of the project I've seen just add it to the artifact version -- this seems to be the easiest and the most convenient way. Not sure why you guys decided to mangle the artifact name itself. Thanks, Roman. On Tue, May 5, 2015 at 11:23 AM, Konstantin Boudnik <[hidden email]> wrote: > Yes, it is only about the pom artifact - not the binary ones. > > Cos > > On Tue, May 05, 2015 at 12:33AM, Valentin Kulichenko wrote: >> Guys, >> >> Ticket says only about top-level pom, but how about all our modules (e.g., >> ignite-spring, ignite-logj4, ...)? Should they have -incubating label as >> well? >> >> On Fri, May 1, 2015 at 4:55 PM, Konstantin Boudnik <[hidden email]> wrote: >> >> > Yup, good catch. The tag is missed. >> > >> > Created https://issues.apache.org/jira/browse/IGNITE-853 >> > >> > On Fri, May 01, 2015 at 10:40AM, Roman Shaposhnik wrote: >> > > Hi! >> > > >> > > it seems that the version ID in your pom.xml >> > > is missing -incubating label. Am I missing something? >> > > >> > > Thanks, >> > |
On Tue, May 05, 2015 at 11:28AM, Roman Shaposhnik wrote:
> As a matter of fact all artifacts that are expected to be deployed > have to have an incubating tag. > > Btw, most of the project I've seen just add it to the artifact > version -- this seems to be the easiest and the most convenient > way. Not sure why you guys decided to mangle the artifact > name itself. That is a good way for sure, if everything needs to be changed. Changin all artifact names would be too much indeed. Cos > On Tue, May 5, 2015 at 11:23 AM, Konstantin Boudnik <[hidden email]> wrote: > > Yes, it is only about the pom artifact - not the binary ones. > > > > Cos > > > > On Tue, May 05, 2015 at 12:33AM, Valentin Kulichenko wrote: > >> Guys, > >> > >> Ticket says only about top-level pom, but how about all our modules (e.g., > >> ignite-spring, ignite-logj4, ...)? Should they have -incubating label as > >> well? > >> > >> On Fri, May 1, 2015 at 4:55 PM, Konstantin Boudnik <[hidden email]> wrote: > >> > >> > Yup, good catch. The tag is missed. > >> > > >> > Created https://issues.apache.org/jira/browse/IGNITE-853 > >> > > >> > On Fri, May 01, 2015 at 10:40AM, Roman Shaposhnik wrote: > >> > > Hi! > >> > > > >> > > it seems that the version ID in your pom.xml > >> > > is missing -incubating label. Am I missing something? > >> > > > >> > > Thanks, > >> > |
Can someone point me to what a <versionId> is? Here are the pom settings
for Ignite, what needs to be changed? <groupId>org.apache.ignite</groupId> <artifactId>ignite-core</artifactId> <version>1.1.0</version> On Tue, May 5, 2015 at 11:39 AM, Konstantin Boudnik <[hidden email]> wrote: > On Tue, May 05, 2015 at 11:28AM, Roman Shaposhnik wrote: > > As a matter of fact all artifacts that are expected to be deployed > > have to have an incubating tag. > > > > Btw, most of the project I've seen just add it to the artifact > > version -- this seems to be the easiest and the most convenient > > way. Not sure why you guys decided to mangle the artifact > > name itself. > > That is a good way for sure, if everything needs to be changed. Changin all > artifact names would be too much indeed. > > Cos > > > On Tue, May 5, 2015 at 11:23 AM, Konstantin Boudnik <[hidden email]> > wrote: > > > Yes, it is only about the pom artifact - not the binary ones. > > > > > > Cos > > > > > > On Tue, May 05, 2015 at 12:33AM, Valentin Kulichenko wrote: > > >> Guys, > > >> > > >> Ticket says only about top-level pom, but how about all our modules > (e.g., > > >> ignite-spring, ignite-logj4, ...)? Should they have -incubating label > as > > >> well? > > >> > > >> On Fri, May 1, 2015 at 4:55 PM, Konstantin Boudnik <[hidden email]> > wrote: > > >> > > >> > Yup, good catch. The tag is missed. > > >> > > > >> > Created https://issues.apache.org/jira/browse/IGNITE-853 > > >> > > > >> > On Fri, May 01, 2015 at 10:40AM, Roman Shaposhnik wrote: > > >> > > Hi! > > >> > > > > >> > > it seems that the version ID in your pom.xml > > >> > > is missing -incubating label. Am I missing something? > > >> > > > > >> > > Thanks, > > >> > > |
There's no such thing as versionId, but rather the version. In the example
below you might consider doing something like: <groupId>org.apache.ignite</groupId> <artifactId>ignite-core</artifactId> <version>1.1.0-incubating</version> On Tue, May 05, 2015 at 11:48AM, Dmitriy Setrakyan wrote: > Can someone point me to what a <versionId> is? Here are the pom settings > for Ignite, what needs to be changed? > > <groupId>org.apache.ignite</groupId> > <artifactId>ignite-core</artifactId> > <version>1.1.0</version> > > On Tue, May 5, 2015 at 11:39 AM, Konstantin Boudnik <[hidden email]> wrote: > > > On Tue, May 05, 2015 at 11:28AM, Roman Shaposhnik wrote: > > > As a matter of fact all artifacts that are expected to be deployed > > > have to have an incubating tag. > > > > > > Btw, most of the project I've seen just add it to the artifact > > > version -- this seems to be the easiest and the most convenient > > > way. Not sure why you guys decided to mangle the artifact > > > name itself. > > > > That is a good way for sure, if everything needs to be changed. Changin all > > artifact names would be too much indeed. > > > > Cos > > > > > On Tue, May 5, 2015 at 11:23 AM, Konstantin Boudnik <[hidden email]> > > wrote: > > > > Yes, it is only about the pom artifact - not the binary ones. > > > > > > > > Cos > > > > > > > > On Tue, May 05, 2015 at 12:33AM, Valentin Kulichenko wrote: > > > >> Guys, > > > >> > > > >> Ticket says only about top-level pom, but how about all our modules > > (e.g., > > > >> ignite-spring, ignite-logj4, ...)? Should they have -incubating label > > as > > > >> well? > > > >> > > > >> On Fri, May 1, 2015 at 4:55 PM, Konstantin Boudnik <[hidden email]> > > wrote: > > > >> > > > >> > Yup, good catch. The tag is missed. > > > >> > > > > >> > Created https://issues.apache.org/jira/browse/IGNITE-853 > > > >> > > > > >> > On Fri, May 01, 2015 at 10:40AM, Roman Shaposhnik wrote: > > > >> > > Hi! > > > >> > > > > > >> > > it seems that the version ID in your pom.xml > > > >> > > is missing -incubating label. Am I missing something? > > > >> > > > > > >> > > Thanks, > > > >> > > > |
Free forum by Nabble | Edit this page |