<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to Project umple</title><link href="https://sourceforge.net/p/umple/" rel="alternate"/><link href="https://sourceforge.net/p/umple/feed.atom" rel="self"/><id>https://sourceforge.net/p/umple/</id><updated>2017-12-28T16:00:19.125000Z</updated><subtitle>Recent changes to Project umple</subtitle><entry><title>_Sidebar modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/_Sidebar/" rel="alternate"/><published>2017-12-28T16:00:19.125000Z</published><updated>2017-12-28T16:00:19.125000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.net45a8c832afbb86c6c585fff92afddc1d3323079a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;h2 id="general"&gt;General&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/Home/"&gt;Wiki Home and News&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/FAQ/"&gt;FAQ Frequently asked questions&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a class="" href="../Examples"&gt;Examples&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a class="" href="../Tutorials"&gt;Tutorials&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/PhilosophyAndVision/"&gt;PhilosophyAndVision&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/BestUmpleUsePractices/"&gt;Best practices for using Umple&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/Publications/"&gt;Publications and presentations&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/InstallEclipsePlugin/"&gt;Installing Eclipse plugin&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="developers"&gt;Developers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="" href="../DevelopmentSetUp"&gt;Developer Setup&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/ContributionProcessToUmple/"&gt;Contribution Process&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="../Architecture"&gt;Architecture&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/CheatSheet/"&gt;Cheat sheet&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/ProjectPortfolio/"&gt;Planned development&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="../DraftManualPages"&gt;DraftManualPages&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="server-maintenance"&gt;Server maintenance&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="" href="../ServerMaintenance"&gt;ServerMaintenance&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="external"&gt;External&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="" href="https://github.com/orgs/umple/teams" rel="nofollow"&gt;Team Members&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/WebSubdomainsUmpleOrg/"&gt;Subdomains of umple.org&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="other"&gt;Other&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="" href="/p/umple/wiki/UCOSP/"&gt;UCOSP and FBOA&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>_Footer modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/_Footer/" rel="alternate"/><published>2017-12-28T16:00:19.084000Z</published><updated>2017-12-28T16:00:19.084000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.net61d2892daad9c80f6f3a34893dc823c91bfe8752</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;a class="" href="http://www.umple.org" rel="nofollow"&gt;Umple.org&lt;/a&gt; • &lt;a class="" href="http://manual.umple.org" rel="nofollow"&gt;User Manual&lt;/a&gt; • &lt;a class="" href="http://try.umple.org" rel="nofollow"&gt;UmpleOnline&lt;/a&gt; • &lt;a class="" href="../DevelopmentSetUp"&gt;Dev setup&lt;/a&gt; • &lt;a class="" href="/p/umple/wiki/Home/"&gt;Wiki home&lt;/a&gt; • &lt;a class="" href="http://code.umple.org" rel="nofollow"&gt;Code&lt;/a&gt; • &lt;a class="" href="/p/umple/wiki/UCOSP/"&gt;UCOSP&lt;/a&gt; &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>WebSubdomainsUmpleOrg modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/WebSubdomainsUmpleOrg/" rel="alternate"/><published>2017-12-28T16:00:18.991000Z</published><updated>2017-12-28T16:00:18.991000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.neteeff2b93e54c8a3348205fd6ce9fce439afdd5a4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Good pages to start seeking information&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.umple.org" rel="nofollow"&gt;http://www.umple.org&lt;/a&gt; Main Umple page&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://dl.umple.org" rel="nofollow"&gt;http://dl.umple.org&lt;/a&gt;  Download instructions to obtain official releases or continuous integration releases&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://manual.umple.org" rel="nofollow"&gt;http://manual.umple.org&lt;/a&gt; User manual introductory page&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="http://classes.umple.org" rel="nofollow"&gt;http://classes.umple.org&lt;/a&gt; User manual page on class definition in Umple&lt;/li&gt;
&lt;li&gt;&lt;a href="http://attributes.umple.org" rel="nofollow"&gt;http://attributes.umple.org&lt;/a&gt; User manual page on attributes&lt;/li&gt;
&lt;li&gt;&lt;a href="http://asociations.umple.org" rel="nofollow"&gt;http://asociations.umple.org&lt;/a&gt; User manual page on associations&lt;/li&gt;
&lt;li&gt;&lt;a href="http://statemachines.umple.org" rel="nofollow"&gt;http://statemachines.umple.org&lt;/a&gt; User manual page on state machines&lt;/li&gt;
&lt;li&gt;&lt;a href="http://motl.umple.org" rel="nofollow"&gt;http://motl.umple.org&lt;/a&gt; User manual page on tracing and the MOTL sublanguage&lt;/li&gt;
&lt;li&gt;&lt;a href="http://grammar.umple.org" rel="nofollow"&gt;http://grammar.umple.org&lt;/a&gt; User manual page with the complete grammar&lt;/li&gt;
&lt;li&gt;&lt;a href="http://api.umple.org" rel="nofollow"&gt;http://api.umple.org&lt;/a&gt; Api quick reference user manual page&lt;/li&gt;
&lt;li&gt;&lt;a href="http://adopt.umple.org" rel="nofollow"&gt;http://adopt.umple.org&lt;/a&gt; User manual page about how to convince potential adopters&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://privacy.umple.org" rel="nofollow"&gt;http://privacy.umple.org&lt;/a&gt; Privacy and risks statement&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://blog.umple.org" rel="nofollow"&gt;http://blog.umple.org&lt;/a&gt; Sub-pages of Dr. Lethbridge's blog relating to Umple&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="http://list.umple.org" rel="nofollow"&gt;http://list.umple.org&lt;/a&gt; Umple main announcements mailing list&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Umple Online, a tool to edit code or diagrams, and generate code from UML&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://try.umple.org" rel="nofollow"&gt;&lt;/a&gt;&lt;a href="http://try.umple.org" rel="nofollow"&gt;&lt;/a&gt;&lt;a href="http://try.umple.org" rel="nofollow"&gt;http://try.umple.org&lt;/a&gt; Umple Online web app (also &lt;a href="http://go.umple.org" rel="nofollow"&gt;&lt;/a&gt;&lt;a href="http://go.umple.org" rel="nofollow"&gt;&lt;/a&gt;&lt;a href="http://go.umple.org" rel="nofollow"&gt;http://go.umple.org&lt;/a&gt;)&lt;ul&gt;
&lt;li&gt;You can append &lt;a class="" href="http://cruise.site.uottawa.ca/umple/UsingUmpleOnline.html" rel="nofollow"&gt;arguments to access specific examples and saved pages&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Quick links in the wiki&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://wiki.umple.org" rel="nofollow"&gt;http://wiki.umple.org&lt;/a&gt; Github Wiki page for Umple.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://examples.umple.org" rel="nofollow"&gt;http://examples.umple.org&lt;/a&gt; Wiki page containing examples.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://philosophy.umple.org" rel="nofollow"&gt;http://philosophy.umple.org&lt;/a&gt; Philosophy of Umple&lt;/li&gt;
&lt;li&gt;&lt;a href="http://install.umple.org" rel="nofollow"&gt;http://install.umple.org&lt;/a&gt; Installing Eclipse so you can get going developing using Umple&lt;/li&gt;
&lt;li&gt;&lt;a href="http://devsetup.umple.org" rel="nofollow"&gt;http://devsetup.umple.org&lt;/a&gt; For contributors, development setup&lt;/li&gt;
&lt;li&gt;&lt;a href="http://portfolio.umple.org" rel="nofollow"&gt;http://portfolio.umple.org&lt;/a&gt; For contributors, current and planned development&lt;/li&gt;
&lt;li&gt;&lt;a href="http://deploy.umple.org" rel="nofollow"&gt;http://deploy.umple.org&lt;/a&gt; For contributors, deploying Umple&lt;/li&gt;
&lt;li&gt;&lt;a href="http://cheatsheet.umple.org" rel="nofollow"&gt;http://cheatsheet.umple.org&lt;/a&gt; For contributors, cheat sheet of useful commands and paths&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Key pages at the Github hosting site&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://code.umple.org" rel="nofollow"&gt;http://code.umple.org&lt;/a&gt; Github main page for Umple (trunk is a synonym)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Quick links to pages in the issues subsystem&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://bugs.umple.org" rel="nofollow"&gt;http://bugs.umple.org&lt;/a&gt; Github issue tracking for Umple (synonym issues, also includes requirements)&lt;/li&gt;
&lt;li&gt;&lt;a href="http://projects.umple.org" rel="nofollow"&gt;http://projects.umple.org&lt;/a&gt; Subset of issues, suitable for student projects&lt;/li&gt;
&lt;li&gt;&lt;a href="http://research.umple.org" rel="nofollow"&gt;http://research.umple.org&lt;/a&gt; Subset of issues, suitable for research&lt;/li&gt;
&lt;li&gt;&lt;a href="http://changed.umple.org" rel="nofollow"&gt;http://changed.umple.org&lt;/a&gt; Recent changes. Issues closed in the last 180 days.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Pages allowing contributors to check the status of the build&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://cc.umple.org" rel="nofollow"&gt;http://cc.umple.org&lt;/a&gt; Build server, listing the latest build&lt;/li&gt;
&lt;li&gt;&lt;a href="http://qa.umple.org" rel="nofollow"&gt;http://qa.umple.org&lt;/a&gt; Most recent test results from the build&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Pages to help understand the architecture&lt;br/&gt;
  * &lt;a href="http://metamodel.umple.org" rel="nofollow"&gt;http://metamodel.umple.org&lt;/a&gt; Class diagram of the Umple compiler itself, generated by Umple&lt;br/&gt;
  * &lt;a href="http://architecture.umple.org" rel="nofollow"&gt;http://architecture.umple.org&lt;/a&gt; Overall architecture&lt;br/&gt;
  * &lt;a href="http://tracingdesign.umple.org" rel="nofollow"&gt;http://tracingdesign.umple.org&lt;/a&gt; Tracing (MOTL -Model Oriented Tracing Language)&lt;br/&gt;
  * &lt;a href="http://fsmdesign.umple.org" rel="nofollow"&gt;http://fsmdesign.umple.org&lt;/a&gt; State machines&lt;/p&gt;
