Forem: binbingoloo

2025 macOS Development Environment Setup Guide

binbingoloo — Fri, 08 Aug 2025 18:15:02 +0000

A comprehensive guide to setting up a modern development environment on macOS with essential tools, terminal customization, and productivity applications.

Full Configurations: https://github.com/binbingoloo/.dotfiles

📋 Table of Contents

🍎 macOS Development Environment Setup Guide 2025
- 📋 Table of Contents
- 🎯 Overview
- What's Included
- 🚀 Getting Started
- Xcode Command Line Tools
- Homebrew Package Manager
- 🖥️ Terminal Setup
- Oh My Zsh
- Powerlevel10k Theme
- Zsh Plugins
  - 1. Zsh Completions
  - 2. Zsh Autosuggestions
  - 3. Zsh Syntax Highlighting
- Terminal Fonts
- 💻 Development Environment
- Language Version Managers
- IDEs & Development Tools
- CLI Power Tools
  - Additional Setup
- 🎨 Productivity Applications
- 🔧 Dotfiles Configuration

🎯 Overview

This guide provides a step-by-step approach to setting up a professional development environment on macOS. It covers everything from basic command-line tools to advanced terminal customization and productivity applications.

What's Included

✅ Package management with Homebrew
✅ Beautiful and functional terminal with Oh My Zsh and Powerlevel10k
✅ Version managers for Node.js, Python, Java, and Rust
✅ Essential development tools and IDEs
✅ Powerful CLI utilities for enhanced productivity
✅ Dotfiles management

🚀 Getting Started

Xcode Command Line Tools

First, install Xcode Command Line Tools which are required by many development tools:

xcode-select --install

Required for: Homebrew, Rust, Python native extensions, Git, and more.

Homebrew Package Manager

Install Homebrew, the missing package manager for macOS:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Add Homebrew to your PATH:

echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"

💡 Tip: Homebrew manages both CLI tools and GUI applications (via cask), providing a foundation for clean installs.

🖥️ Terminal Setup

Oh My Zsh

Install Oh My Zsh, a delightful framework for managing your Zsh configuration:

sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

⚠️ Note: Oh My Zsh will overwrite your existing ~/.zshrc. Make sure to append .zshrc.pre-oh-my-zsh to the new ~/.zshrc if needed.

Powerlevel10k Theme

Install Powerlevel10k, a fast and flexible Zsh theme:

git clone --depth=1 https://github.com/romkatv/powerlevel10k.git "${ZSH_CUSTOM:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k"

Update your ~/.zshrc:

ZSH_THEME="powerlevel10k/powerlevel10k"

Configure Powerlevel10k:

p10k configure

Zsh Plugins

1. Zsh Completions

Additional completion definitions for Zsh:

git clone https://github.com/zsh-users/zsh-completions.git \
  ${ZSH_CUSTOM:-${ZSH:-~/.oh-my-zsh}/custom}/plugins/zsh-completions

Add to ~/.zshrc before sourcing oh-my-zsh:

# zsh-completions
fpath+=${ZSH_CUSTOM:-${ZSH:-~/.oh-my-zsh}/custom}/plugins/zsh-completions/src
autoload -U compinit && compinit

source $ZSH/oh-my-zsh.sh

2. Zsh Autosuggestions

Fish-like autosuggestions for Zsh:

git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions

3. Zsh Syntax Highlighting

Fish shell-like syntax highlighting:

git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting

Update plugins in ~/.zshrc:

plugins=(
  git
  zsh-autosuggestions
  zsh-syntax-highlighting
)

Terminal Fonts

Install Nerd Fonts for better terminal experience:

brew install --cask font-hack-nerd-font
brew install --cask font-jetbrains-mono-nerd-font

💻 Development Environment

Language Version Managers

💡 Best Practice: Avoid installing Node, Python, or Java directly. Use version managers instead.

Language	Tool	Installation	Configuration
Node.js	nvm	`brew install nvm`	See below
Python	pyenv	`brew install pyenv`	See below
Java	sdkman	`curl -s "https://get.sdkman.io/" \	bash`
Rust	rustup	`curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs \	sh`

