maven-build

Execute a full Maven build across multi-module Java and C# projects.

Updated Jul 1, 2024
One-click install
npx skills add https://github.com/biz-Stream/bizprint --skill maven-build-biz-stream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maven-build
Source: https://github.com/biz-Stream/bizprint/tree/main/.claude/skills/maven-build
Command: npx skills add https://github.com/biz-Stream/bizprint --skill maven-build-biz-stream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures the entire multi-module project builds and packages correctly before committing or pushing, preventing broken builds and inconsistent encryption keys between client and server modules.

Core Features & Use Cases

  • Full project build: Runs a clean build across all modules to validate compilation and packaging.
  • Packaging & installer steps: Includes packaging phases required for Java, C# assemblies, and installer generation on Windows.
  • Pre-commit / CI validation: Useful as a local pre-commit check or as a verification step in CI pipelines to catch build and packaging errors early.
  • Operational note: Requires consistent encryption keys across server and client modules and a Windows environment for C# and Inno Setup steps.

Quick Start

Run a full Maven clean install from the repository root to validate all modules before committing.

Frequently Asked Questions about maven-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a full Maven build to validate a multi-module project before committing?

To validate a multi-module project, run a full Maven clean install from the repository root. This executes a clean build across all Java and C# modules to verify compilation and packaging before a commit.

What does a Maven clean install validate in a multi-module Java and C# project?

A Maven clean install validates that the entire multi-module Java and C# project compiles and packages correctly. It ensures a clean build across all modules and runs packaging steps to prevent broken builds.

Do I need Visual Studio and .NET Framework to run a Maven build for C# modules?

Yes, running a Maven build that includes C# modules requires Visual Studio and the .NET Framework. You also need the JDK and Maven for Java modules, and Inno Setup for installer generation on Windows.

Why does my Maven build fail due to inconsistent encryption keys between client and server modules?

Maven builds fail when there are inconsistent encryption keys between client and server modules. Running a full project build validates compilation while ensuring consistent encryption keys across modules to prevent packaging errors.

Can I use Maven to generate installers with Inno Setup in a CI pipeline?

Yes, you can use Maven to generate installers with Inno Setup as a CI pipeline verification step. This process runs packaging and installer generation steps on Windows to catch build and packaging errors early.

When do I need to run packaging and installer generation steps in a Maven build?

You need to run packaging and installer generation steps during pre-commit or CI verification scenarios. This ensures that Java, C# assemblies, and Windows installers are correctly packaged before integration.