vidrieras: 17 days waiting

vidrieras:

17 days waitin 6g: 17 days waiting...

tomcat 6 + facelets + maven

After creating a project with archetype softeu-archetype-jsf to make the webapp works with tomcat 6 do the following:

In your pom add in the add the following dependencies and repository:

view plainprint?

1.  <dependency>  
2.   <groupid>javax.el</groupid>  
3.   <artifactid>el-api</artifactid>  
4.   <version>1.2</version>  
5.   <scope>compile</scope>  
6. </dependency>  
7. <dependency>  
8.   <groupid>com.sun.el</groupid>  
9.   <artifactid>el-ri</artifactid>  
10.   <version>1.0</version>  
11.   <scope>compile</scope>  
12. </dependency>  
13.   
14.    <repository>  
15.       <url>http://download.java.net/maven/2/</url>  
16.       <id>maven2-repository.dev.java.net</id>  
17.       <name>Java.net Repository for Maven 2</name>  
18.    </repository>  

     
      javax.el
      el-api
      1.2
      compile
    
    
      com.sun.el
      el-ri
      1.0
      compile
    

       
          http://download.java.net/maven/2/
          maven2-repository.dev.java.net
          Java.net Repository for Maven 2
       

Blogger Syntax highlighting

Do exactly what he said.

Maven Surefire (JUnit) specific log4j configuration

To have a log4j configuration specific to your tests, for example if your normal log4 configuration write the logs in a file on server for a webapp, do the following:

1. create a file src/test/resources/test-log4j.properties containing the configuration of log4j for your tests e.g. :
   
   log4j.rootLogger=DEBUG, R
   log4j.appender.R=org.apache.log4j.ConsoleAppender
   log4j.appender.R.layout=org.apache.log4j.PatternLayout
   log4j.appender.R.layout.ConversionPattern=%d{ABSOLUTE} %5p %c{3}:%L - %m%n
   
   
2. Edit your pom.xml like this:
   
   view plainprint?

   1. <build>  
   2.  ...  
   3.  <plugins>  
   4.   
   5.    <plugin>  
   6.      <artifactid>maven-surefire-plugin</artifactid>  
   7.      <version>2.3</version>  
   8.      <configuration>  
   9.        <systemproperties>  
   10.          <property>  
   11.            <!-- Specific log4j config for tests -->  
   12.            <name>log4j.configuration</name>  
   13.            <value>test-log4j.properties</value>  
   14.          </property>  
   15.        </systemproperties>  
   16.      </configuration>  
   17.    </plugin>  
   18.    ...  
   19.  </plugins>  
   20. </build>  

   
   
   
    ...
    
   
      
        maven-surefire-plugin
        2.3
        
          
            
              
              log4j.configuration
              test-log4j.properties
            
          
        
      
      ...
    
   
   
   

   
   
3. Note: my normal log4j.properties is located in src/main/webapp/WEB-INF/classes/.
   

Philosophy

I know what you're thinking, 'cause right now I'm thinking the same thing. Actually, I've been thinking it ever since I got here: Why oh why didn't I take the BLUE pill?
Matrix

Ubuntu kde minimal installation

For a laptop the following packages are necessary:
kde-core
kdpf
kmix
knetworkmanager
kpowersave
gtk-qt-engine (better gtk style in kde, necessary for firefox, thunderbird, eclipse,...)

sudo aptitude install kde-core kdpf kmix knetworkmanager kpowersave gtk-qt-engine

others:
korn
kdesvn

themes:

sudo aptitude install kwin-style-crystal kwin-style-powder kwin-style-blended kwin-style-serenity kwin-baghira kwin-style-alphacube kwin-style-knifty kwin-style-suse2 kwin-style-crystal kwin-style-powder kwin-style-blended kwin-style-serenity kwin-baghira kwin-style-alphacube kwin-style-knifty kwin-style-suse2 kde-style-comix kde-style-polyester kde-style-klearlook kde-style-lipstik kde-style-serenity kwin-baghira  kde-icons-crystal kde-icons-gorilla kde-icons-mono kde-icons-nuovext kde-icons-crystalclear kde-icons-korilla kde-icons-noia kde-icons-nuvola

source(FR)

compiz:
if you compiz for gnome installed:
sudo aptitude install compiz-kde

Gnome: Better autohide

Go to Applications:System Tools:Configuration Editor (or terminal: gconf-editor):

If the panel you want to autohide is at the bottom, choose bottom_panel_screen0
Then change the value of "auto_hide_size" to the number of pixels visible after autohide is in effect
/apps/panel/toplevels/bottom_panel_screen0/auto_hide_size (set to 0)

Hidind delays:
/apps/panel/toplevels/bottom_panel_screen0/hide_delay (set to 200)
/apps/panel/toplevels/bottom_panel_screen0/unhide_delay (set to 200)

source