&lt;p&gt;These are maintained as 'hovers' by our domain provider, &lt;a class="" href="https://www.hover.com/manage/hovers" rel="nofollow"&gt;Tocows.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;If you use them, then if we ever move to a different servers, you should be able to access the same information. Also, once you type them once in your browser, your browser will quickly be able to recall these pages as you type the first few letters.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>UmpleOnline modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/UmpleOnline/" rel="alternate"/><published>2017-12-28T16:00:18.927000Z</published><updated>2017-12-28T16:00:18.927000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.net9b6be99674448dd4fd5ab691f88f79b6b7e097f6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;h1 id="umple-online"&gt;Umple Online&lt;/h1&gt;
&lt;p&gt;Umple Online is the online tool for using Umple! &lt;a class="" href="http://try.umple.org" rel="nofollow"&gt;Try it!&lt;/a&gt;. You can edit Umple textual code and see a class diagram appear, or you can edit the class diagram and see the Umple text edited automatically on the screen. You can also generate code.&lt;/p&gt;
&lt;h2 id="user-manual"&gt;User manual&lt;/h2&gt;
&lt;p&gt;The best place to find details is the user manual page:&lt;br/&gt;
&lt;a href="http://cruise.site.uottawa.ca/umple/UsingUmpleOnline.html" rel="nofollow"&gt;http://cruise.site.uottawa.ca/umple/UsingUmpleOnline.html&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="local-setup"&gt;Local setup&lt;/h2&gt;
&lt;p&gt;To set up UmpleOnline in your own environment, look at the following page: &lt;a class="" href="https://github.com/umple/umple/wiki/SettingUpLocalUmpleOnlineWebServer" rel="nofollow"&gt;SettingUpLocalUmpleOnlineWebServer&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="source"&gt;Source&lt;/h2&gt;
&lt;p&gt;UmpleOnline is written mostly in PHP and JavaScript. It can be found in &lt;a class="" href="https://github.com/umple/umple/tree/master/umpleonline" rel="nofollow"&gt;umpleonline/&lt;/a&gt;. Most code is found in the &lt;a class="" href="https://github.com/umple/umple/tree/master/umpleonline/scripts" rel="nofollow"&gt;scripts/&lt;/a&gt; subdirectory.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Umple Docker Container modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/Umple%2520Docker%2520Container/" rel="alternate"/><published>2017-12-28T16:00:18.864000Z</published><updated>2017-12-28T16:00:18.864000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.net62e66e588cb55f61d56558d749985f02c8fe4ea8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This work is experimental.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://hub.docker.com/u/umple/dashboard/" rel="nofollow"&gt;https://hub.docker.com/u/umple/dashboard/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We have a umpleops for generating an umple image which could be used to setup the full umple stack with a "one-click" like approach once docker is installed.  This is very new, and still in the working stages.&lt;/p&gt;
&lt;p&gt;Here is how to launch the latest version.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;mkdir ~/src &amp;amp;&amp;amp; cd ~/src &amp;amp;&amp;amp;  git clone git@github.com:umple/umple.git
docker run -i -t -v `pwd`:/src umple/umple:0.4.0 bash
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;You can skip the first step if you already have umple cloned on your system, and if so, just change &lt;code&gt;pwd&lt;/code&gt; to align with your src directory (the parent dir of umple, NOT umple itself).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>UCOSPLogVictoriaLacroix modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/UCOSPLogVictoriaLacroix/" rel="alternate"/><published>2017-12-28T16:00:18.563000Z</published><updated>2017-12-28T16:00:18.563000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.netca89f7867f3b6c80a3574b19f64034a1822a54d8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Each UCOSP participant is asked to log all the steps they take as they make progress through the semester. This includes difficulties they faced (getting set up, understanding how to model in Umple, using UmpleOnline, code that is difficult to figure out, and development tools that are hard to figure out, or don't seem to work properly). The more log entries added the more we can better get a grip on the usability issues with Umple, and the more we can help future new contributors come up to speed.&lt;/p&gt;
&lt;p&gt;Please record entries in reverse chronological order&lt;/p&gt;
&lt;h1 id="log-entries"&gt;Log Entries&lt;/h1&gt;
&lt;h2 id="date"&gt;Date&lt;/h2&gt;
&lt;h3 id="feb-28-2016"&gt;Feb 28, 2016&lt;/h3&gt;
&lt;p&gt;It's been a frustrating few days for me. As I write this, Orionhub is currently down. Foolishly thinking that a web development service would stay up as long as I needed it to, I did not archive a copy of the &lt;code&gt;orion.js&lt;/code&gt;, which all orion plugins use. I've unfortunately been set back a few days as just trying to find it has been a total headache. &lt;/p&gt;
&lt;h3 id="feb-18-2016"&gt;Feb 18, 2016&lt;/h3&gt;
&lt;p&gt;Working with large code bases is a very interesting process. More often than not, you'll have a solid core that is easy to understand (in this case - the Umple compiler), but a lot of the times there are minuscule pieces that need some dedicated understanding of their own. UmpleOnline, to me, represents that problem.&lt;/p&gt;
&lt;p&gt;When it comes to implementing a compilation process in Orion, I had several options available to me. The most appealing to me was to connect the Orion plugin directly to the compiler that's already a part of UmpleOnline using GET requests on &lt;code&gt;compiler.php&lt;/code&gt;, which is a script in the aforementioned app. This provides the advantages of being ready-made (as it's already existing and working), and a nice central source for code compilation. Plus, Orion was made to work with AJAX-like techniques for getting data around. The problem with understanding this effectively came to breaking down how UmpleOnline compiles Umple models, recreating it minimally in Telnet, and then implementing that in the plugin proper. Telnet might seem like a strange choice but at least it guarantees a sort of minimalism with my implementation, and I do enjoy the tinkering process.&lt;/p&gt;
&lt;p&gt;While I'm still in the process of ironing out the kinks on the Orion side of things, I'm definitely well on the way to connecting the compiler to Orion. Soon, Orion will be a proper (if still very minimal) environment for developing Umple code.&lt;/p&gt;
&lt;h3 id="feb-7-2016"&gt;Feb 7, 2016&lt;/h3&gt;
&lt;p&gt;Not much done of relevance for future work - most of the week was spent trying to understand textmate syntax and correctly implement it into Eclipse Orion.&lt;/p&gt;
&lt;p&gt;While not strictly related to the Umple project itself, Orion's weirdness with loading plugins is just bad when you're developing said plugin. Essentially, any plugin needs to be hosted on an HTTP server to be loaded into Orion. It guarantees that plugins are loaded in a fashion where users can know where they come from, but really causes problems when it comes to developing in a low-power environment (i.e a laptop from 2011). Installing nginx and copying the plugin to the server's document root solved the issue, but developing the plugin on a laptop that gets stressed easily is not favorable - and this does not even factor the fact that Orion is also running it's own all-in-one server.&lt;/p&gt;
&lt;p&gt;Gripes aside, I've now got a basic highlighter going for UmpleOrion. Keywords, brace matching, comments, numbers and strings are all syntactically highlighted in Orion. The next step is recognizing and highlighting extra code for Java, C++ and PHP, which will require some more advanced usage of the Javascript regular expression recognition.&lt;/p&gt;
&lt;p&gt;Preliminary implementations provide some roadblocks with this. For instance&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;// start Java extra code
Java
{

:::Java
    public void someMethod()
    {

        // some code

    } // This brace registers as the closing brace for Java syntax, which means...

    // This is only highlighted as umple code.
    public int someInt;
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;The above example is really problematic when it comes to an easy solution to highlighting extra code properly. There is an implementation (like UmpleOnline's) that simply import's Orion's existing grammars for Java and C++ but that is less that ideal. If I cannot find a solution, then I'll leave the current result as-is for the plugin's development this term.&lt;/p&gt;
&lt;p&gt;Next up though? Compiling and then eventually running Umple code in Orion.&lt;/p&gt;
&lt;h3 id="feb-1-2016"&gt;Feb 1, 2016&lt;/h3&gt;
&lt;p&gt;Not much progress done in terms of getting something concrete put out. I've been assigned the task of writing a plugin for Eclipse Orion with the goal of eventually replacing UmpleOnline. I'm going to use the tentative name of UmpleOrion for the plugin (because it sounds like UmpleOnline, which it will replace). The Orion approach gives quite a few benefits, including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Existing support for many highlighters (Java, C++, etc...) which can be used for extra code in Umple&lt;/li&gt;
&lt;li&gt;Git support&lt;/li&gt;
&lt;li&gt;Runs projects as web applications&lt;/li&gt;
&lt;li&gt;Simple plugin API in Javascript&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;UmpleOrion would provide a full environment to develop software in Umple, supporting many languages. Ideally, (although this may not be possible on the Cruise server) UmpleOrion would also provide compilers for Java and C++ code, and interpreters for other code to allow the user to fully run their Umple code on the server directly. My goals for the term are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Provide syntax highlight for textual Umple models and extra code of other languages.&lt;/li&gt;
&lt;li&gt;Allow the user to compile Umple code to all the usual suspects (Java, etc)&lt;/li&gt;
&lt;li&gt;Allow the user to generate a visual model from their Umple code (much like how Orion does by default with Markdown)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Syntax highlight (for Umple at least) should be trivial as Orion uses TextMate syntax, which is very well-documented. Compilation would require a local instance of the compiler, which again is no problem. As a nice side effect, compilation would add the resulting files to the users' project directories, allowing them to see the results and not have them disappear. Visual models will be a little trickier but emulating UmpleOnline's behaviour should get that done.&lt;/p&gt;
&lt;h3 id="jan-21-26-2016"&gt;Jan 21-26, 2016&lt;/h3&gt;
&lt;p&gt;Would've been done sooner, if it wasn't for a pesky hackathon.&lt;/p&gt;
&lt;h4 id="issue-680"&gt;Issue 680&lt;/h4&gt;
&lt;h4 id="summary"&gt;Summary&lt;/h4&gt;
&lt;p&gt;Injection of code before/after other methods in classes only injects into the first listed method.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;Integer&lt;/span&gt; &lt;span class="nx"&gt;x&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nx"&gt;Integer&lt;/span&gt; &lt;span class="nx"&gt;y&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nx"&gt;before&lt;/span&gt; &lt;span class="nx"&gt;setX&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nx"&gt;setY&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;//this an injected code; &lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="nx"&gt;after&lt;/span&gt; &lt;span class="nx"&gt;setX&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nx"&gt;setY&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;//this another injected code; &lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;Only setX() has code injected before or after it.&lt;/p&gt;
&lt;h4 id="searching"&gt;Searching&lt;/h4&gt;
&lt;p&gt;My first clue was UmpleInternalParser_CodeClass.ump:2560. The method analyses injected code, but only injects the first method.&lt;/p&gt;
&lt;p&gt;This method uses a StringBuilder to build the proper token, never passes it into the CodeInjection constructor. Easy fix!&lt;/p&gt;
&lt;h3 id="jan-15-16-2016"&gt;Jan 15-16, 2016&lt;/h3&gt;
&lt;h4 id="issue-summary"&gt;Issue summary&lt;/h4&gt;
&lt;p&gt;Issue &lt;span&gt;[#608]&lt;/span&gt; is that Umple doesn't quite properly handle abstract classes.&lt;/p&gt;
&lt;p&gt;If an abstract class implements an interface, then Umple will incorrectly create&lt;br/&gt;
a default implementation of methods from the interface, even though it should&lt;br/&gt;
only do so for non-abstract child classes.&lt;/p&gt;
&lt;h4 id="example-code"&gt;Example Code&lt;/h4&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;interface&lt;/span&gt; &lt;span class="nx"&gt;I&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;Integer&lt;/span&gt; &lt;span class="nx"&gt;I1&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;isA&lt;/span&gt; &lt;span class="nx"&gt;I&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;B&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kr"&gt;abstract&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nx"&gt;isA&lt;/span&gt; &lt;span class="nx"&gt;I&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;C&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;isA&lt;/span&gt; &lt;span class="nx"&gt;B&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;Even though B is abstract, Umple will still create a default method for I1() in&lt;br/&gt;
B. This should be fixed so that Umple only implements default methods for&lt;br/&gt;
non-abstract, non-interface classes.&lt;/p&gt;
&lt;h4 id="observations"&gt;Observations&lt;/h4&gt;
&lt;p&gt;Points of interest are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;/cruise.umple/src/UmpleInternalParser_CodeClass.ump:1321&lt;/li&gt;
&lt;li&gt;/cruise.umple/src/Umple_Code.ump:1286&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Adding an abstract check to the third one prevented the method from being&lt;br/&gt;
default implemented, but it does not properly implement in the C class.&lt;br/&gt;
Progress!&lt;/p&gt;
&lt;p&gt;After a night of rest, I've reexamined the code and realized that when&lt;br/&gt;
generating methods for Interfaces, Umple does not recursively check the&lt;br/&gt;
interfaces of the parent (extends) class. This is fine when you have no abstract&lt;br/&gt;
class, but because we have classes explicitly not implementing methods from&lt;br/&gt;
parent interfaces, a class needs to check for unimplemented methods from every&lt;br/&gt;
interface in it's lineage. All one needs is a method to check all&lt;br/&gt;
the parent class' interfaces.&lt;/p&gt;
&lt;p&gt;Another problem that came up with this approach however was that Complex&lt;br/&gt;
Inheritance and Cyclical Inheritance would completely fail, as the original&lt;br/&gt;
method would not track how far down in a chain it was. All that's needed is to&lt;br/&gt;
have a list of already traversed classes &lt;/p&gt;
&lt;h4 id="work-summary"&gt;Work Summary&lt;/h4&gt;
&lt;p&gt;This issue had problems in two places:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Methods from an interface would always implement into a class, even if was&lt;br/&gt;
  abstract. Now if a class is abstract, methods will not automatically&lt;br/&gt;
  implement.&lt;/li&gt;
&lt;li&gt;Due to the previous assumption, classes would only auto-generate interface&lt;br/&gt;
  methods from direct parent interfaces, under the assumting that interfaces in&lt;br/&gt;
  parent classes always received their own default implementation. Now,&lt;br/&gt;
  interfaces are checked through the whole lineage, and end up only being&lt;br/&gt;
  implemented in the first non-abstract classes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="jan-4-2016"&gt;Jan 4, 2016&lt;/h3&gt;
&lt;p&gt;Day 1 of the UCOSP term. I've read up some of the Metamodel for the Umple project. Unsurprisingly, it is &lt;em&gt;very&lt;/em&gt; extensive. I'll definitely continue reading it into the week.&lt;/p&gt;
&lt;h3 id="dec-31-2015"&gt;Dec 31, 2015&lt;/h3&gt;
&lt;p&gt;I've locally cloned the Umple repository in anticipation of the upcoming UCOSP term. Using JDK8 and Ant, Umple built without a hitch and I've added the helper binaries (in the dev-tools directory) to my PATH. A small test compile of an .ump file returned some java code, which then successfully compiled to .class files. I've opted out of setting up an IDE for this project as I prefer to work with ViM and command-line tools for speed.&lt;/p&gt;
&lt;p&gt;I tested some of what Umple could do by very slightly "Umplifying" a side project for fun that I've been working on. I'm really into the approach that Umple takes with code generation - it's designed as a sort-of replacement for code, as it is not recommended to edit the generated code even if it's not been compiled to a binary. I'm considering porting more of that side project to Umple in my spare time. A video game in UML would be a sight to behold indeed.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>UCOSPLogTylerLaporte modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/UCOSPLogTylerLaporte/" rel="alternate"/><published>2017-12-28T16:00:18.439000Z</published><updated>2017-12-28T16:00:18.439000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.net760b6c9e77bb25bc8225f36ad9bafc5e59b89137</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Each UCOSP participant is asked to log all the steps they take as they make progress through the semester. This includes difficulties they faced (getting set up, understanding how to model in Umple, using UmpleOnline, code that is difficult to figure out, and development tools that are hard to figure out, or don't seem to work properly). The more log entries added the more we can better get a grip on the usability issues with Umple, and the more we can help future new contributors come up to speed.&lt;/p&gt;
&lt;p&gt;Please record entries in reverse chronological order&lt;/p&gt;
&lt;h1 id="log-entries"&gt;Log Entries&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;12/19/16 - Ran into several issues as I continued to test my code for issue 760. Resolved them all and it's now functioning as I want.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Now there is logic to check if guards are equivalent or not. It will do most basic comparison between the guards. For example, two guards like &lt;span&gt;[(x + y) &amp;lt; z]&lt;/span&gt; and &lt;span&gt;[z &amp;gt;= (y+x)]&lt;/span&gt; would be confirmed as equivalent. However, some equivalent guards will not be deems equivalent. For example: &lt;span&gt;[(2+5) &amp;gt; 5]&lt;/span&gt; and &lt;span&gt;[7 &amp;gt; 5]&lt;/span&gt; would not be resolved. Also correctly applies negation and deals with parenthesis. For example, &lt;span&gt;[ ((a &amp;gt; b) || (variable &amp;amp;&amp;amp; (!(b &amp;gt;= a) &amp;amp;&amp;amp; (c &amp;lt; b))))]&lt;/span&gt; and &lt;span&gt;[ (((!(b &amp;gt;= c) &amp;amp;&amp;amp; (b &amp;gt;= a)) &amp;amp;&amp;amp; variable) || (a &amp;gt; b))]&lt;/span&gt; would be equivalent. For more examples, refer to the test equivalentGuards.ump (cruise.umple/test/cruise/umple/statemachine/implementation/equivalentGuards.ump)&lt;/p&gt;
&lt;p&gt;Creating pull request now.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;12/19/16 - Finishing the work I did for issue 760. Trying to submit a pull request close to noon.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;12/18/16 - Had several Christmas familial obligations I had to do. &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;12/17/16 - Continued working on issue 760. Discovered that my previous method was a little too specific for numerical expressions and the guards could be a more complicated that I initially thought. Basically started from scratch and created a more generic recursive method that compares the guards. I got it mostly working -- I had difficulty getting it to work properly with the constraintBodys (parenthesis) and negation. I didn't break any current tests, but I need to do more testing to see that it functions as it should.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Then I just need to add a bit of logic to get it to work for stateMachineExpr's and associationExpr's. Then add some tests. &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;12/16/16 - Worked on issue 760. Made a recursive method that would check for equivalent expressions. I got it working for all the numerical expressions. Confirmed that all I didn't break any tests.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Once my pull request for issue 766 was merged, created a pull request for the test updates mentioned below.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;12/15/16 - Worked on issue 766. Made it so it adds the exit code even on self transition. Instead of changing the existing exit code to add it to self transitions, I added an additional condition. When I just changed the existing code, it ended up affecting a bunch of different scenarios. Confirmed that it was working, created tests, and made a pull request.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Added tests for issue 789. Fixed the umple test class that was related to issue 886 and pushed.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;12/13/16 - Continued working on issue 908. Discovered that my changes were being overwritten. Found out the the grammar file I edited just gets overwritten from the grammar files in cruise.umple/src/ when running a build. Updated that file instead, and confirmed that all unit tests were still working. Created new tests and created a pull request for this ticket.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Looked into issue 886. I didn't think there was actually an issue here. I was right, and it turned out that the code sample in the ticket was what was incorrect.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;12/12/16 - Worked on issue 908. After debugging, found out that I just needed to update the grammar file. Changed the regex for the number literal to check for negative numbers as well. Ran the tests and confirmed that I didn't break anything.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;12/06/2016 - Pushed changes for 883. When I did this, I accidentally merged these changes with the fix for issue 819. Added test cases for issue 819. Created a single pull request for both issues. &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;12/05/2016 - Fixed issue 883. Made it so it only added the Null state when it didn't already have a Null state. Added test to testbed that checked if the java files would now compile and added tests for when one class extended a class with a nested state machine and another test for when multiple classes extended a class with a nested state machine&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;12/03/2016 - Started looking into issue 883. First I looked at the point where the “Null”s were being added and found out that the model at this point had extra an extra Null state. Found out this was only happening for when a class extended a class that had a nested state machine. This is because it would call prepare(UmpleClass uClass) on the class that had the nested state machine more than once, and it would add a Null state for each time it was called.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;11/30/2016 - Wrote up logs for previous week’s work&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;11/25/2016&lt;br/&gt;
 Continued working on issue 766. I scrapped all of my changes and started from square one. I ended up wasting a lot of time trying to find a different solution for this issue. I found out why my original change ended up breaking it. For nested states, it would end up determining that one of the parent states were exitable. And since I removed the isSameState check (this would check if the states were identical, or if they belonged to the same parent states), it would add in unnecessary exits from the parent states.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This also led me to discover an additional issue with nested state machines. When the nested state and the parent of the nested state both have exit code, only the nested state’s exit code is called when a transition causes a change in both the nested state and the parent state. I’m probably not being too clear here so I’ll give an example.&lt;br/&gt;
In this example, when flup is called and the transition exits both MotorIdle and StatusOn, only execute_exit_code_nestedState() is called when both execute_exit_code_nested_State() and execute_exit_code_parent() should be called.&lt;/p&gt;
&lt;p&gt;I then tried to look through the entry code to determine if I could find a way to solve both of these issues. I didn’t make any significant headway, and I’m still at a loss with how to fix these issues. I need to spend more time trying to figure it out.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;11/24/2016&lt;br/&gt;
 Continued working on issue 766. I finished updated all the tests and it seemed like something was off with my change. I had a feeling this was the case when I was updating some of the earlier tests, but it was all but confirmed when I updated one of the tests in the TestBed. My change had broken the functionality of parallel state machines. I posted on the issue and talked to Vahdat about it. Turns out my change was just completely off. It was adding a bunch of exit code when it shouldn’t have.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Also talked to Vahdat about issue 819. Beforehand, I had debugged it and it seemed to me like the issue was when it was analyzing the guard token. I wanted to make sure I was looking in the right area because the analyze token method was a little convoluted for me, so I wanted to make sure that was the right place to fix this issue before going forward. However, I had lost the location for this analyze token method because I had debugged it a while ago (turns out there’s a bookmark feature in Eclipse that I will use from now on). We debugged it together and were on the track to getting to the same conclusion (that the issue was with analyzing the token), but I had to leave to drive my mother to a doctor’s appointment. Later that night I saw that Vahdat finished looking into the issue and pushed a solution to it in branch issue819. &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;11/23/2016 - Worked on issue 766. I removed logic that would exclude exit code on self-transitions. Many tests started failing and I started to update them.&lt;br/&gt;
Failing test cases:&lt;br/&gt;
cruise.umple.statemachine.implementation.StateMachineTest&lt;br/&gt;
cruise.umple.statemachine.implementation.java.JavaStateMachineTemplateTest&lt;br/&gt;
cruise.umple.tracer.implementation.java.JavaConsoleTracerTest&lt;br/&gt;
cruise.umple.tracer.implementation.java.JavaFileTracerTest&lt;br/&gt;
cruise.umple.tracer.implementation.java.JavaStringTracerTest&lt;br/&gt;
cruise.statemachine.test.ConcurrentStateMachineTest&lt;br/&gt;
cruise.statemachine.test.FinalStateTest&lt;br/&gt;
cruise.tracer.test.ConsoleTracerStateMachineTest&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;10/25/2016 - Finished fixing issue 796. Added logic to remove the comparison true/false values. Created pull request and the builds have passed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;10/25/2016 - Looked at it with fresh eyes this morning corrected the fix. Now all tests are passing. Just need to update unit tests now.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;10/24/2016 - Found the problem for 796 and implemented a fix. I now have a test failing. Figured out why it's failing and now I need to revise my fix.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;10/23/2016 - Started looking into issue 796. Replicated the issue locally and beginning to debug to find the cause.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;10/12/2016 - One of the builds failed when I pushed my changes for issue 767. Not clear on why, or what the difference is between the 4 builds that get executed when making a pull request.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;10/12/2016 - Finished issue 767.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I was having an issue with it working in Eclipse. A lot of files weren't being recognized even though they existed. I tried doing a first build / full build multiple times, but I still had a bunch of these errors. Turns out I just had to refresh the cruise.umple package. I was refreshing with File --&amp;gt; Refresh but it didn't work until I right clicked cruise.umple and hit refresh.&lt;/p&gt;
&lt;p&gt;Added a couple test cases for this scenario. I was having difficulty getting the test cases to work before, but I was able to get them working properly today. Turns out running them in Eclipse is helpful...&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;10/10/2016 - Looked through state machine bugs and came up with a short list of issues I might work on. 886, 819, 870, 883, 789, 766, 760, 796&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;10/4/2016 - Decided in group meeting to focus on several very high/high priority state machine issues throughout the term.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;9/24/2016 - Continued working on issue 767. Found and fixed the issues in the Java generator and began to update unit tests. Made my own branch and started a pull request. There were some errors that I need to look into.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;9/23/2016 - Started work on my first ticket, issue 767. Looked through the code to try to understand what was going on. Learned how to run and debug Umple in eclipse.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;9/23/2016 - Downloaded a different version of Eclipse and got it and the plugin working properly.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;9/22/2016 - Started to setup the project in Eclipse and get the plugin working. Was having weird issues with many classes not being recognized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;9/20/2016 - Got full build working once mirroservice.org came back up&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;9/20/2016 - Started to set up dev environment. Ran into an external dependency issue when trying to run the first build. Issue fetching org.eclsipse.cdt.core_5.5.0.jar because mirrorservice.org is currently down.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="date"&gt;Date&lt;/h2&gt;&lt;/div&gt;</summary></entry><entry><title>UCOSPLogShikibMehri modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/UCOSPLogShikibMehri/" rel="alternate"/><published>2017-12-28T16:00:18.112000Z</published><updated>2017-12-28T16:00:18.112000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.net2df9e1cb7c3103d0f7b64f9635f907bd9c4b5484</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;h1 id="ucosp-log-entries-for-shikib-mehri"&gt;UCOSP log entries for Shikib Mehri&lt;/h1&gt;
&lt;p&gt;Each UCOSP participant is asked to log all the steps they take as they make progress through the semester. This includes difficulties they faced (getting set up, understanding how to model in Umple, using UmpleOnline, code that is difficult to figure out, and development tools that are hard to figure out, or don't seem to work properly). The more log entries added the more we can better get a grip on the usability issues with Umple, and the more we can help future new contributors come up to speed.&lt;/p&gt;
&lt;p&gt;Please record entries in reverse chronological order&lt;/p&gt;
&lt;h1 id="log-entries"&gt;Log Entries&lt;/h1&gt;
&lt;h3 id="apr-10-2016"&gt;Apr 10, 2016&lt;/h3&gt;
&lt;p&gt;I finished dealing with issue &lt;span&gt;[#803]&lt;/span&gt;. I managed to preserve the ability to specify Ruby code injections in the same format as before (as well as the typical Umple camel case format) while making code injections case sensitive.&lt;/p&gt;
&lt;p&gt;I also moved the functionality for custom code injections and injection with parameters to work for Ruby/Php as well.&lt;/p&gt;
&lt;p&gt;The only thing I have left to do now is to write a few examples for the Umple manual that demonstrate my changes. However if any issues arise with my pull requests, I'm available for the next week to fix them.&lt;/p&gt;
&lt;h3 id="apr-3-2016"&gt;Apr 3, 2016&lt;/h3&gt;
&lt;p&gt;I finished dealing with issue &lt;span&gt;[#804]&lt;/span&gt;. There are is now warning 1013 printed whenever parameters are specified for injections into generated methods.&lt;/p&gt;
&lt;p&gt;I'm currently waiting on Tim/Vahdat's comment on issue &lt;span&gt;[#803]&lt;/span&gt;. I'm not sure if making code injections case sensitive is the best decision for Umple. I presented two options in the issue.&lt;/p&gt;
&lt;h3 id="mar-28-2016"&gt;Mar 28, 2016&lt;/h3&gt;
&lt;p&gt;I haven't posted a log entry for a while -- as this has been a busy week. I did work on Umple all day today and got quite a bit done. I have working functionality that allows me to target code injections at specific methods based on their parameters.&lt;/p&gt;
&lt;p&gt;I've copy pasted the examples from my pull request below:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;void&lt;/span&gt; &lt;span class="nx"&gt;foo&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;String&lt;/span&gt; &lt;span class="nx"&gt;a&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="p"&gt;[...]&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;

  &lt;span class="k"&gt;void&lt;/span&gt; &lt;span class="nx"&gt;foo&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kr"&gt;int&lt;/span&gt; &lt;span class="nx"&gt;a&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="p"&gt;[..]&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;You can now specify the parameters in certain ways to target those methods specifically:&lt;/p&gt;
&lt;p&gt;If you want to inject into the first method and only the first method:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;before custom foo(String) {
  [...]
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;Or if you want to inject only into the second method:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;before custom foo(int) {
  [...]
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;Or if you want to inject into both:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;before custom foo(...) {
  [...]
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;This also injects into both (if parameters unspecified -- it is presumed that you don't care about them):&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;before custom foo {
  [...]
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;You can also just use multiple code injections on the same line and specify parameters for all of them:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;before custom foo(int),foo(String) {
  [...]
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;In terms of what I did with regards to testing (again copy pasted from PR):&lt;/p&gt;
&lt;p&gt;Cleaned up some of the tests that needed to be changed (for minor and justifiable reasons) due to my changes to the grammar. Added in new test files to test this functionality -- covering all of the examples that I mentioned above.&lt;/p&gt;
&lt;p&gt;At this point in time what I've finished is only targeted at custom code injections. This was mostly out of choice -- because we definitely want this functionality for custom code injections -- but I'm not sure how useful it would be for injections into generated methods. If, Tim/Vahdat think it is important to include for those two, I'll just have to hunt down every call to &lt;code&gt;getApplicableCodeInjections&lt;/code&gt; and change the parameters to it and pass in the method parameters as well as the name.&lt;/p&gt;
&lt;p&gt;As long as the PR is accepted (waiting on the CI right now), all I need to do over the remaining two weeks is make my implementation work with other languages (cpp/ruby/php is all I need to do to the best of my knowledge). &lt;/p&gt;
&lt;p&gt;I expect cpp to be straightforward given the code for Java. I don't think ruby will be a problem (I'm familiar with Python, and expect ruby to be mostly similar). I'm a bit worried about PHP as I've never used it and I'm not too familiar with the syntax -- but I should be able to figure it out over the course of two weeks.&lt;/p&gt;
&lt;h3 id="mar-19-2016"&gt;Mar 19, 2016&lt;/h3&gt;
&lt;p&gt;Since my last post, I fixed the issue with the codeLang. I did this by explicitly saying in the grammar that the operationSource must be one of "custom"/"all"/"generated". This led to a successful test pass.&lt;/p&gt;
&lt;p&gt;I modified tests I had written earlier and added new ones. I've now updated the pull request with the new tests and all of the latest code. If it passes (I think it most likely will), it means the pull request is ready to go through as all of the changes are now working.&lt;/p&gt;
&lt;h3 id="mar-18-2016"&gt;Mar 18, 2016&lt;/h3&gt;
&lt;p&gt;I've fixed the main issue that's been holding me back. When writing the code, I made the assumption that all code injections would go through the process of being parsed (at which point the injections with unspecified source would have their operationSource set to be "generated"), however this isn't the case and there are many CodeInjections created programatically. This was a simple fix and it led to the majority of the failing tests to pass.&lt;/p&gt;
&lt;p&gt;Right now, I'm dealing with one more issue. This is an issue that occurs when the codeLang is specified in the injection. I'm not 100% sure what is going on right now -- but my preliminary observations lead me to believe that the operationSource is being set to be the value of the operationName and the operationName is being set to be the codeLang.&lt;/p&gt;
&lt;p&gt;I will look more into this tonight, and ask Tim/Vahdat, if I'm unable to figure it out soon.&lt;/p&gt;
&lt;h3 id="mar-17-2016"&gt;Mar 17, 2016&lt;/h3&gt;
&lt;p&gt;I added the grammar code and parsing code to implement the ability to differentiate between code injections into custom/generated/all methods. What I essentially had was a working implementation of code injections into custom/generated/all methods, that worked locally.&lt;/p&gt;
&lt;p&gt;Yesterday, I pushed my code to my repo, but noticed that it failed integration tests on my open pull request. Since then, I've been trying to figure out why the build is failing. &lt;/p&gt;
&lt;p&gt;I've been trying to backtrack my code until I determine what exactly is making the build fail. It seems like it's most likely an issue with the changes to the grammar. The thing that is making it super difficult to debug is the fact that the &lt;code&gt;/umple/dist/qa/cruise.umple/all-tests.html&lt;/code&gt; page isn't showing any failures -- even though the build says that the &lt;code&gt;cruise.patterns.test.CodeInjectionTest FAILED&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="mar-14-2016"&gt;Mar 14, 2016&lt;/h3&gt;
&lt;p&gt;This week, I've fixed the issue I've been dealing with for the past while. The way I did this is by calling a separate method to identify applicable code injections for custom methods. The applicable code injections were initially an empty list. After doing a first build (this is important to get rid of generated code) and then a full build, this fixed the issues I was having.&lt;/p&gt;
&lt;p&gt;Now what I've done is change the method so that it will only identify code injection as being applicable to custom defined methods if they have a tilde at the end of them. For example:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;void setFoo() {
  // test
}

after setFoo {
  // test2
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;will not inject anything. However the following will inject:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;void setFoo() {
  // test
}

after setFoo~ {
  // test2
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;This syntax won't reflect the final syntax, I'm just experimenting with how to do this. I will be discussing the syntax with Tim and Vahdat throughout this week.&lt;/p&gt;
&lt;h3 id="mar-6-2016"&gt;Mar 6, 2016&lt;/h3&gt;
&lt;p&gt;Dealing with this bug has been difficult to say the least. I think there are some fatal flaws in my understanding of how Umple gets built. Unfortunately, I'm still not 100% sure of how it does get built, but I now know the reason my bug occurs.&lt;/p&gt;
&lt;p&gt;Vahdat helped me figure this out (although I didn't realize at the time that the bug he pointed out was almost identical to the one I was dealing with). The problem stems from the fact that Umple developers have used code injections with the assumption that no code would be injected into custom defined methods.&lt;/p&gt;
&lt;p&gt;However, with my changes this is no longer the case. Meaning that a lot of existing code is going to have issues. The solution, as explained to me by Vahdat, is to finish the parameter specification code for code injections before expecting my code to work. Thus, I will immediately start working on that.&lt;/p&gt;
&lt;p&gt;The reason that this bug was so difficult to figure out, was that the build would occasionally pass. My understanding of this is extremely weak, but it seems like you need to do two full builds consecutively to see this issue. &lt;/p&gt;
&lt;p&gt;My plan for the upcoming week is to finish implementing the code injection with parameter specification. I've been thinking about this for the past week, so I have a reasonable understanding of how to do this. &lt;/p&gt;
&lt;h3 id="mar-3-2016"&gt;Mar 3, 2016&lt;/h3&gt;
&lt;p&gt;I'm still dealing with the build issue. I have zero clue where the incorrect (referencing variables that are not defined) Java code is coming from. I'm pushing a change that Tim proposed (replacing all "\n"s with System.lineSeparator()). It doesn't seem like this is the issue, because even after I fixed this, the build failure persisted.&lt;/p&gt;
&lt;p&gt;Vahdat offered to take a look at the failing build, so I will contact him and see if he can help me figure out what's going on here.&lt;/p&gt;
&lt;p&gt;I've also spent some time looking over the code and thinking about how to do the next part of my task -- which is specifying parameters in code injections (i.e., inject into method foo with parameters (int, string) but don't touch the method foo with parameters (int, int)). This seems fairly simple to do. I'll just need to change the parsing a bit to update what an injection token looks like, modify the method that matches a method name to methods to allow it to take in parameters and allow passing in of parameters from the code generator side (i.e., when the requests for the relevant code injections are made). &lt;/p&gt;
&lt;p&gt;I will get straight to work on the next feature (and I think my last big one) as soon as I resolve the build issue that's occurring at the moment.&lt;/p&gt;
&lt;h3 id="feb-21-2016"&gt;Feb 21, 2016&lt;/h3&gt;
&lt;p&gt;I haven't updated my log page in a while -- as over the past two weeks I've been in a perpetual cycle of almost finishing the feature that I was working on (meaning I've been wanting to delay my log update until that was done). Since my last log post, I submitted a pull request consisting of my finished implementation of warnings being thrown for attempted code injections into non-existent methods. The pull request was approved and the task was marked to be complete.&lt;/p&gt;
&lt;p&gt;Since then I've been working on implementing code-injections into user-defined methods. I initially thought this would be fairly straight-forward. For before injections, it is in fact straight forward, you simply inject the code at the start of the method. However, for after injections, there are a lot of edge cases that needed to be considered.&lt;/p&gt;
&lt;p&gt;The way I handled after injections was to place the code before every return. However, this led to problems in the situation where you have code like:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;if(test)
  return b;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;Because the if-statement is written to only handle a single line in its body. This meant I had to write code to detect the existence of such a situation and deal with it appropriately. But ok, that should be easy enough to do... Or so I thought.&lt;/p&gt;
&lt;p&gt;It's a bit more difficult than simply checking one line up to see if it ends in a &lt;code&gt;)&lt;/code&gt;, because comments are an issue:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;if(test)
  // test
  return b;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;The aforementioned strategy would fail on this. But I guess we could ignore all lines that begin with a comment token (&lt;code&gt;//&lt;/code&gt; in Java). Nope:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;if(test)
  /*
    test
  */
  return b;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;This led to me finding some regex to remove all of the comments for me. From there, adding in braces where they needed to be placed was fairly simple.&lt;/p&gt;
&lt;p&gt;It was also a challenge to get indentation to work properly, especially for cases like:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;if(test) return b;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;So, I applied a pre-processing step where I fixed all returns that weren't on their own line. I wrote an Umple file that covered all of the cases I mentioned and generated the corresponding Java file. The generated file looked exactly as I expected it to.&lt;/p&gt;
&lt;p&gt;While I haven't updated my log over the past two weeks, I did participate in a lot of discussion on the issue assigned to me and my pull request. A lot of what I discussed in this log was also covered there: &lt;a href="https://github.com/umple/umple/pull/731" rel="nofollow"&gt;https://github.com/umple/umple/pull/731&lt;/a&gt; and &lt;a href="https://github.com/umple/umple/issues/710." rel="nofollow"&gt;https://github.com/umple/umple/issues/710.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I'm currently getting a build failure. I'm not sure how my code could have caused this though. The build is complaining about faulty Java code -- which seems to have been injected. However, I cannot find any corresponding before/after statement that matches this code, and I'm not sure where it comes from. It also doesn't have the typical comment above it indicating the source in Umple. I only experienced this failure after I merged the most recent Umple commits into my local repo.&lt;/p&gt;
&lt;h3 id="feb-7-2016"&gt;Feb 7, 2016&lt;/h3&gt;
&lt;p&gt;I've gotten most of the tests to pass. I encountered a variety of issues while doing so. Firstly, my Eclipse set up started giving me issues, which required me to reclone my repo and go through the set up process again. Second, I got confused about where to look for information about which tests failed, when building through the command line.&lt;/p&gt;
&lt;p&gt;For future reference (both for me and if anyone ever reads this), test information is located at &lt;code&gt;dist/qa/cruise.umple/all-tests.html&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;At the moment, I've fixed all of the failing tests. Some of the issues were from me not passing a valid position when instantiating an ErrorMessage. There were a number of issues with the tests themselves, including the fact that no UmpleClass was being assigned to AssociationVariables, but one was required to retrieve the singular name of a field. There were a number of issues with my Umple code in the tests, that I resolved.&lt;/p&gt;
&lt;p&gt;I contacted Vahdat about the remaining failing test, which is an issue in UmpleTraitTests. The test is failing because 0 code injections are identified in a piece of Umple code. When I stepped through the execution of the test, it seems like the code injections are being identified, but the count is still 0 in the end. I'm not sure where the passing on of injections happens between a trait and a class, which is why I asked for help.&lt;/p&gt;
&lt;p&gt;This week has been really busy for me -- with a ton of homework and multiple exams. In a week, I'll have no classes and no work for a week, meaning that I'll be able to contribute significantly to Umple during that time. Until then, I have to suffer through midterms and assignments, but I will find time to work on Umple on Wednesday and Friday of the upcoming week.&lt;/p&gt;
&lt;p&gt;My plan is to (after resolving the UmpleTraitsTest issue) work on the issue involving the value for lists not being generated properly and also look into adding injections to user defined methods.&lt;/p&gt;
&lt;h3 id="jan-31-2016"&gt;Jan 31, 2016&lt;/h3&gt;
&lt;p&gt;I put in a solid 6-7 hours of work into working on Umple today and got quite a bit done. I finished solving issue &lt;span&gt;[#646]&lt;/span&gt;, which involved fixing the issues with false-positive warnings. I identified an issue with associations not being identified at the right point. I'm currently at a stage where I'm getting failures that I don't quite understand, and am planning on emailing the mentors about.&lt;/p&gt;
&lt;p&gt;To test to my implementation, I've been using the umple.jar on cruise.umple/src/Master.ump to ensure there are no false positives with my current implementation. At the moment, when I do this I don't see any 1012 errors, which is what I was seeing before.&lt;/p&gt;
&lt;p&gt;I finished dealing with interfaces today which was fairly trivial after figuring out how to deal with classes. I was still left with a few false-positive warnings though, and upon examination I discovered that the following case was not being handled properly:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;B&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;B&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;after&lt;/span&gt; &lt;span class="nx"&gt;setA&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;// TEST&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;Of course, this took me a while to figure out, because it so happened that the false positives all dealt with abstract classes which made me think that those weren't being handled sufficiently. After a while, I realized that that was not the issue and all of the false positives were akin to the class B in the above example.&lt;/p&gt;
&lt;p&gt;After some more examination, I realized that the way that the inline association tokens were handled is as follows: (1) they were added as attributes to the class that they were written in, the opposite of the token (ie. the correct token for the other class) was added to a list of unlinked associations, (2) sometime later, the unlinked associations were taken out of the list and added to the appropriate class.&lt;/p&gt;
&lt;p&gt;HOWEVER, sometime between (1) and (2) is where the code injection tokens were being analysed. Which meant that my code had no access to the association when it needed them.&lt;/p&gt;
&lt;p&gt;I fixed this issue by ensuring that my associations check happened after all of the tokens were loaded and operated on the created code injections rather than the tokens.&lt;/p&gt;
&lt;p&gt;After doing a full build, my code stopped causing false errors on the build of the umple project. I merged the latest commits into my fork and added a few tests. However, when I did a full build (even after doing a first build again), I get failures that I can't figure out the root cause of.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;template.test:
    [junit] WARNING: multiple versions of ant detected in path for junit 
    [junit]          jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/Project.class
    [junit]      and jar:file:/home/shikib/projects/umple/dist/libs/core/ant.jar!/org/apache/tools/ant/Project.class
    [junit] TEST cruise.umple.compiler.UmpleClassTest FAILED
    [junit] TEST cruise.umple.compiler.UmpleParserTracerTest FAILED
    [junit] TEST cruise.umple.tracer.implementation.java.JavaConsoleTracerTest FAILED
    [junit] TEST cruise.umple.tracer.implementation.java.JavaFileTracerTest FAILED
    [junit] TEST cruise.umple.tracer.implementation.java.JavaStringTracerTest FAILED
    [junit] Tests FAILED

compileJava:
     [java] Processing -&amp;gt; testbed/src/TestHarness.ump
     [java] Umple compiler error. Stack trace follows
     [java] To locate the error in the original Umple source, set GeneratedSourcePath to where the generated Java is located:
     [java] e.g. setenv GeneratedSourcePath ~/umple/cruise.umple/src-gen-umple
     [java] Exception java.lang.RuntimeException in
     [java] java.lang.RuntimeException: Unable to create ErrorMessage due to aPosition
     [java]     at cruise.umple.compiler.ErrorMessage.&amp;lt;init&amp;gt;(ErrorMessage.java:42)
     [java]     at cruise.umple.compiler.ErrorMessage.&amp;lt;init&amp;gt;(ErrorMessage.java:134)
     [java]     at cruise.umple.compiler.UmpleInternalParser.checkCodeInjectionValidity(UmpleInternalParser.java:4228)
     [java]     at cruise.umple.compiler.UmpleInternalParser.checkCodeInjections(UmpleInternalParser.java:1978)
     [java]     at cruise.umple.compiler.UmpleInternalParser.postTokenClassAnalysis(UmpleInternalParser.java:1964)
     [java]     at cruise.umple.compiler.UmpleInternalParser.postTokenAnalysis(UmpleInternalParser.java:1271)
     [java]     at cruise.umple.compiler.UmpleInternalParser.analyze(UmpleInternalParser.java:1054)
     [java]     at cruise.umple.compiler.UmpleModel.run(UmpleModel.java:1215)
     [java]     at cruise.umple.UmpleConsoleMain.runConsole(UmpleConsoleMain.java:109)
     [java]     at cruise.umple.UmpleConsoleMain.main(UmpleConsoleMain.java:151)
     [echo] Last Version: 1.23.0-3bd2bc7

BUILD FAILED
/home/shikib/projects/umple/build/build.xml:9: /home/shikib/projects/umple/build/build.xml:29: The following error occurred while executing this line:
/home/shikib/projects/umple/build/build.testbed.xml:251: The following error occurred while executing this line:
/home/shikib/projects/umple/build/build.testbed.xml:68: The following error occurred while executing this line:
/home/shikib/projects/umple/build/build.testbed.xml:77: Java returned: 255
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;I can't figure out why the tests are failing, and will contact Vahdat for assistance with this. My latest code is available at &lt;a class="" href="http://github.com/shikib/umple" rel="nofollow"&gt;my fork&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id="jan-29-2016"&gt;Jan 29, 2016&lt;/h3&gt;
&lt;p&gt;Over the past few days, I've been working on fixing the issue with after/before code injections on methods extended from a super class or inherited from an interface. I currently have an implementation that works on basic cases, such as:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;k&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;B&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;isA&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nx"&gt;after&lt;/span&gt; &lt;span class="nx"&gt;setK&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;// put code here&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;While this caused a warning before, this is no longer the case. I'm also using a BFS traversal type of strategy to ensure that I get all of the extended classes (ie. going back up the chain). This means that cases like this are also successful (in not printing a warning): &lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;k&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;B&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;isA&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;C&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;isA&lt;/span&gt; &lt;span class="nx"&gt;B&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nx"&gt;after&lt;/span&gt; &lt;span class="nx"&gt;setK&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;// put code here&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;I'm currently working on handling interfaces, which shouldn't be much work after having figured out how to deal with extended classes. Once I finish that (hopefully today) and write a few unit tests, I will make a pull request.&lt;/p&gt;
&lt;h3 id="jan-24-2016"&gt;Jan 24, 2016&lt;/h3&gt;
&lt;p&gt;I haven't updated my log page in two weeks now, so this log will include what I did during the 3-day code sprint in Toronto as well as the week after it.&lt;/p&gt;
&lt;p&gt;I was assigned issue &lt;span&gt;[#410]&lt;/span&gt;, which seemed simple at first, but ended up being more complicated than I originally anticipated simply due to the various cases that I needed to handle. Essentially, the core difficulty with this issue is that I need to generate the warnings for the after/before statements at the modelling level -- however the methods aren't generated until after this stage in the JET (if we're compiling to Java).&lt;/p&gt;
&lt;p&gt;This meant that to determine if an after/before statement specified a valid method, I needed to determine all of the methods that would be generated for a given class. My initial for this issue only dealt with methods that would be generated as a result of attributes (both single-valued attributes and lists). &lt;/p&gt;
&lt;p&gt;For example, the following class would generate &lt;code&gt;setA&lt;/code&gt; and &lt;code&gt;getA&lt;/code&gt;:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;a&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;I also needed to handle the various cases of variable modifiers. For example, because of the "internal" modifier, the following class would not have a &lt;code&gt;setA&lt;/code&gt; or a &lt;code&gt;getA&lt;/code&gt; method.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;A&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;internal&lt;/span&gt; &lt;span class="nx"&gt;a&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;Initially the plan was for me to leave the changes in this state, and handle the methods that were created due to associations + state machines after the code sprint. I assigned myself to issue &lt;span&gt;[#689]&lt;/span&gt; and begun working on it. &lt;/p&gt;
&lt;p&gt;I thought that issue &lt;span&gt;[#689]&lt;/span&gt;, might just be due to the code that handled the const modifier being unable to deal with lists and treating a list variable as having the the type of the values it's storing. This was the case, but there seemed to be more with the bug, as removing the const and just assigning a value to a list was leading to issues.&lt;/p&gt;
&lt;p&gt;I didn't get a chance to look further into this issue at the code sprint, because my earlier commit was generating false positives for the Umple build of itself. When I forked the associations part of the method generation into a separate issue, I figured that while there might be false positive errors for after statements on association-generated methods for a while this wouldn't happen too often. What I hadn't realized was that the Umple project itself was full of these cases and that the warning would be printed out every time anyone did a build of Umple.&lt;/p&gt;
&lt;p&gt;I fixed this (in addition to state machines) and got rid of most of the warnings in my full build. One of the biggest challenges of fixing the code was getting the singular name of a variable. This is because in the case of one to many associations what would happen is that we would have a method with the name add&lt;span&gt;[SingularVariableName]&lt;/span&gt; and get&lt;span&gt;[SingularVariableName]&lt;/span&gt;. I had to locate a method somewhere that did this for me.&lt;/p&gt;
&lt;p&gt;However, even my changes, the warnings in the umpleSelf section of the full build persisted. I looked at the first few and figured that they should be working. I manually compiled similar code which generated no errors. Realizing that I was misunderstanding something about the build process, I decided to experiment a bit. &lt;/p&gt;
&lt;p&gt;I manually added the name of the method to my method that identified invalid code injections and threw a warning, in order to have this be ignored. The warning still persisted. I commented out the one location where I was throwing the error, the warning persisted. I completely deleted my warning from the warnings file, yet the error persisted. &lt;/p&gt;
&lt;p&gt;At this point, I realized that every single time a build occurred, a jar would be downloaded from the internet and used to build my project. The JUnit tests would the version of my project that was built using the jar from the internet. &lt;/p&gt;
&lt;p&gt;I had originally assumed that the last jar that was built would be used to build the next jar, however doing it this way would cause a significant number of problems in the situation where someone gets rid of a bunch of the code (say all of the code that compiles to Java). If they create a jar with this code and then re-add all of the Java-compilation code, they'd be unable compile their project to Java and would thus be unable to create a new jar.&lt;/p&gt;
&lt;p&gt;Today, I made a pull request with these changes. Now false-positives warnings are no longer generated for associations and state machines. However, a few of the warnings persisted and upon examination I realized that these were due to umple classes extending other classes. I didn't know that you could call after/before on methods that would be generated by a superclass.&lt;/p&gt;
&lt;p&gt;I now need to figure out a way to get all of the methods from a superclass. I thought that this would be fairly simple to do, however there are issues with getting a superclass for a given class at the modelling level. Tim has suggested I look into work done by Aymen (committed in December), as he dealt with a similar issue.&lt;/p&gt;
&lt;p&gt;I will look into this issue sometime between Monday - Wednesday and aim to finish this for sure by Wednesday.&lt;/p&gt;
&lt;p&gt;To avoid long periods of not working in this project and not updating my log, I am making a personal commitment to work on Umple for a period of at least 1.5 hours (this includes updating my log) every single week on Sunday/Wednesday/Friday.&lt;/p&gt;
&lt;h2 id="date"&gt;Date&lt;/h2&gt;
&lt;h3 id="jan-10-2016"&gt;Jan 10, 2016&lt;/h3&gt;
&lt;p&gt;Over the past few days, I've been working on setting up Umple on my personal computer. I'm running Ubuntu 14.04 which probably made the process significantly smoother than it might be on Windows. I cloned the Umple repository and followed the &lt;a class="" href="https://github.com/umple/umple/wiki/DevelopmentSetUp" rel="nofollow"&gt;development setup guide&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Although I do the majority of my development from the command line with vim, I set up the project in Eclipse anyway as I figured it might come in handy if I run into issues building/running tests from the command line. I ran all of the JUnit tests in cruise.umple and everything passed successfully. &lt;/p&gt;
&lt;p&gt;To ensure that my Umple build worked correctly, I set up a local Umple web server by running &lt;code&gt;php -S localhost:8001&lt;/code&gt; from the umpleonline directory. Initially, I was able to load example Umple code into the text box on the left hand side of the screen -- however neither the class diagram on the right hand side nor the code generation worked successfully. Both the class diagram viewer and the generated code displayed the following error: "Diagram is out of synchronization with the text due to selecting Manual Sync or an error in the text that has caused the to compiler produce no output."&lt;/p&gt;
&lt;p&gt;Running &lt;code&gt;ant -DshouldPackageUmpleOnline=true -Dmyenv=local -f build.umple.xml packageUmpleonline&lt;/code&gt;, which gives UmpleOnline access to the Umple jar files, fixed this issue and I'm able to use my locally hosted UmpleOnline with all of its features.&lt;/p&gt;
&lt;p&gt;I also experimented with generating Java code from a .ump file. I wasn't sure what the best way to do this was, what I did was run &lt;code&gt;java -jar dist/umple.jar helloworld.ump&lt;/code&gt; from my umple directory. The generated Java file matched the code generated by UmpleOnline and seemed to reflect what was in the .ump file (although there was some extra exception handling Java code that I didn't understand the purpose of).&lt;/p&gt;
&lt;p&gt;I tried looking for more documentation on how to generate non-Java code from the command line (as you already can with UmpleOnline), but I was unable to find anything. I will spend more time looking into this later today or tomorrow. I will also try umplifying some of my existing projects to improve my understanding of Umple.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>UCOSPLogRunqingZhang modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/UCOSPLogRunqingZhang/" rel="alternate"/><published>2017-12-28T16:00:17.934000Z</published><updated>2017-12-28T16:00:17.934000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.netb6d238727b5066fb6c3503daa94acbe51fca80b9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;``Each UCOSP participant is asked to log all the steps they take as they make progress through the semester. This includes difficulties they faced (getting set up, understanding how to model in Umple, using UmpleOnline, code that is difficult to figure out, and development tools that are hard to figure out, or don't seem to work properly). The more log entries added the more we can better get a grip on the usability issues with Umple, and the more we can help future new contributors come up to speed.&lt;/p&gt;
&lt;p&gt;Please record entries in reverse chronological order&lt;/p&gt;
&lt;h1 id="log-entries"&gt;Log Entries&lt;/h1&gt;
&lt;h3 id="date"&gt;Date&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;2017-12-15&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; joint.js now has a better interaction for deleting classes, user will need to click on the delete option button to show up the delete "cross" button on the class diagram.&lt;br/&gt;
&lt;/em&gt; delete and edit attribute is working properly.&lt;br/&gt;
&lt;em&gt; improve the interaction when editing attributes&lt;br/&gt;
&lt;/em&gt; photoSync in joint.js now hide all unrelated icons (class icon, edit delete icon)&lt;br/&gt;
&lt;em&gt; fix the problem with paper offset that cause flying class box not right under cursor&lt;br/&gt;
&lt;/em&gt; add new action to umple sync that will allows adding and deleting state transition&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-11-20&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Added feature that joint.js will provide feedback on different mode (which is consistent with the default editing mode).&lt;br/&gt;
&lt;/em&gt; Added a edit icon which enable/disable the text editing on joint.js rendered box. On disable, the whole box is responsible for the joint.js related event (e.g. add association/generalization)&lt;br/&gt;
&lt;em&gt; Fix issues: &lt;br/&gt;
1. joint.js does not render class box properly when attribute and method display is both deselected&lt;br/&gt;
2. joint.js does not update the size of the interactive region when the size of rendered box is update&lt;br/&gt;
3. joint.js does not work properly on some edge cases:&lt;br/&gt;
    1. when click association mode button to disable adding association mode in the middle of adding associations, joint.js graph will stop catching any actions afterwards (same applies to adding generalization)&lt;br/&gt;
    2. switch between different editing mode&lt;/em&gt; Issue going to work on:&lt;br/&gt;
1. make the joint.js rendering generalization properly as well as better editing experience&lt;br/&gt;
2. delete method/attribute icon does not work properly as expected&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-11-13&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Implemented and tested add new and delete transition action of umple sync&lt;br/&gt;
&lt;/em&gt; Start working on new action allows editing states, transition labels&lt;br/&gt;
* After that I will hook those up with umple online and a few UI improvement for JointJS state diagram&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-11-4&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Start improving JointJs State machine&lt;br/&gt;
&lt;/em&gt; Currently I am working on making the JointJs state machine to be a separate option under option list, however, I kind of stuck right now as the event does not hooked to the button.&lt;br/&gt;
* After fixing this issue, I will start implementing new feature that allows modification of JointJs state diagram to update corresponding umple cd=ode &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-11-3&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Added a new feature that after user to modifying the association link &lt;a class="" href="https://github.com/umple/umple/issues/1127" rel="nofollow"&gt;#1127&lt;/a&gt;&lt;br/&gt;
&lt;/em&gt; I am starting working on making JJS diagram fully functional&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-10-30&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Last weekend I fixed the issue that Association failed to removed from code if it is removed from the graph issue &lt;a class="" href="https://github.com/umple/umple/issues/1125" rel="nofollow"&gt;#1125&lt;/a&gt;&lt;br/&gt;
&lt;/em&gt; Fist approach is done by modifying the complier, however it fail some test that expected it works the old way. Thus For consistency, I force the JJs to name association the way compiler is expecting.&lt;br/&gt;
* Now I will focus more on implement the new action that allows modifying association end&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-10-27&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; After some investigation, I found the problem is actually cause by umplesync. In the buggy case described below, the association generate by JointJs graph is &lt;code&gt;NewClass2_NewClass1&lt;/code&gt;, where the parser remove operation is trying to find association with name &lt;code&gt;NewClass1_NewClass2&lt;/code&gt;. This inconsistency will cause the remove operation incorrectly skip the association.&lt;br/&gt;
&lt;/em&gt; Debug will start ASAP&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-10-26&lt;/strong&gt;&lt;br/&gt;
* Further investigation on the problem of deleting association in JointJs, it does not work on a simplest case&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;NewClass1&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;NewClass2&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;NewClass1&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;However, it works correctly on&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;NewClass1&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;NewClass2&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kr"&gt;class&lt;/span&gt; &lt;span class="nx"&gt;NewClass2&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;I think this implies that the error is not really a race condition.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;As discussed in the meeting, I will implement in a new action that modifies association ends after fixing the issue with remove&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;2017-10-23&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; The last week I was experimenting and investigating ways to implementation of allowing user to edit associations in JointJs graph&lt;br/&gt;
&lt;/em&gt; The most proper event to catch is paper.on(link:disconnect) and (link:connect) which will return both old vertices and new vertices as parameter of call back function.&lt;br/&gt;
&lt;em&gt; The most proper action code I am currently using is remove and add. From my understanding that current editAssociation will need to use two class name to identify the Association it is editing so we cannot use that to update (work flow will be remove-&amp;gt;add-&amp;gt;update model association index)&lt;br/&gt;
&lt;/em&gt; However in further debugging, I found that the remove action stop working after a few add and remove, this week I will first investigate into this issue before any further implementation on editing association&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-10-16&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; After a few experiment and investigation, I think the best way to fix the problem might be by adding a new action that will modify the current association in the cell (source, target) then update the umple code.&lt;br/&gt;
&lt;/em&gt; Currently I'm trying using remove on pointerdown, add on pointerup, but it is causing issue mentioned earlier, I will still try to figure if there is a way to avoid this, if not I will start implementing the feature above.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-10-15&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Add a new PR on the modification I made to fine tuning rendering.&lt;br/&gt;
&lt;/em&gt; Looking into implementing feature that will make moving the association in the graph updating the umple code&lt;br/&gt;
&lt;em&gt; implemented first approach by adding new action to on(cell:pointerdown) and on(cell:pointerup), however there is a problem that clicking the remove button is also pick by theses two on(event), find or propose walk around to this problem tomorrow.&lt;br/&gt;
&lt;/em&gt; Did not find JointJs State option (in a branch?)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-10-12&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fix render Class box with Attribute&lt;/li&gt;
&lt;li&gt;Fix input element height, the one using before cannot display some attribute text completely(e.g. String)&lt;/li&gt;
&lt;li&gt;Fix Class box height, it used to render the box too thick&lt;/li&gt;
&lt;li&gt;Fix break line between class name and attribute, used to be too thick&lt;/li&gt;
&lt;li&gt;Add margin to the class name input, it used to overlay with class icon&lt;/li&gt;
&lt;li&gt;Cosmetic fixing (typo) on inline comment&lt;/li&gt;
&lt;li&gt;As discussed in meeting, I will make a PR soon after I check nothing breaks with the changes&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;2017-10-11&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Finish update to umple user manual and added example for new syntax of association class&lt;br/&gt;
&lt;/em&gt; Start working on JointJS, read through the code, try to fix some rendering problem to have better graph display&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-10-8&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Finished the implementation on association class issue related to &lt;a class="" href="https://github.com/umple/umple/issues/1058" rel="nofollow"&gt;1058&lt;/a&gt;. Tests were added. PR waiting for review.&lt;br/&gt;
&lt;/em&gt; Start working on issue &lt;a class="" href="https://github.com/umple/umple/issues/600" rel="nofollow"&gt;600&lt;/a&gt;. Read through recent comment, getting familiar with the project.&lt;br/&gt;
* Question: Should I working on the existing 600 branch or my own one (not yet start any changes, but poking around the project with my local branch)?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-10-3&lt;/strong&gt;&lt;br/&gt;
* Further implementation on grammar after discussed in the git issue comment &lt;a class="" href="https://github.com/umple/umple/issues/1058" rel="nofollow"&gt;1058&lt;/a&gt; cause some issue that the parser treat inline association as singleEndassociation it treat&lt;code&gt;* -- * Location&lt;/code&gt;as a single end association &lt;code&gt;[multiplicity: *][otherEndruleName: --][type: *][roleName: Location]&lt;/code&gt;, which is super suspicious. Further investigation shows that order will have some influence on the result. I will do more investigate on order of different role under association class on Friday, I may not be able to do much before Thursday as I have a midterm.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-9-28&lt;/strong&gt;&lt;br/&gt;
* Solidate how multiple roleNames in association class, added a few test before actual implementation, test failed as expected. I will start on the actual implementation tomorrow.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-9-19&lt;/strong&gt;&lt;br/&gt;
* Fix the error message of umple compiler, however it seems that the complier using by local umpleonline. However I copy the umple.jar under ..\umpleonline\scripts it works as expected. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-9-19&lt;/strong&gt;&lt;br/&gt;
&lt;strong&gt;Meeting update&lt;/strong&gt;&lt;br/&gt;
&lt;strong&gt;TODO:&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; write a few tests for the error message then make the pull request for the error message.&lt;br/&gt;
&lt;/em&gt; start fixing .grammar file and internalParser for possible way to adapt fixing to this issue to association class&lt;br/&gt;
&lt;em&gt; following up from the last entry, confirm with Tim check hammer the syntax&lt;br/&gt;
&lt;/em&gt; check the php permission problem&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-9-18&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Fix the error message to print out more informative descriptions of the problem. However a few question is still left (commented in the issue ticket &lt;a class="" href="https://github.com/umple/umple/issues/1058" rel="nofollow"&gt;1058&lt;/a&gt;)&lt;br/&gt;
&lt;/em&gt; The problem I encounter earlier seems like I might fail to full build a project while I thought I did.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-9-17&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Set up Umple project in Eclipse. The project now successfully build (warning on 9-16 still exists, but now crash the project for what I am doing now).&lt;br/&gt;
&lt;/em&gt; Spent some good hours hook Eclipse to a remote umple command line tool, put down example in a umple file and stepping through the code.&lt;br/&gt;
* Narrowed down the problem at few functions, left break points there. I will keep digging into this problem in the next couple of days. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-9-16&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Still familiarize with the project as well as finding the problem related to issue &lt;a class="" href="https://github.com/umple/umple/issues/1058" rel="nofollow"&gt;1058&lt;/a&gt;&lt;br/&gt;
&lt;/em&gt; When setting up Eclipse in the step to compiling Umple_Code.ump, received error "&lt;span&gt;[Warning 1009 on line 866 of file "Umple_Code.ump":&lt;br/&gt;
Method 'setExtraCode' has a name conflict with automatic generated getter/setter methods for attribute 'extracode' in class 'MethodBody'. Please use a different method name]&lt;/span&gt;&lt;br/&gt;
"&lt;br/&gt;
&lt;em&gt; Run full test on Eclipse but failed some test (further look into the test, those are some part that I haven't added to the eclipse work bench)&lt;br/&gt;
&lt;/em&gt; Not sure if test is needed for this issue since it is just a warning log issue&lt;br/&gt;
&lt;em&gt; Comment a few notes on the issue page&lt;br/&gt;
&lt;strong&gt;&lt;em&gt; QUESTION &lt;/em&gt;&lt;/strong&gt;&lt;/em&gt; Edited error message error code 19. However after a full build, the change does not show up when I run a local umpleonline.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-9-14&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Browsed all open issue, find one small issue that should be easy for me to tackle (&lt;a class="" href="https://github.com/umple/umple/issues/1058" rel="nofollow"&gt;1058&lt;/a&gt;).&lt;br/&gt;
&lt;/em&gt; Emailed Timothy and got assigned to the issue.&lt;br/&gt;
&lt;em&gt; Familiaring with the project, reading Architecture page and the project try to find where the bug should happened&lt;br/&gt;
&lt;/em&gt; Narrowed down to \cruise.umple\UmpleInternalParse_CodeClass.ump, \cruise.umple\UmpleInternalParse_CodeConstraints.ump, \cruise.umple\UmpleInternalParse_CodeTraceAssoication.ump,\cruise.umple\src\Main_Code.ump&lt;br/&gt;
(not sure if it is correctly though, kind of stuck here)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2017-09-12&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Material Explored&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Skimmed through all the materials that I have been pointed to.&lt;br/&gt;
&lt;/em&gt; Explored all the resource on GitHub page and checked out the latest repository&lt;br/&gt;
* Tried to played around with the umpll online tool, watched some tutorial video and created some small example of both state machine and class diagram&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Development Setup&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Checked out and successfully full built the latest repository&lt;br/&gt;
&lt;/em&gt; Successfully built and host the local umpleOnline&lt;br/&gt;
* Successfully compiled some simple ump file using umple commandline tool&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Eclipse Setup&lt;/strong&gt;&lt;br/&gt;
&lt;em&gt; Installed the eclipse with modelling tool and installed umple plug-in&lt;br/&gt;
&lt;/em&gt; Still need to play with the plugin to create some simple project (ETA Sep 15th)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Other Notes and Questions&lt;/strong&gt;&lt;br/&gt;
* My operating system is MacOs Sierra with php 5.5&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;While playing with umpleOnline tool, at some point the diagram area reject to allow any editing (No response when clicking any diagram). I will keep track of this and see if it is something easily reproducible (It doesn't cause further issue as refreshing the page will fix it).&lt;/li&gt;
&lt;li&gt;Although local umpleOnline works, I receive this message from php "PHP Notice:  Undefined index: languageStyle in UMPLEPATH/umpleonline/scripts/compiler.php on line 76" (As for the security permission mentioned in the meeting, it seems only using apache will have such issue)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;These Questions is more likely to be a personal interest so I don't want to use meeting time for them&lt;/strong&gt;&lt;br/&gt;
* Why umpleOnline does not allow users to edit the label on association or transition (not really sure if it is my problem though)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>UCOSPLogNoahMurad modified by Timothy C. Lethbridge</title><link href="https://sourceforge.net/p/umple/wiki/UCOSPLogNoahMurad/" rel="alternate"/><published>2017-12-28T16:00:17.753000Z</published><updated>2017-12-28T16:00:17.753000Z</updated><author><name>Timothy C. Lethbridge</name><uri>https://sourceforge.net/u/tcltcl/</uri></author><id>https://sourceforge.net30b7ed0aa27b8715d94261a4172ff5deead7c9ad</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Each UCOSP participant is asked to log all the steps they take as they make progress through the semester. This includes difficulties they faced (getting set up, understanding how to model in Umple, using UmpleOnline, code that is difficult to figure out, and development tools that are hard to figure out, or don't seem to work properly). The more log entries added the more we can better get a grip on the usability issues with Umple, and the more we can help future new contributors come up to speed.&lt;/p&gt;
&lt;p&gt;Please record entries in reverse chronological order&lt;/p&gt;
&lt;h1 id="log-entries"&gt;Log Entries&lt;/h1&gt;
&lt;h3 id="april-15th"&gt;April 15th&lt;/h3&gt;
&lt;p&gt;Today I mainly focused on refining the &lt;code&gt;README&lt;/code&gt; for &lt;code&gt;umple.orion&lt;/code&gt;. This involved me running through the setup of the system and using the system to identify information that I should include in the documentation and writing this information in a clear and concise language. I understand that this is not programming, but I am logging this work because it was sufficient (~5 hours) and because documentation is a very important part of the software development cycle. I want to make sure that my work is useable and understood by any successors especially considering its disconnected nature from the rest of the Umple project and early development stage that the Orion project is in (hence, not too much support or documentation available). I also made a minor change to my cleanup script since I was bound to find one minor quirk with all of the setting up and tearing down of the system. &lt;/p&gt;
&lt;p&gt;I also made my pull request and spent time describing what is included in the request. I learned that the point of a pull request is to show the project owner that your modified version of the software is better than the master version. Properly convincing the project owner that your version is better than the master version is an important concluding step of feature additions, because without being able to convince them of this, your code changes will be thrown out. Let us hope for the best!&lt;/p&gt;
&lt;h3 id="april-14th"&gt;April 14th&lt;/h3&gt;
&lt;p&gt;I woke up to some of the strangest Java errors which seemed to spawn overnight. I believe the errors were related to my build path. Regardless, I needed to change my project structure because the tests were not in a pretty plac (I have not ever made first tests for a Java project). Luck was on my side when restructuring the project solved my "cannot resolve the class of a file in the same package" issues.&lt;/p&gt;
&lt;p&gt;I then added the JUnit dependency to my pom to the umple-orion-server had working automated build once again. Continuing with the server, I modified the build process of system to work with a constant-named umple-orion-server. Before doing this, the server built with a version number in the filename and the setup scripts fetched/renamed this file via wildcard. &lt;/p&gt;
&lt;p&gt;I spent a lot of my work session attempting to get cascading menus for the UI of my plugin in Orion. I have tried doing this perviously, so I already knew where and where not to look. Through using and analysing &lt;a class="" href="https://orion-plugins.github.io/" rel="nofollow"&gt;the source code of other Orion plugins&lt;/a&gt;, reading through &lt;a class="" href="https://www.eclipse.org/forums/index.php/t/1066244/" rel="nofollow"&gt;Orion forum posts&lt;/a&gt;, messaging the &lt;a class="" href="https://wiki.eclipse.org/IRC" rel="nofollow"&gt;Orion IRC channel&lt;/a&gt;, reading through the &lt;a class="" href="https://wiki.eclipse.org/Orion/Documentation/Developer_Guide" rel="nofollow"&gt;Orion Client API documentation&lt;/a&gt; and referring to the (sometimes inconsistent to the API documentation) &lt;a class="" href="https://orionhub.org/jsdoc/index.html" rel="nofollow"&gt;Orion JsDoc reference&lt;/a&gt; to experiment with and test different plugin codes, I found nothing better than what is currently in place ie no support for cascading menus in the current build of the Orion client API. I do understand that there are cascading menus for built-in features, but those are baked into the client's code and I would not want to build directly into the Orion client because my additions will most likely break with future updates of Orion and it would also be extremely difficult (time-consuming, costly,...). It is a shame to spend hours working and have nothing to show for it, but that is the cost of research and diving into unknown grounds. &lt;/p&gt;
&lt;p&gt;Moving on, to the Orion plugin, I added every language which is currently supported in the Eclipse plugin. I then applied a few different labellings to the menu items to get a feel for what is the most user friendly. This was important to do because since there is no support for cascading menus, there are a lot of menu items so I wanted to make it easy for the user to find the menu item they are looking for. Earlier this semester I had designed the plugin so that the menu items only appear when you have an Umple file active, so these menu items will only appear when needed and will not annoy users working on other projects or with other files.&lt;/p&gt;
&lt;h3 id="april-13th-evening-night"&gt;April 13th (Evening-Night)&lt;/h3&gt;
&lt;p&gt;I spent this work session atomizing umple-orion-server to make it testable. During this session, I learned how to make JUnit tests and refactored the server accordingly. The server now uses two new classes which are minimally exhaustively tested. The server is now more flexible for the future in case there is a change in the request syntax, and more importantly, the server is testable.&lt;/p&gt;
&lt;h3 id="april-13th-morning-afternoon"&gt;April 13th (Morning-Afternoon)&lt;/h3&gt;
&lt;p&gt;Today I resumed work. I planned on making the system Windows compatible today, but it already was Windows compatible. I spent &lt;em&gt;the day&lt;/em&gt; installing, using and configuring Maven, Firefox, Chrome, Docker, Java, Windows, Orion, the Dockerfile, umple-orion-server, and umple.orion/plugin on Windows in attempts to get my system running on Windows. The outcome is that it is horribly tedious to get running because some of these apps (Maven, Docker) do not have user friendly set-ups and configurations on Windows. At the end of this work session, I performed the almighty &lt;code&gt;git add .; git commit&lt;/code&gt; to learn that &lt;code&gt;Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean&lt;/code&gt;: after all of the configuring and tweaking, the system was working all along. &lt;/p&gt;
&lt;p&gt;The only &lt;em&gt;possible&lt;/em&gt; changes that were made were that I changed line endings in the &lt;code&gt;run&lt;/code&gt; file from Windows line endings (inconclusive of why or how Windows decided to change this file's line endings without asking) back to Unix line endings (since it is run in an Ubuntu image). I say &lt;em&gt;possibly&lt;/em&gt; because, once again, I never opened this file until I realised that Docker was getting confused by its instructions and it printed &lt;code&gt;\r&lt;/code&gt; in one of my debugging sessions. The behaviour of Maven, Docker, the server, and the plugin are all very odd because they seem to function inconsistently, but regardless, I expect (and suggest) the system will be deployed on Linux machines so the instability should not be an issue. These issues will only be raised for developers using Windows to work on this project. For that case, I suggest using a VM or installing Linux. Although this system does run on Windows, it is not worth the trouble.&lt;/p&gt;
&lt;p&gt;This session allowed me to add to the documentation and confirm that the system is Windows compatible, but make the strong recommendation to deploy (and develop) on Linux.&lt;/p&gt;
&lt;p&gt;Aside: I have changed my commit style to commit more often after reading about committiquette.&lt;/p&gt;
&lt;h3 id="march-28-30th"&gt;March 28-30th&lt;/h3&gt;
&lt;p&gt;Vahdat has been having issues building and running the Docker image. Based on his error, it seems like either &lt;a class="" href="https://github.com/docker/docker/issues/30833" rel="nofollow"&gt;Docker has issues handling wildcards&lt;/a&gt;, or the umple-orion server is not building correctly. To fix this, I removed wildcards from the Dockerfile, and updated the README to specify that the setup script must be run from the repository's root directory. I did a few final tests to make sure that everything build properly from source. &lt;/p&gt;
&lt;h3 id="march-25th"&gt;March 25th&lt;/h3&gt;
&lt;p&gt;I modified the Dockerfile and built some other scripts to automate the deployment and running of the Umple-Orion and Orion servers. The biggest challenge today was to be patient while testing.&lt;/p&gt;
&lt;h3 id="march-22nd"&gt;March 22nd&lt;/h3&gt;
&lt;p&gt;I set up the umple server to build properly so that I can be deployed. Various small hiccups were encountered doing so such as needing to install umple.jar to my local repository, but Maven has a helpful community of developers, so none of these issues were major roadblocks.&lt;/p&gt;
&lt;p&gt;Major changes were made to both the plugin and the server to support multiple languages. Along the way, I found a bug where filenames with special characters (like spaces) were being sent to the server in a different encoding. This was resolved by using a URL Decoder. There were also oddities with where the files were being generated. When using the &lt;code&gt;-g&lt;/code&gt; flag with Umple, files get generated in the current directory, so I had to create a folder for output and use the &lt;code&gt;--path&lt;/code&gt; option to redirect the location of output. &lt;/p&gt;
&lt;h3 id="march-20th"&gt;March 20th&lt;/h3&gt;
&lt;p&gt;I have added the Umple content-type along with syntax highlighting to the plugin. These are built in features to the Orion plugin API, so no issues were encountered.&lt;/p&gt;
&lt;h3 id="march-18th"&gt;March 18th&lt;/h3&gt;
&lt;p&gt;The Orion plugin now sends the filename of the currently opened file, along with the username. The Umple server gracefully handles the request.&lt;/p&gt;
&lt;h3 id="march-11th"&gt;March 11th&lt;/h3&gt;
&lt;p&gt;The Umple server can now parse properly formatted requests. The Orion plugin currently sends a fake request with a constant username and file name. &lt;/p&gt;
&lt;p&gt;My next step is to make the Orion plugin send the current user's username and file selection.&lt;/p&gt;
&lt;h3 id="march-3rd-4th"&gt;March 3rd-4th&lt;/h3&gt;
&lt;p&gt;I started building my &lt;a class="" href="https://github.com/nwam/umple.orion/tree/master/umple-orion-server" rel="nofollow"&gt;server&lt;/a&gt; and connecting it to the &lt;a class="" href="https://github.com/nwam/umple.orion/tree/master/plugin" rel="nofollow"&gt;plugin&lt;/a&gt; I have previously created. There we're some dependency issues setting up the server, and further, getting the plugin to make HTTP requests to the server. The latter issue arose because the Orion client runs over HTTPS and my server is hosted on HTTP. I solved this by disabling some security settings in Firefox for the Orion client.&lt;/p&gt;
&lt;p&gt;My next steps are to send the filename(s) and username to my server via the Orion plugin. I have done some surface research and will probably need to change the Orion plugin's service from &lt;a class="" href="https://wiki.eclipse.org/Orion/Documentation/Developer_Guide/Plugging_into_the_editor#orion.edit.command" rel="nofollow"&gt;&lt;code&gt;orion.edit.command&lt;/code&gt;&lt;/a&gt; to &lt;a class="" href="https://wiki.eclipse.org/Orion/Documentation/Developer_Guide/User_interface_services#orion.page.command" rel="nofollow"&gt;&lt;code&gt;orion.page.command&lt;/code&gt;&lt;/a&gt; to be able to send multiple filenames to the server.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;March 5th small update:&lt;/strong&gt; I will be using a combination of &lt;a class="" href="https://wiki.eclipse.org/Orion/Documentation/Developer_Guide/Plugging_into_the_navigator#orion.navigate.command" rel="nofollow"&gt;&lt;code&gt;orion.navigate.command&lt;/code&gt;&lt;/a&gt; and the already-used &lt;code&gt;orion.edit.command&lt;/code&gt;. The former will allow me to send multiple filenames to the server. &lt;/p&gt;
&lt;h3 id="february-27th"&gt;February 27th&lt;/h3&gt;
&lt;p&gt;"The current Orion server is written in Java, using Jetty and Equinox server infrastructure. This server does not currently define any Java API for extending or augmenting its behavior" (&lt;a class="" href="https://wiki.eclipse.org/Orion/Documentation/Developer_Guide/Architecture" rel="nofollow"&gt;Orion Architecture&lt;/a&gt;). Since extending the Orion server is not supported, and modifying/hacking at the &lt;a class="" href="https://github.com/eclipse/orion.server" rel="nofollow"&gt;Orion server source code&lt;/a&gt; would lead to problems in future updates of the source and be incredibly difficult, I have come to an alternate solution after reading through &lt;a class="" href="https://github.com/search?utf8=%E2%9C%93&amp;amp;q=Orion+Eclipse" rel="nofollow"&gt;Eclipse Orion based projects&lt;/a&gt;, &lt;a class="" href="http://planetorion.org/news/" rel="nofollow"&gt;Orion news&lt;/a&gt;, and other sources of information such as &lt;a class="" href="https://wiki.eclipse.org/Orion/Documentation/Developer_Guide" rel="nofollow"&gt;the Orion Developer Guide&lt;/a&gt; and communicating with a member of IBM.&lt;/p&gt;
&lt;p&gt;I propose that I instead build a server with &lt;a class="" href="https://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/keplersr2" rel="nofollow"&gt;Java EE&lt;/a&gt;, which generates the code (just like UmpleOnline) and returns the generated code to the client. The client will be a Orion plugin which sends the selected file and all other related files to this server (initiated with a menu option), then once it gets a response from the Umple Generator server, it will place the received files on the Orion server using the &lt;a class="" href="https://wiki.eclipse.org/Orion/Server_API/File_API" rel="nofollow"&gt;Orion Server File API&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;We will need to be able to host this server (unless there is an UmpleOnline API), but for the meantime I will test it with a local Tomcat server. Aside, I would like to apologize for the lack of apparent activity on my end. I would like to mention that I have been working hard at trying to figure out how to modify the Orion server or send custom requests to the Orion server until I discovered this much simpler alternative solution to the problem at hand.&lt;/p&gt;
&lt;h3 id="february-17th-26th"&gt;February 17th-26th&lt;/h3&gt;
&lt;p&gt;I made a very basic plugin which adds a button to the Orion UI which says "Umple Generation" but does not have functionality. I hosted this plugin on &lt;a class="" href="https://nwam.github.io/umple.orion/umpleGenerator.html" rel="nofollow"&gt;my GitHub pages&lt;/a&gt; so that Orion can install the plugin. Aside from this, I have been putting in &lt;strong&gt;many&lt;/strong&gt; hours, across 4 sessions (days), reading through the Orion documentation and forums, making &lt;a class="" href="https://www.eclipse.org/forums/index.php/t/1084595/" rel="nofollow"&gt;a post of my own&lt;/a&gt; attempting to learn how to send requests from the client to the server and how to make the server generate code with umple.jar upon receiving these requests, however, I cannot seem to find any guidance as to what my next steps should be. &lt;/p&gt;
&lt;p&gt;Edit from the future about my thoughts of the past: I just cannot seem to find a way to modify the Orion server to accomplish my task. I was instructed and guided to hack at the Orion server. I believe that any modifications I make to the Orion server will be highly cohesive and can easily conflict with future updates to Orion (it is still under heavy development). Making these modifications would make me an Orion developer, I am developing for Umple. I need to stop and discard all of progress in order design my own architecture to make this project possible.&lt;/p&gt;
&lt;h3 id="february-9th"&gt;February 9th&lt;/h3&gt;
&lt;p&gt;Today was a day of research. I continued learning about Orion, but this time I went more in depth, gathering knowledge that I will implement Umple code generation (among other features) into Orion.&lt;/p&gt;
&lt;p&gt;Earlier this week I fixed my Docker problem, and today I came across another issue with restarting the Docker application. I ended up learning the basics of using Docker to understand and fix the issue.&lt;/p&gt;
&lt;p&gt;Today I read through all the commits in the &lt;a class="" href="https://github.com/nwam/umple.orion/commits/master" rel="nofollow"&gt;umple.orion&lt;/a&gt; repository (there are only 7 small commits) to see what has been done so far. I then read a little bit of the &lt;a class="" href="http://wiki.eclipse.org/Orion/Server_admin_guide" rel="nofollow"&gt;Orion server admin guide&lt;/a&gt;, all of the &lt;a class="" href="http://wiki.eclipse.org/Orion/Documentation/Developer_Guide/Architecture" rel="nofollow"&gt;Orion architecture&lt;/a&gt;, and &lt;a class="" href="http://wiki.eclipse.org/Orion/Documentation/Developer_Guide/Simple_plugin_example" rel="nofollow"&gt;made my first Orion plugin&lt;/a&gt;, which lead me to &lt;a class="" href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/A_re-introduction_to_JavaScript" rel="nofollow"&gt;learn JavaScript&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;As for the future, I now know how to make a plugin for Orion, but the code generation needs to happen on the Orion server. So I will dive deeper into server-side development in my next work session, hopefully coming out with some implementation of Umple code generation in Orion.&lt;/p&gt;
&lt;h3 id="february-2nd"&gt;February 2nd&lt;/h3&gt;
&lt;p&gt;Fixed up a small issue with my pull request concerning the format a comment in the generated code of the test templates. Started learning about Eclipse Orion on the &lt;a class="" href="https://wiki.eclipse.org/Orion" rel="nofollow"&gt;wiki&lt;/a&gt; and set up and started to get acquainted with Orion by following some of the &lt;a class="" href="https://wiki.eclipse.org/Orion/Documentation/User_Guide/Getting_started" rel="nofollow"&gt;getting started guide&lt;/a&gt;. I also attempted to set up the &lt;a class="" href="https://github.com/umple/umple.orion" rel="nofollow"&gt;Orion repository&lt;/a&gt; but I am getting an error related to a dependency when I try to start docker with &lt;code&gt;sudo systemctl start docker&lt;/code&gt; on Manjaro. I will try solving this error during my next Umple session, perhaps by installing docker from another source. &lt;/p&gt;
&lt;h3 id="january-27th"&gt;January 27th&lt;/h3&gt;
&lt;p&gt;Fixing tests which failed after fixing issue 964. While fixing some of these tests, I've noticed that some of the generated code has method parameters of type &lt;code&gt;Integer&lt;/code&gt;, &lt;code&gt;int&lt;/code&gt;, and &lt;code&gt;integer&lt;/code&gt; (which is now a typeless parameter after fixing &lt;a class="" href="https://github.com/umple/umple/issues/964" rel="nofollow"&gt;issue 964&lt;/a&gt;). Only integer is a primitive PHP type. I have commented further in comments of issue 964. Issued my pull request for 964.&lt;/p&gt;
&lt;p&gt;Another oddity that I ran into is that all &lt;code&gt;ClassCodeInjections_*&lt;/code&gt; tests which were failing continued to fail after generating and placing appropriate code. All reasons for failure were due to the test expecting a comment line but receiving a line of executable code. I fixed this by removing all lines of the form &lt;code&gt;// line *&lt;/code&gt; from the generated files for &lt;code&gt;ClassCodeInjections_*&lt;/code&gt; tests.&lt;/p&gt;
&lt;h3 id="january-20th-22nd"&gt;January 20th-22nd&lt;/h3&gt;
&lt;p&gt;Code sprint at the University of Calgary. I spent the first two days attempting to solve &lt;a class="" href="https://github.com/umple/umple/issues/656" rel="nofollow"&gt;issue 656&lt;/a&gt;, running into a few roadblocks which made solving this issue very much more difficult than it seems at the surface. More information about these problems can be found in &lt;a class="" href="https://github.com/umple/umple/issues/656" rel="nofollow"&gt;the issue's&lt;/a&gt; comments. Luckily, attempting to solve this issue allowed me to explore (in depth) and understand the architecture of Umple. I spent the final day (morning) of the sprint learning some PHP and working on &lt;a class="" href="https://github.com/umple/umple/issues/964" rel="nofollow"&gt;issue 964&lt;/a&gt;. It was a quick fix, but it allowed me to find another issue, which I mentioned in the comments of &lt;a class="" href="https://github.com/umple/umple/issues/964" rel="nofollow"&gt;the issue&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id="january-17th"&gt;January 17th&lt;/h3&gt;
&lt;p&gt;I got the environment set up in eclipse by performing a command line build and following Ahmed's steps. I started looking into solving my first issue. To do so, I have been getting a stronger understanding of Umple's architecture by referring to the architecture page and analysing the directory structure and reading through files.&lt;/p&gt;
&lt;h3 id="january-9th"&gt;January 9th&lt;/h3&gt;
&lt;p&gt;I attempted to set up my development environment in Eclipse. I managed to get everything working except for an error in the cruise.umple.nebula project. In cruise.umple.core.Generator an import of cruise.umple.cpp.gen.Header cannot be resolved. I tried adding cruise.umple to cruise.umple.nebula's build path, but that caused a circular reference error.&lt;/p&gt;
&lt;p&gt;I also went through some practice examples of using Umple. I used Umple Online to generate the Java code.&lt;/p&gt;
&lt;h3 id="january-6th"&gt;January 6th&lt;/h3&gt;
&lt;p&gt;I finished reading the documentation and the key wiki pages. I successfully set up the development environment and plan on setting up the eclipse environment in my next work session.&lt;/p&gt;
&lt;h3 id="january-5th"&gt;January 5th&lt;/h3&gt;
&lt;p&gt;Read through the core of the Umple user manual including User Manual Basics, Classes and Interfaces, Attributes, Associations, Methods and Directives. Did some experimenting in UmpleOnline and skimmed and compiled some generated code.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>