robert burrell donkin wrote:
...
daniel - you seem knowledgeable and have an itch: why not try the apache
way?
Maybe because the apparent Apache way of telling users "don't report problems unless you fix them yourself" (e.g., "submit a patch") is pretty annoying.
Even when I submitted specific wording changes (not having the original author figure out the fix; fixing the grammar problem myself except for concretely editing the source file (via a patch)) my problem report was rejected.
the API needs documenting. creating documentation is the best way to
learn the API.
It's also horribly inefficient. Why should a user have to wade through all the implementation details to re-discover the API intent when the developers ALREADY know it? That makes little sense.
When I design an API, I try to fulfill my responsibility and document it sufficiently. The JaxMeXS team has certainly mostly done that; the JavaDoc pages certainly aren't empty. But why are you so resistant to reports of problems?
so what's stopping you?
What's stopping you?
if you really are having problems building from HEAD and that's what stopping you contributing then that's something that we're happy to help with. if it's an issue with the actual build, of course we'll fix it but we need more details of your problems.
It seems to be building now, so I don't know what your problem was the other day.
i'm surprised to hear you're having problems with JIRA. i've used JIRA on several platforms without any real issues. if we had more details we could try to replicate and then raise any issues we couldn't fix with infrastructure. but we need more details.
It looks like the bug-_entry_ page isn't actually a problem.
I think it was the bug-listing page that is (or at least was) horribly wide, forcing one to scroll horizontally or use a full-screen browser window and maybe not even fitting in that for some reasonable screen sizes. It seems designed under the assumption that everyone uses a full-screen window, that users don't use large screens for multiple windows (e.g., searching for or reporting bugs in one, say, half-full-screen-wide window while looking at the bug symptoms being reported in some other window).
Daniel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
