In order for the phone to be registered for development, it also needs to be browse-able in File Explorer when the phone is connected. In my experience, the most common problem is assuming that any USB cable is compatible when in fact some cables are only useful for charging: Windows Phone 8 is not detected by your computer
When there are problems you may see the following screens:
When the phone is properly detected, you will see the following:
Upon clicking "Register", if your phone is also connected to the Internet, you will see the following in moments and be able to deploy your applications to the device:
Based on following the steps in the official PhoneGap documentation, the following document augments that information with more details, specifically around setting up on Windows 8 and for developing Windows Phone 8/Android apps:
If you encounter a "Cannot connect to service" error, consider attempting with JConsole first by running <JAVA_HOME>/bin/jconsole -debug to determine the reason why; Troubleshooting connection problems in JConsole
Generations - describes Java memory management. It will help you interpret the graphs in the Visual GC plugin
This turns out to be at the Subversion check-out step:
You can click on "Update credentials" to go to a screen to enter in your credentials. But you might get the following error:
HTTP ERROR 500
Problem accessing /hudson/job/PWS-OCDT/descriptorByName/hudson.scm.SubversionSCM/postCredential. Reason:
hudson.model.Job.hasCascadingProject()Z
Caused by:
java.lang.NoSuchMethodError: hudson.model.Job.hasCascadingProject()Z
at hudson.scm.PerJobCredentialStore.getXmlFile(PerJobCredentialStore.java:137)
At this point, check the file-system of your Hudson server. Under <HUDSON_HOME>\jobs\<Job name> you may notice that compared to Jobs that are working, the problematic job does not have a "subversion.credentials" file. Copy over this file as-is to the directory. No Hudson re-start is necessary; just go back to the Dashboard and choose the problematic Job. From this point, you should be able to choose "Update credentials" and work through the screens without getting an unhelpful
hudson.model.Job.hasCascadingProject()Z
error. FYI, this is Hudson ver. 2.1.2 and our Subversion server location changed, which may have caused this issue.
While looking for a Java development podcast (still looking!), I came across JavaScript Jabber. While the focus is JavaScript, there are episodes with more generic topics like Software Team Dynamics. The podcasters are all experienced developers from various backgrounds (e.g. .NET, Ruby, etc.), the audio quality is good, and the shownotes are excellent. Furthermore, they have sponsors so you know they have great content that attracts listeners.
The available repositories that can be added to the Group ("Public Repositories") is on the right (see below). Intuitively, shouldn't they be on the left, and you move them over to the right? By default, newly added Repositories show up in the right column ("Available Repositories").
The main message is that there needs to be validation of the product idea up front, rather than getting the product idea wrong and potentially killing a start-up one or two years down the road. This is not prototyping which can be considered verifying that the underlying technologies should work together but a stage prior to this, using "arts and crafts"-type materials rather than hardware/software.
The secondary message is that calling yourself a tester, even an automation tester, or "quality assurance person" is detrimental to one's career as these skills are thought of as commodities. That is, the person is interchangeable with an offshore resource. Rather QA people should take the role of "righters" or people that make a project "right". I argue that everyone on a project should be responsible for making a project "right", but from past experience, getting your voice heard can be challenging, especially on more hierarchical teams. Also inertia is a hard thing to fight.
