Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!

Magnus Falk

Greenhorn
+ Follow
since Apr 17, 2008
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Magnus Falk

Yeah, I managed to figure that one out before, but the prospect of adding that directory to every single test case relying on that bundle was a bit daunting and I figured that it had to be a better way.

But anyways, it works now so I'm happy =) Thanks for the help!
Runtime classpath (I think). But I'm pretty sure I've managed to figure it out. It seems to simply be a matter of marking the directory as a source folder (as if it contained Java files) via Project->Build Path->New Source Folder.
In my project we're generating Eclipse project files on the fly based on our regular AND build.xml using a custom ANT target. That way we could just make another target to generate IDEA or Netbeans projects if we wanted.
In the project I'm working on we're reading resource bundles from the classpath and it works fine when doing regular ANT builds. We just put a directory on the classpath and are then able to reference our bundles in the code.

Eclipse however, can't stand the fact that we've included a non-JAR file in the classpath and treats it as an error. Is there a way around this?

Cheers,
Magnus