<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/jseq/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/jseq/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/jseq/feature-requests/</id><updated>2008-10-18T21:24:09Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Documentation files are duplicated</title><link href="https://sourceforge.net/p/jseq/feature-requests/12/" rel="alternate"/><published>2008-10-18T21:24:09Z</published><updated>2008-10-18T21:24:09Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.net6b9ff33a225f9686bcd977dba979dc7cb697550d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The documentation files used to be stored only as html in the docs directory, but to make the Mave site target work smoothly, I had to make a duplicate in src/site/apt/docs. I think we should make the src/site/apt/docs files the master, and generate the html documentation to use in the delivery zip file from the APT files.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Update license agreement</title><link href="https://sourceforge.net/p/jseq/feature-requests/11/" rel="alternate"/><published>2008-08-18T19:13:17Z</published><updated>2008-08-18T19:13:17Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.netd98af63bce4978bf376c45fae807b379d0188d25</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The JSeq license agreement should be updated to LGPL. A copyright notice should be included in all relevant files.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Increase test coverage</title><link href="https://sourceforge.net/p/jseq/feature-requests/10/" rel="alternate"/><published>2008-08-18T18:01:51Z</published><updated>2008-08-18T18:01:51Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.net1beb899f14339484d5351fed0aa6dc1eab58d2e0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When building JSeq with Maven, e.g., with the command "mvn site", we see in the Cobertura report that only about 42% of the code is run through by the unit tests.&lt;/p&gt;
&lt;p&gt;Test code coverage should be increased to at least 85%.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Remove Checkstyle and PMD warnings</title><link href="https://sourceforge.net/p/jseq/feature-requests/9/" rel="alternate"/><published>2008-08-18T17:59:24Z</published><updated>2008-08-18T17:59:24Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.net3fb9364181f483f9783c4ff6f71c2189ece2c659</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When building JSeq using Maven, e.g., with the command "mvn site", we see that there are a whole lot of Checkstyle errors, and some PMD warnings.&lt;/p&gt;
&lt;p&gt;The code should be improved to remove these warnings.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add support for building with Maven 2</title><link href="https://sourceforge.net/p/jseq/feature-requests/8/" rel="alternate"/><published>2008-08-17T14:03:28Z</published><updated>2008-08-17T14:03:28Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.netec358a043213e4b44173b145f1c9dcf84377eb41</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;We should add support for building JSeq using Maven 2. There are several reasons for this:&lt;/p&gt;
&lt;p&gt;- It makes it easy to run and generate reports for tools such as CheckStyle, Cobertura, PMD, etc.&lt;/p&gt;
&lt;p&gt;- It can be used to create a project site, which can be uploaded to jseq.sourceforge.net.&lt;/p&gt;
&lt;p&gt;- Since I will probably be using Maven 2 in an upcoming project, I need the practice. :-)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add an -include argument</title><link href="https://sourceforge.net/p/jseq/feature-requests/7/" rel="alternate"/><published>2008-08-17T10:04:51Z</published><updated>2008-08-17T10:04:51Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.net6a498ca1bfdc02a6d94d6f0609e8dc3cde7e6b48</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;We should add an -include command-line argument to JSeq which allows us to create a diagram containing only the specified classes.&lt;/p&gt;
&lt;p&gt;The semantics should be as follows:&lt;/p&gt;
&lt;p&gt;- Simple wildcards are allowed, with a * at the beginning or the end. For example, "foo.bar.*", *.MyTest".&lt;/p&gt;
&lt;p&gt;- If several -include arguments are given, the union of all matched classes shall be traced. For example, "-include foo.bar.* -include foo.baz.*" will include all classes in foo.bar and foo.baz.&lt;/p&gt;
&lt;p&gt;- If -include is used together with -exclude, it should be taken to mean that all classes that match -include are traced, except the ones matching -exclude. For example "-include foo.bar.* -exclude foo.bar.MyTest" will include all classes in foo.bar except MyTest.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>There should be a start script for Linux</title><link href="https://sourceforge.net/p/jseq/feature-requests/6/" rel="alternate"/><published>2008-08-15T18:35:58Z</published><updated>2008-08-15T18:35:58Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.net8c25a622c39d4c8742c6d4106bbebf5441b8e9b2</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, the JSeq bin directory only contains a jseq.bat file for Windows. There should also be a start script that can be used in Linux / *nix.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>It should be easy to call JSeq from another program</title><link href="https://sourceforge.net/p/jseq/feature-requests/5/" rel="alternate"/><published>2008-08-11T13:54:54Z</published><updated>2008-08-11T13:54:54Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.netbd4b123cf8449d30111cd1c1b4c65062608775c7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The only way right now to use JSeq to create a sequence diagram from another program i to call Main.main with a number of command-line arguments. The diagram is always written to a file.&lt;/p&gt;
&lt;p&gt;We should make it easier to JSeq from another program, by providing set methods for all command-line arguments, and by making it possible to return the diagram as an object, not only through files.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>JSeq should use a logging framework</title><link href="https://sourceforge.net/p/jseq/feature-requests/4/" rel="alternate"/><published>2008-08-11T13:42:09Z</published><updated>2008-08-11T13:42:09Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.netdd54b50b140141c3130a20939a886d027da46912</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, all logging in JSeq is done using System.out and System.err. This is not very flexible, and it causes problems if someone wants to use JSeq embedded in another program.&lt;/p&gt;
&lt;p&gt;We should switch to use a real logging framework. For flexibility, it may be a good idea to use Commons Logging -- it is then easy to use different underlying logging packages.&lt;/p&gt;
&lt;p&gt;To reduce the number of dependencies on other packages, the default implementation should probably use java.util.logging as log implementation.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Killing JSeq should still generate a diagram</title><link href="https://sourceforge.net/p/jseq/feature-requests/3/" rel="alternate"/><published>2008-08-06T21:21:31Z</published><updated>2008-08-06T21:21:31Z</updated><author><name>Henrik Arro</name><uri>https://sourceforge.net/u/arro01/</uri></author><id>https://sourceforge.net076bf49e71c9199e4fe8bdbcc988bcb99d9ac59f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It should be possible to generate diagrams for part of the execution of long-running processes.&lt;/p&gt;
&lt;p&gt;This can be very useful when working with web applications, for example, where we want to create a sequence diagram that shows how a certain request is handled.&lt;/p&gt;
&lt;p&gt;Currently, this can be done by attaching to the long-running process, but then that process must be killed for JSeq to generate a diagram. If JSeq is killed with Ctrl-C, no diagram is generated.&lt;/p&gt;
&lt;p&gt;I think that JSeq should generate a diagram even when it is interrupted with Ctrl-C.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>