You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streams.apache.org by Jason Letourneau <jl...@gmail.com> on 2012/12/12 15:17:42 UTC
Git Mirror
The Git mirror is up at:
git://git.apache.org/streams.git or
http://git.apache.org/streams.git
This was a helpful page for me: http://wiki.apache.org/general/GitAtApache
Jason
Re: Git Mirror
Posted by Matt Franklin <m....@gmail.com>.
On Wed, Dec 12, 2012 at 10:45 AM, Ate Douma <at...@douma.nu> wrote:
> On 12/12/2012 03:52 PM, Jason Letourneau wrote:
>>
>> Good point. A follow up question is, if we aren't tracking
>> developers, do we care about releasing independently?
>
> I think we should.
>
> Consider that maybe in time two or more separate streams modules are
> created, e.g. server, client, demo, etc. which we want to maintain and
> release separately. Then a shared master pom defining common properties for
> the project will be very handy.
+1. Given that Jason has started with an ESB strategy, I think it is
likely that we will end up releasing separate components.
>
>
>>
>> Jason
>>
>> On Wed, Dec 12, 2012 at 9:46 AM, Ate Douma <at...@douma.nu> wrote:
>>>
>>> On 12/12/2012 03:38 PM, Jason Letourneau wrote:
>>>>
>>>>
>>>> I am just going to move it under the trunk of the project and remove
>>>> it from its location in the svn location...makes more logical sense to
>>>> me anyways
>>>
>>>
>>>
>>> Downside of doing that is that you no longer can release them
>>> independently.
>>> I'd advise not to do this.
>>>
>>> I don't know how the git mirror for rave was setup, but I'd expect a
>>> working
>>> solution must have been devised there. Maybe Matt knows?
>>>
>>> Ate
>>>
>>>
>>>>
>>>> On Wed, Dec 12, 2012 at 9:33 AM, Jason Letourneau
>>>> <jl...@gmail.com> wrote:
>>>>>
>>>>>
>>>>> Hmm I am noticing that they missing the streams-master-pom project in
>>>>> the mirror...so checking out and building doesn't work out of the box
>>>>>
>>>>> On Wed, Dec 12, 2012 at 9:17 AM, Jason Letourneau
>>>>> <jl...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> The Git mirror is up at:
>>>>>> git://git.apache.org/streams.git or
>>>>>> http://git.apache.org/streams.git
>>>>>>
>>>>>> This was a helpful page for me:
>>>>>> http://wiki.apache.org/general/GitAtApache
>>>>>>
>>>>>> Jason
>>>
>>>
>>>
>
Re: Git Mirror
Posted by Ate Douma <at...@douma.nu>.
On 12/12/2012 03:52 PM, Jason Letourneau wrote:
> Good point. A follow up question is, if we aren't tracking
> developers, do we care about releasing independently?
I think we should.
Consider that maybe in time two or more separate streams modules are created,
e.g. server, client, demo, etc. which we want to maintain and release
separately. Then a shared master pom defining common properties for the project
will be very handy.
>
> Jason
>
> On Wed, Dec 12, 2012 at 9:46 AM, Ate Douma <at...@douma.nu> wrote:
>> On 12/12/2012 03:38 PM, Jason Letourneau wrote:
>>>
>>> I am just going to move it under the trunk of the project and remove
>>> it from its location in the svn location...makes more logical sense to
>>> me anyways
>>
>>
>> Downside of doing that is that you no longer can release them independently.
>> I'd advise not to do this.
>>
>> I don't know how the git mirror for rave was setup, but I'd expect a working
>> solution must have been devised there. Maybe Matt knows?
>>
>> Ate
>>
>>
>>>
>>> On Wed, Dec 12, 2012 at 9:33 AM, Jason Letourneau
>>> <jl...@gmail.com> wrote:
>>>>
>>>> Hmm I am noticing that they missing the streams-master-pom project in
>>>> the mirror...so checking out and building doesn't work out of the box
>>>>
>>>> On Wed, Dec 12, 2012 at 9:17 AM, Jason Letourneau
>>>> <jl...@gmail.com> wrote:
>>>>>
>>>>> The Git mirror is up at:
>>>>> git://git.apache.org/streams.git or
>>>>> http://git.apache.org/streams.git
>>>>>
>>>>> This was a helpful page for me:
>>>>> http://wiki.apache.org/general/GitAtApache
>>>>>
>>>>> Jason
>>
>>
Re: Git Mirror
Posted by Matt Franklin <m....@gmail.com>.
On Thu, Dec 13, 2012 at 11:10 AM, Jason Letourneau
<jl...@gmail.com> wrote:
> Closing out this thread: the Nexus deployment is enabled, so Git
> mirror can be checked out and built with reference to deployed master
> POM snapshot.
It would be good to document the Git mirror on the website. We should
also define a process for handling pull requests so that it fits
within Apache guidelines.
>
> Jason
>
> On Wed, Dec 12, 2012 at 5:24 PM, Jason Letourneau
> <jl...@gmail.com> wrote:
>> I've updated the master POM to inherit from the latest Apache POM (11)
>> and added the sign-and-release maven plugin. The project POM now also
>> references the master POM from the Apache (Nexus) repo rather than a
>> relative path. The build is broken though because Nexus access has
>> not been enabled (Jira ticket is in). With regards to the
>> streams-master-pom source control...its not going to be mirrored to
>> the Git repo, but it is available in the svn repo at:
>> https://svn.apache.org/repos/asf/incubator/streams/streams-master-pom/
>> with the standard trunk, branches, tags structure.
>>
>> I'll update the list when the Nexus access is enabled and I deploy the
>> master for use.
>>
>> Jason
>>
>> On Wed, Dec 12, 2012 at 10:50 AM, Jason Letourneau
>> <jl...@gmail.com> wrote:
>>> Fantastic - I will investigate this - thanks Ate and Matt.
>>>
>>> Jason
>>>
>>> On Wed, Dec 12, 2012 at 10:45 AM, Matt Franklin
>>> <m....@gmail.com> wrote:
>>>> On Wed, Dec 12, 2012 at 10:27 AM, Jason Letourneau
>>>> <jl...@gmail.com> wrote:
>>>>> Or...this seems more likely:
>>>>> http://www.apache.org/dev/publishing-maven-artifacts.html
>>>>
>>>> You should be able to do a mvn deploy once you have configured your
>>>> maven environment for deployment (see Rave release config docs). That
>>>> will put the snapshot out there.
>>>>
>>>> However, it is important that we put a real release out there if we
>>>> expect others to build reliably. Traditionally, the mechanics of
>>>> releasing at Apache take time for people to get the hang of. IMHO,
>>>> the sooner we start, and the smaller the release, the easier it will
>>>> be.
Re: Git Mirror
Posted by Jason Letourneau <jl...@gmail.com>.
Closing out this thread: the Nexus deployment is enabled, so Git
mirror can be checked out and built with reference to deployed master
POM snapshot.
Jason
On Wed, Dec 12, 2012 at 5:24 PM, Jason Letourneau
<jl...@gmail.com> wrote:
> I've updated the master POM to inherit from the latest Apache POM (11)
> and added the sign-and-release maven plugin. The project POM now also
> references the master POM from the Apache (Nexus) repo rather than a
> relative path. The build is broken though because Nexus access has
> not been enabled (Jira ticket is in). With regards to the
> streams-master-pom source control...its not going to be mirrored to
> the Git repo, but it is available in the svn repo at:
> https://svn.apache.org/repos/asf/incubator/streams/streams-master-pom/
> with the standard trunk, branches, tags structure.
>
> I'll update the list when the Nexus access is enabled and I deploy the
> master for use.
>
> Jason
>
> On Wed, Dec 12, 2012 at 10:50 AM, Jason Letourneau
> <jl...@gmail.com> wrote:
>> Fantastic - I will investigate this - thanks Ate and Matt.
>>
>> Jason
>>
>> On Wed, Dec 12, 2012 at 10:45 AM, Matt Franklin
>> <m....@gmail.com> wrote:
>>> On Wed, Dec 12, 2012 at 10:27 AM, Jason Letourneau
>>> <jl...@gmail.com> wrote:
>>>> Or...this seems more likely:
>>>> http://www.apache.org/dev/publishing-maven-artifacts.html
>>>
>>> You should be able to do a mvn deploy once you have configured your
>>> maven environment for deployment (see Rave release config docs). That
>>> will put the snapshot out there.
>>>
>>> However, it is important that we put a real release out there if we
>>> expect others to build reliably. Traditionally, the mechanics of
>>> releasing at Apache take time for people to get the hang of. IMHO,
>>> the sooner we start, and the smaller the release, the easier it will
>>> be.
Re: Git Mirror
Posted by Jason Letourneau <jl...@gmail.com>.
I've updated the master POM to inherit from the latest Apache POM (11)
and added the sign-and-release maven plugin. The project POM now also
references the master POM from the Apache (Nexus) repo rather than a
relative path. The build is broken though because Nexus access has
not been enabled (Jira ticket is in). With regards to the
streams-master-pom source control...its not going to be mirrored to
the Git repo, but it is available in the svn repo at:
https://svn.apache.org/repos/asf/incubator/streams/streams-master-pom/
with the standard trunk, branches, tags structure.
I'll update the list when the Nexus access is enabled and I deploy the
master for use.
Jason
On Wed, Dec 12, 2012 at 10:50 AM, Jason Letourneau
<jl...@gmail.com> wrote:
> Fantastic - I will investigate this - thanks Ate and Matt.
>
> Jason
>
> On Wed, Dec 12, 2012 at 10:45 AM, Matt Franklin
> <m....@gmail.com> wrote:
>> On Wed, Dec 12, 2012 at 10:27 AM, Jason Letourneau
>> <jl...@gmail.com> wrote:
>>> Or...this seems more likely:
>>> http://www.apache.org/dev/publishing-maven-artifacts.html
>>
>> You should be able to do a mvn deploy once you have configured your
>> maven environment for deployment (see Rave release config docs). That
>> will put the snapshot out there.
>>
>> However, it is important that we put a real release out there if we
>> expect others to build reliably. Traditionally, the mechanics of
>> releasing at Apache take time for people to get the hang of. IMHO,
>> the sooner we start, and the smaller the release, the easier it will
>> be.
Re: Git Mirror
Posted by Jason Letourneau <jl...@gmail.com>.
Fantastic - I will investigate this - thanks Ate and Matt.
Jason
On Wed, Dec 12, 2012 at 10:45 AM, Matt Franklin
<m....@gmail.com> wrote:
> On Wed, Dec 12, 2012 at 10:27 AM, Jason Letourneau
> <jl...@gmail.com> wrote:
>> Or...this seems more likely:
>> http://www.apache.org/dev/publishing-maven-artifacts.html
>
> You should be able to do a mvn deploy once you have configured your
> maven environment for deployment (see Rave release config docs). That
> will put the snapshot out there.
>
> However, it is important that we put a real release out there if we
> expect others to build reliably. Traditionally, the mechanics of
> releasing at Apache take time for people to get the hang of. IMHO,
> the sooner we start, and the smaller the release, the easier it will
> be.
Re: Git Mirror
Posted by Matt Franklin <m....@gmail.com>.
On Wed, Dec 12, 2012 at 10:27 AM, Jason Letourneau
<jl...@gmail.com> wrote:
> Or...this seems more likely:
> http://www.apache.org/dev/publishing-maven-artifacts.html
You should be able to do a mvn deploy once you have configured your
maven environment for deployment (see Rave release config docs). That
will put the snapshot out there.
However, it is important that we put a real release out there if we
expect others to build reliably. Traditionally, the mechanics of
releasing at Apache take time for people to get the hang of. IMHO,
the sooner we start, and the smaller the release, the easier it will
be.
Re: Git Mirror
Posted by Jason Letourneau <jl...@gmail.com>.
Or...this seems more likely:
http://www.apache.org/dev/publishing-maven-artifacts.html
We'll need to get setup on the nexus repo first I guess
On Wed, Dec 12, 2012 at 10:23 AM, Jason Letourneau
<jl...@gmail.com> wrote:
> OK - but for the purposes of getting a build working, it looks like I
> can put the master pom on the dev repository (snapshot) here:
> https://dist.apache.org/repos/dist/dev/
>
> Is that correct?
>
> On Wed, Dec 12, 2012 at 10:17 AM, Franklin, Matthew B.
> <mf...@mitre.org> wrote:
>> -----Original Message-----
>>>From: Jason Letourneau [mailto:jletourneau80@gmail.com]
>>>Sent: Wednesday, December 12, 2012 10:15 AM
>>>To: dev@streams.incubator.apache.org
>>>Subject: Re: Git Mirror
>>>
>>>OK - how does one achieve this?
>>
>> We need to define a release process. There are plenty of examples in the Incubator and with existing PMCs. This is the one we created for Rave
>>
>> http://rave.apache.org/release-management.html
>>
>> NOTE: We will need to document the release process on the site. I am checking with INFRA as to what the holdup is on the CMS integration.
>>
>> -Matt
>>
>>>
>>>On Wed, Dec 12, 2012 at 10:09 AM, Franklin, Matthew B.
>>><mf...@mitre.org> wrote:
>>>> eep in mind, the master POM version referenced just needs to be in
>>>repository.apache.org somewhere. It could very well be in SNAPSHOT until a
>>>full release is performed.
Re: Git Mirror
Posted by Jason Letourneau <jl...@gmail.com>.
OK - but for the purposes of getting a build working, it looks like I
can put the master pom on the dev repository (snapshot) here:
https://dist.apache.org/repos/dist/dev/
Is that correct?
On Wed, Dec 12, 2012 at 10:17 AM, Franklin, Matthew B.
<mf...@mitre.org> wrote:
> -----Original Message-----
>>From: Jason Letourneau [mailto:jletourneau80@gmail.com]
>>Sent: Wednesday, December 12, 2012 10:15 AM
>>To: dev@streams.incubator.apache.org
>>Subject: Re: Git Mirror
>>
>>OK - how does one achieve this?
>
> We need to define a release process. There are plenty of examples in the Incubator and with existing PMCs. This is the one we created for Rave
>
> http://rave.apache.org/release-management.html
>
> NOTE: We will need to document the release process on the site. I am checking with INFRA as to what the holdup is on the CMS integration.
>
> -Matt
>
>>
>>On Wed, Dec 12, 2012 at 10:09 AM, Franklin, Matthew B.
>><mf...@mitre.org> wrote:
>>> eep in mind, the master POM version referenced just needs to be in
>>repository.apache.org somewhere. It could very well be in SNAPSHOT until a
>>full release is performed.
RE: Git Mirror
Posted by "Franklin, Matthew B." <mf...@mitre.org>.
-----Original Message-----
>From: Jason Letourneau [mailto:jletourneau80@gmail.com]
>Sent: Wednesday, December 12, 2012 10:15 AM
>To: dev@streams.incubator.apache.org
>Subject: Re: Git Mirror
>
>OK - how does one achieve this?
We need to define a release process. There are plenty of examples in the Incubator and with existing PMCs. This is the one we created for Rave
http://rave.apache.org/release-management.html
NOTE: We will need to document the release process on the site. I am checking with INFRA as to what the holdup is on the CMS integration.
-Matt
>
>On Wed, Dec 12, 2012 at 10:09 AM, Franklin, Matthew B.
><mf...@mitre.org> wrote:
>> eep in mind, the master POM version referenced just needs to be in
>repository.apache.org somewhere. It could very well be in SNAPSHOT until a
>full release is performed.
Re: Git Mirror
Posted by Jason Letourneau <jl...@gmail.com>.
OK - how does one achieve this?
On Wed, Dec 12, 2012 at 10:09 AM, Franklin, Matthew B.
<mf...@mitre.org> wrote:
> eep in mind, the master POM version referenced just needs to be in repository.apache.org somewhere. It could very well be in SNAPSHOT until a full release is performed.
RE: Git Mirror
Posted by "Franklin, Matthew B." <mf...@mitre.org>.
>-----Original Message-----
>From: Jason Letourneau [mailto:jletourneau80@gmail.com]
>Sent: Wednesday, December 12, 2012 9:53 AM
>To: dev@streams.incubator.apache.org
>Subject: Re: Git Mirror
>
>Good point. A follow up question is, if we aren't tracking
>developers, do we care about releasing independently?
Keep in mind, the master POM version referenced just needs to be in repository.apache.org somewhere. It could very well be in SNAPSHOT until a full release is performed.
My personal preference would be to setup the master POM the way we like and use it to develop our release process. That way we can push it out the door and not have to worry about getting it mirrored over.
>
>Jason
>
>On Wed, Dec 12, 2012 at 9:46 AM, Ate Douma <at...@douma.nu> wrote:
>> On 12/12/2012 03:38 PM, Jason Letourneau wrote:
>>>
>>> I am just going to move it under the trunk of the project and remove
>>> it from its location in the svn location...makes more logical sense to
>>> me anyways
>>
>>
>> Downside of doing that is that you no longer can release them
>independently.
>> I'd advise not to do this.
>>
>> I don't know how the git mirror for rave was setup, but I'd expect a working
>> solution must have been devised there. Maybe Matt knows?
>>
>> Ate
>>
>>
>>>
>>> On Wed, Dec 12, 2012 at 9:33 AM, Jason Letourneau
>>> <jl...@gmail.com> wrote:
>>>>
>>>> Hmm I am noticing that they missing the streams-master-pom project in
>>>> the mirror...so checking out and building doesn't work out of the box
>>>>
>>>> On Wed, Dec 12, 2012 at 9:17 AM, Jason Letourneau
>>>> <jl...@gmail.com> wrote:
>>>>>
>>>>> The Git mirror is up at:
>>>>> git://git.apache.org/streams.git or
>>>>> http://git.apache.org/streams.git
>>>>>
>>>>> This was a helpful page for me:
>>>>> http://wiki.apache.org/general/GitAtApache
>>>>>
>>>>> Jason
>>
>>
Re: Git Mirror
Posted by Jason Letourneau <jl...@gmail.com>.
Good point. A follow up question is, if we aren't tracking
developers, do we care about releasing independently?
Jason
On Wed, Dec 12, 2012 at 9:46 AM, Ate Douma <at...@douma.nu> wrote:
> On 12/12/2012 03:38 PM, Jason Letourneau wrote:
>>
>> I am just going to move it under the trunk of the project and remove
>> it from its location in the svn location...makes more logical sense to
>> me anyways
>
>
> Downside of doing that is that you no longer can release them independently.
> I'd advise not to do this.
>
> I don't know how the git mirror for rave was setup, but I'd expect a working
> solution must have been devised there. Maybe Matt knows?
>
> Ate
>
>
>>
>> On Wed, Dec 12, 2012 at 9:33 AM, Jason Letourneau
>> <jl...@gmail.com> wrote:
>>>
>>> Hmm I am noticing that they missing the streams-master-pom project in
>>> the mirror...so checking out and building doesn't work out of the box
>>>
>>> On Wed, Dec 12, 2012 at 9:17 AM, Jason Letourneau
>>> <jl...@gmail.com> wrote:
>>>>
>>>> The Git mirror is up at:
>>>> git://git.apache.org/streams.git or
>>>> http://git.apache.org/streams.git
>>>>
>>>> This was a helpful page for me:
>>>> http://wiki.apache.org/general/GitAtApache
>>>>
>>>> Jason
>
>
Re: Git Mirror
Posted by Ate Douma <at...@douma.nu>.
On 12/12/2012 03:38 PM, Jason Letourneau wrote:
> I am just going to move it under the trunk of the project and remove
> it from its location in the svn location...makes more logical sense to
> me anyways
Downside of doing that is that you no longer can release them independently.
I'd advise not to do this.
I don't know how the git mirror for rave was setup, but I'd expect a working
solution must have been devised there. Maybe Matt knows?
Ate
>
> On Wed, Dec 12, 2012 at 9:33 AM, Jason Letourneau
> <jl...@gmail.com> wrote:
>> Hmm I am noticing that they missing the streams-master-pom project in
>> the mirror...so checking out and building doesn't work out of the box
>>
>> On Wed, Dec 12, 2012 at 9:17 AM, Jason Letourneau
>> <jl...@gmail.com> wrote:
>>> The Git mirror is up at:
>>> git://git.apache.org/streams.git or
>>> http://git.apache.org/streams.git
>>>
>>> This was a helpful page for me: http://wiki.apache.org/general/GitAtApache
>>>
>>> Jason
Re: Git Mirror
Posted by Jason Letourneau <jl...@gmail.com>.
I am just going to move it under the trunk of the project and remove
it from its location in the svn location...makes more logical sense to
me anyways
On Wed, Dec 12, 2012 at 9:33 AM, Jason Letourneau
<jl...@gmail.com> wrote:
> Hmm I am noticing that they missing the streams-master-pom project in
> the mirror...so checking out and building doesn't work out of the box
>
> On Wed, Dec 12, 2012 at 9:17 AM, Jason Letourneau
> <jl...@gmail.com> wrote:
>> The Git mirror is up at:
>> git://git.apache.org/streams.git or
>> http://git.apache.org/streams.git
>>
>> This was a helpful page for me: http://wiki.apache.org/general/GitAtApache
>>
>> Jason
Re: Git Mirror
Posted by Jason Letourneau <jl...@gmail.com>.
Hmm I am noticing that they missing the streams-master-pom project in
the mirror...so checking out and building doesn't work out of the box
On Wed, Dec 12, 2012 at 9:17 AM, Jason Letourneau
<jl...@gmail.com> wrote:
> The Git mirror is up at:
> git://git.apache.org/streams.git or
> http://git.apache.org/streams.git
>
> This was a helpful page for me: http://wiki.apache.org/general/GitAtApache
>
> Jason