[jira] Created: (MEV-644) xerces:xercesImpl is missing verisons greater than 2.8.0 in metadata
xerces:xercesImpl is missing verisons greater than 2.8.0 in metadata Key: MEV-644 URL: http://jira.codehaus.org/browse/MEV-644 Project: Maven Evangelism Issue Type: Bug Components: Invalid Metadata Reporter: Karla Jacobsen The maven-metadata.xml for xerces:xercesImpl is missing versions 2.8.1, 2.9.0, and 2.9.1. As a side note, this was a very difficult issue to decode for a newbie. It would be very helpful to have more documentation, or better error messages to indicate that bad metadata could be the cause of resolve problems. I was seeing the problem when trying to use a range of versions, or when specifying a constrained range (e.g. [2.8.1,) or [2.8.1]). My build succeeded when I just used 2.8.1, so it took me quite a while to figure out why. In case it is helpful...I was running a build using the Ant Maven task 'dependencies' and the following pom.xml: 4.0.0 com.mycompany example 1.1.1 xerces xercesImpl [2.8.1,2.9.1] xalan xalan [2.7.0,2.7.1] Here is the relevant Ant output (when running in verbose mode): [artifact:pom] Loading Maven settings file: C:\bin\apache-maven-2.0.9\conf\settings.xml [available] Found: .pom.xml -resolve-compile-dependencies: [artifact:dependencies] Loading Maven settings file: C:\bin\apache-maven-2.0.9\conf\settings.xml [artifact:dependencies] Maven Ant Tasks version: 2.0.10 [artifact:dependencies] Using local repository: C:\Documents and Settings\kjacobse\.m2\repository [artifact:dependencies] Resolving dependencies... [artifact:dependencies] Using remote repositories: - id=enterprise.mvn.repository, url=file:///V:/depot/maven, releases=enabled, snapshots=enabled - id=central, url=http://localhost:8081/nexus/content/repositories/MavenProxy/, releases=enabled, snapshots=disabled com.mycompany:example:jar:1.1.1 (selected) [artifact:dependencies] [INFO] artifact xerces:xercesImpl: checking for updates from enterprise.mvn.repository [artifact:dependencies] [INFO] artifact xerces:xercesImpl: checking for updates from central [artifact:dependencies] An error has occurred while processing the Maven artifact tasks. [artifact:dependencies] Diagnosis: [artifact:dependencies] [artifact:dependencies] Unable to resolve artifact: Couldn't find a version in [2.0.0, 2.0.2, 2.2.1, 2.3.0, 2.4.0, 2.5.0, 2.6.0, 2.6.1, 2.6.2, 2.7.1, 2.8.0] to match range [2.8.1,2.9.1] [artifact:dependencies] xerces:xercesImpl:jar:null [artifact:dependencies] [artifact:dependencies] from the specified remote repositories: [artifact:dependencies] enterprise.mvn.repository (file:///V:/depot/maven), [artifact:dependencies] central (http://localhost:8081/nexus/content/repositories/MavenProxy/) [artifact:dependencies] [artifact:dependencies] Path to dependency: [artifact:dependencies] 1) com.mycompany:example:jar:1.1.1 [artifact:dependencies] [artifact:dependencies] [artifact:dependencies] BUILD FAILED C:\eclipse\eclipse-workspaces\eclipse-jee-galileo\galileo\build\super-build.xml:406: Unable to resolve artifact: Couldn't find a version in [2.0.0, 2.0.2, 2.2.1, 2.3.0, 2.4.0, 2.5.0, 2.6.0, 2.6.1, 2.6.2, 2.7.1, 2.8.0] to match range [2.8.1,2.9.1] xerces:xercesImpl:jar:null from the specified remote repositories: enterprise.mvn.repository (file:///V:/depot/maven), central (http://localhost:8081/nexus/content/repositories/MavenProxy/) Path to dependency: 1) com.mycompany:example:jar:1.1.1 at org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTask.java:175) at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtifactTask.java:678) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423) at org.eclipse.ant.internal.ui.antsupport.Internal
[jira] Created: (MJAVADOC-274) Regression in 2.6.1 - modules with no sources cause an error
Regression in 2.6.1 - modules with no sources cause an error Key: MJAVADOC-274 URL: http://jira.codehaus.org/browse/MJAVADOC-274 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6.1 Reporter: Andrey Razumovsky After upgrading from 2.6 to 2.6.1 our Apache Cayenne builds got broken. The problem is in module with no public or protected sources (there's only a package-private class). Now, after infamous message "'org.apache.maven.plugins:maven-javadoc-plugin:2.6:javadoc' has not be previously called for the project ..." build fails and creates an error report. In the report: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in JavaDocs report generation: Exit code: 1 - javadoc: error - No public or protected classes found to document. Command line was: C:\Progra~1\Java\jdk1.6.0_13\jre\..\bin\javadoc.exe @options @packages Refer to the generated Javadoc files in 'C:\Project\cayenne-parent\framework\cayenne-jdk1.6-unpublished\target\site\apidocs' dir. -- 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-240) ignoreNonCompile not available for analyze-report
ignoreNonCompile not available for analyze-report - Key: MDEP-240 URL: http://jira.codehaus.org/browse/MDEP-240 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: analyze Affects Versions: 2.1 Reporter: Pablo Assignee: Brian Fox I'd like to use the property ignoreNonCompile=true for my site report, but the goal analyze-report doesn't have this property. The doc is pretty clear about it, but I don't see any reason of not having this option for reports too. http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html#ignoreNonCompile http://maven.apache.org/plugins/maven-dependency-plugin/analyze-report-mojo.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAVADOC-274) Regression in 2.6.1 - modules with no sources cause an error
[ http://jira.codehaus.org/browse/MJAVADOC-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197410#action_197410 ] Andrey Razumovsky commented on MJAVADOC-274: And one more thing. I'm not sure about the reason, but both in 2.6 and 2.6.1, when we try to disable this new feature by setting detectOfflineLinks=false, Maven build succeeds, but Hudson cannot publish JavaDoc. Seems like some docs were not properly built. See error at very end of log: http://hudson.zones.apache.org/hudson/job/Cayenne-trunk/jdk=JDK%201.5%20%28latest%29/28/console FATAL: /export/home/hudson/hudson/jobs/Cayenne-trunk/workspace/jdk/JDK 1.5 (latest)/trunk/framework/cayenne-jdk1.5-unpublished/target/site/apidocs not found. > Regression in 2.6.1 - modules with no sources cause an error > > > Key: MJAVADOC-274 > URL: http://jira.codehaus.org/browse/MJAVADOC-274 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6.1 >Reporter: Andrey Razumovsky > > After upgrading from 2.6 to 2.6.1 our Apache Cayenne builds got broken. The > problem is in module with no public or protected sources (there's only a > package-private class). Now, after infamous message > "'org.apache.maven.plugins:maven-javadoc-plugin:2.6:javadoc' has not be > previously called for the project ..." build fails and creates an error > report. In the report: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] An error has occurred in JavaDocs report generation: > Exit code: 1 - javadoc: error - No public or protected classes found to > document. > Command line was: C:\Progra~1\Java\jdk1.6.0_13\jre\..\bin\javadoc.exe > @options @packages > Refer to the generated Javadoc files in > 'C:\Project\cayenne-parent\framework\cayenne-jdk1.6-unpublished\target\site\apidocs' > dir. -- 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-4429) jspc plugin works in Maven 2.2.1, fails in 3.0
jspc plugin works in Maven 2.2.1, fails in 3.0 -- Key: MNG-4429 URL: http://jira.codehaus.org/browse/MNG-4429 Project: Maven 2 Issue Type: Bug Components: Plugin API Reporter: Dan Fabulich Attachments: jspcbug.zip, log.txt Consider the attached project, which uses org.codehaus.mojo.jspc:jspc-maven-plugin. The build passes on Maven 2.2.1, but fails in Maven 3.0-SNAPSHOT (r832897; 2009-11-04 15:16:21-0800) with an error message that I don't understand. It's quite possible that there's something wrong with the packaging for this plugin, but AFAIK it should continue to work in Maven 3. -- 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: (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[ http://jira.codehaus.org/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197430#action_197430 ] Harold Shinsato commented on MDEP-82: - Being able to go offline so all needed dependencies (including plugin dependencies) will work is something we have a requirement to do for our builds or it will be hard for us to get to use maven. Is there a workaround for this issue that would not require writing custom code? > go-offline / resolve-plugins does not resolve all plugin dependencies > - > > Key: MDEP-82 > URL: http://jira.codehaus.org/browse/MDEP-82 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: go-offline, resolve-plugins >Affects Versions: 2.0-alpha-4 > Environment: Maven 2.0.6 >Reporter: Arne Degenring >Assignee: Brian Fox > Attachments: pom.xml > > > The attached pom.xml is a very simple JAR project, without any direct > dependencies or plugin dependencies. > Start with an empty local repository, and run mvn dependency:go-offline on > it. Some files get downloaded, but not everything that is needed for the > build. If you run "mvn -o package" afterwards, you end up with the following > error: > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not > exist or no valid version could be found > Afterwards, even "mvn package" without the "-o" parameter does not work any > longer. -- 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
