ControlTier build instructions

Serban Alexe

unread,

Dec 21, 2009, 6:52:45 AM12/21/09

to ControlTier

Hello,

Are the Controltier Build Instructions up-to-date ?
Can they be followed in order to really obtain a complete ControlTier
build ?

I encountered several problems while following step-by-step each
instruction from this page: http://controltier.org/wiki/Integrated_build_instructions_3.4
.

See below for some details.

Thank You.

- During CTL build
- needed variables are properly set, property files created as
specified;
- command: $MAVEN_HOME/bin/maven ctl:stgz ctl:tgz ctl:zip
- output:

[xdoclet] [ERROR] Error parsing File /home/salexe/ctier-build/
ctlsvn/src/java/com/controltier/ctl/common/INodeEntry.java:Encountered
"<" at line 63, column 15.
[xdoclet] [ERROR] Was expecting one of:
[xdoclet] [ERROR] <IDENTIFIER> ...
[xdoclet] [ERROR] "[" ...
[xdoclet] [ERROR] "." ...
[xdoclet] [ERROR]

and about 15 more like it.

- the build is reported as SUCCESFUL
- the build artifacts resulting from this step have different version
(1.4.10) that the one mentioned in the build instructions (1.4.2)

- During Controltier "common" libs build
- needed variables are properly set, property files created as
specified;
- command: $MAVEN_HOME/bin/maven -Djava.net.preferIPv4Stack=true
java:jars

- ERRORS are encountered, trying to download the file
http://ctl-dispatch.sourceforge.net/repository/ctl/jars/ctl-1.4.10.jar

- the build artifacts resulting from this step have different version
(3.4.10) that the one mentioned in the build instructions (3.4.2)

- During Controltier Seed jar build

- again an attempt is made to download the file:
http://controltier.sourceforge.net/repository/ctl/jars/ctl-1.4.10.jar

- Seed Building fails with the following error:

[java] Buildfile: /home/salexe/ctier-build/ctiersvn/common/src/ant/
modules/buildseed.xml
[java]
[java] BUILD FAILED
[java] /home/salexe/ctier-build/ctiersvn/common/src/ant/modules/
buildseed.xml:9: taskdef class
com.controltier.ctl.shared.tasks.AntResource cannot be found
[java]
[java] Total time: 0 seconds
[java] [ERROR] Java Result: 1

- the expected build artifact is not present.

- During Workbench webapp build

- first command: $MAVEN_HOME/bin/maven -
Djava.net.preferIPv4Stack=true java:jar-resources
- attepmts are made to download (via wget) several jars, many of them
fail
(eg: http://controltier.sourceforge.net/repository/commander/jars/commander-3.4.10.jar
, http://controltier.sourceforge.net/repository/catalina/jars/catalina-4.0.6.jar,
etc...)

- second command: $MAVEN_HOME/bin/maven -
Djava.net.preferIPv4Stack=true java:jar war
- again, some download attempts fail
( eg: Error opening connection java.io.FileNotFoundException:
http://ctl-dispatch.sourceforge.net/repository/ctier-common/jars/ctier-common-3.4.10.jar
)
- the Java Compiler throws errors:
[javac] [ERROR] /home/salexe/ctier-build/ctiersvn/workbench/src/java/
org/opendepo/depo/map/ExtKnowledgeMap.java:41: package
org.opendepo.depo.map.vocabulary does not exist
[javac] [ERROR] import org.opendepo.depo.map.vocabulary.KM;
[javac] [ERROR] ^
[javac] [ERROR] /home/salexe/ctier-build/ctiersvn/workbench/src/java/
org/opendepo/utils/rdql/QueryBuilder.java:680: cannot find symbol
[javac] [ERROR] symbol : class Mapper
[javac] [ERROR] location: class org.opendepo.utils.rdql.QueryBuilder
[javac] [ERROR] private static Mapper selectCheck =
Mapper.filterMapper(new instanceOfPredicate(SelectPart.class));
- the build fails

[ERROR] BUILD FAILED
[ERROR] File...... /home/salexe/ctier-build/ctiersvn/maven/plugins/
maven-java-plugin-1.1/plugin.jelly
[ERROR] Element... javac
[ERROR] Line...... 54
[ERROR] Column.... 48
[ERROR] Compile failed; see the compiler error output for details.
Total time: 20 seconds

This is the point where I stopped :)

