« Back to Development...

Development Environment (Windows)

The intent of this article is to explain what Liferay Portal is and get Java developers set up, running, and off to productivity as soon as possible on the Windows operating system. It is high level and it not intended to answer in-depth questions. However, there will be details provided on how to install certain files and complete installation tasks that are required.

Liferay in a Nutshell #

Liferay Portal is a web application. In a nutshell, you can think of as the portal as one big servlet. It is a servlet that happens to be a portlet container. The portal source builds this portlet container using the Ant build tool and the JDK.

Required Files #

Download all of these files below and set aside for installation. They are all required for the development environment. Some of these tools, you can use alternatives. You can use IntelliJ instead of Eclipse, for example, but for the sake of simplicity of this article, we will stick with the below:

JDK 5 #

Download the JDK here: http://java.sun.com/javase/downloads/index jdk5.jsp

What you want is (as of Oct 2007) "JDK 5.0 Update 13". Click on the "Download" button. After accepting the agreement. Choose "Windows Offline Installation, Multi-language".

Ant 1.7 #

Download Ant 1.7 here: http://apache.eu.lucid.dk/ant/binaries/apache-ant-1.7.0-bin.zip

Jikes 1.22 #

Download Jikes 1.22 here: http://downloads.sourceforge.net/jikes/jikes-1.22-1.windows.zip?modtime=1096862035&big mirror=0

Liferay Portal Source #

Download Liferay Portal Source 4.4.2 here: http://downloads.sourceforge.net/lportal/liferay-portal-src-4.4.2.zip

Liferay-Tomcat5.5 Bundle for JDK 5 #

Download the bundle here: http://downloads.sourceforge.net/lportal/liferay-portal-tomcat-5.5-jdk5-4.4.2.zip

The bundle is and instance of Apache Tomcat preloaded with Liferay Portal. Not only does it have a build of the portal source, but also the required files in order to run this web application.

Eclipse 3.3 #

Download Eclipse 3.3 here: http://www.eclipse.org/downloads/

What you want is Eclipse Classic.

Installation and Setup #

Let's install the files that have been downloaded.

JDK 5 #

When you get to setting the location of the install, switch from the default location to C:\Java\jdk1.5.0_13\

Same goes for the JRE. Change the destination to: C:\Java\jre1.5.0_13\

Set JAVA_HOME. Right click "My Computer" and go to "Properties". Go to the advanced tab and click on "Environment Variables" and you will need to add anew System variable. Set JAVA_HOME to "C:\Java\jdk1.5.0_13\"

Edit the PATH. Add the following to the beginning of the PATH system variable: %JAVA_HOME%\bin;

Click OK.

Check that Windows recognizes Java and the correct version:

Ant 1.7 #

Unzip the ant archive to C:\Java\apache-ant-1.7.0 . It should look something like this:

Set ANT_HOME. Right click "My Computer" and go to "Properties". Go to the advanced tab and click on "Environment Variables" and you will need to add anew System variable. Set ANT_HOME to "C:\Java\apache-ant-1.7.0"

Edit the PATH. Similar to JAVA_HOME, add the following to the PATH system variable: %ANT_HOME%\bin;

Click OK.

Check that Windows recognizes Ant and the correct version:

Jikes 1.22 #

Unzip the jikes archive to C:\Java\jikes-1.22 . It should look something like this:

Set JIKES_HOME. Right click "My Computer" and go to "Properties". Go to the advanced tab and click on "Environment Variables" and you will need to add anew System variable. Set JIKES_HOME to "C:\Java\jikes-1.22"

Edit the PATH. Similar to JAVA_HOME and ANT_HOME, add the following to the PATH system variable: %JIKES_HOME%\bin;

Click OK.

Check that Windows recognizes Jikes and the correct version:

Liferay-Tomcat5.5 Bundle for JDK 5 #

The Tomcat bundle is an instance of Apache Tomcat with Liferay Portal pre-installed and ready to run against an embedded Hypersonic database. Aside from installing the JDK, no configuration is required. You can simply download the bundle, unzip the archive into a directory of your choice and run startup.bat in the "bin" directory.

Please do NOT use Hypersonic/HSQL in production! It is for demo purposes only.

Explode the archive into an directory of your choice. For this article, we will create a directory: C:\projects\liferay\tomcat

Go to the bin directory and double click startup.bat to start up the bundle. Id the portal starts up it means you have installed Java correctly. Look at the Tomcat console and you should see a message that the Tomcat has started:

You can also try logging on to the portal by pointing your browser to http://localhost:8080/ and using the username/password: test@liferay.com/test.

Liferay Portal Source 4.3.3 #

Let's setup the source code so we can set up the EXT environment later, and also as a reference in our development.

Explode the archive into C:\projects\liferay\portal

EXT environment #

The EXT environment is how developers can separate their custom code from the Liferay source code. Liferay recommends developing in the EXT environment because it makes applying patches to bugs and upgrades easier. Essentially, the EXT environment is a layer on top of the source. In the EXT, the source is put into JAR files. When you do a build from EXT, you are creating more JAR files, that are loaded by the class loader after the ones from source.

Let's create an EXT environment from the source we unpacked above.

Create a release.{username}.properties file. Find your username by opening a command prompt and typing "env" and you will see your "username" there.

