Re: [DISCUSS] Ignite Update Checker

Hey guys In my opinion, maven.org is still owned by a third party (Sonatype). We don't know what kind of data analysis or intelligence extraction they run. If Ignite servers all over the world were hitting maven.org periodically asking for an Ignite Maven artifact, it gives Sonatype a clear

Re: Updating Apache Camel Integration to the latest version

Sure, I'll try to do it this week. Cheers! On 31 Jul 2017 21:22, "Denis Magda" wrote: > Hello Raul, > > Would you mind updating the Apache Camel integration to the latest Ignite > version (2.1)? The current one is pretty outdated - 1.9. >

Fwd: Updating Ignite Version on Apache Camel Side

ernal integrations Date: October 27, 2016 at 4:11:08 PM PDT To: mailto:dev@ignite.apache.org , Raul Kripalani < mailto:ra...@apache.org > Igniters, I’ve prepared the page that includes all the external projects/products that integrate with Apache Ignite.  https://cwiki.apache.org/conf

Fwd: Updating Ignite Version on Apache Camel Side

in forwarded message: From: Denis Magda < mailto:dma...@gridgain.com > Subject: Page with external integrations Date: October 27, 2016 at 4:11:08 PM PDT To: mailto:dev@ignite.apache.org , Raul Kripalani < mailto:ra...@apache.org > Igniters, I’ve prepared the page that includes a

Re: Ignite Maven project version number

have any problems with it. Thus decided to introduce it to community. > > > Igor Rudyak > > > > > > On Thu, Aug 18, 2016 at 5:21 AM, Raul Kripalani <r...@evosent.com> wrote: > > > Hi Igor, > > > > Unfortunately the ${app.version} approach does not

Re: Ignite Maven project version number

on}* > 5) Such a way, if you want switch to development of next version - you just > need to change ${app.version} property in parent POM and it will be > automatically "reused" by all other POMs. The benefit here is that we need > to change version number only in one place. >

Re: Ignite Maven project version number

On Wed, Aug 17, 2016 at 11:14 PM, Igor Rudyak wrote: > It's not the solution in this case, cause parent version is always "1" > What's the reason we've chosen to handle the hierarchy differently to most other projects out there? ​Have we considered versioning the parent POM?

Re: Ignite Maven project version number

Igor, To my knowledge, you can just remove the version tag altogether, and the module will inherit the version from the parent. Cheers. --- Raúl Kripalani linkedin.com/in/raulkripalani | evosent.com | blog: raul.io

Re: Let's make cache name not null in ignite 2.0

On Thu, Jun 2, 2016 at 5:56 PM, Alexey Kuznetsov wrote: > User can create cache via Spring XML and simply not specify property > "name". > And Yes, Ignite will take null without any warning. > > I think we at least should start to print warning in current Ignite 1.x. >

Re: Apache Flink <=> Apache Ignite integration

On Wed, Mar 30, 2016 at 2:20 PM, Roman wrote: > Raul, > > Small comment from me. > > >* As a Flink sink => inject data directly into a cache via a DataStreamer. > After reviews, IGNITE-813 is exactly this functionality. > > That's cool, Roman! The idea would be to host

Apache Flink <=> Apache Ignite integration

Hello from the Apache Ignite community! Last year there was an interesting thread [1] about such integration. Unfortunately there's been little follow-through, so let's try and fix that in 2016 ;-) I'm sure a lot has changed in the Flink community, with the recent graduation and 1.0 release, so

Re: Contributions that are waiting for review

I believe all we need is a shell script in our source tree that queries the JIRA API and produces an output on stdout. We can then schedule an overnight job with, e.g. a 0 23 * * * cron expression, and configure the output to be sent to the ML, as indicated here:

Re: Contributions that are waiting for review

e has been waiting. > > I have some experience with JIRA REST API, so maybe I could help with this. > > On Thu, Mar 3, 2016 at 6:24 PM, Raul Kripalani <ra...@apache.org> wrote: > > > How about a nightly job that fetches all tickets from JIRA which are > > unresolved a

Re: Switching back to review-then-commit process

On Thu, Mar 3, 2016 at 5:46 PM, Raul Kripalani <ra...@apache.org> wrote: > * CTR for contributors for all modules, for obvious reasons (no commit > access ;-)). > Obviously, I meant RTC! *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big

Re: Switching back to review-then-commit process

the > functionality, RTC makes sense. > > On Thu, Mar 3, 2016 at 7:20 AM, Raul Kripalani <ra...@apache.org> wrote: > > > I thought we were already on RTC process. > > > > What do you mean with contributors following this process? > > > > Raúl.

Re: Contributions that are waiting for review

How about a nightly job that fetches all tickets from JIRA which are unresolved and have Patch Available = true, and (1) sends them to the dev ML or (2) posts it in Gitter? Will it help raise awareness and put them on the radar? Raúl. On 2 Mar 2016 20:47, "Denis Magda"

Re: Switching back to review-then-commit process

I thought we were already on RTC process. What do you mean with contributors following this process? Raúl. On 3 Mar 2016 11:54, "Denis Magda" wrote: > Igniters, > > I would propose to switch back to review-then-commit process. This process > has to be followed by both

Re: streamer documentation

at 6:31 AM, Denis Magda <dma...@gridgain.com> wrote: > Thanks Raul! > > Please don't forget to add the doc to both 1.5 and 1.6 [1], that has been > recently created. > > [1] https://apacheignite.readme.io/v1.6 > > -- > Denis > > > On 2/11/2016 1:34 AM, Raul

Re: OSGi Support?

:01, "Dmitriy Setrakyan" <dsetrak...@apache.org> wrote: > Raul, > > To my knowledge Ignite can run under OpenJDK as well. Would this package be > required in OpenJDK? > > D. > > On Sat, Feb 20, 2016 at 11:24 AM, Raul Kripalani <ra...@apache.org> wrote:

Re: OSGi Support?

Hey John, Yeah, this is expected. Ignite uses some packages only available in the Oracle JDK (proprietary Sun packages). Karaf doesn't export the sun.nio.ch package by default from bundle 0 (system bundle). You need to add it to the jre.properties file manually in the Karaf etc directory. Then

Re: The Changelog podcast

Yep. Github way of voting tends to be a "+1" comment. On 30 Jan 2016 00:16, "Dmitriy Setrakyan" <dsetrak...@apache.org> wrote: > Raul, > > How do I give it a +1 on github? Should I just reply to your original > comment? > > D. > > On Fri, Jan 29,

Re: New method in IgniteCache API.

Hello, How often will end users invoke this functionality? It sounds somewhat like an administrative function. If it won't be invoked frequently, and its function is not on par with get(), put(), etc., I would propose to add the method to IgniteCacheEx instead, to avoid excessively polluting

Re: Ignite Voting Process

Hi Brane, On Thu, Dec 31, 2015 at 8:58 AM, Branko Čibej wrote: > We'd be publishing modules that can't be used without the LGPL > components. I'm not sure how that stands WRT our policies but I can't > see how it would be a service to our users to actively nudge them > towards

Re: Ignite Voting Process

Hi Anton, Why don't we publish artifacts for ignite-geospatial, ignite-hibernate and ignite-schedule? The lgpl profile is not triggered in these instructions, and these artifacts cease existing in Maven Central 1.2.0-incubating onwards. I know they depend on LGPL-licensed libraries, but we can

Re: [VOTE] Apache Ignite 1.5.0.final RC3

+1 binding. *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Tue, Dec 29, 2015 at 10:54 AM, Anton Vinogradov

We are live on OpenHub!

Hey guys, I took some time to configure our project on OpenHub and we're now live with analytics! https://www.openhub.net/p/apache-ignite Regards, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani |

Re: UNRESOLVED tickets

My resolved tickets can be closed too. I wasn't aware that you differentiated both statuses in this project. Will do it later when I'm on a computer. Raúl. On 22 Dec 2015 06:26, "Dmitriy Setrakyan" wrote: > Raul, Cos, > > You have 9 tickets in RESOLVED state for 1.5

Re: 1.5.final

On Tue, Dec 22, 2015 at 9:25 AM, Anton Vinogradov wrote: > IGNITE-2116 ignite-osgi-karaf has only readme and license files > Waiting for Raul's answer. > Replied in the ticket. Sorry for the delay. Too many open fronts! *Raúl Kripalani* PMC & Committer @ Apache

