Details
-
Type:
Improvement
-
Status:
Reopened
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.6
-
Fix Version/s: None
-
Component/s: jira
-
Labels:None
-
Environment:Hide{code}
$ mvn -v
Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
Maven home: /usr/share/maven
Java version: 1.6.0_29, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac"
{code}Show{code} $ mvn -v Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac" {code}
-
Number of attachments :
Description
maven-changes-plugin is great and compiles a nice Jira report.
We need an ability to skip the Jira report compilation. Jira instance may not always be available when on different network or completely disconnected from Jira.
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-changes-plugin</artifactId> <version>2.6</version> <configuration> <skip>true<skip> ... </configuration> </plugin>
Skip flag above can then be parameterized.
I'm not sure if the plugin can be sensitive to --offline flag instead of <skip> flag.
When Jira is unavailable, current behavior just times out during the build. But build takes forever to complete waiting for times outs and retries.
Attached is the fix for this issue MCHANGES-279.
This fix checks for presence of --offline flag and accordingly skips the network operations expected for jira/trac reporting.