In this case, I would need to create a file called "release.james.properties". Create one based on your username. Place it in C:\projects\liferay\portal .

In this file add these lines:

  ##
  ## Extension Environment
  ##
   
  lp.ext.dir=C:/projects/liferay/ext

Save.

Go to the command prompt and go to C:/projects/liferay/portal . Issue this command

  ant clean start build-ext

This will build your ext environment:

Check C:\projects\liferay\ext to see that the directory has been built:

You have created the EXT environment, and this is the place where you will do all development, and from where you will do future deployments.

Deploy EXT #

Now that you have created an EXT directory, let's set it up for deployment.

The first thing you need to do is create a file called app.server.{username}.properties . Similar as with the release.properties above, find your username:

NOTE:

If you´re using Tomcat 6.x it´s necessary to uncomment the following entries in the app.server.properties config file:

    app.server.tomcat.version=6.0
    app.server.tomcat.dir=${app.server.parent.dir}/tomcat-6.0.16
    app.server.tomcat.classes.global.dir=${app.server.tomcat.dir}/lib
    app.server.tomcat.lib.endorsed.dir=${app.server.tomcat.dir}/lib/ext
    app.server.tomcat.lib.global.dir=${app.server.tomcat.dir}/lib/ext
    app.server.tomcat.lib.support.dir=${app.server.tomcat.dir}/lib/ext
    app.server.tomcat.support.dir=${app.server.tomcat.dir}/lib/ext
    app.server.tomcat.zip.name=liferay-portal-tomcat-6.0-${downloads.version}.zip

In this case the file will be called app.server.james.properties. Create one for yourself based on your username:

In this file, add these lines:

  app.server.type=tomcat
  app.server.tomcat.dir=C:/projects/liferay/tomcat

This tells the Ant build tool what type of app server to deploy to, and where it is located.

Save the file.

After making sure Tomcat is not running, open a command prompt and issue this command:

  ant clean deploy

This will clean the files currently on Tomcat, and then do a deployment from the code that is in your EXT.

Your EXT is a fully self-contained version of your entire portal source. You do not need the portal source any more in order to build. However, it is good idea to keep it around as a reference in case you need to develop code based off of the source.

At this point, starting up Tomcat and browsing to http://localhost:8080/ should give you the same result as starting the bundle.

Congratulations! You have successfully deployed from EXT and are ready to develop!

Eclipse 3.3 #

Most people prefer to use some sort of IDE to do development. For simplicity we will demonstrate how to set up the EXT as a project in Eclipse and also how to set up the debugger.

Set up the Java Projects #

Unzip the eclipse archive into: C:\Java\eclipse

Startup eclipse by double clicking on eclipse.exe . Choose C:\projects\liferay as your workspace

Go to the Workbench:

Go to menu Window ==> Show View and open up "Navigator" and "Ant"

Go to menu File ==> New ==> Java Project

Name your project "ext" and use the "Create project from existing source" option. Point to: C:\projects\liferay\ext

Click "Finish"

Do a similar procedure for the portal source. Call the project "portal" and point to: C:\projects\liferay\portal

Now, let's set up the ant plugin so you can do your builds directly from within Eclipse! All you have to do is open up the "ext" project tree, and drag the build.xml file to the Ant window.

Now all you have to do is double click the "deploy" and task to do your build!

Set up the Debugger #

Let's set up the debugger. This way, you can run tomcat from within Eclipse, and step through any break points you have set.

Go to the menue Run ==> Open Debug Dialog...

Click on the "tomcat" Java Application and fill in these values in the Main tab:

Project: ext Main class: org.apache.catalina.startup.Bootstrap

Click on the Arguments tab and fill in these values:

Program arguments: start VM arguments:

  -Xms128m -Xmx512m -Dfile.encoding=UTF8 -Duser.timezone=GMT
  -XX:MaxPermSize=128m
  -Djava.security.auth.login.config=C:/projects/liferay/tomcat/conf/jaas.config
  -Djava.endorsed.dirs=C:/projects/liferay/tomcat/common/endorsed
  -Dcatalina.base=C:/projects/liferay/tomcat
  -Dcatalina.home=C:/projects/liferay/tomcat
  -Djava.io.tmpdir=C:/projects/liferay/tomcat/temp

Working Directory: C:/projects/liferay/tomcat/bin

Click on the JRE tab and make sure the JRE you installed earlier (JDK 5 installation) is selected:

Click on the Classpath tab. Remove the "Invalid path" entry and the bootstrap.jar from User Entries so that only the JRE is left. Then, click on the User Entries tree, then click on the "Add External JARs..." button.

Navigate to C:\projects\liferay\tomcat\bin\boostrap.jar and select it with the "Open" button

Click on the Source tab and click on the "Add..." button. Choose "Java Project" and add the portal project so you can have the source to debug through as well.

Click on "Apply" and "Debug" to see the portal start up!

Now you can set break points and step through your code.

Similarly, you can choose "Run..." instead of "Debug" if you just want to run Tomcat.

If you have problems running Tomcat from within Eclipse, a suggestion is to delete the Tomcat application from with the Run dialog and create a new Java Application from scratch with all of the above information.

Portal Configuration #

The whole of portal configuration is beyond the scope of this article. However, you can start with the signing on as the admin and looking through the administrative tools.

