David Jencks created FELIX-4538:
---
Summary: [DS] problem with stale references with "triangle" of
static references
Key: FELIX-4538
URL: https://issues.apache.org/jira/browse/FELIX-4538
Project: Felix
FWIW the latest framework bundle didn't have a src jar with it. It would be
nice if that src.jar could be available again. Previous versions did have
this. Usually the IDE is capable of attaching this to the binary. For
example the me plugin for eclipse.
Regards, Achim
sent from mobile device
Am
I'm pretty strongly -1 on the default binary artifact including the sources.
So far felix follows maven conventions more or less and this is definitely
against maven conventions.
On the other hand I'm cautiously +0.5 on building an additional artifact that
is the binary jar + sources.
I reall
+1 FWIW.
I agree that having the source within the bundles might be a nice-to-have.
AFAICT we already deploy the sources to maven and as such can download them as
dependencies.
I would be ok if we would have a build profile which would create a developer's
artifact which embeds the sources wit
On 18 Jun 2014, at 16:01, Karl Pauls wrote:
> On Wed, Jun 18, 2014 at 4:37 PM, Paul Bakker wrote:
>
>> Karl, are you *against* the idea, or just not very fond of it? In other
>> words: can we apply this change to the poms or not?
>
> Changing our parent pom so that all sub projects will be bui
Hi,
I'm agree with Karl. A 'lot' of space for a bit comfort.
There are environments with very limited space for the bundle store.
-1 for the idea
Kind Regards
Uwe
On June 18, 2014 4:37:38 PM Paul Bakker wrote:
Karl, are you *against* the idea, or just not very fond of it? In other
words: c
On Wed, Jun 18, 2014 at 4:37 PM, Paul Bakker wrote:
> Karl, are you *against* the idea, or just not very fond of it? In other
words: can we apply this change to the poms or not?
>
Changing our parent pom so that all sub projects will be build like this
without the option to change it? Yes, I'm
On 18/06/14 16:34, Karl Pauls wrote:
On Wed, Jun 18, 2014 at 4:11 PM, Jan Willem Janssen <
janwillem.jans...@luminis.eu> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/06/14 16:08, Karl Pauls wrote:
FWIW, I'm not a super big fan of shipping the source in the
binaries as that mak
Karl, are you *against* the idea, or just not very fond of it? In other
words: can we apply this change to the poms or not?
Cheers,
Paul
On Wed, Jun 18, 2014 at 10:11 AM, Jan Willem Janssen <
janwillem.jans...@luminis.eu> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 18/06/14
On Wed, Jun 18, 2014 at 4:11 PM, Jan Willem Janssen <
janwillem.jans...@luminis.eu> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 18/06/14 16:08, Karl Pauls wrote:
> > FWIW, I'm not a super big fan of shipping the source in the
> > binaries as that makes them extra bloated - we s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/06/14 16:08, Karl Pauls wrote:
> FWIW, I'm not a super big fan of shipping the source in the
> binaries as that makes them extra bloated - we should
> deploy/release the source.jars via maven and bnd should learn how
> to download them from the m
Oh, I was assuming you where talking about generating maven source jars on
release. So that will not work (I'd still be happy if somebody gets that
one done in the parent pom).
FWIW, I'm not a super big fan of shipping the source in the binaries as
that makes them extra bloated - we should deploy/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
+1 for this idea!
On 18/06/14 15:39, Ferry Huberts wrote:
>
> On 18/06/14 15:27, Karl Pauls wrote:
>> Attaching the source jars makes a lot of sense - somebody wants
>> to take a go at our parent pom?
>>
>
> IIRC you can't do it in the parent
On 18/06/14 15:27, Karl Pauls wrote:
Attaching the source jars makes a lot of sense - somebody wants to take a
go at our parent pom?
IIRC you can't do it in the parent pom.
You need to add
<_source>true
to the bundle plugin configurations
regards,
Karl
On Wed, Jun 18, 2014 at 3:18 PM,
I had a quick look at it, but it looks like the bundle-plugin is configured
per project, not in the parent pom?
Cheers,
Paul
On Wed, Jun 18, 2014 at 9:27 AM, Karl Pauls wrote:
> Attaching the source jars makes a lot of sense - somebody wants to take a
> go at our parent pom?
>
> regards,
>
>
Attaching the source jars makes a lot of sense - somebody wants to take a
go at our parent pom?
regards,
Karl
On Wed, Jun 18, 2014 at 3:18 PM, Paul Bakker wrote:
> +1
>
> I believe Maven source jars are already generated, but it would be great to
> also generate the sources in the binaries li
+1
I believe Maven source jars are already generated, but it would be great to
also generate the sources in the binaries like Bndtools expects.
Cheers,
Paul
On Wed, Jun 18, 2014 at 9:11 AM, Ferry Huberts wrote:
>
>
> On 18/06/14 14:48, Raymond Auge wrote:
>
>> +1
>>
>> I find if incredibly t
On 18/06/14 14:48, Raymond Auge wrote:
+1
I find if incredibly tiring to have to fetch the source bundles for libs
all the time.
Meanwhile, some libs like bnd for instance, contain the sources and that
makes them a joy to work with.
the reason I sent this mail is that I have an insane jett
+1
I find if incredibly tiring to have to fetch the source bundles for libs
all the time.
Meanwhile, some libs like bnd for instance, contain the sources and that
makes them a joy to work with.
However, I could see a counter argument for the size of the archive being
adversely affected by the in
[
https://issues.apache.org/jira/browse/FELIX-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert updated FELIX-2340:
Fix Version/s: (was: gogo.command-0.14.0)
gogo.command-0.16.0
> Comb
Hi,
I'd like to request that the sources be added to released bundles.
This makes debugging so much easier, especially when using bndtools.
The bnd instruction to accomplish this (also applicable to the bundle
plugin) is:
-sources: true
--
Ferry Huberts
21 matches
Mail list logo
