Re: [tycho-user] Why is Tycho manifest-first?

["Dahanne, Anthony" <Anthony.Dahanne@xxxxxxxxxxxxx>]

Igor,
This crazy idea sounds so cool ;-)
That would be awesome !
It reminds of a war project (built with Maven) depending on OSGi bundles (built with Tycho) only published to p2 repositories...

Is there a way for this war project to consume those already built OSGi bundles ?

(for now I only use Tycho to build equinox plugins and features...)

Regards,
Anthony




 
Le contenu de ce courriel s'adresse au destinataire seulement. Il contient de l'information pouvant être confidentielle. Vous ne devez ni le copier ni l'utiliser ni le divulguer à qui que ce soit à moins que vous soyez le destinataire ou une personne désignée autorisée. Si vous le receviez par erreur, veuillez nous aviser immédiatement et le détruire.
 
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
 

De : tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] De la part de Igor Fedorenko
Envoyé : 16 novembre 2011 16:10
À : tycho-user@xxxxxxxxxxx
Objet : Re: [tycho-user] Why is Tycho manifest-first?

FWIW, latest m2e-tycho lets you work on pom-first projects using Eclipse
PDE without additional overhead either, so I would not use this to
choose between pom-first and manifest first.

The real difference comes from dependencies. If most of project
dependencies come from p2 repositories, then manifest-first makes
dependency resolution easier, if not the only viable option. If,
however, all project dependencies are available from Maven repositories,
then pom-first works much better.

Developer background and personal preferences also play a role here.
Personally, I find it easier to have bundle manifest generated for me,
but I know other developers prefer maintaing manifests by hand. One
of the crazier ideas I recently had was to rework Eclipse Platform build
using pom-first approach, so that entire eclipse platform becomes
natively available from a Maven repository. I gave up on this idea
mostly because I did not see how to convince platform developers let a
tool generate bundle manifests for them.

--
Regards,
Igor

On 11-11-16 2:57 PM, Max Rydahl Andersen wrote:
> ...manifest-first makes it much easier to migrate to from PDE-build and still be able to work with Eclipse PDE without additional overhead.
>
> /max
>
> On Nov 14, 2011, at 22:14, Aaron Digulla wrote:
>
>> Hello,
>>
>> I'm wondering why you're using p2 technology (with all it's drawbacks) instead of using Maven's fast&reliable dependency resolution to create a MANIFEST.MF from that?
>>
>> Wouldn't it be much more simple to add a manifest builder plugin which I can configure from a POM that produces a MANIFEST.MF?
>>
>> Regards,
>>
>> --
>> Aaron "Optimizer" Digulla a.k.a. Philmann Dark
>> "It's not the universe that's limited, it's our imagination.
>> Follow me and I'll show you something beyond the limits."
>> http://blog.pdark.de/
>> _______________________________________________
>> tycho-user mailing list
>> tycho-user@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>
> /max
> http://about.me/maxandersen
>
>
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user