[Issue 6417] Build using wiki instructions fail - works from within Eclipse

[email protected]
Newsgroups gmane.comp.lang.uml.argouml.issues
Message-ID <[email protected]>
http://argouml.tigris.org/issues/show_bug.cgi?id=6417



User linus changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |FIXED
--------------------------------------------------------------------------------
        Target milestone|---                       |0.35.1
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Tue Mar 13 14:53:21 -0700 2012 -------
Hello Öyvind!

I have now improved the wiki page a little. I hope it is clearer.

I have also found and fixed a bug in the build.xml file that affects the run target. If you do
$ ./build.sh run
you encounter the problem you mentioned. I assume that is what you are trying so I will 
consider this issue fixed.

I had not noticed this problem because most of the time I have been doing
$ cd build
$ java -jar argouml.jar
$
instead because that is more how ArgoUML is started in the release. This is also the reason I 
had a long explanation about the class path and how to update of the manifest in argouml.jar 
that is applicable when started in this way.

The problem I found was also with the class path but when started from build.xml.

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=448&dsMessageId=2935076

To unsubscribe from this list, e-mail: [[email protected]].
Please do not reply to this mail. Instead, add your comments in the issue.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.