Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Fwd: [Bug 387557] JarProcessor 'tampers' eclipse.inf of signed jars in some cases 


On 12-09-06 7:08 PM, Paul Webster wrote:

Hi Igor,

Can we just add something to the pom.xml to exclude that file from being
processed/copied/whatever?  Or do we actually have to delete it?



This is what I am trying to understand.

If eclipse.inf is not used for anything essential, then we just ignore
it, maybe adding some check for unknown parameters to be really safe.

There are couple of bundles that have pack and/or signed disabled with
eclipse.inf, so we may need to honour this.

I do not see any other relevant usecase for eclipse.inf, but I want
Platform developers to confirm.



On Thu, Sep 6, 2012 at 3:56 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:

    To make sure I am not missing an important usecase here. Why is use of
    eclipse.inf required for jdt.core?

    For example, Tycho never packs or signs nested jars, so
    jarprocessor.exclude.children=__true is redundant.

    jarprocessor.exclude.pack=true and jarprocessor.exclude.sign=true can be
    easily achieved via pom.xml configuration. And I need to
    double-check if they are actually needed for the projects they are
    used in.


Does p2 use any of the instructions in the eclipse.inf?

I see mostly the excludes, but here's another example:
rt.equinox.incubator/p2/publishing/org.eclipse.equinox.p2.tests/testData/directorywatcher2/org.junit_3.8.2.v200706111738

pack200.args = -E4
pack200.conditioned = true



This is test data, as far as I can tell, most likely unzipped version of
a prebuilt bundle. I do not believe it is built either by PDE/Build nor
Tycho.


--
Regards,
Igor





PW


--
Paul Webster
Hi floor.  Make me a sammich! - GIR


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev

Back to the top