Menu

Software & DevOps

New Site New Focus

/

It’s been a while since I last posted anything and the site has been quite stale and out dated. So I thought I’d update it to a more modern responsive site that looks good on both desktop and mobile. As I wanted to focus more on actual writing and less on building a site I […]

The post New Site New Focus appeared first on Javaguru.

Continue reading...

Monitoring and Graphing Liferay with MRTG

/

dbpool.png

MRTG (The Multi Router Traffic Grapher) is usually used to monitor SNMP enabled network devices and draw graphs of how much traffic has passed through each interface. It can also be used to graph any two values (in/out) and I use it for graphing cpu usage, loadavg, iowait, used memory, disk space and temperature sensor […]

The post Monitoring and Graphing Liferay with MRTG appeared first on Javaguru.

Continue reading...

Liferay Maven Support in Liferay 6.1 GA3

/

We’ve finally released both CE and EE versions of Liferay 6.1 GA3 and along with those releases we’ve also released the corresponding versions of Liferay Maven Support and Portal artifacts. The version numbers are 6.1.2 for CE GA3 and 6.1.30 for EE GA3. With this release there is one significant improvement in the Liferay Maven Plugin and that is they are no longer directly dependent on a Liferay Portal version. We could have just released one version and it would have worked with either portal version, in fact they both work with any portal version starting from 6.1.0. In the future we will probably move to a single release of Liferay Maven Support which will eventually have it’s own release cycle completely independent of the portals release cycle.  

All the archetypes will now have a separate property for Liferay Maven Plugin version called liferay.maven.plugin.version. The plugin will also now require you to tell which portal version you are developing against and you’ll do that by providing it liferayVersion in the configuration section. Here’s a example from liferay-theme-archetype:




	<plugin>

	  <groupId>com.liferay.maven.plugins</groupId>

	  <artifactId>liferay-maven-plugin</artifactId>

	  <version>${liferay.maven.plugin.version}</version>

	  <executions>

	    <execution>

	      <phase>generate-sources</phase>

	      <goals>

	        <goal>theme-merge</goal>

	        <goal>build-css</goal>

	        <goal>build-thumbnail</goal>

	      </goals>

	    </execution>

	  </executions>

	  <configuration>

	    <autoDeployDir>${liferay.auto.deploy.dir}</autoDeployDir>

	    <appServerDeployDir>${liferay.app.server.deploy.dir}</appServerDeployDir>

	    <appServerLibGlobalDir>${liferay.app.server.lib.global.dir}</appServerLibGlobalDir>

	    <appServerPortalDir>${liferay.app.server.portal.dir}</appServerPortalDir>

	    <liferayVersion>${liferay.version}</liferayVersion>

	    <parentTheme>${liferay.theme.parent}</parentTheme>

	    <pluginType>theme</pluginType>

	    <themeType>${liferay.theme.type}</themeType>

	  </configuration></plugin>



	Please remember that the plugin will still be affected any bugs in the Liferay Portal Version so if you have patches installed you should point the plugin to a patched portal bundle by setting the liferay.app.server.xxx properties. If you discover any bugs in any of the plugin mojos please report them to our MAVEN Jira project.


                
                    
Continue reading...


            
            
        

        
	

	
	
	



                    

            
«‹ 2 3 4 5›»