[jira] (MCHANGES-325) RestJiraDownloader doesn't process issueType
[ https://jira.codehaus.org/browse/MCHANGES-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated MCHANGES-325: Comment: was deleted (was: Patch that fixes this issue) > RestJiraDownloader doesn't process issueType > > > Key: MCHANGES-325 > URL: https://jira.codehaus.org/browse/MCHANGES-325 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.9 >Reporter: Marshall Schor > Attachments: patch-without-debug-msgs.txt > > > The RestJiraDownloader receives as one of the many fields, the issuetype, but > ignores it. So, although the docs suggest you can have the "Type" field as a > display option, and a sort option (see: > http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html > scroll to selecting columns), this in fact fails for 2.9 version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-325) RestJiraDownloader doesn't process issueType
[ https://jira.codehaus.org/browse/MCHANGES-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated MCHANGES-325: Attachment: patch-without-debug-msgs.txt Reattaching patch without debug messages > RestJiraDownloader doesn't process issueType > > > Key: MCHANGES-325 > URL: https://jira.codehaus.org/browse/MCHANGES-325 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.9 >Reporter: Marshall Schor > Attachments: patch-without-debug-msgs.txt > > > The RestJiraDownloader receives as one of the many fields, the issuetype, but > ignores it. So, although the docs suggest you can have the "Type" field as a > display option, and a sort option (see: > http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html > scroll to selecting columns), this in fact fails for 2.9 version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-325) RestJiraDownloader doesn't process issueType
[ https://jira.codehaus.org/browse/MCHANGES-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated MCHANGES-325: Attachment: (was: patch.txt) > RestJiraDownloader doesn't process issueType > > > Key: MCHANGES-325 > URL: https://jira.codehaus.org/browse/MCHANGES-325 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.9 >Reporter: Marshall Schor > > The RestJiraDownloader receives as one of the many fields, the issuetype, but > ignores it. So, although the docs suggest you can have the "Type" field as a > display option, and a sort option (see: > http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html > scroll to selecting columns), this in fact fails for 2.9 version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-325) RestJiraDownloader doesn't process issueType
[ https://jira.codehaus.org/browse/MCHANGES-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated MCHANGES-325: Attachment: patch.txt Patch that fixes this issue > RestJiraDownloader doesn't process issueType > > > Key: MCHANGES-325 > URL: https://jira.codehaus.org/browse/MCHANGES-325 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.9 >Reporter: Marshall Schor > Attachments: patch.txt > > > The RestJiraDownloader receives as one of the many fields, the issuetype, but > ignores it. So, although the docs suggest you can have the "Type" field as a > display option, and a sort option (see: > http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html > scroll to selecting columns), this in fact fails for 2.9 version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-691) Aggregator pom with child parent not handled
[
https://jira.codehaus.org/browse/MSITE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337882#comment-337882
]
Ivan C edited comment on MSITE-691 at 12/27/13 4:19 PM:
I am having exactly the same issue with a somewhat similar setup: aggregator
does not extend the parent, and the parent and children directories are at the
level of the aggregator pom, no extra layer in between.
I would like to see a good example of how to setup site generation with this
type of project layout or something similar.
was (Author: osobrujo):
I am having exactly the same issue with a somewhat similar setup:
aggregator does not extend the parent, but layout is the same.
I would like to see a good example of how to setup site generation with this
type of project layout.
> Aggregator pom with child parent not handled
>
>
> Key: MSITE-691
> URL: https://jira.codehaus.org/browse/MSITE-691
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 3.3
>Reporter: Stephen Colebourne
> Attachments: OG-Platform.zip
>
>
> The attached zip demonstrates a project where the parent is an aggregator
> only pom and the children include the parent:
> {code}
> platform
> - pom.xml (aggregator only)
> - projects
> - parent
> - pom.xml (parent for the child project)
> - child
> - pom.xml
> {code}
> Running the zip file with "mvn clean test site" will build incorrect
> hyperlinks.
> The top left hyperlinks, added by the site plugin, are defined as
> "parent/index.html" and "child/child/index.html". I consider the former to be
> correct, but not the latter.
> In addition, the navigation links produce both a link to the parent (under
> the "Parent Project" heading), and a second link to the parent under the
> "Modules" heading. This seems unnecessary, and in fact does not work in
> design terms, see below. (It appears that separate aggregator and parent pom
> projects are not really supported in design terms)
> The child projects also contain the wrong link to the parent (under "Parent
> Projects" in the navigation area). They create a link as
> "../../parent/index.html". This will be one ".." too far, as the
> "distributionManagement.site.url" definition removes the extra level.
> Finally, the site of the parent pom does not contain a "Parent projects" link
> in the navigation area. That would make sense if there was no aggregator
> project, but does not make sense here from a website pint of view.
> What I would expect is the following staged website:
> {code}
> target
> - staging
> - index.html (links to child projects, including parent)
> - parent
> - index.html (link back to aggregator)
> - child
> - index.html (link back to aggregator, link to parent:
> "../parent/index.html")
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-691) Aggregator pom with child parent not handled
[
https://jira.codehaus.org/browse/MSITE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337882#comment-337882
]
Ivan C commented on MSITE-691:
--
I am having exactly the same issue with a somewhat similar setup: aggregator
does not extend the parent, but layout is the same.
I would like to see a good example of how to setup site generation with this
type of project layout.
> Aggregator pom with child parent not handled
>
>
> Key: MSITE-691
> URL: https://jira.codehaus.org/browse/MSITE-691
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 3.3
>Reporter: Stephen Colebourne
> Attachments: OG-Platform.zip
>
>
> The attached zip demonstrates a project where the parent is an aggregator
> only pom and the children include the parent:
> {code}
> platform
> - pom.xml (aggregator only)
> - projects
> - parent
> - pom.xml (parent for the child project)
> - child
> - pom.xml
> {code}
> Running the zip file with "mvn clean test site" will build incorrect
> hyperlinks.
> The top left hyperlinks, added by the site plugin, are defined as
> "parent/index.html" and "child/child/index.html". I consider the former to be
> correct, but not the latter.
> In addition, the navigation links produce both a link to the parent (under
> the "Parent Project" heading), and a second link to the parent under the
> "Modules" heading. This seems unnecessary, and in fact does not work in
> design terms, see below. (It appears that separate aggregator and parent pom
> projects are not really supported in design terms)
> The child projects also contain the wrong link to the parent (under "Parent
> Projects" in the navigation area). They create a link as
> "../../parent/index.html". This will be one ".." too far, as the
> "distributionManagement.site.url" definition removes the extra level.
> Finally, the site of the parent pom does not contain a "Parent projects" link
> in the navigation area. That would make sense if there was no aggregator
> project, but does not make sense here from a website pint of view.
> What I would expect is the following staged website:
> {code}
> target
> - staging
> - index.html (links to child projects, including parent)
> - parent
> - index.html (link back to aggregator)
> - child
> - index.html (link back to aggregator, link to parent:
> "../parent/index.html")
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-325) RestJiraDownloader doesn't process issueType
Marshall Schor created MCHANGES-325: --- Summary: RestJiraDownloader doesn't process issueType Key: MCHANGES-325 URL: https://jira.codehaus.org/browse/MCHANGES-325 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.9 Reporter: Marshall Schor The RestJiraDownloader receives as one of the many fields, the issuetype, but ignores it. So, although the docs suggest you can have the "Type" field as a display option, and a sort option (see: http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html scroll to selecting columns), this in fact fails for 2.9 version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-658) Assembly fails for multi-module project if webstart-maven-plugin is in use
[ https://jira.codehaus.org/browse/MASSEMBLY-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MASSEMBLY-658. - Resolution: Won't Fix Fix Version/s: 2.5 Assignee: Tony Chemit You are just using the *jnlp-inline* mojo which is an aggregator mojo, so does not match with your needs. Just use instead the *jnlp-single* mojo instead to make your example works. > Assembly fails for multi-module project if webstart-maven-plugin is in use > -- > > Key: MASSEMBLY-658 > URL: https://jira.codehaus.org/browse/MASSEMBLY-658 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: dependencySet >Affects Versions: 2.4 > Environment: Apache Maven 3.0.5 > (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 13:51: > 28+) > Maven home: C:\dev\apache-maven-3.0.5\bin\.. > Java version: 1.6.0_45, vendor: Sun Microsystems Inc. > Java home: C:\Program Files\Java\jdk1.6.0_45\jre > Default locale: en_GB, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" >Reporter: Robin Roos >Assignee: Tony Chemit > Fix For: 2.5 > > Attachments: npe-war-assebmbly.zip, output.log > > > The mvn invocation I used is: > mvn clean package > I attach a simple test case of a multi-module project. If the acme-jnlp > module is commented out in the parent POM then the project builds > successfully. If the acme-jnlp module is not commented out, then the assembly > of acme-dist fails because of a NullPointerException. > acme-dist and acme-war to not rely on the artifacts generated by acme-jnlp. > The mere fact that the plugin is executed causes the later module assembly to > fail. > Modules have the following purposes: > acme-parent: parent project which contains the module > acme-jnlp: create JNLP and ZIP files not used by any other modules > acme-war: create a .WAR file > acme-dist: use assembly plugin to create a .ZIP containing the .WAR > acme-deploy: holds dependencies to other modules, but does nothing else -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
