[Design the new POJO MicroContainer] - Re: Update the relevant .classpath files
by ALRubinger
"adrian(a)jboss.org wrote : It's not a vote. Either make a logical argument or go join some Apache project where you can make these usless comments to your hearts content. :-)
We get it, Adrian, you're intimidating.
I'll spell it out, then.
Adding .classpath and .project files to the repo might seem like a convenience to users of the Eclipse IDE, but actuality what we're doing here is introducing elements that are unbound to actual changes in the POM, and may be misleading.
By guaranteeing a build that will function from the command-line only, we add a fail-fast; compilation WILL fail in IDEs. It becomes the responsibility of the developer to add extensions to make it work in their preferred environment. And with the maven commands I've illustrated, it's incredibly simply to do so with Eclipse. We can even bind it to the build lifecycle in an Eclipse profile if we'd like.
Generated code in a central repo is redundant and easily outdated. And users of IntelliJ (like Ales) shouldn't have to worry about the CP of Eclipse users.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133287#4133287
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133287
16 years, 11 months
[Design the new POJO MicroContainer] - Re: Update the relevant .classpath files
by adrian@jboss.org
"alesj" wrote : OK, I definitely don't want to see you loosing too much time doing this stuff :-), but I fail to see how this is relevant.
|
| e.g. you get your updated .classpath from svn
| or you get updated pom from svn, close Eclispe (so you're not pulling the rug), run the maven-ide generator, open Eclipse
|
Because, I get an error when I load eclipse when it can't find the method/class/jar.
I fix it, and then I've might have to fight eclipse's incremental compiler
because I missed a step in some many stage svn update procedure.
We've had this discussion before. What I really want is maven to automatically
run mvn eclipse:eclipse when it detects the .classpath is earlier than
the pom.xml. That way any developer modifying the poms will
automatically check in updated .classpath files and it doesn't become
an "infinite stage" process to get a working development environment
after an svn update as I try to figure out what changed
what I need/forgot to rerun and what eclipse thinks is going on.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133278#4133278
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133278
16 years, 11 months
[Design of OSGi Integration] - Re: Logging and Exception Handling
by adrian@jboss.org
"johnbailey" wrote :
| I would also like to know if there are any ground rules on logging and Exception handling to follow.
They're on the WIKI somewhere.
Basically:
ERROR - if a system admin would need to know (but only if you handle the error - don;t log and rethrow that just leads to duplicate logging!)
WARN - may be a problem but you can recover
INFO - is this something somebody is likely to find really useful?
DEBUG - deployment time or other low volume logging
TRACE - Everything else you might need to understand what happened
e.g. in your example
| public URL getEntry()
| {
| try
| {
| ...
| }
| catch (Exception e)
| {
| if (log.isTraceEnabled())
| log.trace("Error getting entry: " + entry, e);
| return null;
| }
| }
|
Dont use isXEnabled for anything but TRACE.
All other logging should be such low volume that it isn't necessary
and probably redundant.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133264#4133264
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133264
16 years, 11 months