> On Dec 1, 2015, at 19:14, Benson Margulies wrote:
>
> On Dec 1, 2015 6:43 PM, "Richard S. Hall" wrote:
>>
>>
>>> On Dec 1, 2015, at 17:50, Benson Margulies
> wrote:
>>>
>>>
>
> On Dec 1, 2015, at 17:50, Benson Margulies wrote:
>
> https://cwiki.apache.org/confluence/display/~bimargul...@gmail.com/Felix+and+Git
>
> ?
Seems like a good start, although is that editable by others?
It seems like other technical issues were raised about the
On Dec 1, 2015 6:43 PM, "Richard S. Hall" wrote:
>
>
> > On Dec 1, 2015, at 17:50, Benson Margulies
wrote:
> >
> >
https://cwiki.apache.org/confluence/display/~bimargul...@gmail.com/Felix+and+Git
> >
> > ?
>
> Seems like a good start, although is that
https://cwiki.apache.org/confluence/display/~bimargul...@gmail.com/Felix+and+Git
?
On Tue, Dec 1, 2015 at 1:56 PM, Richard S. Hall wrote:
> On 12/1/15 13:40 , Carsten Ziegeler wrote:
>>
>> Richard S. Hall wrote
>>>
>>> Well, the argument to the contrary is perhaps that is
On Tue, Dec 1, 2015 at 7:50 PM, David Jencks wrote:
> I also see no way to edit your page, and I have no idea who might be a
> confluence space administrator who could change permissions.
>
> I was going to add to the pro-single-git-repo the point that you can check
>
I also see no way to edit your page, and I have no idea who might be a
confluence space administrator who could change permissions.
I was going to add to the pro-single-git-repo the point that you can check out
exactly the parts you want using git sparse-checkout.
I don’t think the decision to
I believe that everyone in the felix-users confluence group now has
access to edit pages in my 'personal space'.
On Tue, Dec 1, 2015 at 9:49 PM, Benson Margulies wrote:
> On Tue, Dec 1, 2015 at 7:50 PM, David Jencks wrote:
>> I also see no way to
We at Pentaho made the migration to Git and GitHub from Subversion and
Perforce a few years ago now. At the time we decided to go with multiple
repositories (we're at around 100 right now). In retrospect this was a
large mistake.
Development often spans multiple repositories creating dependent
Hello Benson,
There is, at least, substantial apathy about git on the part of the
sub-communities that work on some of the sub-projects. In my view,
this apathy, including perhaps a bit of antipathy, sunk the discussion
of just converting as one big repo. As I see it, Felix is a bit of a
On Tue, Dec 1, 2015 at 11:43 AM, Marcel Offermans
wrote:
> Hello Benson,
>
> There is, at least, substantial apathy about git on the part of the
> sub-communities that work on some of the sub-projects. In my view,
> this apathy, including perhaps a bit of antipathy,
Marcel Offermans wrote
>
> Let me speak for myself here, I don’t see compelling arguments for moving to
> Git. What problem are we solving here? Why is moving to Git the right
> solution?
> That’s where my lack of enthusiasm comes from. Nobody has yet explained that
> to me. And splitting
On 12/1/15 12:57 , Carsten Ziegeler wrote:
Marcel Offermans wrote
Let me speak for myself here, I don’t see compelling arguments for moving to
Git. What problem are we solving here? Why is moving to Git the right solution?
That’s where my lack of enthusiasm comes from. Nobody has yet
On 12/1/15 13:40 , Carsten Ziegeler wrote:
Richard S. Hall wrote
Well, the argument to the contrary is perhaps that is makes it more
difficult for us as a community to have oversight into releases. It
almost assures us that some/many community members will never checkout
subprojects that aren't
Alexandre Roman created FELIX-5125:
--
Summary: NPE in ConfigInstaller
Key: FELIX-5125
URL: https://issues.apache.org/jira/browse/FELIX-5125
Project: Felix
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FELIX-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved FELIX-5124.
-
Resolution: Invalid
In the mean time I did some more tests and found other plug-ins and scenarios
I will write a VOTE thread with a description.
On Tue, Dec 1, 2015 at 10:12 AM, Carsten Ziegeler wrote:
> Benson Margulies wrote
>> I would like to peel the bundle plugin. Does any pmc member sympathize
>> sufficiently to start a vote to test consensus to do that?
>
> I
Benson Margulies wrote
> I would like to peel the bundle plugin. Does any pmc member sympathize
> sufficiently to start a vote to test consensus to do that?
I don't want to be a PITA, but would you care about writing a more
detailed description of what that would mean? (git repo name, how it is
Here's how I'd call the vote:
This is a vote to move the reference source of the maven-bundle-plugin to git.
To be specific,
- http://git.apache.org/ will list the repository as
'felix-maven-bundle-plugin.git' (because all repo names start with
their project name).
- all existing history will
[
https://issues.apache.org/jira/browse/FELIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033905#comment-15033905
]
David Bosschaert commented on FELIX-5112:
-
An updated pull request has been provided here:
I apologize for losing track of this whole discussion. I don’t recall seeing a
convincing to me reason to have, at least initially, more than one git repo.
Wasn’t there even a new git feature that let you check out only part of a
project?
However many repos we decide on, I’m in favor of git
It sure seems as if there are no PMC members fond enough of the git
idea to call a vote. I'm treating this as a dead topic for now.
+1
regards
/Pierre
On Tue, Dec 1, 2015 at 7:29 AM, Carsten Ziegeler
wrote:
> +1
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>
+1 (non-binding)
On Tue, Dec 1, 2015 at 2:59 AM, Carsten Ziegeler wrote:
> +1
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
U ok.. let me see if I can belatedly recapture the brilliance..
I think it was simply the observation that if the end result was to have
many repos, couldn't each subproject just start pealing itself off into a
git repo as it sees fit?
Call it lazy migration if you will.
The side effects
I would like to peel the bundle plugin. Does any pmc member sympathize
sufficiently to start a vote to test consensus to do that?
On Dec 1, 2015 9:38 AM, "Raymond Auge" wrote:
> U ok.. let me see if I can belatedly recapture the brilliance..
>
> I think it was
Benson Margulies wrote
> It sure seems as if there are no PMC members fond enough of the git
> idea to call a vote. I'm treating this as a dead topic for now.
>
Looks like :(
I had a brief discussion two weeks ago with Ray, and he had an
interesting idea. @Ray do you want to bring it up?
David Jencks wrote
> I apologize for losing track of this whole discussion. I don’t recall seeing
> a convincing to me reason to have, at least initially, more than one git
> repo. Wasn’t there even a new git feature that let you check out only part
> of a project?
>
> However many repos we
David,
There is, at least, substantial apathy about git on the part of the
sub-communities that work on some of the sub-projects. In my view,
this apathy, including perhaps a bit of antipathy, sunk the discussion
of just converting as one big repo. As I see it, Felix is a bit of a
loose
Benson Margulies wrote
> Here's how I'd call the vote:
>
> This is a vote to move the reference source of the maven-bundle-plugin to git.
>
> To be specific,
>
> - http://git.apache.org/ will list the repository as
> 'felix-maven-bundle-plugin.git' (because all repo names start with
> their
On Tue, Dec 1, 2015 at 11:16 AM, Carsten Ziegeler wrote:
> Benson Margulies wrote
>> Here's how I'd call the vote:
>>
>> This is a vote to move the reference source of the maven-bundle-plugin to
>> git.
>>
>> To be specific,
>>
>> - http://git.apache.org/ will list the
[
https://issues.apache.org/jira/browse/FELIX-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop resolved FELIX-4816.
--
Resolution: Fixed
Fix Version/s: org.apache.felix.dependencymanager-r1
forgot to close
31 matches
Mail list logo