Re: Building org.apache.felix.jaas fails

Hi Robert, Whats the mvn+java version you are using. I tried with latest trunk and it build fine mvn -v Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T22:59:23+05:30) Maven home: xxx/apache-maven-3.2.5 Java version: 1.7.0_55, vendor: Oracle Corporation Java home: xxx/jdk

Re: git?

There is a relatively standard Apache workflow that handles GH PR's. The committer merges the PR and pushes it, editing a comment to say 'closes #nnn" and the PR gets closed. On Sun, Oct 25, 2015 at 12:51 PM, David Jencks wrote: > While working on bnd and OSGI at github I’ve become quite attache

[GitHub] felix pull request: FELIX-5074, make compatible with bndlib 3.0

Github user asfgit closed the pull request at: https://github.com/apache/felix/pull/38 --- 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

[jira] [Resolved] (FELIX-5074) Using org.apache.felix.scr.bnd together with maven-bundle-plugin leads to using the wrong bnd version

[ https://issues.apache.org/jira/browse/FELIX-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop resolved FELIX-5074. -- Resolution: Fixed Fix Version/s: scr bnd plugin 1.5.0 Applied the patch (thanks Konrad).

[jira] [Commented] (FELIX-5074) Using org.apache.felix.scr.bnd together with maven-bundle-plugin leads to using the wrong bnd version

[ https://issues.apache.org/jira/browse/FELIX-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973469#comment-14973469 ] ASF GitHub Bot commented on FELIX-5074: --- Github user asfgit closed the pull request

Re: git?

While working on bnd and OSGI at github I’ve become quite attached to the triangular workflow model. (cf https://github.com/blog/2042-git-2-5-including-multiple-worktrees-and-triangular-workflows ) I p

Re: git?

Hi, In the 12+ years I’ve been working on apache projects I can’t recall any time when I’ve wanted to simultaneously check out different branches of modules of the same top level project. Therefore, unless anyone has actual contrary experience, I’d be in favor of trying a single git repo and r

Re: git?

I am not sure if one git repo for everything would be a good idea. The main reason is that in git (unlike in subversion) each branch and tag you do contains all the other unrelated projects too. I think it would also be quite difficult to checkout a state of the repo where you need bundle A in b