ProjectAssist Installation Errors (part 3)

Moving along, I decided to try the ProjectAssist install on a different machine, which we will be using for a development server, instead of doing it on my standalone XP workstation. Maybe the installer will work better on this environment.

I did a fresh install of Windows 2000 SP4, and then installed Project Assist, using all the defaults except

1. install dir was c:\dev
2. data dir was c:\dev\data
3. added the smtp url & port.
4. I added a settings.xmp file to .m2 dir to handle the maven proxy access.
5. I added perl’s environment variable to handle the perl proxy access.

When the installer finished, it displayed a list of all errors (shown below). There were lots of them.

Here are the reported errors:

ProjectAssist Installation Errors (part 2)

Having determined the cause of the maven issues, I moved on and cleaned up my system and restarted the install.

I then got perl errors, which the log listed as:

(13:22:49:671) Installing C:\borland\projectassist\Perl\site\lib\Net\LDAP\Extension\WhoAmI.pm
(13:22:49:671) Perl install: processing INSTALL component AppConfig...
(13:22:53:609) Can't call method "ok" on an undefined value at c:/Borland/ProjectAssist/Perl/site/lib/PPM/UI.pm line 881, line 21.
(13:22:53:609) Perl install: ppm command did not succed (exitCode 1):
c:\borland\projectassist\Perl\bin\perl -x -S PPM install c:\borland\projectassist\bugzilla_perl_modules\AppConfig.ppd
(13:22:53:609) Perl install: processing INSTALL component Template-Toolkit...
(13:22:57:218) Can't call method "ok" on an undefined value at c:/Borland/ProjectAssist/Perl/site/lib/PPM/UI.pm line 881, line 17.
(13:22:57:218) Perl install: ppm command did not succed (exitCode 1):
c:\borland\projectassist\Perl\bin\perl -x -S PPM install c:\borland\projectassist\bugzilla_perl_modules\Template-Toolkit.ppd


ProjectAssist Installation Errors (part 1)

After concluding that ProjectAssist does not like “partial installs”, I decided to go with the complete install.

I cleaned up the XP install (removed apache, tomcat, mysql etc and made sure there were no registry entries or services) and fired up ProjectAssist.

Creating a new configuration was pretty straightforward, all I had to change from the defaults was to set my smtp server address.

I pretty quickly got an error at the step where it was configuring maven2. The error I received was:

Warnings and/or errors were posted. Click the "Details" button to see the install log.
Installation failed: Error creating sample project with Maven
java.lang.Exception
com.borland.dsib.r.g.a(Unknown Source)
com.borland.dsib.r.g.d(Unknown Source)
com.borland.dsib.r.g.a(Unknown Source)
com.borland.dsib.r.d.d(Unknown Source)
com.borland.dsib.ub.b(Unknown Source)
com.borland.dsib.ub.h(Unknown Source)
com.borland.dsib.ub.a(Unknown Source)
com.borland.dsib.utilities.m.a(Unknown Source)
com.borland.dsib.utilities.m.access$0(Unknown Source)
com.borland.dsib.utilities.m$1.run(Unknown Source)
java.lang.Thread.run(Thread.java:595)

Looking into this error, it seems that Maven needs internet access to update it’s dependencies.

ProjectAssist Administration Notes

In the continuing saga of attempting to get ProjectAssist working, I spent the last week trying to get my “development stack” configured.

I would have to say that at the moment, I am not yet impressed.

The idea behind using Project Assist was:

“ProjectAssist dramatically reduces the time and complexity to create new team and project definitions”

Unfortunately, I have now spent more time debugging the Project Assist installation process than I would have spend just installing the supported projects manually.

Here is what I ran into:

More on ProjectAssist

Much thanks to Joe McGlynn (Director Product Management @ Codegear) for his assistance in getting ProjectAssist up and running for me. Now that I am able to test the functionality, I can see how the server installation goes.

I will post more in a few days when I find out more.

C Programming in Eclipse

In my day to day job, I mainly use java, primarily for the development of graphical interfaces to communicate with custom built hardware running embedded microprocessors (written in assembly and c). In addition though, I also write c and c++ for backend code that needs to run really fast, or needs to do stuff that java has a hard time with.

For example, I am working on a project that uses JNI to integrate a java GUI to a c++ dll, which does some complex data processing for GPS location triangulation. This code is already working in c++ and I don’t want to have top reingineer it in java, as it involves some very ugly math.

I have recently made a switch to eclipse(jbuilder) for java development.

ProjectAssist Update:

Quick update to my last post:

While I have been recently confronted with some issues with codegear’s new suite of product, I do respect their willingness to resolve issue and make things right. I posted a note about my issue on the borland newsgropups and got a response this morning…

ProjectAssist Woes!

Just when I thought my troubles were over after getting my system licensed, the fun with ProjectAssist began.

I am a regular user (and administrator) of some of the ProjectAssist’s supported open source technologies.

When I first heard about ProjectAssist, I was excited:

Registration Issues Resolved

I am pleased to say that after a couple of months of hassling with the registration process, I now have a registered copy of JBuilder Enterprise Trial.

Thanks goes out to the customer support engineer in Singapore who figured out that in addition to deleting the “.borland” directory in my “my documents” folder, I also had to delete one other directory in the same place, (which started with a dot and then had a bunch of garbage characters.) For example: “.fkpihgnfgtc”.