Signing in with the test@liferay.com user, password test, will be signing on as the Omni Admin. After signon, navigate to the "My Community" community's private page to see some of the admin portlets that are used to configure the portal as well as administer users and permissions.

This area may be expanded to include how to set up communities, users, basic permissions, and default portal settings.

Conclusion #

If you have followed all of the steps in this guide, congratulations! You are all set up to be productive and start development in Liferay. Good luck!

0 Attachments
103224 Views
Average (1 Vote)
The average rating is 5.0 stars out of 5.
Comments
Threaded Replies Author Date
I have followed this excellent tutorial with... Arvind Gupta August 22, 2008 8:27 AM
Lo mismo digo, siguiendo paso a paso las... Carlos Velle August 26, 2008 1:50 AM
In english please... Nice article: but could... Thibault Schalck August 26, 2008 11:26 AM
Good tutorial, but how about setting up a Web... Brian Preuß September 9, 2008 4:09 AM
Best guide for setting up for developmet in... Mara Pillott September 18, 2008 1:24 PM
Very good article . Followed all the steps ,... kannan chakkaravarthy October 10, 2008 2:30 PM
If you set up your devenv with Tomcat 6.0.x... Andreas Minnich October 20, 2008 2:46 AM
it's very good. Sohui Gu October 26, 2008 12:15 AM
Im getting following exception... Satish Bejgum November 7, 2008 5:50 AM
la méme erreur est ce que il est exise une... azahaf hakim June 16, 2010 1:05 AM
Nice one but i am not able to configure... Chirag Suthar November 16, 2008 9:11 PM
This is one of the best "Getting started for... Liferay tester January 25, 2009 1:11 PM
I've got the same problem one year later, did... ciccio pasticcio December 11, 2009 2:39 AM
I made it work (with tomcat)! For sure it's not... ciccio pasticcio December 15, 2009 7:07 AM
=========================... ciccio pasticcio December 15, 2009 7:11 AM
NO, WAIT! - I WAS WRONG (as you may easily see)... ciccio pasticcio December 15, 2009 7:28 AM
Okay I've followed the instructions and got the... Andrew W McDougall March 16, 2009 1:42 PM
hello, i tried to follow those steps but i have... Asmae Samoua April 6, 2009 10:59 AM
this is a nice tutorial for windows, could some... sergio andres ruiz April 16, 2009 1:55 PM
Can this be used for Liferay 5.2.3? I read... Ziggy © August 9, 2009 10:49 AM
Hi all . i follows by the instruction deploy... metilmarket newell kanavaro August 12, 2009 4:55 AM
I don't think anyone's paying attention. Dave Willis September 16, 2009 12:07 PM
Perfect. That's also working with Liferay 5.2.3... Johannes Hipp March 12, 2010 6:20 AM
can anyone tell me where the build-ext is in... m e June 11, 2010 8:19 AM
I have followed this tutorial.It runs fine but... Umesh Annegirikar October 4, 2010 1:46 AM
Hi I have followed all the steps given in the... Umesh Annegirikar October 4, 2010 4:42 AM
i m getting some error please help me... bhavishya goyal March 13, 2011 10:30 AM

I have followed this excellent tutorial with Eclipse 3.4 and JDK1.6.7, and It is working exactly same.
Posted on 8/22/08 8:27 AM.
Lo mismo digo, siguiendo paso a paso las instrucciones no he tenido ningún problema en configurarlo todo a la perfección. Solo una cosa en Eclipse 3.4 no se llama "Open Debug Dialog", sino que han cambiado el nombre por "Debug Configurations", no os volváis locos xD
Posted on 8/26/08 1:50 AM.
In english please...

Nice article: but could you add a part that explains how to create a portlet within Eclipse ? What are the step, what kind or project do we need to create and what are the configuration steps ?

Because for the moment I don't really understand how all this work...

Thanks
Posted on 8/26/08 11:26 AM in reply to Carlos Velle.
Good tutorial, but how about setting up a Web Tools Platform (WTP) project with Eclipse? Has anybody accomplished this?
Posted on 9/9/08 4:09 AM.
Best guide for setting up for developmet in Windows. I tried a few other posts and got hopelessly lost, but this guide was exactly what I needed! Thank you!
Posted on 9/18/08 1:24 PM.
Very good article . Followed all the steps , now iam all set to have my development env
Posted on 10/10/08 2:30 PM.
If you set up your devenv with Tomcat 6.0.x you'll have to edit the app.server.properties file in the ext directory
Posted on 10/20/08 2:46 AM.
it's very good.
Posted on 10/26/08 12:15 AM.
Im getting following exception
java.lang.NoClassDefFoundError: org/apache/catalina/startup/Bootstrap
Caused by: java.lang.ClassNotFoundException: org.apache.catalina.startup.Bootstrap
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
Exception in thread "main"
Posted on 11/7/08 5:50 AM.
Nice one but i am not able to configure debugging with Jboss in place of tomcat server.
can any buddy help me out in that?

