If a client can't connect to a training workstation via a direct VNC connection, or Microsoft Remote Desktop, we'll usually "fallback" to using the workstation sharing features built into WebEx Training Center.   We can connect the same EC2 instances to the WebEx Training Center, but we try to avoid doing this by default for a few reasons: The WebEx training lab workstation feature is very buggy and we could never get anyone from WebEx support to answer direct questions about this features, and there is currently no way to automate the registration of a workstation with WebEx Training Center.

If a training client cannot connect to WebEx due to security restrictions, we usually suggest onsite training.

Unfortunately, that version of the site does not yet have a Ruby DSL
available. We have to take some time to make sure that this site
reflects the current state of the project.

Ok, were there differences in the behavior between Maven 3 and Maven 2.2.1 on your project. What are the details of your particular project? All of this stuff, if you started to report it on the m2eclipse-users mailing list would be helpful to help diagnose what your particular issue is. If it comes down to some particular error, it'll go into our build as an integration test. But, we're going to need more information. Again, move the conversation over to m2eclipse-user there are a team of developers eagerly awaiting your problem report.

It isn't clear what that particular bug report is pointing to as an underlying problem. One issue may be that your build isn't working under the version of Maven 3.0 shipped with the plugin. Could you try pointing at the Maven installation you use from the command-line?

Also, if you want the fastest turn around, I'd suggest moving this conversation to the m2eclipse-users mailing list. Subscribe here:user-subscribe@m2eclipse.codehaus.org

It is likely that you haven't download the repository index. Open up
the Maven Repositories view and refresh the index for central.

Again, I've got some fairly complex dependencies and multi-module
projects that push the boundaries of Maven. They all work for me in
m2eclipse 0.10.0. If you took some time to ask a question of the
m2eclipse developers, and if you provided some details they'd probably
be able to either:

1. Help you identify a bug in m2eclipse, OR
2. Identify a problem with your project configuration.

Invest the time to provide details and you will get the assistance you need.

Hmmm, works fine for me, and I've got some pretty complex
interdependencies. Get more information and I'm sure m2eclipse
developers would be more than happy to help.

Hmmm... I don't know about easy. Contributing to open source projects involves a certain level of commitment. See the infamous Linus Torvalds email about making it "easier" to contribute to the kernel. Talking to one of our contributors on the phone yesterday I made the point that we're looking to make it easier to contribute (but not too easy).

At a minimum starting to contribute to the book takes about three hours of familiarization at best. You'll have to figure out the toolset, the naming conventions, and there are some rough edges in the book build that I'm still trying to work out with manfred moser.

Aside from that, I do think that we need a smallish introduction page that discusses tools (xmlmind) and build. These are stored in github at the moment and they couldn't be more difficult to find. We need some document that described the format, and it might make sense if that were an external project.

This particular book build has spawned a bunch of related book efforts, it might be time for a meta-book that describes the tools and process for end-to-end open source publishing.

First, I'm glad you solve your problem.

But, I think the idea of the GPG passphrase is that it is supposed to be the most secret thing you can imagine. When I created my PGP passphrase, I'm pretty sure that the program I was using told me not to write it down anywhere. If someone gets a hold of your private key and your passphrase, then they can forge signatures. While I'm glad this solves the problem, I'm not sure I'd recommend that anyone else do this. GPG passphrases are meant to be stored in only one place.... your own (biological) memory.

One of the reasons we've waited on this was to give the market more time to shake out formats. I think we've had sufficient time for this to happen, but I still want to wait at least one more week to see if this mythical "Apple Tablet" that everyone expects on the 27th will support one format over another.

The other thing i'm wary of is using some autogen tool to just convert from the book PDF to a mobile sized book. Programming books have unique constraints (many 80 character width code samples + wide screenshots). When I've tried to "downconvert" in the past i've seen poor results in terms of readability on small width devices. What am I trying to say? You probably won't see an iPhone-friendly version of these books. It is more likely that the end product will demand a higher width device.