Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Question about product materialization

You are right, I have a dependency on org.eclipse.xtext.ui but it has an optional dependency on org.eclipse.jdt.core.
I spent a whole day tuning my build so that the product exported with the product export mojo was ok.
Since I changed to eclipse-repository, I am facing this issue.

Regards
Jeff


On Fri, Feb 17, 2012 at 6:16 PM, Oberlies, Tobias <tobias.oberlies@xxxxxxx> wrote:
The error message even gives you the path to the JDT bundle. You seem to be including the org.eclipse.xtext.ui feature in your own feature, and that feature includes things that require JDT.

Regards
Tobias


> -----Original Message-----
> From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-
> bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
> Sent: Freitag, 17. Februar 2012 17:48
> To: tycho-user@xxxxxxxxxxx
> Subject: Re: [tycho-user] Question about product materialization
>
> Some of the bundles in your RCP appear to have "hard" dependencies on
> the JDT. You need to trace them back to the direct dependencies of your
> projects and find a way to get rid of them (or accept JDT to be a part
> of the rcp).
>
> --
> Regards,
> Igor
>
> On 12-02-17 11:42 AM, Jeff MAURY wrote:
> > I tried to remove org.eclipse.jdt.core using the filters parameters but
> > my build now fails:
> > https://gist.github.com/1854289
> >
> > Regards
> > Jeff
> >
> >
> > On Fri, Feb 17, 2012 at 4:10 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
> > <mailto:igor@xxxxxxxxxxxxxx>> wrote:
> >
> >     This is likely because Xtext->JDT dependency is "optional/greedy" in
> >     Xtext p2 metadata. This is how P2 3.7 and earlier used to treat
> optional
> >     dependencies and the problem should go away once Xtext starts to use
> P2
> >     3.8M2 or newer for their build. In the mean time, you may be able to
> >     remove org.eclipse.jdt.* IUs from your RCP target platform using
> >
> >     http://wiki.eclipse.org/Tycho/__Target_Platform#Filtering
> >     <http://wiki.eclipse.org/Tycho/Target_Platform#Filtering>
> >
> >     --
> >     Regards,
> >     Igor
> >
> >
> >     On 12-02-17 9:59 AM, Jeff MAURY wrote:
> >
> >         My fault, I didn't look at the config.ini. I was able to
> generate a
> >         launcher.ini (vmargs for example).
> >         Now the only difference I see is regarding the optional
> >         dependencies: I
> >         am building an Xtext based product and Xtext has optional
> >         dependency on JDT.
> >         With the ProductExportMojo, the generated stuff didn't had the
> JDK
> >         plugins whereas now, I always see them even if I used the
> >         recommandation
> >         from http://wiki.eclipse.org/Tycho/__Release_Notes/0.14
> >         <http://wiki.eclipse.org/Tycho/Release_Notes/0.14>
> >
> >         Regards
> >         Jeff
> >
> >
> >         On Thu, Feb 16, 2012 at 11:51 PM, Igor Fedorenko
> >         <igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>
> >         <mailto:igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>>
> wrote:
> >
> >             I think .product properties are expected to go in
> >         config.ini, no? In any
> >             case, the behaviour should be consistent for all target
> >         environments, so
> >             please provide a small standalone example with detailed
> >         description of
> >             expected behaviour and we'll have a look.
> >
> >             --
> >             Regards,
> >             Igor
> >
> >
> >             On 12-02-16 3:58 PM, Jeff MAURY wrote:
> >
> >                 Hello,
> >
> >                 I have a product built with Tycho that was build with
> the
> >                 product export
> >                 mojo. As it is deprecated, I switched to an
> >         eclipse-repository
> >                 packaging
> >                 type and used the tycho-p2-director-plugin to build the
> >         product
> >                 files
> >                 (through the materialize-products goal)
> >                 But it seems the eclipse.ini (or launcher.ini as I
> >         changed the
> >                 name of
> >                 the launcher) is generated only for the MacOS
> >         distribution and
> >                 does not
> >                 contains items from my product file (properties)
> >                 Is it a bug or am I missing something ?
> >
> >                 Thanks
> >                 Jeff
> >
> >                 --
> >                 Jeff MAURY
> >
> >         "Legacy code" often differs from its suggested alternative by
> >                 actually
> >                 working and scaling.
> >                   - Bjarne Stroustrup
> >
> >         http://www.jeffmaury.com
> >         http://riadiscuss.jeffmaury.____com
> >         <http://riadiscuss.jeffmaury.__com
> >         <http://riadiscuss.jeffmaury.com>>
> >         http://www.twitter.com/____jeffmaury
> >         <http://www.twitter.com/__jeffmaury>
> >         <http://www.twitter.com/__jeffmaury
> >         <http://www.twitter.com/jeffmaury>>
> >
> >
> >                 ___________________________________________________
> >                 tycho-user mailing list
> >         tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> >         <mailto:tycho-user@xxxxxxxxxxx <mailto:tycho-
> user@xxxxxxxxxxx>__>
> >         https://dev.eclipse.org/____mailman/listinfo/tycho-user
> >         <https://dev.eclipse.org/__mailman/listinfo/tycho-user>
> >         <https://dev.eclipse.org/__mailman/listinfo/tycho-user
> >         <https://dev.eclipse.org/mailman/listinfo/tycho-user>>
> >
> >             ___________________________________________________
> >             tycho-user mailing list
> >         tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> >         <mailto:tycho-user@xxxxxxxxxxx <mailto:tycho-
> user@xxxxxxxxxxx>__>
> >         https://dev.eclipse.org/____mailman/listinfo/tycho-user
> >         <https://dev.eclipse.org/__mailman/listinfo/tycho-user>
> >
> >         <https://dev.eclipse.org/__mailman/listinfo/tycho-user
> >         <https://dev.eclipse.org/mailman/listinfo/tycho-user>>
> >
> >
> >
> >
> >         --
> >         Jeff MAURY
> >
> >         "Legacy code" often differs from its suggested alternative by
> >         actually
> >         working and scaling.
> >           - Bjarne Stroustrup
> >
> >         http://www.jeffmaury.com
> >         http://riadiscuss.jeffmaury.__com
> <http://riadiscuss.jeffmaury.com>
> >         http://www.twitter.com/__jeffmaury
> >         <http://www.twitter.com/jeffmaury>
> >
> >
> >         _________________________________________________
> >         tycho-user mailing list
> >         tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> >         https://dev.eclipse.org/__mailman/listinfo/tycho-user
> >         <https://dev.eclipse.org/mailman/listinfo/tycho-user>
> >
> >     _________________________________________________
> >     tycho-user mailing list
> >     tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> >     https://dev.eclipse.org/__mailman/listinfo/tycho-user
> >     <https://dev.eclipse.org/mailman/listinfo/tycho-user>
> >
> >
> >
> >
> > --
> > Jeff MAURY
> >
> > "Legacy code" often differs from its suggested alternative by actually
> > working and scaling.
> >   - Bjarne Stroustrup
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> > http://www.twitter.com/jeffmaury
> >
> >
> > _______________________________________________
> > 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
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user



--
Jeff MAURY

"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

Back to the top