Difference between revisions of "DPS909 and OSD600 Winter 2009 Eclipse WTP Weekly Schedule"

From CDOT Wiki
Jump to: navigation, search
m (→‎Week 5 (Feb 9) - Test-Driven Development (TDD): fixed link to junit tutorial)
 
Line 157: Line 157:
 
* '''TODO'''
 
* '''TODO'''
 
** Read about '''[http://en.wikipedia.org/wiki/Test-driven_development Test-driven development]''' for using the JUnit testing facility in Eclipse.
 
** Read about '''[http://en.wikipedia.org/wiki/Test-driven_development Test-driven development]''' for using the JUnit testing facility in Eclipse.
−
** Read the tutorial '''[http://open.ncsu.edu/se/tutorials/junit/#section1_0 Unit Testing in Eclipse Using JUnit]'''
+
** Read the tutorial '''Unit Testing in Eclipse Using JUnit: from [http://agile.csc.ncsu.edu/SEMaterials/tutorials/junit/junit_tutorial_3.1.html here] or [http://www.cs.umanitoba.ca/~eclipse/10-JUnit.pdf here]'''
 
** Practice the Eclipse Debugger. [http://eclipsetutorial.sourceforge.net/debugger.html Use this tutorial] for an '''introduction to debugger's features.''' One can [http://sourceforge.net/project/showfiles.php?group_id=200662&package_id=251688# download the tutorials]
 
** Practice the Eclipse Debugger. [http://eclipsetutorial.sourceforge.net/debugger.html Use this tutorial] for an '''introduction to debugger's features.''' One can [http://sourceforge.net/project/showfiles.php?group_id=200662&package_id=251688# download the tutorials]
−
 
  
 
== Week 6 (Feb 16) - Eclipse WTP wiki ==
 
== Week 6 (Feb 16) - Eclipse WTP wiki ==

Latest revision as of 20:15, 22 April 2009

Introduction

The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn and/or review how to work with Java EE, WTP, Eclipse project techniques and practices. Second, students focus on bug fixing within the Eclipse WTP project itself. All your work will be based on this Basic Tutor

Part I – Essential Open Source Development and Java/Eclipse Skills and Concepts

Week 1 (Jan 12) Course introduction

  • TODO
    • Create an account on this wiki for yourself
    • Create a personal wiki page on this wiki
    • Add a link for yourself to the People page and the Winter 2009 Open Source Students page
    • Create a blog (wordpress or blogspot or whatever) and create a feed category or tag called "open source"
    • Read the Blog Guidelines for instructions on how to use your blog in the course
    • Add your blog feed and info to the Open Source@Seneca Planet List so that it appears in the OpenSource@Seneca Planet
    • Blog on your reactions to the readings for this week.
    • Begin learning how to use IRC for communication. It is better to get started early such as your Eclipse workplace is set for programming.
    • After you install Eclipse for RCP/Plug-in Developers (175 MB) you will have ECF (Eclipse Communication Framework) and IRC client; you can open an IRC client from the Communication Perspective.


Week 2 (Jan 19) - Eclipse Webtools Overview

The First Milestone

At the end of the second week you must have an working environment:
Please, follow the instructions from tutorial to install Eclipse PlugIn and Eclipse WTP on your systems.

IMPORTANT NOTE: As it was suggested by Mr. Angel Vera: “The best place for the students to post question and get answers to it will be the eclipse newsgroup". There is a long list of newsgroups that you can benefit from depending on the question. As you are going to be working with Webtools, you would probably want to stay within the Eclipse Web Tools Platform Project. This is an open community of adopters and developers working with the Webtools project.

Week 3 (Jan 26) - Navigating the WTP source tree

The Second Milestone

At the end of the third week you must attentively decide and publish the list of your bug(s) (i.e. the bug(s) you want to work on in this course)
Please, update the project column of the table Winter 2009 Open Source Students with the following information: WTP-Bug ID, Severity, and Priority".

IMPORTANT NOTE: The marks obtained on the second milestone will be posted on your course page. Continue to wiki and blog intensively as a provided evidence of your persist involvement and dedication to improve WTP Projects by fixing bugs in such a wonderful community work.


Week 4 (Feb 2) - WTP Servertools Webpage

The Third Milestone

At the end of the this week you must release the first Project Deliverable:
Reproduce the bug. This is your 0.1 Release
Please, update your blog by defining the steps to reproduce your bug (i.e. the bug that you are working on). As a example use this blog


Week 5 (Feb 9) - Test-Driven Development (TDD)

Week 6 (Feb 16) - Eclipse WTP wiki

The Fourth Milestone

At the end of the this week, based on the presentation, you must have a good idea how to search Eclipse source. Blog about your experience in finding the source code (problems, advices, interesting findings). Define the steps to find the code that is related to your bug (i.e. the bug that you are working on).

Week 7 (Feb 23) - WTP Stable Build

  • Eclipse Platform (Platform, JDT)
  • EMF v2.5 Runtime Minimum executable code.
  • EMF XSD v2.5 Runtime Minimum executable code.
  • Graphical Editing Framework (GEF)
  • Data Tools Platform (DTP)
  • Assignment 2 - Due: March 10, 2009
  • Presentation
    • Lawrence Mandel, Software Developer IBM Rational Software
      • Eclipse Plug-in Architecture
      • Techniques for developing Eclipse WTP
    • Tuesday Feb, 24 from 11:40 a.m. to 1:25 p.m. @ S2149
  • TODO


Week 8 (March 9) Bug Fixing


Week 9 (March 16) Eclipse NewsPortal

  • Eclipse NewsPortal
  • Web Persistence with JPA
  • Bug Release 0.2 Due Date: March 20, 2009
  • TODO
    • Verify your fixes (your code) against the latest build: Build for wtp-R3.1-S: S-3.1M6-20090318020101
    • As per March 19, when you write to Bugzilla use the Build 3.1M6 (as the new releases are released, please download and use them accordingly)

Week 10 (March 23) Sample Project Template

  • Sample Project Template
    • 30% - Bug 0.3 Release
    • Complete your personal wiki page and describe briefly your accomplishments (from the beginning to the present date).

Please use as a model the this wiki page Although, this example is related to the Mozilla project, the same template can be used for your project (bugs) description. Your project wiki page will be used as a synthesis for the final evaluation of your work. It is very important to write about: Project Ideas, Details and News.

Week 11 (March 30) The Fifth Milestone

As per today, April 2nd, 11.15 p.m. a new build is released. Please use Build wtp-R3.1-I: I-3.1-20090402044606 for your latest fixes. The community is looking forward to seeing your FIXES on Bugzilla. Please post your concise analysis and solution (in your blog posting), together with your patch.

The Fifth Milestone

At the end of the this week (11 - deadline extended), you have to post the result of your work in Bugzilla (as defined in our March 24 lecture). Post all your findings related to the bug that you are working on. For most of you this will be your fixes, but if you did not reach that point, post your findings as you consider them valuable for the community. This is your 0.3 Release and will be marked (30%).

Week 12 (April 06) - Collaboratively Bug Fixing


Week 13 (Apr 12) - Open Source Learning Experience

    • Your Work Results and Accomplishments
    • Wiki Updates and Presentations



Summary of Accomplishments

DPS909 and OSD600 Winter 2009 Eclipse WTP Summary

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_Eclipse_WTP_Weekly_Schedule&oldid=25605"