On Sat, Oct 24, 2015 at 4:21 PM, David Jencks wrote:
> I like having several felix subprojects open in one eclipse instance at once,
> which the current svn structure facilitates. Having just one git svn rebase
> to run is nice. Is there a way to stitch together several smaller git repos
> t
If I am understanding you correctlyl you can create your own git project
and add the other git repos as submodules in your project. Then do
git submodule foreach git pull origin master
I personally hate git submodules though.
David Daniel
On 2015-10-24 16:21, David Jencks wrote:
> I like
I like having several felix subprojects open in one eclipse instance at once,
which the current svn structure facilitates. Having just one git svn rebase to
run is nice. Is there a way to stitch together several smaller git repos that
would work similarly? Not knowing how to do this, I am st
At Felix, I'd like to add publication of a maven-generated site to the
existing CMS content, following the trail of what's done at Maven.
I see that the main site for Felix is at
https://svn.apache.org/repos/infra/websites/production/felix/content,
that's
http://felix.apache.org
I created
https
Greeting, Marcel,
It's not my intention to try to talk anyone into changing how they
release anything. For the things that are built with Maven, it's my
preference to avoid exercising the maven-release-plugin's feature of
handling multiple released items in a repo, but it's just a
preference. If t
On 24 October 2015 at 11:36:03, Benson Margulies
(ben...@basistech.com(mailto:ben...@basistech.com)) wrote:
> > So I would definitely argue against getting a Git repository per bundle.
> > Per subproject sounds like the right granularity to me.
>
> If a subproject is released all at once, t
On Sat, Oct 24, 2015 at 2:27 PM, Richard Hall wrote:
> On Oct 24, 2015 2:21 PM, "Marcel Offermans"
> wrote:
>>
>> Within Felix we have “subprojects” that consist of one or more bundles
> and I would argue that they are always released together. This does not
> mean that for every release, every b
[
https://issues.apache.org/jira/browse/FELIX-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved FELIX-5070.
-
Resolution: Fixed
Fix Version/s: maven-bundle-plugin-3.0.2
r1710372 adds a unit tes
On Oct 24, 2015 2:21 PM, "Marcel Offermans"
wrote:
>
> Within Felix we have “subprojects” that consist of one or more bundles
and I would argue that they are always released together. This does not
mean that for every release, every bundle needs to change, sometimes only a
subset of the released b
Within Felix we have “subprojects” that consist of one or more bundles and I
would argue that they are always released together. This does not mean that for
every release, every bundle needs to change, sometimes only a subset of the
released bundles change.
So I would definitely argue against g
Here's the basic issue. The maven-release-plugin doesn't always work
with git when the pom you are releasing is not the top of the
repository. I put a great deal of work into fixing it, and yet others
continue to report problems. (It works for my favorite test case.)
So, the conservative strategy
Still no luck. I even logged out and into jira.
On Sat, Oct 24, 2015 at 10:21 AM, Carsten Ziegeler wrote:
> Am 24.10.15 um 14:14 schrieb Benson Margulies:
>> I can close them, but I can't assign them to myself.
>>
> Should work now
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege.
YAY!!
as you can tell, I’m in favor of it.
I think that 1 repo per project may be too small. For instance I think it
makes sense to have one repo for the 3 gogo projects, even though they are
released separately. I think soon there will be at least 4 scr projects and
I’d like them to be in 1
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/37
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/19
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/29
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/5
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/14
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/8
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/28
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Am 24.10.15 um 14:14 schrieb Benson Margulies:
> I can close them, but I can't assign them to myself.
>
Should work now
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
I can close them, but I can't assign them to myself.
[
https://issues.apache.org/jira/browse/FELIX-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved FELIX-5073.
-
Resolution: Fixed
Fix Version/s: maven-bundle-plugin-3.0.2
r1710332 | bimargulies |
[
https://issues.apache.org/jira/browse/FELIX-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972555#comment-14972555
]
ASF GitHub Bot commented on FELIX-4970:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FELIX-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved FELIX-4970.
-
Resolution: Fixed
Fix Version/s: gogo.runtime-0.16.4
Fixed in r1710336.
> all feli
[
https://issues.apache.org/jira/browse/FELIX-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972546#comment-14972546
]
ASF GitHub Bot commented on FELIX-4930:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FELIX-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972547#comment-14972547
]
ASF GitHub Bot commented on FELIX-4962:
---
Github user asfgit closed the pull request
Folks might find some use for
https://wiki.apache.org/lucene-java/BensonMargulies/GitSvnWorkflow.
I just made a dummy commit to close out a pile of older PR's
corresponding to resolve jiras.
[
https://issues.apache.org/jira/browse/FELIX-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972548#comment-14972548
]
ASF GitHub Bot commented on FELIX-4529:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FELIX-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972543#comment-14972543
]
ASF GitHub Bot commented on FELIX-4963:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FELIX-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972542#comment-14972542
]
ASF GitHub Bot commented on FELIX-2702:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FELIX-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972545#comment-14972545
]
ASF GitHub Bot commented on FELIX-2930:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FELIX-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972541#comment-14972541
]
ASF GitHub Bot commented on FELIX-4969:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FELIX-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972544#comment-14972544
]
ASF GitHub Bot commented on FELIX-4764:
---
Github user asfgit closed the pull request
35 matches
Mail list logo