Add to your ~/.zshrc:

# NVM
export NVM_DIR="$HOME/.nvm"
[ -s "/opt/homebrew/opt/nvm/nvm.sh" ] && \. "/opt/homebrew/opt/nvm/nvm.sh"
[ -s "/opt/homebrew/opt/nvm/etc/bash_completion.d/nvm" ] && \. "/opt/homebrew/opt/nvm/etc/bash_completion.d/nvm"

# Pyenv
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init --path)"
eval "$(pyenv init -)"

# SDKMAN - THIS MUST BE AT THE END OF THE FILE
export SDKMAN_DIR="$HOME/.sdkman"
[[ -s "$HOME/.sdkman/bin/sdkman-init.sh" ]] && source "$HOME/.sdkman/bin/sdkman-init.sh"

IDEs & Development Tools

brew install --cask visual-studio-code
brew install --cask intellij-idea-ce
brew install --cask postman

CLI Power Tools

Essential command-line tools for enhanced productivity:

Tool	Installation	Description
WezTerm	`brew install --cask wezterm`	GPU-accelerated terminal emulator
tmux	`brew install tmux`	Terminal multiplexer for multiple sessions
Neovim	`brew install neovim`	Hyperextensible Vim-based text editor
zoxide	`brew install zoxide`	Smart cd command with directory history
fzf	`brew install fzf`	Fuzzy finder for files/history/search
fd	`brew install fd`	Fast and user-friendly alternative to find
ripgrep	`brew install ripgrep`	Lightning-fast recursive file search
bat	`brew install bat`	Cat clone with syntax highlighting
lsd	`brew install lsd`	Modern ls with icons and colors
git-delta	`brew install git-delta`	Syntax-highlighting pager for git
jq	`brew install jq`	Command-line JSON processor
lazygit	`brew install lazygit`	Simple terminal UI for git commands
gh	`brew install gh`	GitHub's official command line tool
htop/btop	`brew install htop btop`	Interactive process viewers

Additional Setup

zoxide - Add to ~/.zshrc:

eval "$(zoxide init zsh)"

fzf - Run the install script:

$(brew --prefix)/opt/fzf/install

fzf-tab - Enhanced tab completions:

git clone https://github.com/Aloxaf/fzf-tab ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/fzf-tab

🎨 Productivity Applications

Application	Installation	Description
Notion	`brew install --cask notion`	All-in-one workspace
Obsidian	`brew install --cask obsidian`	Knowledge base with local Markdown
Discord	`brew install --cask discord`	Communication platform
Stats	`brew install --cask stats`	System monitoring in menu bar
Ice	`brew install --cask jordanbaird-ice`	Menu bar organizer
KeyCastr	`brew install --cask keycastr`	Keystroke visualizer
Flameshot	`brew install --cask flameshot`	Screenshot and annotation tool

🔧 Dotfiles Configuration

Create symbolic links for your dotfiles:

# Create symlinks for configuration files
ln -sf $(pwd)/.zprofile ~/.zprofile
ln -sf $(pwd)/.zshrc ~/.zshrc
ln -sf $(pwd)/.vimrc ~/.vimrc
ln -sf $(pwd)/.tmux.conf ~/.tmux.conf
ln -sf $(pwd)/.p10k.zsh ~/.p10k.zsh
ln -sf $(pwd)/.gitmessage ~/.gitmessage
ln -sf $(pwd)/.gitconfig ~/.gitconfig
ln -sf $(pwd)/.fzf.zsh ~/.fzf.zsh
ln -sf $(pwd)/.editorconfig ~/.editorconfig
ln -sf $(pwd)/.config/nvim ~/.config/nvim
ln -sf $(pwd)/.config/lazygit/config.yml ~/Library/Application\ Support/lazygit/config.yml
ln -sf $(pwd)/.config/bat ~/.config/bat
ln -sf $(pwd)/.config/lsd ~/.config/lsd
ln -sf $(pwd)/.config/wezterm ~/.config/wezterm

