Wednesday, September 11, 2002

we've got 3 moons? Is This Moon Three? [Slashdot] Crikey, we might have 3 moons. You learn something new every day. 8:52:18 PM    comment []

More on integrating Maven, JIRA and JUnit JIRA-Maven is a very, very cool idea. Thought for the day. Linking JUnit test cases with your bug tracker. I wonder how easy this would be to do with JIRA and a Maven plugin? Should be pretty damn simple. I chatted to Jason a while back about writing a JIRA Service to read the POM and automatically generate projects / versions within JIRA. That would be wicked! (and should only take someone who knows the Maven internals an hour to do!). [snip much useful info on neat JIRA features] Ha! Your wish is my command sir.  What other integration would you like besides the above? (which should all be easy to do!) [rebelutionary] Thanks Mike :-). If we can do all of the above that'd be pretty cool. Incidentally if you didn't know, when you run unit tests in Maven it creates a whole bunch of text and XML files, one per JUnit test case and the file name is the same name as the unit test. The files are all generated in the target/test-reports directory. The XML contains details of the tests, what worked and didn't along with a bunch of other stuff. So it should be pretty simple to write a  Maven plugin, or Ant task or just a bean, that can take these files and pipe them into JIRA to clear any bugs associated with now, working unit tests, or to reopen any bugs due to unit test cases failing. I guess this should happen whenever a distribution or release build is done.   8:17:58 PM    comment []

Maven-Scarab integration too JIRA-Maven is a very, very cool idea. Thought for the day. Linking JUnit test cases with your bug tracker. I wonder how easy this would be to do with JIRA and a Maven plugin? Should be pretty damn simple. I chatted to Jason a while back about writing a JIRA Service to read the POM and automatically generate projects / versions within JIRA. That would be wicked! (and should only take someone who knows the Maven internals an hour to do!). As for your CVS integration idea (taking the CVS log and files changed, and linking directly to the JIRA bug) that is much improved in 1.4 too! (details here)  [rebelutionary] While I do think this is very cool, I'd love to see a bug tracking interface created which any of the trackers could implement. Currently I'm thinking of Scarab but I know there are others beside those two.. Man, I really need to look into Maven more. [josh lucas' Radio Weblog] Of course adding a similar plugin for things like Scarab should be pretty easy to do too. I tend to use JIRA mostly so I'd personally prefer a JIRA plugin first, but once we've got one bug tracker plugin for Maven I'm sure it'd be possible to create others. I generally wanted to start a discussion to see exactly what a Maven <-> JUnit <-> bug tracker integration should look like. 8:10:30 PM    comment []

Goggling on Java Server Faces Googling for thoughts on Java Server Faces. So far, I like what I see of JSF. [Blogging Roller] Thanks for the googling :-). The Struts community has always said they'd migrate to JSTL when its available. It also looks like they'll migrate to JSF too when thats available as well. So I guess ultimately it could turn out that Struts becomes mostly just a front controller for the web application, JSF is the UI event and widget model with plugin renderers and JSTL will be one of the rendering kits 10:49:37 AM    comment []

MS browser monopoly Werblog reports that Netscape's share is now four percent. [Scripting News] So does this statistic also mean that less than 4% of surfers use a Linux/Unix or do these stats only include windows users. Incidentally this entry raised this great but scary comment from Keith Teare IE has become - defacto - a piece of infrastructure. It is no less a gateway to content and services than Windows is a gateway to applications. In the world of web services - where binding the browser to a service will be a decision for Microsoft - the message should be "service-providers beware". As you know, I think that imposes on Microsoft a responsibility to act in a certain way. IMHO what happened to RealNames is the first of an inevitable series of examples of Microsoft leveraging the browser monopoly to resist innovation it does not benefit sufficiently from. Take a look at what happens when you type Keywords in IE now - an MSN search result with paid for links. This is old technology that they own and monetize [search] being favored by Microsoft against a new innovation that they neither own nor 100% monetize [natural language navigation]. 8:00:30 AM    comment []