Jemplode47 src - org.jempeg.empeg.music is empty

As the subject says...

I can't find JOrbisTagExtractor or TFFID3TagWriter...

OK. Now I'm confused. I mean, I'm just copying files over and zipping them! grumblegrumblegrumble. Let me go check wtf is going on.

weird -- somehow they were marked as being ignored by CVS, so eclipse wasn't copying them when i copied the folder. I'm attaching a zip of the jempeg-empeg/src/org/jempeg/empeg/music/tags folder.

ms

Muttermuttergrumble
I'd only just built some dummy stubs when someone goes and posts the real things...



Oops, err, "package com.tffenterprises.music.io does not exist"
It appears that my dummy stubs *were* far superior to the real thing

Unfortunately I can't put out the source to that one ... That's owned by Daniel Zimmerman. So to compile, you'll need to put jemplode.jar in your classpath (or take out com.tffenterprises out of the jar and just put that in there)

OK - ta.

phew - having fun.
Just downloaded eclipse and seem to have gotten your projects imported (less rmm and tests)

Noticed that the v47 src has:
public static String VERSION_STRING = "46";

Wondered why the debugger was showing V46 for a while...
It ran - and I thought it was attaching to an already running Jemplode - got v confused - in my pessimistic state that actually seemed more likely than I'd actually gotten a Java IDE to work and built someone else's code


PS Eclipse looks great!

In reply to:

---

Just downloaded eclipse and seem to have gotten your projects imported (less rmm and tests)

---

Yeah -- i share testcases between jEmplode and RMMLite, so there are some cross dependencies in there. You could probably just remove the dependency on the "rmmlite" project and delete the offending java's that don't compile.

In reply to:

---

Noticed that the v47 src has:
public static String VERSION_STRING = "46";

---

This is in Version.java? I just grabbed the source zip and it says 47. You sure you got the latest? Maybe there's another rogue version string floating around -- what file is that in?

In reply to:

---

Wondered why the debugger was showing V46 for a while...

---

Something's definitely funky ... It's possible the jemplode.jar you have in your classpath to resolve some of those missing dependencies might be overriding the source files? I would doubt that, but i suppose it's possible -- might want to check the project build order to make sure source comes first?

In reply to:

---

PS Eclipse looks great!

---

By far the best Java IDE, IMO. It's fast and incredibly featureful ... the refactoring tools are just amazing.

ms

It was me.

The source file has:
* @version $Revision: 1.2 $
and the latest files (CVS control files) in the zip are dated 24/10/03 06:37

So I suspect I got the v46 source - maybe my v47 download aborted - dunno. Doesn't matter - I'm getting the latest now...

Done, built, running and in my cvs server
Trying to figure out the eclipse CVS interface and how it interacts with command line CVS now.

Oh man -- the Eclipse CVS interface is really nice ... great ui for branching, tagging, merging, exporting/importing patches. My only major complaints are about branch/tag discovery, but that's more of a general problem with CVS than eclipse in particular (though they managed to find the most confusing UI for it). I used to be a hardcore commandline CVS person, and I almost never touch the commandline except in the most complex of cases.

ms