- Project tools
-
-
- Using ArgoUML
-
- How do I...
-
| Category |
Featured projects |
| scm |
Subversion,
Subclipse,
TortoiseSVN,
RapidSVN
|
| issuetrack |
Scarab |
| requirements |
xmlbasedsrs |
| design |
ArgoUML |
| techcomm |
SubEtha,
eyebrowse,
midgard,
cowiki |
| construction |
antelope,
scons,
frameworx,
build-interceptor,
propel,
phing
|
| testing |
maxq,
aut
|
| deployment |
current |
| process |
ReadySET |
| libraries |
GEF,
Axion,
Style,
SSTree
|
| Over 500 more tools... |
|
The Tigris site will receive a major upgrade the evening of Monday, December 1, beginning at 8:30 pm PST. Downtime is projected to be about ten hours.
Further details in the announcement
How to report bugs and register enhancements
| Search database |
|
| Jump to issue |
|
| Prerequisites |
To enter an issue, you must register at the Tigris website, and log in.
To be able to make any change to existing issues,
you have to apply for an
Observer role in the ArgoUML project and get it granted.
Register,
Log in, and
Apply for an Observer role
|
|
Report a bug in ArgoUML
|
Step by step instruction on what to do:
- Search for the problem among the problems in
the
Issuezilla database.
- If found, add yourself as CC to the Issue and vote for it.
You can then monitor its progress. You are done.
This also qualifies you for closing the issue.
- If your problem is not found or some of your peculiarities
or details is not included in the description, go on.
- Enter a new issue
or add information to an already existing issue.
Be sure to include
what version of ArgoUML you are running,
what version of jdk,
all the steps that lead up to this,
what happens, and
what you expected to happen.
- Add attachments with more information to your newly created issue
by revisiting it and clicking Create a new attachment.
The extra information that might be relevant for the issue
as attachments is
screen shots,
your project file,
log files...
If the problem is repeatable, rerun with debug logging enabled
(java -Dlog4j.configuration=org/argouml/resource/full.lcf -jar argouml.jar)
and add the log file argo_full.log from your home
directory as attachment.
You will get updates via mail when someone comments or does
something with your issue.
If nothing happens, you can solve the issue yourself and describe
the solution in the issue.
When the issue is resolved or verified,
close it after you have accepted the solution.
The life-cycle of issues and the roles of people handling them
is described in the
Cookbook Chapter 9.
Don't forget to
vote
for the issues that you really care about.
|
|
Suggest an enhancement
|
This is if you have suggestion on more things that you think ArgoUML
should do for you that it currently does not do.
Consider it our common wish list.
Don't forget to
vote
for the enhancements that you really care about.
|
|
Report a bug on the web site
|
This is when you find errors among the things present on the web site.
|
| My issues |
View both active issues assigned to you and those that you have entered.
|
| Reports |
Generate and view issue tracking reports.
|
Why you should do this
By reporting bugs you are contributing to the ArgoUML project and
your help will lead to making ArgoUML a better product.
By voting you are showing your interest and help the developers
get a good idea of what is important and what is not.
This is one of the sources of inspiration for the people in the project.
By suggesting enhancements you are contributing ideas for some
future version of ArgoUML.
If you want to contribute even more to the project
you could start solving issues.
For details read through the Developer Zone and
especially the Cookbook
Section 1.3.
|