[jira] Created: (MRELEASE-680) Fails on cygwin with multiline module with nullpointer exception.
Fails on cygwin with multiline module with nullpointer exception.
-
Key: MRELEASE-680
URL: http://jira.codehaus.org/browse/MRELEASE-680
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.0
Environment: cygwin on Windows 7 (and probably earlier Windows
versions too).
Reporter: Dan Haywood
Was failing with a nullpointer exception. I downloaded the source and added
some println statements to ReleaseUtil.java (in mvn-release-manager), so it's
easy enough to see:
First I added:
public static String getCommonBasedir( List reactorProjects, char separator
)
{
System.out.println("ReleaseUtil#getCommonBaseDir()");
...
and in the main loop of this same method I added:
// added:start
System.out.println(" - dir : " + dir );
// added:end
if ( basedir == null )
{
basedir = dir;
}
else
...
Also, I added:
public static int getBaseWorkingDirectoryParentCount( String basedir,
String workingDirectory )
{
System.out.println("getBaseWorkingDirectoryParentCount()");
System.out.println(" ** basedir : " + basedir );
System.out.println(" ** workingDirectory : " + workingDirectory );
...
When I ran:
mvn release:clean release:prepare -P apache-release -D dryRun=true
then I got:
[INFO] Transforming 'Apache Isis'...
ReleaseUtil#getCommonBaseDir()
reactor project: MavenProject: org.apache.isis:isis-parent:0.1.2-incubating-SN
APSHOT @ D:\svn\ai\branches\release-practice\trunk\pom.xml
- dir : D:/svn/ai/branches/release-practice/trunk
reactor project: MavenProject: org.apache.isis:applib:0.1.2-incubating-SNAPSHO
T @ D:\SVN\ai\branches\release-practice\trunk\applib\pom.xml
- dir : D:/SVN/ai/branches/release-practice/trunk/applib
** basedir : D:
getBaseWorkingDirectoryParentCount()
** basedir : D:
** workingDirectory : D:\svn\ai\branches\release-practice\trunk
** workingDirectory : D:\svn\ai\branches\release-practice
** workingDirectory : D:\svn\ai\branches
** workingDirectory : D:\svn\ai
** workingDirectory : D:\svn
** workingDirectory : D:\
** workingDirectory : null
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.shared.release.util.ReleaseUtil.getBaseWorkingDirect
oryParentCount(ReleaseUtil.java:248)
at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.tran
slateScm(RewritePomsForReleasePhase.java:109)
at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.tran
sformScm(RewritePomsForReleasePhase.java:62)
at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transf
ormDocument(AbstractRewritePomsPhase.java:303)
at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transf
As you can see, the logic to walk up the directory hierarchy blows up. I think
this is because 'basedir' itself is wrong (in my case, it ought to be the
initial value of workingDirectory, and exit the loop immediately).
--
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-740) Fractional part of method execution time is truncated for non English locale
[
http://jira.codehaus.org/browse/SUREFIRE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267356#action_267356
]
Kristian Rosenvold commented on SUREFIRE-740:
-
Never mind, found them myself. MAVEN_OPTS="-Duser.language=ru
-Duser.country=RU". German exhibits problem too
> Fractional part of method execution time is truncated for non English locale
>
>
> Key: SUREFIRE-740
> URL: http://jira.codehaus.org/browse/SUREFIRE-740
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 2.8.1
> Environment: Windows 7 Pro x64 with Russian locale/JDK
> 1.6.0_21/Apache Maven 3.0.3 (r1075438; 2011-02-28 20:31:09+0300)
>Reporter: Dmitry Malenok
>
> The problem is that Maven Surefire Plugin and Maven Surefire Report Plugin
> use different locales for writing and reading TEST-* file if the default
> locale is not set to English locale.The first one always uses
> "Locale.ENGLISH" (org.apache.maven.surefire.report.AbstractReporter, line
> 43), but the second one uses the default locale
> (org.apache.maven.plugins.surefire.report.TestSuiteXmlParser, line 50).
> Russian and English locale use different decimal symbol ("," - Russian
> locale, '.' - English locale) that causes the described problem.
--
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-740) Fractional part of method execution time is truncated for non English locale
[
http://jira.codehaus.org/browse/SUREFIRE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267354#action_267354
]
Kristian Rosenvold commented on SUREFIRE-740:
-
Do you have the appropriate value for -Duser.language= -Duser.country= and
-Duser.variant= to reproduce this ? I really need it for an integration test
(As usual, the fix in the code is 1 line and 5 minutes, creating a test is much
harder...)
> Fractional part of method execution time is truncated for non English locale
>
>
> Key: SUREFIRE-740
> URL: http://jira.codehaus.org/browse/SUREFIRE-740
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 2.8.1
> Environment: Windows 7 Pro x64 with Russian locale/JDK
> 1.6.0_21/Apache Maven 3.0.3 (r1075438; 2011-02-28 20:31:09+0300)
>Reporter: Dmitry Malenok
>
> The problem is that Maven Surefire Plugin and Maven Surefire Report Plugin
> use different locales for writing and reading TEST-* file if the default
> locale is not set to English locale.The first one always uses
> "Locale.ENGLISH" (org.apache.maven.surefire.report.AbstractReporter, line
> 43), but the second one uses the default locale
> (org.apache.maven.plugins.surefire.report.TestSuiteXmlParser, line 50).
> Russian and English locale use different decimal symbol ("," - Russian
> locale, '.' - English locale) that causes the described problem.
--
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: (DOXIA-429) Broken link syntax in APT
[
http://jira.codehaus.org/browse/DOXIA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated DOXIA-429:
--
Description:
A common cause of frustration is APT's linking feature. Consider this example:
You want to link to an external resource without a name for the link. So you do
write:
{noformat}
{{http://truezip.java.net}}
{noformat}
Some time later you decide you would prefer a name for the link, but you cannot
insert {name} like so:
{noformat}
{{{TrueZIP User Website}http://truezip.java.net}} // BROKEN!
{noformat}
Rather than this, you have to reverse the order and write:
{noformat}
{{{http://truezip.java.net}TrueZIP User Website}}
{noformat}
So the URI effectively moves from
{noformat}
{{URI}}{noformat}
to
{noformat}
{{{URI}NAME}}
{noformat}
This is really annoying!
I know you can't change this without breaking compatibility. So please provide
a new linking feature, probably something like this:
[[URI]] and [[[NAME]URI]] respectively.
was:
A common cause of frustration is APT's linking feature. Consider this example:
You want to link to an external resource without a name for the link. So you do
write:
{{http://truezip.java.net}}
Some time later you decide you would prefer a name for the link, but you cannot
insert {name} like so:
{{{TrueZIP User Website}http://truezip.java.net}} // BROKEN!
Rather than this, you have to reverse the order and write:
{{{http://truezip.java.net}TrueZIP User Website}}
So the URI effectively moves from {{URI}} to {{{URI}NAME}}. This is really
annoying!
I know you can't change this without breaking compatibility. So please provide
a new linking feature, probably something like this:
[[URI]] and [[[NAME]URI]] respectively.
> Broken link syntax in APT
> -
>
> Key: DOXIA-429
> URL: http://jira.codehaus.org/browse/DOXIA-429
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Apt
>Affects Versions: 1.2
>Reporter: Christian Schlichtherle
>Priority: Minor
>
> A common cause of frustration is APT's linking feature. Consider this
> example: You want to link to an external resource without a name for the
> link. So you do write:
> {noformat}
> {{http://truezip.java.net}}
> {noformat}
> Some time later you decide you would prefer a name for the link, but you
> cannot insert {name} like so:
> {noformat}
> {{{TrueZIP User Website}http://truezip.java.net}} // BROKEN!
> {noformat}
> Rather than this, you have to reverse the order and write:
> {noformat}
> {{{http://truezip.java.net}TrueZIP User Website}}
> {noformat}
> So the URI effectively moves from
> {noformat}
> {{URI}}{noformat}
> to
> {noformat}
> {{{URI}NAME}}
> {noformat}
> This is really annoying!
> I know you can't change this without breaking compatibility. So please
> provide a new linking feature, probably something like this:
> [[URI]] and [[[NAME]URI]] respectively.
--
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] (MPOM-10) Apache Parent POM 9 apache-release profile issues
Apache Parent POM 9 apache-release profile issues - Key: MPOM-10 URL: https://issues.apache.org/jira/browse/MPOM-10 Project: Maven POM Issue Type: Bug Reporter: Sebb The apache-release profile creates a zip archive of all the contents of the current directory tree (excluding SVN and target). This includes some files that should not be present in the zip, e.g. .pmd, .fbprefs, and DOAP files. These should be excluded from the archive. Also, the profile does not create a tar.gz version of source archive. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-429) Broken link syntax in APT
[
http://jira.codehaus.org/browse/DOXIA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267349#action_267349
]
Christian Schlichtherle commented on DOXIA-429:
---
Nope! I mean
http://truezip.java.net
You get it.
> Broken link syntax in APT
> -
>
> Key: DOXIA-429
> URL: http://jira.codehaus.org/browse/DOXIA-429
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Apt
>Affects Versions: 1.2
>Reporter: Christian Schlichtherle
>Priority: Minor
>
> A common cause of frustration is APT's linking feature. Consider this
> example: You want to link to an external resource without a name for the
> link. So you do write:
> {{http://truezip.java.net}}
> Some time later you decide you would prefer a name for the link, but you
> cannot insert {name} like so:
> {{{TrueZIP User Website}http://truezip.java.net}} // BROKEN!
> Rather than this, you have to reverse the order and write:
> {{{http://truezip.java.net}TrueZIP User Website}}
> So the URI effectively moves from {{URI}} to {{{URI}NAME}}. This is really
> annoying!
> I know you can't change this without breaking compatibility. So please
> provide a new linking feature, probably something like this:
> [[URI]] and [[[NAME]URI]] respectively.
--
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: (DOXIA-429) Broken link syntax in APT
[
http://jira.codehaus.org/browse/DOXIA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267348#action_267348
]
Christian Schlichtherle commented on DOXIA-429:
---
The first example is shredded by JIRA and should read (cross fingers I now
quote correctly):
\{\{http://truezip.java.net\}\}
> Broken link syntax in APT
> -
>
> Key: DOXIA-429
> URL: http://jira.codehaus.org/browse/DOXIA-429
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Apt
>Affects Versions: 1.2
>Reporter: Christian Schlichtherle
>Priority: Minor
>
> A common cause of frustration is APT's linking feature. Consider this
> example: You want to link to an external resource without a name for the
> link. So you do write:
> {{http://truezip.java.net}}
> Some time later you decide you would prefer a name for the link, but you
> cannot insert {name} like so:
> {{{TrueZIP User Website}http://truezip.java.net}} // BROKEN!
> Rather than this, you have to reverse the order and write:
> {{{http://truezip.java.net}TrueZIP User Website}}
> So the URI effectively moves from {{URI}} to {{{URI}NAME}}. This is really
> annoying!
> I know you can't change this without breaking compatibility. So please
> provide a new linking feature, probably something like this:
> [[URI]] and [[[NAME]URI]] respectively.
--
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: (DOXIA-429) Broken link syntax in APT
Broken link syntax in APT
-
Key: DOXIA-429
URL: http://jira.codehaus.org/browse/DOXIA-429
Project: Maven Doxia
Issue Type: Bug
Components: Module - Apt
Affects Versions: 1.2
Reporter: Christian Schlichtherle
Priority: Minor
A common cause of frustration is APT's linking feature. Consider this example:
You want to link to an external resource without a name for the link. So you do
write:
{{http://truezip.java.net}}
Some time later you decide you would prefer a name for the link, but you cannot
insert {name} like so:
{{{TrueZIP User Website}http://truezip.java.net}} // BROKEN!
Rather than this, you have to reverse the order and write:
{{{http://truezip.java.net}TrueZIP User Website}}
So the URI effectively moves from {{URI}} to {{{URI}NAME}}. This is really
annoying!
I know you can't change this without breaking compatibility. So please provide
a new linking feature, probably something like this:
[[URI]] and [[[NAME]URI]] respectively.
--
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: (DOXIA-428) Fix broken fragment links in Doxia
Fix broken fragment links in Doxia -- Key: DOXIA-428 URL: http://jira.codehaus.org/browse/DOXIA-428 Project: Maven Doxia Issue Type: Bug Components: Module - Apt Affects Versions: 1.2 Reporter: Christian Schlichtherle Using APT in maven-site-plugin:3.0-beta-3, it is impossible to link to a class member in Javadoc, because the link requires a fragment to be used which is shredded by the APT conversion. You can't even link to Object.toString() because this would be converted to href="Object.html#toString()". While this makes a perfectly valid fragment according to RFC 2396, APT shreds it to some unusable result. Please fix this linking feature - it's utterly broken! APT should not touch fragments at all when referring to external links. -- 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-5037) Download only snapshot artefacts in local repo and not timestamped jars
[ http://jira.codehaus.org/browse/MNG-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Webb updated MNG-5037: --- Attachment: aether-nolocaltimestamps.zip Attached is an extension that gets around this problem. Unzip the file, build with Maven then drop target/aether-nolocaltimestamps-1.11.jar in $M2_HOME/lib/ext The extension replaces the default EnhancedLocalRepositoryManager with a version that uses artifact.getBaseVersion() rather than artifact.getVersion(). The same change could be applied directly to EnhancedLocalRepositoryManager if it is acceptable. > Download only snapshot artefacts in local repo and not timestamped jars > --- > > Key: MNG-5037 > URL: http://jira.codehaus.org/browse/MNG-5037 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 3.0.3 >Reporter: Yann Albou > Attachments: aether-nolocaltimestamps.zip > > > Since Maven 3 the local repository contains timestamped jars. > With Maven 2 because of the option uniqueVersion to false the local repo is > not full of timestamped jars. The support for this option has been removed in > mvn 3 which I understand for the upload in the remote repo. But for the local > repo it should be possible to only download the snapshots... > See thread: > http://maven.40175.n5.nabble.com/Issue-with-mvn3-timestamp-snapshots-being-downloaded-in-local-repository-td3408008.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: (MRELEASE-545) When Using a Custom Settings XML File (with the -s option) release:prepare Does Not Read Proper Credentials
[
http://jira.codehaus.org/browse/MRELEASE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267333#action_267333
]
H.-C. Gürsoy commented on MRELEASE-545:
---
Hi Folks,
I run today into same issue with version 2.1 of the plugin:
{noformat}
[INFO] [DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' -->
[INFO] [DEBUG] (f) artifact = com.foocom:sample:jar:1.5
[INFO] [DEBUG] (f) attachedArtifacts =
[com.foocom:sample:java-source:sources:1.5,
com.foocom:sample:javadoc:javadoc:1.5]
[INFO] [DEBUG] (f) deploymentRepository =
Repository[releases|http://ci-repo-prod01.foocom.local:8081/nexus/content/repositories/simpleapp_release/]
[INFO] [DEBUG] (s) localRepository =
Repository[local|file:///home/guersoy/.m2/repository]
[INFO] [DEBUG] (f) packaging = jar
[INFO] [DEBUG] (f) pomFile =
/data/guersoy/workspaces/nexus-sample/target/checkout/pom.xml
[INFO] [DEBUG] (f) skip = false
[INFO] [DEBUG] (f) updateReleaseInfo = true
[INFO] [DEBUG] -- end configuration --
[INFO] [INFO] [deploy:deploy {execution: default-deploy}]
[INFO] [DEBUG] Using Wagon implementation lightweight from default mapping for
protocol http
[INFO] [DEBUG] Checking for pre-existing User-Agent configuration.
[INFO] [DEBUG] Adding User-Agent configuration.
[INFO] [DEBUG] not adding permissions to wagon connection
[INFO] Uploading:
http://ci-repo-prod01.foocom.local:8081/nexus/content/repositories/simpleapp_release//de/foocom/sample/1.5/sample-1.5.jar
[INFO] 2/2K
[INFO] [DEBUG] Using Wagon implementation lightweight from default mapping for
protocol http
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Error deploying artifact: Failed to transfer file:
http://ci-repo-prod01.foocom.local:8081/nexus/content/repositories/simpleapp_release/de/foocom/sample/1.5/sample-1.5.jar.
Return code is: 401
{noformat}
This is awfull because this issue is a show stopper for using the plugin in
central build systems hosting different projects with different credentials.
> When Using a Custom Settings XML File (with the -s option) release:prepare
> Does Not Read Proper Credentials
> ---
>
> Key: MRELEASE-545
> URL: http://jira.codehaus.org/browse/MRELEASE-545
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0
>Reporter: Tim O'Brien
>
> Here's the "situation":
> 1. You have multiple Maven Settings files because you are dealing with
> different environments. Assume you have:
>~/.m2/envA-settings.xml
>~/.m2/envB-settings.xml
> 2. Your build deploys to a repository manager with a server id of "nexus".
>
> 3. ~/m2/envA-settings.xml contains the server credentials for the server with
> an id of "nexus"
> Problem:
> Running the following command:
>mvn -s ~/.m2/envA-settings.xml release:perform
> After a successful prepare, gets a 401 error because the release:perform goal
> is not picking up the credentials from ~/.m2/envA-settings.xml.
> The work-around to this problem is to move ~/.m2/envA-settings.xml to
> ~/.m2/settings.xml.For some reason the perform goal only works for me
> when I am using the default location for Maven Settings XML. It seems
> like the release:perform should honor the custom location of a Maven Settings
> file.
> This quirk ate my day.
--
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
