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.

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

Script to create new binding skeleton: problem with file bundles/pom.xml #13405

Open
lolodomo opened this issue Sep 18, 2022 · 7 comments
Open
Labels
external bug A problem or unintended behavior of an external library

Comments

@lolodomo
Copy link
Contributor

lolodomo commented Sep 18, 2022

The script to create a new binding skeleton is generating a lot of changes in the file bundles/pom.xml. Only one line should be added (for the new binding) but in fact it generates a lot of more changes, certainly for formatting reason.

Tested with the Windows bat command file.

@lolodomo lolodomo added the bug An unexpected problem or unintended behavior of an add-on label Sep 18, 2022
@wborn
Copy link
Member

wborn commented Sep 19, 2022

Do you really mean bom/pom.xml or those new lines that are added to bundles/pom.xml?

@lolodomo
Copy link
Contributor Author

You,'re right, it is bundles/pom.xml. I correct issue title and description,

@lolodomo lolodomo changed the title Script to create new binding skeleton: problem with file bom/pom.xml Script to create new binding skeleton: problem with file bundles/pom.xml Sep 19, 2022
@lolodomo
Copy link
Contributor Author

lolodomo commented Sep 19, 2022

Look at current PR #13400 for an example.

wborn added a commit to wborn/openhab-addons that referenced this issue Sep 19, 2022
@wborn
Copy link
Member

wborn commented Sep 19, 2022

Look at PR #13418 for a workaround. 😉

@wborn wborn added external bug A problem or unintended behavior of an external library and removed bug An unexpected problem or unintended behavior of an add-on labels Nov 5, 2022
@wborn
Copy link
Member

wborn commented Oct 24, 2024

Is this still an issue for you @lolodomo now that ARCHETYPE-637 got fixed in 3.3.0 of the maven-archetype-plugin?
The scripts don't specify a version so they use the latest version.

@lolodomo
Copy link
Contributor Author

I can try during the coming weekend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external bug A problem or unintended behavior of an external library
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants