Re: [orbit-dev] Multiple bundle recipes for httpclient-* vs. a single on

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

For this thread's info:  ECF filetransfer depends upon httpclient+httpcomponents as available through Orbit recipes.   It's hopefully obvious...but care needs to be taken to maintain backward compatibility of httpclient+httpcomponents as we likely won't have time respond for Eclipse Oxygen milestones.

If what's being done won't change the exports or dependencies (e.g.commons codec version) ...then it should be fine.

Scott


On 1/24/2017 7:10 AM, Andreas Sewe wrote:

Gunnar Wagenknecht wrote:

Any advice how to write an osgi.bnd file such that it takes
everything except Bundle-Vendor and a few other descriptive headers
from the MANIFEST.MF already included in httpclient-osgi? I've
consulted the options of ebr-maven-plugin:help but couldn't find
anything that would help me in this regard; AFAICT, the
ebr-maven-plugin always want to create a MANIFEST.MF from scratch.
Is this correct?

No, it uses the Maven bnd plug-in under the covers. It re-uses as
much headers as possible.

Good to know.

However, this can be problematic. Therefore the Orbit paren is setup
to remove a few headers by default. Checkout the Orbit parent to see
which properties you can override/customize: 
http://git.eclipse.org/c/orbit/orbit-recipes.git/tree/releng/mavenparent/pom.xml

Thank you for the pointers. Very helpful.

Best wishes,

Andreas

_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/orbit-dev