[jira] Created: (MINVOKER-91) Decouple test execution from build failure
Decouple test execution from build failure -- Key: MINVOKER-91 URL: http://jira.codehaus.org/browse/MINVOKER-91 Project: Maven 2.x Invoker Plugin Issue Type: New Feature Affects Versions: 1.4 Reporter: Stephen Connolly Priority: Minor Attachments: integration-test-verify.patch If you are using invoker-based tests as well as other integration test frameworks (e.g. failsafe-maven-plugin), and you have an integration test environment that needs to be torn down properly, there is currently no way to tear down this test enviroment when invoker-based tests are failing. The attached patch adds two new goals, integration-test and verify, both designed to copy the behaviour of the failsafe-maven-plugin -- 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: (MINVOKER-91) Decouple test execution from build failure
[ http://jira.codehaus.org/browse/MINVOKER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187215#action_187215 ] Stephen Connolly commented on MINVOKER-91: -- Oh, before I forget, the patch includes three integration tests of these new goals > Decouple test execution from build failure > -- > > Key: MINVOKER-91 > URL: http://jira.codehaus.org/browse/MINVOKER-91 > Project: Maven 2.x Invoker Plugin > Issue Type: New Feature >Affects Versions: 1.4 >Reporter: Stephen Connolly >Priority: Minor > Attachments: integration-test-verify.patch > > > If you are using invoker-based tests as well as other integration test > frameworks (e.g. failsafe-maven-plugin), and you have an integration test > environment that needs to be torn down properly, there is currently no way to > tear down this test enviroment when invoker-based tests are failing. > The attached patch adds two new goals, integration-test and verify, both > designed to copy the behaviour of the failsafe-maven-plugin -- 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: (DOXIA-357) NoSuchElementException with a table caption
NoSuchElementException with a table caption
---
Key: DOXIA-357
URL: http://jira.codehaus.org/browse/DOXIA-357
Project: Maven Doxia
Issue Type: Bug
Components: Module - FO
Affects Versions: 1.1.1
Reporter: Vincent Siveton
When parsing a table with a caption like the following
{noformat}
caption table
foo
bar
{noformat}
we could have:
{noformat}
java.util.NoSuchElementException
at java.util.LinkedList.remove(LinkedList.java:644)
at java.util.LinkedList.removeLast(LinkedList.java:144)
at
org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.endElement(PrettyPrintXMLWriter.java:276)
at org.apache.maven.doxia.module.fo.FoSink.writeEndTag(FoSink.java:1702)
at
org.apache.maven.doxia.module.fo.FoAggregateSink.writeEndTag(FoAggregateSink.java:520)
at org.apache.maven.doxia.module.fo.FoSink.tableRows_(FoSink.java:1002)
{noformat}
--
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-357) NoSuchElementException with a table caption
[
http://jira.codehaus.org/browse/DOXIA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed DOXIA-357.
-
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 1.1.2
fixed in [r804450|http://svn.apache.org/viewvc?rev=804450&view=rev], snapshot
deployed
> NoSuchElementException with a table caption
> ---
>
> Key: DOXIA-357
> URL: http://jira.codehaus.org/browse/DOXIA-357
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - FO
>Affects Versions: 1.1.1
>Reporter: Vincent Siveton
>Assignee: Vincent Siveton
> Fix For: 1.1.2
>
>
> When parsing a table with a caption like the following
> {noformat}
>
> caption table
>
> foo
>
>
> bar
>
>
> {noformat}
> we could have:
> {noformat}
> java.util.NoSuchElementException
> at java.util.LinkedList.remove(LinkedList.java:644)
> at java.util.LinkedList.removeLast(LinkedList.java:144)
> at
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.endElement(PrettyPrintXMLWriter.java:276)
> at
> org.apache.maven.doxia.module.fo.FoSink.writeEndTag(FoSink.java:1702)
> at
> org.apache.maven.doxia.module.fo.FoAggregateSink.writeEndTag(FoAggregateSink.java:520)
> at
> org.apache.maven.doxia.module.fo.FoSink.tableRows_(FoSink.java:1002)
> {noformat}
--
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] Issue Comment Edited: (DOXIA-357) NoSuchElementException with a table caption
[
http://jira.codehaus.org/browse/DOXIA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187221#action_187221
]
Vincent Siveton edited comment on DOXIA-357 at 8/15/09 7:20 AM:
fixed in [r804464|http://svn.apache.org/viewvc?rev=804464&view=rev], snapshot
deployed
was (Author: siveton):
fixed in [r804450|http://svn.apache.org/viewvc?rev=804450&view=rev],
snapshot deployed
> NoSuchElementException with a table caption
> ---
>
> Key: DOXIA-357
> URL: http://jira.codehaus.org/browse/DOXIA-357
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - FO
>Affects Versions: 1.1.1
>Reporter: Vincent Siveton
>Assignee: Vincent Siveton
> Fix For: 1.1.2
>
>
> When parsing a table with a caption like the following
> {noformat}
>
> caption table
>
> foo
>
>
> bar
>
>
> {noformat}
> we could have:
> {noformat}
> java.util.NoSuchElementException
> at java.util.LinkedList.remove(LinkedList.java:644)
> at java.util.LinkedList.removeLast(LinkedList.java:144)
> at
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.endElement(PrettyPrintXMLWriter.java:276)
> at
> org.apache.maven.doxia.module.fo.FoSink.writeEndTag(FoSink.java:1702)
> at
> org.apache.maven.doxia.module.fo.FoAggregateSink.writeEndTag(FoAggregateSink.java:520)
> at
> org.apache.maven.doxia.module.fo.FoSink.tableRows_(FoSink.java:1002)
> {noformat}
--
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: (MAVENUPLOAD-2560) Synchronizing the org.jvnet repository to central
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187235#action_187235
]
Kohsuke Kawaguchi commented on MAVENUPLOAD-2560:
OK, I think you are saying that I'm supposed to serve proper maven-metadata.xml
from my rsync (as opposed to just no maven-metadata.xml at all.) I'll do that.
> Synchronizing the org.jvnet repository to central
> -
>
> Key: MAVENUPLOAD-2560
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2560
> Project: Maven Upload Requests
> Issue Type: Wish
>Reporter: Kohsuke Kawaguchi
>Assignee: Brian Fox
>
> The CSV entry for the sync:
> {noformat}
> "org.jvnet","rsync://maven.hudson-ci.org/maven.org.jvnet","rsync","Kohsuke
> Kawaguchi","k...@kohsuke.org",,
> {noformat}
> The proof of the ownership of the domain can be confirmed by verifying that
> jvnet.org belongs to java.net (more specifically Sun Microsystems ---
> http://www.whois.net/whois/jvnet.org). I couldn't find an authoritative
> document saying that this belongs to java.net, but as a java.net community
> leader, I can vouch for that. You can also see a number of existing java.net
> projects that publish in this group ID ( http://maven.dyndns.org/2/org/jvnet/
> )
> I'm requesting this as an administrator of java.net Maven2 repository, and
> you can find my ID (super_kohsuke) in https://maven2-repository.dev.java.net/
> I also wanted to mention that this groupId shadows MAVENUPLOAD-2515. I
> currently set up my rsync daemon not to serve org.jvnet.hudson from
> rsync://maven.hudson-ci.org/maven.org.jvnet , but if it's easier for you
> guys, I'm happy to have "org.jvnet.hudson" sync removed, and sync it through
> this channel instead.
--
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: (DOXIA-358) avoid to store in memory the full generated FO document when only table content is needed
avoid to store in memory the full generated FO document when only table content
is needed
-
Key: DOXIA-358
URL: http://jira.codehaus.org/browse/DOXIA-358
Project: Maven Doxia
Issue Type: Improvement
Components: Module - FO
Affects Versions: 1.1.1
Reporter: Herve Boutemy
this is particularly needed when generating an aggregated document, since it
can become really big.
For example maven site generates a 2.7 MB {{apache-maven.fo}} file
--
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-358) avoid to store in memory the full generated FO document when only table content is needed
[
http://jira.codehaus.org/browse/DOXIA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed DOXIA-358.
---
Assignee: Herve Boutemy
Resolution: Fixed
Fix Version/s: 1.1.2
fixed in r804288
> avoid to store in memory the full generated FO document when only table
> content is needed
> -
>
> Key: DOXIA-358
> URL: http://jira.codehaus.org/browse/DOXIA-358
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - FO
>Affects Versions: 1.1.1
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 1.1.2
>
>
> this is particularly needed when generating an aggregated document, since it
> can become really big.
> For example maven site generates a 2.7 MB {{apache-maven.fo}} file
--
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: (MAVENUPLOAD-2520) Upload Smackx 3.1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187245#action_187245 ] Christoph Kutzinski commented on MAVENUPLOAD-2520: -- Please, also upload the sources for it! I'm sick of all these open source libraries in Maven without sources attached. I mean what is open source good for without source code? > Upload Smackx 3.1.0 > --- > > Key: MAVENUPLOAD-2520 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2520 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Niklas Gustavsson > > This JAR is developed by Ignite Realtime, and not by me. However, Ignite has > not shown any great interest in uploading Smack to Maven central: > http://www.igniterealtime.org/community/message/164751 > And, this is merely an upgrade of the already existing releases, so the > groupId should be fine I hope. -- 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: (MJAVADOC-254) aggregation fails to get classpath, blows up
aggregation fails to get classpath, blows up Key: MJAVADOC-254 URL: http://jira.codehaus.org/browse/MJAVADOC-254 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Environment: maven 2.1.0, macos, java 1.5. Reporter: Benson Margulies Attachments: foo javadoc:aggregate blows up with an error inside of the javadoc tool. The immediate problem is that junit isn't in the classpath, so junit annotations explode. If I add junit to the dependencies of the aggregating project, I just run into trouble with other missing annotations, like some for Spring. [DEBUG] /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc @options @packages 1 error [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - In doclet class com.sun.tools.doclets.standard.Standard, method start has thrown an exception java.lang.reflect.InvocationTargetException java.lang.AssertionError: cannot find method org.junit.runner.RunWith.value() at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.findAccessMethod(ClassReader.java:1074) at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.deproxyCompound(ClassReader.java:1057) at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.deproxyCompoundList(ClassReader.java:1046) at com.sun.tools.javac.jvm.ClassReader$AnnotationCompleter.enterAnnotation(ClassReader.java:1195) at com.sun.tools.javac.comp.Annotate.flush(Annotate.java:94) at com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:1541) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:355) at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:612) at com.sun.tools.javac.code.Symbol$ClassSymbol.flags(Symbol.java:550) at com.sun.tools.javadoc.ClassDocImpl.getFlags(ClassDocImpl.java:105) at com.sun.tools.javadoc.ClassDocImpl.isAnnotationType(ClassDocImpl.java:116) at com.sun.tools.javadoc.DocEnv.isAnnotationType(DocEnv.java:574) at com.sun.tools.javadoc.DocEnv.getClassDoc(DocEnv.java:546) at com.sun.tools.javadoc.PackageDocImpl.getClasses(PackageDocImpl.java:152) at com.sun.tools.javadoc.PackageDocImpl.addAllClassesTo(PackageDocImpl.java:168) at com.sun.tools.javadoc.RootDocImpl.classes(RootDocImpl.java:178) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:96) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64) at com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42) at com.sun.tools.doclets.standard.Standard.start(Standard.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269) at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143) at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340) at com.sun.tools.javadoc.Start.begin(Start.java:128) at com.sun.tools.javadoc.Main.execute(Main.java:41) at com.sun.tools.javadoc.Main.main(Main.java:31) Command line was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc @options @packages -- 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-254) aggregation fails to get classpath, blows up
[ http://jira.codehaus.org/browse/MJAVADOC-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187261#action_187261 ] Benson Margulies commented on MJAVADOC-254: --- It seems off that the tests are getting processed, even though I never mention test-javadoc or test-aggregate anywhere. > aggregation fails to get classpath, blows up > > > Key: MJAVADOC-254 > URL: http://jira.codehaus.org/browse/MJAVADOC-254 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6 > Environment: maven 2.1.0, macos, java 1.5. >Reporter: Benson Margulies > Attachments: foo > > > javadoc:aggregate blows up with an error inside of the javadoc tool. The > immediate problem is that junit isn't in the classpath, so junit annotations > explode. If I add junit to the dependencies of the aggregating project, I > just run into trouble with other missing annotations, like some for Spring. > [DEBUG] > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > @options @packages > 1 error > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - > javadoc: error - In doclet class com.sun.tools.doclets.standard.Standard, > method start has thrown an exception > java.lang.reflect.InvocationTargetException > java.lang.AssertionError: cannot find method org.junit.runner.RunWith.value() > at > com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.findAccessMethod(ClassReader.java:1074) > at > com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.deproxyCompound(ClassReader.java:1057) > at > com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.deproxyCompoundList(ClassReader.java:1046) > at > com.sun.tools.javac.jvm.ClassReader$AnnotationCompleter.enterAnnotation(ClassReader.java:1195) > at com.sun.tools.javac.comp.Annotate.flush(Annotate.java:94) > at com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:1541) > at com.sun.tools.javac.code.Symbol.complete(Symbol.java:355) > at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:612) > at com.sun.tools.javac.code.Symbol$ClassSymbol.flags(Symbol.java:550) > at com.sun.tools.javadoc.ClassDocImpl.getFlags(ClassDocImpl.java:105) > at > com.sun.tools.javadoc.ClassDocImpl.isAnnotationType(ClassDocImpl.java:116) > at com.sun.tools.javadoc.DocEnv.isAnnotationType(DocEnv.java:574) > at com.sun.tools.javadoc.DocEnv.getClassDoc(DocEnv.java:546) > at > com.sun.tools.javadoc.PackageDocImpl.getClasses(PackageDocImpl.java:152) > at > com.sun.tools.javadoc.PackageDocImpl.addAllClassesTo(PackageDocImpl.java:168) > at com.sun.tools.javadoc.RootDocImpl.classes(RootDocImpl.java:178) > at > com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:96) > at > com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64) > at > com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42) > at com.sun.tools.doclets.standard.Standard.start(Standard.java:23) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269) > at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143) > at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340) > at com.sun.tools.javadoc.Start.begin(Start.java:128) > at com.sun.tools.javadoc.Main.execute(Main.java:41) > at com.sun.tools.javadoc.Main.main(Main.java:31) > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > @options @packages -- 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: (MJAVADOC-255) Cannot suppress reports
Cannot suppress reports --- Key: MJAVADOC-255 URL: http://jira.codehaus.org/browse/MJAVADOC-255 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Reporter: Benson Margulies I wanted to suppress javadoc aggregation for mvn site:site. So, I tried No effect. it goes ahead and runs the aggregate report. help:effectivePom does not show the empty reportSets element. -- 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: (MJAVADOC-256) No list of the possible reports in the doc
No list of the possible reports in the doc -- Key: MJAVADOC-256 URL: http://jira.codehaus.org/browse/MJAVADOC-256 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Reporter: Benson Margulies Reading up one side of the doc and down the other, I get the feeling that there is a 1-1 relationship between the goals and the reports. But nothing on the site says this in so many words. The pom doc on reporting and reportSets seems to think that the javadoc plugin will carry the load, and vica versa. -- 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
