p2-dev http://dev.eclipse.org/mhonarc/lists/p2-dev/maillist.html p2-dev en-us Sat, 25 May 2013 02:10:33 GMT Sat, 25 May 2013 02:10:33 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) p2-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/p2-dev/maillist.html Re: [p2-dev] How to uninstall a feature from a p2 site http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05206.html
They would but we are attempting to rev the versions internally and then publish.  So if we accidentally publish a bad artifact, we'd like to remove it and then re-publish without changing the version.  Also repository size may be a concern.

Thanks for your help!

On May 24, 2013, at 9:31 PM, Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx> wrote:

No, this is not a capability that the publisher applications have. Their goal is to be straightforward and dumb J Read some files produce some metadata.
But I would ask, if you have different features what would not they have a different version?
 
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Josh Hester
Sent: May-24-13 9:27 PM
To: P2 developer discussions
Subject: Re: [p2-dev] How to uninstall a feature from a p2 site
 
Thanks for the reply!
 
Sorry, I misspoke earlier.  We *are* using the Features and Bundles publisher (org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher).  Is there an option that we can pass in to remove a feature that has already been published?  I see the p2.remove.iu task.  Is there a command line option to pass this to the features and bundles publisher application?
 
Thanks,
 
-Josh
 
 
On May 24, 2013, at 8:57 PM, Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx> wrote:


There is an ant task called p2.remove.iu [1] that allows to remove IUs from a repository. Note that if this repo has been “put in production” this is not recommended as users may rely on the IUs you want to remove.
Another way to easily deal with repos is to use composite repository and publish different builds (assuming that this is what you are trying to do) in different repos.
 
Finally the p2 director is not used to add and remove to a repo. This is the role of the publisher. The director is the tool that performs the installation
 
 
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Josh Hester
Sent: May-24-13 10:12 AM
To: p2-dev@xxxxxxxxxxx
Subject: [p2-dev] How to uninstall a feature from a p2 site
 
Hi,
 
We are using the p2 director to publish features and bundles to a p2 site.  Is there a way to uninstall features from the p2 update site?
 
Thanks,
 
-Josh
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
 
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

]]> Sat, 25 May 2013 02:05:42 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05206.html Josh.Hester@xxxxxxx (Josh Hester) Re: [p2-dev] How to uninstall a feature from a p2 site http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05205.html There is an ant task called p2.remove.iu [1] that allows to remove IUs from a repository. Note that if this repo has been &#8220;put in production&#8221; this is not recommended as users may rely on the IUs you want to remove. Another way to easily deal with repos is...

No, this is not a capability that the publisher applications have. Their goal is to be straightforward and dumb J Read some files produce some metadata.

But I would ask, if you have different features what would not they have a different version?

 

From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Josh Hester
Sent: May-24-13 9:27 PM
To: P2 developer discussions
Subject: Re: [p2-dev] How to uninstall a feature from a p2 site

 

Thanks for the reply!

 

Sorry, I misspoke earlier.  We *are* using the Features and Bundles publisher (org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher).  Is there an option that we can pass in to remove a feature that has already been published?  I see the p2.remove.iu task.  Is there a command line option to pass this to the features and bundles publisher application?

 

Thanks,

 

-Josh

 

 

On May 24, 2013, at 8:57 PM, Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx> wrote:



There is an ant task called p2.remove.iu [1] that allows to remove IUs from a repository. Note that if this repo has been “put in production” this is not recommended as users may rely on the IUs you want to remove.

Another way to easily deal with repos is to use composite repository and publish different builds (assuming that this is what you are trying to do) in different repos.

 

Finally the p2 director is not used to add and remove to a repo. This is the role of the publisher. The director is the tool that performs the installation

 

 

From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Josh Hester
Sent: May-24-13 10:12 AM
To: p2-dev@xxxxxxxxxxx
Subject: [p2-dev] How to uninstall a feature from a p2 site

 

Hi,

 

We are using the p2 director to publish features and bundles to a p2 site.  Is there a way to uninstall features from the p2 update site?

 

Thanks,

 

-Josh

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

 

]]> Sat, 25 May 2013 01:31:50 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05205.html pascal.rapicault@xxxxxxx (Pascal Rapicault) Re: [p2-dev] How to uninstall a feature from a p2 site http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05204.html Thanks for the reply!

Sorry, I misspoke earlier.  We *are* using the Features and Bundles publisher (org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher).  Is there an option that we can pass in to remove a feature that has already been published?  I see the p2.remove.iu task.  Is there a command line option to pass this to the features and bundles publisher application?

Thanks,

-Josh


On May 24, 2013, at 8:57 PM, Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx> wrote:

There is an ant task called p2.remove.iu [1] that allows to remove IUs from a repository. Note that if this repo has been “put in production” this is not recommended as users may rely on the IUs you want to remove.
Another way to easily deal with repos is to use composite repository and publish different builds (assuming that this is what you are trying to do) in different repos.
 
Finally the p2 director is not used to add and remove to a repo. This is the role of the publisher. The director is the tool that performs the installation
 
 
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Josh Hester
Sent: May-24-13 10:12 AM
To: p2-dev@xxxxxxxxxxx
Subject: [p2-dev] How to uninstall a feature from a p2 site
 
Hi,
 
We are using the p2 director to publish features and bundles to a p2 site.  Is there a way to uninstall features from the p2 update site?
 
Thanks,
 
-Josh
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

]]> Sat, 25 May 2013 01:27:06 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05204.html Josh.Hester@xxxxxxx (Josh Hester) Re: [p2-dev] How to uninstall a feature from a p2 site http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05203.html There is an ant task called p2.remove.iu [1] that allows to remove IUs from a repository. Note that if this repo has been &#8220;put in production&#8221; this is not recommended as users may rely on the IUs you want to remove. Another way to easily deal with repos is...

There is an ant task called p2.remove.iu [1] that allows to remove IUs from a repository. Note that if this repo has been “put in production” this is not recommended as users may rely on the IUs you want to remove.

Another way to easily deal with repos is to use composite repository and publish different builds (assuming that this is what you are trying to do) in different repos.

 

Finally the p2 director is not used to add and remove to a repo. This is the role of the publisher. The director is the tool that performs the installation

 

[1] http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_repositorytasks.htm&resultof=%22p2%22%20%22ant%22%20%22task%22

 

From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Josh Hester
Sent: May-24-13 10:12 AM
To: p2-dev@xxxxxxxxxxx
Subject: [p2-dev] How to uninstall a feature from a p2 site

 

Hi,

 

We are using the p2 director to publish features and bundles to a p2 site.  Is there a way to uninstall features from the p2 update site?

 

Thanks,

 

-Josh

]]> Sat, 25 May 2013 00:57:04 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05203.html pascal.rapicault@xxxxxxx (Pascal Rapicault) Re: [p2-dev] [tycho-user] please test staged tycho 0.18.0 http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05202.html -- Jeff MAURY&quot;Legacy code&quot; often differs from its suggested alternative by actually working and scaling. &#xA0;- Bjarne Stroustruphttp://www.jeffmaury.comhttp://riadiscuss.jeffmaury.comhttp://www.twitter.com/jeffmaury
Jan,

I will do it.

Jeff


On Fri, May 24, 2013 at 6:04 PM, Sievers, Jan <jan.sievers@xxxxxxx> wrote:
- cross-posting to p2-dev -

thanks for reporting, Jeff.

just after staging tycho 0.18.0 I noticed
https://bugs.eclipse.org/bugs/show_bug.cgi?id=408997

which looks suspiciously similar. Solver timeouts with NPE in SAT solver.
Could you add your findings to this bug?

We did have a last minute update in the p2 version consumed by tycho [1] which might have caused this regression.
Although the new p2 version contains some fixes, we may have to revert to the previous p2 version from tycho 0.17.0.

Regards,
Jan

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=407972

From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Jeff MAURY
Sent: Freitag, 24. Mai 2013 17:37
To: Tycho user list
Cc: Tycho developers list; Common-build Developers discussion
Subject: Re: [tycho-user] please test staged tycho 0.18.0

Hello again,
I also have an error with the open source project GLDT (github.com/jeffmaury.gldt).
Jeff

On Fri, May 24, 2013 at 3:03 PM, Sievers, Jan <jan.sievers@xxxxxxx> wrote:
Tycho milestone release 0.18.0 has been staged.
This is mostly a bugfix release with fixes required by projects on the Kepler release train.

For details of new features and bugfixes, see release notes [1].
Please help by testing the staged milestone build. To use it, change your tycho version to 0.18.0 and add snippet [2] to your pom.

We plan to promote this release on Wed May 29th.

Regards,
Tycho team