Thanks emoticon
Posted on 11/16/08 9:11 PM.
Liferay tester
This is one of the best "Getting started for developers" article for liferay. Thank you for sharing.
Posted on 1/25/09 1:11 PM in reply to Chirag B Suthar.
Okay I've followed the instructions and got the same response as Satish did. I then removed the org.apache.catalina.startup.Bootstrap from the VM args as it shows above and it seems to startup ok - but for some reason I'm having problems now with it connecting to the db. Here's my error:Loading jar:file:/C:/projects/liferay/tomcat5.5/webapps/ROOT/WEB-INF/lib/portal-impl.jar­!/captcha.properties
15:30:56,346 INFO [PluginPackageUtil:1339] Checking for available updates
15:31:00,471 ERROR [PluginPackageUtil:1331] com.liferay.portal.plugin.PluginPackageException: Unable to communicate with repository http://plugins.liferay.com/official
com.liferay.portal.plugin.PluginPackageExcept­ion: Unable to communicate with repository http://plugins.liferay.com/official
at com.liferay.portal.plugin.PluginPackageUtil._loadRepository(PluginPackageUtil.ja­va:705)
at com.liferay.portal.plugin.PluginPackageUtil._getRepository(PluginPackageUtil.jav­a:428)
at com.liferay.portal.plugin.PluginPackageUtil._getAvailablePluginPackages(PluginPa­ckageUtil.java:343)
at com.liferay.portal.plugin.PluginPackageUtil._getLatestAvailablePluginPackage(Plu­ginPackageUtil.java:369)
at com.liferay.portal.plugin.PluginPackageUtil.getLatestAvailablePluginPackage(Plug­inPackageUtil.java:128)
at com.liferay.portal.plugin.PluginPackageUtil$UpdateAvailableRunner.setUpdateAvail­able(PluginPackageUtil.java:1359)
at com.liferay.portal.plugin.PluginPackageUtil$UpdateAvailableRunner.run(PluginPack­ageUtil.java:1328)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect

Anyway not sure what is happening here but if someone could explain I'd appreciate it. Also how do I begin to debug once this is all setup in Eclipse as discussed? Do I place my debug stops in the portal (src) or in the ext (project)? It was clear how it links together above when wanting to debug the liferay code.
Posted on 3/16/09 1:42 PM.
hello,
i tried to follow those steps but i have some errors, is it the same with liferay portal 5.2.2?
Posted on 4/6/09 10:59 AM.
this is a nice tutorial for windows, could some tell me if this tutorial works for linux (debian) ?? thanks
Posted on 4/16/09 1:55 PM.
Can this be used for Liferay 5.2.3? I read somewhere that there is a difference in the way Jikes is used?
Posted on 8/9/09 10:49 AM in reply to sergio andres ruiz.
Hi all .
i follows by the instruction deploy the ext environment using liferay -portal-src 5.2.3.
when i start up the tomcat i get the error like that :

Aug 12, 2009 6:23:59 PM org.apache.catalina.core.StandardContext Start
SERVER : ERROR listenerStart

Please give me advice.

thank regards
Posted on 8/12/09 4:55 AM in reply to Ziggy ..
I don't think anyone's paying attention.
Posted on 9/16/09 12:07 PM in reply to metilmarket newell kanavaro.
I've got the same problem one year later, did anybody knows how to complete this good tutorial on jboss?
Posted on 12/11/09 2:39 AM in reply to Chirag B Suthar.
I made it work (with tomcat)!
For sure it's not the easiest way, but if you are interested...

I used a lot of references, this guide and How+to+debug+Liferay+server+with+Eclipse.pdf
(check out on a search engine).

I deployed the portal-src on a tomcat 5.5 (from apache, not a boundle),
then I compiled and deployed the ext env.
Posted on 12/15/09 7:07 AM in reply to eriktech ecoologic.
========================= app.server.user.properties:

##
## EDIT THIS FILE.
##

##
## Server Type
##

app.server.type=jboss-tomcat

##
## Server Directory
##

app.server.parent.dir=${project.dir}/..

##
## JBoss+Tomcat
##


#
# Uncommment the following lines to deploy the portal in JBoss+Tomcat 5.0.x
# instead of JBoss+Tomcat 5.0.x.
#
app.server.jboss-tomcat.version=5.1
app.server.jboss-tomcat.dir=${app.server.parent.dir}/jboss
app.server.jboss-tomcat.classes.global.dir=${app.server.jboss-tomcat.instance.di­r}/lib
app.server.jboss-tomcat.instance.dir=${app.server.jboss-tomcat.dir}/server/defau­lt
app.server.jboss-tomcat.lib.global.dir=${app.server.jboss-tomcat.instance.dir}/l­ib
app.server.jboss-tomcat.zip.name=liferay-portal-jboss-tomcat-5.0-${downloads.ver­sion}.zip

================================= build.user.properties
##
## EDIT THIS FILE.
##

##
## Compiler
##

ant.build.javac.source=1.6
ant.build.javac.target=1.6



##
## Proxy
##

setproxy.proxy.host= ${myproxy}
setproxy.proxy.port=3128

##
## Upgrade Extension Environment
##

lp.ext.dir=${project.dir}/../ext

========================================= release.user.properties
##
## EDIT THIS FILE.
##

##
## Release Info
##

release.info=on

##
## Release Source
##

#lp.source.dir=${project.dir}/../source
lp.source.dir=${project.dir}/../portal

##
## Extension Environment
##

lp.ext.dir=${project.dir}/../ext

##
## Plugins Environment
##

