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

[Build] Fix main profile activation by default #10814

Merged
merged 1 commit into from
Jun 3, 2021

Conversation

lhotari
Copy link
Member

@lhotari lhotari commented Jun 3, 2021

Fixes #10791

Motivation

Additional context

  • In maven, activeByDefault works only if no other profile is already active.
  • When JDK11 changes were made, a profile jdk11 was added which gets activated when JDK version >= 11. This broke the activeByDefault solution for activating the main profile.

Modifications

  • Use a better solution to activate the main profile by default by using a property value with inversion (!) rule.

@lhotari lhotari requested a review from eolivelli June 3, 2021 11:35
@lhotari lhotari self-assigned this Jun 3, 2021
@lhotari lhotari added type/bug The PR fixed a bug or issue reported a bug area/build labels Jun 3, 2021
@lhotari lhotari added this to the 2.8.0 milestone Jun 3, 2021
@lhotari lhotari merged commit 94fec9d into apache:master Jun 3, 2021
sijie pushed a commit that referenced this pull request Jun 18, 2021
### Motivation

Similar to #10814, functions module build failed due to the falg `activeByDefault` fail to activate the profile if any other profile is activated.

### Modifications

- Use a better solution to activate the `main` profile by default by using a property value with inversion (`!`) rule.
yangl pushed a commit to yangl/pulsar that referenced this pull request Jun 23, 2021
- Use a better solution to activate the main profile by default by using a property value with inversion (!) rule.
- The previous solution used <exists><file>pom.xml</file></exists> which doesn't work in all cases for some reason.
- In maven, activeByDefault works only if no other profile is already active. This isn't usable since there's already a profile called jdk11 which is active.
yangl pushed a commit to yangl/pulsar that referenced this pull request Jun 23, 2021
### Motivation

Similar to apache#10814, functions module build failed due to the falg `activeByDefault` fail to activate the profile if any other profile is activated.

### Modifications

- Use a better solution to activate the `main` profile by default by using a property value with inversion (`!`) rule.
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
- Use a better solution to activate the main profile by default by using a property value with inversion (!) rule.
- The previous solution used <exists><file>pom.xml</file></exists> which doesn't work in all cases for some reason.
- In maven, activeByDefault works only if no other profile is already active. This isn't usable since there's already a profile called jdk11 which is active.
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
### Motivation

Similar to apache#10814, functions module build failed due to the falg `activeByDefault` fail to activate the profile if any other profile is activated.

### Modifications

- Use a better solution to activate the `main` profile by default by using a property value with inversion (`!`) rule.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"mvn package" has not built any jar
3 participants