[jira] Issue Comment Edited: (MCHANGES-126) NullPointerException when executing jira-report with JIRA 3.13
[
http://jira.codehaus.org/browse/MCHANGES-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150367#action_150367
]
lonfic edited comment on MCHANGES-126 at 10/9/08 6:32 AM:
to fix the problem simply ignore the version number when the parent is not item
in the class
org\apache\maven\plugin\jira\JiraXML
...
else if ( qName.equals( "version" ) && currentParent.equals( "item" ))
{
issue.setVersion( currentElement.toString().trim() );
}
...
instead of
else if ( qName.equals( "version" ) )
{
issue.setVersion( currentElement.toString().trim() );
}
...
was (Author: lonfic):
to fix the problem simply ignore the version number when the parent is not
item
...
else if ( qName.equals( "version" ) && currentParent.equals( "item" ))
{
issue.setVersion( currentElement.toString().trim() );
}
...
instead of
else if ( qName.equals( "version" ) )
{
issue.setVersion( currentElement.toString().trim() );
}
...
> NullPointerException when executing jira-report with JIRA 3.13
> --
>
> Key: MCHANGES-126
> URL: http://jira.codehaus.org/browse/MCHANGES-126
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira-report
>Affects Versions: 2.0
>Reporter: Régis DUTERTRE
>Priority: Blocker
>
> I have installed the {color:red}*new JIRA 3.13*{color} and I cannot generate
> the jira-report
> See stacktrace below:
> {quote}
> java.lang.NullPointerException
> at org.apache.maven.plugin.jira.JiraXML.endElement(JiraXML.java:131)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1241)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:311)
> at org.apache.maven.plugin.jira.JiraXML.(JiraXML.java:65)
> at
> org.apache.maven.plugin.jira.JiraReportGenerator.(JiraReportGenerator.java:94)
> at
> org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:251)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-37) eclipse:eclipse should execute in a later phase than "generate-sources"
[ http://jira.codehaus.org/browse/MECLIPSE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin LERMAN updated MECLIPSE-37: Attachment: patch-eclipse-eclipse the attached patch set the lifecycle of the plugin to initialize, generate-sources, generate-resources, generate-test-sources, generate-test-resources > eclipse:eclipse should execute in a later phase than "generate-sources" > --- > > Key: MECLIPSE-37 > URL: http://jira.codehaus.org/browse/MECLIPSE-37 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path >Affects Versions: 2.0 >Reporter: Mark Donszelmann >Assignee: Arnaud Heritier > Fix For: 2.6 > > Attachments: patch-eclipse-eclipse > > > the eclipse:eclipse goal should run in a later phase than it currently does > (generate-sources) > as user defined plugins may add to the compileSourceRoots and > testCompileSourceRoots. > If it runs later, added paths will be written correctly to the .classpath. > Suggested phase is "test" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-126) NullPointerException when executing jira-report with JIRA 3.13
[
http://jira.codehaus.org/browse/MCHANGES-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150367#action_150367
]
Corentin Lonfils commented on MCHANGES-126:
---
to fix the problem simply ignore the version number when the parent is not item
...
else if ( qName.equals( "version" ) && currentParent.equals( "item" ))
{
issue.setVersion( currentElement.toString().trim() );
}
...
instead of
else if ( qName.equals( "version" ) )
{
issue.setVersion( currentElement.toString().trim() );
}
...
> NullPointerException when executing jira-report with JIRA 3.13
> --
>
> Key: MCHANGES-126
> URL: http://jira.codehaus.org/browse/MCHANGES-126
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira-report
>Affects Versions: 2.0
>Reporter: Régis DUTERTRE
>Priority: Blocker
>
> I have installed the {color:red}*new JIRA 3.13*{color} and I cannot generate
> the jira-report
> See stacktrace below:
> {quote}
> java.lang.NullPointerException
> at org.apache.maven.plugin.jira.JiraXML.endElement(JiraXML.java:131)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1241)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:311)
> at org.apache.maven.plugin.jira.JiraXML.(JiraXML.java:65)
> at
> org.apache.maven.plugin.jira.JiraReportGenerator.(JiraReportGenerator.java:94)
> at
> org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:251)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-123) Create an xdoc DTD or XSD for maven 2
[ http://jira.codehaus.org/browse/DOXIA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed DOXIA-123. - Assignee: Vincent Siveton Resolution: Fixed I added xsd files in [r703144|http://svn.apache.org/viewvc?rev=703144&view=rev] > Create an xdoc DTD or XSD for maven 2 > - > > Key: DOXIA-123 > URL: http://jira.codehaus.org/browse/DOXIA-123 > Project: Maven Doxia > Issue Type: Task > Components: Module - Xdoc >Reporter: Lukas Theussl >Assignee: Vincent Siveton > Fix For: 1.0-beta-1 > > > In Maven 1, a valid xdoc was defined to be something that was converted into > a valid xhtml document by the m1 xdoc plugin. I guess in m2 the same > procedure should be applied to doxia. We need to identify the features that > 1) should be added 2) should be removed with respect to the m1 xdoc dtd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-347) Site plugin install the wrong site.xml descriptor in local repository since 2.0-beta-6
[ http://jira.codehaus.org/browse/MSITE-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150365#action_150365 ] Lammert Westerhoff commented on MSITE-347: -- I had exactly the same problem but this issue seems to be fixed in 2.0-beta-7. At least for me, using 2.0-beta-7 solved the problem. > Site plugin install the wrong site.xml descriptor in local repository since > 2.0-beta-6 > -- > > Key: MSITE-347 > URL: http://jira.codehaus.org/browse/MSITE-347 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Affects Versions: 2.0-beta-6, 2.0-beta-7 >Reporter: Stefano Bagnara > Attachments: site-plugin-test.zip > > > I just tryed to build an old project and I found that it was no more working. > After investigating this I see that now maven ends up installing a wrong > site.xml (the one from the parent) instead of the right one. > I attach a simple multimodule project to reproduce this issue. > If you run an "mvn install site" from the root you see that in the > com.example/project/1.0-SNAPSHOT folder the project-1.0-SNAPSHOT-site.xml is > instead the site.xml for the "parent" artifact and not the one that I have in > the "project" artifact. > This seems a critical issue. > Try uncommenting the pluginManagement where I declare site 2.0-beta-5 and > everything will work fine! > I don't know how to setup the environment to be able to create an it test to > submit to the site plugin developers, hope the test is good enough. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-606) New version of Prefuse to upload - beta-20071021
New version of Prefuse to upload - beta-20071021 - Key: MEV-606 URL: http://jira.codehaus.org/browse/MEV-606 Project: Maven Evangelism Issue Type: Wish Reporter: Paul Hammant Following on from http://jira.codehaus.org/browse/MEV-523 , the is a newer version of Prefuse for the repo : http://sourceforge.net/project/showfiles.php?group_id=98962&package_id=106038&release_id=548630 The zip there contains the project ready to build. 'ant all' makes a jar and a source jar. 'ant api' makes Javadoc in doc/ Java 1.4 is the minimum level for Prefuse, so watch out when building. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-606) New version of Prefuse to upload - beta-20071021
[ http://jira.codehaus.org/browse/MEV-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150390#action_150390 ] Benjamin Bentmann commented on MEV-606: --- Upload requests are usually filled under [MAVENUPLOAD|http://jira.codehaus.org/browse/MAVENUPLOAD], following the [Guide to uploading artifacts to the Central Repository|http://maven.apache.org/guides/mini/guide-central-repository-upload.html]. > New version of Prefuse to upload - beta-20071021 > - > > Key: MEV-606 > URL: http://jira.codehaus.org/browse/MEV-606 > Project: Maven Evangelism > Issue Type: Wish >Reporter: Paul Hammant > > Following on from http://jira.codehaus.org/browse/MEV-523 , the is a newer > version of Prefuse for the repo : > http://sourceforge.net/project/showfiles.php?group_id=98962&package_id=106038&release_id=548630 > The zip there contains the project ready to build. >'ant all' makes a jar and a source jar. >'ant api' makes Javadoc in doc/ > Java 1.4 is the minimum level for Prefuse, so watch out when building. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect dependency classpath
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150394#action_150394 ] Rodolfo Rothganger commented on MJAVADOC-214: - I´ve got a similar problems regarding annotations not found by the plugin. In my project there is a parent POM declaring FindBugs annotations as "compile" scoped dependencies. While tring to deploy an artifact with the above POM as parent produced the following error: " a "java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc at com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46) at com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811) " To work around the problem I´ve declared the compile scoped annotations as dependencies of the plugin itself. > test javadoc goal uses incorrect dependency classpath > - > > Key: MJAVADOC-214 > URL: http://jira.codehaus.org/browse/MJAVADOC-214 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Brett Porter > > according to this report: > http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19158787.html > The test javadoc goal is not using the test classpath dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
How do I add an extra source directory to the Maven JXR Plugin
How do I add an extra source directory to the Maven JXR Plugin? I'm using the build-helper-maven-plugin to add it to my build, but I'd like to see the XREF source for this extra source directory as well. Thanks, Scott
[jira] Commented: (MAVENUPLOAD-2050) Upload Google Collections Library snapshots to central Maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150404#action_150404 ] Jared Levy commented on MAVENUPLOAD-2050: - The sync to the central repository is now working. http://repo1.maven.org/maven-google/com/google/collections/google-collections/0.8/ > Upload Google Collections Library snapshots to central Maven repository > --- > > Key: MAVENUPLOAD-2050 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2050 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jared Levy >Assignee: Carlos Sanchez > > Please upload these two bundles of the Google Collections Library to the > central repository. > http://google-collections.googlecode.com/files/google-collect-snapshot-20071022-bundle.jar > http://google-collections.googlecode.com/files/google-collect-snapshot-20080321-bundle.jar > Though the "snapshot" version is non-standard, it's consistent with our > releases in > http://code.google.com/p/google-collections/downloads/list?can=1&q=&colspec=Filename+Summary+Uploaded+Size+DownloadCount > There's been a lot of interest in this, as you can see at > http://code.google.com/p/google-collections/issues/detail?id=24 > Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3785) Allow properties parameter to be a properties file
Allow properties parameter to be a properties file
--
Key: MNG-3785
URL: http://jira.codehaus.org/browse/MNG-3785
Project: Maven 2
Issue Type: Improvement
Reporter: Marvin Froeder
Priority: Minor
Right now, when I have a properties parameter:
/**
* My Properties.
*
* @parameter
*/
private Properties myProperties;
I configure it like this:
propertyName1
propertyValue1
propertyName2
propertyValue2
Would be cool it I can use a file instead of describing all properties:
${basedir}/myconfigs.properties
VELO
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3786) Aborting build truncates repository.xml
Aborting build truncates repository.xml --- Key: MNG-3786 URL: http://jira.codehaus.org/browse/MNG-3786 Project: Maven 2 Issue Type: Bug Components: Command Line Environment: Maven version: 2.0.8 Java version: 1.6.0_06 OS name: "linux" version: "2.6.24-19-generic" arch: "amd64" Family: "unix" Reporter: Parker Abercrombie I aborted a build with Ctrl-C. When I tried to build again I got an error about a premature end of file on ~/.m2/repository.xml. Sure enough, the file had been truncated to a single line: Deleting the file and rebuilding solved the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-342) scm:tag should support flat project layout
[ http://jira.codehaus.org/browse/SCM-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150421#action_150421 ] Duncan Doyle commented on SCM-342: -- Vincent, why are you not comfortable to remove the @aggregator? The current tagging functionality basically doesn't work with any flat project layout. The patch supplied has been in production at our company for over a year without any issues. I would really like to see this issue closed one way or the other, it has been open for over a year now. > scm:tag should support flat project layout > -- > > Key: SCM-342 > URL: http://jira.codehaus.org/browse/SCM-342 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin >Affects Versions: 1.0 > Environment: Windows XP, Eclipse 3.3 >Reporter: Duncan Doyle > Attachments: flatProjectTagPatch.txt > > > I have a Maven2 Flat Project Layout as described here: > http://maven.apache.org/guides/mini/guide-ide-eclipse.html > Basically my directory layout is as follows: > /MavenRoot/pom.xml (this is the SuperPom) > /Module1/pom.xml > /Module2/pom.xml > /Module3/pom.xml > Modules 1,2 and 3 are specified in the section of the SuperPom > (e.g() ../Module1). Each POM contains its own CVS connection > URL. > When I execute the scm:tag goal on the SuperPom in the MavenRoot project, > only the MavenRoot project gets tagged. The same behaviour can be seen with > the scm:update goal, which was fixed by providing a scm:update-subprojects > goal. > I would like to see this behaviour fixed in the SCM plugin, while Maven2 > advices a Flat Project Layout when working with Eclipse. At this moment I > can't use the tag goal at all (it should be executed automatically by > CruiseControl on a succesfull build). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-319) Make eclipse:rad work with manifests without "Class-Path:"-entries
[ http://jira.codehaus.org/browse/MECLIPSE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150426#action_150426 ] Rich Dougherty commented on MECLIPSE-319: - I've come across this problem too - and actually made a near-identical patch. It would be great to get Mikko Koponen's patch into the next version. > Make eclipse:rad work with manifests without "Class-Path:"-entries > -- > > Key: MECLIPSE-319 > URL: http://jira.codehaus.org/browse/MECLIPSE-319 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: RAD support >Affects Versions: 2.4 >Reporter: Mikko Koponen >Priority: Minor > Attachments: manifest-classpath-null-check.patch, > rad-manifest-problem-log.txt > > > So... We have a project with somewhat bad manifest files, and we'd like to > use the rad goal. > The plugin fails for existing manifests that don't have Class-Path entries, > attached is an error log. > The - also attached - patch fixes this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
