From: wobbet <nu...@jb...> - 2005-05-07 14:35:42
|
Not disheartened at all. Mildly frustrated but not disheartened... The simple fact that you made the changes is encouraging. I've seen other projects where people pointed out config errors and they were ignored. I ignore those projects :) Is there a way that I can send you email to get some of this off of the forums? I went ahead and downloaded the JBoss IDE and that cleaned up the Log4J errors so that wasn't a bad thing. I figured the IDE download would be a good thing anyway to allow direct debugging of my code. On the Eclipse front, I've found that checking in the .project, .classpath, etc. files can cause difficulties. If you or I make even a minor change to one of those and commits then an update will cause conflicts. When I updated after you said "fixed" Eclipse told me that the .project and .classpath files were no longer valid. My suggestion is that you provide a .tar.gz/.zip file containing the initial Eclipse config as part of the source distro rather than committing it. If someone is using Eclipse they can use that as a starting point and configure with the local changes they need. I think I've found some defects in at least one of the XML files but I'm not 100% certain. Should I send a patch immediately or discuss w/ you first? rjsjr View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876885#3876885 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876885 |