"SOAP 1.1 endpoint already registered" - Spring 6 and CXF 4 Integration Issue

binbingoloo — Wed, 06 Aug 2025 06:23:47 +0000

During our recent upgrade from Spring 3 to Spring 6 while using CXF 4, we encountered a perplexing issue:

SOAP 1.1 endpoint already registered on address /soap/xxxService

Root Cause

We discovered that Spring 6's enhanced bean lifecycle management conflicts with CXF's endpoint registration mechanism. Here's what happens:

1. Spring 6 Configuration Loading Changes

Spring 6 introduced stricter bean definition and lifecycle management, which can cause CXF endpoints to be registered multiple times through different mechanisms:

// Multiple registration paths:
// 1. Auto-discovery via @WebService annotations
// 2. Explicit XML configuration
// 3. Java-based configuration
// 4. CXF's internal auto-configuration

2. The Duplicate Registration Scenario

Without proper CXF initialization, endpoints get registered multiple times:

<!-- XML Configuration -->
<jaxws:endpoint id="xxxService" 
                implementor="#xxxServiceImpl"
                address="/soap/xxxService" />

<!-- Component Scanning might also pick up the same service -->
<context:component-scan base-package="com.example.service" />

3. Missing CXF Core Configuration

Spring 6 no longer automatically loads certain CXF configurations that were previously handled implicitly, leading to an improperly initialized CXF Bus and DestinationRegistry.

Why Importing CXF Configuration Files Solves the Issue

The Role of `cxf.xml`

The META-INF/cxf/cxf.xml file contains essential CXF infrastructure beans:

<beans xmlns="http://www.springframework.org/schema/beans"...>
    <!-- CXF Bus - the core of CXF -->
    <bean id="cxf" class="org.apache.cxf.bus.spring.SpringBus" destroy-method="shutdown">
        <!-- ... -->
    </bean>

    <!-- Ensures Bus singleton pattern -->
    <bean id="org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor"
          class="org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor">
        <!-- ... -->
    </bean>
</beans>

Solution

Add the imports to your Spring configuration:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:jaxws="http://cxf.apache.org/jaxws"
       xsi:schemaLocation="...">

    <!-- Import CXF core configurations -->
    <import resource="classpath:META-INF/cxf/cxf.xml"/>

    <!-- Your endpoint definitions -->
    <jaxws:endpoint id="xxxService"
                    implementor="com.example.service.XxxServiceImpl"
                    address="/soap/xxxService">
        <jaxws:properties>
            <entry key="schema-validation-enabled" value="true"/>
        </jaxws:properties>
    </jaxws:endpoint>
</beans>

The imported configurations guarantee that only one CXF Bus is created and properly initialized. The DestinationRegistry from cxf-servlet.xml maintains a single registry of all endpoints Explicit configuration takes precedence over any auto-discovery mechanisms.

"No qualifying bean of type 'jakarta.xml.ws.WebServiceContext' available"

binbingoloo — Wed, 06 Aug 2025 03:57:58 +0000

Description

We recently undertook a major technology stack upgrade, migrating from:

JDK 8 → JDK 21
Spring 3 → Spring 6.x
WebSphere (WAS) → Tomcat 10
CXF → CXF 4.x

During this migration, we encountered the following error:

No qualifying bean of type 'jakarta.xml.ws.WebServiceContext' available

Root Cause

After extensive investigation, we discovered that Spring 6 removed the built-in JAX-WS support that was previously available in Spring 5 and earlier versions. This change wasn't prominently documented in the Spring 6 migration guide, making it a hidden pitfall for teams upgrading legacy applications.

The issue occurs because:

Spring's CommonAnnotationBeanPostProcessor tries to inject WebServiceContext as a regular Spring bean
WebServiceContext is not a Spring-managed bean - it should be handled by the JAX-WS runtime (CXF in our case)
Spring 6 no longer automatically excludes WebServiceContext from dependency injection

Research and References

During our investigation, we found several relevant resources:

Key insights from these resources:

Solution

For Spring Framework Applications (Our Case)

Since we're using Spring Framework without Spring Boot, we adapted the CxfJaxwsAutoConfiguration from Spring Boot for our application.

