Skip to content

Conversation

@amandalindsay
Copy link
Contributor

For https://hazelcast.atlassian.net/browse/DOC-606

Apply same changes to windowing.adoc as per #580 (#1883) which corrected the artifacts for the samples so these point to the correct versions. Affects lines 57 & 58 in windowing.adoc

@k-jamroz Please also take a look at the authors question on line 32:

// AUTHORS NOTE: if we are to tell them to use mvn clean install to build the project, where
// should this go? Here or later in the process, such as line 203 instead of mvn package?
// For example "Run mvn clean install to make sure you can build the project and get its artifacts locally."
// Does that sound OK? If so, I will apply the same chnage in the map-join.adoc file which is similar.

Please advise

@amandalindsay amandalindsay added the backport to 5.5 Backport commits from main to v/5.5 label Sep 29, 2025
@netlify
Copy link

netlify bot commented Sep 29, 2025

Deploy Preview for hardcore-allen-f5257d ready!

Name Link
🔨 Latest commit ad475f8
🔍 Latest deploy log https://app.netlify.com/projects/hardcore-allen-f5257d/deploys/68db99e920bea0000822dc92
😎 Deploy Preview https://deploy-preview-1895--hardcore-allen-f5257d.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

<dependencies>
<dependency>
<groupId>com.hazelcast.jet</groupId>
<artifactId>hazelcast-jet</artifactId>
Copy link
Contributor

@k-jamroz k-jamroz Sep 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

jet is now part of main distribution

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry @k-jamroz I don't understand what this means in terms of the changes required to the doc. Can you please markup what, if anything, needs to be updated on lines 49-52, plus advise what we should say about mvn clean install as per Authors Note above. Thanks

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is no hazelcast-jet artifact (JAR) anymore. everything is contained in hazelcast and hazelcast-enterprise

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see https://github.com/hazelcast/hz-docs/pull/1895/files#r2411354148, if there are other references to hazelcast-jet artifacts they should also be changed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but the extensions, like hazelcast-jet-kafka etc. still exist as sepearate modules

Comment on lines 55 to 56
<groupId>com.hazelcast.jet</groupId>
<artifactId>hazelcast-jet</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<groupId>com.hazelcast.jet</groupId>
<artifactId>hazelcast-jet</artifactId>
<groupId>com.hazelcast</groupId>
<artifactId>hazelcast</artifactId>

into it:
`trade-monitor` and copy the Maven file into it:

// AUTHORS NOTE: if we are to tell them to use mvn clean install to build the project, where
Copy link
Contributor

@k-jamroz k-jamroz Oct 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there are 2 different builds:

  1. you need to build hazelcast-code-samples/ project
  2. the example project in this tutorial uses some JAR created by hazelcast-code-samples/ project but is a separate project

the workflow should be roughly (this will build all examples, not only jet-related):

git clone https://github.com/hazelcast/hazelcast-code-samples.git
cd hazelcast-code-samples
mvn clean install

this should be performed in "Before You Begin" section

then you create java project etc. and step 3 (mvn clean package) remains the same.

Note that I have not tested these commands - worth checking for typos or if I missed sth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport to 5.5 Backport commits from main to v/5.5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants