-
1. Re: Cannot debug from Eclipse (Mac OS 10.7, Drive 3.01)
xujieadobe Jan 17, 2012 8:06 PM (in response to Shigli)Hi:
In some occasions Adobe Drive does not work well with 64 bit JVM. So my suggestion is:
1. Uninstall x86_64 java environment from your system if possible. Or at least set your system Path variable to point to 32 bit JVM's bin path. Verify it works well by type java -version in the command window.
2. Install a 32 bit Eclipse.
3. Clean your old configurations by delete the original Eclipse working directory.
4. Follow the document to set up environment.
The csstat command is provided by bundle com.adobe.drive.connector.service. Make sure its status is "ACTIVE" before you use it.
Hope this will work for you.
J.
-
2. Re: Cannot debug from Eclipse (Mac OS 10.7, Drive 3.01)
Shigli Jan 18, 2012 5:46 AM (in response to xujieadobe)Thanks so much for the suggestions.
I haven't tried the 32 bit JVM yet, but your comments got me thinking about which bundles I have selected in my run configuration. When I first tried selecting ALL bundles, I got an error when launching:
The bundle could not be resolved. Reason: Missing Constraint: Import-Package: com.adobe.versioncue.serialization; version="0.0.0"
To correct that, I had gone back to the run configuration, cleared all bundles, and pressed the "Add Required Bundles" button. This only added a small subset of all bundles, but got rid of the validation error.
I now went back and selected all bundles, despite the validation error, and now I am successfully able to launch the sample.basicftp bundle from Eclipse on one of my two machines. The other one doesn't work, and when I go type 'ss' I see one of the bundles seems to get stuck in the STARTING state:
com.adobe.csi.bootstrap_2.0.0.201003221714
I can probably continue working with my one working machine, but something still doesn't seem right.
1) Should I be seeing that "Missing Constraint" error above? If not, then where do I find the bundle that it is looking for?
2) Any idea why the com.adobe.csi.bootstrap is getting stuck in the STARTING state.
Once again, thanks so much for your help!
-
3. Re: Cannot debug from Eclipse (Mac OS 10.7, Drive 3.01)
xujieadobe Jan 18, 2012 6:50 AM (in response to Shigli)There should be no error messages when lunching. Switch to 32 bit JVM is still the first thing you should do, otherwise you could run into other weird errors.
If you don't want to remove your 64 bit JDK, you can try this:
1. Install a 32 bit JDK1.5.
2. Delete Eclipse workspace folder.
3. Open Eclipse preferences, add the newly installed JDK to Installed JREs, and set it as default and click Apply and OK.
4. Follow the instructions in the document.
5. In Eclipse preferences, go to Plug-in Development -> Target Platform, double click the newly added platform "Adobe Drive", switch to Environment tab, select the 32 bit JRE other than Default JRE.
6. In the Run configuration, make sure the 32 bit JRE is selected in the "Settings" tab.
Good luck.


