[jira] (MPIR-268) Add Gradle dependency information
Michael Osipov created MPIR-268: --- Summary: Add Gradle dependency information Key: MPIR-268 URL: https://jira.codehaus.org/browse/MPIR-268 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: dependency-info Affects Versions: 2.6 Reporter: Michael Osipov The Dependency Information report is missing a Gradle dependency snippet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-636) Provide documentation about connection and developerConnection
[ https://jira.codehaus.org/browse/SCM-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed SCM-636. -- Resolution: Fixed Fix Version/s: 1.9 Assignee: Robert Scholte Fixed in [fd487ab9|http://git-wip-us.apache.org/repos/asf/maven-scm/commit/fd487ab9] > Provide documentation about connection and developerConnection > -- > > Key: SCM-636 > URL: https://jira.codehaus.org/browse/SCM-636 > Project: Maven SCM > Issue Type: Improvement > Components: documentation >Affects Versions: 1.5 >Reporter: Alberto Gallardo >Assignee: Robert Scholte >Priority: Minor > Fix For: 1.9 > > > I couldn't find any documentation in the official site about the different > *connection* and *developerConnection*. What are the differences between > them? When and how to use them? Is this scm-dependent? etc. This info should > be added to the [usage > page|http://maven.apache.org/scm/maven-scm-plugin/usage.html]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-260) No translation for report.dependency-info.* in several resource bundles
[
https://jira.codehaus.org/browse/MPIR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317208#comment-317208
]
Michael Osipov commented on MPIR-260:
-
{{report.dependency-info.description}} is even missing in the base bundle.
> No translation for report.dependency-info.* in several resource bundles
> ---
>
> Key: MPIR-260
> URL: https://jira.codehaus.org/browse/MPIR-260
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
>Affects Versions: 2.5
> Environment: n/a
>Reporter: Anders Hammar
>Priority: Minor
>
> Need to add the report.dependency-info.* props in several of the resource
> bundles:
> * de
> * cs
> * es
> * gl
> * hu
> * it (lacking several other props as well)
> * ja
> * ko
> * lt
> * nl (lacking several other props as well)
> * no
> * pl (lacking some others as well)
> * pt_BR
> * pt
> * ru
> * sk
> * sv
> * tr
> * zh_CN
> * zh_TW
> It's these props:
> report.dependency-info.name
> report.dependency-info.title
> report.dependency-info.description
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-702) Incorrect documentation for parameter "skip" of goal "check-local-modification" of the plugin
[ https://jira.codehaus.org/browse/SCM-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed SCM-702. -- Resolution: Fixed Fix Version/s: 1.9 Assignee: Robert Scholte Fixed in [bb864ac1|http://git-wip-us.apache.org/repos/asf/maven-scm/commit/bb864ac1] > Incorrect documentation for parameter "skip" of goal > "check-local-modification" of the plugin > - > > Key: SCM-702 > URL: https://jira.codehaus.org/browse/SCM-702 > Project: Maven SCM > Issue Type: Bug > Components: documentation, maven-plugin >Affects Versions: 1.8.1 >Reporter: Maarten van Schouwen >Assignee: Robert Scholte >Priority: Minor > Fix For: 1.9 > > > The documentation for the parameter "skip" of goal "check-local-modification" > of the plugin is incorrect. Currently it is a copy of the documentation for > parameter "errorMessage". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-360) JavaDoc aggregation fails (ignores deployed snapshots, complains that release versions don't satisfy the version range)
[
https://jira.codehaus.org/browse/MJAVADOC-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317205#comment-317205
]
Robert Scholte commented on MJAVADOC-360:
-
For the one willing to pick this this up: The
{{DefaultRepositoryMetadataManager}} is a possible cause. Maybe this says it
all:
http://maven.apache.org/ref/3.0.4/maven-compat/xref/org/apache/maven/artifact/repository/metadata/DefaultRepositoryMetadataManager.html#217
That would explain why the SNAPSHOT's aren't merged.
> JavaDoc aggregation fails (ignores deployed snapshots, complains that release
> versions don't satisfy the version range)
> ---
>
> Key: MJAVADOC-360
> URL: https://jira.codehaus.org/browse/MJAVADOC-360
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.8.1
> Environment: Apache Maven 3.0.4
> (rNON-CANONICAL_2012-01-24_13-02_root; 2012-01-24 13:02:02+)
> Maven home: /opt/maven
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "3.6.11-1-arch", arch: "amd64", family: "unix"
> java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.5)
> (ArchLinux-6.b24_1.11.5-1-x86_64)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>Reporter: Mark R
>
> A multi-module project that uses a few deployed snapshots is now failing to
> build due to the javadoc aggregator giving the following error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:aggregate
> (aggregate) on project io7m-jcanephora: An error has occurred in
> JavaDocs report generation: Unable to find a version in [2.0.0, 2.1.0,
> 2.1.1, 2.1.2, 2.2.0, 2.3.0] to match the range
> [2.4.0-SNAPSHOT,2.4.0-SNAPSHOT],[2.4.0,3.0.0) [ERROR]
> com.io7m.jaux:io7m-jaux:jar:null
> Essentially, the aggregator seems to be saying that only the released
> versions (on the Central repository) are being considered for use, and they
> don't fall within the range given by the dependency on the snapshot version
> of that package (io7m-jaux).
> This was originally discussed on the mailing list here (to no resolution, but
> it was suggested that I open this issue):
> https://mail-archives.apache.org/mod_mbox/maven-users/201301.mbox/%3c20130108140632.851a...@athena.apache.org%3E
> I have uploaded a snapshot of the project to the github repository at:
> https://github.com/io7m/io7m-jcanephora
> The README file gives two required public repositories necessary to build the
> project, and recommends the use of -Dmaven.test.skip=true (as the test suite
> is quite intensive and not needed here). I've been building with "mvn -C
> clean verify -Dmaven.test.skip=true.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-168) http://maven.apache.org/maven-v4_0_0.xsd not accessible
[ https://jira.codehaus.org/browse/MNGSITE-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNGSITE-168. -- Resolution: Not A Bug Assignee: Robert Scholte It should be http://maven.apache.org/xsd/maven-4.0.0.xsd Is there any documentation which refers to your URL? > http://maven.apache.org/maven-v4_0_0.xsd not accessible > --- > > Key: MNGSITE-168 > URL: https://jira.codehaus.org/browse/MNGSITE-168 > Project: Maven Project Web Site > Issue Type: Bug > Environment: Firefox, wget >Reporter: Mathieu Baudier >Assignee: Robert Scholte > > http://maven.apache.org/maven-v4_0_0.xsd doesn't seem to be accessible > anymore. We use it in our POMs as XML grammar. Has it moved? > $ wget http://maven.apache.org/maven-v4_0_0.xsd > --2013-01-12 19:06:38-- http://maven.apache.org/maven-v4_0_0.xsd > Resolving maven.apache.org... 140.211.11.131, 192.87.106.229, > 2001:610:1:80bc:192:87:106:229 > Connecting to maven.apache.org|140.211.11.131|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2013-01-12 19:06:38 ERROR 404: Not Found. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-168) http://maven.apache.org/maven-v4_0_0.xsd not accessible
Mathieu Baudier created MNGSITE-168: --- Summary: http://maven.apache.org/maven-v4_0_0.xsd not accessible Key: MNGSITE-168 URL: https://jira.codehaus.org/browse/MNGSITE-168 Project: Maven Project Web Site Issue Type: Bug Environment: Firefox, wget Reporter: Mathieu Baudier http://maven.apache.org/maven-v4_0_0.xsd doesn't seem to be accessible anymore. We use it in our POMs as XML grammar. Has it moved? $ wget http://maven.apache.org/maven-v4_0_0.xsd --2013-01-12 19:06:38-- http://maven.apache.org/maven-v4_0_0.xsd Resolving maven.apache.org... 140.211.11.131, 192.87.106.229, 2001:610:1:80bc:192:87:106:229 Connecting to maven.apache.org|140.211.11.131|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-01-12 19:06:38 ERROR 404: Not Found. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-267) With Maven 3, "Dependency Repository Locations" links artifacts with my local repository manager id and url instead of public repository info
[ https://jira.codehaus.org/browse/MPIR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPIR-267: --- Affects Version/s: 2.4 > With Maven 3, "Dependency Repository Locations" links artifacts with my local > repository manager id and url instead of public repository info > - > > Key: MPIR-267 > URL: https://jira.codehaus.org/browse/MPIR-267 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.4, 2.6 >Reporter: Herve Boutemy > > MPIR-244 fixed the issue in the first table of the "Dependency Repository > Locations" section > but the next table still has the issue: the header of the table gives the > mirror id and the link to download the artifact points to the repository > manager -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-267) With Maven 3, "Dependency Repository Locations" links artifacts with my local repository manager id and url instead of public repository info
Herve Boutemy created MPIR-267: -- Summary: With Maven 3, "Dependency Repository Locations" links artifacts with my local repository manager id and url instead of public repository info Key: MPIR-267 URL: https://jira.codehaus.org/browse/MPIR-267 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: dependencies Affects Versions: 2.6 Reporter: Herve Boutemy MPIR-244 fixed the issue in the first table of the "Dependency Repository Locations" section but the next table still has the issue: the header of the table gives the mirror id and the link to download the artifact points to the repository manager -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