[1] http://wiki.eclipse.org/Tycho/Release_Notes/0.18
[2]
<pluginRepositories>
 <pluginRepository>
  <id>tycho-staged</id>
  <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-053/</url>
 </pluginRepository>
</pluginRepositories>
_______________________________________________
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
_______________________________________________
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
]]> Fri, 24 May 2013 16:11:09 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05202.html jeffmaury@xxxxxxx (Jeff MAURY) Re: [p2-dev] [tycho-user] please test staged tycho 0.18.0 http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05201.html Tycho milestone release 0.18.0 has been staged. This is mostly a bugfix release with fixes required by projects on the Kepler release train. For details of new features and bugfixes, see release notes [1]. Please help by testing the staged milestone build.... - cross-posting to p2-dev - thanks for reporting, Jeff. just after staging tycho 0.18.0 I noticed https://bugs.eclipse.org/bugs/show_bug.cgi?id=408997 which looks suspiciously similar. Solver timeouts with NPE in SAT solver. Could you add your findings to this bug? We did have a last minute update in the p2 version consumed by tycho [1] which might have caused this regression. Although the new p2 version contains some fixes, we may have to revert to the previous p2 version from tycho 0.17.0. Regards, Jan [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=407972 From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Jeff MAURY Sent: Freitag, 24. Mai 2013 17:37 To: Tycho user list Cc: Tycho developers list; Common-build Developers discussion Subject: Re: [tycho-user] please test staged tycho 0.18.0 Hello again, I also have an error with the open source project GLDT (github.com/jeffmaury.gldt). Jeff On Fri, May 24, 2013 at 3:03 PM, Sievers, Jan <jan.sievers@xxxxxxx> wrote: Tycho milestone release 0.18.0 has been staged. This is mostly a bugfix release with fixes required by projects on the Kepler release train. For details of new features and bugfixes, see release notes [1]. Please help by testing the staged milestone build. To use it, change your tycho version to 0.18.0 and add snippet [2] to your pom. We plan to promote this release on Wed May 29th. Regards, Tycho team [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.18 [2] <pluginRepositories>  <pluginRepository>   <id>tycho-staged</id>   <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-053/</url>  </pluginRepository> </pluginRepositories> _______________________________________________ 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 ]]> Fri, 24 May 2013 16:04:45 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05201.html jan.sievers@xxxxxxx (Sievers, Jan) [p2-dev] How to uninstall a feature from a p2 site http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05200.html Hi, We are using the p2 director to publish features and bundles to a p2 site. Is there a way to uninstall features from the p2 update site? Thanks, -Josh

Hi,

 

We are using the p2 director to publish features and bundles to a p2 site.  Is there a way to uninstall features from the p2 update site?

 

Thanks,

 

-Josh

]]> Fri, 24 May 2013 14:12:05 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05200.html Josh.Hester@xxxxxxx (Josh Hester) [p2-dev] RPM, P2 and reconciliation again - huge problems http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05199.html Hi P2 masters, Eclipse packages in Fedora use dropins as a primary deployment mechanism, because there is no way to make P2 and RPM working together (which I can explain in details upon request or at EclipseCon France). Shared scenarios were greatly improv... Hi P2 masters, Eclipse packages in Fedora use dropins as a primary deployment mechanism, because there is no way to make P2 and RPM working together (which I can explain in details upon request or at EclipseCon France). Shared scenarios were greatly improved in Kepler thanks to Ericsson support. But there is still one more issue that is not resolved - and I guess not really visible unless you use shared deployments at large scale, which is related to the implicit dependencies in Eclipse - causing incomplete bundles refresh and in turn various ClassCastExceptions, NoClassDefFoundErrors during first startup [1][2]. This really makes Eclipse in Fedora to look unprofessional. After I tracked those implicit dependencies, and built Eclipse with proper patches, it turned out dropins did not worked anymore as expected due to the fact that during the OSGi refresh core P2 bundles were restarted, and the OSGi attempted to restart dropins synchronizer, which failed because of being in the "starting" state. The scenario once more in bullet points: * a bundle providing vital classes put in the dropins (f.e. javax.xml) * reconciler goes into starting state * reconciler installs javax.xml, writes timestamps and applies configuration * osgi starts refreshing bundles (stopping them and starting) * osgi tries to restart reconciler (which is still starting, an exception occurs) In the end: timestamps are stored, bundles.info seems to be ok, but OSGi cache is old, because the new configuration was not applied. Eclipse will not pick it unless invoked explicitly with -clean. It does not make Eclipse in Fedora unprofessional, it just sucks! As a result - I had to revert my patch for [2] and accept first-run problems. I've tried to come up with any creative solution, but did not managed to get anything valuable here: * OSGi can't really interrupt start method - man, that would be a hack! * Reconciliation can't be moved out of a start method - because the Eclipse start process must be blocked until reconciliation is complete. This applied to an applyConfiguration, too. * External reconciler cannot be run, because nothing should be stored in a master configuration. Looks like a dead end. Any suggestions how should I proceed with this? [1] Bug 297769 - Split packages are not refreshed properly https://bugs.eclipse.org/bugs/show_bug.cgi?id=297769 [2] Bug 406359 - Yet another class surviving refresh invoked by dropins https://bugs.eclipse.org/bugs/show_bug.cgi?id=406359 Regards, -- Krzysztof Daniel <kdaniel@xxxxxxxxxx> Red Hat ]]> Wed, 15 May 2013 10:37:22 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05199.html kdaniel@xxxxxxx (Krzysztof Daniel) Re: [p2-dev] [tycho-user] Trouble upgrading Mac Bundles http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05198.html