#lp.plugins.dir=${project.dir}/../../plugins/build

##
## Eclipse
##

lp.eclipse.dir=D:/Erik/eclipse
lp.eclipse.project.name=ext

##
## SVN
##

#svn.revision=

##
## AntInstaller
##

#ant.installer.dir=C:/Java/ant-installer-0.7.4
Posted on 12/15/09 7:11 AM in reply to eriktech ecoologic.
NO, WAIT! - I WAS WRONG (as you may easily see)...
Posted on 12/15/09 7:28 AM in reply to eriktech ecoologic.
Perfect. That's also working with Liferay 5.2.3 and OC4J!

Best regards.
Johannes
Posted on 3/12/10 6:20 AM.
can anyone tell me where the build-ext is in the actual version?
Can't find it anywhere.
Posted on 6/11/10 8:19 AM in reply to Johannes Hipp.
la méme erreur est ce que il est exise une soulutions??,,
Posted on 6/16/10 1:05 AM in reply to satish bejgum.
I have followed this tutorial.It runs fine but at last stage it shows the following exception

C:\liferay-portal-5.2.3\portal\liferay-portal-src-5.2.3\build.xml:515:
The following error occurred while executing this line:
C:\liferay-portal-5.2.3\portal\liferay-portal-src-5.2.3\build.xml:602: Failed to
copy C:\liferay-portal-5.2.3\portal\liferay-portal-src-5.2.3\tools\ext_tmpl\ext
-impl\­src\com\ext\portlet\reports\action\ViewReportsAction.java to C:\liferay-po
rtal-5.2.3\portal\liferay-portal-src-5.2.3\liferay-portal-5.2.3 omcat-6.0.18libext\ext-impl\src\com\ext\portlet\reports\action\ViewReportsAction­.java due to java.io.FileNotFoundException
C:\liferay-portal-5.2.3\portal\liferay-portal-src-5.2.3\liferay-portal-5.2.3 omcat-6.0.18libext\ext-impl\src\com\ext\portlet\reports\action\ViewReportsAction­.java
(The filename, directory name, or volume label syntax is incorrect)

& build get failed.
So...please tell me the solution to these issue.
Posted on 10/4/10 1:46 AM.
Hi I have followed all the steps given in the tutorial.
This is very very nice tutorial.
I have get some exceptions for debugging but all the Ext is setting up very efficiently.

Thanking you....
Posted on 10/4/10 4:42 AM.
i m getting some error please help me
Buildfile: C:\portal\build.xml

clean:

clean:

clean:
Deleting: C:\portal\portal-kernel\portal-kernel.jar

clean:

clean:

clean:

clean:

clean:

clean:

cle­an:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean­:

clean:

build-common-web.clean:

clean:

build-common-web.clean:

clean:

clean-common-im­ages:

clean-common-images:

clean-common-images:

clean:

clean:

clean:

clean-module:

clea­n-module:

clean-module:

clean-module:

clean-module:

clean-module:

deploy:

compile:
Created dir: C:\portal\portal-kernel\classes
C:\portal\build-common-java.xml:29: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
Compiling 48 source files to C:\portal\portal-kernel\classes

jar:
Building jar: C:\portal\portal-kernel\portal-kernel.jar

deploy:
Copying 1 file to D:\Java\tomcat-5.5.17\common\lib\ext

compile:
Created dir: C:\portal\util-bridges\classes
C:\portal\build-common-java.xml:29: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
Compiling 8 source files to C:\portal\util-bridges\classes

build-common-java.jar:
Building jar: C:\portal\util-bridges\util-bridges.jar

jar:
Copying 1 file to C:\portal\portal-ejb\classes\com\liferay\portal\deploy\dependencies

deploy:
Copying 1 file to D:\Java\tomcat-5.5.17\webapps\ROOT\WEB-INF\lib

compile:
C:\portal\build-common-java.xml:29: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
Compiling 189 source files to C:\portal\util-java\classes

build-common-java.jar:
Building jar: C:\portal\util-java\util-java.jar

jar:
Copying 1 file to C:\portal\portal-ejb\classes\com\liferay\portal\deploy\dependencies

deploy:
Copying 1 file to D:\Java\tomcat-5.5.17\webapps\ROOT\WEB-INF\lib

jar:

compile:
C:\portal\build-common-java.xml:29: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
Compiling 67 source files to C:\portal\util-taglib\classes

Found 1 semantic error compiling "C:/portal/util-taglib/src/com/liferay/taglib/util/ParamAncestorTagImpl.java":

25. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.

Found 4 semantic errors compiling "C:/portal/util-taglib/src/com/liferay/taglib/theme/DefineObjectsTag.java":

25. import com.liferay.portal.theme.ThemeDisplay;
^-----------------------------------^
*** Semantic Error: The import "com/liferay/portal/theme/ThemeDisplay" is not valid, since it does not name a type in a package.


26. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.


42. ThemeDisplay themeDisplay =
^----------^
*** Semantic Error: Type "ThemeDisplay" was not found.


43. (ThemeDisplay)req.getAttribute(WebKeys.THEME_DISPLAY);
^----------^
*** Semantic Error: Type "ThemeDisplay" was not found.

Found 22 semantic errors compiling "C:/portal/util-taglib/src/com/liferay/taglib/theme/DefineObjectsTei.java":