Re: Changes for ignite-jms11 and ignite-mtqq modules for fabric binary package

On Thu, Dec 10, 2015 at 9:54 AM, Sergey Kozlov wrote: > libs/optional/ignite-jms11/ > jms-api-1.1-rev-1.jar replaced by geronimo-jms_1.1_spec-1.1.1.jar > Correct. The same API but the latter is OSGi friendly. > libs/optional/ignite-mqtt/ > added guava-18.0.jar > In

Re: ignite-osgi-karaf on maven repository

It's a very valid question, indeed. A Karaf feature is simply a shortcut to install modules in the OSGi container, so I don't see a problem with the ignite-hibernate feature itself. We do not distribute Hibernate. However, where I do see a possible risk is with the ignite-all feature, which

Re: Introduction letter.

Welcome to the community, Vladimir! *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Thu, Dec 10, 2015 at 9:08 AM,

Re: [ANNOUNCE] Apache Ignite official chatroom

On Thu, Dec 3, 2015 at 3:30 AM, Dmitriy Setrakyan wrote: > Specifically, your pretty Readme.md is not showing. Any ideas how to fix? > I had to sync it up manually. I thought that GH had an option to keep forks synced as long as they hadn't diverged. I was mistaken. If

Re: [ANNOUNCE] Apache Ignite official chatroom

On Thu, Dec 3, 2015 at 3:11 PM, Dmitriy Setrakyan wrote: > Where did you click? Unfortunately it's a manual process: https://help.github.com/articles/syncing-a-fork/. *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging

New README.md for Github

Ladies and gents, While I was adding the Gitter badge I realised we don't have a nice README.md. So I created one. Let me know what you think: https://github.com/apache/ignite Regards, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging

[ANNOUNCE] Apache Ignite official chatroom

Hello users, Hello team! The Apache Ignite PMC is pleased to announce that the project now has an official chatroom on Gitter: https://gitter.im/apacheignite/ignite. Come join us there! All you need is a Github account. We've updated the Ignite website accordingly:

[ANNOUNCE] Apache Ignite official chatroom

Hello users, Hello team! The Apache Ignite PMC is pleased to announce that the project now has an official chatroom on Gitter: https://gitter.im/apacheignite/ignite. Come join us there! All you need is a Github account. We've updated the Ignite website accordingly:

Re: [VOTE] Apache Ignite 1.5.0-b1

+1 Raúl. On Wed, Dec 2, 2015 at 12:16 PM, Yakov Zhdanov wrote: > Dear Sirs! > > We have uploaded release candidate to > https://dist.apache.org/repos/dist/dev/ignite/1.5.0-b1-rc1/ > > This is very important release containing initial versions of Ignite.NET > and Ignite C++

Re: EA versioning

Ok from me, the troublemaker :) Glad that we agreed on a policy. On 1 Dec 2015 19:51, "Yakov Zhdanov" wrote: > Guys, I like the scheme we have come to. > > Will submit apache-ignite-1.5.0-b1-rc1 for vote tomorrow :) > > --Yakov >

Re: EA versioning

On Tue, Dec 1, 2015 at 5:57 PM, Sergi Vladykin wrote: > Thanks, Raul! I like your synthesis. > > We have already agreed to use 1.5.0-*b1* format for early access builds, > but I did not see any opinions about *final* for releases. > Does anyone have objections to use

Re: EA versioning

On Tue, Dec 1, 2015 at 7:12 PM, Dmitriy Setrakyan wrote: > > In that case, if we add “.final” suffix, will it satisfy both, Maven and > OSGI worlds? Yep. In fact, "final" in Maven is equivalent to no qualifier. From Javadoc [1]: strings are checked for well-known

Re: EA versioning

On Tue, Dec 1, 2015 at 6:55 PM, Dmitriy Setrakyan wrote: > What would the “final” qualifier give us? From what I can see, Maven > version comparison will work fine without it. Does maven have special > handling for the “final” suffix? > Yes it does. And OSGi doesn't, so a

Re: EA versioning

On Tue, Dec 1, 2015 at 7:15 PM, Dmitriy Setrakyan wrote: > Raul, as an OSGI expert, do you confirm? > Yep, it was my proposal only to add "-final". Just to be clear, this is a Maven qualifier. The maven-bundle-plugin will translate the hyphen to a dot, for compatibility

