[jira] Commented: (MNG-2551) pom metadata file gets truncated during install into local repository
[ http://jira.codehaus.org/browse/MNG-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119114 ] Lee Bieber commented on MNG-2551: - I have the same problem as described above, when ever I deploy a jar file into my repository, the pom file is truncated at 4096 bytes. This is using maven 2.0.8, with Java 1.5.0_12 on CentOS. This happens when I do NOT use SNAPSHOT in my version string and run "mvn deploy" > pom metadata file gets truncated during install into local repository > - > > Key: MNG-2551 > URL: http://jira.codehaus.org/browse/MNG-2551 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.4 > Environment: Win XP, JDK 1.4 >Reporter: Sharmarke Aden > Fix For: Reviewed Pending Version Assignment > > Attachments: pom.xml, shared-1.9.0.pom > > > When I attempt to install my project artifact to my local repository it seems > that sometimes an incomplete/truncated ".pom" is deployed to my local > repository. It's kind of weird because sometimes it happens and sometimes it > doesn't. Any thoughts as to what could cause this? Attached is my pom.xml and > the truncated pom meta data artifact deployed to my local repository. One > thing I found that's odd is that the size of the truncated pom generated is > consistently 4096 bytes. > p.s. my pom.xml is UTF-8 encoded and uses Unix style line delimiters. -- 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: (MNG-2551) pom metadata file gets truncated during install into local repository
[
http://jira.codehaus.org/browse/MNG-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127560
]
Lee Bieber commented on MNG-2551:
-
Looks like a pilot error on my part. I was deploying to the same repository as
I was trying to retrieve the pom file from. So the best solution I can find is
to set distribution management as this:
common-repository
Common Repository
file://${basedir}/target/deploy
> pom metadata file gets truncated during install into local repository
> -
>
> Key: MNG-2551
> URL: http://jira.codehaus.org/browse/MNG-2551
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 2.0.4
> Environment: Win XP, JDK 1.4
>Reporter: Sharmarke Aden
>Assignee: Brian Fox
> Attachments: pom-good.xml, pom.xml, shared-1.9.0.pom
>
>
> When I attempt to install my project artifact to my local repository it seems
> that sometimes an incomplete/truncated ".pom" is deployed to my local
> repository. It's kind of weird because sometimes it happens and sometimes it
> doesn't. Any thoughts as to what could cause this? Attached is my pom.xml and
> the truncated pom meta data artifact deployed to my local repository. One
> thing I found that's odd is that the size of the truncated pom generated is
> consistently 4096 bytes.
> p.s. my pom.xml is UTF-8 encoded and uses Unix style line delimiters.
--
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: (MSUREFIRE-165) Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest method
[ http://jira.codehaus.org/browse/MSUREFIRE-165?page=comments#action_80808
]
Lee Bieber commented on MSUREFIRE-165:
--
I'm having the same issue, has this ever been resolved?
> Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest
> method
> ---
>
> Key: MSUREFIRE-165
> URL: http://jira.codehaus.org/browse/MSUREFIRE-165
> Project: Maven 2.x Surefire Plugin
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.2, 2.3
> Environment: Windows XP, JDK 1.5, Maven 2.0.4, TestNG 5.1
>Reporter: Manish Shah
>
> Create a TestNG test with a method as follows:
> @BeforeTest
> public void beforeTest() {
> throw new RuntimeException("Simulate an exception from a beforeTest
> method");
> }
> When surefire attempts to run this test, the plugin fails with the following
> stack trace:
> org.apache.maven.surefire.booter.SurefireExecutionException: null; nested
> exception is java.lang.NullPointerException: n
> ull
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.report.AbstractTextReporter.testFailed(AbstractTextReporter.java:106)
> at
> org.apache.maven.surefire.report.ReporterManager.testFailed(ReporterManager.java:299)
> at
> org.apache.maven.surefire.report.ReporterManager.testFailed(ReporterManager.java:281)
> at
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:97)
> at org.testng.internal.Invoker.runTestListeners(Invoker.java:1164)
> at org.testng.internal.Invoker.runTestListeners(Invoker.java:1149)
> at
> org.testng.internal.Invoker.handleConfigurationFailure(Invoker.java:191)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:170)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:236)
> at org.testng.SuiteRunner.run(SuiteRunner.java:145)
> at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:901)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:863)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:64)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)
--
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
