[
https://issues.apache.org/jira/browse/FELIX-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-5620.
-
Resolution: Fixed
Fixed in rev 1792427
The json serialization was return String type value
Carsten Ziegeler created FELIX-5620:
---
Summary: Bundle start/stop buttons are missing
Key: FELIX-5620
URL: https://issues.apache.org/jira/browse/FELIX-5620
Project: Felix
Issue Type: Bug
On 23/04/17 19:14, Ferry Huberts wrote:
I have this in my products (cnf/build.bnd), might be helpful.
# To include source and debug information in the Eclipse build but NOT
it's only about sources here, it's an incomplete copy/paste
if you also want this about debug then you can add
javac
I have this in my products (cnf/build.bnd), might be helpful.
# To include source and debug information in the Eclipse build but NOT in the
# gradle build, uncomment the following lines:
-sources:${if;${gestalt;batch};false;true}
Ferry
On 23/04/17 17:36, David Jencks wrote:
I mean OSGI-OPT.
The source jars for released versions are at maven central, but I was debugging
trunk, and the source jars aren’t built automatically (and, actually I thought
of adding source to the bundle and didn’t think of building the source jar).
Wrong list — but would dragging/dropping
I agree that this is a usability issue that should be fixed in the tool. It’s
just not practical to expect everybody to adopt the convention of putting
source under OSGI-OPT.
Neil
> On 23 Apr 2017, at 15:21, Thomas Watson wrote:
>
> I think including source is fine.
>
> Did you mean OSGI-OPT
I think including source is fine.
Did you mean OSGI-OPT instead of OSGI-INF. The spec recommends OSGI-OPT be
used to include source.
I am concerned that bndtools makes it hard for one such as you to debug our
code. If it is hard for you then it is impossible for the masses. This
seems like a p
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/105
---
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 enabl
[
https://issues.apache.org/jira/browse/FELIX-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980355#comment-15980355
]
Peter Kriens commented on FELIX-5618:
-
That would be great!
And about bndtools, what'
[
https://issues.apache.org/jira/browse/FELIX-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980350#comment-15980350
]
ASF GitHub Bot commented on FELIX-5613:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FELIX-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-5613.
-
Resolution: Fixed
Thanks for the patch [~nbartlett]. I've applied it in rev 1792348
> SCR
[
https://issues.apache.org/jira/browse/FELIX-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5613:
Fix Version/s: scr-2.0.10
> SCR bundle fails to start without Config Admin
> ---
[
https://issues.apache.org/jira/browse/FELIX-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned FELIX-5613:
---
Assignee: Carsten Ziegeler
> SCR bundle fails to start without Config Admin
> ---
Working on FELIX-5618 I couldn’t figure out a way to debug DS in bndtools
without modifying the DS bundle to include sources. This is certainly the
easiest way to get the sources visible in a bndtools environment. After this
experience I’d like to include the sources for DS in OSGI-INF as reco
[
https://issues.apache.org/jira/browse/FELIX-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980313#comment-15980313
]
David Jencks commented on FELIX-5618:
-
Thanks for the info. Using bndtools for this m
15 matches
Mail list logo