> Maybe (...)

 

I case you want to find out: http://wiki.eclipse.org/Developing_Tycho

 

Regards

Tobias

 

 

From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: Donnerstag, 9. Mai 2013 17:02
To: P2 developer discussions
Cc: p2-dev@xxxxxxxxxxx; Tycho user list
Subject: Re: [p2-dev] [tycho-user] Trouble upgrading Mac Bundles

 

This is a publisher / metadata gen issue. Maybe the invocation from tycho is incorrect.

 


On 2013-05-09, at 10:56 AM, Doug Schaefer <dschaefer@xxxxxxx> wrote:

And I can confirm that manually adding the missing IU, "tooling*.executable.macosx.x86-bundled", into the repository's content.xml works.

 

Is this the p2 director not inserting this correctly, or is it tycho not passing in the right parameters to the director, or am I missing an argument in my pom?

 

Thanks,

Doug.

 

From: Doug Schaefer <dschaefer@xxxxxxx>
Date: Thursday, 9 May, 2013 9:27 AM
To: Tycho user list <tycho-user@xxxxxxxxxxx>, "p2-dev@xxxxxxxxxxx" <p2-dev@xxxxxxxxxxx>
Subject: Re: [tycho-user] Trouble upgrading Mac Bundles

 

To further my investigation, I see a macosx-bundled filter in the p2content.xml file. It doesn't seem to be set true when the repository is created taking the non-bundle executable IU. Is there a way to turn this filter on when generating the repository?

 

From: Doug Schaefer <dschaefer@xxxxxxx>
Reply-To: Tycho user list <tycho-user@xxxxxxxxxxx>
Date: Thursday, 9 May, 2013 1:00 AM
To: Tycho user list <tycho-user@xxxxxxxxxxx>
Subject: Re: [tycho-user] Trouble upgrading Mac Bundles

 

Sorry, I meant can't upgrade. But I guess that's obvious from the error messageâ

 

From: Doug Schaefer <dschaefer@xxxxxxx>
Reply-To: Tycho user list <tycho-user@xxxxxxxxxxx>
Date: Thursday, 9 May, 2013 12:57 AM
To: "tycho-user@xxxxxxxxxxx" <tycho-user@xxxxxxxxxxx>
Subject: [tycho-user] Trouble upgrading Mac Bundles

 

Hey gang,

 

I'm using the new platform specific rootFolders feature in 0.18-SNAPSHOT tycho to generate the Mac version of my product as a Mac app bundle. I'm pretty sure this worked at one point but now I can upgrade from build to build. I get the following:

 

Cannot complete the install because one or more required items could not be found.

  Software being installed: QNX Momentics IDE 10.2.0.v201305090421 (com.qnx.tools.bbt.ide.ide-internal 10.2.0.v201305090421)

  Missing requirement for filter properties ~= $0: toolingcom.qnx.tools.bbt.ide.ide-internal.application 10.2.0.v201305090421 requires 'toolingcom.qnx.tools.bbt.ide.ide-internal.executable.cocoa.macosx.x86-bundled [10.2.0.v201305090421]' but it could not be found

  Cannot satisfy dependency:

    From: QNX Momentics IDE 10.2.0.v201305090421 (com.qnx.tools.bbt.ide.ide-internal 10.2.0.v201305090421)

    To: toolingcom.qnx.tools.bbt.ide.ide-internal.application [10.2.0.v201305090421]

 