Re: [VOTE] Apache Ignite 1.5.0-EA

Thank you, Yakov! It's appreciated. On 1 Dec 2015 07:42, "Yakov Zhdanov" wrote: > Guys, let's close this vote thread. I think we will resubmit another build > today evening. I will also send out my vision on EA process and I ask > everyone to respond on that thread. > >

Re: EA versioning

It is different when the keyword is part of the version (1.1.1.RELEASE), like Spring, and when it's a qualifier (1.1.1-RELEASE). Maven treats both cases differently. On 1 Dec 2015 14:52, "Yakov Zhdanov" wrote: > Sergi, very good point! Guys, it seems that EA is not a good

Re: Ignite-1.5 Release

On Mon, Nov 30, 2015 at 5:05 PM, Yakov Zhdanov wrote: > Raul, every build submitted for vote is RC (so, on first iteration this > will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get > official release. My idea is to have EA available via maven and from the >

Re: Ignite-1.5 Release

On Mon, Nov 30, 2015 at 5:23 PM, Yakov Zhdanov wrote: > 1. I see nothing wrong in having EA perpetually available. I would even > prefer all vendors to keep all EA versions available just for tracking and > history purposes. > We have opposite views here. To me, early

Re: Ignite-1.5 Release

gt; wrote: > Hi > > Some companies provide EA releases in maven: > > > https://oss.sonatype.org/content/repositories/releases/com/hazelcast/hazelcast/3.6-EA/ > > > On Mon, Nov 30, 2015 at 9:39 PM, Raul Kripalani <ra...@apache.org> wrote: > > > On Mon, N

Re: [VOTE] Apache Ignite 1.5.0-EA

On Mon, Nov 30, 2015 at 11:25 PM, Andrey Kornev wrote: > And since you've asked for opinions, it's also my opinion that the > discussion about the naming was a non-consequential bikeshedding ( > https://en.wikipedia.org/wiki/Parkinson's_law_of_triviality) and >

Re: Optional modules without README and apache license

On Fri, Nov 27, 2015 at 9:38 AM, Anton Vinogradov wrote: > Raul, we are goin to make release today (4 hours later this email) is it > possible to push jms11, zk, mqtt changes before this moment? > Changes pushed. Regards, *Raúl Kripalani* PMC & Committer @ Apache

Re: OSGi integration ready for review

t.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Tue, Nov 24, 2015 at 8:11 PM, Raul Kripalani <ra...@apache.org> wrote: > Hello all, > > The initial OSGi integration is ready for review in branch ignite-1270. > Feature

Re: ignite is not listed among Apache projects

On Thu, Nov 26, 2015 at 1:22 PM, Dmitriy Setrakyan wrote: > Anyone knows how do we get a mention on this page? > http://projects-old.apache.org/indexes/quick.html > We need a DOAP file (Description Of A Project) for Ignite, and once we have that, we get in touch with

OSGi integration ready for review

Hello all, The initial OSGi integration is ready for review in branch ignite-1270. Features included: * OSGi manifest for most modules. I could OSGi-fy 22 modules. Some are left out due to complexity or not supporting OSGi: hadoop, mesos, cloud, gce, yarn, etc. * Karaf features repository with 1

Re: Ignite-1.5 Release

HI Romain, On Tue, Nov 24, 2015 at 4:14 PM, Romain Gilles wrote: > I have some comments for your pull request, one or two points. How does it > works do you plan to create a pull request? > I personally don't create pull requests as I am a committer. The code is in the

Re: Ignite-1.5 Release

On Tue, Nov 24, 2015 at 9:32 AM, Dmitriy Setrakyan wrote: > At the risk of sounding pedantic, I think this link is best included as > part of some other OSGI documentation page (no?): > https://dash.readme.io/project/apacheignite/v1.5/docs/introduction > The page

Re: Branch deletion prohibited

Hi Brane, I hadn't joined the project back then, so I don't know the history, but my guess is that the loss of traceability might have occurred as a result of importing the code from an external repository. I don't see why they could be attributed to branch deletion – probably I'm not feeling

Re: Ignite-1.5 Release

Igniters, OSGi integration is basically done. I need to give it another review pass. I also want to see if I can OSGi-fy the new modules quickly (twitter, flume, etc). Meanwhile I've worked on the documentation and it's pretty much done: *

Re: Branch deletion prohibited

Exactly. Let's wait for Infra's feedback on why that restriction and when it'll be lifted.

Re: Ignite-1.5 Release

Branch ignite-1790 merged into ignite-1.5 with --squash. Like it was requested previous on previous occasions. On 19 Nov 2015 03:01, "Dmitriy Setrakyan" <dsetrak...@apache.org> wrote: > On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani <r...@evosent.com> wrote: > >

Re: Branch deletion prohibited

gt; > > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > > > > > > > Raul, > > > > > > > > ASF is currently prohibiting deletion of GIT branches until further > > > notice. > > > > Please add your branch

Re: Branch deletion prohibited

s leads to tons of garbage in repo and abandoned branches, etc. > > > > --Yakov > > > > 2015-11-19 12:19 GMT+03:00 Raul Kripalani <r...@evosent.com>: > > > > > As I said: "Pull requests make sense when outsiders want to make > > > contributions

Re: Branch deletion prohibited

your branch to this Wiki page, so we don’t loose track: > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete > > > > Thanks, > > D. > > > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani <ra...@apache.org> &g

Re: Ignite-1.5 Release

a look to your pull request. > > Thanks, > > Romain > > Le jeu. 19 nov. 2015 à 04:01, Dmitriy Setrakyan <dsetrak...@apache.org> a > écrit : > > > On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani <r...@evosent.com> > wrote: > > > > > I merge

Re: Branch deletion prohibited

r can contribute. > > --Yakov > > 2015-11-19 12:08 GMT+03:00 Raul Kripalani <r...@evosent.com>: > > > I disagree. > > > > Code should be in the ASF infra. > > > > Pull requests make sense when outsiders want to make contributions. > > >

Re: Branch deletion prohibited

On Thu, Nov 19, 2015 at 9:28 AM, Yakov Zhdanov wrote: > But this leads to tons of garbage in repo and abandoned branches, etc. > "Let's not do X because our developers are irresponsible and leave branches behind?" -- Really? We have a zillion-pages set of contribution

Re: Ignite-1.5 Release

Can someone please clarify the *exact* release schedule? I hear that the merges may be completed tomorrow Friday, but the release will be built next Friday. Is this correct? I'm finishing my work on the OSGi integration (three modules), which I'd like to get into 1.5. I'm pretty much done, and

Re: Javadoc warnings at Ignite 1.5

gt; I've added some requirment to > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > Please see section Checklist before pust > < > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Checklistbeforepust > > > . > > On Thu, Nov 19,

Re: Branch deletion prohibited

ry restricted by INFRA. As soon as it is > > enabled again why not using it? It is the easiest way to provide > > contributions and review them. > > > > On Thu, Nov 19, 2015 at 12:49 PM, Raul Kripalani <ra...@apache.org> > wrote: > > > > > Lads, > > &g

Re: Javadoc warnings at Ignite 1.5

t; > > > I've added some requirment to > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > > Please see section Checklist before pust > > > < > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Co

Branch deletion prohibited

Fellows, I'm trying to push a branch deletion and the ASF Git tells me that branch deletion is prohibited. Has someone changed something? [raul@~/Workbench/Source/ignite$] git push -f origin :ignite-1790 remote: error: denying ref deletion for refs/heads/ignite-1790 To

Re: Ignite-1.5 Release

I merged the Camel Streamer today and I hope to finish the first phase of OSGi tomorrow. I'll need someone to review the latter quickly if we want it merged for 1.5... No code changes in existing codebase. Just a new osgi module and many POM changes mainly to generate the manifests. Should be a

Re: Review the new Camel Streamer (IGNITE-1790)

On Mon, Nov 16, 2015 at 12:32 PM, Denis Magda wrote: > Is there any chance we make this contribution available as a part of the > upcoming release? > Yes, it'll be. Will get around to reviewing it by tomorrow. *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel

Re: Check Ignite code base with Findbugs.

I'd prefer to plug it into the Maven build: https://gleclaire.github.io/findbugs-maven-plugin/. *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani

Re: ignite-platform module

On Thu, Nov 12, 2015 at 8:24 PM, Dmitriy Setrakyan wrote: > How about renaming your module folders as following: > > - modules > |— osgi > |— osgi-karaf > |— osgi-paxlogging > Sounds good to me! *Raúl Kripalani* PMC & Committer @ Apache Ignite,

Re: ignite-platform module

On Thu, Nov 12, 2015 at 5:23 PM, Dmitriy Setrakyan wrote: > Vladimir, I think it is unclear how one approach is better than the other > apart from just being different. I would avoid undertaking this type of > restructuring unless we have a really compelling reason. > I

Re: ignite-platform module

On Thu, Nov 12, 2015 at 8:24 PM, Dmitriy Setrakyan wrote: > Raul, following this logic, we should also group all streaming integration > into one streaming folder and so on… My vote is to keep the structure > consistent and flat for now, and if the community decides that

Latest state of new Binary format

Hello, I need to know in which branch the latest state of the Binary format is, in order to introduce changes. It is my understanding that it hasn't been merged to 1.5 yet, right? Regards, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging

ignite-platform module

Hello, Currently we have a single ignite-platform module aggregating all sources for .NET and CPP integration. For the OSGi integration I'm working on, I need to add two modules to the Ignite codebase to facilitate deploying Ignite on top of Apache Karaf (OSGi container). One can regard Apache

Re: Latest state of new Binary format

http://blog.raulkr.net | twitter: @raulvk On Thu, Nov 12, 2015 at 12:46 PM, Raul Kripalani <ra...@apache.org> wrote: > Hello, > > I need to know in which branch the latest state of the Binary format is, > in order to introduce changes. > > It is my understanding that it hasn't b

Re: OSGi migration may require a special marshaller

On Wed, Nov 11, 2015 at 1:48 AM, Dmitriy Setrakyan wrote: > Raul, we cannot be adding package name and version in all cases, as it will > have a negative impact on performance, especially when there is an > *optimistic* approach that requires no over-the-wire overhead

Re: OSGi Manifest headers and feature repository pushed (IGNITE-1527)

t be more > appropriate to treat all Ignite dependencies as “Fragments”. > > [1] http://wiki.osgi.org/wiki/Fragment > > On Wed, Nov 11, 2015 at 3:41 AM, Raul Kripalani <ra...@apache.org> wrote: > > > Hey Dmitriy, > > > > On Wed, Nov 11, 2015 at 1:52 AM, Dmit

Re: Ignite-1.5 Release

Sorry I haven't made an appearance in this thread yet. > 6. MQTT streamer > https://issues.apache.org/jira/browse/IGNITE-535 Yes, it was merged to master before the ignite-1.5 was created. I'd like to add: Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790 -- I'll merge this

Re: OSGi migration may require a special marshaller

free me to implement a temporary OSGi version by the time you are > done with the overall IGNITE-1270 tasks. > > Thanks, > > Romain > > Le mar. 10 nov. 2015 à 15:42, Raul Kripalani <r...@evosent.com> a écrit : > > > Hi Romain, > > > > If you don't mind,

OSGi Manifest headers and feature repository pushed (IGNITE-1527)

Hi all, Just to inform you that I've pushed the POM changes to generate the OSGi Manifest for all Java modules except: gce, cloud, hadoop, log4j2, spark, yarn, mesos, as the prove a bit more difficult for different reasons each. Some modules are bundles (e.g. mqtt, zookeeper, kafka, etc.) while

Re: IGNITE-1527 Add OSGi manifest headers

Yes, it's done. Please check the branch. I'm working on finishing the features.xml. Hopefully done this evening or tomorrow. On 9 Nov 2015 16:47, "Romain Gilles" wrote: > Hi Raoul, > Did you start on this task? I will be please to help you on it. > > Romain. >

Re: OSGi migration may require a special marshaller

> > > > > > > > Romain > > > > > > > > > > > > Le mar. 3 nov. 2015 à 20:05, Dmitriy Setrakyan < > > dsetrak...@apache.org> > > > > a > > > > > > écrit : > >

Re: log4j2 garbage files

>>> Gianfranco, please, review and merge the fix. >>> >>> Thanks, >>> -- Artem -- >>> >>> On Thu, Oct 29, 2015 at 9:46 PM, Raul Kripalani <ra...@apache.org> >>> wrote: >>> >>> Gianfranco, Artem, >>>> &

Re: OSGi migration may require a special marshaller

extension point in the class resolution > mechanism it can be interesting for end user in order to allow them to > optimize it based on there specific use cases. > > Romain. > > Le mar. 3 nov. 2015 à 00:21, Raul Kripalani <r...@evosent.com> a écrit : > > > Hi Andre

Re: Questions about TeamCity CI organization

anization? I think there is no needs > to change something. > > Thanks, > -- Artem -- > > On Tue, Nov 3, 2015 at 12:27 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > I am also curious to get answers to the questions posted by Raul. Can > > someone kno

RE: OSGi migration may require a special marshaller

Hi Andrey, Thanks for the participation in this topic. I don't like the solution to incorporate the bundle symbolic name in the serialised form. Nothing guarantees that the classdef will be located under the same bundle in both source and target machines. We also have to take into account that

Re: OSGi migration may require a special marshaller

Hi Romain, I'm working on the OSGi compatibility of Ignite. I appreciate your input. I'm thinking about the situation you describe and I wonder if you're exporting Ignite as an OSGi service which is then consumed from other bundles. Under this situation, it would be quite easy to reproduce the

AWS Tests on TeamCity

I'm working on upgrading the dependencies of ignite-aws, as we need the upgrade for OSGi integration. Unfortunately, it seems the AWS builds on TeamCity are failing because the AWS API params cannot be resolved: %secure:teamcity.password.env.test.amazon.access.key%

Re: AWS Tests on TeamCity

2015 at 4:25 PM, Denis Magda <dma...@gridgain.com> wrote: > > > Nick, should know the credentials. > > > > Nick, please help Raul with the setup. > > > > > > -- > > Denis > > > > > > On 10/29/2015 4:16 PM, Raul Kripalani wrote: > > &

Re: AWS Tests on TeamCity

; > Nick, should know the credentials. > > > > Nick, please help Raul with the setup. > > > > > > -- > > Denis > > > > > > On 10/29/2015 4:16 PM, Raul Kripalani wrote: > > > >> I'm working on upgrading the dependencies of ign

log4j2 garbage files

Gianfranco, Artem, Could you please check why we have garbage source files ending in a twiddle ~ inside the log4j2 module? https://github.com/apache/ignite/tree/master/modules/log4j2/src/main/java/org/apache/ignite/logger/log4j2 Thanks, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache

Re: Review the new Camel Streamer (IGNITE-1790)

es it work for you? > > -- > Denis > > On 10/28/2015 3:51 PM, Raul Kripalani wrote: > >> Hello, >> >> I've pushed a new Apache Camel streamer in the ignite-1790 branch. >> >> Build and tests ran successfully on TC (Ignite Streamers build config)

Regrouping of streamers under TeamCity

Hello all, I've regrouped Ignite streamer modules in TeamCity into the existing Ignite Streamers build configuration. Thus, the separate Ignite JMS and Ignite MQTT have disappeared. I faced some troubles with the ActiveMQ KahaDB file locks in TeamCity, hence my commits today in that module, as I

WebSockets with Apache Ignite

Hey guys, I'd like to gauge the interest in the community for a WebSockets client for Apache Ignite. Such a client would allow users to build browser-based real-time enterprise apps that interact with Apache Ignite directly, omitting the middleware for simple use cases. Browsers would be able to

Re: Account @ TeamCity, please

builds manually. > > D. > > On Fri, Oct 23, 2015 at 11:14 AM, Raul Kripalani <ra...@apache.org> wrote: > > > Hey guys, > > > > Could someone please create an account for me @ TeamCity with > committer/PMC > > permissions? > > > > Thanks

Questions about TeamCity CI organization

Hey guys, I have a few questions about the way our builds are organised in TeamCity. 1. All build configurations seem to be building the entire project tree. Is this correct? 2. The goal of the build configurations here is to partition the tests so that the test execution can be distributed

Re: Data Snapshots in Ignite

. Regards, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Wed, Oct 21, 2015 at 10:06 AM, Raul Kripalani

  1   2   >