25. import com.liferay.portal.model.Account;
^------------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Account" is not valid, since it does not name a type in a package.


26. import com.liferay.portal.model.ColorScheme;
^----------------------------------^
*** Semantic Error: The import "com/liferay/portal/model/ColorScheme" is not valid, since it does not name a type in a package.


27. import com.liferay.portal.model.Company;
^------------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Company" is not valid, since it does not name a type in a package.


28. import com.liferay.portal.model.Contact;
^------------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Contact" is not valid, since it does not name a type in a package.


29. import com.liferay.portal.model.Layout;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Layout" is not valid, since it does not name a type in a package.


30. import com.liferay.portal.model.LayoutTypePortlet;
^----------------------------------------^
*** Semantic Error: The import "com/liferay/portal/model/LayoutTypePortlet" is not valid, since it does not name a type in a package.


31. import com.liferay.portal.model.Theme;
^----------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Theme" is not valid, since it does not name a type in a package.


32. import com.liferay.portal.model.User;
^---------------------------^
*** Semantic Error: The import "com/liferay/portal/model/User" is not valid, since it does not name a type in a package.


33. import com.liferay.portal.security.permission.PermissionChecker;
^------------------------------------------------------^
*** Semantic Error: The import "com/liferay/portal/security/permission/PermissionChecker" is not valid, since it does not name a type in a package.


34. import com.liferay.portal.theme.PortletDisplay;
^-------------------------------------^
*** Semantic Error: The import "com/liferay/portal/theme/PortletDisplay" is not valid, since it does not name a type in a package.


35. import com.liferay.portal.theme.ThemeDisplay;
^-----------------------------------^
*** Semantic Error: The import "com/liferay/portal/theme/ThemeDisplay" is not valid, since it does not name a type in a package.


56. "themeDisplay", ThemeDisplay.class.getName(), true,
^----------^
*** Semantic Error: Type "ThemeDisplay" was not found.


59. "company", Company.class.getName(), true, VariableInfo.AT_END),
^-----^
*** Semantic Error: Type "Company" was not found.


61. "account", Account.class.getName(), true, VariableInfo.AT_END),
^-----^
*** Semantic Error: Type "Account" was not found.


63. "user", User.class.getName(), true, VariableInfo.AT_END),
^--^
*** Semantic Error: Type "User" was not found.


65. "contact", Contact.class.getName(), true, VariableInfo.AT_END),
^-----^
*** Semantic Error: Type "Contact" was not found.


67. "layout", Layout.class.getName(), true, VariableInfo.AT_END),
^----^
*** Semantic Error: Type "Layout" was not found.


73. "layoutTypePortlet", LayoutTypePortlet.class.getName(), true,
^---------------^
*** Semantic Error: Type "LayoutTypePortlet" was not found.


79. "permissionChecker", PermissionChecker.class.getName(), true,
^---------------^
*** Semantic Error: Type "PermissionChecker" was not found.


87. "theme", Theme.class.getName(), true, VariableInfo.AT_END),
^---^
*** Semantic Error: Type "Theme" was not found.


89. "colorScheme", ColorScheme.class.getName(), true,
^---------^
*** Semantic Error: Type "ColorScheme" was not found.


92. "portletDisplay", PortletDisplay.class.getName(), true,
^------------^
*** Semantic Error: Type "PortletDisplay" was not found.

Found 1 semantic error compiling "C:/portal/util-taglib/src/com/liferay/taglib/portlet/NamespaceTag.java":

25. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.

Found 5 semantic errors compiling "C:/portal/util-taglib/src/com/liferay/taglib/util/IncludeTag.java":

25. import com.liferay.portal.model.Theme;
^----------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Theme" is not valid, since it does not name a type in a package.


26. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.


53. Theme theme = (Theme)req.getAttribute(WebKeys.THEME);
^---^
*** Semantic Error: Type "Theme" was not found.


53. Theme theme = (Theme)req.getAttribute(WebKeys.THEME);
^---^
*** Semantic Error: Type "Theme" was not found.


58. ThemeUtil.include(ctx, req, res, pageContext, page, theme);
^--------------------------------------------------------^
*** Semantic Error: No applicable overload for a method with signature "include(javax.servlet.ServletContext, javax.servlet.http.HttpServletRequest, com.liferay.util.servlet.StringServletResponse, javax.servlet.jsp.PageContext, java.lang.String, ??)" was found in type "com.liferay.taglib.util.ThemeUtil". Perhaps you wanted the overloaded version "void include(javax.servlet.ServletContext ctx, javax.servlet.http.HttpServletRequest req, javax.servlet.http.HttpServletResponse res, javax.servlet.jsp.PageContext pageContext, java.lang.String page, ?? theme) throws java.lang.Exception;" instead?

Found 20 semantic errors compiling "C:/portal/util-taglib/src/com/liferay/taglib/util/ThemeUtil.java":

25. import com.liferay.portal.language.LanguageUtil_IW;
^-----------------------------------------^
*** Semantic Error: The import "com/liferay/portal/language/LanguageUtil_IW" is not valid, since it does not name a type in a package.


26. import com.liferay.portal.model.Theme;
^----------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Theme" is not valid, since it does not name a type in a package.


27. import com.liferay.portal.servlet.SharedSessionUtil;
^------------------------------------------^
*** Semantic Error: The import "com/liferay/portal/servlet/SharedSessionUtil" is not valid, since it does not name a type in a package.


28. import com.liferay.portal.theme.ThemeDisplay;
^-----------------------------------^
*** Semantic Error: The import "com/liferay/portal/theme/ThemeDisplay" is not valid, since it does not name a type in a package.


29. import com.liferay.portal.util.PortalUtil_IW;
^-----------------------------------^
*** Semantic Error: The import "com/liferay/portal/util/PortalUtil_IW" is not valid, since it does not name a type in a package.


30. import com.liferay.portal.util.PropsUtil_IW;
^----------------------------------^
*** Semantic Error: The import "com/liferay/portal/util/PropsUtil_IW" is not valid, since it does not name a type in a package.


31. import com.liferay.portal.util.ServiceLocator;
^------------------------------------^
*** Semantic Error: The import "com/liferay/portal/util/ServiceLocator" is not valid, since it does not name a type in a package.


32. import com.liferay.portal.util.SessionClicks_IW;
^--------------------------------------^
*** Semantic Error: The import "com/liferay/portal/util/SessionClicks_IW" is not valid, since it does not name a type in a package.


33. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.


34. import com.liferay.portlet.PortletConfigImpl;
^-----------------------------------^
*** Semantic Error: The import "com/liferay/portlet/PortletConfigImpl" is not valid, since it does not name a type in a package.


35. import com.liferay.portlet.PortletURLFactory;
^-----------------------------------^
*** Semantic Error: The import "com/liferay/portlet/PortletURLFactory" is not valid, since it does not name a type in a package.


81. PageContext pageContext, String page, Theme theme)
^---^
*** Semantic Error: Type "Theme" was not found.


87. includeVM(ctx, req, pageContext, page, theme);
^-------------------------------------------^
*** Semantic Error: No applicable overload for a method with signature "includeVM(javax.servlet.ServletContext, javax.servlet.http.HttpServletRequest, javax.servlet.jsp.PageContext, java.lang.String, ??)" was found in type "com.liferay.taglib.util.ThemeUtil". Perhaps you wanted the overloaded version "void includeVM(javax.servlet.ServletContext ctx, javax.servlet.http.HttpServletRequest req, javax.servlet.jsp.PageContext pageContext, java.lang.String page, ?? theme) throws java.lang.Exception;" instead?


93. includeJSP(ctx, req, res, path, theme);
^------------------------------------^
*** Semantic Error: No applicable overload for a method with signature "includeJSP(javax.servlet.ServletContext, javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, java.lang.String, ??)" was found in type "com.liferay.taglib.util.ThemeUtil". Perhaps you wanted the overloaded version "void includeJSP(javax.servlet.ServletContext ctx, javax.servlet.http.HttpServletRequest req, javax.servlet.http.HttpServletResponse res, java.lang.String path, ?? theme) throws java.lang.Exception;" instead?


99. String path, Theme theme)
^---^
*** Semantic Error: Type "Theme" was not found.


146. String page, Theme theme)
^---^
*** Semantic Error: Type "Theme" was not found.


195. PortletConfigImpl portletConfig =
^---------------^
*** Semantic Error: Type "PortletConfigImpl" was not found.


196. (PortletConfigImpl)req.getAttribute(WebKeys.JAVAX_PORTLET_CONFIG);
^---------------^
*** Semantic Error: Type "PortletConfigImpl" was not found.


226. ThemeDisplay themeDisplay =
^----------^
*** Semantic Error: Type "ThemeDisplay" was not found.


227. (ThemeDisplay)req.getAttribute(WebKeys.THEME_DISPLAY);
^----------^
*** Semantic Error: Type "ThemeDisplay" was not found.

Found 1 semantic error compiling "C:/portal/util-taglib/src/com/liferay/taglib/ui/ToggleTag.java":

25. import com.liferay.portal.util.SessionClicks;
^-----------------------------------^
*** Semantic Error: The import "com/liferay/portal/util/SessionClicks" is not valid, since it does not name a type in a package.

Found 6 semantic errors compiling "C:/portal/util-taglib/src/com/liferay/taglib/ui/BoxTag.java":

25. import com.liferay.portal.model.Theme;
^----------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Theme" is not valid, since it does not name a type in a package.


26. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.


61. Theme theme = (Theme)req.getAttribute(WebKeys.THEME);
^---^
*** Semantic Error: Type "Theme" was not found.


61. Theme theme = (Theme)req.getAttribute(WebKeys.THEME);
^---^
*** Semantic Error: Type "Theme" was not found.


66. ThemeUtil.include(ctx, req, res, pageContext, getTop(), theme);
^------------------------------------------------------------^
*** Semantic Error: No applicable overload for a method with signature "include(javax.servlet.ServletContext, javax.servlet.http.HttpServletRequest, com.liferay.util.servlet.StringServletResponse, javax.servlet.jsp.PageContext, java.lang.String, ??)" was found in type "com.liferay.taglib.util.ThemeUtil". Perhaps you wanted the overloaded version "void include(javax.servlet.ServletContext ctx, javax.servlet.http.HttpServletRequest req, javax.servlet.http.HttpServletResponse res, javax.servlet.jsp.PageContext pageContext, java.lang.String page, ?? theme) throws java.lang.Exception;" instead?


<-----------------
86. ThemeUtil.include(
87. ctx, req, res, pageContext, getBottom(), theme);
--------------------------------------------------------------------------------­------>
*** Semantic Error: No applicable overload for a method with signature "include(javax.servlet.ServletContext, javax.servlet.http.HttpServletRequest, com.liferay.util.servlet.StringServletResponse, javax.servlet.jsp.PageContext, java.lang.String, ??)" was found in type "com.liferay.taglib.util.ThemeUtil". Perhaps you wanted the overloaded version "void include(javax.servlet.ServletContext ctx, javax.servlet.http.HttpServletRequest req, javax.servlet.http.HttpServletResponse res, javax.servlet.jsp.PageContext pageContext, java.lang.String page, ?? theme) throws java.lang.Exception;" instead?

Found 6 semantic errors compiling "C:/portal/util-taglib/src/com/liferay/taglib/portletext/RuntimeTag.java":

26. import com.liferay.portal.model.Layout;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Layout" is not valid, since it does not name a type in a package.


27. import com.liferay.portal.model.Portlet;
^------------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Portlet" is not valid, since it does not name a type in a package.


28. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.


29. import com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil;
^-------------------------------------------------------------^
*** Semantic Error: The import "com/liferay/portlet/layoutconfiguration/util/RuntimePortletUtil" is not valid, since it does not name a type in a package.


114. Layout layout = (Layout)req.getAttribute(WebKeys.LAYOUT);
^----^
*** Semantic Error: Type "Layout" was not found.


114. Layout layout = (Layout)req.getAttribute(WebKeys.LAYOUT);
^----^
*** Semantic Error: Type "Layout" was not found.

Found 3 semantic errors compiling "C:/portal/util-taglib/src/com/liferay/taglib/security/EncryptTag.java":

25. import com.liferay.portal.model.Company;
^------------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Company" is not valid, since it does not name a type in a package.


26. import com.liferay.portal.util.PortalUtil;
^--------------------------------^
*** Semantic Error: The import "com/liferay/portal/util/PortalUtil" is not valid, since it does not name a type in a package.


82. Company company = PortalUtil.getCompany(
^-----^
*** Semantic Error: Type "Company" was not found.

Found 12 semantic errors compiling "C:/portal/util-taglib/src/com/liferay/taglib/security/PermissionsURLTag.java":

25. import com.liferay.portal.model.Layout;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Layout" is not valid, since it does not name a type in a package.


26. import com.liferay.portal.theme.PortletDisplay;
^-------------------------------------^
*** Semantic Error: The import "com/liferay/portal/theme/PortletDisplay" is not valid, since it does not name a type in a package.


27. import com.liferay.portal.theme.ThemeDisplay;
^-----------------------------------^
*** Semantic Error: The import "com/liferay/portal/theme/ThemeDisplay" is not valid, since it does not name a type in a package.


28. import com.liferay.portal.util.PortletKeys;
^---------------------------------^
*** Semantic Error: The import "com/liferay/portal/util/PortletKeys" is not valid, since it does not name a type in a package.


29. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.


30. import com.liferay.portlet.PortletURLImpl;
^--------------------------------^
*** Semantic Error: The import "com/liferay/portlet/PortletURLImpl" is not valid, since it does not name a type in a package.


31. import com.liferay.portlet.PortletURLUtil;
^--------------------------------^
*** Semantic Error: The import "com/liferay/portlet/PortletURLUtil" is not valid, since it does not name a type in a package.


56. ThemeDisplay themeDisplay =
^----------^
*** Semantic Error: Type "ThemeDisplay" was not found.


57. (ThemeDisplay)req.getAttribute(WebKeys.THEME_DISPLAY);
^----------^
*** Semantic Error: Type "ThemeDisplay" was not found.


59. PortletDisplay portletDisplay = themeDisplay.getPortletDisplay();
^------------^
*** Semantic Error: Type "PortletDisplay" was not found.


61. Layout layout = themeDisplay.getLayout();
^----^
*** Semantic Error: Type "Layout" was not found.


76. PortletURL portletURL = new PortletURLImpl(
^------------^
*** Semantic Error: Type "PortletURLImpl" was not found.

Found 3 semantic errors compiling "C:/portal/util-taglib/src/com/liferay/taglib/ui/BreadcrumbTag.java":

25. import com.liferay.portal.model.Layout;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/model/Layout" is not valid, since it does not name a type in a package.


54. public void setSelLayout(Layout selLayout) {
^----^
*** Semantic Error: Type "Layout" was not found.


76. private Layout _selLayout;
^----^
*** Semantic Error: Type "Layout" was not found.

Found 1 semantic error compiling "C:/portal/util-taglib/src/com/liferay/taglib/ui/ErrorTag.java":

25. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.

Found 1 semantic error compiling "C:/portal/util-taglib/src/com/liferay/taglib/ui/SectionTag.java":

25. import com.liferay.portal.util.WebKeys;
^-----------------------------^
*** Semantic Error: The import "com/liferay/portal/util/WebKeys" is not valid, since it does not name a type in a package.
Posted on 3/13/11 10:30 AM in reply to Umesh Annegirikar.