Greg Schueler

unread,

Dec 21, 2009, 1:19:58 PM12/21/09

to contr...@googlegroups.com

Hi Serban,

The build instructions might be slightly out of date, I will go through and see if there are any changes I need to make to the docs.

There is a full build script in the controltier sourcebase, called "buildall.sh". this script is a better reference than the build docs, since it has been used more recently. You may want to compare it to your steps, and see if they differ.

Some notes about your output:

You are building from the 3-4-support branch, which has the latest code version (3.4.10). The docs refer to 3.4.2 as an example. If you want to build a specific previous version, you should check out the appropriate tag from each sourcebase.

The errors prefixed with " [xdoclet]" can be ignored.

did you follow the instructions to copy the build artifacts to the LOCALREPO area? e.g.:

mkdir -p $LOCALREPO/ctl/jars

cp target/ctl-dispatch-$CTLVERS.jar $LOCALREPO/ctl/jars/ctl-$CTLVERS.jar

These steps are necessary to provide the dependencies for later steps.

It sounds like the ctier-common libraries were not built and put in the right LOCALREPO location, which caused later build steps to fail.

--
You received this message because you are subscribed to the Google Groups "ControlTier" group.
To post to this group, send email to contr...@googlegroups.com
To unsubscribe from this group, send email to controltier...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/controltier?hl=en
http://wiki.controltier.org

Greg Schueler

unread,

Dec 21, 2009, 2:46:25 PM12/21/09

to contr...@googlegroups.com

Hi Serban,

I went through the build process, and updated the build instructions on that page. There we a few changes. These fixes bring the document up to date with the buildall.sh script:

Fixed GRAILS_HOME paths because Jobcenter/Reportcenter use different versions of Grails
Removed 3.4.2 version numbers, described appropriate version numbers in the beginning.
Removed some redundant CTL build instructions.
Fixed LOCALREPOURL variable: should be "file:$LOCALREPO", to have appropriate format.
Fixed ordering: Workbench should be built AFTER the Commander extension.
Removed coreutils build step: this is no longer used
Fixed Jobcenter build: use specific GRAILS_HOME for grails 1.1.1. Reset PATH and GRAILS_HOME vars after build.
Fixed Reportcenter build: use specific GRAILS_HOME for grails 1.0.3. Reset PATH and GRAILS_HOME vars after build.
Added Ctier Examples build required for installer.
Added optional RPM build step.

Greg Schueler

unread,

Dec 21, 2009, 3:33:05 PM12/21/09

to contr...@googlegroups.com

Additional fix:

Fix CTL build to copy ctl-dispatch artifacts correctly.
Add CTL Bundle build step after Workbench build.

Serban Alexe

unread,

Dec 23, 2009, 9:10:44 AM12/23/09

to ControlTier

Hello Greg,

I did follow each step presented on the building instructions page,
INCLUDING creating needed directories and copying building artifacts
after each phase of the building process.
I did try to use the "buildall.sh" script, back few days ago, after
manually building failed, and I also tried it today, after reading
your replies.

The result is the same, the execution of "buildall.sh" fails.

