RE : RE : Scripting felix

[DEBROUX Lionel <Li...@atos.net>]

Hi again,

> Thanks for the example given, you are right, we are using Maven. I am
> currently adding base depencies by using copy-dependencies as you
> describe. But I am not using some of the additional maven niceties
> you are demonstrating, so thanks for the pointers.
You're welcome.

> What I like about the gogo-deployment method is that dependency
> resolution for obr:deploy happens on the basis of manifest.mf, so
> for our project bundles I can test this functionality directly as part
> of the integration build.
OK.

> I realize I could deploy the felix output of the maven method during
> the build in order to test manifest issues, but I must admit I am a
> little worried about runtime dependency issues and/or adding too much
> to our felix build with maven as dependency resolver... I note you
> are setting excludeTransitive to true in copy-dependencies of the
> example below :)
I guess that having excludeTransitive to true, in the POM I extracted
and simplified for posting here, was just a way to force explicit
specification of dependencies in the POM, so that no new dependency
can slip in without anybody noticing.

> -> Is there no way to have gogo persist its deployments, as it does
> when I deploy bundles interactively?
>
> -> Would you advise against using this approach for other reasons?
I don't know, let's wait for answers from other persons :)


Regards,
Lionel.
________________________________


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.