Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Missing requirement : Batik

Hi Benoit,


The target platform is based on the following p2 for Papyrus:  http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/neon/

Which contains org.eclipse.papyrus.sdk.feature.feature.group

This feature should mention it's orbit dependancy and the related p2 in its pom or TP. Right ? And thus I should not have this kind of issue.

Or should I explicitely add this repo into the Papyrus RT target Platform even if the software that requires the Batik is into Papyrus and not in Papyrus RT.

Regards


Céline


Le 04/07/2016 à 17:48, MAGGI Benoit a écrit :

Hi Céline,

 

I don’t think it has something to do with Missing CQ.

 

Which orbit update site are you using for your build?

I believe Papyrus is consuming this one [1] that contains your missing library.

 

Regards,

Benoit

1       : http://download.eclipse.org/tools/orbit/downloads/drops/R20160520211859/repository

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Céline JANSSENS
Envoyé : lundi 4 juillet 2016 17:31
À : mdt-papyrus.dev@xxxxxxxxxxx
Objet : Re: [mdt-papyrus.dev] Missing CQs for some dependencies

 

Hi Rémi,

It seems we still have issue about batik.dom dependencies:

When I try to build the target platform based on Papyrus Nightly , I have the following error: 

[ERROR] Cannot resolve target definition:
[ERROR]   Software being installed: org.eclipse.papyrus.sdk.feature.feature.group 2.0.0.201607040959
[ERROR]   Missing requirement: org.eclipse.papyrus.infra.gmfdiag.common 2.0.0.201607040959 requires 'bundle org.apache.batik.dom.svg [1.7.0,1.8.0)' but it could not be found
[ERROR]   Cannot satisfy dependency: org.eclipse.papyrus.infra.gmfdiag.feature.feature.group 2.0.0.201607040959 depends on: org.eclipse.papyrus.infra.gmfdiag.common [2.0.0.201607040959]
[ERROR]   Cannot satisfy dependency: org.eclipse.papyrus.sdk.feature.feature.group 2.0.0.201607040959 depends on: org.eclipse.papyrus.infra.gmfdiag.feature.feature.group [2.0.0.201607040959]
[ERROR] 


Regards

Le 25/05/2016 à 12:10, SCHNEKENBURGER Remi 211865 a écrit :

After some investigation, it comes from the diagram definition editor extra plugin. It embeds directly the jar in the git repository, which is a bad practice.

Plugins should depend only from orbit plugins when they depend on a specific external library.

 

So for the contributors of the diagram: could you please remove the jar from the plugin in the git repo, and update the classpath of the plugin to depend on batik from orbit?

 

Regards,

Rémi

 

-------------------------------------------------------

 

Rémi SCHNEKENBURGER

+33 (0)1 69 08 48 48

CEA Saclay Nano-INNOV

Institut CARNOT CEA LIST

 

Description : PapyrusLogo_SmallFormatwww.eclipse.org/papyrus

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de SCHNEKENBURGER Remi 211865
Envoyé : mercredi 25 mai 2016 11:49
À : Papyrus Project list (mdt-papyrus.dev@xxxxxxxxxxx) <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] [mdt-papyrus.dev] Missing CQs for some dependencies

 

Hi All,

 

We are currently working on the IPlog for the release review 2.0.0 of the Papyrus project. When generating the IPlog, it seems that new dependencies to third party plugins have been added to the plugins without explicitly running a CQ for those libraries.

Here are the issues we currently have [1]:

 
 
It looks like some unapproved versions of some libraries have leaked into the
project downloads since the last IP Log check (it looks like they may have
appeared in some of you service releases).
 
org.apache.batik.dom.source_1.6.1.*.jar (No CQ found)
org.apache.batik.dom_1.6.1.*.jar (No CQ found)
org.apache.commons.io_2.2.0.*.jar (No CQ found)
org.apache.commons.lang3_3.1.0.*.jar (No CQ found)
xalan-2.6.0.*.jar (No CQ found)
xerces_2_5_0.jar (No CQ found)
 

Do you know when/where these dependencies were introduced, and what they are used for? Shall we remove them from the dependencies or create a new CQ for these ones?

 

Regards,

Rémi

 

[1] https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11480

 

-------------------------------------------------------

 

Rémi SCHNEKENBURGER

+33 (0)1 69 08 48 48

CEA Saclay Nano-INNOV

Institut CARNOT CEA LIST

 

Description : PapyrusLogo_SmallFormatwww.eclipse.org/papyrus

 




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

 

--

 

 

 

Céline JANSSENS
Software Engineer
+33 (0)2 44 47 23 23

 

Mail : cej@xxxxxxxxxxx


6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net

 

Garanti sans virus. www.avast.com

 



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

--

 
  Céline JANSSENS
Software Engineer
+33 (0)2 44 47 23 23
  Mail : cej@xxxxxxxxxxx

6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net

Garanti sans virus. www.avast.com

Back to the top