I've created a new thread for this as I want to get it out of the UI thread.



This is b/c all of the jar's dependencies are not present. The way that I test the jar built by maven (the latest build) is:

In the ted-core directory, run:



This will build the latest ted jar (placing it in the target folder), and will copy the jar's dependencies into the target/dependency folder.

Next I copy the newly built jar file into the dependency folder and run ted from there.

So, I never use the 'runnable ted' folder.

Euh, and what if you're working with Windows and there is no command line? I assume you've to use the Maven plugin for Eclipse but I wouldn't know which option it then would be.


I think we should move this one out of the main folder and make a development build folder in the releases branch.

Okay I managed to get it to work.

The only problem I now have is that the new jar will only open with the noTray command. Do any of you know what the problem could be there?

I think the JDIC libraries are not correctly copied or not present in the folder of your ted.jar?

Yep... That sounds about right.


I'm working on a mvn process to copy everything in the right place during the maven 'package' phase.

I should be able to get that in place over the weekend.

I've created a ticket in flyspray for this.

https://ted.nu/bugs/index.php?do=details&task_id=301

Please take a look as I have some questions about the jdic.jar and OS specific files.

Edit Jofo: adjust url in post as you took over ownership of the issue by clicking on it

Mike, any progress on this issue? I tried to get ted to work with jdic this weekend but I failed miserably. I just can't figure out why it does work in Eclipse but doesn't do it after you created the jar.

Just about finished. I have a few questions though...

Does the tray support require only the stub_jdic.jar files, or does it also require the .so files under the <os>/x86 folder as well?

I'm struggling with learning how this works.

However... hold tight, I'll see if I can get this committed for tonight.

Ah... Looks like Jdic.jar is not being put in the manifest by maven.

I'm working now, but I'll fix it tonight and get it committed.

Cheers.

As far as i know, the jdic jar files function as a kind of proxy to the platform specific files that implement jdic functionality in a language that is not java. So we still need everything in the sub folders, since that is where all the magic happens.

Just to let you know...

I worked on this issue last night for a little while, and finally found a way around this issue (thanks for the insight Kenny).

I'll be able to finish it up tonight and close off this issue.

Okay cool, looking forward to being able to build a new jar

I'll see if I can make a dev build with all the needed jars.

Just committed a fix for this.

Here's the run-down.


To build a runnable version of Ted, run the following from the ted-core directory:



When this is completed, a runnable directory should be created in:

ted/ted-core/target/

If you run the ted jar in this 'runnable' directory everything should now work.

Let me know if you have any problems.


You can also do this through eclipse if the IAM plugin is installed.
1) Right click the ted-core project.
2) Maven 2 --> Run Goal
3) Enter 'package' as the goal
4) Click OK.

Also, there are currently some test jars that get copied into the runnable directory that are not needed. My plan is to eventually use maven's assembly plugin to assemble a proper release.

The solution above will get you going for now.

Forget about the previous comment.

Only runtime dependencies are now being copied into the runnable folder.

Okay thanks! I don't have time before Sunday to check it out but I'll then have a look at it.