Kosmos is a suite of development project monitoring portlets, developed at JBoss Labs. The JSR-168-compliant portlets are backed by a server component, to track the evolution of various aspects: version control, issue tracker, continuous integration builds and project dependencies. One feature is that they deliver an instant project state view in quasi-realtime.

A picture is worth a thousand words: please take a look at the screenshots!

Version highlights:

• pluggable cached data store (with a default WebDAV implementation out of the box)
• improved UI: expandable long lists, localized chart images
• compatibility with eXo Platform 1.0
• support for secured Subversion repositories
• support for the new SourceForge layout
• localization: French resource bundles
• simplified distribution: binary distribution package with both the server and the portlet components

One of our current near-term goals is to provide localized versions, so we're looking for translators!

Congrats, Aron!

...and congrats on being a winner in the PortletSwap contest.

STAY METAL!
Roy Russo

Thanks, Roy.

I hope a next turn of the contest at Portletswap will attract more participants.
Competitions are good.

Aron Gombas
Founder, http://www.midori.hu
Founder, http://labs.jboss.com/projects/kosmos

Any news on the bugs with this portlet suite on Liferay being fixed?

Good question.
Thing is that the issues you see on http://labs.jboss.com/portal/kosmos/compatibility.html are partly solved. BUG-2 is solved with a nasty trick, BUG-1 is still there, but this one affects only CruiseControl monitoring (this is a very strange bug indeed).

However, there is still a couple of smaller issues to resolve, if you grab the latest HEAD version from the repository, it will work in Liferay environment.
For some kinda perfect port, you have to wait for the next release, but Liferay support in on the top of my priority list.

Aron Gombas
Founder, http://www.midori.hu
Founder, http://labs.jboss.com/projects/kosmos

Thanks very much. Kudos for your product and your extremely speedy response. Can't wait to try it. But are you saying that this binary release doesn't work on liferay at the moment? If at all possible, I don't really want to have to build it from head to get it working :-)

Thanks, Brian.

Well, building it from the sources couldn't be simpler: ant -f build-distro.xml and that's it.
If it helps you, I can upload a binary distro generated from the HEAD some hours later. Also, I can put a Liferay page screenshot online to "prove" that it works ;)

Aron Gombas
Founder, http://www.midori.hu
Founder, http://labs.jboss.com/projects/kosmos

You know Aron, it's responses as helpful and as quick as that that will make your project a huge success.

I'll build it myself if it's that simple, but what I'd say to you is, most developers don't want to have to do that so if you can put up a binary dist and a few lines of how to deploy it on liferay, it will speed up the process of more people trying it out. Screenshots not necessary. I trust you! :-)

Also, once you have done that I think you should post a thread about it on the liferay forums. I think lots of people might be interested in this project there if you tell them about the binary.

Do me a favour and post the link to where you post it whenever you get around to it.

thanks and congrats again.

Brian

Well, to all Liferay users.

You can download a more or less Liferay-compatible preview of Kosmos from our download page: http://labs.jboss.com/portal/index.html?ctrl:id=page.default.downloads&project=kosmos

This is a binary package, so all you have to do is extracting the archive to your /webapps dir. This will add 3 new webapps: Kosmos server, Kosmos portlets and Slide (you can skip this if Slide is already there in your installation).
Please note that this is a preview release, made for Brian's request.

Have fun.

Aron Gombas
Founder, http://www.midori.hu
Founder, http://labs.jboss.com/projects/kosmos

A Liferay screenshot as added at: http://labs.jboss.com/portal/kosmos/images/liferay_portal_page.htm

...and the "announcement" got posted at:
http://forums.liferay.com/index.php?showtopic=3632

That's all, folks.

Aron

Thanks Aaron!

Thanks very much Aaron. That's perfect!

hate to be a pain Aaron, but when I add the portlets to liferay I get the following error:

<code>
com.caucho.hessian.client.HessianRuntimeException: java.net.ConnectException: Connection refused: connect
at com.caucho.hessian.client.HessianProxy.invoke(HessianProxy.java)
at $Proxy143.getProjects(Unknown Source)
at hu.midori.kosmos.portlet.jira.JiraMonitoringPortlet.doView(JiraMonitoringPortlet.java:75)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:235)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:163)
at com.liferay.portal.servlet.PortletServlet.service(PortletServlet.java:78)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510)
at com.liferay.portlet.CachePortlet._invoke(CachePortlet.java:297)
at com.liferay.portlet.CachePortlet.render(CachePortlet.java:155)
at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render_005fportlet_jsp.java:575)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
</code>

I suspect it might be because I not access to the remote jira or something like that. I looked on the reference manual. Do I have to change values in the portlet.xml file by default?

I suspect it might be because I not access to the remote jira or something like that. I looked on the reference manual. Do I have to change values in the portlet.xml file by default?

No, it's not a problem with the service trying to access remote resources (like JIRA or SVN), but it's the Kosmos portlet that cannot connect to service provided by the Kosmos server.

The reason can be:
- the URL from the portlet to the server is not correct (see the service.url <init-param> in portlet.xml). This happens e.g. if your port is not 8080 as the default
- the Kosmos server webapp is not running

Hope this helps. If not, let's move the problem to the Kosmos Forums at http://www.jboss.com/index.html?module=bb&op=viewforum&f=225 , and discuss it there.

Aron

Thanks Aaron. The port number fixed it.

looks cool now!

cheers,
Brian

Glad that it helped. (This issue is probably one of the most popular FAQ items ;))

Have fun.

Aron

Hi,

Has anyone been able to install kosmos on Liferay (Jboss/tomcat) successfully? I am getting lots of exceptions. It would be great if you could post some directions on installation from downloading kosmos to getting it installed.

thanks a ton,
Samit