Maven Repository for Shindig 1.1

[Martin Svensson <ma...@ericsson.com>]

Hello,

I am quite new to shindig development. Me and my interns are working on
a Open Social bridge to IMS type informartion. So far everything has
worked without any problems, the only thing I havent find is a maven
(shapshot) repository for the Shindig 1.1. components. I was thinking of
setting up such repository internally at our site but wanted to check if
you already deploy those components to an externally accessible
repository.

Regards,
Martin Svensson
Ericsson Research 

Ps
If anyone is interested in what we are going with this work let me know

Re: Maven Repository for Shindig 1.1

[Vincent Siveton <vi...@gmail.com>]

Hi Tim,

2009/6/19 Tim Moore <tm...@atlassian.com>:
> I don't trust humans :-) If people are finding problems with the builds that
> aren't caught by automated tests, it would be nice if they at least file
> bugs to improve the test suite (if not actually make the improvements

IMHO problems will be not in the build or automatic tests but mainly
in the code functionality and the stability of the generated
artifacts.
A typical developer day is to work, to commit, to improve, to
recommit, to reimprove etc.
If Hudson starts and deploys automatic snapshots on r.a.o between
these commits, the build will be fine but the artifacts could be not
usable.

In Maven land, we decided that it is the responsibility of the devs to
deploy snapshots to r.a.o only when the judge the artifacts are
stable.

> It may also be worthwhile to consider more frequent tagged releases... call
> them betas, or milestones... the point is that it will give people a more
> stable version to depend on than a snapshot, and a more current version than
> 1.0-incubating. I'm not sure what Apache rules are, but I would hope that as
> long as the release isn't announced or packaged up for download then it
> shouldn't require a vote to release a monthly or biweekly milestone.

Since Shindig is in the incubator, it could be hard to have a
consensus each month (see the effort to release 1.0...)

We are using Hudson to have snapshots but we could certainly deploy
them to r.a.o, maybe based on a regular timeline.

Cheers,

Vincent

Re: Maven Repository for Shindig 1.1

[Ian Boston <ie...@tfd.co.uk>]

On 20 Jun 2009, at 01:12, Tim Moore wrote:

> I'm not sure what Apache rules are, but I would hope that as long as  
> the release isn't announced or packaged up for download then it  
> shouldn't require a vote to release a monthly or biweekly milestone.
>
> -- Tim


IIRC anything other than snapshot deploys requires a full vote  
process, first on shindig-dev and then on 3 +1 votes form the  
Incubator PMC members. Those are the rules of the incubator.

That can be quick, but in our instance for some unknown reason its  
taken several months to achieve. So doing anything other than snapshot  
releases is a full time job at the moment. It should not stay that way.

Its also several hours work to prepare a release.
Ian

Re: Maven Repository for Shindig 1.1

[chico charlesworth <ch...@googlemail.com>]

+1

changed our pom to get the shindig dependencies from m2-snapshot-repository,
ran our integration tests, which depend on shindig-common and
shindig-social-api, and all is well .. maybe someone else could check that
shindig-gadgets and shindig-features are also working as expected?

Cheers,
Chico

2009/6/20 Paul Lindner <li...@inuus.com>

> Okay,
> I just did my first mvn deploy of 1.1-SNAPSHOT
>
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/shindig/
>
> Could someone with more maven experience tell me if I performed this
> properly?
>
> Thanks
>
>
> On Fri, Jun 19, 2009 at 5:12 PM, Tim Moore <tm...@atlassian.com> wrote:
>
> > On Jun 19, 2009, at 2:49 PM, Ian Boston wrote:
> >
> >
> >> On 19 Jun 2009, at 21:09, Vincent Siveton wrote:
> >>
> >>  2009/6/19 Paul Lindner <li...@inuus.com>:
> >>>
> >>>> Okay, sounds good then.
> >>>> For the truly bleeding edge should we have hudson publish timestamped
> >>>> snapshots somewhere?
> >>>>
> >>>
> >>> Personally, I am not in favour to automate the snapshot deployment:
> >>> human action ensures that the code does what it is supposed to do.
> >>>
> >>> Cheers,
> >>>
> >>> Vincent
> >>>
> >>
> >>
> >> We do already have snapshots going out from hudson, but I agree, if they
> >> are broken in a subtle way and go out to the repo its a pain for
> everyone
> >> depending on them.
> >>
> >
> > I don't trust humans :-) If people are finding problems with the builds
> > that aren't caught by automated tests, it would be nice if they at least
> > file bugs to improve the test suite (if not actually make the
> improvements
> > themselves). A list of holes in the tests would actually be a nice way to
> > encourage more contributions from the community. Maybe this is already
> > happening, but I only see a handful of issues in JIRA related to
> improving
> > test coverage, and they're mostly pretty broad (although SHINDIG-1031
> looks
> > like a good starting point).
> >
> > It may also be worthwhile to consider more frequent tagged releases...
> call
> > them betas, or milestones... the point is that it will give people a more
> > stable version to depend on than a snapshot, and a more current version
> than
> > 1.0-incubating. I'm not sure what Apache rules are, but I would hope that
> as
> > long as the release isn't announced or packaged up for download then it
> > shouldn't require a vote to release a monthly or biweekly milestone.
> >
> > -- Tim
> >
>

Re: Maven Repository for Shindig 1.1

[Ian Boston <ie...@tfd.co.uk>]

lgtm,
obviously doesn't include the release tarballs etc, but then I don't  
think that you would want it to.
Ian

On 20 Jun 2009, at 01:50, Paul Lindner wrote:

> Okay,
> I just did my first mvn deploy of 1.1-SNAPSHOT
>
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/shindig/
>
> Could someone with more maven experience tell me if I performed this
> properly?
>
> Thanks
>
>
> On Fri, Jun 19, 2009 at 5:12 PM, Tim Moore <tm...@atlassian.com>  
> wrote:
>
>> On Jun 19, 2009, at 2:49 PM, Ian Boston wrote:
>>
>>
>>> On 19 Jun 2009, at 21:09, Vincent Siveton wrote:
>>>
>>> 2009/6/19 Paul Lindner <li...@inuus.com>:
>>>>
>>>>> Okay, sounds good then.
>>>>> For the truly bleeding edge should we have hudson publish  
>>>>> timestamped
>>>>> snapshots somewhere?
>>>>>
>>>>
>>>> Personally, I am not in favour to automate the snapshot deployment:
>>>> human action ensures that the code does what it is supposed to do.
>>>>
>>>> Cheers,
>>>>
>>>> Vincent
>>>>
>>>
>>>
>>> We do already have snapshots going out from hudson, but I agree,  
>>> if they
>>> are broken in a subtle way and go out to the repo its a pain for  
>>> everyone
>>> depending on them.
>>>
>>
>> I don't trust humans :-) If people are finding problems with the  
>> builds
>> that aren't caught by automated tests, it would be nice if they at  
>> least
>> file bugs to improve the test suite (if not actually make the  
>> improvements
>> themselves). A list of holes in the tests would actually be a nice  
>> way to
>> encourage more contributions from the community. Maybe this is  
>> already
>> happening, but I only see a handful of issues in JIRA related to  
>> improving
>> test coverage, and they're mostly pretty broad (although  
>> SHINDIG-1031 looks
>> like a good starting point).
>>
>> It may also be worthwhile to consider more frequent tagged  
>> releases... call
>> them betas, or milestones... the point is that it will give people  
>> a more
>> stable version to depend on than a snapshot, and a more current  
>> version than
>> 1.0-incubating. I'm not sure what Apache rules are, but I would  
>> hope that as
>> long as the release isn't announced or packaged up for download  
>> then it
>> shouldn't require a vote to release a monthly or biweekly milestone.
>>
>> -- Tim
>>

Re: Maven Repository for Shindig 1.1

[Vincent Siveton <vi...@gmail.com>]

Hi Paul,


2009/6/19 Paul Lindner <li...@inuus.com>:
> Okay,
> I just did my first mvn deploy of 1.1-SNAPSHOT
>
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/shindig/
>
> Could someone with more maven experience tell me if I performed this
> properly?
>

We need to use r.a.o instead of this old repo. I will create a separated thread.

Thanks,

Vincent

Re: Maven Repository for Shindig 1.1

[Paul Lindner <li...@inuus.com>]

Okay,
I just did my first mvn deploy of 1.1-SNAPSHOT

http://people.apache.org/repo/m2-snapshot-repository/org/apache/shindig/

Could someone with more maven experience tell me if I performed this
properly?

Thanks


On Fri, Jun 19, 2009 at 5:12 PM, Tim Moore <tm...@atlassian.com> wrote:

> On Jun 19, 2009, at 2:49 PM, Ian Boston wrote:
>
>
>> On 19 Jun 2009, at 21:09, Vincent Siveton wrote:
>>
>>  2009/6/19 Paul Lindner <li...@inuus.com>:
>>>
>>>> Okay, sounds good then.
>>>> For the truly bleeding edge should we have hudson publish timestamped
>>>> snapshots somewhere?
>>>>
>>>
>>> Personally, I am not in favour to automate the snapshot deployment:
>>> human action ensures that the code does what it is supposed to do.
>>>
>>> Cheers,
>>>
>>> Vincent
>>>
>>
>>
>> We do already have snapshots going out from hudson, but I agree, if they
>> are broken in a subtle way and go out to the repo its a pain for everyone
>> depending on them.
>>
>
> I don't trust humans :-) If people are finding problems with the builds
> that aren't caught by automated tests, it would be nice if they at least
> file bugs to improve the test suite (if not actually make the improvements
> themselves). A list of holes in the tests would actually be a nice way to
> encourage more contributions from the community. Maybe this is already
> happening, but I only see a handful of issues in JIRA related to improving
> test coverage, and they're mostly pretty broad (although SHINDIG-1031 looks
> like a good starting point).
>
> It may also be worthwhile to consider more frequent tagged releases... call
> them betas, or milestones... the point is that it will give people a more
> stable version to depend on than a snapshot, and a more current version than
> 1.0-incubating. I'm not sure what Apache rules are, but I would hope that as
> long as the release isn't announced or packaged up for download then it
> shouldn't require a vote to release a monthly or biweekly milestone.
>
> -- Tim
>

Re: Maven Repository for Shindig 1.1

[Tim Moore <tm...@atlassian.com>]

On Jun 19, 2009, at 2:49 PM, Ian Boston wrote:

>
> On 19 Jun 2009, at 21:09, Vincent Siveton wrote:
>
>> 2009/6/19 Paul Lindner <li...@inuus.com>:
>>> Okay, sounds good then.
>>> For the truly bleeding edge should we have hudson publish  
>>> timestamped
>>> snapshots somewhere?
>>
>> Personally, I am not in favour to automate the snapshot deployment:
>> human action ensures that the code does what it is supposed to do.
>>
>> Cheers,
>>
>> Vincent
>
>
> We do already have snapshots going out from hudson, but I agree, if  
> they are broken in a subtle way and go out to the repo its a pain  
> for everyone depending on them.

I don't trust humans :-) If people are finding problems with the  
builds that aren't caught by automated tests, it would be nice if they  
at least file bugs to improve the test suite (if not actually make the  
improvements themselves). A list of holes in the tests would actually  
be a nice way to encourage more contributions from the community.  
Maybe this is already happening, but I only see a handful of issues in  
JIRA related to improving test coverage, and they're mostly pretty  
broad (although SHINDIG-1031 looks like a good starting point).

It may also be worthwhile to consider more frequent tagged releases...  
call them betas, or milestones... the point is that it will give  
people a more stable version to depend on than a snapshot, and a more  
current version than 1.0-incubating. I'm not sure what Apache rules  
are, but I would hope that as long as the release isn't announced or  
packaged up for download then it shouldn't require a vote to release a  
monthly or biweekly milestone.

-- Tim

Re: Maven Repository for Shindig 1.1

[Ian Boston <ie...@tfd.co.uk>]

On 19 Jun 2009, at 21:09, Vincent Siveton wrote:

> 2009/6/19 Paul Lindner <li...@inuus.com>:
>> Okay, sounds good then.
>> For the truly bleeding edge should we have hudson publish timestamped
>> snapshots somewhere?
>
> Personally, I am not in favour to automate the snapshot deployment:
> human action ensures that the code does what it is supposed to do.
>
> Cheers,
>
> Vincent


We do already have snapshots going out from hudson, but I agree, if  
they are broken in a subtle way and go out to the repo its a pain for  
everyone depending on them.
Ian

Re: Maven Repository for Shindig 1.1

[Vincent Siveton <vi...@gmail.com>]

2009/6/19 Paul Lindner <li...@inuus.com>:
> Okay, sounds good then.
> For the truly bleeding edge should we have hudson publish timestamped
> snapshots somewhere?

Personally, I am not in favour to automate the snapshot deployment:
human action ensures that the code does what it is supposed to do.

Cheers,

Vincent

Re: Maven Repository for Shindig 1.1

[Paul Lindner <li...@inuus.com>]

Okay, sounds good then.
For the truly bleeding edge should we have hudson publish timestamped
snapshots somewhere?


On Fri, Jun 19, 2009 at 12:21 PM, Vincent Siveton <vincent.siveton@gmail.com
> wrote:

> Hi Paul,
>
> No don't use p.a.o
>
> You should use [1] with mvn deploy. All artifacts will be in snapshots
> repo.
>
> Cheers,
>
> Vincent
>
> [1] https://repository.apache.org/
>
> 2009/6/19 Paul Lindner <li...@inuus.com>:
> > Currently there is no maven repo for 1.1.
> >
> > As part of getting the 1.1 snapshots available I plan to publish to a
> maven
> > repo on people.apache.org.  Should get to this early next week.
> > Thanks,
> > Paul
> >
> >
> >
> > On Fri, Jun 19, 2009 at 10:06 AM, Martin Svensson <
> > martin.a.svensson@ericsson.com> wrote:
> >
> >> Hello,
> >>
> >> I am quite new to shindig development. Me and my interns are working on
> >> a Open Social bridge to IMS type informartion. So far everything has
> >> worked without any problems, the only thing I havent find is a maven
> >> (shapshot) repository for the Shindig 1.1. components. I was thinking of
> >> setting up such repository internally at our site but wanted to check if
> >> you already deploy those components to an externally accessible
> >> repository.
> >>
> >> Regards,
> >> Martin Svensson
> >> Ericsson Research
> >>
> >> Ps
> >> If anyone is interested in what we are going with this work let me know
> >>
> >
>

Re: Maven Repository for Shindig 1.1

[Vincent Siveton <vi...@gmail.com>]

Hi Paul,

No don't use p.a.o

You should use [1] with mvn deploy. All artifacts will be in snapshots repo.

Cheers,

Vincent

[1] https://repository.apache.org/

2009/6/19 Paul Lindner <li...@inuus.com>:
> Currently there is no maven repo for 1.1.
>
> As part of getting the 1.1 snapshots available I plan to publish to a maven
> repo on people.apache.org.  Should get to this early next week.
> Thanks,
> Paul
>
>
>
> On Fri, Jun 19, 2009 at 10:06 AM, Martin Svensson <
> martin.a.svensson@ericsson.com> wrote:
>
>> Hello,
>>
>> I am quite new to shindig development. Me and my interns are working on
>> a Open Social bridge to IMS type informartion. So far everything has
>> worked without any problems, the only thing I havent find is a maven
>> (shapshot) repository for the Shindig 1.1. components. I was thinking of
>> setting up such repository internally at our site but wanted to check if
>> you already deploy those components to an externally accessible
>> repository.
>>
>> Regards,
>> Martin Svensson
>> Ericsson Research
>>
>> Ps
>> If anyone is interested in what we are going with this work let me know
>>
>

RE: Maven Repository for Shindig 1.1

[Martin Svensson <ma...@ericsson.com>]

Great. Then I will wait for that one instead!

Thanks,
Martin
 

-----Original Message-----
From: Paul Lindner [mailto:lindner@inuus.com] 
Sent: Friday, June 19, 2009 10:40 AM
To: shindig-dev@incubator.apache.org
Subject: Re: Maven Repository for Shindig 1.1

Currently there is no maven repo for 1.1.

As part of getting the 1.1 snapshots available I plan to publish to a
maven repo on people.apache.org.  Should get to this early next week.
Thanks,
Paul



On Fri, Jun 19, 2009 at 10:06 AM, Martin Svensson <
martin.a.svensson@ericsson.com> wrote:

> Hello,
>
> I am quite new to shindig development. Me and my interns are working 
> on a Open Social bridge to IMS type informartion. So far everything 
> has worked without any problems, the only thing I havent find is a 
> maven
> (shapshot) repository for the Shindig 1.1. components. I was thinking 
> of setting up such repository internally at our site but wanted to 
> check if you already deploy those components to an externally 
> accessible repository.
>
> Regards,
> Martin Svensson
> Ericsson Research
>
> Ps
> If anyone is interested in what we are going with this work let me 
> know
>

Re: Maven Repository for Shindig 1.1

[Paul Lindner <li...@inuus.com>]

Currently there is no maven repo for 1.1.

As part of getting the 1.1 snapshots available I plan to publish to a maven
repo on people.apache.org.  Should get to this early next week.
Thanks,
Paul



On Fri, Jun 19, 2009 at 10:06 AM, Martin Svensson <
martin.a.svensson@ericsson.com> wrote:

> Hello,
>
> I am quite new to shindig development. Me and my interns are working on
> a Open Social bridge to IMS type informartion. So far everything has
> worked without any problems, the only thing I havent find is a maven
> (shapshot) repository for the Shindig 1.1. components. I was thinking of
> setting up such repository internally at our site but wanted to check if
> you already deploy those components to an externally accessible
> repository.
>
> Regards,
> Martin Svensson
> Ericsson Research
>
> Ps
> If anyone is interested in what we are going with this work let me know
>