<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Shivanshu Singh</title>
    <description/>
    <link>https://speakerdeck.com/shivanshukumar</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/shivanshukumar.rss"/>
    <lastBuildDate>2013-05-01 00:55:20 -0400</lastBuildDate>
    <item>
      <title>Verifying Dependencies in Eclipse</title>
      <description>Eclipse is a system of plugins, where multiple plugins come together to form any typical instance of the application. The core eclipse infrastructure is in itself a combination of plugins. With a large number of options available from a marketplace of plugins, where an end usr may choose to install just about any arbitrary mix of them on eclipse, ensuring compatibility between plugins in a chosen combination is important especially when considering that eclipse is now being used in all sorts of (sensitive and non-sensitive) contexts. In this talk I presented my ongoing work and experiences so far in checking if given a combination of plugins, all the stated dependencies of all the plugins are satisfied, and to see if any plugins have unnecessary, unstated or unsatisfied dependencies. </description>
      <media:content url="https://files.speakerdeck.com/presentations/0bdaf2d094490130d1bc6e09463ce40c/preview_slide_0.jpg?1401638" type="image/jpeg" medium="image"/>
      <content:encoded>Eclipse is a system of plugins, where multiple plugins come together to form any typical instance of the application. The core eclipse infrastructure is in itself a combination of plugins. With a large number of options available from a marketplace of plugins, where an end usr may choose to install just about any arbitrary mix of them on eclipse, ensuring compatibility between plugins in a chosen combination is important especially when considering that eclipse is now being used in all sorts of (sensitive and non-sensitive) contexts. In this talk I presented my ongoing work and experiences so far in checking if given a combination of plugins, all the stated dependencies of all the plugins are satisfied, and to see if any plugins have unnecessary, unstated or unsatisfied dependencies. </content:encoded>
      <pubDate>Mon, 29 Apr 2013 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/shivanshukumar/verifying-dependencies-in-eclipse</link>
      <guid>https://speakerdeck.com/shivanshukumar/verifying-dependencies-in-eclipse</guid>
    </item>
  </channel>
</rss>
