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

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?

On Thu, Sep 6, 2012 at 3:56 PM, Igor Fedorenko <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

PW


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

Back to the top