Skip to main content

Integrate JAVA development in your Team Foundation Environment

At our company, we are integrating JAVA development on our Team Foundation Server 2010 environment. Thanks to Team Explorer Everywhere and the nice Eclipse integration, this is very easy to do. So our JAVA developers can benefit from all the rich features offered by TFS.

There was only one step left to configure, integrating the JAVA build environment with TFS. Turns out, that this is very easy to achieve thanks to the Team Foundation Build Extensions. It provides the ability to execute Ant or Maven 2 builds from Team Foundation Server and publish the results of the build along with any associated JUnit test results back to Team Foundation Server.  This not only works for Team Foundation Server 2010, but also for Team Foundation Server 2005 and Team Foundation Server 2008.

How to get this done?

First install the JAVA JDK, Ant (if Ant support is required) or Maven 2 (if Maven support is required) on your build server. Afterwards install the build extensions on the build machine. In addition, you should configure the appropriate environment variables (i.e. JAVA_HOME, ANT_HOME, M2_HOME) as per the relevant install guidance for Ant and Maven. These environment variables should point to the correct install locations.

As a last step, you must create a build definition which makes use of them.  The easiest way to do this is to use a Microsoft Visual Studio Team Explorer Everywhere client to create the build definition.

That’s all!

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more