PDA

View Full Version : SDK fix - default.properties



dhartford
04-20-2006, 06:41 AM
should update the default.properties file for:

solutions.dir=../pentaho-solutions/test

Do not know what should be corrected for:
scripts.dir=./scripts/demo

dhartford
04-20-2006, 07:16 AM
Another SDK problem (04-18-2006) is:

11:13:25,631 ERROR [AuditEntry] java.lang.ClassNotFoundException: org.pentaho.audit.AuditFileEntry

should be org.pentaho.core.audit.AuditFileEntry

dhartford
04-20-2006, 08:03 AM
Ignore AuditFileEntry problem above ---

This should be documented as an UPGRADE requirement for the pentaho-solutions folder. The pentaho.xml file should be replaced/updated to reflect new class names.

dhartford
05-24-2006, 06:47 AM
dhartford wrote:

should update the default.properties file for:

solutions.dir=../pentaho-solutions/test

Do not know what should be corrected for:
scripts.dir=./scripts/demo

As of 05-19-2006 SDK, this has not been corrected and the above still has to be done.

scripts.dir, I manually create that directory.

Post edited by: dhartford, at: 05/24/2006 10:48

bhagan
05-25-2006, 11:06 AM
Hi dhartford,

The latest SDK should have the change to the pentaho.xml that you pointed out.

As for the properties file, the workspace as described in the SDK is a little different than we use here, and it can be different for every developer.

The idea behind providing the properties and all the targets in the SDK is to get you, the developer, looking at how we built our demo applications, which should give you enough knowledge to then either tweak these files for your own solutions or use the platform SDK in your own framework, which I see you've already done by changing the value of the solutions directory and the scripts dir to suit your needs.

Have a great day,

Brian

gmoran
05-25-2006, 12:30 PM
Hi dhartford,

The best way for you to work with the default.properties values that you want to change is to NOT change the default.properties file at all, but to take advantage of Ant's ability to use an override file.

If you create a file named build.properties in the same directory as your default.properties file, then place the offending properties in that file (solutions.dir and scripts.dir) with the values that you want, the Ant script will pick up your new values over the the ones that are specified in the default.properties file.

This is standard Ant behavior. The value this provides to you is that you don't have to merge the default.properties file everytime you get a new SDK. And your build.properties file always lives locally with your custom values in it.

Also you'll be pleased to know that we will be providing anonymous read access to our subversion repository soon (soon is relative to a mountain of other tasks:) ), so working in our development environment should get much easier.

Hope this helps you out,
Gretchen