From: "John Mazzitelli" <mazz(a)redhat.com&gt; To: "Discussions around Hawkular development" <hawkular-dev(a)lists.jboss.org&gt; Sent: Tuesday, July 21, 2015 11:42:06 AM Subject: [Hawkular-dev] glue code - where does it go? We have a fairly annoying problem with our current glue code location. Right now, we have the "glue code" that is known as "feed-comm" inside the hawkular repo - there is specifically the "feed-comm-api" artifact that contains some Java code that is required for use by Java-based feeds in order to talk to the server (also includes some JSON schemas for non-Java feeds to use). But since this is in hawkular repo, my agent needs a hawkular release in order to pull in the feed-comm-api artifact! Well, obviously, that's what we are moving toward for next week - a alpha hawkualr release. But until that happens, I can't release the agent. But, interestingly enough, because hawkular (kettle) contains the agent, hawkular can't be released until it has an agent release to pull in. Round and round we go. I really hate saying we need yet another repo, but how else can we get glue code that is common between server and feeds/agents that isn't dependent upon a hawkular release being made? _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev

Yes, I am going to move it to bus. I think its a good place. Doing that now. ----- Original Message ----- > Hi, > thinking about it, it could probably even stay as it is, but it would > require the "feed-comm" mvn module to have it's own release cycle > independent on hawkular (not share the ${project.version} as it is right > now). Also, I think, the feed-comm can't depend back on the root pom via > <parent><relativePath>, then it should be possible to release the > feed-comm independently of hawkular and break the 'dependency deadlock'. > > However, if we want our Travis to do all the mvn deploy fun, then this won't > work, so I am +1 on moving it to bus repo (or hawkular-commons, but to me it > logically fits more into the hawkular-bus because of the communication > nature and their release cycle will be more likely similar than the release > cycle of web socket mechanism + embedded C*) > > jk > > > ----- Original Message ----- > | From: "John Mazzitelli" <mazz(a)redhat.com&gt; > | To: "Discussions around Hawkular development" > | <hawkular-dev(a)lists.jboss.org&gt; > | Sent: Wednesday, 22 July, 2015 12:59:44 AM > | Subject: Re: [Hawkular-dev] glue code - where does it go? > | > | hawkular-commons seems like a good place for glue code that is shared > | across > | hawkular components. > | > | I could put this stuff in hawkular-bus since it is "comm" related (though > | it > | is comm between clients and server, not just comm between server-side > | components) > | > | This will need to be solved - because I can't release the agent right now. > | Agent needs the feed-comm API which is in hawkular, but hawkular needs the > | agent before it can be released. > | > | So this: > | > | https://github.com/hawkular/hawkular/tree/integration-latest-of-everythin... > | > | needs to be moved to some location other than the hawkular build. > | > | > | ----- Original Message ----- > | > Hello, > | > > | > We have this repository that is now used only for the embedded Cassandra > | > distribution. Do you think it would a good place for this kind of comm > | > code? > | > > | > > | > https://github.com/hawkular/hawkular-commons > | > > | > > | > Thank you, > | > Stefan > | > > | > ----- Original Message ----- > | > > From: "John Mazzitelli" <mazz(a)redhat.com&gt; > | > > To: "Discussions around Hawkular development" > | > > <hawkular-dev(a)lists.jboss.org&gt; > | > > Sent: Tuesday, July 21, 2015 11:42:06 AM > | > > Subject: [Hawkular-dev] glue code - where does it go? > | > > > | > > We have a fairly annoying problem with our current glue code location. > | > > > | > > Right now, we have the "glue code" that is known as "feed-comm" inside > | > > the > | > > hawkular repo - there is specifically the "feed-comm-api" artifact that > | > > contains some Java code that is required for use by Java-based feeds in > | > > order to talk to the server (also includes some JSON schemas for > | > > non-Java > | > > feeds to use). > | > > > | > > But since this is in hawkular repo, my agent needs a hawkular release > | > > in > | > > order to pull in the feed-comm-api artifact! Well, obviously, that's > | > > what > | > > we > | > > are moving toward for next week - a alpha hawkualr release. But until > | > > that > | > > happens, I can't release the agent. > | > > > | > > But, interestingly enough, because hawkular (kettle) contains the > | > > agent, > | > > hawkular can't be released until it has an agent release to pull in. > | > > > | > > Round and round we go. > | > > > | > > I really hate saying we need yet another repo, but how else can we get > | > > glue > | > > code that is common between server and feeds/agents that isn't > | > > dependent > | > > upon a hawkular release being made? > | > > _______________________________________________ > | > > hawkular-dev mailing list > | > > hawkular-dev(a)lists.jboss.org > | > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > | > > > | > > | _______________________________________________ > | hawkular-dev mailing list > | hawkular-dev(a)lists.jboss.org > | https://lists.jboss.org/mailman/listinfo/hawkular-dev > | > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev