All the window managers mentioned above have their own peculiarities and features. I don’t want to go into the details of each one so,  here is the archlinux wiki page which compares the different tiling window managers.

My choice fell on xmonad. It has several reasons. The first being it looks awesome (no pun intended). The second being the language behind it, yes haskell[2].  The configuration file is also written in haskell, with which it is possible to customize and  extend the basic features provided by xmonad.  It  surely is a challenge to learn a fresh new language to be able to understand the configuration file and  to customize. This actually was a plus point for me because  I already had heard  many interesting things about haskell, so  I wanted to learn it to have a feel of  a lazy and purely functional language.  So, xmonad being a new paradigm window manager for me, it was also an opportunity for me to start learning haskell.

Some screenshots to give you  a feel of what I am talking about.

Xmonad clean with conky, dzen , conky, mpd, weather status bar

Xmonad running tmux and vim editing the primary configuration file of xmonad.

Xmonad is a very efficient dynamic tiling window manager which is very slim in terms of memory usage. Although the core part is relatively plain in terms of features, there are plenty of extensions which could be used to take advantage of different features.  Although for me it was an interesting  opportunity to start learning  haskell and understand the config file,  it is not at all necessary to learn haskell to configure xmonad. There are many example configurations available on the xmonad site with screenshots.  The xmonad config file is generally well  readable, so it is possible and often recommended  to initially copy an example configuration and keep on modifying it until you get it customized to your needs. I also liked the way xmonad handles multiple screens. Actually in the beginning it felt a bit  strange, but after some experience with it,  it is so  intuitive, that you would not like multiple screen handling of any other window manager.

This  is  my config file which is more or less a basic configuration with some changes.  Please feel free to suggest any improvements or changes. I have started learning haskell by following the book Real World Haskell, which in my opinion is a very good book for beginners. Please feel free to suggest any other useful resources for that as well.  I hope I will be able to use more of xmonad and fix some issues I am having with it.

On the cons side, xmonad doesn’t handle swing (java) based applications very well. There is a workaround in the config file by setting the param  setWMName  to “LG3D” to get it working.  I am still  having problems related to focusing with eclipse java IDE.  I am looking for a solution to this issue.

Links:

1. Window Managers

2. Haskell

We now come to the model and action modules which are of type ejb. Particularly in this example (Open18) they are just seam components i.e. pojos  annotated with @Name, but they could also have been ejbs.

Bellow is the pom.xml for model module. It contains all the entities (JPA)  and some helper classes. It shows jboss-seam as provided dependency which will be provided by the ear module which packages the artifact which will be deployed. This modules takes all the hibernate dependencies from the parent project.

<project xmlns="http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"&gt;
  <parent>
    <groupId>com.hardik.seaminaction</groupId>
    <artifactId>Open18</artifactId>
    <version>1.0-SNAPSHOT</version>
  </parent>
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.hardik.seaminaction</groupId>
  <artifactId>model</artifactId>
  <packaging>ejb</packaging>
  <version>1.0-SNAPSHOT</version>
  <name>model</name>
  <url>http://maven.apache.org</url&gt;
  <dependencies>
      <dependency>
            <groupId>org.jboss.seam</groupId>
            <artifactId>jboss-seam</artifactId>
            <version>2.2.0.GA</version>
            <type>ejb</type>
            <scope>provided</scope>
        </dependency>
  </dependencies>
  <build>
  	<plugins>
  		<plugin>
  			<groupId>org.apache.maven.plugins</groupId>
  			<artifactId>maven-ejb-plugin</artifactId>
  			<configuration>
  				<ejbVersion>3.0</ejbVersion>
  			</configuration>
  		</plugin>
  	</plugins>
  </build>
</project>

Here the action module which is also of type ejb. It contains all the action classes which are in turn pojos annotated with @Name. The JSF dependency which we see is for the JSF message classes.

<project xmlns="http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"&gt;
  <parent>
    <groupId>com.hardik.seaminaction</groupId>
    <artifactId>Open18</artifactId>
    <version>1.0-SNAPSHOT</version>
  </parent>
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.hardik.seaminaction</groupId>
  <artifactId>action</artifactId>
  <packaging>ejb</packaging>
  <version>1.0-SNAPSHOT</version>
  <name>action</name>
  <url>http://maven.apache.org</url&gt;
  <dependencies>
      <dependency>
          <groupId>com.hardik.seaminaction</groupId>
          <artifactId>model</artifactId>
          <version>1.0-SNAPSHOT</version>
      </dependency>

      <dependency>
            <groupId>org.jboss.seam</groupId>
            <artifactId>jboss-seam</artifactId>
            <version>2.2.0.GA</version>
            <type>ejb</type>
            <scope>provided</scope>
        </dependency>
      <dependency>
            <groupId>javax.faces</groupId>
            <artifactId>jsf-api</artifactId>
            <version>1.2_02</version>
            <scope>provided</scope>
        </dependency>

  </dependencies>
  <build>
  	<plugins>
  		<plugin>
  			<groupId>org.apache.maven.plugins</groupId>
  			<artifactId>maven-ejb-plugin</artifactId>
  			<configuration>
  				<ejbVersion>3.0</ejbVersion>
  			</configuration>
  		</plugin>
  	</plugins>
  </build>
</project>

Links:

1. Mavenising seam projects [ part 1 ].

Maven on the other hand is emerging as the de-facto building tool for java. As I have already mentioned before, maven gives you a very good overview of your project and you are not lost in minor details. Those details are automatically taken care of. With seam projects, maven is especially useful because you know which dependencies are needed.

When I started learning seam, by reading the very popular book Seam in Action by Dan Allan [5], I had already switched to maven for all my projects. I decided to mavenise the examples of the book. There are many such projects. The seam documentation also points to the seam-maven-refimpl project [6] which provides a nice template for any seam project. As I wanted to find out how the maven implementation a seam project differs from that of a standard java EE project first hand, I didn’t use the template provided by this project. I just started with a standard java EE project and started adding seam dependencies to it, until I had a working example.

The implementation  can be found here. Please feel free to point out any mistakes or suggest improvements to th code.

I have also tried to convert the first examples of the book Seam 2.x Web Development by David Salter [7]. These examples are very simple i.e. without persistence, richfaces etc, although they use state less session beans.

Here I will discuss the Open18 example from the Seam In Action book in detail.

Here is the pom file of the main parent project which is no different from an ordinary Java EE project. The only seam specific thing is the jboss repository entry at the end.

<?xml version="1.0" encoding="UTF-8"?>
xmlns="http://maven.apache.org/POM/4.0.0&quot;
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"&gt;
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.hardik.seaminaction</groupId>
  <artifactId>Open18</artifactId>
  <packaging>pom</packaging>
  <version>1.0-SNAPSHOT</version>
  <name>Open18</name>
  <url>http://maven.apache.org</url&gt;
  <modules>
  	<module>action</module>
  	<module>model</module>
    <module>war</module>
    <module>ear</module>
  </modules>
  <build>
  	<plugins>
  		<plugin>
  			<groupId>org.apache.maven.plugins</groupId>
  			<artifactId>maven-compiler-plugin</artifactId>
  			<configuration>
  				<source>1.6</source>
  				<target>1.6</target>
  			</configuration>
  		</plugin>
  	</plugins>
  </build>
  <dependencyManagement>
  	<dependencies>
  		<dependency>
  			<groupId>com.hardik.seaminaction</groupId>
  			<artifactId>ear</artifactId>
  			<version>1.0-SNAPSHOT</version>
  		</dependency>
  		<dependency>
  			<groupId>com.hardik.seaminaction</groupId>
  			<artifactId>war</artifactId>
  			<version>1.0-SNAPSHOT</version>
  		</dependency>
  		<dependency>
  			<groupId>com.hardik.seaminaction</groupId>
  			<artifactId>action</artifactId>
  			<version>1.0-SNAPSHOT</version>
  		</dependency>
        <dependency>
  			<groupId>com.hardik.seaminaction</groupId>
  			<artifactId>model</artifactId>
  			<version>1.0-SNAPSHOT</version>
        </dependency>
  	</dependencies>
  </dependencyManagement>
    <dependencies>
        <!-- hibernate dependencies with provided scope -->
    </dependencies>

   <repositories>
  	<repository>
  		<id>jboss</id>
  		JBoss Repository
        <url>http://repository.jboss.org/maven2/</url&gt;
  	</repository>
  </repositories>
</project>

Links:

1. Seam
2. Contexts and Dependency Injection in Java EE 6 (JSR 299)
3. Google Guice
4. Spring framework
5. Seam in action
6. Seam maven reference implementation
7. Seam 2.x Web Development

Tagged: cdi, Java, javaee, jboss, jsr 299, jsr299, maven, seam, seam framework, seamframework ]]> http://hardikmehta.wordpress.com/2010/03/07/mavenising-seam-projects-part-1/feed/ 1 hardikmehta http://hardikmehta.wordpress.com/2010/03/07/switched-to-archlinux/ http://hardikmehta.wordpress.com/2010/03/07/switched-to-archlinux/#comments Sun, 07 Mar 2010 13:24:25 +0000 hardikmehta http://hardikmehta.wordpress.com/?p=514 ]]> At last a new post after a long time !

Lately, I was very busy with real life issues and concerns so could not find time to write.

In spite of being a fan of debian [1], I decided to change my operating system. I was completely happy  with sidux [2] which is essentially debian sid with a pinch of spice, but wanted to try something new and different. I had heard a lot of good things about Archlinux [3]. First I decided to try it on a virtual machine and was impressed by the simplicity of the system. It is highly configurable and yet simple when it comes to configuring it to your taste.  For me the common thing is that sidux and Archlinux both are rolling distributions.  Arch claims to be optimized for i686, so at least theoretically it should be faster than sidux. Though,  I don’t have any benchmarks to support this. Debian has may be the highest number of binary packages available, but Arch has AUR [4] and ABS [5], so it becomes easy to compile a package from sources.

Another reason, I switched to Arch was that I was experimenting with lightweight window managers like fluxbox, openbox, dwm, xmonad etc. The community at Archlinux provides a great support and knowledge base for them. In fact I got encouraged to try those window managers by browsing through the screenshot threads in the Archlinux forums. On the other hand, sidux officially  supports only Kde, and I somehow felt that the community at sidux discourages the use of alternatives to kde and also other lightweight applications.

Although, it was not GUI based like sidux, the installation of Arch went rather smoothly. Archwiki [6] is an indispensable resource. I have a 4 years old Dell Inspiron 6000. The system seems to run smoothly. There are less daemons running compared to sidux, so the boot time is less. I have more or less the same setup as my sidux installation with openbox as main window manager and kde 4 as a fallback ! I am also maintaining my plasmoid plasma_pyweather [7], so I don’t want to get rid of kde altogether.

I don’t know yet, if I will continue with Arch or go back to sidux again. I have realized that you need to read all the messages carefully when you upgrade the system with pacman, this was also true for sidux, but the forum with upgrade warning was a great help.  Anyway, I hope to post interesting things about my experience using Arch.

Here some screenshots for those who want to see it to believe.

Arch clean

Arch dirty

Links:

1. Debian GNU/Linux
2. sidux
3. Arch Linux
4. Arch User Repository
5. Arch Build System
6. Arch Wiki
7. A weather plasmoid in python

Tagged: arch linux, archlinux, debian, Linux, sidux ]]> http://hardikmehta.wordpress.com/2010/03/07/switched-to-archlinux/feed/ 1 hardikmehta Arch clean Arch dirty http://hardikmehta.wordpress.com/2009/09/12/maven-dependencies-for-a-basic-jsf-project/ http://hardikmehta.wordpress.com/2009/09/12/maven-dependencies-for-a-basic-jsf-project/#comments Sat, 12 Sep 2009 07:52:02 +0000 hardikmehta http://hardikmehta.wordpress.com/?p=497 ]]> With some search and experiments, I figured out the following maven dependencies for a basic JSF project. These dependencies also allow autocompletion of JSF tags in the IDEs like eclipse and intellij idea. I post this for my own reference and may be someone searching for it.

<project xmlns="http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"&gt;
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.hardik.jsfinaction</groupId>
  <artifactId>HelloJsf</artifactId>
<packaging>war</packaging>
  <version>1.0</version>
  <name>HelloJsf Maven Webapp</name>
  <url>http://maven.apache.org</url&gt;
  <dependencies>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>4.0</version>
      <scope>test</scope>
    </dependency>
    <dependency>
        <groupId>jstl</groupId>
        <artifactId>jstl</artifactId>
        <version>1.1.2</version>
        <scope>compile</scope>
    </dependency>
    <dependency>
        <groupId>javax.faces</groupId>
        <artifactId>jsf-api</artifactId>
        <version>1.2_02</version>
        <scope>compile</scope>
    </dependency>
    <dependency>
        <groupId>javax.faces</groupId>
        <artifactId>jsf-impl</artifactId>
        <version>1.2-b19</version>
        <scope>compile</scope>
    </dependency>
    <dependency>
        <groupId>taglibs</groupId>
        <artifactId>standard</artifactId>
        <version>1.1.2</version>
        <scope>compile</scope>
    </dependency>
    <dependency>
        <groupId>javax.el</groupId>
        <artifactId>el-api</artifactId>
        <version>1.0</version>
        <scope>provided</scope>
    </dependency>
  </dependencies>
  <build>
    <finalName>HelloJsf</finalName>
<plugins>
<plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <configuration>
                <source>1.6</source>
                <target>1.6</target>
            </configuration>
        </plugin>
<plugin>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>tomcat-maven-plugin</artifactId>
            <configuration>
                <server>tomcat</server>
            </configuration>
        </plugin>
    </plugins>
  </build>
</project>

Even though, I didn’t know PyQT4 or PyKDE4 libraries at all, I decided to write my first plasmoid in python.  This is an exremely simple plasmoid, the core of which was put together in a few hours on a rainy weekend. I have to admit that being a java developer, my code is not pythonic enough.

It can be downloaded from: kde-look.

Here the source code: plasma_pyweather.

The layout is based on my conky setup described here. I have tried to keep it as compact as possible including most of the provided information, if not all.  I don’t want the weather information to cover most of the screen.  The initial version of the plasmoid was written using the QT4 widgets, but was looking ugly.

The weather information is fetched from google weather api. The location and the unit are configurable. The api provides forecast only for the next 3 days, so the number of forecast days were not made configurable.  Some how for google weather api the locale and so the unit is connected to the language, therefor  I had to convert the units myself. To keep the display compact I rounded the temperatures to integers.

I got to learn PyQT4 and PyKDE4 libraries while writing this. Especially PyQT4 is a very powerful gui library for python.  It is fun programming with it. I have used eclipse + pydev for developing. In the beginning I didn’t have the auto-completion for PyQT4 as well as PyKDE4 in this environment, because they are not installed as pure python source code files. I could fix this with following answer.

The other interesting things, I learned was to use the qt-designer tool for creating gui. It is a nice WYSIWYG tool for designing complex guis. The configuration form is designed using this tool. The qt-designer creates a .ui file, which is an xml file. The .ui file can be converted to the python source code using the pyuic4 tool in the following way.

pyuic4 -o configForm_ui.py ../ui/configForm.ui

