Thanks for the reply, I was guessing it may have something to due with the new 1.8 modding framework. Even though you've addressed the issue, I'm including the post I was working on as it may be helpful to others trying to get Magic Launcher working with these new builds.
I just tried build 1410 and got the same result, no jar file in the versions folder.
Also, I failed to mention in the previous post that even without the jar files, the Minecraft Launcher 1.6.11 does show the the forge versions, I can create profiles from those versions, I can launch with those profiles, and the splash screen reports MCP v9.10, FML v8.99.4.1410, and Minecraft Forge 11.14.1.1410. I can open and play a world and was even able to load a mod.
My only real issue then is that I normally use Magic Launcher to manage mods and it wants the jar file in the versions folder but I have no jar file to make it happy.
Ok, I did some more research and found in the fml-client logs that it's working because it's using a jar file from ".minecraft\libraries\net\minecraftforge\forge\<forge-version>". I tried copying that file to the versions folder but that didn't make Magic Launcher happy. I noticed in the fml-client logs that it also uses ".minecraft\versions\1.8\1.8.jar" so I set the Magic Laucher Environment to 1.8-Forge11.14.1.1410 and Minecraft.jar to the "....minecraft\versions\1.8\1.8.jar". This seems to make Magic Launcher happy and I can use it to manage 1.8 mods. It's not as convenient as before but it seems to work. Now if I could Optifine 1.8.4 working....