[jira] Created: (MJAVADOC-307) phases not executed
phases not executed --- Key: MJAVADOC-307 URL: http://jira.codehaus.org/browse/MJAVADOC-307 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.7, 2.6.1, 2.6, 2.5 Environment: linux, windows, maven 2.2.1 Reporter: Luca Priority: Critical it is a strange issue... if you use a javadoc plugin 2.4 then the following occurs: launching mvn without site phase all works fine like expected. launching mvn with site then some phases in modules are not executed. i.e. 'mvn clean install site' then the install phase is not executed if you comment the javadoc plugin or you use the 2.4 version, all works again -- 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: (MJAVADOC-307) phases not executed
[ http://jira.codehaus.org/browse/MJAVADOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca updated MJAVADOC-307: -- Attachment: javadoc-issue.tgz phases not executed --- Key: MJAVADOC-307 URL: http://jira.codehaus.org/browse/MJAVADOC-307 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.5, 2.6, 2.6.1, 2.7 Environment: linux, windows, maven 2.2.1 Reporter: Luca Priority: Critical Attachments: javadoc-issue.tgz it is a strange issue... if you use a javadoc plugin 2.4 then the following occurs: launching mvn without site phase all works fine like expected. launching mvn with site then some phases in modules are not executed. i.e. 'mvn clean install site' then the install phase is not executed if you comment the javadoc plugin or you use the 2.4 version, all works again -- 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: (MASSEMBLY-542) Create bill of materials
Create bill of materials Key: MASSEMBLY-542 URL: http://jira.codehaus.org/browse/MASSEMBLY-542 Project: Maven 2.x Assembly Plugin Issue Type: New Feature Reporter: Max Schaefer I would like the assembly plugin to produce a kind of bill of materials xml. That should tell where each file came from. E.g. if in a dependency set the files are renamed via the output filename mapping I would like to know what was the original maven coordinate. If an archive is unpacked I would like to know which files were extracted. That would make it much easier to track down the maven artifact that originally contained certain files of my assembly. The bill of materials could even transformed into a maven report. -- 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: (MRELEASE-318) Release plugin throws NullPointerException when using version range for dependency
[ http://jira.codehaus.org/browse/MRELEASE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252187#action_252187 ] Kristoffer Peterhäesel commented on MRELEASE-318: - Yeah. Not working for me in Maven 2.2.1 either. Exact same stack trace as the one from [~mdp] Release plugin throws NullPointerException when using version range for dependency -- Key: MRELEASE-318 URL: http://jira.codehaus.org/browse/MRELEASE-318 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.0-beta-7 Reporter: David Hoffer Assignee: Brett Porter Priority: Blocker Fix For: 2.1 Attachments: MNG-3351-unittest.patch, MNG-3351.zip, MNG-3351_dependency_poms.zip, simple-test-case-console-log.txt, simple-testcase.zip After upgrading to 2.0.8 I find that the release plugin throws NPE if any dependency uses version range. I have one dependency with version range version[1.0,2.0)/version the rest are test scope with fixed version. Here is the crash stack trace: java.lang.NullPointerException: version was null for com.xrite:xrite-colorlib-api [13:42:05]: at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) [13:42:05]: at org.apache.maven.artifact.DefaultArtifact.isSnapshot(DefaultArtifact.java:557) [13:42:05]: at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkArtifact(CheckDependencySnapshotsPhase.java:252) [13:42:05]: at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkProject(CheckDependencySnapshotsPhase.java:138) [13:42:05]: at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.execute(CheckDependencySnapshotsPhase.java:106) [13:42:05]: at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) [13:42:05]: at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) [13:42:05]: at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) [13:42:05]: at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:127) [13:42:05]: at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:228) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) [13:42:05]: at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) [13:42:05]: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) [13:42:05]: at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) [13:42:05]: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [13:42:05]: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [13:42:05]: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [13:42:05]: at java.lang.reflect.Method.invoke(Method.java:597) [13:42:05]: at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [13:42:05]: at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [13:42:05]: at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [13:42:05]: at org.codehaus.classworlds.Launcher.main(Launcher.java:375) It seems the reason version is null is that the call to selectVersionFromNewRangeIfAvailable() assumes that versionRange.getRecommendedVersion() will always return non-null, else it sets the version to null! However during the release:prepare phase this is not true, see the output: [13:42:04]: [INFO] [release:prepare] [13:42:04]: [INFO] Verifying that there are no local modifications... [13:42:04]: [INFO] Executing: svn --non-interactive status [13:42:04]: [INFO] Working directory: C:\BuildAgent\work\23044d751bcc9843 [13:42:05]: [INFO] Checking dependencies and plugins for snapshots ... [13:42:05]: TEST!!! version=null [13:42:05]: TEST!!! versionRange=[1.0,2.0) [13:42:05]: TEST!!! getRecommendedVersion=null TEST!!! Lines are my test code so I could see what is going on here. -- This message is
[jira] Created: (MNG-4987) LATEST or RELEASE version picked from wrong repository metadata.xml
LATEST or RELEASE version picked from wrong repository metadata.xml
---
Key: MNG-4987
URL: http://jira.codehaus.org/browse/MNG-4987
Project: Maven 2 3
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0.2
Environment: Ubuntu 10.10
Reporter: Michael Hartmeier
In maven-aether-provider 3.0.2, DefaultVersionResolver, line 378ff says
{noformat}
private void merge( String key, MapString, VersionInfo infos, String
timestamp, String version,
ArtifactRepository repository )
{
VersionInfo info = infos.get( key );
if ( info == null )
{
info = new VersionInfo( timestamp, version, repository );
infos.put( key, info );
}
else if ( info.isOutdated( timestamp ) )
{
info.version = version;
info.repository = repository;
}
}
{noformat}
If I understand correctly, you should add
{noformat}
info.timestamp = timestamp
{noformat}
to the else part. Otherwise, you'll use a wrong timestamp in future calls to
this method.
--
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-4987) LATEST or RELEASE version picked from wrong repository metadata.xml
[
http://jira.codehaus.org/browse/MNG-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252188#action_252188
]
Michael Hartmeier commented on MNG-4987:
It probably not a major bug, but I don't see where I can change that now
LATEST or RELEASE version picked from wrong repository metadata.xml
---
Key: MNG-4987
URL: http://jira.codehaus.org/browse/MNG-4987
Project: Maven 2 3
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0.2
Environment: Ubuntu 10.10
Reporter: Michael Hartmeier
In maven-aether-provider 3.0.2, DefaultVersionResolver, line 378ff says
{noformat}
private void merge( String key, MapString, VersionInfo infos, String
timestamp, String version,
ArtifactRepository repository )
{
VersionInfo info = infos.get( key );
if ( info == null )
{
info = new VersionInfo( timestamp, version, repository );
infos.put( key, info );
}
else if ( info.isOutdated( timestamp ) )
{
info.version = version;
info.repository = repository;
}
}
{noformat}
If I understand correctly, you should add
{noformat}
info.timestamp = timestamp
{noformat}
to the else part. Otherwise, you'll use a wrong timestamp in future calls to
this method.
--
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: (MANTTASKS-210) When creating path objects using the dependencies task it is not possible to filter out artifacts by type.
When creating path objects using the dependencies task it is not possible to filter out artifacts by type. -- Key: MANTTASKS-210 URL: http://jira.codehaus.org/browse/MANTTASKS-210 Project: Maven 2.x Ant Tasks Issue Type: Improvement Components: dependencies task Affects Versions: 2.1.1 Reporter: Stephen Connolly Priority: Minor If you reference an object of type pom and pull its dependencies into a path object, the resulting path will contain the pom files which java then presumes to be malformed zip files. If you use type=jar then it will not resolve the dependencies of the pom artifact at all, so you need to have type=jar,pom to get the dependencies of the packaging pom artifact. What is needed is a separate pathType attribute to allow retrieving the full set of dependencies into the fileset, while selecting a subset for the path object. -- 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: (MANTTASKS-210) When creating path objects using the dependencies task it is not possible to filter out artifacts by type.
[ http://jira.codehaus.org/browse/MANTTASKS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly closed MANTTASKS-210. -- Resolution: Fixed Fix Version/s: 2.1.2 r1061291. When creating path objects using the dependencies task it is not possible to filter out artifacts by type. -- Key: MANTTASKS-210 URL: http://jira.codehaus.org/browse/MANTTASKS-210 Project: Maven 2.x Ant Tasks Issue Type: Improvement Components: dependencies task Affects Versions: 2.1.1 Reporter: Stephen Connolly Priority: Minor Fix For: 2.1.2 If you reference an object of type pom and pull its dependencies into a path object, the resulting path will contain the pom files which java then presumes to be malformed zip files. If you use type=jar then it will not resolve the dependencies of the pom artifact at all, so you need to have type=jar,pom to get the dependencies of the packaging pom artifact. What is needed is a separate pathType attribute to allow retrieving the full set of dependencies into the fileset, while selecting a subset for the path object. -- 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-543) links to modules where not working if modules are builded with --no-recursive (see continuum)
[ http://jira.codehaus.org/browse/MSITE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252192#action_252192 ] Luca commented on MSITE-543: it seems that with 2.3-SNAPSHOT not wotks in both cases: with and without recursion mvn -N clean install site-deploy -Dsite.deploy.url=file:///home/luca/Work/egov/trash/regression/javadoc/site2 mvn clean package site-deploy -Dsite.deploy.url=file:///home/luca/Work/egov/trash/regression/javadoc/site1 testcase attached links to modules where not working if modules are builded with --no-recursive (see continuum) - Key: MSITE-543 URL: http://jira.codehaus.org/browse/MSITE-543 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0-beta-4, 2.0-beta-5, 2.0-beta-6 Reporter: Luca Attachments: site-issue.tgz I've to place the modules into a separate directory: root/ ..pom.xml ..modules/ module1 module2 this is supported by maven through modules modulemodules/module1/module modulemodules/module2/module /modules in pom. but the site generation seems to be broken: if mvn site-deploy is used the links to the modules contain modules/module1/index.html which is ok but unfortunately the generated site structure will be generated as follows: root/ ..module1 ..module2 The result is that the links do not work. If I run mvn site-stage everything looks ok. The links doesn't contain modules dir anymore and eveything is working. -- 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: (MSITE-543) links to modules where not working if modules are builded with --no-recursive (see continuum)
[ http://jira.codehaus.org/browse/MSITE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca updated MSITE-543: --- Attachment: site-issue.tgz links to modules where not working if modules are builded with --no-recursive (see continuum) - Key: MSITE-543 URL: http://jira.codehaus.org/browse/MSITE-543 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0-beta-4, 2.0-beta-5, 2.0-beta-6 Reporter: Luca Attachments: site-issue.tgz I've to place the modules into a separate directory: root/ ..pom.xml ..modules/ module1 module2 this is supported by maven through modules modulemodules/module1/module modulemodules/module2/module /modules in pom. but the site generation seems to be broken: if mvn site-deploy is used the links to the modules contain modules/module1/index.html which is ok but unfortunately the generated site structure will be generated as follows: root/ ..module1 ..module2 The result is that the links do not work. If I run mvn site-stage everything looks ok. The links doesn't contain modules dir anymore and eveything is working. -- 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-260) Detail display doesn't work if there are tests with the same name
[ http://jira.codehaus.org/browse/SUREFIRE-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-260. --- Resolution: Fixed Fix Version/s: 2.7.2 Assignee: Kristian Rosenvold Fixed in r1061306 Detail display doesn't work if there are tests with the same name - Key: SUREFIRE-260 URL: http://jira.codehaus.org/browse/SUREFIRE-260 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin Affects Versions: 2.0 Report Plugin Reporter: Carlos Sanchez Assignee: Kristian Rosenvold Fix For: 2.7.2, Backlog toggleDisplay uses only the name of the test method for identifying the tests, it should use the full class name+method name -- 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: (MANTTASKS-211) Support launching Maven 3.x from the mvn task
Support launching Maven 3.x from the mvn task - Key: MANTTASKS-211 URL: http://jira.codehaus.org/browse/MANTTASKS-211 Project: Maven 2.x Ant Tasks Issue Type: Improvement Components: mvn task Affects Versions: 2.1.1 Reporter: Stephen Connolly The mvn task cannot launch maven 3.0.x as the list of dependencies is not complete if resolving from maven-core only. Resolving from apache-maven will give the correct list of dependencies now that MANTTASKS-210 allows path object filtering. -- 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: (MSITE-545) ArrayIndexOutOfBoundsException Generating Project Team report.
ArrayIndexOutOfBoundsException Generating Project Team report.
Key: MSITE-545
URL: http://jira.codehaus.org/browse/MSITE-545
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_23
Java home: C:\Program Files\Java\jdk1.6.0_23\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows vista version: 6.0 arch: amd64 Family: windows
Reporter: Gary Gregory
Attachments: pom.xml
Building Apache Commons Codec with the attached POM I get an
ArrayIndexOutOfBoundsException:
{noformat}
[INFO] Generating Project Team report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance
and no SinkFactory available. Please update this plugin.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] 1
[INFO]
[INFO] Trace
java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791)
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableHeaderCell(XhtmlSink.java:777)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeaderCell(AbstractMavenReportRenderer.java:267)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeader(AbstractMavenReportRenderer.java:356)
at
org.apache.maven.report.projectinfo.TeamListReport$TeamListRenderer.renderBody(TeamListReport.java:165)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.TeamListReport.executeReport(TeamListReport.java:60)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
The attached POM is based on r. 1061085
--
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: (MANTTASKS-211) Support launching Maven 3.x from the mvn task
[ http://jira.codehaus.org/browse/MANTTASKS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly closed MANTTASKS-211. -- Resolution: Fixed Fix Version/s: 2.1.2 r1061312. Support launching Maven 3.x from the mvn task - Key: MANTTASKS-211 URL: http://jira.codehaus.org/browse/MANTTASKS-211 Project: Maven 2.x Ant Tasks Issue Type: Improvement Components: mvn task Affects Versions: 2.1.1 Reporter: Stephen Connolly Assignee: Stephen Connolly Fix For: 2.1.2 The mvn task cannot launch maven 3.0.x as the list of dependencies is not complete if resolving from maven-core only. Resolving from apache-maven will give the correct list of dependencies now that MANTTASKS-210 allows path object filtering. -- 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: (MSITE-545) ArrayIndexOutOfBoundsException Generating Project Team report.
[
http://jira.codehaus.org/browse/MSITE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed MSITE-545.
--
Resolution: Not A Bug
ArrayIndexOutOfBoundsException Generating Project Team report.
Key: MSITE-545
URL: http://jira.codehaus.org/browse/MSITE-545
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_23
Java home: C:\Program Files\Java\jdk1.6.0_23\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows vista version: 6.0 arch: amd64 Family: windows
Reporter: Gary Gregory
Attachments: pom.xml
Building Apache Commons Codec with the attached POM I get an
ArrayIndexOutOfBoundsException:
{noformat}
[INFO] Generating Project Team report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] 1
[INFO]
[INFO] Trace
java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791)
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableHeaderCell(XhtmlSink.java:777)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeaderCell(AbstractMavenReportRenderer.java:267)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeader(AbstractMavenReportRenderer.java:356)
at
org.apache.maven.report.projectinfo.TeamListReport$TeamListRenderer.renderBody(TeamListReport.java:165)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.TeamListReport.executeReport(TeamListReport.java:60)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
The attached POM is based on r. 1061085
--
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:
[jira] Commented: (MSITE-545) ArrayIndexOutOfBoundsException Generating Project Team report.
[
http://jira.codehaus.org/browse/MSITE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252202#action_252202
]
Gary Gregory commented on MSITE-545:
Hm, sorry, I filed this against the wrong project. Should be with MPIR.
ArrayIndexOutOfBoundsException Generating Project Team report.
Key: MSITE-545
URL: http://jira.codehaus.org/browse/MSITE-545
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_23
Java home: C:\Program Files\Java\jdk1.6.0_23\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows vista version: 6.0 arch: amd64 Family: windows
Reporter: Gary Gregory
Attachments: pom.xml
Building Apache Commons Codec with the attached POM I get an
ArrayIndexOutOfBoundsException:
{noformat}
[INFO] Generating Project Team report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] 1
[INFO]
[INFO] Trace
java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791)
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableHeaderCell(XhtmlSink.java:777)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeaderCell(AbstractMavenReportRenderer.java:267)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeader(AbstractMavenReportRenderer.java:356)
at
org.apache.maven.report.projectinfo.TeamListReport$TeamListRenderer.renderBody(TeamListReport.java:165)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.TeamListReport.executeReport(TeamListReport.java:60)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
The attached POM is based on r. 1061085
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
[jira] Updated: (SUREFIRE-260) Detail display doesn't work if there are tests with the same name
[ http://jira.codehaus.org/browse/SUREFIRE-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-260: Fix Version/s: (was: Backlog) Detail display doesn't work if there are tests with the same name - Key: SUREFIRE-260 URL: http://jira.codehaus.org/browse/SUREFIRE-260 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin Affects Versions: 2.0 Report Plugin Reporter: Carlos Sanchez Assignee: Kristian Rosenvold Fix For: 2.7.2 toggleDisplay uses only the name of the test method for identifying the tests, it should use the full class name+method name -- 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-329) Support for JUNIT extensions
[ http://jira.codehaus.org/browse/SUREFIRE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252215#action_252215 ] Timothy Mecklem commented on SUREFIRE-329: -- This would help us immensely to distinguish between the tests we want to run during local builds and those we want to execute during integrations which are slower. Please include this feature. Support for JUNIT extensions Key: SUREFIRE-329 URL: http://jira.codehaus.org/browse/SUREFIRE-329 Project: Maven Surefire Issue Type: Wish Components: Junit 4.x support Reporter: Anuj Kathuria Fix For: Backlog Is there any plan to support using JUNIT extensions such as @Category,@PreRequisite with Maven2 SureFire plugin? The JUNIT EXTENSION URL: http://www.junitext.org/ We would like to specify the categories to run via a configurable option in the maven surefire plugin that supports JUNIT extensions See example Java Code: The following runs only tests with Category - Z. //In JUnit4 JUnitCore core = new JUnitCore(); // use for categories special listener, give some statistics core.addListener(new CategoryTextListener(System.out)); Request req = Request.aClass(SpcfTest.class); core.run(req.filterWith(new CategoryFilter(Z))); -- 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-686) maven reported BUILD FAILURE even if all tests passed
[ http://jira.codehaus.org/browse/SUREFIRE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252226#action_252226 ] Kristian Rosenvold commented on SUREFIRE-686: - Just by grepping through the jacob source code I see myriads of System.exit calls. I suggest you file this as an issue against jacob maven reported BUILD FAILURE even if all tests passed --- Key: SUREFIRE-686 URL: http://jira.codehaus.org/browse/SUREFIRE-686 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.7.1 Environment: windows 2003 zh_CN jdk 1.5.0_07 maven 2.2.1, 3.0.1, 3.0.2 Reporter: panxiaobo Attachments: build-output-2.7.2.txt, build-output.txt I tried to build a project with maven, the project contains junit test. maven reported BUILD FAILURE even if all tests passed. maven output: = Results : Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. = one of the tests is using jacob 1.14.3 to instance a COM, and after deleting the test, maven build successfully. more detail output are attached -- 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-686) maven reported BUILD FAILURE even if all tests passed
[ http://jira.codehaus.org/browse/SUREFIRE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-686. --- Resolution: Won't Fix Assignee: Kristian Rosenvold Since it is generally considered extremely bad practice to terminate the vm like that, I am closing this issue as won't fix. Issue should be handled in jacob project. maven reported BUILD FAILURE even if all tests passed --- Key: SUREFIRE-686 URL: http://jira.codehaus.org/browse/SUREFIRE-686 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.7.1 Environment: windows 2003 zh_CN jdk 1.5.0_07 maven 2.2.1, 3.0.1, 3.0.2 Reporter: panxiaobo Assignee: Kristian Rosenvold Attachments: build-output-2.7.2.txt, build-output.txt I tried to build a project with maven, the project contains junit test. maven reported BUILD FAILURE even if all tests passed. maven output: = Results : Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. = one of the tests is using jacob 1.14.3 to instance a COM, and after deleting the test, maven build successfully. more detail output are attached -- 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: (MDEP-299) dependency:get -DrepositoryUrl is mentioned wrong in help
dependency:get -DrepositoryUrl is mentioned wrong in help - Key: MDEP-299 URL: http://jira.codehaus.org/browse/MDEP-299 Project: Maven 2.x Dependency Plugin Issue Type: Bug Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) Reporter: goerge Assignee: Brian Fox Priority: Minor dependency:get -DrepositoryUrl doesn't work as mentioned in dependency:help -Ddetail=true -Dgoal=get. What actually work is parameter repoUrl but in help is mentioned parameter repositoryUrl. Solution: simply rename parameter or update help to be consistent. -- 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-545) ArrayIndexOutOfBoundsException Generating Project Team report.
[
http://jira.codehaus.org/browse/MSITE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252240#action_252240
]
Lukas Theussl commented on MSITE-545:
-
For the record: latest pir plugin requires site-plugin = 2.1
ArrayIndexOutOfBoundsException Generating Project Team report.
Key: MSITE-545
URL: http://jira.codehaus.org/browse/MSITE-545
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_23
Java home: C:\Program Files\Java\jdk1.6.0_23\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows vista version: 6.0 arch: amd64 Family: windows
Reporter: Gary Gregory
Attachments: pom.xml
Building Apache Commons Codec with the attached POM I get an
ArrayIndexOutOfBoundsException:
{noformat}
[INFO] Generating Project Team report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] 1
[INFO]
[INFO] Trace
java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791)
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableHeaderCell(XhtmlSink.java:777)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeaderCell(AbstractMavenReportRenderer.java:267)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeader(AbstractMavenReportRenderer.java:356)
at
org.apache.maven.report.projectinfo.TeamListReport$TeamListRenderer.renderBody(TeamListReport.java:165)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.TeamListReport.executeReport(TeamListReport.java:60)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
The attached POM is based on r. 1061085
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
[jira] Commented: (MSITE-543) links to modules where not working if modules are builded with --no-recursive (see continuum)
[ http://jira.codehaus.org/browse/MSITE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252242#action_252242 ] Lukas Theussl commented on MSITE-543: - I don't see a url element in any of your poms. In a multi-module site build, these are essential, see this [faq|http://maven.apache.org/plugins/maven-site-plugin/faq.html#Use_of_url]. See also MSITE-535. links to modules where not working if modules are builded with --no-recursive (see continuum) - Key: MSITE-543 URL: http://jira.codehaus.org/browse/MSITE-543 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0-beta-4, 2.0-beta-5, 2.0-beta-6 Reporter: Luca Attachments: site-issue.tgz I've to place the modules into a separate directory: root/ ..pom.xml ..modules/ module1 module2 this is supported by maven through modules modulemodules/module1/module modulemodules/module2/module /modules in pom. but the site generation seems to be broken: if mvn site-deploy is used the links to the modules contain modules/module1/index.html which is ok but unfortunately the generated site structure will be generated as follows: root/ ..module1 ..module2 The result is that the links do not work. If I run mvn site-stage everything looks ok. The links doesn't contain modules dir anymore and eveything is working. -- 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] Moved: (MPIR-218) ArrayIndexOutOfBoundsException Generating Project Team report.
[
http://jira.codehaus.org/browse/MPIR-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg moved MSITE-545 to MPIR-218:
Affects Version/s: (was: 2.2)
Key: MPIR-218 (was: MSITE-545)
Project: Maven 2.x Project Info Reports Plugin (was: Maven 2.x
and 3.x Site Plugin)
ArrayIndexOutOfBoundsException Generating Project Team report.
Key: MPIR-218
URL: http://jira.codehaus.org/browse/MPIR-218
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_23
Java home: C:\Program Files\Java\jdk1.6.0_23\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows vista version: 6.0 arch: amd64 Family: windows
Reporter: Gary Gregory
Attachments: pom.xml
Building Apache Commons Codec with the attached POM I get an
ArrayIndexOutOfBoundsException:
{noformat}
[INFO] Generating Project Team report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] 1
[INFO]
[INFO] Trace
java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791)
at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableHeaderCell(XhtmlSink.java:777)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeaderCell(AbstractMavenReportRenderer.java:267)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeader(AbstractMavenReportRenderer.java:356)
at
org.apache.maven.report.projectinfo.TeamListReport$TeamListRenderer.renderBody(TeamListReport.java:165)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.TeamListReport.executeReport(TeamListReport.java:60)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
The attached POM is based on r. 1061085
--
This message is automatically generated by JIRA.
-
If you think
[jira] Closed: (SUREFIRE-319) skiptrue/skip cannot be overridden using mvn -Dmaven.test.skip=false test
[ http://jira.codehaus.org/browse/SUREFIRE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-319. --- Resolution: Fixed Fix Version/s: (was: Backlog) 2.7.2 Assignee: Kristian Rosenvold Fixed with a documentation update in r1061478. WIll appear at http://maven.apache.org/plugins/maven-surefire-plugin/examples/skipping-test.html once 2.7.2 is released, in the mean time it can be seen here http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/skipping-test.apt.vm?view=markup skiptrue/skip cannot be overridden using mvn -Dmaven.test.skip=false test - Key: SUREFIRE-319 URL: http://jira.codehaus.org/browse/SUREFIRE-319 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Environment: java version 1.5.0_09 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode) Reporter: Graham Leggett Assignee: Kristian Rosenvold Fix For: 2.7.2 If the pom file is configured to skip tests using skiptrue/skip, and an attempt is made to override this on the command line using mvn -Dmaven.test.skip=false test, the attempt does not work (the test is still skipped). In theory, the command line flag should override the pom setting. -- 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-682) skipTests cannot be overridden by commandline param
[ http://jira.codehaus.org/browse/SUREFIRE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-682. --- Resolution: Fixed Fix Version/s: 2.7.2 Assignee: Kristian Rosenvold Fixed with a documentation update in r1061478. WIll appear at http://maven.apache.org/plugins/maven-surefire-plugin/examples/skipping-test.html once 2.7.2 is released, in the mean time it can be seen here http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/skipping-test.apt.vm?view=markup skipTests cannot be overridden by commandline param - Key: SUREFIRE-682 URL: http://jira.codehaus.org/browse/SUREFIRE-682 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.7.1 Reporter: Julien HENRY Assignee: Kristian Rosenvold Fix For: 2.7.2 This issue is very similar to SUREFIRE-319 When skipTests is defined in the pom, there is no way to override the value using -DskipTests or -DskipTests=true|false on the command line. I think it would be better if command line parameter could have higher priority over pom configuration. -- 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-602) Unable to run tests using a different JVM unless using forkMode=once (always and pertest do not work)
[ http://jira.codehaus.org/browse/SUREFIRE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-602. --- Resolution: Cannot Reproduce Assignee: Kristian Rosenvold I have tried verifying this issue with both surefire 2.4.3 and 2.7.1. The forking of the jvm works as advertised in all cases I am able to reproduce, and I am able to do so regardless of forkmode. Please note that forkMode=once and forkMode=always may cause classes to be loaded in different order (for once), which may cause different behaviour, which may be the real source of this issue. Feel free to reopen this issue if any substantial additional information is available. Unable to run tests using a different JVM unless using forkMode=once (always and pertest do not work) --- Key: SUREFIRE-602 URL: http://jira.codehaus.org/browse/SUREFIRE-602 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.4.3 Environment: Maven version: 2.0.10 Java version: 1.5.0_08 OS name: windows xp version: 5.1 arch: x86 Family: windows Reporter: Richard Chamberlain Assignee: Kristian Rosenvold Hi, Our build farm uses java 1.5.0_08. We have written some code in java 6. We can get it to compile in java 6, but running tests wasn't that easy. We originally set the config to: plugin artifactIdmaven-surefire-plugin/artifactId version2.4.3/version configuration redirectTestOutputToFiletrue/redirectTestOutputToFile jvmD:\buildTools\jdk\1.6.0\bin\java.exe/jvm forkModepertest/forkMode includes include**/*Behavior.java/include /includes /configuration /plugin But this didn't work reporting a bad version in class file error. When we set forkMode to once, it worked. After further investigation - the jvm property is only picked up when forkMode is once - it does not work when forkmode is pertest or always This was extremely painful to work out what the bug was. Can I also suggest that you print out the JVM version and any parameters in the debug (mvn -X) output? Thanks, Richard -- 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: (MSHARED-179) FilteringUtils.escapeWindowsPath only works if the Windows path is at the beginning of a property
[
http://jira.codehaus.org/browse/MSHARED-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSHARED-179.
---
Resolution: Fixed
Fix Version/s: maven-filtering-1.0
Assignee: Dennis Lundberg
Fixed in [r1061510|http://svn.apache.org/viewvc?view=revisionrevision=1061510].
FilteringUtils.escapeWindowsPath only works if the Windows path is at the
beginning of a property
-
Key: MSHARED-179
URL: http://jira.codehaus.org/browse/MSHARED-179
Project: Maven Shared Components
Issue Type: Bug
Components: maven-filtering
Affects Versions: maven-filtering-1.0-beta-4
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
Fix For: maven-filtering-1.0
Attachments: MSHARED-179.patch, MSHARED-179.zip
If the Windows path is in the middle, like in a JDBC URL escaping is not
done. Here's the code from FilteringUtils.java that causes it:
{code:java}
public static final String escapeWindowsPath( String val )
{
if ( !StringUtils.isEmpty( val ) val.indexOf( :\\ ) == 1 )
...
{code}
--
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-4988) API to calculate execution plan without full mojo execution configuration
API to calculate execution plan without full mojo execution configuration - Key: MNG-4988 URL: http://jira.codehaus.org/browse/MNG-4988 Project: Maven 2 3 Issue Type: Improvement Components: Embedding Affects Versions: 3.0 Reporter: Igor Fedorenko Attachments: MNGECLIPSE-2724.diff m2e uses project execution plan to determine how to configure the project in eclipse workspace and what to do during workbench build. Not all mojo execution bound to execution plan are relevant for this (think enforcer or deploy plugin), so m2e needs an API to analyse execution plan and perform full configuration of interesting mojo execution only. Original m2e jira https://issues.sonatype.org/browse/MNGECLIPSE-2724 Proposed patch attached. -- 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: (MNG-4988) API to calculate execution plan without full mojo execution configuration
[ http://jira.codehaus.org/browse/MNG-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko updated MNG-4988: Attachment: MNGECLIPSE-2724.diff revised patch that fixes unit test failures API to calculate execution plan without full mojo execution configuration - Key: MNG-4988 URL: http://jira.codehaus.org/browse/MNG-4988 Project: Maven 2 3 Issue Type: Improvement Components: Embedding Affects Versions: 3.0 Reporter: Igor Fedorenko Attachments: MNGECLIPSE-2724.diff, MNGECLIPSE-2724.diff m2e uses project execution plan to determine how to configure the project in eclipse workspace and what to do during workbench build. Not all mojo execution bound to execution plan are relevant for this (think enforcer or deploy plugin), so m2e needs an API to analyse execution plan and perform full configuration of interesting mojo execution only. Original m2e jira https://issues.sonatype.org/browse/MNGECLIPSE-2724 Proposed patch attached. -- 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: (SCM-596) Implements List command for mercurial provider
[ http://jira.codehaus.org/browse/SCM-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-596: - Fix Version/s: 1.5 Assignee: Olivier Lamy Implements List command for mercurial provider -- Key: SCM-596 URL: http://jira.codehaus.org/browse/SCM-596 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-mercurial (hg) Affects Versions: 1.4 Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 1.5 -- 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: (SCM-596) Implements List command for mercurial provider
Implements List command for mercurial provider -- Key: SCM-596 URL: http://jira.codehaus.org/browse/SCM-596 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-mercurial (hg) Affects Versions: 1.4 Reporter: Olivier Lamy -- 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: (MASSEMBLY-516) Error in Example for sharing-descriptors?
[ http://jira.codehaus.org/browse/MASSEMBLY-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252278#action_252278 ] Jeff Campbell commented on MASSEMBLY-516: - It is also important to note that the descriptor xml file MUST be in /src/main/resources/assemblies (not /src/main/resources/assembly). It seems that half the maven-assembly-plugin documentation indicates that assembly xml files should go in either: /src/main/resources/assembly or /src/main/resources/assemblies I wish there was a better defined standard and that the documentation would be consistent. It might be good to add to this fix the ability to look in either of these to paths for the descriptor xml file. Error in Example for sharing-descriptors? - Key: MASSEMBLY-516 URL: http://jira.codehaus.org/browse/MASSEMBLY-516 Project: Maven 2.x Assembly Plugin Issue Type: Bug Environment: - Reporter: Knut Pape Assignee: John Casey Fix For: 2.3 On Page http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html It says that the assembly file from a jar on the class-path shoulld be included the following way: descriptors descriptormyassembly.xml/descriptor /descriptors This didn't work for me. After some fidling (I'm pritty sure that the problem was not a spelling mistake) I came to the following solution: Instead of referencing the assembly by filename I referenced it by it's ID and voila - it worked: descriptorRefs descriptorRefmy-assembly-descriptor-id/descriptorRef /descriptorRefs -- 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-4988) API to calculate execution plan without full mojo execution configuration
[ http://jira.codehaus.org/browse/MNG-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252281#action_252281 ] Benjamin Bentmann commented on MNG-4988: Looks good, go ahead. API to calculate execution plan without full mojo execution configuration - Key: MNG-4988 URL: http://jira.codehaus.org/browse/MNG-4988 Project: Maven 2 3 Issue Type: Improvement Components: Embedding Affects Versions: 3.0 Reporter: Igor Fedorenko Attachments: MNGECLIPSE-2724.diff, MNGECLIPSE-2724.diff m2e uses project execution plan to determine how to configure the project in eclipse workspace and what to do during workbench build. Not all mojo execution bound to execution plan are relevant for this (think enforcer or deploy plugin), so m2e needs an API to analyse execution plan and perform full configuration of interesting mojo execution only. Original m2e jira https://issues.sonatype.org/browse/MNGECLIPSE-2724 Proposed patch attached. -- 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: (SCM-596) Implements List command for mercurial provider
[ http://jira.codehaus.org/browse/SCM-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-596. Resolution: Fixed fixed rev 1061548. Implements List command for mercurial provider -- Key: SCM-596 URL: http://jira.codehaus.org/browse/SCM-596 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-mercurial (hg) Affects Versions: 1.4 Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 1.5 -- 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: (MASSEMBLY-516) Error in Example for sharing-descriptors?
[ http://jira.codehaus.org/browse/MASSEMBLY-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252283#action_252283 ] Dennis Lundberg commented on MASSEMBLY-516: --- Jeff, Where in the docs does it say you should use /src/main/resources/assembly ? I can't find any reference to that. Error in Example for sharing-descriptors? - Key: MASSEMBLY-516 URL: http://jira.codehaus.org/browse/MASSEMBLY-516 Project: Maven 2.x Assembly Plugin Issue Type: Bug Environment: - Reporter: Knut Pape Assignee: John Casey Fix For: 2.3 On Page http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html It says that the assembly file from a jar on the class-path shoulld be included the following way: descriptors descriptormyassembly.xml/descriptor /descriptors This didn't work for me. After some fidling (I'm pritty sure that the problem was not a spelling mistake) I came to the following solution: Instead of referencing the assembly by filename I referenced it by it's ID and voila - it worked: descriptorRefs descriptorRefmy-assembly-descriptor-id/descriptorRef /descriptorRefs -- 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: (ARCHETYPE-258) Support excluding files from to-be-created archetype
[ http://jira.codehaus.org/browse/ARCHETYPE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252286#action_252286 ] Ryan Connolly commented on ARCHETYPE-258: - Jordan: Just curious why you opted to fork this instead of contributing a patch to this project? Support excluding files from to-be-created archetype Key: ARCHETYPE-258 URL: http://jira.codehaus.org/browse/ARCHETYPE-258 Project: Maven Archetype Issue Type: Wish Components: Creator Affects Versions: 2.0-alpha-4 Reporter: Stevo Slavic Please support configuration option for archetype:create-from-project mojo to exclude ((eclipse) IDE specific) files and directories (like .project, .classpath, .settings, .svn) when creating an archetype. -- 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: (MNG-4988) API to calculate execution plan without full mojo execution configuration
[ http://jira.codehaus.org/browse/MNG-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko closed MNG-4988. --- Resolution: Fixed Fix Version/s: 3.0.3 Committed revised patch. http://svn.apache.org/viewvc?view=revisionrevision=1061589 API to calculate execution plan without full mojo execution configuration - Key: MNG-4988 URL: http://jira.codehaus.org/browse/MNG-4988 Project: Maven 2 3 Issue Type: Improvement Components: Embedding Affects Versions: 3.0 Reporter: Igor Fedorenko Assignee: Igor Fedorenko Fix For: 3.0.3 Attachments: MNGECLIPSE-2724.diff, MNGECLIPSE-2724.diff m2e uses project execution plan to determine how to configure the project in eclipse workspace and what to do during workbench build. Not all mojo execution bound to execution plan are relevant for this (think enforcer or deploy plugin), so m2e needs an API to analyse execution plan and perform full configuration of interesting mojo execution only. Original m2e jira https://issues.sonatype.org/browse/MNGECLIPSE-2724 Proposed patch attached. -- 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-4989) Properties defined in settings.xml not being passed to dependent project dependency classifiers
Properties defined in settings.xml not being passed to dependent project
dependency classifiers
---
Key: MNG-4989
URL: http://jira.codehaus.org/browse/MNG-4989
Project: Maven 2 3
Issue Type: Bug
Components: Dependencies, Inheritance and Interpolation, Profiles
Affects Versions: 3.0
Environment: Apache Maven 3.0 (r1004208; 2010-10-05 00:50:56+1300)
Java version: 1.6.0_22
Java home: C:\Program Files\Java\jdk1.6.0_22\jre
Default locale: en_NZ, platform encoding: Cp1252
OS name: windows 7 version: 6.1 arch: amd64 Family: windows
Reporter: Gynn Rickerby
Given the following projects and dependencies:
Project A - Project B - Project C
If Project B defines:
dependency
groupIdProjectC/groupId
artifactProjectC/artifact
version1.0/version
classifier${target.classifier}/classifier
/dependency
And the settings.xml contains:
profile
...
properties
target.classifiersomeclassifier/target.classifier
/properties
...
/profile
Where the profile in question is the active profile.
Project B will build fine.
Project A will fail, with:
Failure to find ProjectC:ProjectC:${target.classifier}:1.0
--
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-597) NPE in AccuRev provider changelog
[ http://jira.codehaus.org/browse/SCM-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252300#action_252300 ] Grant Gardner commented on SCM-597: --- will work on a patch this w/e NPE in AccuRev provider changelog - Key: SCM-597 URL: http://jira.codehaus.org/browse/SCM-597 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-accurev Affects Versions: 1.4 Reporter: Grant Gardner org.apache.maven.lifecycle.LifecycleExecutionException: Cannot run changelog command : at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot run changelog command : at org.apache.maven.scm.plugin.ChangeLogMojo.execute(ChangeLogMojo.java:129) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63) at org.apache.maven.scm.provider.accurev.command.changelog.AccuRevChangeLogCommand.changelog(AccuRevChangeLogCommand.java:419) at org.apache.maven.scm.provider.accurev.AccuRevScmProvider.changelog(AccuRevScmProvider.java:390) at org.apache.maven.scm.provider.AbstractScmProvider.changeLog(AbstractScmProvider.java:250) at org.apache.maven.scm.plugin.ChangeLogMojo.execute(ChangeLogMojo.java:106) ... 19 more Caused by: java.lang.NullPointerException at org.apache.maven.scm.provider.accurev.command.changelog.AccuRevChangeLogCommand.getChangeLog(AccuRevChangeLogCommand.java:406) at org.apache.maven.scm.provider.accurev.command.changelog.AccuRevChangeLogCommand.executeAccurevCommand(AccuRevChangeLogCommand.java:269) at org.apache.maven.scm.provider.accurev.command.AbstractAccuRevCommand.executeCommand(AbstractAccuRevCommand.java:66) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) ... 23 more -- 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: (SCM-597) NPE in AccuRev provider changelog
NPE in AccuRev provider changelog - Key: SCM-597 URL: http://jira.codehaus.org/browse/SCM-597 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-accurev Affects Versions: 1.4 Reporter: Grant Gardner org.apache.maven.lifecycle.LifecycleExecutionException: Cannot run changelog command : at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot run changelog command : at org.apache.maven.scm.plugin.ChangeLogMojo.execute(ChangeLogMojo.java:129) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63) at org.apache.maven.scm.provider.accurev.command.changelog.AccuRevChangeLogCommand.changelog(AccuRevChangeLogCommand.java:419) at org.apache.maven.scm.provider.accurev.AccuRevScmProvider.changelog(AccuRevScmProvider.java:390) at org.apache.maven.scm.provider.AbstractScmProvider.changeLog(AbstractScmProvider.java:250) at org.apache.maven.scm.plugin.ChangeLogMojo.execute(ChangeLogMojo.java:106) ... 19 more Caused by: java.lang.NullPointerException at org.apache.maven.scm.provider.accurev.command.changelog.AccuRevChangeLogCommand.getChangeLog(AccuRevChangeLogCommand.java:406) at org.apache.maven.scm.provider.accurev.command.changelog.AccuRevChangeLogCommand.executeAccurevCommand(AccuRevChangeLogCommand.java:269) at org.apache.maven.scm.provider.accurev.command.AbstractAccuRevCommand.executeCommand(AbstractAccuRevCommand.java:66) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) ... 23 more -- 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
