v3 Stack Coordinates Update

The v3 train is now aligned on a single coordinate strategy to prepare the stack for upcoming v4 work.

What changed

• Modules in the v3 stack now use groupId com.norconex.collectors.v3.
• The train is synchronized on version 3.2.0-SNAPSHOT.
• Maven artifact path for new v3 builds is now under com/norconex/collectors/v3/....

Download and Maven behavior

Download links and Maven snippets on this site now switch automatically based on artifact version:

• Versions earlier than 3.2.0-SNAPSHOT keep legacy coordinates.
• Versions starting at 3.2.0-SNAPSHOT use the new v3 coordinates.

Elasticsearch Committer note

The Elasticsearch Committer previously had a higher historical version line (5.x) under legacy coordinates. Starting with the v3 coordinate migration, it follows the v3 train stream under com.norconex.collectors.v3 and aligns with 3.2.0-SNAPSHOT.

See also the Elasticsearch Committer page for product-specific context.

Filesystem Collector joins the v3 stack

The Filesystem Collector is now aligned with the v3 stack coordinates and synchronized train versioning. This puts it on the same dependency and release stream as the rest of the v3 crawler modules.

See also the Filesystem Collector page for product-specific details.

Google Cloud Search Committer in v3 stack

The Google Cloud Search Committer now has a Norconex-managed 3.x release line in the synchronized v3 stack, using the same coordinate strategy and release train versioning.

The older 2.x line developed and hosted by Google remains available as a legacy option.

See also the Google Cloud Search Committer page for current and legacy setup information.

This keeps historical releases stable while making the v3 line explicit and clean moving forward.