Changes

<!-- Provides more depth than Here are the Project Description. This is details of the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to themmilestones so far. -->

Key contacts<b><font style="font-size:110%">0.1 Milestone</font></b>---- The purpose of this milestone is twofold - research and preliminary RPM package release. The research into the Eclipse extensions for Android showed that there are about 6 extensions (or plugins) for Eclipse that are related to Android:<pre>- ADT (Android Development Tools)- DDMS (Dalvik Debug Monitor Server)- GLDebugger (OpenGL Debugger)- Hierarchyviewer- Traceview- Base</pre> Progress so far:<pre>- research phase is mostly completed; we know what we need to do- extensions are stored as JAR files; JARs contain the source Java files- for a successful completion of this project, we need to simplify the process of installing ADT as much as possible</pre> How ADT needs to be installed at the moment:<pre>-> Install Eclipse, start Eclipse-> Get the Android depository link -> Add New Software In Eclipse -> Paste link -> Accept a few licences -> Wait for download and installation -> Restart Eclipse</pre> Instead, we intend to shorten it to this:<pre>-> Install Eclipse -> Run "yum install eclipse-adt eclipse-ddms ..." or "yum install @"Android Extensions for Eclipse-> Start Eclipse </pre> Alon will be focusing on packaging the ADT plugin and Daniel will be focusing on the DDMS plugin.  <b><font style="font-size:100%">ADT</font></b>---- In order to retrieve the files required for this release, the following steps were taken:<pre>- Eclipse was installed on Fedora 17 using the built in yum installer.- Plugins were installed using the built-in updater in Eclipse.- Required files were retrieved from the plugins and features folders under the main Eclipse folder:  eclipse/ dropins/ eclipse/ features/ plugins/  OR  eclipse/ dropins/ org.eclipse.core.tools_1.4.0.200710121455.jar org.eclipse.releng.tools_3.3.0.v20070412/ plugin.xml tools.jar</pre> To build the actual RPM, I downloaded a source RPM of an existing non-android Eclipse plugin and took a look at the spec file to determine the required steps needed to package and install the ADT Plugin. The RPM that I am releasing today, places the files in the correct folders, however, the dependencies required for the ADT Plugin are not included and therefore require manual intervention at this point. You can find the release files below: [http://dl.dropbox.com/u/3209356/ADT/adtplugin-0.0.1-1.fc17.noarch.rpm RPM][http://dl.dropbox.com/u/3209356/ADT/adtplugin-0.0.1-1.fc17.src.rpm SRPM][http://dl.dropbox.com/u/3209356/ADT/adtplugin.spec Spec file]  <b><font style="font-size:100%">DDMS</font></b>---- As stated previously, to package DDMS, the Dalvik Debug Monitor Server, first you have to have Eclipse installed (done through a simple <code>yum install<br /code>operation). After that, we would need an RPM to use to install the DDMS plugin. My RPM package was created by using the spec file of an already existing Eclipse plugin, and modifying it to my needs. I used the source JAR files that are provided by the Android project and packaged them into an RPM file, using rpmbuild. Here’s a quick [http://i.imgur.com/JJmPj.png screenshot]. Now we have an RPM that is almost complete - it places the JAR files in the correct sub-folders of Eclipse, but the plugin will not work - it needs a few [http://i.imgur.com/onxqd.png dependencies] to be satisfied. Those dependencies will be taken care of by milestone 0.2. Here are the RPM, SRC-RPM and spec files.[Userhttps: dkdelidj|Daniel//www.dropbox.com/s/yr1wj6646wqytin/ddms-0.0.1-1.fc17.noarch.rpm RPM][https://www.dropbox.com/s/0qt8x7qdv7be5e1/ddms-0.0.1-1.fc17.src.rpm SRPM] [https://www.dropbox.com/s/twts0w40sysboad/ddms.spec Spec file]  <b><font style="font-size:110%">0.2 Milestone</font></b>---- Progress so far:<pre>- ADT/DDMS plugins are both functioning if placed in the plugins/ and features/ directories- The RPM for ADT/DDMS works and gets installed without issues- Hierarchy Viewer RPM is also a successful installation</pre> Our team decided to package ADT and DDMS as one packages, and then add another RPM for another Android plugin. Daniel will package the ADT/DDMS plugins and Alon will package the Hierarchy Viewer.  <b><font style="font-size:100%">ADT + DDMS</font></b>---- Since ADT and DDMS cannot function without each other, we've combined them into one package called "eclipse-adt_ddms-plugin". ADT and DDMS both require each other and 2 more JAR files - the overlay and the base. All of them are included in the RPM.  For a more detailed look at the preparation phase of the RPM, please visit the [http://sbr600.tumblr.com/post/36367708826/0-2-android-extensions-for-eclipse blog post] by Daniel.  <b><font style="font-size:100%">Hierarchy Viewer</font></b>---- Due to the small change in our project plan as described above, Hierarchy Viewer is now the plugin packaged by Alon instead of ADT. Please visit the 0.2 release [Userhttp: //ayufidin|Alon.blogspot.ca/2012/11/packaging-android-extensions-for-eclipse_23.html post]for details.  <b><font style="font-size:110%">0.3 Milestone</font></b>----  <b><font style="font-size:100%">ADT + DDMS</font></b>---- ADT & DDMS final release is packaged by Daniel, please visit the blog [http://sbr600.tumblr.com/post/37518058012/0-3-adt-and-ddms-rpm-packages post]

Alon <b><font style="font- ADT Pluginsize:100%">Hierarchy Viewer + Traceview</font></b>Daniel - DDMS Plugin---

* 0.1 Goals for each release and plans for reaching those goals:<!--> Create RPMs that contain the Note: each contributor is expected to have unique goals.jar files relevant These goals may be ''related'' to each pluginother students' work, but must be ''distinct'' and ''attainable'' regardless of the RPM will place state of the files into other students' work. For example, under the "dropins" folder umbrella of one project title, one student may work on packaging a piece of Eclipsesoftware and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project.* 0.2 --> Include dependencies required for each plugin within the RPMs.

* 0.1 -> Create draft RPMs that contain the .jar files relevant to each plugin, the RPM will place the files into the "dropins" folder of Eclipse.* 0.2 -> Include dependencies required for each plugin within the RPMs, making sure we have functional RPMs.* 0.3 -> Finalizing RPMsand making sure that it is in the main Fedora Repo.

[http://sbr600.tumblr.com/ Daniel's blog]<!-- Links to the blogs of people involved, both inside and outside Seneca --br />[http://ayufidin.blogspot.ca/ Alon's blog]