Here's how Spring Boot handles it:

@Configuration
@ConditionalOnClass({ Resource.class, WebServiceContext.class })
public class CxfJaxwsAutoConfiguration {
    @Bean
    static BeanFactoryPostProcessor jaxwsBeanFactoryPostProcessor() {
        return new BeanFactoryPostProcessor() {
            @Override
            public void postProcessBeanFactory(ConfigurableListableBeanFactory beanFactory) throws BeansException {
                final var beans = beanFactory.getBeansOfType(CommonAnnotationBeanPostProcessor.class, true, false);
                // The {@code javax.xml.ws.WebServiceContext} interface should be ignored since it will 
                // be resolved by the CXF's JAX-WS runtime.
                beans.forEach((name, bean) -> bean.ignoreResourceType(WebServiceContext.class.getName()));
            }
        };
    }
}

Our Implementation

We created a custom configuration class for our Spring Framework application:

package com.yourcompany.config;

import jakarta.annotation.Resource;
import jakarta.xml.ws.WebServiceContext;
import org.springframework.beans.BeansException;
import org.springframework.beans.factory.config.BeanFactoryPostProcessor;
import org.springframework.beans.factory.config.ConfigurableListableBeanFactory;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.CommonAnnotationBeanPostProcessor;
import org.springframework.context.annotation.Configuration;

@Configuration
public class CxfJaxwsConfiguration {

    @Bean
    public static BeanFactoryPostProcessor jaxwsBeanFactoryPostProcessor() {
        return new BeanFactoryPostProcessor() {
            @Override
            public void postProcessBeanFactory(ConfigurableListableBeanFactory beanFactory) throws BeansException {
                // Check if the required classes are available
                if (!isClassPresent("jakarta.annotation.Resource") || 
                    !isClassPresent("jakarta.xml.ws.WebServiceContext")) {
                    return;
                }

                final var beans = beanFactory.getBeansOfType(CommonAnnotationBeanPostProcessor.class, true, false);
                // Tell Spring to ignore WebServiceContext for dependency injection
                // CXF's JAX-WS runtime will handle it instead
                beans.forEach((name, bean) -> bean.ignoreResourceType(WebServiceContext.class.getName()));
            }
        };
    }

    private static boolean isClassPresent(String className) {
        try {
            Class.forName(className, false, CxfJaxwsConfiguration.class.getClassLoader());
            return true;
        } catch (ClassNotFoundException e) {
            return false;
        }
    }
}

How It Works

The BeanFactoryPostProcessor runs early in the Spring context initialization
It finds all CommonAnnotationBeanPostProcessor instances
It instructs them to ignore WebServiceContext when processing @Resource annotations
This allows CXF's JAX-WS runtime to properly inject WebServiceContext instead of Spring trying to find it as a bean

I hope this helps others facing the same issue during their Spring 6 migration!

Forem: binbingoloo

2025 macOS Development Environment Setup Guide

📋 Table of Contents

🎯 Overview

What's Included

🚀 Getting Started

Xcode Command Line Tools

Homebrew Package Manager

🖥️ Terminal Setup

Oh My Zsh

Powerlevel10k Theme

Zsh Plugins

1. Zsh Completions

2. Zsh Autosuggestions

3. Zsh Syntax Highlighting

Terminal Fonts

💻 Development Environment

Language Version Managers

IDEs & Development Tools

CLI Power Tools

Additional Setup

🎨 Productivity Applications

🔧 Dotfiles Configuration

"SOAP 1.1 endpoint already registered" - Spring 6 and CXF 4 Integration Issue

Root Cause

1. Spring 6 Configuration Loading Changes

2. The Duplicate Registration Scenario

3. Missing CXF Core Configuration

Why Importing CXF Configuration Files Solves the Issue

The Role of cxf.xml

Solution

"No qualifying bean of type 'jakarta.xml.ws.WebServiceContext' available"

Description

Root Cause

Research and References

Solution

For Spring Framework Applications (Our Case)

Our Implementation

How It Works

The Role of `cxf.xml`