• View
• Edit
• History
• Print

Osgi2-0

In November 2014, Erwin De Ley worked on getting the ptII repo to be more OSGi complaint.

Resources

• https://repo.eecs.berkeley.edu/svn-anon/projects/eal/ptII/branches/osgi-2-0/ - Erwin's branch

Eclipse Instructions

• Start up Eclipse, create a new workspace.
• Windows -> Show View -> Others -> SVN Repository
  • If SVN Repository is not present, then set up Eclipse with SVN. See
    • Mac: http://chess.eecs.berkeley.edu/ptexternal/nightly/doc/eclipse/mac/eclipseSVN.htm
    • Windows: http://chess.eecs.berkeley.edu/ptexternal/nightly/doc/eclipse/windows/eclipseSVN.htm
• Right Click, select New Repository Location
  • For anonymous access, paste in https://repo.eecs.berkeley.edu/svn-anon/projects/eal/ptII
  • If you have read/write access to the repo, paste in https://repo.eecs.berkeley.edu/svn/projects/eal/ptII/, Enter your user name and password, Click Finish (If you would like read/write access, email Christopher)
• Click on the SVN Repo, click on branches, select osgi-2-0
• Right click on osgi-2-0, Select Find/Check Out As
• Select Find projects in the children of the selected resource, select Finish. The repo will be scanned for projects.
• In "Selected projects will be checked out into the workspace", select Finish. There will be lots of errors because ptII is missing
• In the SVN Repositories tab, check out the ptII repo
  • Right click on the trunk, select Find/Check Out As
  • In Check Out As, keep the default "Check out as a project configured using the New Project Wizard", click on Finish
  • In "Select a wizard", Expand Java and then click on "Java Project", then click on Next.
  • In "Create a Java Project", for Project Name, enter ptII. Under Project Layout, select "Use project folder as root for sources and class files". Click Next.
  • In "Java Settings", select "Allow output folders for source folder", click Finish. ptII will be checked out
  • After ptII is checked out, copy .classpath.default to .classpath. Use either the shell or Window -> Show View -> Navigator.
  • If the ptII project does not build, then right click on the ptII project and select Refresh.
• Set the PT_LOC variable to the location of the ptII tree:
  • Under Preferences -> General -> Workspace -> Linked resources
  • In the Path Variables section, select New, enter PT_LOC for Name and select Folder
  • Browse to workspace directory, select the ptII directory and click on Open
  • Click on OK
• Clean all the projects and rebuild: Project -> Clean ...

Problems

StringUtilities.java could not be read

The problem was

The project was not built since the source file /ptolemy.core/linked-src/ptolemy/util/StringUtilities.java could not be read

Solution:

• Expand ptolemy.core -> linked-src -> ptolemy.util.
• Right click on the StringUtilities.java, select Properties. Note that the Location is "PT_LOC/ptolemy/util/StringUtilities.java".
• Click on the Edit button next to the Location. Then Click on Variables. Note that

"PT_LOC" is "/C:/data/build-folders/ptolemy"

• Click on Edit, then File. Find the ptII directory checked out above

I'm not sure if I got the above right, but I ended up editing the .project files.

ptolemy.moml package.html not found

Solution: Open up the link-source and delete it, it is not necessary.

Do the same with README.txt in that directory.

Change on Nov 27th

PT_LOC variable has been removed from the individual .project files.
You should now set it as a variable for linked resource in your workspace preferences, under General > Workspace > Linked resources > Path variables
PT_LOC should point to the root folder of your workspace.

Continuing along

• Right clicking on the projects and refreshing helped and finally everything built

Running the test

• Select org.ptolemy.core.test
• Run -> Run Configurations. Select Junit, hit the new button and hit Run
• testModelExecution fails with

This is caused by the relience of the flow execution test assertions on using ptolemy DebugListeners. But it seems that currently ptolemy doesn't consistently generate events (cfr also JavaDoc of the ModelExecutionTest). After the release of ptII v10, we can check on how to get this working.

• testModeDefinition1 passes!

Licenses

$PTII/ptolemy/actor/gui/GenerateCopyrights.java has a generateHTML(Configuration) method that will use reflection to look for classes listed in GenerateCopyrights that have licenses.

org.ptolemy.actor.gui.test/src/test/java/org/ptolemy/actor/gui/test/GenerateHTMLTest.java defines a test that invokes generateHTML(null), which lists that licenses on stdout.

Running the tests in org.ptolemy.actor.gui.test as above will display the licenses in the Eclipse console.

What files are in the sources uses in the branch?

677 files, 237k lines