As I can figure out (please correct me if I'm wrong), the buildall.sh
scrips basically performes the same building process (system
variables, directories, svn-checkout necessary modules, and wget
needed dependencies).

I will try again to perform the manual building instructions,
according to the updated page from the wiki.

See below for the output of the "buildall.sh" script.

Thank You.

So, today I ran again the "buildall.sh" script, and the following
happened:

- svn-checkout worked OK: ctiersvn, ctlsvn, jobcentersvn,
ctierseedsvn.

- build_ctl() - worked OK, just the "[xdoclet]" errors and some
javadoc warnings

- build_common() step:
- cd $CTIERSVN/common && $MAVEN_HOME/bin/maven -
Djava.net.preferIPv4Stack=true java:jars
- some java.io.FileNotFoundException are encountered on attempts to
get various needed files, but after several attempts, attepts are made
to different alternative locations (local computer or different URL),
and the file download succedes... I assume it worked OK.
eg:

OR:

- build_controltier_seed() - worked OK

- build_commander_extension() - worked OK

- build_workbench()
- seems to work OK
- some errors are reported:

[get] Getting: file:/home/salexe/build/localrepo/struts-layout/js/
HM_Loader-1.0.js
[get] Error getting file:/home/salexe/build/localrepo/struts-layout/
js/HM_Loader-1.0.js to /home/salexe/build/ctiersvn/workbench/src/
content/itnav/config/HM_Loader.js
[get] Getting: file:/home/salexe/build/localrepo/struts-layout/js/
HM_ScriptIE4-1.0.js
[get] Error getting file:/home/salexe/build/localrepo/struts-layout/
js/HM_ScriptIE4-1.0.js to /home/salexe/build/ctiersvn/workbench/src/
content/itnav/config/HM_ScriptIE4.js
[get] Getting: file:/home/salexe/build/localrepo/struts-layout/js/
javascript-1.0.js
[get] Error getting file:/home/salexe/build/localrepo/struts-layout/
js/javascript-1.0.js to /home/salexe/build/ctiersvn/workbench/src/
content/itnav/config/javascript.js
[get] Getting: file:/home/salexe/build/localrepo/struts-layout/js/
HM_ScriptDOM-1.0.js
[get] Error getting file:/home/salexe/build/localrepo/struts-layout/
js/HM_ScriptDOM-1.0.js to /home/salexe/build/ctiersvn/workbench/src/
content/itnav/config/HM_ScriptDOM.js
[get] Getting: file:/home/salexe/build/localrepo/struts-layout/js/
HM_ScriptNS4-1.0.js
[get] Error getting file:/home/salexe/build/localrepo/struts-layout/
js/HM_ScriptNS4-1.0.js to /home/salexe/build/ctiersvn/workbench/src/
content/itnav/config/HM_ScriptNS4.js
[get] Getting: file:/home/salexe/build/localrepo/struts-layout/js/
swap-1.0.js
[get] Error getting file:/home/salexe/build/localrepo/struts-layout/
js/swap-1.0.js to /home/salexe/build/ctiersvn/workbench/src/content/
itnav/config/swap.js

- build_ctl_bundle()
- reports "BUILD SUCCESFULL"
- fails to get some files:

Error getting file:/home/salexe/build/localrepo/non-distributable-
jars.list ; it does not exist.
-----------------------------------------------
W A R N I N G
-----------------------------------------------
Failed to download list of non-distributable
jars non-distributable-jars.list
Will continue with attempted downloads of dependent jars.

Error getting file:/home/salexe/build/localrepo/ctl-dispatch/jars/
ctl-dispatch-1.4.10.jar ; it does not exist.

-------------------------------------------------
W A R N I N G
------------------------------------------------
Failed to download dependent file ctl-dispatch-1.4.10.jar

(*) NOTE: the buildall.sh script contains a comment about this:

build_ctl_bundle(){

# ...

#!! failed to download ctl-dispatch.jar ... !!!

# ...

}

- build_jobcenter() - FAILS, with the following output:

clean:
[exec] Exception in thread "main" java.lang.NoClassDefFoundError:
org/codehaus/groovy/grails/cli/support/GrailsStarter
[delete] Deleting directory /home/salexe/build/jobcentersvn/
target/jobcenter-1.4.10

-checkversion:

-getversion:

config:
[echo] build ident: 1.4.10.20091223
[copy] Copying 1 file to /home/salexe/build/jobcentersvn/grails-
app/i18n
[copy] Copying 1 file to /home/salexe/build/jobcentersvn/grails-
app/i18n

war:
[exec] Exception in thread "main" java.lang.NoClassDefFoundError:
org/codehaus/groovy/grails/cli/support/GrailsStarter

-check-jetty:

-download-jetty:

prepare:
[mkdir] Created dir: /home/salexe/build/jobcentersvn/target/
jobcenter-1.4.10
Jobcenter build failed

On Dec 21, 10:33 pm, Greg Schueler <g...@controltier.com> wrote:
> Additional fix:
>
> -
> - Fix CTL build to copy ctl-dispatch artifacts correctly.
> - Add CTL Bundle build step after Workbench build.

>
> On Mon, Dec 21, 2009 at 11:46 AM, Greg Schueler <g...@controltier.com>wrote:
>
> > Hi Serban,
>
> > I went through the build process, and updated the build instructions on
> > that page. There we a few changes. These fixes bring the document up to
> > date with the buildall.sh script:
>

> > - Fixed GRAILS_HOME paths because Jobcenter/Reportcenter use different
> > versions of Grails
> > - Removed 3.4.2 version numbers, described appropriate version numbers
> > in the beginning.
> > - Removed some redundant CTL build instructions.
> > - Fixed LOCALREPOURL variable: should be "file:$LOCALREPO", to have
> > appropriate format.
> > - Fixed ordering: Workbench should be built AFTER the Commander
> > extension.
> > - Removed coreutils build step: this is no longer used
> > - Fixed Jobcenter build: use specific GRAILS_HOME for grails 1.1.1.

> > Reset PATH and GRAILS_HOME vars after build.

> > - Fixed Reportcenter build: use specific GRAILS_HOME for grails 1.0.3.

> > Reset PATH and GRAILS_HOME vars after build.

> > - Added Ctier Examples build required for installer.
> > - Added optional RPM build step.

>
> > On Mon, Dec 21, 2009 at 10:19 AM, Greg Schueler <g...@controltier.com>wrote:
>
> >> Hi Serban,
>
> >> The build instructions might be slightly out of date, I will go through
> >> and see if there are any changes I need to make to the docs.
>
> >> There is a full build script in the controltier sourcebase, called
> >> "buildall.sh". this script is a better reference than the build docs, since
> >> it has been used more recently. You may want to compare it to your steps,
> >> and see if they differ.
>
> >> Some notes about your output:
>
> >> You are building from the 3-4-support branch, which has the latest code
> >> version (3.4.10). The docs refer to 3.4.2 as an example. If you want to
> >> build a specific previous version, you should check out the appropriate tag
> >> from each sourcebase.
>
> >> The errors prefixed with " [xdoclet]" can be ignored.
>
> >> did you follow the instructions to copy the build artifacts to the
> >> LOCALREPO area? e.g.:
>
> >> mkdir -p $LOCALREPO/ctl/jars
>
> >> cp target/ctl-dispatch-$CTLVERS.jar $LOCALREPO/ctl/jars/ctl-$CTLVERS.jar
>
> >> These steps are necessary to provide the dependencies for later steps.
>
> >> It sounds like the ctier-common libraries were not built and put in the
> >> right LOCALREPO location, which caused later build steps to fail.
>

> >>>http://controltier.sourceforge.net/repository/commander/jars/commande...
> >>> ,
> >>>http://controltier.sourceforge.net/repository/catalina/jars/catalina-...

> >>> ,
> >>> etc...)
>
> >>> - second command: $MAVEN_HOME/bin/maven -
> >>> Djava.net.preferIPv4Stack=true java:jar war
> >>> - again, some download attempts fail
> >>> ( eg: Error opening connection
> >>> java.io.FileNotFoundException:
>

> >>>http://ctl-dispatch.sourceforge.net/repository/ctier-common/jars/ctie...

Greg Schueler

unread,

Dec 23, 2009, 1:40:08 PM12/23/09

to contr...@googlegroups.com

Hi Serban,

sounds like you are close to completing the build!

build_common(): the not found messages are ok. it attempts to get the jars from external repos, then falls back to your LOCALREPO.

build_ctl_bundle: that warning can be ignored

build_jobcenter: it seems to have an error executing grails. Can you verify that the grails 1.1.1 version is extracted correctly to the $builddir/local/grails-1.1.1 dir? I.e. there should be a $builddir/local/grails-1.1.1/bin/grails file. Make sure the scripts inside the "bin' dir have executable permissions.

I found this grails issue, I'm not sure if it has any info you can use: http://jira.codehaus.org/browse/GRAILS-2267

is it possible that the "grails" command is conflicting with another grails installation already on your PATH variable prior to running the build? Another issue may be if you have multiple JVMs installed, and your PATH variable may be pointing at a different one.

note: you can retry single steps of the build process using buildall.sh, just execute "buildall.sh jobcenter" for example. If you continue the build that way, just reference the ordering of subsequent steps to perform at the bottom of the script.

Greg Schueler

unread,

Dec 23, 2009, 1:41:50 PM12/23/09

to contr...@googlegroups.com

I made another fix to buildall.sh that only affects the server rpm build step

Update buildall.sh server_rpm step: change maven goal to server:rpmbuild-full to correctly generate installer tgz file prior to server rpm build

Reply all

Reply to author

Forward

ControlTier build instructions - problems

Serban Alexe

Greg Schueler

Greg Schueler

Greg Schueler

Serban Alexe

Greg Schueler

Greg Schueler