Il 17/07/2016 21:43, Ferry Huberts ha scritto:
> Ok,
>
> But did you even try to consider that the analysis tool has bugs?
>
> My situation clearly proves this.
>
> If I may offer to explain this in the form of a requirement that is
> either missing or violated:
>
> If a requirement can be satisfied internally within a package then
> an external dependency must not be created.
>
we prefer to not bundle (using tools like jarjar, or
prefer is nice, however...
Now what happens if I build a package containing multiple bundles, Maybe
even some bundles proxying other (external bundles). Your analysis tool
will again do the wrong thing.
Please do try to understand the situation.
I can continue punching holes in your argument all day long as long as
you don't acknowledge that the analysis tool has bugs....
And I would still like to know how I can disable this analysis.
And read up on it.
maven-bundle-plugin e.g. Embed-Dependency, Private-Package we use
often
<excludeDependencies>true</excludeDependencies>)
>
> My package satisfies all dependencies internally but still external
> dependencies are created.
>
this depend if that dependencies use/import in its apis of that external
deps
> THAT is the real bug.
>
> And it is completely irrelevant that my package contains what Fedora
> considers non-free binaries.
>
>
>
> On 17/07/16 21:11, gil wrote:
>>
>>
>> Il 17/07/2016 20:10, Ferry Huberts ha scritto:
>>>
>>>
>>> On 17/07/16 20:02, gil wrote:
>>>>
>>>>
>>>> Il 17/07/2016 19:18, Ferry Huberts ha scritto:
>>>>>
>>>>>
>>>>> On 17/07/16 19:15, Ferry Huberts wrote:
>>>>>>
>>>>>>
>>>>>> On 17/07/16 17:24, gil wrote:
>>>>>>> hi
>>>>>>>
>>>>>>> i think of no because gradle use ecj (org.eclipse.jdt:core)
>>>>>>
>>>>>> What do you mean?
>>>>>>
>>>>>>
>>>>>> As I said, the package is self-contained.
>>>>>> I don't want all this analysis.
>>>>>>
>>>>>> And I don't build it for Fedora as a whole, I build it for
private
>>>>>> deployment so the non-free aspect is not relevant for me.
>>>>>
>>>> really? i not interested to talk about pre-built libraries
>>>> i think you should close
>>>>
https://bugzilla.redhat.com/show_bug.cgi?id=1348689 .
>>>> if You want use Your Gradle package is only an Your problem
>>>> If someone else as the Gradle maintainer has the time or
>>>> inclination to
>>>> "devote" to
>>>> you this is still one other question.
>>>> Your choice has nothing to do with the problems related to the package
>>>> maintained in Fedora.
>>>
>>>
>>> Wow, that is rather hostile.
>>>
>>> You are being openly hostile and I don't understand why.
>>> Is it something I said or did wrong?
>>>
>>> I came here because I was referred here from the bug report.
>>>
>>> I just want to understand what changed, why the analysis is run and
>>> how I can disable it so that my package builds again like it did
>>> before.
>>>
>>> If there is some documentation on the changes and/or specifics of the
>>> analysis, then please refer me to it, I'd be happy to read it.
>>>
>>>
>>> I maintain lots of RPMs I deploy into my network and with clients.
>>> This reaction to my questions is not helping to convince me to
>>> continue doing that.
>>>
>>> I'm baffled.
>>>
>>>
>> this is not to be hostile or less (in my case not at all) but to be
>> objective
>> I offer my apologies if you want to accept
>> like the advice I've given you so far
>> as already written not we use some apis because in Fedora are not
>> acceptable, that is NOT FREE. for which we use alternativie that are
>> available in our repository. this leads sometimes to have some
>> inconvenience (for you only)
>> regards
>> .g
>>>>
>>>>> The spec file is here:
>>>>>
https://github.com/fhuberts/rpmsUpstream/blob/master/fedora/gradle-upstre...
>>>>>
>>>>>
>>>>>
>>>>> Details are in the bug report, and I was referred here from that
>>>>> report.
>>>>>
>>>>>>
>>>>>> FYI I am an OSGi developer.
>>>>>>
>>>> i do not care who you are.
>>>> best regards
>>>> .g
>>>>>>>
>>>>>>> and in the
>>>>>>>
http://pkgs.fedoraproject.org/cgit/rpms/gradle.git/tree/gradle.spec#n170
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> is listed
>>>>>>>
>>>>>>> and in
>>>>>>>
http://pkgs.fedoraproject.org/cgit/rpms/gradle.git/tree/gradle.spec#n85
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> use eclipse "osgi" apis (beacuse the OSGi Alliaces
libraries arent
>>>>>>> non
>>>>>>> free for Fedora)
>>>>>>>
>>>>>>> regards
>>>>>>> .g
>>>>>>>
>>>>>>> Il 17/07/2016 17:07, Ferry Huberts ha scritto:
>>>>>>>> Hi list,
>>>>>>>>
>>>>>>>>
>>>>>>>> I have a custom gradle RPM that I build since fedora 23.
>>>>>>>> However, now on Fedora 24 this started pulling in a
boatload of
>>>>>>>> 'dependencies' that not actually dependencies
since the package is
>>>>>>>> self-contained.
>>>>>>>>
>>>>>>>> During the build some kind of osgi dependency analysis is
run that
>>>>>>>> results in all these (fake) dependencies.
>>>>>>>>
>>>>>>>> Can I turn this analysis off?
>>>>>>>> It seems to be new in Fedora 24 because I had no such
problems in
>>>>>>>> Fedora 23.
>>>>>>>>
>>>>>>>> Please also refer to
>>>>>>>>
https://bugzilla.redhat.com/show_bug.cgi?id=1348689 for
more
>>>>>>>> details,
>>>>>>>> including build logs.
>>>>>>>>
>>>>>>>>
>>>>>>> --
>>>>>>> java-devel mailing list
>>>>>>> java-devel(a)lists.fedoraproject.org
>>>>>>>
https://lists.fedoraproject.org/admin/lists/java-devel@lists.fedoraprojec...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> java-devel mailing list
>>>> java-devel(a)lists.fedoraproject.org
>>>>
https://lists.fedoraproject.org/admin/lists/java-devel@lists.fedoraprojec...
>>>>
>>>>
>>>>
>>>
>> --
>> java-devel mailing list
>> java-devel(a)lists.fedoraproject.org
>>
https://lists.fedoraproject.org/admin/lists/java-devel@lists.fedoraprojec...
>>
>
--
java-devel mailing list
java-devel(a)lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/java-devel@lists.fedoraprojec...