Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add 4.9.0 to Catalog for Main and Spring Boot #1691

Merged
merged 3 commits into from
Dec 9, 2024
Merged

feat: Add 4.9.0 to Catalog for Main and Spring Boot #1691

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0fd682d
feat: Add 4.9.0 to Catalog for Main, Spring Boot and kamelets
apupier Dec 4, 2024
7c9db89
chore: fix Camel 4.9.0 tests
lordrip Dec 5, 2024
7afe558
feat: Update Kamelet Catalog to 4.9.0
apupier Dec 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions packages/catalog-generator/scripts/build-catalogs.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,16 +15,16 @@ const require = createRequire(import.meta.url);
const CATALOGS = {
// https://repo1.maven.org/maven2/org/apache/camel/camel-catalog/
// https://maven.repository.redhat.com/ga/org/apache/camel/camel-catalog/
Main: ['4.8.2', '4.4.4', '4.4.0.redhat-00046', '4.8.0.redhat-00017'],
Main: ['4.9.0', '4.8.2', '4.4.4', '4.4.0.redhat-00046', '4.8.0.redhat-00017'],
// https://repo1.maven.org/maven2/org/apache/camel/quarkus/camel-quarkus-catalog/
// https://maven.repository.redhat.com/ga/org/apache/camel/quarkus/camel-quarkus-catalog/
Quarkus: ['3.16.0', '3.8.4', '3.8.0.redhat-00018', '3.15.0.redhat-00007'],
// https://repo1.maven.org/maven2/org/apache/camel/springboot/camel-catalog-provider-springboot/
// https://maven.repository.redhat.com/ga/org/apache/camel/springboot/camel-catalog-provider-springboot/
SpringBoot: ['4.8.2', '4.4.4', '4.4.0.redhat-00039', '4.8.0.redhat-00022'],
SpringBoot: ['4.9.0', '4.8.2', '4.4.4', '4.4.0.redhat-00039', '4.8.0.redhat-00022'],
};
// https://repo1.maven.org/maven2/org/apache/camel/kamelets/camel-kamelets/
const KAMELETS_VERSION = '4.8.1';
const KAMELETS_VERSION = '4.9.0';

const generateCatalogs = () => {
let camelCatalogPath = '';
Expand Down
4 changes: 2 additions & 2 deletions packages/ui/src/components/Form/dataFormat/DataFormatEditor.test.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ describe('DataFormatEditor', () => {
fireEvent.change(inputElement, { target: { value: 'json' } });
});
dropdownItems = screen.getAllByTestId(/dataformat-dropdownitem-.*/);
expect(dropdownItems).toHaveLength(3);
expect(dropdownItems).toHaveLength(4);
});

it('should clear filter and close the dropdown with close button', async () => {
Expand All @@ -174,7 +174,7 @@ describe('DataFormatEditor', () => {
fireEvent.change(inputElement, { target: { value: 'json' } });
});
let dropdownItems = screen.getAllByTestId(/dataformat-dropdownitem-.*/);
expect(dropdownItems).toHaveLength(3);
expect(dropdownItems).toHaveLength(4);
const clearButton = screen.getByLabelText('Clear input value');
await act(async () => {
fireEvent.click(clearButton);
Expand Down
38 changes: 27 additions & 11 deletions ...els/visualization/flows/support/__snapshots__/camel-component-schema.service.test.ts.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -303,13 +303,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -656,13 +656,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -860,6 +860,14 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"title": "Backoff Multiplier",
"type": "integer",
},
"browseLimit": {
"default": 100,
"deprecated": false,
"description": "Maximum number of messages to keep in memory available for browsing. Use 0 for unlimited.",
"group": "advanced",
"title": "Browse Limit",
"type": "integer",
},
"bufferSize": {
"default": 131072,
"deprecated": false,
Expand Down Expand Up @@ -1449,13 +1457,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -1561,6 +1569,14 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"title": "Bridge Error Handler",
"type": "boolean",
},
"browseLimit": {
"default": 100,
"deprecated": false,
"description": "Maximum number of messages to keep in memory available for browsing. Use 0 for unlimited.",
"group": "advanced",
"title": "Browse Limit",
"type": "integer",
},
"bufferSize": {
"default": 131072,
"deprecated": false,
Expand Down Expand Up @@ -2243,13 +2259,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should not build a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -2436,13 +2452,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should transform a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -2587,7 +2603,7 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should transform a
"type": "string",
},
"variableSend": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down
Loading