Maybe we could do it later after graduation as we would create new repository then and it maybe also not very good to split eagle-alert as separate module at this stage, since cause complex for community contribution and development.
How do you think currently exclude eagle-alert-parent from eagle-parent building, so that we could deploy eagle-alert independently, and it won't impact alert engine snapshot while general deployment. Hao > On Nov 3, 2016, at 7:03 PM, Su, Liangfei <[email protected]> wrote: > > Due to “SecurityException: Invalid signature file digest for Manifest main > attributes” when deploy alert topology to storm. Related to recent change of > alert-common depend to eagle-common. Would try exclude in downstream way. > > In general, I would suggest to community to consider the option of separate > alert engine as a sub project. Eagle v0.5.0 is designed to be able to run > alert engine as standalone app. > > For all who’s working on/care the eagle source code structure, please let me > know your comment. > > Thanks > Ralph > > From: Hao Chen <[email protected]> > Date: Thursday, November 3, 2016 at 12:55 PM > To: "[email protected]" <[email protected]> > Cc: "Su, Liangfei" <[email protected]> > Subject: Re: snapshot version changes frequently > > Hi Jeff, > > May I know what's the error/exception? > > - Hao > > On Thu, Nov 3, 2016 at 9:42 AM, Pei, Jeff <[email protected]> wrote: > Hi Eagle team, > > We depends on your 0.5.0-incubating-SNAPSHOT version for a project. However > due to its snapshot version, it constantly changing versions and broke our > dependency system today. (probably since you did a release in the past 24 > hours) > > Could you please publish some none snapshot version so that we can easily > roll back and depends on something that does not change? > > Thanks, > > Jeff > > >
