[jira] (MSCMPUB-4) Need a working example for GitHub/gh-pages, preferably naturally linked to natural site lifecycle, and multi-module
[
https://jira.codehaus.org/browse/MSCMPUB-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340388#comment-340388
]
Anthony Whitford commented on MSCMPUB-4:
For the *Maven Multi Module Configuration* advice, it mentions this command:
{noformat}
mvn -Preporting site site:stage
{noformat}
Is the {{reporting}} profile necessary? (Because it doesn't seem to exist.)
I am able to stage the site just fine, but the next step:
{noformat}
mvn scm-publish:publish-scm
{noformat}
is failing for me with:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:1.0-SNAPSHOT:publish-scm
(default-cli)
on project lombok-maven: Execution default-cli of goal
org.apache.maven.plugins:maven-scm-publish-plugin:1.0-SNAPSHOT:
publish-scm failed: The scm url cannot be null. - [Help 1]
{noformat}
The root issue seems to be here:
{noformat}
Caused by: java.lang.NullPointerException: The scm url cannot be null.
at
org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:195)
at
org.apache.maven.shared.release.scm.DefaultScmRepositoryConfigurator.getConfiguredRepository(DefaultScmRepositoryConfigurator.java:78)
at
org.apache.maven.shared.release.scm.DefaultScmRepositoryConfigurator.getConfiguredRepository(DefaultScmRepositoryConfigurator.java:67)
{noformat}
And the debug information for the plugin is:
{noformat}
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-scm-publish-plugin:1.0-SNAPSHOT:publish-scm from
plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-scm-publish-plugin:1.0-SNAPSHOT,
parent: sun.misc.Launcher$AppClassLoader@713c817]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-scm-publish-plugin:1.0-SNAPSHOT:publish-scm'
with basic configurator --
[DEBUG] (f) automaticRemotePathCreation = true
[DEBUG] (f) basedir = /Users/anthony/Documents/lombok.maven
[DEBUG] (f) checkinComment = Site checkin for project Maven Plugin for
Project Lombok
[DEBUG] (f) checkoutDirectory =
/Users/anthony/Documents/lombok.maven/target/scmpublish-checkout
[DEBUG] (f) content = /Users/anthony/Documents/lombok.maven/target/staging
[DEBUG] (f) localCheckout = false
[DEBUG] (s) pubScmUrl = scm:git:g...@github.com:awhitford/lombok.maven.git
[DEBUG] (f) scmBranch = gh-pages
[DEBUG] (f) siteOutputEncoding = UTF-8
[DEBUG] (f) skipDeletedFiles = false
[DEBUG] (f) tryUpdate = false
[DEBUG] (f) project = MavenProject:
org.projectlombok:lombok-maven:1.12.4.0-SNAPSHOT @
/Users/anthony/Documents/lombok.maven/pom.xml
[DEBUG] (f) settings = org.apache.maven.execution.SettingsAdapter@dcd88ea
[DEBUG] -- end configuration --
{noformat}
_Am I doing something wrong?_
Need a working example for GitHub/gh-pages, preferably naturally linked to
natural site lifecycle, and multi-module
---
Key: MSCMPUB-4
URL: https://jira.codehaus.org/browse/MSCMPUB-4
Project: maven-scm-publish-plugin
Issue Type: Story
Environment: Mac OSX 10.8.2, Java 1.6 Update 35, Maven 3.0.4, Maven
Site Plugin 3.2, Maven SCM Plugin 1.8, Git
Reporter: Anthony Whitford
Priority: Critical
I am trying to update my
[lombok-maven-plugin|http://awhitford.github.com/lombok.maven/lombok-maven-plugin/index.html]
project to use this plugin to publish the project to _Github Pages_.
When I try this command:
{noformat}
mvn clean site site:stage-deploy scm-publish:publish-scm
{noformat}
which is outlined
[here|http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/multi-module-configuration.html],
I get this error:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:1.0-beta-1:publish-scm
(default-cli) on project lombok-maven: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-log command failed.
[ERROR] Command output:
[ERROR] fatal: ambiguous argument 'master': unknown revision or path not in
the working tree.
[ERROR] Use '--' to separate paths from revisions
{noformat}
(?) Is there a multi-module project in GitHub that uses this plugin that I
can use as an example?
This is what I did so far...
{code:xml}
properties
siteMainDirectory${user.home}/Sites/lombok.maven/siteMainDirectory
scmPubCheckoutDirectory${user.home}/site-content-scm/lombok.maven/scmPubCheckoutDirectory
/properties
...
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version3.2/version
configuration
skipDeploytrue/skipDeploy
stagingSiteURLfile://${siteMainDirectory}/stagingSiteURL
/configuration
/plugin
...
/plugins
/pluginManagement
...
plugins
[jira] (MENFORCER-184) enforce-(don't)-exist rules should support wildcards
Martin Höller created MENFORCER-184: --- Summary: enforce-(don't)-exist rules should support wildcards Key: MENFORCER-184 URL: https://jira.codehaus.org/browse/MENFORCER-184 Project: Maven Enforcer Plugin Issue Type: New Feature Components: Standard Rules Reporter: Martin Höller With the standard rules enforce-exist and enforce-dont-exist it is possible to ensure files exist resp. do not exist. Unfortunately the files must be specified with the exact name! Wildcards are currently not supported. My concrete use case is, I wan't to enforce, that no *Test.class files exist in some output-directory. This is currently not possible. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-184) enforce-(don't)-exist rules should support wildcards
[
https://jira.codehaus.org/browse/MENFORCER-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Höller updated MENFORCER-184:
Description:
With the standard rules enforce-exist and enforce-dont-exist it is possible to
ensure files exist resp. do not exist. Unfortunately the files must be
specified with the exact name! Wildcards are currently not supported.
My concrete use case is, I wan't to enforce, that no *Test.class files exist in
some output-directory. This is currently not possible. Some configuration like
the following should be supported:
{{ rules
requireFilesDontExist
messageIntegration-Test classes must be named *IT but *Test
classes exist./message
includes
include${project.build.testOutputDirectory}/at/co/xss/lib/service/mail/DummyTest.*/include
/includes
/requireFilesDontExist
/rules}}
was:
With the standard rules enforce-exist and enforce-dont-exist it is possible to
ensure files exist resp. do not exist. Unfortunately the files must be
specified with the exact name! Wildcards are currently not supported.
My concrete use case is, I wan't to enforce, that no *Test.class files exist in
some output-directory. This is currently not possible.
enforce-(don't)-exist rules should support wildcards
Key: MENFORCER-184
URL: https://jira.codehaus.org/browse/MENFORCER-184
Project: Maven Enforcer Plugin
Issue Type: New Feature
Components: Standard Rules
Reporter: Martin Höller
With the standard rules enforce-exist and enforce-dont-exist it is possible
to ensure files exist resp. do not exist. Unfortunately the files must be
specified with the exact name! Wildcards are currently not supported.
My concrete use case is, I wan't to enforce, that no *Test.class files exist
in some output-directory. This is currently not possible. Some configuration
like the following should be supported:
{{ rules
requireFilesDontExist
messageIntegration-Test classes must be named *IT but
*Test classes exist./message
includes
include${project.build.testOutputDirectory}/at/co/xss/lib/service/mail/DummyTest.*/include
/includes
/requireFilesDontExist
/rules}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-184) enforce-(don't)-exist rules should support wildcards
[
https://jira.codehaus.org/browse/MENFORCER-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Höller updated MENFORCER-184:
Description:
With the standard rules enforce-exist and enforce-dont-exist it is possible to
ensure files exist resp. do not exist. Unfortunately the files must be
specified with the exact name! Wildcards are currently not supported.
My concrete use case is, I wan't to enforce, that no *Test.class files exist in
some output-directory. This is currently not possible. Some configuration like
the following should be supported:
{code}
rules
requireFilesDontExist
includes
include${project.build.outputDirectory}/**/*Test.*/include
/includes
/requireFilesDontExist
/rules
{code}
was:
With the standard rules enforce-exist and enforce-dont-exist it is possible to
ensure files exist resp. do not exist. Unfortunately the files must be
specified with the exact name! Wildcards are currently not supported.
My concrete use case is, I wan't to enforce, that no *Test.class files exist in
some output-directory. This is currently not possible. Some configuration like
the following should be supported:
{{ rules
requireFilesDontExist
messageIntegration-Test classes must be named *IT but *Test
classes exist./message
includes
include${project.build.testOutputDirectory}/at/co/xss/lib/service/mail/DummyTest.*/include
/includes
/requireFilesDontExist
/rules}}
enforce-(don't)-exist rules should support wildcards
Key: MENFORCER-184
URL: https://jira.codehaus.org/browse/MENFORCER-184
Project: Maven Enforcer Plugin
Issue Type: New Feature
Components: Standard Rules
Reporter: Martin Höller
With the standard rules enforce-exist and enforce-dont-exist it is possible
to ensure files exist resp. do not exist. Unfortunately the files must be
specified with the exact name! Wildcards are currently not supported.
My concrete use case is, I wan't to enforce, that no *Test.class files exist
in some output-directory. This is currently not possible. Some configuration
like the following should be supported:
{code}
rules
requireFilesDontExist
includes
include${project.build.outputDirectory}/**/*Test.*/include
/includes
/requireFilesDontExist
/rules
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNGSITE-194) Fix links and content around Nexus and Sonatype Maven books
[ https://jira.codehaus.org/browse/MNGSITE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340411#comment-340411 ] Tamás Cservenák commented on MNGSITE-194: - Applied as http://svn.apache.org/viewvc?view=revisionrevision=1562849 Fix links and content around Nexus and Sonatype Maven books --- Key: MNGSITE-194 URL: https://jira.codehaus.org/browse/MNGSITE-194 Project: Maven Project Web Site Issue Type: Improvement Reporter: Manfred Moser Priority: Critical Attachments: MNGSITE-194.diff I will provide a patch with some updates shortly. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNGSITE-194) Fix links and content around Nexus and Sonatype Maven books
[ https://jira.codehaus.org/browse/MNGSITE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák closed MNGSITE-194. --- Resolution: Fixed Assignee: Tamás Cservenák Patch applied as http://svn.apache.org/viewvc?view=revisionrevision=1562849 Fix links and content around Nexus and Sonatype Maven books --- Key: MNGSITE-194 URL: https://jira.codehaus.org/browse/MNGSITE-194 Project: Maven Project Web Site Issue Type: Improvement Reporter: Manfred Moser Assignee: Tamás Cservenák Priority: Critical Attachments: MNGSITE-194.diff I will provide a patch with some updates shortly. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Attachment: MNG-5176.patch
I have updated the patch again.
maven.git
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [ 13.717 s]
[INFO] Maven Model ... SUCCESS [ 13.419 s]
[INFO] Maven Artifact SUCCESS [ 7.287 s]
[INFO] Maven Plugin API .. SUCCESS [ 10.522 s]
[INFO] Maven Model Builder ... SUCCESS [ 15.180 s]
[INFO] Maven Settings SUCCESS [ 5.521 s]
[INFO] Maven Settings Builder SUCCESS [ 6.470 s]
[INFO] Maven Repository Metadata Model ... SUCCESS [ 4.796 s]
[INFO] Maven Aether Provider . SUCCESS [ 14.340 s]
[INFO] Maven Core SUCCESS [ 51.760 s]
[INFO] Maven Compat .. SUCCESS [ 32.400 s]
[INFO] Maven Embedder SUCCESS [ 11.244 s]
[INFO] Apache Maven Distribution . SUCCESS [ 17.697 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 03:24 min
[INFO] Finished at: 2014-01-30T13:48:26+01:00
[INFO] Final Memory: 55M/278M
[INFO]
{noformat}
and
maven-scm.git
{noformat}
[INFO] Applying mojo extractor for language: java
[INFO] Mojo extractor for language: java found 0 mojo descriptors.
[INFO] Applying mojo extractor for language: bsh
[INFO] Mojo extractor for language: bsh found 0 mojo descriptors.
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Maven SCM . SUCCESS [01:37 min]
[INFO] Maven SCM API . SUCCESS [ 49.921 s]
[INFO] Maven SCM Managers SUCCESS [ 5.292 s]
[INFO] Maven SCM Manager for Plexus .. SUCCESS [ 19.543 s]
[INFO] Maven SCM Test SUCCESS [ 43.112 s]
[INFO] Maven SCM Providers ... SUCCESS [ 5.782 s]
[INFO] Maven SCM AccuRev Provider SUCCESS [ 46.710 s]
[INFO] Maven SCM Bazaar Provider . SUCCESS [ 31.212 s]
[INFO] Maven SCM Clearcase Provider .. SUCCESS [ 38.130 s]
[INFO] Maven SCM CVS Provider - Parent ... SUCCESS [ 5.618 s]
[INFO] Maven SCM CVS Provider TCK tests .. SUCCESS [ 26.636 s]
[INFO] Maven SCM CVS Provider - Common library ... SUCCESS [ 49.035 s]
[INFO] Maven SCM CVS Provider - CVS Executable Impl. . SUCCESS [ 28.367 s]
[INFO] Maven SCM CVS Provider - CVS Java Impl. ... SUCCESS [ 38.279 s]
[INFO] Maven SCM Mercurial (Hg) Provider . SUCCESS [ 37.785 s]
[INFO] Maven SCM Git Provider - Parent ... SUCCESS [ 5.479 s]
[INFO] Maven SCM Git Provider - Common library ... SUCCESS [ 30.737 s]
[INFO] Maven SCM Git Provider TCK Tests .. SUCCESS [ 29.046 s]
[INFO] Maven SCM Git Provider - Git Executable Impl. . SUCCESS [ 49.699 s]
[INFO] Maven SCM Git Provider - JGit Impl. ... SUCCESS [ 38.159 s]
[INFO] Maven SCM Local Provider .. SUCCESS [ 33.002 s]
[INFO] Maven SCM Perforce Provider ... SUCCESS [ 39.655 s]
[INFO] Maven SCM Starteam Provider ... SUCCESS [ 36.574 s]
[INFO] Maven SCM Subversion Provider - Parent SUCCESS [ 5.515 s]
[INFO] Maven SCM Subversion Provider - Common library SUCCESS [ 30.390 s]
[INFO] Maven SCM Subversion Provider TCK Tests ... SUCCESS [ 23.621 s]
[INFO] Maven SCM Subversion Provider - SVN Executable Impl. SUCCESS [ 50.651 s]
[INFO] Maven SCM Synergy Provider SUCCESS [ 34.258 s]
[INFO] Maven SCM Visual Source Safe Provider . SUCCESS [ 36.695 s]
[INFO] Maven SCM TFS Provider SUCCESS [ 31.799 s]
[INFO] Maven SCM MKS Integrity Provider .. SUCCESS [ 45.573 s]
[INFO] Maven SCM Jazz/Rational Team Concert Provider . SUCCESS [ 39.437 s]
[INFO] Maven SCM Standard Providers .. SUCCESS [ 10.255 s]
[INFO] Maven SCM Client .. SUCCESS [ 29.600 s]
[INFO] Maven SCM Plugin .. SUCCESS [01:23 min]
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Attachment: iso8601-duration-alt.png
Durations overview ISO 8601:2006
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: iso8601-duration-alt.png, MNG-5176.patch,
MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final
[jira] (MPIR-292) On the Modules report, the links to sub-sub-modules are not correctly generated
[
https://jira.codehaus.org/browse/MPIR-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340415#comment-340415
]
Michael Osipov commented on MPIR-292:
-
I think it should **not** be displayed because if you define in menu
ref=modules in your {{site.xml}} you have direct descendants only. Behavior
should be the same.
On the Modules report, the links to sub-sub-modules are not correctly
generated
---
Key: MPIR-292
URL: https://jira.codehaus.org/browse/MPIR-292
Project: Maven Project Info Reports Plugin
Issue Type: Bug
Affects Versions: 2.7
Reporter: Anghel Botos
Priority: Minor
Attachments: FixSubSubModulesLinks.patch, MyProjectSite.zip,
MyProject.zip
On the Modules report (About project page), the links to sub-sub-modules are
not correctly generated.
In the attached MyProject.zip file I have the following project structure:
project
**subProject
subSubProject
I've ran site and site:deploy, the resulting site is located in
MyProjectSite.zip. If you open the index.html you will see that on the About
project page, in the table, both the subProject and the subSubProject are
listed as modules, but only the link to the direct child (subProject) is
correct, while the link to the subSubProject is incorrect.
I've also added a patch that fixes this problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNGSITE-194) Fix links and content around Nexus and Sonatype Maven books
[ https://jira.codehaus.org/browse/MNGSITE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340432#comment-340432 ] Manfred Moser commented on MNGSITE-194: --- Thanks Tamas. Fix links and content around Nexus and Sonatype Maven books --- Key: MNGSITE-194 URL: https://jira.codehaus.org/browse/MNGSITE-194 Project: Maven Project Web Site Issue Type: Improvement Reporter: Manfred Moser Assignee: Tamás Cservenák Priority: Critical Attachments: MNGSITE-194.diff I will provide a patch with some updates shortly. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-307) Check for whitespace on fixVersionIds and statusIds
[
https://jira.codehaus.org/browse/MCHANGES-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340433#comment-340433
]
Anthony Whitford commented on MCHANGES-307:
---
I might be getting this issue too with Jira 6.1.5:
{noformat}
[INFO] Generating JIRA Report report--- maven-changes-plugin:2.9
[WARNING]
org.apache.maven.plugin.MojoFailureException: Could not find status Resolved.
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:259)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:240)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:206)
at
org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:128)
at
org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:367)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
{noformat}
Note that I don't see the extra space being an issue... My pom configuration
looks like:
{code:xml}
configuration
jiraUserXXX/jiraUser
jiraPassword/jiraPassword
maxEntries500/maxEntries
onlyCurrentVersiontrue/onlyCurrentVersion
statusIdsResolved,Closed/statusIds
useJqltrue/useJql
/configuration
reportSets
reportSet
reports
reportjira-report/report
/reports
/reportSet
/reportSets
{code}
Check for whitespace on fixVersionIds and statusIds
---
Key: MCHANGES-307
URL: https://jira.codehaus.org/browse/MCHANGES-307
Project: Maven Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.9
Reporter: Tobias Rübner
Attachments: MCHANGES-307.patch
On the configuration of the maven changes plugin for the jira-report there
are some configuration parameters that do not like whitespace.
I think this will include component, fixVersionIds, statusIds, resolutionIds,
typeIds and priorityIds.
The report generation will fail with the follwing error:
{code}
org.apache.maven.plugin.MojoFailureException: Could not find status Closed.
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:268)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:249)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:214)
at
org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:129)
at
org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:367)
...
{code}
Note the leading whitespace that came through the definition in the pom file.
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
configuration
useJqltrue/useJql
jiraUser${jira.user}/jiraUser
jiraPassword${jira.password}/jiraPassword
onlyCurrentVersiontrue/onlyCurrentVersion
resolutionIdsFixed/resolutionIds
statusIdsResolved, Closed/statusIds
/configuration
reportSets
reportSet
reports
reportjira-report/report
/reports
/reportSet
/reportSets
/plugin
{code}
I possible solution could be to trim the whitespace.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-324) plugin logs into jira, but doesn't seem to make the status request with the session?
[
https://jira.codehaus.org/browse/MCHANGES-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340434#comment-340434
]
Anthony Whitford commented on MCHANGES-324:
---
This is what I am running into too, and I get the following stack trace:
{noformat}
[INFO] Generating JIRA Report report--- maven-changes-plugin:2.9
[WARNING]
org.apache.maven.plugin.MojoFailureException: Could not find status Closed.
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:259)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:240)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:206)
at
org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:128)
at
org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:367)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
{noformat}
Can this please be placed on the 2.10 Road Map?
plugin logs into jira, but doesn't seem to make the status request with the
session?
Key: MCHANGES-324
URL: https://jira.codehaus.org/browse/MCHANGES-324
Project: Maven Changes Plugin
Issue Type: Bug
Reporter: Antony Stubbs
After successful login, I end up with:
{code}
Nov 11, 2013 5:47:19 PM org.apache.cxf.interceptor.LoggingOutInterceptor
INFO: Outbound Message
---
ID: 3
Address: https://x/rest/api/2/status
Http-Method: GET
Content-Type: application/json
Headers: {Accept=[application/json], Content-Type=[application/json]}
--
Nov 11, 2013 5:47:19 PM org.apache.cxf.interceptor.LoggingInInterceptor
INFO: Inbound Message
ID: 3
Response-Code: 200
Encoding: UTF-8
Content-Type: application/json;charset=UTF-8
Headers: {Cache-Control=[no-cache, no-store, no-transform],
connection=[keep-alive], Content-Length=[2],
content-type=[application/json;charset=UTF-8], Date=[Mon, 11 Nov 2013
22:47:30 GMT], Server=[nginx],
Set-Cookie=[atlassian.xsrf.token=B14E-GL73-6FKZ-OP3B|dd19dbabf6f82c59be235929d3f1ee8d9e41fa4a|lout;
Path=/], Strict-Transport-Security=[max-age=31536;includeSubdomains],
Vary=[Accept-Encoding], X-AREQUESTID=[1067x34467x1], X-ASEN=[SEN-2356824],
X-AUSERNAME=[anonymous]}
Payload: []
{code}
Which returns nothing as you can see. I think that may be because it has
X-AUSERNAME=[anonymous] ? Instead of using the session it created...
After logging into jira in chrome, pasting the just the rest url into the
browser returns all the different status (works as I'd expect).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-307) Check for whitespace on fixVersionIds and statusIds
[
https://jira.codehaus.org/browse/MCHANGES-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Whitford updated MCHANGES-307:
--
Comment: was deleted
(was: I might be getting this issue too with Jira 6.1.5:
{noformat}
[INFO] Generating JIRA Report report--- maven-changes-plugin:2.9
[WARNING]
org.apache.maven.plugin.MojoFailureException: Could not find status Resolved.
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:259)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:240)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:206)
at
org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:128)
at
org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:367)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
{noformat}
Note that I don't see the extra space being an issue... My pom configuration
looks like:
{code:xml}
configuration
jiraUserXXX/jiraUser
jiraPassword/jiraPassword
maxEntries500/maxEntries
onlyCurrentVersiontrue/onlyCurrentVersion
statusIdsResolved,Closed/statusIds
useJqltrue/useJql
/configuration
reportSets
reportSet
reports
reportjira-report/report
/reports
/reportSet
/reportSets
{code}
)
Check for whitespace on fixVersionIds and statusIds
---
Key: MCHANGES-307
URL: https://jira.codehaus.org/browse/MCHANGES-307
Project: Maven Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.9
Reporter: Tobias Rübner
Attachments: MCHANGES-307.patch
On the configuration of the maven changes plugin for the jira-report there
are some configuration parameters that do not like whitespace.
I think this will include component, fixVersionIds, statusIds, resolutionIds,
typeIds and priorityIds.
The report generation will fail with the follwing error:
{code}
org.apache.maven.plugin.MojoFailureException: Could not find status Closed.
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:268)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:249)
at
org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:214)
at
org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:129)
at
org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:367)
...
{code}
Note the leading whitespace that came through the definition in the pom file.
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
configuration
useJqltrue/useJql
jiraUser${jira.user}/jiraUser
jiraPassword${jira.password}/jiraPassword
onlyCurrentVersiontrue/onlyCurrentVersion
resolutionIdsFixed/resolutionIds
statusIdsResolved, Closed/statusIds
/configuration
reportSets
reportSet
reports
reportjira-report/report
/reports
/reportSet
/reportSets
/plugin
{code}
I possible solution could be to trim the whitespace.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSCMPUB-4) Need a working example for GitHub/gh-pages, preferably naturally linked to natural site lifecycle, and multi-module
[
https://jira.codehaus.org/browse/MSCMPUB-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340437#comment-340437
]
Robert Scholte commented on MSCMPUB-4:
--
I did a small adjustment in [r1562963|http://svn.apache.org/r1562963], which is
the only place (other than by plexus DI) where the scmUrl is set. Not sure if
this fixes the issue, please give it another try.
Need a working example for GitHub/gh-pages, preferably naturally linked to
natural site lifecycle, and multi-module
---
Key: MSCMPUB-4
URL: https://jira.codehaus.org/browse/MSCMPUB-4
Project: maven-scm-publish-plugin
Issue Type: Story
Environment: Mac OSX 10.8.2, Java 1.6 Update 35, Maven 3.0.4, Maven
Site Plugin 3.2, Maven SCM Plugin 1.8, Git
Reporter: Anthony Whitford
Priority: Critical
I am trying to update my
[lombok-maven-plugin|http://awhitford.github.com/lombok.maven/lombok-maven-plugin/index.html]
project to use this plugin to publish the project to _Github Pages_.
When I try this command:
{noformat}
mvn clean site site:stage-deploy scm-publish:publish-scm
{noformat}
which is outlined
[here|http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/multi-module-configuration.html],
I get this error:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:1.0-beta-1:publish-scm
(default-cli) on project lombok-maven: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-log command failed.
[ERROR] Command output:
[ERROR] fatal: ambiguous argument 'master': unknown revision or path not in
the working tree.
[ERROR] Use '--' to separate paths from revisions
{noformat}
(?) Is there a multi-module project in GitHub that uses this plugin that I
can use as an example?
This is what I did so far...
{code:xml}
properties
siteMainDirectory${user.home}/Sites/lombok.maven/siteMainDirectory
scmPubCheckoutDirectory${user.home}/site-content-scm/lombok.maven/scmPubCheckoutDirectory
/properties
...
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version3.2/version
configuration
skipDeploytrue/skipDeploy
stagingSiteURLfile://${siteMainDirectory}/stagingSiteURL
/configuration
/plugin
...
/plugins
/pluginManagement
...
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
executions
execution
idstage-for-scm-publish/id
phasepost-site/phase
goals
goalstage/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-publish-plugin/artifactId
version1.0-beta-1/version
configuration
checkoutDirectory${scmPubCheckoutDirectory}/checkoutDirectory
content\${siteMainDirectory}/content
tryUpdatetrue/tryUpdate
scmBranchgh-pages/scmBranch
pubScmUrlscm:git:g...@github.com:awhitford/lombok.maven.git/pubScmUrl
/configuration
executions
execution
idscm-publish/id
phasesite-deploy/phase
goals
goalpublish-scm/goal
/goals
/execution
/executions
/plugin
/plugins
{code}
Finally, I'm really interested in wiring this up so that when I do a normal
{{site-deploy}} or an implicit one through the release process, it gets
published to {{gh-pages}} -- just like I had working with
[wagon-gitsite|https://github.com/awhitford/wagon-gitsite].
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-208) The plugin generates reports incompatible with the 'maven-jxr-plugin' version 2.4.
Christian Schulte created MCHECKSTYLE-208: - Summary: The plugin generates reports incompatible with the 'maven-jxr-plugin' version 2.4. Key: MCHECKSTYLE-208 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-208 Project: Maven Checkstyle Plugin Issue Type: Bug Reporter: Christian Schulte -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-179) The plugin generates reports incompatible with the 'maven-jxr-plugin' version 2.4.
Christian Schulte created MPMD-179: -- Summary: The plugin generates reports incompatible with the 'maven-jxr-plugin' version 2.4. Key: MPMD-179 URL: https://jira.codehaus.org/browse/MPMD-179 Project: Maven PMD Plugin Issue Type: Bug Reporter: Christian Schulte -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSCMPUB-4) Need a working example for GitHub/gh-pages, preferably naturally linked to natural site lifecycle, and multi-module
[
https://jira.codehaus.org/browse/MSCMPUB-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340442#comment-340442
]
Anthony Whitford commented on MSCMPUB-4:
Awesome! It looks like it worked:
[lombok.maven|http://awhitford.github.io/lombok.maven/]
Need a working example for GitHub/gh-pages, preferably naturally linked to
natural site lifecycle, and multi-module
---
Key: MSCMPUB-4
URL: https://jira.codehaus.org/browse/MSCMPUB-4
Project: maven-scm-publish-plugin
Issue Type: Story
Environment: Mac OSX 10.8.2, Java 1.6 Update 35, Maven 3.0.4, Maven
Site Plugin 3.2, Maven SCM Plugin 1.8, Git
Reporter: Anthony Whitford
Priority: Critical
I am trying to update my
[lombok-maven-plugin|http://awhitford.github.com/lombok.maven/lombok-maven-plugin/index.html]
project to use this plugin to publish the project to _Github Pages_.
When I try this command:
{noformat}
mvn clean site site:stage-deploy scm-publish:publish-scm
{noformat}
which is outlined
[here|http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/multi-module-configuration.html],
I get this error:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:1.0-beta-1:publish-scm
(default-cli) on project lombok-maven: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-log command failed.
[ERROR] Command output:
[ERROR] fatal: ambiguous argument 'master': unknown revision or path not in
the working tree.
[ERROR] Use '--' to separate paths from revisions
{noformat}
(?) Is there a multi-module project in GitHub that uses this plugin that I
can use as an example?
This is what I did so far...
{code:xml}
properties
siteMainDirectory${user.home}/Sites/lombok.maven/siteMainDirectory
scmPubCheckoutDirectory${user.home}/site-content-scm/lombok.maven/scmPubCheckoutDirectory
/properties
...
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version3.2/version
configuration
skipDeploytrue/skipDeploy
stagingSiteURLfile://${siteMainDirectory}/stagingSiteURL
/configuration
/plugin
...
/plugins
/pluginManagement
...
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
executions
execution
idstage-for-scm-publish/id
phasepost-site/phase
goals
goalstage/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-publish-plugin/artifactId
version1.0-beta-1/version
configuration
checkoutDirectory${scmPubCheckoutDirectory}/checkoutDirectory
content\${siteMainDirectory}/content
tryUpdatetrue/tryUpdate
scmBranchgh-pages/scmBranch
pubScmUrlscm:git:g...@github.com:awhitford/lombok.maven.git/pubScmUrl
/configuration
executions
execution
idscm-publish/id
phasesite-deploy/phase
goals
goalpublish-scm/goal
/goals
/execution
/executions
/plugin
/plugins
{code}
Finally, I'm really interested in wiring this up so that when I do a normal
{{site-deploy}} or an implicit one through the release process, it gets
published to {{gh-pages}} -- just like I had working with
[wagon-gitsite|https://github.com/awhitford/wagon-gitsite].
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSCMPUB-4) Need a working example for GitHub/gh-pages, preferably naturally linked to natural site lifecycle, and multi-module
[
https://jira.codehaus.org/browse/MSCMPUB-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MSCMPUB-4.
---
Resolution: Fixed
Fix Version/s: 1.0
great!
thank you for your tests that helped us detect a stupid little bug :)
I'll do the 1.0 release shortly: stay tuned!
Need a working example for GitHub/gh-pages, preferably naturally linked to
natural site lifecycle, and multi-module
---
Key: MSCMPUB-4
URL: https://jira.codehaus.org/browse/MSCMPUB-4
Project: maven-scm-publish-plugin
Issue Type: Story
Environment: Mac OSX 10.8.2, Java 1.6 Update 35, Maven 3.0.4, Maven
Site Plugin 3.2, Maven SCM Plugin 1.8, Git
Reporter: Anthony Whitford
Priority: Critical
Fix For: 1.0
I am trying to update my
[lombok-maven-plugin|http://awhitford.github.com/lombok.maven/lombok-maven-plugin/index.html]
project to use this plugin to publish the project to _Github Pages_.
When I try this command:
{noformat}
mvn clean site site:stage-deploy scm-publish:publish-scm
{noformat}
which is outlined
[here|http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/multi-module-configuration.html],
I get this error:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:1.0-beta-1:publish-scm
(default-cli) on project lombok-maven: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-log command failed.
[ERROR] Command output:
[ERROR] fatal: ambiguous argument 'master': unknown revision or path not in
the working tree.
[ERROR] Use '--' to separate paths from revisions
{noformat}
(?) Is there a multi-module project in GitHub that uses this plugin that I
can use as an example?
This is what I did so far...
{code:xml}
properties
siteMainDirectory${user.home}/Sites/lombok.maven/siteMainDirectory
scmPubCheckoutDirectory${user.home}/site-content-scm/lombok.maven/scmPubCheckoutDirectory
/properties
...
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version3.2/version
configuration
skipDeploytrue/skipDeploy
stagingSiteURLfile://${siteMainDirectory}/stagingSiteURL
/configuration
/plugin
...
/plugins
/pluginManagement
...
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
executions
execution
idstage-for-scm-publish/id
phasepost-site/phase
goals
goalstage/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-publish-plugin/artifactId
version1.0-beta-1/version
configuration
checkoutDirectory${scmPubCheckoutDirectory}/checkoutDirectory
content\${siteMainDirectory}/content
tryUpdatetrue/tryUpdate
scmBranchgh-pages/scmBranch
pubScmUrlscm:git:g...@github.com:awhitford/lombok.maven.git/pubScmUrl
/configuration
executions
execution
idscm-publish/id
phasesite-deploy/phase
goals
goalpublish-scm/goal
/goals
/execution
/executions
/plugin
/plugins
{code}
Finally, I'm really interested in wiring this up so that when I do a normal
{{site-deploy}} or an implicit one through the release process, it gets
published to {{gh-pages}} -- just like I had working with
[wagon-gitsite|https://github.com/awhitford/wagon-gitsite].
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
