Adding GeoSolutions maven repo for snaphots

[Simone Giannecchini]

Dear All,
I am going to add GeoSolutions maven repo for snapshots as it might be
useful for deploying temporary snapshots and interim milestone
releases for the project.
If there are objections let me know.

Regards,
Simone Giannecchini
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.
==

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

[Michael Bedward]

On 10 January 2013 22:39, Simone Giannecchini

<simone.gi...@geo-solutions.it> wrote:
> Dear All,
> I am going to add GeoSolutions maven repo for snapshots as it might be
> useful for deploying temporary snapshots and interim milestone
> releases for the project.
> If there are objections let me know.
>

Objection :)

I'm not keen on two separate snapshot repos for jaitools - it seems
like a recipe for user confusion. Is there a reason why the Sonatype
snapshot repo is not sufficient ?

Michael

[Simone Giannecchini]

Ciao Michael,
please, find my answers inline below...

Regards,
Simone Giannecchini
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.
==

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Generally speaking we tend to always put in the mix maven repos on
which we have some degree of control, osgeo, our own, opengeo.
This way we have more repos that can be used and where we deploy,
therefore it is more difficult that users might not be able to pull
artifacts.

That said, in this specific case I needed a quick way to push the
snapnhots therefore I used our own. I am perfectly fine with NOT using
our own repo
as long as the instructions to push snapshots are share between the committers.




>
> Michael
>
> --
> You received this message because you are subscribed to the Google Groups "jai-tools" group.
> To post to this group, send email to jai-...@googlegroups.com.
> To unsubscribe from this group, send email to jai-tools+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/jai-tools?hl=en.
>

[Michael Bedward]

Hi Simone,

Andrea has credentials for the jaitools repo at Sonatype so can deploy
snapshots and releases there - this is why I don't understand the need
for another repo ? It seems much easier to stick with one and avoid
version chaos.

Just my 2c

Michael

On 12 January 2013 00:51, Simone Giannecchini

[Andrea Aime]

On Sat, Jan 12, 2013 at 12:10 AM, Michael Bedward <michael...@gmail.com> wrote:

Hi Simone,

Andrea has credentials for the jaitools repo at Sonatype so can deploy
snapshots and releases there - this is why I don't understand the need
for another repo ?  It seems much easier to stick with one and avoid
version chaos.

Ah, while we work togheter we are not in the same office, so it's important

that we can operate independently.

He did not ask me, but if he had, I would have said "no, I don't have the

credentials", cause I forgot I had them... actually don't remember anything

about deploying on Sonatype, last time I did was probably over than

one year go...

Cheers

Andrea

 

--

==

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

==

Ing. Andrea Aime 

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054  Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39  339 8844549

[andrea antonello]

Hi all,
I am also all for the non duplication of the repos. But I have not
really anything against moving it to the geosolutions repo, if that
helps quicken the release cycle.

[...]

> Ah, while we work togheter we are not in the same office, so it's important
> that we can operate independently.
> He did not ask me, but if he had, I would have said "no, I don't have the
> credentials", cause I forgot I had them... actually don't remember anything
> about deploying on Sonatype, last time I did was probably over than
> one year go...

The snapshot releasing of sonatype is really straight forward, so that
should not be a problem, if the credentials are there. I am using it
also for the jgrasstools project, so I could take over that one, but I
think that it would make few sense, given the fact that you guys need
to be able to release a SNAP whenever you need to.

Cheers,
Andrea

[Simone Giannecchini]

Ciao Michael,
I believe Andrea described already the situation. I am happy with
using only sonatype as long as we can all deploy to it.
Of course this does not mean that we should not coordinate when
pushing artifacts, especially for releases, but in some situations,
like the one we just experienced, being able to deploy a snapshot is
crucial.

That said, once we have agree on a common way to deploy artifacts I
believe I will take action to set up a Jenkins instance to deply
nightly builds or something.
At least I believe it would be a good exercise.

Regards,
Simone Giannecchini
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.
==

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

On Thu, Jan 10, 2013 at 11:35 PM, Michael Bedward
<michael...@gmail.com> wrote:

[Michael Bedward]

On 12 January 2013 21:06, Simone Giannecchini

<simone.gi...@geo-solutions.it> wrote:
>
> That said, once we have agree on a common way to deploy artifacts I
> believe I will take action to set up a Jenkins instance to deply
> nightly builds or something.
> At least I believe it would be a good exercise.
>

There is presently a jaitools job on the same hudson server as
geotools / geoserver. I imagine that could deploy to Sonatype, though
Justin would need to confirm and approve that.

