Replies: 7 comments 9 replies
-
From the error message you are using |
Beta Was this translation helpful? Give feedback.
-
Appears to derive (at least for me) from the use of 'qualifier' as part of the
|
Beta Was this translation helpful? Give feedback.
-
We always get this warning in Tycho 3.0.5 too in our RCP Product build - https://github.com/archimatetool/archi We also only use Only occurs when building a |
Beta Was this translation helpful? Give feedback.
-
Locally I just upgraded Maven from 3.6.3 to 3.9.2 and I also started to receive these warnings: [WARNING] Plugin issue(s): When I go back to Maven 3.6.3 they disappear. |
Beta Was this translation helpful? Give feedback.
-
We see this message in our Eclipse Memory Analyzer builds with Tycho 2.7.5. E.g. https://ci.eclipse.org/mat/job/tycho-mat-nightly/1411/consoleFull
|
Beta Was this translation helpful? Give feedback.
-
I think this is more a "maven feature" so the used maven version influence if the warning is shown or not. |
Beta Was this translation helpful? Give feedback.
-
See also #2644. Basically p2-publisher injects a value into the maven model, and later maven validation complains, because read-only configuration arguments should not have a value. |
Beta Was this translation helpful? Give feedback.
-
After migrating to Tycho 4.0.0-SNAPSHOT from Tycho 2.7.5, we now get the following warnings in our build:
It occurs several times in the build of our product:
I can't find any
qualifier
in our repo that relates to this (only in bundle/feature versions, etc). I can't find anybuildQualifier
in our repo at all. We do make use offorceContextQualifier
for thetycho-packaging-plugin
(not sure if that is related or not).Do you have any idea what is causing this warning?
Beta Was this translation helpful? Give feedback.
All reactions