[jira] Commented: (DOXIA-426) Markdown module
[ http://jira.codehaus.org/browse/DOXIA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267216#action_267216 ] Lukas Theussl commented on DOXIA-426: - Thanks! I have [added the module to the sandbox|http://svn.apache.org/viewvc?rev=1104018&view=rev] for the moment. Some questions/comments: * since MarkdownSink is not implemented it would be better to remove the class altogether, or do you plan to provide an implementation? * the MarkdownParser emits the parsing result as rawText, this means the parser is only usable for html output (see related DOXIA-183). This should be re-written to emit proper doxia events (e.g. by chaining a XhtmlParser). * I'd prefer some more realistic test cases before promoting this out of the sandbox > Markdown module > --- > > Key: DOXIA-426 > URL: http://jira.codehaus.org/browse/DOXIA-426 > Project: Maven Doxia > Issue Type: New Feature > Components: Modules >Affects Versions: 1.3 >Reporter: Julien Nicoulaud > Attachments: doxia-module-markdown.patch > > > [Markdown|http://en.wikipedia.org/wiki/Markdown] is a widespread Markup > language. It would be nice if there was a Doxia module for Markdown. > Here is a proposed simple implementation that defers all the parsing and > rendering to [PegDown|http://pegdown.org] (Apache License V2), which is the > most reliable Java library for Markdown. -- 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: (DOXIA-104) Support use of custom properties in XDOC files
[ http://jira.codehaus.org/browse/DOXIA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267218#action_267218 ] Lukas Theussl commented on DOXIA-104: - It is resolved as 'Won't fix'. Unknown sink events are events that a parser may emit when it encounters an element for which no sink method exists. Eg the xdoc parser may emit an unknown event for a
[jira] Created: (MDEP-311) Parameter for "dependency:copy-dependencies" could not provided from command line
Parameter for "dependency:copy-dependencies" could not provided from command line - Key: MDEP-311 URL: http://jira.codehaus.org/browse/MDEP-311 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Conny Kreyssel Assignee: Brian Fox I have to try to make a offline repository for our multi project. But if i call "mvn dependency:copy-dependencies -DoutputDirectory=... -DcopyPom=true -DuseRepositoryLayout=true" it exports all artifacts in flat mode without poms. If i set this plugin params in the project master pom, it exports all artifact in repository layout and inclusive poms. I think this could happen on more than the provided params. -- 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
Re: Created: (MECLIPSE-676) linkedResources: vs
How can i apply this patch to the plugin? greetz -- View this message in context: http://maven.40175.n5.nabble.com/Created-MECLIPSE-676-linkedResources-location-vs-locationURI-tp3275128p4402673.html Sent from the Maven - Issues mailing list archive at Nabble.com.
[jira] Commented: (DOXIA-104) Support use of custom properties in XDOC files
[ http://jira.codehaus.org/browse/DOXIA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267219#action_267219 ] Data Nucleus commented on DOXIA-104: Hi Lukas, i've tried various versions. Most recently 2.1.1 since 2.1 is buggy for validating basic XDOC documents. Yes, it preserves the in the generated (X)HTML, but I'm not too bothered about preserving them. My question is how do I access them in a velocity file site.vm? ???.head.name or something? Thx > Support use of custom properties in XDOC files > -- > > Key: DOXIA-104 > URL: http://jira.codehaus.org/browse/DOXIA-104 > Project: Maven Doxia > Issue Type: Task > Components: Module - Xdoc >Affects Versions: 1.0-alpha-8 >Reporter: Andy Jefferson >Assignee: Lukas Theussl >Priority: Critical > > In the JPOX Maven1 use of "site" we tagged all (XDOC) docs like this > > > Application Identity > Persistence > 1_2 > > ... > > since XDOCs werent validated against any DTD etc. > Then in site.jsl we could access these properties via > > > > With Maven2 I don't see how I can do this. I define my own skin for JPOX and > in site.vm I have $title, $authors but nothing more. Delving into Doxia I see > where they were set up. No allowance for users own properties. > The requirement for JPOX is that we have a large number of documents, and we > tag each doc for particular categories ... which will then appear on the web > site as horizontal navigation (the default Maven skin only has the navColumn > ... vertical navigation). By being able to tag docs into > categories/subcategories etc we can then generate a site that the user > selects a horizontal nav category, and then a horizontal nav sub-category, > and they see vertical navigation within that subcategory. This was possible > with Maven1 due to the above ability. Without an equivalent in Maven2 we > cannot switch over. > The JPOX docs (from Maven1) are available at > http://www.jpox.org/docs/1_2/index.html > so you can understand what is being talked about here. If you need any more > info let me know. -- 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: (DOXIA-104) Support use of custom properties in XDOC files
[ http://jira.codehaus.org/browse/DOXIA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267221#action_267221 ] Lukas Theussl commented on DOXIA-104: - The DefaultSiteRenderer emits the head in a variable $headContent, but as a plain String, so I'm afraid you can't access child elements like above. > Support use of custom properties in XDOC files > -- > > Key: DOXIA-104 > URL: http://jira.codehaus.org/browse/DOXIA-104 > Project: Maven Doxia > Issue Type: Task > Components: Module - Xdoc >Affects Versions: 1.0-alpha-8 >Reporter: Andy Jefferson >Assignee: Lukas Theussl >Priority: Critical > > In the JPOX Maven1 use of "site" we tagged all (XDOC) docs like this > > > Application Identity > Persistence > 1_2 > > ... > > since XDOCs werent validated against any DTD etc. > Then in site.jsl we could access these properties via > > > > With Maven2 I don't see how I can do this. I define my own skin for JPOX and > in site.vm I have $title, $authors but nothing more. Delving into Doxia I see > where they were set up. No allowance for users own properties. > The requirement for JPOX is that we have a large number of documents, and we > tag each doc for particular categories ... which will then appear on the web > site as horizontal navigation (the default Maven skin only has the navColumn > ... vertical navigation). By being able to tag docs into > categories/subcategories etc we can then generate a site that the user > selects a horizontal nav category, and then a horizontal nav sub-category, > and they see vertical navigation within that subcategory. This was possible > with Maven1 due to the above ability. Without an equivalent in Maven2 we > cannot switch over. > The JPOX docs (from Maven1) are available at > http://www.jpox.org/docs/1_2/index.html > so you can understand what is being talked about here. If you need any more > info let me know. -- 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-427) Doesn't handle HTML "EMBED" element
Doesn't handle HTML "EMBED" element --- Key: DOXIA-427 URL: http://jira.codehaus.org/browse/DOXIA-427 Project: Maven Doxia Issue Type: Bug Components: Module - Xdoc Affects Versions: 1.2 Reporter: Data Nucleus If I have an XDOC file with http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";> http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"/> then Maven site comes up with [WARNING] [XHTML Sink] No HTML tag found for unknown event: 'embed', ignoring! The resultant HTML has Demo http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";> Is there a way I can get the generated HTML to include this valid HTML tag? Thx -- 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-464) Site generation fails on in xdoc documentation
[
http://jira.codehaus.org/browse/MSITE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267222#action_267222
]
Data Nucleus commented on MSITE-464:
Same thing seems to happen with the PDF plugin. Has it been fixed in that?
(i've used PDF v1.1, SITE v2.1.1)
XDOC has
...
with no XSD, and PDF plugin gives
[INFO] Error during document generation: Error parsing
/home/andy/work/dn_maven2_site/target/pdf/site.tmp/xdoc/guides/jdo/springframework/index.xml:
Error validating the model: Error:
Public ID: null
System ID: null
Line number: 2
Column number: 11
Message: cvc-elt.1: Cannot find the declaration of element 'document'.
> Site generation fails on in xdoc documentation
> -
>
> Key: MSITE-464
> URL: http://jira.codehaus.org/browse/MSITE-464
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Windows XP, Maven 2.2.1, JDK 1.6.0_17
>Reporter: Niall Pemberton
>Assignee: Lukas Theussl
> Fix For: 2.1.1
>
> Attachments: MSITE-464.zip, test_doctype.xml
>
>
> Apache Commons has a couple of components with documentation showing examples
> of XML documents including the element - these are enclosed in
> CDATA elements and docs generated with no problems using version 2.0.1 of the
> maven-site-plugin - but fail with version 2.1.
> Running "mvn site" fails with the following error:
> {code}
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error parsing
> 'C:\svn\commons-proper\chain\xdocs\test_doctype.xml': line [-1] Error
> validating the model: Error:
> Public ID: null
> System ID: null
> Line number: 3
> Column number: 11
> Message: cvc-elt.1: Cannot find the declaration of element 'document'.
> {code}
> I'm attaching an example xdoc document which causes this issue
--
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-5094) If POM's parent is not availabe in local repository then DefaultProjectBuilder is unable to resolve this parent while POM build
If POM's parent is not availabe in local repository then DefaultProjectBuilder is unable to resolve this parent while POM build --- Key: MNG-5094 URL: http://jira.codehaus.org/browse/MNG-5094 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.3 Environment: Linux, Using maven 3.0.3 apis to build a MavenProject from a POM file via DefaultProjectBuilder. Reporter: amaresh mourya I created a maven project via "mvn archetype:generate" with selection item no as 3. Project I created was abc:xyz:1.0:jar. I am using build( File pomFile, ProjectBuildingRequest request ) method of DefaultProjectBuilder which returns ProjectBuildingResult containing MavenProject of POM file. Here is parent section of POM http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 com.cedarsoft open 4.0.2 abc xyz 1.0 --- Problem: My local repository doesn't contain com.cedarsoft:open:4.0.2. So while building with this build method I was expecting it to download parent (com.cedarsoft:open:4.0.2) and move ahead with the building work, but it didn't happen. This used to happen with maven 2.2.1 apis using DefaultMavenProjectBuilder. I debugged and found that while resolving parent (com.cedarsoft:open:4.0.2) repositories list is empty whereas it should provide Central repository from Super POM to resolve this parent artifact. This used to happen with maven 2.2.1 apis What I did to avoid this : Either I add central repository in my POM or add Central repository in ProjectBuildingRequest. So I think this is a bug of maven 3.0.3 where its unable to pass central repository while resolving artifacts. -- 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-464) Site generation fails on in xdoc documentation
[
http://jira.codehaus.org/browse/MSITE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267223#action_267223
]
Lukas Theussl commented on MSITE-464:
-
See MPDF-39
> Site generation fails on in xdoc documentation
> -
>
> Key: MSITE-464
> URL: http://jira.codehaus.org/browse/MSITE-464
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Windows XP, Maven 2.2.1, JDK 1.6.0_17
>Reporter: Niall Pemberton
>Assignee: Lukas Theussl
> Fix For: 2.1.1
>
> Attachments: MSITE-464.zip, test_doctype.xml
>
>
> Apache Commons has a couple of components with documentation showing examples
> of XML documents including the element - these are enclosed in
> CDATA elements and docs generated with no problems using version 2.0.1 of the
> maven-site-plugin - but fail with version 2.1.
> Running "mvn site" fails with the following error:
> {code}
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error parsing
> 'C:\svn\commons-proper\chain\xdocs\test_doctype.xml': line [-1] Error
> validating the model: Error:
> Public ID: null
> System ID: null
> Line number: 3
> Column number: 11
> Message: cvc-elt.1: Cannot find the declaration of element 'document'.
> {code}
> I'm attaching an example xdoc document which causes this issue
--
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: (DOXIA-427) Doesn't handle HTML "EMBED" element
[
http://jira.codehaus.org/browse/DOXIA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated DOXIA-427:
Description:
If I have an XDOC file with
{code:xml}
http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"/>
{code}
then Maven site comes up with
{noformat}[WARNING] [XHTML Sink] No HTML tag found for unknown event: 'embed',
ignoring!{noformat}
The resultant HTML has
{code:xml}
Demo
http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
{code}
Is there a way I can get the generated HTML to include this valid HTML tag?
Thx
was:
If I have an XDOC file with
http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"/>
then Maven site comes up with
[WARNING] [XHTML Sink] No HTML tag found for unknown event: 'embed', ignoring!
The resultant HTML has
Demo
http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
Is there a way I can get the generated HTML to include this valid HTML tag?
Thx
> Doesn't handle HTML "EMBED" element
> ---
>
> Key: DOXIA-427
> URL: http://jira.codehaus.org/browse/DOXIA-427
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Xdoc
>Affects Versions: 1.2
>Reporter: Data Nucleus
>
> If I have an XDOC file with
> {code:xml}
>
>
> height="620"
> codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
>
>
>
>
>loop="false" TYPE="application/x-shockwave-flash"
> PLUGINSPAGE="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"/>
>
>
>
>
> {code}
> then Maven site comes up with
> {noformat}[WARNING] [XHTML Sink] No HTML tag found for unknown event:
> 'embed', ignoring!{noformat}
> The resultant HTML has
> {code:xml}
> Demo
>
> height="620"
> codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
>
>
>
>
>
>
>
>
> {code}
> Is there a way I can get the generated HTML to include this valid HTML tag?
> Thx
--
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: (DOXIA-427) Doesn't handle HTML "EMBED" element
[
http://jira.codehaus.org/browse/DOXIA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267228#action_267228
]
Lukas Theussl commented on DOXIA-427:
-
You could use the SWF Macro to embed flash :
http://maven.apache.org/doxia/macros/index.html#SWF_Macro (disclaimer: I have
never used it myself).
> Doesn't handle HTML "EMBED" element
> ---
>
> Key: DOXIA-427
> URL: http://jira.codehaus.org/browse/DOXIA-427
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Xdoc
>Affects Versions: 1.2
>Reporter: Data Nucleus
>
> If I have an XDOC file with
> {code:xml}
>
>
> height="620"
> codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
>
>
>
>
>loop="false" TYPE="application/x-shockwave-flash"
> PLUGINSPAGE="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"/>
>
>
>
>
> {code}
> then Maven site comes up with
> {noformat}[WARNING] [XHTML Sink] No HTML tag found for unknown event:
> 'embed', ignoring!{noformat}
> The resultant HTML has
> {code:xml}
> Demo
>
> height="620"
> codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
>
>
>
>
>
>
>
>
> {code}
> Is there a way I can get the generated HTML to include this valid HTML tag?
> Thx
--
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: (DOXIA-427) Doesn't handle HTML "EMBED" element
[
http://jira.codehaus.org/browse/DOXIA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated DOXIA-427:
Component/s: Module - Xhtml
Core
> Doesn't handle HTML "EMBED" element
> ---
>
> Key: DOXIA-427
> URL: http://jira.codehaus.org/browse/DOXIA-427
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core, Module - Xdoc, Module - Xhtml
>Affects Versions: 1.2
>Reporter: Data Nucleus
>
> If I have an XDOC file with
> {code:xml}
>
>
> height="620"
> codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
>
>
>
>
>loop="false" TYPE="application/x-shockwave-flash"
> PLUGINSPAGE="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"/>
>
>
>
>
> {code}
> then Maven site comes up with
> {noformat}[WARNING] [XHTML Sink] No HTML tag found for unknown event:
> 'embed', ignoring!{noformat}
> The resultant HTML has
> {code:xml}
> Demo
>
> height="620"
> codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
>
>
>
>
>
>
>
>
> {code}
> Is there a way I can get the generated HTML to include this valid HTML tag?
> Thx
--
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: (DOXIA-427) Doesn't handle HTML "EMBED" element
[
http://jira.codehaus.org/browse/DOXIA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267229#action_267229
]
Lukas Theussl commented on DOXIA-427:
-
Btw, is HTML 5 only, doxia does not support any of the new [HTML 5
elements|http://dev.w3.org/html5/html4-differences/#new-elements].
> Doesn't handle HTML "EMBED" element
> ---
>
> Key: DOXIA-427
> URL: http://jira.codehaus.org/browse/DOXIA-427
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core, Module - Xdoc, Module - Xhtml
>Affects Versions: 1.2
>Reporter: Data Nucleus
>
> If I have an XDOC file with
> {code:xml}
>
>
> height="620"
> codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
>
>
>
>
>loop="false" TYPE="application/x-shockwave-flash"
> PLUGINSPAGE="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"/>
>
>
>
>
> {code}
> then Maven site comes up with
> {noformat}[WARNING] [XHTML Sink] No HTML tag found for unknown event:
> 'embed', ignoring!{noformat}
> The resultant HTML has
> {code:xml}
> Demo
>
> height="620"
> codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0";>
>
>
>
>
>
>
>
>
> {code}
> Is there a way I can get the generated HTML to include this valid HTML tag?
> Thx
--
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: (MCOMPILER-155) Ignore output line "Picked up _JAVA_OPTIONS ..."
Ignore output line "Picked up _JAVA_OPTIONS ..." Key: MCOMPILER-155 URL: http://jira.codehaus.org/browse/MCOMPILER-155 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.3.2 Reporter: Raimar Falke Attachments: picked_up.patch If the environment variable _JAVA_OPTIONS is set the forked javac process writes a line "Picked up _JAVA_OPTIONS..." which is not understood by the maven plugin. The 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
[jira] Updated: (SUREFIRE-704) maven surefire Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetStarting called twice
[
http://jira.codehaus.org/browse/SUREFIRE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S Daigle updated SUREFIRE-704:
--
Attachment: stack.txt
test-out.txt
Hi Kristian. Now that we're using the latest 2.8.2-SNAPSHOT version of the
plugin, were seeing the following errors in some of our tests. For example,
this happened with a System.err.println("foo");
java.lang.NullPointerException
at
org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:84)
at
com.attivio.special.client.AttivioDocumentClientTest.getBatchingDocumentClient(AttivioDocumentClientTest.java:65)
at
com.attivio.special.client.AttivioDocumentClientTest.batchingDocumentTest(AttivioDocumentClientTest.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Do you know what this is? I attach the stack.txt and test-out.txt logfiles so
you have more information.
Thanks
> maven surefire Error while executing forked tests.; nested exception is
> java.lang.IllegalStateException: testSetStarting called twice
> -
>
> Key: SUREFIRE-704
> URL: http://jira.codehaus.org/browse/SUREFIRE-704
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
>Affects Versions: 2.7.2
> Environment: Windows/Linux/SunOS
>Reporter: S Daigle
>Assignee: Kristian Rosenvold
> Fix For: 2.8.2
>
> Attachments: stack.txt, surefire-272.txt, surefire-failure.log,
> surefire.txt, test-out.txt
>
>
> We want to upgrade from our current 2.5 version of the maven-surefire-plugin
> to something newer but cannot get past the error below. We've tried versions
> 2.6, 2.7 up to and including 2.7.3-SNAPSHOT but they all fail.
> When setting forkmode to "once" and redirectTestOutputToFile to "true", we
> get the following error on multiple tests:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.7.3-SNAPSHOT:test
> (default-test) on project api: Error while executing forked tests.; nested
> exception is java.lang.IllegalStateException: testSetStarting called twice ->
> [Help 1]
> Please see the attachment for full "mvn -e test" output.
> If we set the redirectTestOutputToFile to false, it works but we need this
> option set to true.
> 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] Reopened: (SUREFIRE-704) maven surefire Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetStarting called twice
[ http://jira.codehaus.org/browse/SUREFIRE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S Daigle reopened SUREFIRE-704: --- Hi Kristian. I reopened because I didn't know if you would get my last update. > maven surefire Error while executing forked tests.; nested exception is > java.lang.IllegalStateException: testSetStarting called twice > - > > Key: SUREFIRE-704 > URL: http://jira.codehaus.org/browse/SUREFIRE-704 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.7.2 > Environment: Windows/Linux/SunOS >Reporter: S Daigle >Assignee: Kristian Rosenvold > Fix For: 2.8.2 > > Attachments: stack.txt, surefire-272.txt, surefire-failure.log, > surefire.txt, test-out.txt > > > We want to upgrade from our current 2.5 version of the maven-surefire-plugin > to something newer but cannot get past the error below. We've tried versions > 2.6, 2.7 up to and including 2.7.3-SNAPSHOT but they all fail. > When setting forkmode to "once" and redirectTestOutputToFile to "true", we > get the following error on multiple tests: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.3-SNAPSHOT:test > (default-test) on project api: Error while executing forked tests.; nested > exception is java.lang.IllegalStateException: testSetStarting called twice -> > [Help 1] > Please see the attachment for full "mvn -e test" output. > If we set the redirectTestOutputToFile to false, it works but we need this > option set to true. > 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] Commented: (SUREFIRE-704) maven surefire Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetStarting called twice
[ http://jira.codehaus.org/browse/SUREFIRE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267259#action_267259 ] Kristian Rosenvold commented on SUREFIRE-704: - I need the relevant pars of your pom.xml (surefire config) > maven surefire Error while executing forked tests.; nested exception is > java.lang.IllegalStateException: testSetStarting called twice > - > > Key: SUREFIRE-704 > URL: http://jira.codehaus.org/browse/SUREFIRE-704 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.7.2 > Environment: Windows/Linux/SunOS >Reporter: S Daigle >Assignee: Kristian Rosenvold > Fix For: 2.8.2 > > Attachments: stack.txt, surefire-272.txt, surefire-failure.log, > surefire.txt, test-out.txt > > > We want to upgrade from our current 2.5 version of the maven-surefire-plugin > to something newer but cannot get past the error below. We've tried versions > 2.6, 2.7 up to and including 2.7.3-SNAPSHOT but they all fail. > When setting forkmode to "once" and redirectTestOutputToFile to "true", we > get the following error on multiple tests: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.3-SNAPSHOT:test > (default-test) on project api: Error while executing forked tests.; nested > exception is java.lang.IllegalStateException: testSetStarting called twice -> > [Help 1] > Please see the attachment for full "mvn -e test" output. > If we set the redirectTestOutputToFile to false, it works but we need this > option set to true. > 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] Issue Comment Edited: (SUREFIRE-704) maven surefire Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetStarting called twice
[ http://jira.codehaus.org/browse/SUREFIRE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267259#action_267259 ] Kristian Rosenvold edited comment on SUREFIRE-704 at 5/17/11 12:07 PM: --- I need the relevant parts of your pom.xml (surefire config). And yes, I see everything that goes on here ;) was (Author: krosenvold): I need the relevant pars of your pom.xml (surefire config) > maven surefire Error while executing forked tests.; nested exception is > java.lang.IllegalStateException: testSetStarting called twice > - > > Key: SUREFIRE-704 > URL: http://jira.codehaus.org/browse/SUREFIRE-704 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.7.2 > Environment: Windows/Linux/SunOS >Reporter: S Daigle >Assignee: Kristian Rosenvold > Fix For: 2.8.2 > > Attachments: stack.txt, surefire-272.txt, surefire-failure.log, > surefire.txt, test-out.txt > > > We want to upgrade from our current 2.5 version of the maven-surefire-plugin > to something newer but cannot get past the error below. We've tried versions > 2.6, 2.7 up to and including 2.7.3-SNAPSHOT but they all fail. > When setting forkmode to "once" and redirectTestOutputToFile to "true", we > get the following error on multiple tests: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.3-SNAPSHOT:test > (default-test) on project api: Error while executing forked tests.; nested > exception is java.lang.IllegalStateException: testSetStarting called twice -> > [Help 1] > Please see the attachment for full "mvn -e test" output. > If we set the redirectTestOutputToFile to false, it works but we need this > option set to true. > 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] Updated: (SUREFIRE-704) maven surefire Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetStarting called twice
[ http://jira.codehaus.org/browse/SUREFIRE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S Daigle updated SUREFIRE-704: -- Attachment: sf-pom-config.txt Thanks again Kristian. I attached our surefire plugin config for you. > maven surefire Error while executing forked tests.; nested exception is > java.lang.IllegalStateException: testSetStarting called twice > - > > Key: SUREFIRE-704 > URL: http://jira.codehaus.org/browse/SUREFIRE-704 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.7.2 > Environment: Windows/Linux/SunOS >Reporter: S Daigle >Assignee: Kristian Rosenvold > Fix For: 2.8.2 > > Attachments: sf-pom-config.txt, stack.txt, surefire-272.txt, > surefire-failure.log, surefire.txt, test-out.txt > > > We want to upgrade from our current 2.5 version of the maven-surefire-plugin > to something newer but cannot get past the error below. We've tried versions > 2.6, 2.7 up to and including 2.7.3-SNAPSHOT but they all fail. > When setting forkmode to "once" and redirectTestOutputToFile to "true", we > get the following error on multiple tests: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.3-SNAPSHOT:test > (default-test) on project api: Error while executing forked tests.; nested > exception is java.lang.IllegalStateException: testSetStarting called twice -> > [Help 1] > Please see the attachment for full "mvn -e test" output. > If we set the redirectTestOutputToFile to false, it works but we need this > option set to true. > 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] Closed: (SUREFIRE-704) maven surefire Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetStarting called twice
[ http://jira.codehaus.org/browse/SUREFIRE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-704. --- Resolution: Fixed Extended IT and fixed piggybacked bug report in r1104433, updated snapshot published. It is generally easier to keep track of what is opened/closed at any given time if you create new issues for different problems, even if the version is not yet released. > maven surefire Error while executing forked tests.; nested exception is > java.lang.IllegalStateException: testSetStarting called twice > - > > Key: SUREFIRE-704 > URL: http://jira.codehaus.org/browse/SUREFIRE-704 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.7.2 > Environment: Windows/Linux/SunOS >Reporter: S Daigle >Assignee: Kristian Rosenvold > Fix For: 2.8.2 > > Attachments: sf-pom-config.txt, stack.txt, surefire-272.txt, > surefire-failure.log, surefire.txt, test-out.txt > > > We want to upgrade from our current 2.5 version of the maven-surefire-plugin > to something newer but cannot get past the error below. We've tried versions > 2.6, 2.7 up to and including 2.7.3-SNAPSHOT but they all fail. > When setting forkmode to "once" and redirectTestOutputToFile to "true", we > get the following error on multiple tests: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.3-SNAPSHOT:test > (default-test) on project api: Error while executing forked tests.; nested > exception is java.lang.IllegalStateException: testSetStarting called twice -> > [Help 1] > Please see the attachment for full "mvn -e test" output. > If we set the redirectTestOutputToFile to false, it works but we need this > option set to true. > 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] Commented: (SUREFIRE-704) maven surefire Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetStarting called twice
[ http://jira.codehaus.org/browse/SUREFIRE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267271#action_267271 ] S Daigle commented on SUREFIRE-704: --- Thanks so much Kristian for the quick turnaround on this. I tested your changes and no more errors. I'll remember to open new issues in the future. Thanks again for all your help with this plugin. > maven surefire Error while executing forked tests.; nested exception is > java.lang.IllegalStateException: testSetStarting called twice > - > > Key: SUREFIRE-704 > URL: http://jira.codehaus.org/browse/SUREFIRE-704 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.7.2 > Environment: Windows/Linux/SunOS >Reporter: S Daigle >Assignee: Kristian Rosenvold > Fix For: 2.8.2 > > Attachments: sf-pom-config.txt, stack.txt, surefire-272.txt, > surefire-failure.log, surefire.txt, test-out.txt > > > We want to upgrade from our current 2.5 version of the maven-surefire-plugin > to something newer but cannot get past the error below. We've tried versions > 2.6, 2.7 up to and including 2.7.3-SNAPSHOT but they all fail. > When setting forkmode to "once" and redirectTestOutputToFile to "true", we > get the following error on multiple tests: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.3-SNAPSHOT:test > (default-test) on project api: Error while executing forked tests.; nested > exception is java.lang.IllegalStateException: testSetStarting called twice -> > [Help 1] > Please see the attachment for full "mvn -e test" output. > If we set the redirectTestOutputToFile to false, it works but we need this > option set to true. > 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: (SUREFIRE-740) Fractional part of method execution time is truncated for non English locale
Fractional part of method execution time is truncated for non English locale
Key: SUREFIRE-740
URL: http://jira.codehaus.org/browse/SUREFIRE-740
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Report Plugin
Affects Versions: 2.8.1
Environment: Windows 7 Pro x64 with Russian locale/JDK 1.6.0_21/Apache
Maven 3.0.3 (r1075438; 2011-02-28 20:31:09+0300)
Reporter: Dmitry Malenok
The problem is that Maven Surefire Plugin and Maven Surefire Report Plugin use
different locales for writing and reading TEST-* file if the default locale is
not set to English locale.The first one always uses "Locale.ENGLISH"
(org.apache.maven.surefire.report.AbstractReporter, line 43), but the second
one uses the default locale
(org.apache.maven.plugins.surefire.report.TestSuiteXmlParser, line 50). Russian
and English locale use different decimal symbol ("," - Russian locale, '.' -
English locale) that causes the described 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