I also learned to use the .qrc file for resources like images. The .qrc file can be converted into python source code using  pyrcc4 tool

pyrcc4 -o images_rc.py images.qrc

The qrc file is also an xml file which contains the references to the images used. It can be created by just editing.

<RCC>
    <qresource prefix="/images">
        <file alias="sunny.svgz">../images/sunny.svgz</file>
        <file alias="showers.svgz">../images/showers.svgz</file>
        <file alias="not-available.svgz">../images/not-available.svgz</file>
        <file alias="cloudy.svgz">../images/cloudy.svgz</file>
        <file alias="thunderstorms.svgz">../images/thunderstorms.svgz</file>
        <file alias="haze.svgz">../images/haze.svgz</file>
        <file alias="windy.svgz">../images/windy.svgz</file>
    </qresource>
</RCC>

I decided to write this weather plasmoid in python, because all the other weather plasmoids I found were binaries. I have also tried to keep the data and presentation layer separate, I hope I succeeded in that.  In fact plasma framework provides a very good way of doing that in terms of data engines. I would also like to use the data engines, may be with this or other plasmoid I may develop.

The svg images for weather conditions are taken from kde-look. The credit goes to the original artist, painkiller10. I have considered only a number of weather conditions, so If you see a question mark image as the weather condition, let me know which condition it is, so I can update the code to consider it.

Please feel free to report any bugs or suggestions for improvement. I am sure there is a big room of improvement from code point of view as well as functionality. I am also open for changing the layout or changing the information displayed if someone comes with a better suggestion than the current one.

Some more screen shots:

Looks almost like conky with the seamless theme.

With settings dialog box

Tagged: desktop, eclipse, forecast, gadget, google weather api, kde4, plasmoid, pydev, pykde4, pyqt4, Python, python-plasmoid, qt4, weather, widget ]]> http://hardikmehta.wordpress.com/2009/08/13/a-weather-plasmoid-in-python/feed/ 19 hardikmehta wplasmoid_greytrans wplasmoid_seamless-tmb wplasmoid_settings http://hardikmehta.wordpress.com/2009/08/04/a-script-to-display-weather-forecast-for-conkyconky-screen-shot/ http://hardikmehta.wordpress.com/2009/08/04/a-script-to-display-weather-forecast-for-conkyconky-screen-shot/#comments Tue, 04 Aug 2009 06:35:00 +0000 hardikmehta http://hardikmehta.wordpress.com/?p=400 ]]>

Conky is undoubtedly the most configurable, versatile and amazing program I have ever come across.  With very little effort you can get a very sleek looking desktop. I have seen people using it to display all kinds of information under the sky.  Although, it can only display pure text, there is a possibility to use different symbolic fonts to display text based images.  Moreover, it is also very efficient program. Its own footprint is very small compared to most of the gadget frameworks like adesklets, gDesklets and of course plasma.  Configuration is also relatively easy. The best way is to copy configuration file from some one else and keep on changing it until you get what you want.  Another application worth mentioning here is dzen2. Dzen2 has ability to render any text graphically, although it lacks the built in variables of conky. In archlinux there is an application package called conky-cli which is a stripped down version of conky without X11 dependency. A combination of conky-cli and dzen2 is then used to make taskbars for minimalistic desktops like xmonad, wmii, dwm etc. Personally, I haven’t tried this combination yet.

Ubuntu and Archlinux forums have dedicated threads with conky screen shots and config files. I came across many screen shots with weather information, forecast and small symbols with weather conditions. Most of them were using a perl script (for which I cannot find the link now) to fetch, parse and show the weather information from weather.com.  The weather symbols were ttf fonts.  I didn’t want to take the script one-to-one and perl is anyway too cryptic for me to  decipher. I decided to take the concept and develop something similar on my own.

So I created the google weather script. It is a simple bash script to fetch the xml file using google weather api, I changed the source because although weather.com was providing good information, they were changing the format of the request too often, their terms and conditions of usage were also not very comprehensible for me. Then I use different style-sheets to process the xml response and show different information depending on the argument passed to the bash script. I also use the weather.ttf fonts to render the symbols for different weather conditions.  For transforming xml, I use the xsltproc tool.

Here is the conky running under kde4 desktop. With different desktop environments       conky needs to be adjusted  a bit. Another weakness of conky in integrating external scripts is that the output must be pre-formatted before supplying it to conky. Conky just takes the text and renders it.  In principle any executable can be called from conky to display its output.

Conky has many built-in variables for displaying common system parameters which are well documented on the official documentation page. Besides the common parameters like cpu / memory usage, uptime, upload-download speed, top 3 cpu using processes and top 3 memory using processes, the screen shot on the left also displays the dictionry.com word of the day rss feed, which I find extremely useful. It also uses a similar script and xslt transformation. There is also a built-in rss feed processor in conky.

I use mpd for playing music. There is also built-in mpd support in conky and can be used to display information about current song being played. If you want to show different information at different places on the desktop, it is also possible to have multiple instances of conky running at the same time with different configuration files.

As evident  in the screen shot it is difficult to adjust the spacing of the weather output due to mixing of different types and sizes of  fonts.  My script only considers some frequent weather conditions, but it can easily adapted to support many different weather conditions.  The spacing must be adjusted for individual setup by editing the line no. 16 in the  file fcConditions.xslt

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform&quot; version="1.0" >
    <xsl:include href="conditionsInclude.xslt"/>
    <xsl:output method="text" disable-output-escaping="yes" encoding="utf-8"/>
    <xsl:template match="xml_api_reply">
        <xsl:apply-templates select="weather"/>
    </xsl:template>

    <xsl:template match="weather">
        <xsl:for-each select="forecast_conditions[position() >= 2]">
           <xsl:call-template name="get-condition-symbol">
                <xsl:with-param name="condition">
                    <xsl:value-of select="condition/@data"/>
                </xsl:with-param>
            </xsl:call-template>
            <xsl:if test="position() != 3">
                <xsl:text> </xsl:text>
            </xsl:if>
        </xsl:for-each>
    </xsl:template>
</xsl:stylesheet>

I have hard-coded the update interval to 1 hour. This can also be changed very easily to the required value by changing the value of the update variable in the weather.sh file.

# don't get the file if created within an hour
update=3600

I use mainly following configurations for conky.

• Configuration for fluxbox / openbox.
• Configuration for kde4.
• Configuration for mpd.

I have released the script with GPL V3 license, so feel free to use it if you like it. Please comment about any bug reports, improvements, questions or suggestions.

Tagged: bash, conky, desktop, fluxbox, gadget, google weather api, kde, kde4, Linux, openbox, plugin, weather, weather forecast, widget, xml, xslt, xsltproc ]]> http://hardikmehta.wordpress.com/2009/08/04/a-script-to-display-weather-forecast-for-conkyconky-screen-shot/feed/ 8 hardikmehta conky screen shot http://hardikmehta.wordpress.com/2009/07/30/created-a-repository-with-github-for-storing-sharing-config-files/ http://hardikmehta.wordpress.com/2009/07/30/created-a-repository-with-github-for-storing-sharing-config-files/#comments Thu, 30 Jul 2009 19:56:20 +0000 hardikmehta http://hardikmehta.wordpress.com/?p=403 ]]> I noticed that since long time dotfiles.org website which I used to store and share my config files was unreachable.  So I created a repository with github. It is called dotfiles. I will update all the links pointing to my configs files to the new location. If you still notice some old links please drop a comment.

Update:

The issue has been fixed. There were two points.

1. I was using the wrong (deprecated) goal archetype:create instead of archetype:generate.

2. With the plugin archetype-j2ee-simple there is a bug which is already reported here.

I got my answer from Antony Stubbs on Stackoverflow.

At last I also decided to join the maven[1] bandwagon, I will start using maven for managing my projects. Convention over configuration  sounds  indeed a nice idea.  When I first heard about maven  I didn’t have a good “feeling” about it, may be because I was too comfortable with ant and believe to be able to achieve any task with it. But now after reading some documentation and articles about maven, I came to realise it is completely new paradigm than ant. In my opinion the best aspect of maven is that you always have the big picture of your project in mind instead of a small task or operation to be done.  I started liking maven and  also started learning it.  For reference I have started following  Maven: The Definitive Guide[2]. Another great advantage could be that if you know maven and a join a new team which also uses maven for project management, you don’t have to spend hours or may be days trying to figure out the structure of their project and being able to build it.

Although I started liking maven, sometimes it feels like a strange tool, where you have to configure a lot to achieve your goal. if you want some custom stuff in your project. I also find it annoying that by default the compiler-plugin assumes you want to build for java 1.4 or java 1.3.  Moreover, because there are always so called sensible or obvious defaults assumed, in maven world, not all the obvious defaults are obvious to you and you have to know the documentation well to be able to know what those defaults are. and how you can achieve something different. It feels somewhat like javadocs, until you get used to the apis you need frequently, you have to rely on auto-completion of your IDE or have the javadoc always open. There is no wonder that the second part of the book, I mentioned contains only the maven reference.

But, yes, I am here to talk about the quirk of maven which I encountered during my learning process. I am just a maven beginner, so may be this is normal behavior, but I don’t think so.

So, while starting to learn maven, I started with a contrived JavaEE application (brave huh), which is taken as example in the very good book EJB 3 in Action[3]. I searched the net and found out about the maven archetype j2ee-simple here. I used following commandline to generate the stubs of a simple JavaEE project, actually I was interested in the standard directory structure.

mvn archetype:create -DgroupId=com.hardik -DartifactId=ActionBazaar -DarchetypeArtifactId=maven-archetype-j2ee-simple

The project was created perfectly, but by default it was not compiling. When I executed mvn intall I had following errors.

$ mvn install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: unknown

Reason: Could not find the model file '/home/hardik/projects/ActionBazaar/site'. for project unknown

[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Could not find the model file '/home/hardik/projects/ActionBazaar/site'. for project unknown
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:432)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:300)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
    at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Could not find the model file '/home/hardik/projects/ActionBazaar/site'. for project unknown
    at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1575)
    at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
    at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
    at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:632)
    at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:515)
    at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:588)
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:419)
    ... 12 more
Caused by: java.io.FileNotFoundException: /home/hardik/projects/ActionBazaar/site (No such file or directory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:106)
    at hidden.org.codehaus.plexus.util.xml.XmlReader.<init>(XmlReader.java:124)
    at hidden.org.codehaus.plexus.util.xml.XmlStreamReader.<init>(XmlStreamReader.java:67)
    at hidden.org.codehaus.plexus.util.ReaderFactory.newXmlReader(ReaderFactory.java:118)
    at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1570)
    ... 18 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Thu Jul 09 18:44:31 CEST 2009
[INFO] Final Memory: 1M/4M

[INFO] ------------------------------------------------------------------------

It is talking about some model file for the site module. The site module is generally the “website” of your project that maven generates just by looking at your pom.xml file. I removed the site module from the module list of the pom file and it started working. But I still wonder why the default project structure doesn’t build. I am sure this is incorrect behavior.

If someone has had the same problem, and was able to fix, please let me know.

References:

1. Apache-maven
2. Maven: The Definitive Guide
3. EJB 3 in Action

session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,com.sun.enterprise.jst.server.sunappsrv,1.0.28
No repository found containing: org.eclipse.update.feature,com.sun.enterprise.jst.server.sunappsrv.feature,1.0.28

After searching a lot I found a way to install it using the update site http://ajax.dev.java.net/eclipse, like any other plugin. This worked well.

May be the problem is temporary and after sometime the standard way will also start working.