Michael

[Simone Giannecchini]

Ciao Michael,
I would like to have something I can control myself rather than having
to go through someone
I don't have control upon.

What do you suggest?

Regards,
Simone Giannecchini
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.
==

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

[Michael Bedward]

If that Hudson server is fine for building and deploying GeoTools and
GeoServer why is it a problem to have jaitools hosted there also ?

Sorry, but I don't understand why control has become an issue now when
it hasn't before. Is it a problem to do with me rather than technical
issues ? If so, let me know :)

Michael

On 14 January 2013 23:52, Simone Giannecchini

[Simone Giannecchini]

Ciao Michael,
please, read below....

Regards,
Simone Giannecchini
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.
==

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

On Tue, Jan 15, 2013 at 1:16 AM, Michael Bedward
<michael...@gmail.com> wrote:
> If that Hudson server is fine for building and deploying GeoTools and
> GeoServer why is it a problem to have jaitools hosted there also ?
>
> Sorry, but I don't understand why control has become an issue now when
> it hasn't before. Is it a problem to do with me rather than technical
> issues ? If so, let me know :)
>

It does not depend on you, of course :)

But we have already found ourselves a few times in the position to
need a critical but simple fix in the short time
and we had to either put in place relatively complex workaround or
hacks to be able to include deployed jars in our
apps.

So, if I do a critical fix I would need to be able to:

-1- commit the fix sooner rather than later (otherwise, this comes
from experience, the fixes might get lost in a dead branch)
-2- push new snaphots if the tests are ok (unless there is automatic
deployof snapshots)

Notice that I am talking about bug fixes not new features or deep refactors.

[Michael Bedward]

Hi Simone,

> So, if I do a critical fix I would need to be able to:
>
> -1- commit the fix sooner rather than later (otherwise, this comes
> from experience, the fixes might get lost in a dead branch)
> -2- push new snaphots if the tests are ok (unless there is automatic
> deployof snapshots)
>
> Notice that I am talking about bug fixes not new features or deep refactors.
>

I think this can be handled quite easily and reliably with the
existing Sonatype snapshot repo.

Manual deployment of snapshots is easy and can be done from any source
repo - all that is required is to be a member of the Sonatype jaitools
account. Andrea is a member and you could also be added if that's
useful. I can send you a description of how I do the snapshots
currently (just a couple of maven invocations from the command line).

Alternatively, we could also ask Justin if it would be OK to add a
jaitools deployment job to Hudson. It could have daily polling of the
repo plus you could kick it manually if required.

The reasons that I favour sticking with the single Sonatype repo are
that it makes admin easier and provides a single destination for both
snapshots and staging to Maven Central. The service has been very
reliable since I've been using it for jaitools and JTS and their
support is quick and helpful.

Michael

[Simone Giannecchini]

Ciao Michael,
please, read below...

Regards,
Simone Giannecchini
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.
==

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

On Wed, Jan 16, 2013 at 1:26 PM, Michael Bedward
<michael...@gmail.com> wrote:
> Hi Simone,
>
>> So, if I do a critical fix I would need to be able to:
>>
>> -1- commit the fix sooner rather than later (otherwise, this comes
>> from experience, the fixes might get lost in a dead branch)
>> -2- push new snaphots if the tests are ok (unless there is automatic
>> deployof snapshots)
>>
>> Notice that I am talking about bug fixes not new features or deep refactors.
>>
>
> I think this can be handled quite easily and reliably with the
> existing Sonatype snapshot repo.
>
> Manual deployment of snapshots is easy and can be done from any source
> repo - all that is required is to be a member of the Sonatype jaitools
> account. Andrea is a member and you could also be added if that's
> useful. I can send you a description of how I do the snapshots
> currently (just a couple of maven invocations from the command line).
>

That would probably do it.

> Alternatively, we could also ask Justin if it would be OK to add a
> jaitools deployment job to Hudson. It could have daily polling of the
> repo plus you could kick it manually if required.
>

I would do this anyway. It is something good to have in place I
believe if it does not add any complexity to the management
activities.

> The reasons that I favour sticking with the single Sonatype repo are
> that it makes admin easier and provides a single destination for both
> snapshots and staging to Maven Central. The service has been very
> reliable since I've been using it for jaitools and JTS and their
> support is quick and helpful.

No worries, the approach you suggest sounds reasonable for me.
-a- ability to do manual push for us as well
-b- possibility to have nightly builds using the opengeo CI