I see the tooling*-bundled IU in the p2content.xml file but not in the content.jar in the repository. Is this a bug, or am I doing it wrong? Or is this something wrong in p2?

 

Thanks!

Doug.

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

]]> Mon, 13 May 2013 08:34:38 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05198.html tobias.oberlies@xxxxxxx (Oberlies, Tobias) Re: [p2-dev] [tycho-user] Trouble upgrading Mac Bundles http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05197.html
OK, I raised a bug against Tycho: https://bugs.eclipse.org/bugs/show_bug.cgi?id=407676

Do we know what the invocation should be so I can check?

From: Pascal Rapicault <pascal@xxxxxxxxxxxxx>
Reply-To: P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date: Thursday, 9 May, 2013 11:01 AM
To: P2 developer discussions <p2-dev@xxxxxxxxxxx>
Cc: "p2-dev@xxxxxxxxxxx" <p2-dev@xxxxxxxxxxx>, Tycho user list <tycho-user@xxxxxxxxxxx>
Subject: Re: [p2-dev] [tycho-user] Trouble upgrading Mac Bundles

This is a publisher / metadata gen issue. Maybe the invocation from tycho is incorrect.



On 2013-05-09, at 10:56 AM, Doug Schaefer <dschaefer@xxxxxxx> wrote:

And I can confirm that manually adding the missing IU, "tooling*.executable.macosx.x86-bundled", into the repository's content.xml works.

Is this the p2 director not inserting this correctly, or is it tycho not passing in the right parameters to the director, or am I missing an argument in my pom?

Thanks,
Doug.

From: Doug Schaefer <dschaefer@xxxxxxx>
Date: Thursday, 9 May, 2013 9:27 AM
To: Tycho user list <tycho-user@xxxxxxxxxxx>, "p2-dev@xxxxxxxxxxx" <p2-dev@xxxxxxxxxxx>
Subject: Re: [tycho-user] Trouble upgrading Mac Bundles

To further my investigation, I see a macosx-bundled filter in the p2content.xml file. It doesn't seem to be set true when the repository is created taking the non-bundle executable IU. Is there a way to turn this filter on when generating the repository?

From: Doug Schaefer <dschaefer@xxxxxxx>
Reply-To: Tycho user list <tycho-user@xxxxxxxxxxx>
Date: Thursday, 9 May, 2013 1:00 AM
To: Tycho user list <tycho-user@xxxxxxxxxxx>
Subject: Re: [tycho-user] Trouble upgrading Mac Bundles

Sorry, I meant can't upgrade. But I guess that's obvious from the error message…

From: Doug Schaefer <dschaefer@xxxxxxx>
Reply-To: Tycho user list <tycho-user@xxxxxxxxxxx>
Date: Thursday, 9 May, 2013 12:57 AM
To: "tycho-user@xxxxxxxxxxx" <tycho-user@xxxxxxxxxxx>
Subject: [tycho-user] Trouble upgrading Mac Bundles

Hey gang,

I'm using the new platform specific rootFolders feature in 0.18-SNAPSHOT tycho to generate the Mac version of my product as a Mac app bundle. I'm pretty sure this worked at one point but now I can upgrade from build to build. I get the following:

Cannot complete the install because one or more required items could not be found.
  Software being installed: QNX Momentics IDE 10.2.0.v201305090421 (com.qnx.tools.bbt.ide.ide-internal 10.2.0.v201305090421)
  Missing requirement for filter properties ~= $0: toolingcom.qnx.tools.bbt.ide.ide-internal.application 10.2.0.v201305090421 requires 'toolingcom.qnx.tools.bbt.ide.ide-internal.executable.cocoa.macosx.x86-bundled [10.2.0.v201305090421]' but it could not be found
  Cannot satisfy dependency:
    From: QNX Momentics IDE 10.2.0.v201305090421 (com.qnx.tools.bbt.ide.ide-internal 10.2.0.v201305090421)
    To: toolingcom.qnx.tools.bbt.ide.ide-internal.application [10.2.0.v201305090421]

I see the tooling*-bundled IU in the p2content.xml file but not in the content.jar in the repository. Is this a bug, or am I doing it wrong? Or is this something wrong in p2?

Thanks!
Doug.
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
 ]]> Thu, 09 May 2013 18:20:37 GMT http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05197.html dschaefer@xxxxxxx (Doug Schaefer)