[jira] Updated: (SCM-649) Enhance SCM changelog model to hold more data about changes
[ https://jira.codehaus.org/browse/SCM-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-649: - Component/s: maven-scm-provider-bazaar > Enhance SCM changelog model to hold more data about changes > --- > > Key: SCM-649 > URL: https://jira.codehaus.org/browse/SCM-649 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-git, maven-scm-provider-svn >Affects Versions: 1.6 >Reporter: Petr Kozelka >Assignee: Olivier Lamy > Fix For: 1.7 > > Attachments: scm-richmodel-bazaar.patch, scm-richmodel-git.patch, > scm-richmodel-model.patch, scm-richmodel-svn.patch > > > Hello, > I would like to get more information from SCM changelog command, and attached > patches contain my proposal doing some part of this. > There are separate patches for model and for GIT and SVN implementations, I > hope it makes them easier to review. > New functionality is mostly covered with tests. > +Summary of proposed enhancements:+ > ChangeFile.java: > - added: ScmFileStatus *action* > - added: String *originalName* > - added: String *originalRevision* > - they all included in toString() > ScmFileStatus.java: > - added: *RENAMED* = new ScmFileStatus( "renamed" ); > - added: *COPIED* = new ScmFileStatus( "copied" ); > ChangeSet.java: > - added: String *parentRevision* > - added: Set *mergedRevisions* > - both added to toString() > - both added to toXML() + those from ChangeFile - all values stored in > elements not attributes just like the others > GIT implementation notes (GitChangeLogConsumer): > - besides parsing the "whatchanged" command, now the consumer can handle also > many options of the "log" command and harvest most of its provided info. > In particular, the output of "git log --format=raw -C --raw --no-abbrev" > can be parsed. > - there is a potential to simply enable parsing for some more information > like committer, committerDate and treeHash, which I didn't yet (as GIT-only > stuff it may require separate discussion) > SVN implementation notes (SvnChangeLogConsumer): > - svn action "A" (Add) translates to "added" or "copied" depending of > presence of originalFile > - svn action "M" (Modified) always translates to "modified" no matter if > there is an originalFile; _any opinions about this ?_ > - svn action "R" (Replace) translates to "updated" which IMHO has > sufficiently close semantic -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-237) Unexpected download
Robert Scholte created MPIR-237:
---
Summary: Unexpected download
Key: MPIR-237
URL: https://jira.codehaus.org/browse/MPIR-237
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependency-management
Affects Versions: 2.4
Environment: Apache Maven 3.0.4 (r1206075; 2011-11-25 09:20:29+0100)
Maven home: D:\apache-maven-3.0.4-RC2\bin\..
Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
Java home: E:\Program Files\Java\jdk1.6.0_25\jre
Default locale: nl_NL, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Reporter: Robert Scholte
I was kind of surprised to see maven 3.0.5-SNAPSHOT being downloaded. Looks
like a bug to me.
This happend during a {{mvn site}} on the coberturta-maven-plugin rev. 15529
{noformat}
[INFO] Generating "Dependency Management" report---
maven-project-info-reports-plugin:2.4
[INFO] artifact org.apache.maven:maven-plugin-api: checking for updates from
nexus
Downloading:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5-SNAPSHOT/maven-metadata.xml
Downloaded:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5-SNAPSHOT/maven-metadata.xml
(782 B at 0.3 KB/sec)
Downloading:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5-SNAPSHOT/maven-plugin-api-3.0.5-20111209.224224-4.pom
Downloaded:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5-SNAPSHOT/maven-plugin-api-3.0.5-20111209.224224-4.pom
(3 KB at 2.3 KB/sec)
Downloading:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven/3.0.5-SNAPSHOT/maven-metadata.xml
Downloaded:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven/3.0.5-SNAPSHOT/maven-metadata.xml
(809 B at 0.3 KB/sec)
Downloading:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven/3.0.5-SNAPSHOT/maven-3.0.5-20111209.224136-4.pom
Downloaded:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven/3.0.5-SNAPSHOT/maven-3.0.5-20111209.224136-4.pom
(22 KB at 7.7 KB/sec)
[INFO] artifact junit:junit: checking for updates from nexus
{noformat}
--
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-237) Unexpected download
[
https://jira.codehaus.org/browse/MPIR-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285483#comment-285483
]
Robert Scholte commented on MPIR-237:
-
This issue depends on the maven-version
|| Maven Version || maven-plugin-api version download ||
| 2.2.1 | 3.0.3 |
| 3.0.1 | 3.0.3 |
| 3.0.2 | 3.0.3 |
| 3.0.3 | 3.0.5-SNAPSHOT|
| 3.0.4-RC2 | 3.0.5-SNAPSHOT|
| 3.0.4-RC3 | 3.0.3 |
At least with 3.0.4-RC3 it won't download the LATEST but the RELEASED version.
> Unexpected download
> ---
>
> Key: MPIR-237
> URL: https://jira.codehaus.org/browse/MPIR-237
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 2.4
> Environment: Apache Maven 3.0.4 (r1206075; 2011-11-25 09:20:29+0100)
> Maven home: D:\apache-maven-3.0.4-RC2\bin\..
> Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
> Java home: E:\Program Files\Java\jdk1.6.0_25\jre
> Default locale: nl_NL, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Robert Scholte
>
> I was kind of surprised to see maven 3.0.5-SNAPSHOT being downloaded. Looks
> like a bug to me.
> This happend during a {{mvn site}} on the coberturta-maven-plugin rev. 15529
> {noformat}
> [INFO] Generating "Dependency Management" report---
> maven-project-info-reports-plugin:2.4
> [INFO] artifact org.apache.maven:maven-plugin-api: checking for updates from
> nexus
> Downloading:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5-SNAPSHOT/maven-metadata.xml
> (782 B at 0.3 KB/sec)
> Downloading:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5-SNAPSHOT/maven-plugin-api-3.0.5-20111209.224224-4.pom
> Downloaded:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5-SNAPSHOT/maven-plugin-api-3.0.5-20111209.224224-4.pom
> (3 KB at 2.3 KB/sec)
> Downloading:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven/3.0.5-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven/3.0.5-SNAPSHOT/maven-metadata.xml
> (809 B at 0.3 KB/sec)
> Downloading:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven/3.0.5-SNAPSHOT/maven-3.0.5-20111209.224136-4.pom
> Downloaded:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven/3.0.5-SNAPSHOT/maven-3.0.5-20111209.224136-4.pom
> (22 KB at 7.7 KB/sec)
> [INFO] artifact junit:junit: checking for updates from nexus
> {noformat}
--
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-649) Enhance SCM changelog model to hold more data about changes
[ https://jira.codehaus.org/browse/SCM-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-649. Resolution: Fixed bazaar in r1212880 Thanks > Enhance SCM changelog model to hold more data about changes > --- > > Key: SCM-649 > URL: https://jira.codehaus.org/browse/SCM-649 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-git, maven-scm-provider-svn >Affects Versions: 1.6 >Reporter: Petr Kozelka >Assignee: Olivier Lamy > Fix For: 1.7 > > Attachments: scm-richmodel-bazaar.patch, scm-richmodel-git.patch, > scm-richmodel-model.patch, scm-richmodel-svn.patch > > > Hello, > I would like to get more information from SCM changelog command, and attached > patches contain my proposal doing some part of this. > There are separate patches for model and for GIT and SVN implementations, I > hope it makes them easier to review. > New functionality is mostly covered with tests. > +Summary of proposed enhancements:+ > ChangeFile.java: > - added: ScmFileStatus *action* > - added: String *originalName* > - added: String *originalRevision* > - they all included in toString() > ScmFileStatus.java: > - added: *RENAMED* = new ScmFileStatus( "renamed" ); > - added: *COPIED* = new ScmFileStatus( "copied" ); > ChangeSet.java: > - added: String *parentRevision* > - added: Set *mergedRevisions* > - both added to toString() > - both added to toXML() + those from ChangeFile - all values stored in > elements not attributes just like the others > GIT implementation notes (GitChangeLogConsumer): > - besides parsing the "whatchanged" command, now the consumer can handle also > many options of the "log" command and harvest most of its provided info. > In particular, the output of "git log --format=raw -C --raw --no-abbrev" > can be parsed. > - there is a potential to simply enable parsing for some more information > like committer, committerDate and treeHash, which I didn't yet (as GIT-only > stuff it may require separate discussion) > SVN implementation notes (SvnChangeLogConsumer): > - svn action "A" (Add) translates to "added" or "copied" depending of > presence of originalFile > - svn action "M" (Modified) always translates to "modified" no matter if > there is an originalFile; _any opinions about this ?_ > - svn action "R" (Replace) translates to "updated" which IMHO has > sufficiently close semantic -- 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] (MNG-5214) Dependency resolution substitutes g:a:v:jar for j:a:v:something-else when something-else isn't in the reactor
[ https://jira.codehaus.org/browse/MNG-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MNG-5214. - Resolution: Fixed Now there's a full integration test that fails before this fix and works after. > Dependency resolution substitutes g:a:v:jar for j:a:v:something-else when > something-else isn't in the reactor > - > > Key: MNG-5214 > URL: https://jira.codehaus.org/browse/MNG-5214 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 3.0.5 > > > Start with: > https://svn.apache.org/repos/asf/cxf/trunk > Put some pergem space into MAVEN_OPTS (http://cxf.apache.org/building.html) > run mvn -Pfastinstall > Now, cd to systests/wsdl_maven > Run mvn site:site > Here's what's happening under the covers. The first child module has an > execution of the CXF java2ws plugin in 'process-classes'. The second module > has an execution of the CXF codegen plugin in 'generate-sources'. > The first module creates, and attaches, an artifact: > org.apache.cxf.systests.wsdl_maven:cxf-systests-java2ws:(v):wsdl. > The second module declares it as a dependency. > In a multi-module project, one module has a plugin execution in phase > 'process-classes' that produces an attached artifact (with type 'wsdl'). > The site lifecycle does not, by default, include process-classes. So the wsdl > isn't in the reactor, but it's cousin the 'jar' is. > When the codegen plugin calls the artifact resolver, it expects to get an > error, or, better yet, a copy of that wsdl from the local repo or the apache > snapshot repo. Instead, the resolver 'resolves' the artifact to the > corresponding 'jar' in the reactor. Calling getFile() returns the > target/classes directory. -- 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] (ARCHETYPE-395) Basedir variable is not passed to archetype
[
https://jira.codehaus.org/browse/ARCHETYPE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated ARCHETYPE-395:
---
Fix Version/s: 2.3
> Basedir variable is not passed to archetype
> ---
>
> Key: ARCHETYPE-395
> URL: https://jira.codehaus.org/browse/ARCHETYPE-395
> Project: Maven Archetype
> Issue Type: Bug
> Components: Creator
>Affects Versions: 2.1
> Environment: Linux: Ubuntu 11.10 64b, maven 3.0.3
>Reporter: Romain Sertelon
> Fix For: 2.3
>
>
> The property basedir is not replaced in archetype files.
> For instance, I'd like to use ${basedir} in one of my archetype's files, but
> it is not replaced.
> I'll check if I can fix the problem, but I wanted you to be noticed :)
--
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] (SUREFIRE-807) Link from "Cobertura Test Coverage" links to index page
Karl Heinz Marbaise created SUREFIRE-807: Summary: Link from "Cobertura Test Coverage" links to index page Key: SUREFIRE-807 URL: https://jira.codehaus.org/browse/SUREFIRE-807 Project: Maven Surefire Issue Type: Bug Components: Maven Failsafe Plugin, Maven Surefire Plugin Affects Versions: 2.11 Reporter: Karl Heinz Marbaise Priority: Minor The current link on the "Project Reports" area "Coberatura Test Coverage" links to the index page instead to the code coverage report. -- 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-147) guide-m2-development should state recommended version of Ant (eg: 1.7.1 fails, and is still the default in some LTS distros).
Dan Rollo created MNGSITE-147:
-
Summary: guide-m2-development should state recommended version of
Ant (eg: 1.7.1 fails, and is still the default in some LTS distros).
Key: MNGSITE-147
URL: https://jira.codehaus.org/browse/MNGSITE-147
Project: Maven Project Web Site
Issue Type: Bug
Reporter: Dan Rollo
The "guide-m2-development" ("Guide to Developing Maven",
"http://maven.apache.org/guides/development/guide-m2-development.html";) section:
"Don't forget tests!" does not mention a recommended version of Ant to use. I
found the hard way that Ant version:
Apache Ant version 1.7.1 compiled on September 8 2010
will fail with an error like:
BUILD FAILED
/home/dan/javadev/maven/maven-3/trunk/build.xml:228: Syntax error in property:
${
There is a bug in Ant that is apparently fixed in Ant 1.8+.
(see: http://comments.gmane.org/gmane.comp.jakarta.turbine.maven.devel/98115 )
Ant 1.7.1 was the default in my linux environment (Ubuntu 10.04 LTS), and I
expect others might hit this same bug and not be so lucky in searching for a
cause/solution.
I will attach a doc patch that recommends Ant 1.8+.
(I tried to find a way to verify the Ant version in the build.xml, but couldn't
find a way that was not coupled to known versions).
Also (and sorry to overload this report with another issue), I think the
current guide-m2-development.apt in subversion includes another error:
The 'ant all' command was moved up to the same line that sets the M2_HOME env
var. Also, that M2_HOME env var line is missing the export command. The patch
fixes these as well.
--
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-147) guide-m2-development should state recommended version of Ant (eg: 1.7.1 fails, and is still the default in some LTS distros).
[
https://jira.codehaus.org/browse/MNGSITE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Rollo updated MNGSITE-147:
--
Attachment: MNGSITE-147_recommended_Ant_Version.patch
add recommended Ant version.
fix 'export M2_HOME' and 'ant ant' newline.
> guide-m2-development should state recommended version of Ant (eg: 1.7.1
> fails, and is still the default in some LTS distros).
> -
>
> Key: MNGSITE-147
> URL: https://jira.codehaus.org/browse/MNGSITE-147
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Dan Rollo
> Attachments: MNGSITE-147_recommended_Ant_Version.patch
>
>
> The "guide-m2-development" ("Guide to Developing Maven",
> "http://maven.apache.org/guides/development/guide-m2-development.html";)
> section:
> "Don't forget tests!" does not mention a recommended version of Ant to use. I
> found the hard way that Ant version:
> Apache Ant version 1.7.1 compiled on September 8 2010
> will fail with an error like:
> BUILD FAILED
> /home/dan/javadev/maven/maven-3/trunk/build.xml:228: Syntax error in
> property: ${
> There is a bug in Ant that is apparently fixed in Ant 1.8+.
> (see: http://comments.gmane.org/gmane.comp.jakarta.turbine.maven.devel/98115 )
> Ant 1.7.1 was the default in my linux environment (Ubuntu 10.04 LTS), and I
> expect others might hit this same bug and not be so lucky in searching for a
> cause/solution.
> I will attach a doc patch that recommends Ant 1.8+.
> (I tried to find a way to verify the Ant version in the build.xml, but
> couldn't find a way that was not coupled to known versions).
> Also (and sorry to overload this report with another issue), I think the
> current guide-m2-development.apt in subversion includes another error:
> The 'ant all' command was moved up to the same line that sets the M2_HOME env
> var. Also, that M2_HOME env var line is missing the export command. The patch
> fixes these as well.
--
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-147) guide-m2-development should state recommended version of Ant (eg: 1.7.1 fails, and is still the default in some LTS distros).
[
https://jira.codehaus.org/browse/MNGSITE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285501#comment-285501
]
Dan Rollo edited comment on MNGSITE-147 at 12/10/11 11:34 PM:
--
add recommended Ant version.
fix 'export M2_HOME' and 'ant all' newline.
was (Author: bhamail):
add recommended Ant version.
fix 'export M2_HOME' and 'ant ant' newline.
> guide-m2-development should state recommended version of Ant (eg: 1.7.1
> fails, and is still the default in some LTS distros).
> -
>
> Key: MNGSITE-147
> URL: https://jira.codehaus.org/browse/MNGSITE-147
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Dan Rollo
> Attachments: MNGSITE-147_recommended_Ant_Version.patch
>
>
> The "guide-m2-development" ("Guide to Developing Maven",
> "http://maven.apache.org/guides/development/guide-m2-development.html";)
> section:
> "Don't forget tests!" does not mention a recommended version of Ant to use. I
> found the hard way that Ant version:
> Apache Ant version 1.7.1 compiled on September 8 2010
> will fail with an error like:
> BUILD FAILED
> /home/dan/javadev/maven/maven-3/trunk/build.xml:228: Syntax error in
> property: ${
> There is a bug in Ant that is apparently fixed in Ant 1.8+.
> (see: http://comments.gmane.org/gmane.comp.jakarta.turbine.maven.devel/98115 )
> Ant 1.7.1 was the default in my linux environment (Ubuntu 10.04 LTS), and I
> expect others might hit this same bug and not be so lucky in searching for a
> cause/solution.
> I will attach a doc patch that recommends Ant 1.8+.
> (I tried to find a way to verify the Ant version in the build.xml, but
> couldn't find a way that was not coupled to known versions).
> Also (and sorry to overload this report with another issue), I think the
> current guide-m2-development.apt in subversion includes another error:
> The 'ant all' command was moved up to the same line that sets the M2_HOME env
> var. Also, that M2_HOME env var line is missing the export command. The patch
> fixes these as well.
--
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
