A possible reason for this has just occured to me.

ArgoUML is becoming more modularized with the different diagram types
being split out into pluggable components. The first of these to be
split into a module is the sequence diagram.

It could be that the code that loads those modules has not been called
when the command line code is interpreted.

Do record the defect and place under subcomponent moduleloader.

We're busy looking at a defect release at the moment and the sooner
this is recorded the more likely it is to get in.

Regards

Bob



On 27 April 2010 19:07, Bob Tarling <[email protected]> wrote:
> I can tell you that I did a quick test with 0.30.1 beta 3 and there is
> a similar error.
>
> Please get the issue logged and we'll see what we can do.
>
> Regards
>
> Bob
>
> On 27 April 2010 18:36, Bob Tarling <[email protected]> wrote:
>> Hi Nathanial
>>
>> I'd rather look at this in relation to our current build rather than
>> have to look back. I'd like to try to replicate this with our current
>> subversion code.
>>
>> Could you first of all create an issue in IZ
>> http://argouml.tigris.org/project_bugs.html and attach anything of
>> relevance there.
>>
>> Running a custom build is not advisable, particularly as it is so old.
>> We have many fixed defects since then.
>>
>> I'd like to see a patch of what is different for you. We can then look
>> at what is needed to satisfy your requirements in all our official
>> builds in future.
>>
>> Regards
>>
>> Bob
>>
>> On 26 April 2010 07:17, Nathaniel Kofalt <[email protected]> wrote:
>>> Hello all!
>>>
>>>     We use a custom ArgoUML build (currently of 0.28.1) - essentially
>>> just a minor change by "thn" (revision 17025, see link below) that makes
>>> it possible to save all graphics from the command-line. Combined with a
>>> simple commit script, and now we have a SVN repository of ArgoUML
>>> projects that automatically generate pictures of themselves into a
>>> folder, which gets served over Apache. This allows us to have a
>>> browser-viewable set of images always showing the latest revision of the
>>> UML. This is very convenient for our team, and our main reason for using
>>> ArgoUML.
>>>
>>>     The command we use is pretty vanilla, just open the project and
>>> export all in batch mode (put in your own locations at the ... marks):
>>>     java -jar ...argouml.jar -batch -command
>>> "org.argouml.uml.ui.ActionOpenProject=....example.zargo" -command
>>> "org.argouml.uml.ui.ActionSaveAllGraphics=..../exampleEmptyFolder"
>>>
>>>     And this works perfectly in most cases. However, any project with a
>>> Sequence diagram causes this exception:
>>>     org.argouml.persistence.OpenException:
>>> java.lang.ClassNotFoundException:
>>> org.argouml.sequence2.diagram.UMLSequenceDiagram
>>>     (plus a lengthy stack traced, attached to this email).
>>>
>>>     Replicating this error is pretty easy:
>>>         svn checkout
>>> http://argouml.tigris.org/svn/argouml/releases/VERSION_0_28_1/src
>>> argouml/src --username guest
>>>         svn checkout
>>> http://argouml.tigris.org/svn/argouml/releases/VERSION_0_28_1/tools
>>> argouml/tools --username guest
>>>         Apply the diff linked below (one file), easy enough to do manually
>>>         Build project with "argouml\src\argouml-build\build.sh" or
>>> similar "build.bat"
>>>         Newly-built project appears in "argouml\src\argouml-build\build"
>>>         Use the java command above on any ArgoUML project without a
>>> Sequence diagram to see it generate PNG images for each diagram
>>>         Use the java command above on any ArgoUML project with a
>>> Sequence diagram to see it fail
>>>
>>>     The diff link:
>>> http://argouml.tigris.org/source/browse/argouml/trunk/src/argouml-app/src/org/argouml/uml/ui/ActionSaveAllGraphics.java?view=diff&r1=17024&r2=17025&pathrev=17025&diff_format=l
>>>
>>>     This seems strange, since presumably the only difference from the
>>> official releases is that tiny feature added (like 30 lines). To confuse
>>> matters, the class source it can't find
>>> (org.argouml.sequence2.diagram.UMLSequenceDiagram) clearly exists in the
>>> checkouts we build from (in the
>>> "argouml\src\argouml-core-diagrams-sequence2\src\org\argouml\sequence2\diagram"
>>> folder).
>>>
>>>     For convenience I also attached the exact modified file,
>>> "argouml\src\argouml-app\src\org\argouml\uml\ui\ActionSaveAllGraphics.java"
>>> so you don't have to apply the diff manually. I am familiar with Java,
>>> but I'm confused since opening the project in GUI mode produces the same
>>> error, yet in the official builds I can open the project just fine. Am I
>>> doing some portion of the build process wrong?
>>>
>>>     Any help is appreciated!
>>>
>>> Nathaniel Kofalt
>>>
>>> ------------------------------------------------------
>>> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2595638
>>>
>>> To unsubscribe from this discussion, e-mail: 
>>> [[email protected]].
>>
>

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

To unsubscribe from this discussion, e-mail: 
[[email protected]].

Reply via email to