[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aperi-dev] testable build: 20070423-171458
|
The Bulk Loader is my bug. Will fix.
Dave Wolfe/Portland/IBM
(dwolfe@xxxxxxxxxx)
TL: 775-3376 Office: 503-578-3376 Personal: 503-329-3960
UI Technical Lead, Aperi Open Source Storage Management
http://www.eclipse.org/aperi
"A good composer does not imitate; he
steals." - Igor Stravinsky
Simona Constantin <simona_constantin@xxxxxxxxxx>
Sent by: aperi-dev-bounces@xxxxxxxxxxx
04/24/2007 06:17 AM
|
Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx> |
|
|
To
| Todd Singleton/San Jose/IBM@IBMUS
|
|
cc
| aperi-dev-bounces@xxxxxxxxxxx, aperi-dev@xxxxxxxxxxx
|
|
Subject
| Re: [aperi-dev] testable build: 20070423-171458 |
|
Hello Todd,
I have tried the build aperi-20070423-171458.zip today on Linux while
fixing bugzilla bug 183478 and I encountered following problems:
-> the unix executables does not have execute permission set. It is
easy to see the cfgaperi does not have it but you figure out that there
are other scripts that need it when the installer come across them and
give IOException
-> The file scripts/db2config contains ^M(CRLF) characters which prevent
the bash from executing it.
-> The configuration ends with two errors ( see the output below).
Aperi Bulk Report Processor: Loader
repository directory = /usr/kits/simona/aperi/reports
zip file = ../reporting/configuration/canned-reports.zip
jdbcDriver = com.ibm.db2.jcc.DB2Driver
jdbcUrl = jdbc:db2://localhost:50001/Aperi
jdbcUser = db2inst1
Connection authorization failure occurred. Reason: password
invalid.
----
The output above should indicate that the schema was created
successfully on your system. If there was an error,
Aperi will not function correctly. Consult the installation
documentation for more information.
Configuring the report server...
../reporting/reporting
Error occurred while performing the configuration updates.
java.io.FileNotFoundException: ../configure/searchReplace.config (No such
file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at java.io.FileReader.<init>(FileReader.java:41)
at org.eclipse.aperi.configure.ConfigureAperi.reportServer(ConfigureAperi.java:739)
at org.eclipse.aperi.configure.ConfigureAperi.configure(ConfigureAperi.java:300)
at org.eclipse.aperi.configure.ConfigureAperi.configureAperi(ConfigureAperi.java:145)
at org.eclipse.aperi.configure.ConfigureAperi.main(ConfigureAperi.java:122)
---
Simona Constantin
Phone: +(40)-725.164.930;
Todd Singleton <toddsing@xxxxxxxxxx>
Sent by: aperi-dev-bounces@xxxxxxxxxxx
04/24/2007 03:56 AM
|
Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx> |
|
|
To
| aperi-dev@xxxxxxxxxxx
|
|
cc
|
|
|
Subject
| [aperi-dev] testable build: 20070423-171458 |
|
The build is now semi-automatic (sounds like a gun). The mysterious
org.eclipse.aperi.reporting bundle is now treated as a third-party bundle.
In this way, the rest of the build can run smoothly. The implication
of this: changes to the reporting bundle are NOT automatically incorporated
into the build. With every change to this bundle, please notify me
(or whoever is responsible for the build).
In the meanwhile, we will continue to hunt down the defect that inhibits
the compilation fo the reporting bundle.
Todd Singleton
Software Engineer, Tivoli, IBM
Bldg. 50, A152
5600 Cottle Road
San Jose, CA
email: toddsing@xxxxxxxxxx_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev
_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev
