orpiske commented on PR #12966: URL: https://github.com/apache/camel/pull/12966#issuecomment-1932492310
> Due to the default activation rules, the full profile seems to interfere with the ability to run integration tests as a standalone task. The only way I could run them was via the profile that I created. If there is a combination of properties and profiles that enables integration tests to run, please let me know what that is, as it is not documented as far as I can tell. If you are running [as you described above](https://github.com/apache/camel/pull/12966#discussion_r1476489604) (where you said you were running the command `mvn failsafe:verify`), then you are **doing it wrong**. That's why the tests are not running for you. You should use `mvn verify` [as explained in the failsafe documentation](https://maven.apache.org/surefire/maven-failsafe-plugin/). > > I can try to move the profile to `parent/pom.xml` but it may not work, if my memory is correct. The only item to fix is the typo on the project's `pom.xml` file. > In any case, how would a contributor know what belongs in `pom.xml` vs `parent/pom.xml`? Typically, learning the details about a project happen organically: via reviews, discussions (on Zulip, here or on the mailing list, etc), etc. This is specially true a in project as large and as complex as Camel, with a rather small number of core contributors. We try our best to document how users can get started with [contributions in our Contributing Guide](https://camel.apache.org/camel-core/contributing/). In there, we link to a number of issues that are [good for first timers](https://issues.apache.org/jira/browse/CAMEL-20384?filter=12348073): issues and improvements that don't involve the project build, CI, core code, architecture and other items that may require a greater understanding of the project needs and requirements. [That's how many of us started](https://github.com/apache/camel/pull/2887). In many cases, we rely on convention over configuration (such as the case of running the unit tests using `mvn test` and the integration tests using `mvn verify`), so that contributors jumping from another project can reuse what they've learned. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
