Bug 977867 - Jcr2vfs migration tool fails to start with 'could not find or load main class ...libs.aether-api-1.13.1.jar'
Jcr2vfs migration tool fails to start with 'could not find or load main class...
Status: CLOSED CURRENTRELEASE
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: Build and Assembly (Show other bugs)
6.0.0
Unspecified Unspecified
unspecified Severity high
: ---
: 6.0.0
Assigned To: Julian Coleman
Petr Široký
: TestBlocker
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-25 09:43 EDT by Petr Široký
Modified: 2014-08-06 16:18 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-08-06 16:18:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Petr Široký 2013-06-25 09:43:00 EDT
Description of problem:
Running the jcr2vfs migration tool results in the error "could not find or load main class ...libs.aether-api-1.13.1.jar".

Whole output: 
$ sh runMigration.sh
Usage: ./runMigration.sh
For example: ./runMigration.sh
Some notes:
- Working dir should be the directory of this script.
- Java is recommended to be JDK and java 6 for optimal performance
- The environment variable JAVA_HOME should be set to the JDK installation directory
  For example (linux): export JAVA_HOME=/usr/lib/jvm/java-6-sun
  For example (mac): export JAVA_HOME=/Library/Java/Home

Starting migration app...
Error: Could not find or load main class ...libs.aether-api-1.13.1.jar

Error occurred. Check if $JAVA_HOME (/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64) is correct.



Version-Release number of selected component (if applicable):
6.0.0-DR5

How reproducible:
Always

Steps to Reproduce:
1. Get and unzip the jcr2vfs migratool.
2. Execute "sh runMigration.sh"

Actual results:
Above error displayed.

Expected results:


Additional info:
Comment 1 Petr Široký 2013-06-25 09:51:01 EDT
This issue is not appearing with latest community bits, so maybe it was fixed in mean time or the productization process introduced this error. I will wait for DR6 to see if the error is still present.
Comment 2 Petr Široký 2013-07-17 10:34:26 EDT
Closing as the issue is fixed in 6.0.0-DR6.

Note You need to log in before you can comment on or make changes to this bug.