You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Pei, Jeff" <yp...@ebay.com> on 2016/11/03 01:42:03 UTC
snapshot version changes frequently
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
Re: snapshot version changes frequently
Posted by Hao Chen <cn...@gmail.com>.
Yeah, I think the dependency repo should be stable and immutable after v0.5.0 released.
> On Nov 3, 2016, at 10:11 PM, Liangfei.Su <su...@gmail.com> wrote:
>
> This suggestion not to urgency. Good to hear +1 for that J
>
>
>
> I think we could stay the eagle-alert-parent still in eagle-parent, so that we make sure every-time build covers all the code in repo. Down stream should reflect the changes on upstream, it's ok. The problem is we don't have stable release version for down stream right now. Looking forward to graduation process and release planning.
>
>
>
> Ralph
>
>
>
>
>> On Thu, Nov 3, 2016 at 7:29 PM, Hao Chen <cn...@gmail.com> wrote:
>> 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 <li...@ebay.com> 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 <ha...@apache.org>
>> > Date: Thursday, November 3, 2016 at 12:55 PM
>> > To: "dev@eagle.incubator.apache.org" <de...@eagle.incubator.apache.org>
>> > Cc: "Su, Liangfei" <li...@ebay.com>
>> > 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 <yp...@ebay.com> 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
>> >
>> >
>> >
>
Re: snapshot version changes frequently
Posted by "Liangfei.Su" <su...@gmail.com>.
This suggestion not to urgency. Good to hear +1 for that J
I think we could stay the eagle-alert-parent still in eagle-parent, so that
we make sure every-time build covers all the code in repo. Down
stream should reflect the changes on upstream, it's ok. The problem is we
don't have stable release version for down stream right now. Looking
forward to graduation process and release planning.
Ralph
On Thu, Nov 3, 2016 at 7:29 PM, Hao Chen <cn...@gmail.com> wrote:
> 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 <li...@ebay.com> 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 <ha...@apache.org>
> > Date: Thursday, November 3, 2016 at 12:55 PM
> > To: "dev@eagle.incubator.apache.org" <de...@eagle.incubator.apache.org>
> > Cc: "Su, Liangfei" <li...@ebay.com>
> > 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 <yp...@ebay.com> 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
> >
> >
> >
>
Re: snapshot version changes frequently
Posted by Hao Chen <cn...@gmail.com>.
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 <li...@ebay.com> 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 <ha...@apache.org>
> Date: Thursday, November 3, 2016 at 12:55 PM
> To: "dev@eagle.incubator.apache.org" <de...@eagle.incubator.apache.org>
> Cc: "Su, Liangfei" <li...@ebay.com>
> 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 <yp...@ebay.com> 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
>
>
>
Re: snapshot version changes frequently
Posted by "Su, Liangfei" <li...@ebay.com>.
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 <ha...@apache.org>
Date: Thursday, November 3, 2016 at 12:55 PM
To: "dev@eagle.incubator.apache.org" <de...@eagle.incubator.apache.org>
Cc: "Su, Liangfei" <li...@ebay.com>
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 <yp...@ebay.com>> 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
Re: snapshot version changes frequently
Posted by Hao Chen <ha...@apache.org>.
Hi Jeff,
May I know what's the error/exception?
- Hao
On Thu, Nov 3, 2016 at 9:42 AM, Pei, Jeff <yp...@ebay.com> 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
>
>
>