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.

Sign up for GitHub

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

Jump to bottom

Issue #283: Update issue report generation #284

Merged
merged 2 commits into from
Jan 16, 2023
Merged

Issue #283: Update issue report generation #284

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
60fd04f
Issue #283: Update issue report generation
reckart Jan 16, 2023
ff7f3e4
Issue #283: Update issue report generation
reckart Jan 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 marker-file-identifying-parent-pom → marker-file-enabling-changes-report
View file
Open in desktop
File renamed without changes.
32 changes: 24 additions & 8 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,23 +331,39 @@
</profile>

<profile>
<id>apache-release</id>
<id>generate-changes-report</id>
<activation>
<file>
<exists>marker-file-enabling-changes-report</exists>
</file>
</activation>
<build>
<plugins>
<plugin>
<artifactId>maven-changes-plugin</artifactId>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>default-cli</id>
<!--
- Copies the legacy Jira issue report to the issuesFixed folder. We cannot simple
- configure the uimaj-legacy-jira-report module to write the report directly there
- because otherwise it woudl be cleaned during the clean phase of the root module.
-->
<id>copy-legacy-jira-issues-report-to-issues-fixed-folder</id>
<phase>generate-resources</phase>
<goals>
<goal>github-report</goal>
<goal>run</goal>
</goals>
<configuration>
<columnNames>Type,Id,Status,Summary</columnNames>
<onlyCurrentVersion>true</onlyCurrentVersion>
<githubAPIScheme>https</githubAPIScheme>
<githubAPIPort>443</githubAPIPort>
<target>
<!--
GitHub changes report is always generated, Jira only during release builds,
so it could be missing - hence failonerror="false"
-->
<copy todir="${basedir}/issuesFixed" failonerror="false">
<fileset dir="uimaj-legacy-jira-report/target/issuesFixed"/>
</copy>
</target>
</configuration>
</execution>
</executions>
Expand Down
12 changes: 10 additions & 2 deletions uimaj-legacy-jira-report/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,9 +59,17 @@
<goal>jira-report</goal>
</goals>
<configuration>
<columnNames>Type,Key,Status,Summary</columnNames>
<outputDirectory>${project.basedir}/../issuesFixed</outputDirectory>
<useJql>true</useJql>
<fixVersionIds>${jiraVersion}</fixVersionIds>
<columnNames>Type,Key,Status,Summary</columnNames>
<resolutionIds>Fixed</resolutionIds>
<statusIds>Closed,Resolved</statusIds>
<sortColumnNames>Type, Key</sortColumnNames>
<!-- changed sortColumnNames for Jira 5
was: <sortColumnNames>Status, Key, Type</sortColumnNames>
-->
<outputDirectory>target/issuesFixed</outputDirectory>
<maxEntries>1000</maxEntries> <!-- hopefully, bigger than ever needed -->
</configuration>
</execution>
</executions>
Expand Down
2 changes: 0 additions & 2 deletions uimaj-parent/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -276,8 +276,6 @@
<!-- See: https://issues.apache.org/jira/browse/UIMA-6349 -->
<groupId>com.github.siom79.japicmp</groupId>
<artifactId>japicmp-maven-plugin</artifactId>
<!-- Version can be removed after updating to the UIMA Parent POM 16 or higher -->
<version>0.15.7</version>
<configuration>
<newVersion>
<file>
Expand Down