Software Build and Release Specialist

I ran into another not-so-clear Perforce error message today while trying to import a new project to an existing depot.  I had a new project1 which I wanted to import into the existing // depot, but when I tried to add via P4V or ‘p4 add’ in the command line, I kept getting this message:

D:\Work\P4>p4 client myproject_foo
Error in client specification.
Mapping ‘//some_directory/…’ is not under ‘//some_other_directory/…’.
Hit return to continue…

After fumbling around, I found that I had to create a depot first as the superuser in the command line before I can import/add the new project:

p4 depot new_project

Then now I can add new project to my clientspec in the command line like this:

p4 client (it will open a notepad window, just add your new project under the ‘View:’ section, save, and close)

Now you can do ‘p4 add’ or using P4V to import your new project.

Are you using CruiseControl 2.7? Have you inspected the CC log lately? Seeing this error message?

atusReportTask- Failed to reach dashboard instance : http://mydomain.com:8080/dashboard/buildloop/listener, either the dashboard has not started up or there is a network problem

Recently I’ve been experiencing some build wlappc jspc freezing issue which I’ve fixed and works fine when I run it via command line, but the build continue to freeze when it invokes via CruiseControl.  Turns out, there were quite a few people who have experienced the same problem.

To fix it, I just ugpraded my CruiseControl suite from 2.7 to 2.8.2.  Quick and clean fix, forget spending time troubleshooting this problem at the low levels.  No time for that, software release must go out on schedule…

Wow.   This little problem was extremely tricky to detect — mainly due to WebLogic’s wlappc ANT Task’s poor documentation.   In one of the projects I’m working on, there is a need to pre-compile WebLogic JSP so it will be much faster during deployment/runtime and we can catch any potential errors early.   Previously, this step of the compilation has never given us any problem until when it decides to act up and freezes or hangs certain builds.  However, it was never an issue since restarting the build usually fixes it.

That is, until recently when the freezing/hanging started to happen on a consistent basis.  Here’s the snippet of the ANT Task:

<wlappc source=”${some.base.dir}” classpath=”${some.dir}/some_class.jar” verbose=”true”/>

The ANT output during build time is this and is where it freezes:

[wlappc] [jspc] Compiling /path/to/jsp/foo.jsp

Then after searching high and low on BEA’s site, I came upon this page (Here) which describes the task in detail.  I then realized I should add in idlVerbose=”true”.  Once I’ve added that, this is the output I got from the build:

[wlappc] [jspc] Compiling /path/to/jsp/foo.jsp
[wlappc] WARNING: unable to get an input stream for jar:file:/path/to/some/jar/WEB-INF/lib/struts.jar!/
[wlappc] java.lang.NoClassDefFoundError: org/apache/bcelx/classfile/ClassParser
[wlappc] [...]

Muuuuch better.  To fix it, now I know I need to explicitly define bcel*.jar in the classpath.  Here’s the modified ANT task:

<wlappc source=”${some.base.dir}”
classpath=”${some.dir}/some_class.jar;
${env.ANT_HOME}/lib/bcel-5.1.jar”
verbose=”true” idlVerbose=”true”/>

Notice the difference?  Yeah, that fixed it…