• Type: Bug
• Resolution: Done
• Priority: Major
• Fix Version/s: 35.0.0.Beta1, 35.0.0.Final
• Affects Version/s: None
• Component/s: Quickstarts
• Labels:

  None

[WFLY-18633] Remove openshift profile from quickstart's parent...

Collapse comment: Eduardo Martins added a comment - 2024/10/28 3:49 PM, Edited by Eduardo Martins - 2024/10/28 3:49 PM

Eduardo Martins added a comment - 2024/10/28 3:49 PM - edited

We should also take the opportunity and move the build/finalName configuration out of the parent, since that should be visible locally in each quickstart, so users see all they need to do to replicate.

Expand comment: Eduardo Martins added a comment - 2024/10/28 3:49 PM, Edited by Eduardo Martins - 2024/10/28 3:49 PM

Eduardo Martins added a comment - 2024/10/28 3:49 PM - edited We should also take the opportunity and move the build/finalName configuration out of the parent, since that should be visible locally in each quickstart, so users see all they need to do to replicate.

Collapse comment: Eduardo Martins added a comment - 2024/10/28 2:02 PM

Eduardo Martins added a comment - 2024/10/28 2:02 PM

Please note that this also means that we should move, to each QS pom.xml openshift profile, the following config:

                    <!-- do not attach sources to openshift deployments -->
                    <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-source-plugin</artifactId>
                        <executions>
                            <execution>
                                <id>attach-sources</id>
                                <phase>none</phase>
                            </execution>
                        </executions>
                    </plugin>

Expand comment: Eduardo Martins added a comment - 2024/10/28 2:02 PM

Eduardo Martins added a comment - 2024/10/28 2:02 PM Please note that this also means that we should move, to each QS pom.xml openshift profile, the following config: <!-- do not attach sources to openshift deployments --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-source-plugin</artifactId> <executions> <execution> <id>attach-sources</id> <phase>none</phase> </execution> </executions> </plugin>