[jira] Created: (MNGSITE-72) Maven 2 property reference guide
Maven 2 property reference guide Key: MNGSITE-72 URL: http://jira.codehaus.org/browse/MNGSITE-72 Project: Maven 2 Project Web Site Issue Type: Bug Environment: All Reporter: Robert Bracewell The main Maven website needs to include documentation or a reference guide that explains all Maven 2.x properties. I havent been able to find any such link on the 2.x website if such does exist -- 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-423) when I try to checkout file from perforce with maven, I get an exception "Perforce password (P4PASSWD) invalid or unset."
[ http://jira.codehaus.org/browse/SCM-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155547#action_155547 ] Robert Bracewell commented on SCM-423: -- I also see exactly the same issue However if I revert t0 1.0 of the plugin then it works fine > when I try to checkout file from perforce with maven, I get an exception > "Perforce password (P4PASSWD) invalid or unset." > - > > Key: SCM-423 > URL: http://jira.codehaus.org/browse/SCM-423 > Project: Maven SCM > Issue Type: Bug >Affects Versions: 1.1 > Environment: windowsxp, >Reporter: alex zh > > Hi all, > I'm using maven scm plugin 1.1 and Perforce for building, when I try to > checkout code from Perforce it get the following exception: can anyone help ? > I've logged in before I run mvn scm:checkout command. > D:\>mvn scm:checkout > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] --- > [INFO] Building BSGCommon > [INFO]task-segment: [scm:checkout] (aggregator-style) > [INFO] --- > [INFO] [scm:checkout] > [INFO] Removing D:\target\checkout > [INFO] --- > [ERROR] BUILD ERROR > [INFO] --- > [INFO] Cannot run checkout command : > Embedded error: Can't login. > Perforce password (P4PASSWD) invalid or unset. > [INFO] --- > [INFO] For more information, run Maven with the -e switch > [INFO] --- > [INFO] Total time: 7 seconds > [INFO] Finished at: Wed Oct 22 15:53:25 IST 2008 > [INFO] Final Memory: 6M/13M > [INFO] --- -- 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-385) Filtering replaces tokens it should not be replacing
Filtering replaces tokens it should not be replacing
Key: MASSEMBLY-385
URL: http://jira.codehaus.org/browse/MASSEMBLY-385
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-3
Environment: Maven 2.0.9
Reporter: Robert Bracewell
Priority: Critical
Attachments: component.zip
What is described below is attached as an example that duplicates this
When filtering is turned on and a token ends with .url then very strange things
happen
The assembly descriptor uses
${basedir}/src/config/xml/applicationContext.xml
xml
true
The file being filtered contains:
After the assembly is run the file contains:
The string This is a not a URL but demonstrates the BUG comes from the url tag
defined in parent pom
The string test1 is the artifactId
--
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-4020) Release plugin disregards SCM configured element within the pom
Release plugin disregards SCM configured element within the pom --- Key: MNG-4020 URL: http://jira.codehaus.org/browse/MNG-4020 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle, POM Environment: Maven 2.0.9 using maven-release-plugin version 2.0-beta-7 Reporter: Robert Bracewell I have a scenario where the SCM tag is configured with the following: scm:perforce:p4server:1666://components/projectA/pom.xml scm:perforce:p4server:1666://components/projectA/pom.xml The location in Perforce //components/projectA contains the pom.xml in question and then a bunch of sub-directories located at the same level as the pom. When the release plugin runs a perform it churns out the following: [INFO] [release:perform] [INFO] Checking out the project to perform the release ... [INFO] The SCM location in your pom.xml (//components/projectA/pom.xml) is not equal to the depot location (//components/projectA). This happens frequently with branches. Ignoring the SCM location. For my situation the above is incorrect as I am only releasing a pom not several modules. The release:perform then continues to sync every file located under //components/projectA which in my case is several thousand and as such takes several minutes to complete. The release plugin should be able to handle such SCM elements and understand that only a single file is being released when such is explicitly defined -- 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-3542) Filtering test resources replaces the wrong value
Filtering test resources replaces the wrong value
-
Key: MNG-3542
URL: http://jira.codehaus.org/browse/MNG-3542
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Environment: Windows XP and Linux
Tried with Maven 2.0.7 upwards
Java 1.5
Reporter: Robert Bracewell
Noticed an oddity with filtering in that it is replacing the wrong properties
under certain conditions. The key thing to note in below mockup is the url
property in pom.xml
Contents of pom.xml:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
http://THIS_IS_A_URL_TO_HIGHLIGHT_THE_BUG
com.maven.bugs
bug1
1
jar
Maven Bug 1
src/test/resources
true
In the src/test/resources directory is a file that contains:
${test.url}
When running mvn clean process-test-resources the file generated in
target/test-classes now contains:
http://THIS_IS_A_URL_TO_HIGHLIGHT_THE_BUG
This is not what I expect as I don't have a property for test.url defined
--
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
