Return-Path: X-Original-To: apmail-felix-dev-archive@www.apache.org Delivered-To: apmail-felix-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A262411F12 for ; Wed, 18 Jun 2014 18:26:23 +0000 (UTC) Received: (qmail 59474 invoked by uid 500); 18 Jun 2014 18:26:23 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 59403 invoked by uid 500); 18 Jun 2014 18:26:23 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 59391 invoked by uid 99); 18 Jun 2014 18:26:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 18:26:23 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bcanhome@googlemail.com designates 209.85.216.169 as permitted sender) Received: from [209.85.216.169] (HELO mail-qc0-f169.google.com) (209.85.216.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 18:26:20 +0000 Received: by mail-qc0-f169.google.com with SMTP id c9so1179381qcz.0 for ; Wed, 18 Jun 2014 11:25:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=DiQJUNpiDrhq2yR6SYOuvHqhlTc68XBhSSvlswJyKok=; b=K92kvq8cwlRK0GUDIW5lcpU+q3TuDWGcfDO8npN5Jauf4NIVMRzddgelLHt4bEXsQA O/vGvT7vJT1P/IacjPGLcDYo76rY1qOQbJw84Q5WQwJkQaf3nyv7Xj/6SA5GCWLHX45n znzEh6tLkFWrKJiBjCLhOFqeHfEhJb37rwJduyzbSTXMzHuAlxidJBqpbJXr0XADQEAi 9/TTNziu1R+4EuKOdzqu7Sg5ot7qekCpZ6nTW7pKk6H087M8XrdtO8O9tOy+UD9uDIXK aDPgnWxOqXF81r56+noL21Qlc0ZWekQwnEJsGFU6WrSmDYOgOnjbiOOvmRgj+4YVtoaE SH4A== MIME-Version: 1.0 X-Received: by 10.224.51.72 with SMTP id c8mr5920801qag.82.1403115956165; Wed, 18 Jun 2014 11:25:56 -0700 (PDT) Received: by 10.96.189.42 with HTTP; Wed, 18 Jun 2014 11:25:56 -0700 (PDT) Received: by 10.96.189.42 with HTTP; Wed, 18 Jun 2014 11:25:56 -0700 (PDT) In-Reply-To: References: <53A13C72.1030306@hupie.com> <53A1900F.2000803@hupie.com> <53A19697.5010807@hupie.com> <901B8149-D7D0-4B1C-8998-99DE821AF99B@adobe.com> Date: Wed, 18 Jun 2014 20:25:56 +0200 Message-ID: Subject: Re: RFE: add sources to bundles From: Achim Nierbeck To: dev@felix.apache.org Content-Type: multipart/alternative; boundary=089e0160bb6c2563ea04fc20641f X-Virus-Checked: Checked by ClamAV on apache.org --089e0160bb6c2563ea04fc20641f Content-Type: text/plain; charset=UTF-8 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 18.06.2014 18:04 schrieb "David Jencks" : > 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 really would think that rather than fighting maven it might be more > advisable to teach bndtools about maven standards so that it can find the > sources jar automatically given a binary jar. This would fix the problem > for any bundle built with maven, not just felix bundles. > > thanks > david jencks > > On Jun 18, 2014, at 8:33 AM, Felix Meschberger wrote: > > > +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 with the binary code. But the > default IMHO should remain to be binary only. > > > > Regards > > Felix > > > > Am 18.06.2014 um 16:08 schrieb Karl Pauls : > > > >> 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/release the source.jars > >> via maven and bnd should learn how to download them from the maven repo > or > >> at least provide a way to attach them manually without forcing the > source > >> to be contained in the jar (if it can't do that already). > >> > >> regards, > >> > >> Karl > >> > >> > >> On Wed, Jun 18, 2014 at 3:39 PM, 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 pom. > >>> You need to add > >>> <_source>true > >>> to the bundle plugin configurations > >>> > >>> > >>> 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 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 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 jetty crash > that I > >>>>>> wanted to track down. Because no sources were included and I use > many > >>>>>> > >>>>> felix > >>>>> > >>>>>> bundles with widely differing versions it became a nightmare and I > just > >>>>>> gave up. > >>>>>> > >>>>>> > >>>>>> > >>>>>> However, I could see a counter argument for the size of the archive > >>>>>>> > >>>>>> being > >>>>> > >>>>>> adversely affected by the inclusion of sources, particularly for > those > >>>>>>> small profile installations (particularly embedded). > >>>>>>> > >>>>>>> > >>>>>>> I'm sure an acceptable solution can be found. > >>>>>> > >>>>>> > >>>>>> > >>>>>> On Wed, Jun 18, 2014 at 3:14 AM, Ferry Huberts > >>>>>>> wrote: > >>>>>>> > >>>>>>> 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 > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>> Ferry Huberts > >>>>>> > >>>>>> > >>>>> > >>>> > >>>> > >>>> > >>> -- > >>> Ferry Huberts > >>> > >> > >> > >> > >> -- > >> Karl Pauls > >> karlpauls@gmail.com > >> http://twitter.com/karlpauls > >> http://www.linkedin.com/in/karlpauls > >> https://profiles.google.com/karlpauls > > > > --089e0160bb6c2563ea04fc20641f--