[jira] Commented: (MNG-4986) After "mvn deploy" an SNAPSHOT artifact to company central repo(artifactory-2.3.1), Could not download the artifact in other machines.
[
http://jira.codehaus.org/browse/MNG-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255823#action_255823
]
Benjamin Bentmann commented on MNG-4986:
The log and the repo contents you provided don't match up. The log says
{noformat}
[DEBUG] Could not find metadata
com.wacube.mebula:com.wacube.mebula.buffer:1.0.1-SNAPSHOT/maven-metadata.xml in
local (C:\devtools\apache-maven-repo\repository)
{noformat}
while the {{buffer-1.0.1-SNAPSHOT.zip}} contains {{maven-metadata-local.xml}}.
Likewise
{noformat}
[WARNING] The POM for
com.wacube.mebula:com.wacube.mebula.buffer:jar:1.0.1-SNAPSHOT is missing
{noformat}
doesn't match the fact that the {{_maven.repositories}} marks the file as
locally present. Without an example project, I'm not able to draw a fruitful
conclusion from this.
> After "mvn deploy" an SNAPSHOT artifact to company central
> repo(artifactory-2.3.1), Could not download the artifact in other machines.
> --
>
> Key: MNG-4986
> URL: http://jira.codehaus.org/browse/MNG-4986
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0, 3.0.1, 3.0.2
> Environment: Windows XP SP3, Oracle JDK 1.6.0_22, MAVEN
> 3.0/3.0.1/3.0.2
>Reporter: Isaac Qu
>Assignee: Benjamin Bentmann
> Attachments: buffer-1.0.1-SNAPSHOT.zip, local-repo-contents.zip,
> maven-debug-inf.txt
>
>
> After "mvn deploy" an SNAPSHOT artifact to company central
> repo(artifactory-2.3.1), Could not download the artifact in other machines.
> MAVEN 2.2.1 has no this problem.
> Following is detailed error info.
> D:\work_p2p\tcpip>mvn install
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building Wacube Mebula TCP/IP Service 1.1.0-SNAPSHOT
> [INFO]
>
> Downloading:
> http://192.168.0.2:8080/artifactory/repo/com/wacube/mebula/com.wacube.mebula.buffer/maven-metadata.xml
> Downloading:
> http://192.168.0.2:8080/artifactory/repo/com/wacube/mebula/com.wacube.mebula.buffer/maven-metadata.xml
> Downloaded:
> http://192.168.0.2:8080/artifactory/repo/com/wacube/mebula/com.wacube.mebula.buffer/maven-metadata.xml
> (337
> B at 2.3 KB/sec)
> Downloaded:
> http://192.168.0.2:8080/artifactory/repo/com/wacube/mebula/com.wacube.mebula.buffer/maven-metadata.xml
> (337
> B at 1.9 KB/sec)
> [WARNING] The POM for
> com.wacube.mebula:com.wacube.mebula.buffer:jar:1.0.1-SNAPSHOT is missing, no
> dependency informatio
> n available
> Downloading:
> http://192.168.0.2:8080/artifactory/repo/com/wacube/mebula/com.wacube.mebula.core/maven-metadata.xml
> Downloading:
> http://192.168.0.2:8080/artifactory/repo/com/wacube/mebula/com.wacube.mebula.core/maven-metadata.xml
> Downloaded:
> http://192.168.0.2:8080/artifactory/repo/com/wacube/mebula/com.wacube.mebula.core/maven-metadata.xml
> (375 B
> at 3.4 KB/sec)
> Downloaded:
> http://192.168.0.2:8080/artifactory/repo/com/wacube/mebula/com.wacube.mebula.core/maven-metadata.xml
> (375 B
> at 2.9 KB/sec)
> [WARNING] The POM for
> com.wacube.mebula:com.wacube.mebula.core:jar:1.1.1-SNAPSHOT is missing, no
> dependency information
> available
> [WARNING] The POM for
> com.wacube.mebula:com.wacube.mebula.core:jar:1.1.2-SNAPSHOT is missing, no
> dependency information
> available
--
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-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255820#action_255820
]
Fabien Bousquet commented on SCM-606:
-
I have a problem with date and author which may be falses.
The header line (author, commitor etc...) is followed by the following
information at least once for *each commit* (See
http://www.kernel.org/pub/software/scm/git/docs/git-blame.html).
So when a release have already listed in blame output, date and author can be
falses.
I propose a patch which stores release informations (author and date) and uses
it when possible.
Mark, Could you review ?
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
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: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabien Bousquet updated SCM-606:
Attachment: SCM606_bis.patch
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch,
> SCM606_bis.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
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] Closed: (MNG-4956) Cygwin mvn script modifies CLASSPATH environment variable
[
http://jira.codehaus.org/browse/MNG-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4956.
--
Resolution: Fixed
Fix Version/s: 3.0.3
Assignee: Benjamin Bentmann
Fixed in [r1070158|http://svn.apache.org/viewvc?view=revision&revision=1070158].
> Cygwin mvn script modifies CLASSPATH environment variable
> -
>
> Key: MNG-4956
> URL: http://jira.codehaus.org/browse/MNG-4956
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0
> Environment: Cygwin on Windowx
>Reporter: Zemian Deng
>Assignee: Benjamin Bentmann
> Fix For: 3.0.3
>
>
> When running in Cygwin, the apache-maven-3.0/bin/mvn script actually changed
> the user env CLASSPATH to an invalid Java classpath value, which is
> unexpected! To repeat this, try the following on Cygwin:
> Create this simple pom.xml in an project:
> {code: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
> deng
> mvn-examples
> jar
> 1.0-SNAPSHOT
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
> 1.6
>
>
>
>
>
>
>
>
>
> {code}
> {code}
> $ /apps/apache-maven-3.0/bin/mvn -v
> Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400)
> Java version: 1.6.0_19
> Java home: C:\apps\jdk1.6.0_19\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> $ export CLASSPATH="C:\\my-classes;C:\\my-lib\app.jar"
> $ echo $CLASSPATH
> C:\my-classes;C:\my-lib\app.jar
> $ /apps/apache-maven-3.0/bin/mvn antrun:run
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building mvn-examples 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-antrun-plugin:1.6:run (default-cli) @ mvn-examples ---
> [INFO] Executing tasks
> main:
> [echo] Maven env.CLASSPATH:
> /cygdrive/c/my-classes:/cygdrive/c/my-lib/app.jar
> [INFO] Executed tasks
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.843s
> [INFO] Finished at: Wed Dec 29 23:37:41 EST 2010
> [INFO] Final Memory: 2M/15M
> [INFO]
>
> {code}
> NOTE 1: The CLASSPATH value has been modified with cygwin path prefix, which
> become an invalid Java classpath value!
> NOTE 2: If I use mvn.bat in cygwin shell, it will work as expected. So this
> only affect the mvn shell script only.
> NOTE 3: This only affect the variable "CLASSPATH", b/c if I use
> JAVA_CLASSPATH, the value didn't change.
--
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-4956) Cygwin mvn script modifies CLASSPATH environment variable
[
http://jira.codehaus.org/browse/MNG-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4956:
---
Description:
When running in Cygwin, the apache-maven-3.0/bin/mvn script actually changed
the user env CLASSPATH to an invalid Java classpath value, which is unexpected!
To repeat this, try the following on Cygwin:
Create this simple pom.xml in an project:
{code: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
deng
mvn-examples
jar
1.0-SNAPSHOT
org.apache.maven.plugins
maven-antrun-plugin
1.6
{code}
{code}
$ /apps/apache-maven-3.0/bin/mvn -v
Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400)
Java version: 1.6.0_19
Java home: C:\apps\jdk1.6.0_19\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
$ export CLASSPATH="C:\\my-classes;C:\\my-lib\app.jar"
$ echo $CLASSPATH
C:\my-classes;C:\my-lib\app.jar
$ /apps/apache-maven-3.0/bin/mvn antrun:run
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building mvn-examples 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-antrun-plugin:1.6:run (default-cli) @ mvn-examples ---
[INFO] Executing tasks
main:
[echo] Maven env.CLASSPATH:
/cygdrive/c/my-classes:/cygdrive/c/my-lib/app.jar
[INFO] Executed tasks
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.843s
[INFO] Finished at: Wed Dec 29 23:37:41 EST 2010
[INFO] Final Memory: 2M/15M
[INFO]
{code}
NOTE 1: The CLASSPATH value has been modified with cygwin path prefix, which
become an invalid Java classpath value!
NOTE 2: If I use mvn.bat in cygwin shell, it will work as expected. So this
only affect the mvn shell script only.
NOTE 3: This only affect the variable "CLASSPATH", b/c if I use JAVA_CLASSPATH,
the value didn't change.
was:
When running in Cygwin, the apache-maven-3.0/bin/mvn script actually changed
the user env CLASSPATH to an invalid Java classpath value, which is unexpected!
To repeat this, try the following on Cygwin:
Create this simple pom.xml in an project:
{code: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
deng
mvn-examples
jar
1.0-SNAPSHOT
org.apache.maven.plugins
maven-antrun-plugin
1.6
{code:xml}
{code}
$ /apps/apache-maven-3.0/bin/mvn -v
Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400)
Java version: 1.6.0_19
Java home: C:\apps\jdk1.6.0_19\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
$ export CLASSPATH="C:\\my-classes;C:\\my-lib\app.jar"
$ echo $CLASSPATH
C:\my-classes;C:\my-lib\app.jar
$ /apps/apache-maven-3.0/bin/mvn antrun:run
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building mvn-examples 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-antrun-plugin:1.6:run (default-cli) @ mvn-examples ---
[INFO] Executing tasks
main:
[echo] Maven env.CLASSPATH:
/cygdrive/c/my-classes:/cygdrive/c/my-lib/app.jar
[INFO] Executed tasks
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.843s
[INFO] Finished at: Wed Dec 29 23:37:41 EST 2010
[INFO] Final Memory: 2M/15M
[INFO]
{code}
NOTE 1: The CLASSPATH value has been modified with cygwin path prefix, which
become an invalid Java classpath value!
NOTE 2: If I use mvn.bat in cygwin shell, it will work as expected. So this
only affect the mvn shell script only.
NOTE 3: This only affect the variable "CLASSPATH", b/c if I use JAVA_CLASSPATH,
the value didn't change.
> Cygwin mvn script modifies CLASSPATH environment variable
> -
>
> Key: MNG-4956
> URL: http://jira.codehaus.org/browse/MNG-4956
> Project: Maven 2 & 3
>
[jira] Closed: (MNG-5000) child distributionManagment.site.url not correct in a flat directory layout
[
http://jira.codehaus.org/browse/MNG-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5000.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
bq. (ie modules get deployed to the same level)
Which is the expected behavior as per MNG-3134 and the structure of the example
project.
bq. [...] running help:effective-pom in one of the modules shows that the
effective distributionManagement.site.url of the module is actually
/tmp/module1, this is what the site plugin uses.
This is what I see with Maven 3.0.x
{code:xml}
MSITE-227
file:///tmp/module1/
{code}
and with Maven 2.2.1:
{code:xml}
MSITE-227
file:///tmp/module1
{code}
which apart from the trailing slash from the parent's URL being preserved by
Maven 3.x, is identical. So I don't see how this is a core issue.
> child distributionManagment.site.url not correct in a flat directory layout
> ---
>
> Key: MNG-5000
> URL: http://jira.codehaus.org/browse/MNG-5000
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.2
> Environment: windows
>Reporter: Stefan Hansel
>Assignee: Benjamin Bentmann
> Attachments: artifact-id-testcase.zip
>
>
> There is a multimodule flat project structure:
> root
> module1
> module2
> module1 has an artifactID of 'module1' (same as directory name)
> modulu2 has an artifactID of 'module-2' (different to directory name)
> After a 'mvn site-deploy' the generated report has the folder structure:
> /root
> /root/module-2
> /module1
> So based on the artifactID the submodules are created as a child of the root
> - or not.
> This is at least inconsistent and should be changed to be handled always the
> same - independent of the artifactID.
> This is also important for other plugins (i.e. the dashboard plugin).
> They seem to have some hardcoded directory structure (preferring submodules
> as childs of the root report).
> Due to this bug (see http://jira.codehaus.org/browse/MOJO-1630) the links
> between reports there still don't work as long as artifactID=module's
> directory.
> Attached you will find a testcase (based on maven3, but can also be used with
> maven2 when the version of the site-plugin is changed).
--
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-4997) Plugin @Parameter alias does not work for complex parameter types
[ http://jira.codehaus.org/browse/MNG-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4997: --- Summary: Plugin @Parameter alias does not work for complex parameter types (was: Plugin @Parameter alias does not work for Maps) > Plugin @Parameter alias does not work for complex parameter types > - > > Key: MNG-4997 > URL: http://jira.codehaus.org/browse/MNG-4997 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugin API >Affects Versions: 2.2.1 >Reporter: Gili > Fix For: 3.0 > > > It looks like MNG-674 fixed @parameter aliasing for simple types, but not for > Map. > I declare this in the plugin: > /** >* The environment variables. >* >* @parameter alias="environment" >* @required >*/ > private Map environmentVariables; > and this in the POM: > > bar > > This fails, but using a simple type works: > /** >* The environment variables. >* >* @parameter alias="environment" >* @required >*/ > private String environmentVariables; > [...] > bar -- 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] Closed: (MNG-4997) Plugin @Parameter alias does not work for complex parameter types
[ http://jira.codehaus.org/browse/MNG-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4997. -- Resolution: Fixed Fix Version/s: 3.0 Assignee: Benjamin Bentmann > Plugin @Parameter alias does not work for complex parameter types > - > > Key: MNG-4997 > URL: http://jira.codehaus.org/browse/MNG-4997 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugin API >Affects Versions: 2.2.1 >Reporter: Gili >Assignee: Benjamin Bentmann > Fix For: 3.0 > > > It looks like MNG-674 fixed @parameter aliasing for simple types, but not for > Map. > I declare this in the plugin: > /** >* The environment variables. >* >* @parameter alias="environment" >* @required >*/ > private Map environmentVariables; > and this in the POM: > > bar > > This fails, but using a simple type works: > /** >* The environment variables. >* >* @parameter alias="environment" >* @required >*/ > private String environmentVariables; > [...] > bar -- 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] Closed: (MNG-4551) List parameter in a mojo has strange behaviour
[
http://jira.codehaus.org/browse/MNG-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4551.
--
Resolution: Fixed
Fix Version/s: (was: Issues to be reviewed for 3.x)
3.0.3
Assignee: Benjamin Bentmann
The issue with {{expression}} on plugin parameters using collection interfaces
has been fixed in
[r1070102|http://svn.apache.org/viewvc?view=revision&revision=1070102].
For the configuration merging during inheritance, please see [Merging Plugin
Configuration in Complex
Projects|http://www.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/]
> List parameter in a mojo has strange behaviour
> --
>
> Key: MNG-4551
> URL: http://jira.codehaus.org/browse/MNG-4551
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.2.1
> Environment: windows, maven 2.2.1, java 1.5.15, gmaven 1.0 rc4
>Reporter: Gabriel Dogaru
>Assignee: Benjamin Bentmann
> Fix For: 3.0.3
>
>
> I had different problems with a mojo parameter of type list in my Mojo.
> I use a parent pom to configure all the plugins used in our projects.
> There I give the list 4 values like this, and every module should be able to
> overwrite this and use any dbs it needs.
>
> metadata
> portal
> client
> model
>
> In my mojo I have
> * @parameter
> * @required
> */
> List moduleDbs
> 1. If I try to use
> * @parameter expression="${moduleDbs}"
> it fails saying it can not initialize the list.
> 2.I tried to overwrite the configuration in a module with an empty db set.
> tried both and but the mojo still had
> one record in the list
> Also I needed to overwrite it with a value that was not in the parent, like
> lolisima and the list also contained metadata from the original configuration.
> When I switched the type from List to
> * @parameter expression="${moduleDbs}"
>* @required
>*/
> String[] moduleDbs
> everything worked perfectly.
> I am not sure if this has something to do with maven core. I am using gmaven
> and it may be because of the way groovy treats arrays and lists.
--
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: (MPDF-47) docDescriptors of other locales than default are ignored for pdf generation
[
http://jira.codehaus.org/browse/MPDF-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255805#action_255805
]
Fabian Unfried commented on MPDF-47:
Sorry, wasn't aware of that Jira has some table syntax which is very similar to
the directory layout you're using on the site and pd plugin page, so here again
the directory layout:
- src/
-- site/
--- xdoc/
index.xml (some default language content)
help.xml (some default language content)
foo.xml (some default language content)
--- de/
xdoc/
- index.xml (some different content than default language)
- help.xml (some different content than default language)
- foo.xml (some different content than default language)
--- site.xml (Default site descriptor)
--- site_de.xml (German site descriptor)
--- pdf.xml (Default pdf descriptor)
--- pdf_de.xml (German pdf descriptor)
> docDescriptors of other locales than default are ignored for pdf generation
> ---
>
> Key: MPDF-47
> URL: http://jira.codehaus.org/browse/MPDF-47
> Project: Maven 2.x PDF Plugin
> Issue Type: Bug
>Affects Versions: 1.1
> Environment: Maven 2.2.1, Windows 7 (and NetBeans 6.9.1)
>Reporter: Fabian Unfried
> Attachments: pdf.xml, pdf_de.xml
>
>
> If you have a multi language maven site and you'll try to build a pdf also
> with multiple locales only the default pdf.xml docDescriptor will be used for
> generating the pdfs.
> Try following:
> Create a directory layout like:
> +- src/
>+- site/
> +- xdoc/
> | +- index.xml (some default language content)
> | +- help.xml (some default language content)
> | +- foo.xml (some default language content)
> |
> +- de/
> | +- xdoc/
> | +- index.xml (some different content than default language)
> | +- help.xml (some different content than default language)
> | +- foo.xml (some different content than default language)
> +- site.xml (Default site descriptor)
> +- site_de.xml (German site descriptor)
> +- pdf.xml (Default pdf descriptor)
> +- pdf_de.xml (German pdf descriptor)
> Content of pdf.xml:
> see attachment pdf.xml
> Content of pdf_de.xml:
> see attachment pdf_de.xml
> Content of pom.xml:
> ...
>
> ...
>
> ...
>
> org.apache.maven.plugins
> maven-site-plugin
> 2.2
>
> en,de
>
>
>
> org.apache.maven.plugins
> maven-pdf-plugin
> 1.1
>
>
> ${project.reporting.outputDirectory}
> false
> true
> en,de
>
>
>
> pdf
> site
>
> pdf
>
>
>
>
>
>
> If you now execute
> mvn site
> or
> mvn pdf:pdf
> and compare the two generated pdfs you'll see that the table of contents is
> the one from the pdf.xml in both pdfs. I guess in this case the file
> pdf_de.xml isn't used at anytime during the build, because the build (mvn
> site or mvn pdf:pdf) is also successful if you have syntax errors in the
> pdf_de.xml file, e.g. leave a item tag open in that file and build again.
--
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: (MPDF-47) docDescriptors of other locales than default are ignored for pdf generation
docDescriptors of other locales than default are ignored for pdf generation
---
Key: MPDF-47
URL: http://jira.codehaus.org/browse/MPDF-47
Project: Maven 2.x PDF Plugin
Issue Type: Bug
Affects Versions: 1.1
Environment: Maven 2.2.1, Windows 7 (and NetBeans 6.9.1)
Reporter: Fabian Unfried
Attachments: pdf.xml, pdf_de.xml
If you have a multi language maven site and you'll try to build a pdf also with
multiple locales only the default pdf.xml docDescriptor will be used for
generating the pdfs.
Try following:
Create a directory layout like:
+- src/
+- site/
+- xdoc/
| +- index.xml (some default language content)
| +- help.xml (some default language content)
| +- foo.xml (some default language content)
|
+- de/
| +- xdoc/
| +- index.xml (some different content than default language)
| +- help.xml (some different content than default language)
| +- foo.xml (some different content than default language)
+- site.xml (Default site descriptor)
+- site_de.xml (German site descriptor)
+- pdf.xml (Default pdf descriptor)
+- pdf_de.xml (German pdf descriptor)
Content of pdf.xml:
see attachment pdf.xml
Content of pdf_de.xml:
see attachment pdf_de.xml
Content of pom.xml:
...
...
...
org.apache.maven.plugins
maven-site-plugin
2.2
en,de
org.apache.maven.plugins
maven-pdf-plugin
1.1
${project.reporting.outputDirectory}
false
true
en,de
pdf
site
pdf
If you now execute
mvn site
or
mvn pdf:pdf
and compare the two generated pdfs you'll see that the table of contents is the
one from the pdf.xml in both pdfs. I guess in this case the file pdf_de.xml
isn't used at anytime during the build, because the build (mvn site or mvn
pdf:pdf) is also successful if you have syntax errors in the pdf_de.xml file,
e.g. leave a item tag open in that file and build again.
--
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] Closed: (MNG-4371) NullPointerException in matchPattern
[ http://jira.codehaus.org/browse/MNG-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4371. -- Resolution: Incomplete Fix Version/s: (was: Issues to be reviewed for 3.x) Assignee: Benjamin Bentmann Please retry with the latest M2Eclipse release and refill the issue in their issue tracker if the problem persists. This report doesn't carry any version information which would be required to associate the stack trace with current code. > NullPointerException in matchPattern > > > Key: MNG-4371 > URL: http://jira.codehaus.org/browse/MNG-4371 > Project: Maven 2 & 3 > Issue Type: Bug > Environment: Windows Maven 2.0.9 Eclipse Ganymede >Reporter: Jean-Louis MONTEIRO >Assignee: Benjamin Bentmann > > Hi, > For some unknown reasons, a NullPointerException breaks m2eclipse plugin. > Here is the stacktrace > java.lang.NullPointerException > at > org.apache.maven.artifact.manager.DefaultWagonManager.matchPattern(DefaultWagonManager.java:857) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getMirror(DefaultWagonManager.java:829) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getMirrorRepository(DefaultWagonManager.java:668) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:418) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:335) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:193) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:83) > at > org.maven.ide.eclipse.internal.project.EclipseArtifactResolver.resolve(EclipseArtifactResolver.java:34) > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:552) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:233) > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:131) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:518) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:138) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:88) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:526) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildProjectWithDependencies(DefaultMavenProjectBuilder.java:404) > at > org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies_aroundBody0(MavenEmbedder.java:453) > at > org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies_aroundBody1$advice(MavenEmbedder.java:304) > at > org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies(MavenEmbedder.java:1) > at > org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$MavenProjectReader.execute(MavenProjectManagerImpl.java:1053) > at > org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:995) > at > org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.refresh(MavenProjectManagerImpl.java:377) > at > org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.refresh(MavenProjectManagerImpl.java:351) > at > org.maven.ide.eclipse.internal.project.MavenProjectManagerRefreshJob.run(MavenProjectManagerRefreshJob.java:85) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255801#action_255801
]
Mark Struberg commented on SCM-606:
---
In git author and committer can be different. If I submit a linux patch and
Linus takes and git-applys it to the kernel tree and push it upstream, then you
will find Linus as committer and me as author...
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
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] Closed: (MNG-5013) Allow to condense configuation of plugin parameter beans that commonly require only one value
[
http://jira.codehaus.org/browse/MNG-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5013.
--
Resolution: Fixed
Fix Version/s: 3.0.3
Assignee: Benjamin Bentmann
Done in [r1070102|http://svn.apache.org/viewvc?view=revision&revision=1070102].
The feature is generally only available on the discretion of the plugin author
who needs to implement how the scalar value maps to the overall bean data. To
do so, the bean class in question can be equipped with a method named {{set()}}
like this:
{code:java}
public class Resource
{
private File directory;
public void set( File directory )
{
this.directory = directory;
}
...
}
{code}
> Allow to condense configuation of plugin parameter beans that commonly
> require only one value
> -
>
> Key: MNG-5013
> URL: http://jira.codehaus.org/browse/MNG-5013
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle, POM
>Affects Versions: 3.0.2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0.3
>
>
> Let's take this example configuration snippet:
> {code:xml}
>
>
> src/foo
> true
>
> src/bar
>
> {code}
> Apparently, the last {{}} element is meant as a shorthand form for
> {{src/bar}}.
> Not only does support for this notation save users a few bits of (sometimes
> hated) XML but it also provides plugin authors with a smooth upgrade path say
> when a parameter was initially typed as {{File[]}} but later needs to be
> extended into {{Bean[]}}.
--
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] Closed: (MNG-5012) Allow to configure array-typed plugin parameters from expressions yielding collections and vice versa
[
http://jira.codehaus.org/browse/MNG-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5012.
--
Resolution: Fixed
Fix Version/s: 3.0.3
Assignee: Benjamin Bentmann
Done in [r1070102|http://svn.apache.org/viewvc?view=revision&revision=1070102].
> Allow to configure array-typed plugin parameters from expressions yielding
> collections and vice versa
> -
>
> Key: MNG-5012
> URL: http://jira.codehaus.org/browse/MNG-5012
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle
>Affects Versions: 3.0.2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0.3
>
>
> The distinction between arrays and collections is often times more a low-tech
> thingy than anything else, conceptually, both types are useful to hold zero
> or more items. As such it would be nice if plugin authors can freely choose
> which type works best for their plugin parameters. E.g. many Maven APIs
> provide collections yet arrays currently render the nicer plugin docs
> (component type mentioned). Currently, this is not possible:
> {code:java}
> /** @parameter default-value="${project.compileSourceRoots}" */
> String[] sourceRoots;
> {code}
--
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] Closed: (MNG-5011) Allow to configure array/collection type plugin parameters via system properties
[
http://jira.codehaus.org/browse/MNG-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5011.
--
Resolution: Fixed
Fix Version/s: 3.0.3
Assignee: Benjamin Bentmann
Done in [r1070102|http://svn.apache.org/viewvc?view=revision&revision=1070102].
> Allow to configure array/collection type plugin parameters via system
> properties
>
>
> Key: MNG-5011
> URL: http://jira.codehaus.org/browse/MNG-5011
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Command Line, Plugins and Lifecycle
>Affects Versions: 3.0.2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0.3
>
>
> It would be helpful for plugin authors and users if Maven could configure
> collections/arrays from comma-separated property values, e.g.
> {noformat}
> mvn -Dincludes=*Foo,*Bar,whatever/** goal
> {noformat}
> This allows plugin authors to consequently use the proper data type for
> parameters and avoids doing manual string splitting to please the user's
> occasional need to configure a parameter from the command line.
--
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] Closed: (MNG-3575) Allow hexadecimal parameters
[ http://jira.codehaus.org/browse/MNG-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-3575. -- Resolution: Fixed Fix Version/s: (was: Issues to be reviewed for 3.x) 3.0.3 Assignee: Benjamin Bentmann Added support for hex and octal notations in [r1070102|http://svn.apache.org/viewvc?view=revision&revision=1070102]. > Allow hexadecimal parameters > > > Key: MNG-3575 > URL: http://jira.codehaus.org/browse/MNG-3575 > Project: Maven 2 & 3 > Issue Type: Improvement >Reporter: Marvin Froeder >Assignee: Benjamin Bentmann > Fix For: 3.0.3 > > > I like to ask to hexadecimal support on parameters, like this: > /* >* @parameter default-value="0x869CA7" >*/ > private int defaultBackgroundColor; -- 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] Closed: (MNG-4992) Allow to configure plugin parameters of type java.util.Properties just like a map
[
http://jira.codehaus.org/browse/MNG-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4992.
--
Resolution: Fixed
Done in [r1070102|http://svn.apache.org/viewvc?view=revision&revision=1070102].
> Allow to configure plugin parameters of type java.util.Properties just like a
> map
> -
>
> Key: MNG-4992
> URL: http://jira.codehaus.org/browse/MNG-4992
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle, POM
>Affects Versions: 3.0.2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0.3
>
>
> {{java.util.Properties}} is a {{java.util.Map}}, yet plugin parameters of
> type {{Properties}} cannot be configured like ordinary {{Map}} parameters,
> i.e.:
> {code:xml}
>
> value
>
> {code}
--
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-5013) Allow to condense configuation of plugin parameter beans that commonly require only one value
Allow to condense configuation of plugin parameter beans that commonly require
only one value
-
Key: MNG-5013
URL: http://jira.codehaus.org/browse/MNG-5013
Project: Maven 2 & 3
Issue Type: Improvement
Components: Plugins and Lifecycle, POM
Affects Versions: 3.0.2
Reporter: Benjamin Bentmann
Priority: Minor
Let's take this example configuration snippet:
{code:xml}
src/foo
true
src/bar
{code}
Apparently, the last {{}} element is meant as a shorthand form for
{{src/bar}}.
Not only does support for this notation save users a few bits of (sometimes
hated) XML but it also provides plugin authors with a smooth upgrade path say
when a parameter was initially typed as {{File[]}} but later needs to be
extended into {{Bean[]}}.
--
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-5012) Allow to configure array-typed plugin parameters from expressions yielding collections and vice versa
Allow to configure array-typed plugin parameters from expressions yielding
collections and vice versa
-
Key: MNG-5012
URL: http://jira.codehaus.org/browse/MNG-5012
Project: Maven 2 & 3
Issue Type: Improvement
Components: Plugins and Lifecycle
Affects Versions: 3.0.2
Reporter: Benjamin Bentmann
Priority: Minor
The distinction between arrays and collections is often times more a low-tech
thingy than anything else, conceptually, both types are useful to hold zero or
more items. As such it would be nice if plugin authors can freely choose which
type works best for their plugin parameters. E.g. many Maven APIs provide
collections yet arrays currently render the nicer plugin docs (component type
mentioned). Currently, this is not possible:
{code:java}
/** @parameter default-value="${project.compileSourceRoots}" */
String[] sourceRoots;
{code}
--
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-5011) Allow to configure array/collection type plugin parameters via system properties
Allow to configure array/collection type plugin parameters via system properties
Key: MNG-5011
URL: http://jira.codehaus.org/browse/MNG-5011
Project: Maven 2 & 3
Issue Type: Improvement
Components: Command Line, Plugins and Lifecycle
Affects Versions: 3.0.2
Reporter: Benjamin Bentmann
Priority: Minor
It would be helpful for plugin authors and users if Maven could configure
collections/arrays from comma-separated property values, e.g.
{noformat}
mvn -Dincludes=*Foo,*Bar,whatever/** goal
{noformat}
This allows plugin authors to consequently use the proper data type for
parameters and avoids doing manual string splitting to please the user's
occasional need to configure a parameter from the command line.
--
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] Deleted: (MNG-5010) Allow to configure numeric plugin parameters using hexadecimal or octal notation
[ http://jira.codehaus.org/browse/MNG-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann deleted MNG-5010: --- > Allow to configure numeric plugin parameters using hexadecimal or octal > notation > > > Key: MNG-5010 > URL: http://jira.codehaus.org/browse/MNG-5010 > Project: Maven 2 & 3 > Issue Type: Improvement >Reporter: Benjamin Bentmann >Priority: Minor > > In some contexts, it's more convenient to specify a number in hexadecimal or > octal notation. Plugin authors that currently wish to support this need to > declare the parameter type as String and need to handle the conversion > themselves. This should eventually be supported by the underlying > configuration framework out of the box. -- 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-5010) Allow to configure numeric plugin parameters using hexadecimal or octal notation
Allow to configure numeric plugin parameters using hexadecimal or octal notation Key: MNG-5010 URL: http://jira.codehaus.org/browse/MNG-5010 Project: Maven 2 & 3 Issue Type: Improvement Components: Plugins and Lifecycle, POM Affects Versions: 3.0.2 Reporter: Benjamin Bentmann Priority: Minor In some contexts, it's more convenient to specify a number in hexadecimal or octal notation. Plugin authors that currently wish to support this need to declare the parameter type as String and need to handle the conversion themselves. This should eventually be supported by the underlying configuration framework out of the box. -- 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: (DOXIASITETOOLS-51) site.xml parameter and template variables not documented
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255791#action_255791 ] SebbASF commented on DOXIASITETOOLS-51: --- The link to [2] is entitled "XML Schema Reference for the site descriptor" which could be better worded, for example: "full reference for the site descriptor" > site.xml parameter and template variables not documented > - > > Key: DOXIASITETOOLS-51 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-51 > Project: Maven Doxia Sitetools > Issue Type: Bug >Reporter: SebbASF > > There's no proper documentation on the Maven site descriptor "custom" tag. > It's not mentioned in the main documentation [1], and is only mentioned in > passing in [2] - which in turn is not referenced from [1] > Here are the full details from [2]: > customDOM Custom configuration for use with customized > Velocity templates > The DOM reference above appears to be an instance of Xpp3Dom [3]. > Also, the Doxia code sets various context variables (in DefaultSiteRenderer > ?). > This should all be documented, along with some simple examples, and > referenced as necessary from the Maven site plugin documentation > [1] > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > [2] > http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html > [3] > http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/xml/Xpp3Dom.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: (MSITE-551) custom content not returned correctly
[
http://jira.codehaus.org/browse/MSITE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255790#action_255790
]
SebbASF commented on MSITE-551:
---
2.2
> custom content not returned correctly
> -
>
> Key: MSITE-551
> URL: http://jira.codehaus.org/browse/MSITE-551
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Reporter: SebbASF
>
> Given the following:
> {code:title=site.xml}
>
>
> Content
>
>
> {code}
> and the template snippet:
> {code:title=template.vm}
> $decoration.custom
> {code}
> the output is:
> {noformat}
>
> Content
> {noformat}
> The first line should not be present.
--
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: (MSITE-550) site:site parameter does not work
[
http://jira.codehaus.org/browse/MSITE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255787#action_255787
]
SebbASF commented on MSITE-550:
---
If you build the example, you will see that $dummy is resolved, but $att1 is
not.
> site:site parameter does not work
> --
>
> Key: MSITE-550
> URL: http://jira.codehaus.org/browse/MSITE-550
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: SebbASF
> Attachments: MSITE-550.zip
>
>
> The site:site goal has an optional attributes parameter:
> {quote}
> attributes:
> The template properties for rendering the site.
> * Type: java.util.Map
> * Required: No
> * Expression: ${attributes}
> {quote}
> However this does not work - no parameters are created for the template.
--
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: (MSITE-550) site:site parameter does not work
[
http://jira.codehaus.org/browse/MSITE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SebbASF updated MSITE-550:
--
Attachment: MSITE-550.zip
Here is a simple example.
BTW, don't the unit tests include any examples of using ?
> site:site parameter does not work
> --
>
> Key: MSITE-550
> URL: http://jira.codehaus.org/browse/MSITE-550
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: SebbASF
> Attachments: MSITE-550.zip
>
>
> The site:site goal has an optional attributes parameter:
> {quote}
> attributes:
> The template properties for rendering the site.
> * Type: java.util.Map
> * Required: No
> * Expression: ${attributes}
> {quote}
> However this does not work - no parameters are created for the template.
--
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: (MSITE-553) Incomplete documentation site descriptor inheritance
[ http://jira.codehaus.org/browse/MSITE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255783#action_255783 ] SebbASF commented on MSITE-553: --- Thanks, that's much clearer. > Incomplete documentation site descriptor inheritance > > > Key: MSITE-553 > URL: http://jira.codehaus.org/browse/MSITE-553 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site descriptor > Environment: > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html >Reporter: SebbASF >Assignee: Lukas Theussl >Priority: Minor > Fix For: 2.3 > > > The page > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > section "Inheritance" says: > bq. By default, only the basic settings are inherited. > However it does not say what "basic settings" are. > It appears to be any items outside the body, but this is not very obvious, as > some of these are definitely not "basic" - e.g. and . If it > really means all top-level child elements of the , apart from > , then it would be helpful to say so. -- 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: (MSITE-552) site.xml parameter and template variables not documented
[ http://jira.codehaus.org/browse/MSITE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255782#action_255782 ] Dennis Lundberg commented on MSITE-552: --- Yes the custom element seems to need better documentation, which should be at the Doxia site. In paragraph 3 in [1] has a link to [2]. That should be enough for the Site Plugin portion of this issue. > site.xml parameter and template variables not documented > - > > Key: MSITE-552 > URL: http://jira.codehaus.org/browse/MSITE-552 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Reporter: SebbASF > > There's no proper documentation on the Maven site descriptor "custom" tag. > It's not mentioned in the main documentation [1], and is only mentioned in > passing in [2] - which in turn is not referenced from [1] > Here are the full details from [2]: > customDOM Custom configuration for use with customized > Velocity templates > The DOM reference above appears to be an instance of Xpp3Dom [3]. > Also, the Doxia code sets various context variables (in DefaultSiteRenderer > ?). > This should all be documented, along with some simple examples, and > referenced as necessary from the Maven site plugin documentation > [1] > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > [2] > http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html > [3] > http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/xml/Xpp3Dom.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] Moved: (DOXIASITETOOLS-51) site.xml parameter and template variables not documented
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MSITE-552 to DOXIASITETOOLS-51: - Key: DOXIASITETOOLS-51 (was: MSITE-552) Project: Maven Doxia Sitetools (was: Maven 2.x and 3.x Site Plugin) > site.xml parameter and template variables not documented > - > > Key: DOXIASITETOOLS-51 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-51 > Project: Maven Doxia Sitetools > Issue Type: Bug >Reporter: SebbASF > > There's no proper documentation on the Maven site descriptor "custom" tag. > It's not mentioned in the main documentation [1], and is only mentioned in > passing in [2] - which in turn is not referenced from [1] > Here are the full details from [2]: > customDOM Custom configuration for use with customized > Velocity templates > The DOM reference above appears to be an instance of Xpp3Dom [3]. > Also, the Doxia code sets various context variables (in DefaultSiteRenderer > ?). > This should all be documented, along with some simple examples, and > referenced as necessary from the Maven site plugin documentation > [1] > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > [2] > http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html > [3] > http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/xml/Xpp3Dom.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: (MSITE-551) custom content not returned correctly
[
http://jira.codehaus.org/browse/MSITE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255781#action_255781
]
Dennis Lundberg commented on MSITE-551:
---
Which version of the Site Plugin are you using?
> custom content not returned correctly
> -
>
> Key: MSITE-551
> URL: http://jira.codehaus.org/browse/MSITE-551
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Reporter: SebbASF
>
> Given the following:
> {code:title=site.xml}
>
>
> Content
>
>
> {code}
> and the template snippet:
> {code:title=template.vm}
> $decoration.custom
> {code}
> the output is:
> {noformat}
>
> Content
> {noformat}
> The first line should not be present.
--
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: (MSITE-550) site:site parameter does not work
[
http://jira.codehaus.org/browse/MSITE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255780#action_255780
]
Dennis Lundberg commented on MSITE-550:
---
Do you have a sample project that we can use to test this?
> site:site parameter does not work
> --
>
> Key: MSITE-550
> URL: http://jira.codehaus.org/browse/MSITE-550
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: SebbASF
>
> The site:site goal has an optional attributes parameter:
> {quote}
> attributes:
> The template properties for rendering the site.
> * Type: java.util.Map
> * Required: No
> * Expression: ${attributes}
> {quote}
> However this does not work - no parameters are created for the template.
--
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] Closed: (MNG-5009) StackOverflowError in DefaultProjectBuilder.build when points at current aggregator POM
[
http://jira.codehaus.org/browse/MNG-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5009.
--
Resolution: Fixed
Fix Version/s: 3.0.3
Assignee: Benjamin Bentmann
Fixed in [r1070083|http://svn.apache.org/viewvc?view=revision&revision=1070083].
> StackOverflowError in DefaultProjectBuilder.build when points at
> current aggregator POM
>
>
> Key: MNG-5009
> URL: http://jira.codehaus.org/browse/MNG-5009
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM, Reactor and workspace
>Affects Versions: 2.2.1, 3.0.2
>Reporter: Igor Fedorenko
>Assignee: Benjamin Bentmann
> Fix For: 3.0.3
>
> Attachments: pom.xml
>
>
> I was refactoring m2e unit tests and got the following StackOverflowError
> when rebuilding test artifact repository (see below). To reproduce, run "mvn
> clean" from testLifecycleMappingMetadata of the attached project. I'll
> provide more info when I figure out what causes this.
> {noformat}
> [INFO] Scanning for projects...
> ---
> constituent[0]: file:/opt/maven/lib/maven-embedder-3.0.2.jar
> constituent[1]: file:/opt/maven/lib/maven-settings-3.0.2.jar
> constituent[2]: file:/opt/maven/lib/plexus-utils-2.0.4.jar
> constituent[3]: file:/opt/maven/lib/maven-core-3.0.2.jar
> constituent[4]: file:/opt/maven/lib/maven-model-3.0.2.jar
> constituent[5]: file:/opt/maven/lib/maven-settings-builder-3.0.2.jar
> constituent[6]: file:/opt/maven/lib/plexus-interpolation-1.14.jar
> constituent[7]: file:/opt/maven/lib/plexus-component-annotations-1.5.5.jar
> constituent[8]: file:/opt/maven/lib/plexus-sec-dispatcher-1.3.jar
> constituent[9]: file:/opt/maven/lib/plexus-cipher-1.4.jar
> constituent[10]: file:/opt/maven/lib/maven-repository-metadata-3.0.2.jar
> constituent[11]: file:/opt/maven/lib/maven-artifact-3.0.2.jar
> constituent[12]: file:/opt/maven/lib/maven-plugin-api-3.0.2.jar
> constituent[13]: file:/opt/maven/lib/sisu-inject-plexus-1.4.3.1.jar
> constituent[14]: file:/opt/maven/lib/sisu-inject-bean-1.4.3.1.jar
> constituent[15]: file:/opt/maven/lib/sisu-guice-2.9.1-noaop.jar
> constituent[16]: file:/opt/maven/lib/maven-model-builder-3.0.2.jar
> constituent[17]: file:/opt/maven/lib/maven-aether-provider-3.0.2.jar
> constituent[18]: file:/opt/maven/lib/aether-api-1.9.jar
> constituent[19]: file:/opt/maven/lib/aether-spi-1.9.jar
> constituent[20]: file:/opt/maven/lib/aether-util-1.9.jar
> constituent[21]: file:/opt/maven/lib/aether-impl-1.9.jar
> constituent[22]: file:/opt/maven/lib/maven-compat-3.0.2.jar
> constituent[23]: file:/opt/maven/lib/wagon-provider-api-1.0-beta-7.jar
> constituent[24]: file:/opt/maven/lib/commons-cli-1.2.jar
> constituent[25]: file:/opt/maven/lib/wagon-http-lightweight-1.0-beta-7.jar
> constituent[26]: file:/opt/maven/lib/wagon-http-shared-1.0-beta-7.jar
> constituent[27]: file:/opt/maven/lib/xercesMinimal-1.9.6.2.jar
> constituent[28]: file:/opt/maven/lib/nekohtml-1.9.6.2.jar
> constituent[29]: file:/opt/maven/lib/wagon-file-1.0-beta-7.jar
> constituent[30]: file:/opt/maven/lib/aether-connector-wagon-1.9.jar
> ---
> Exception in thread "main" java.lang.StackOverflowError
> at java.util.Vector.size(Vector.java:268)
> at java.util.Stack.pop(Stack.java:65)
> at
> org.codehaus.plexus.interpolation.PrefixAwareRecursionInterceptor.expressionResolutionFinished(PrefixAwareRecursionInterceptor.java:85)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:246)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:124)
> at
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.interpolateInternal(AbstractStringBasedModelInterpolator.java:241)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:158)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:305)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.run(StringSearchModelInterpolator.java:122)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateObject(StringSearchModelInterpolator.java:75)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateModel(StringSearchModelInterpolator.java:58)
> at
> org.apache.maven.model.buil
[jira] Closed: (MSITE-553) Incomplete documentation site descriptor inheritance
[ http://jira.codehaus.org/browse/MSITE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-553. --- Resolution: Fixed Fix Version/s: 2.3 Assignee: Lukas Theussl Clarified in [r1070079|http://svn.apache.org/viewvc?rev=1070079&view=rev] > Incomplete documentation site descriptor inheritance > > > Key: MSITE-553 > URL: http://jira.codehaus.org/browse/MSITE-553 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site descriptor > Environment: > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html >Reporter: SebbASF >Assignee: Lukas Theussl >Priority: Minor > Fix For: 2.3 > > > The page > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > section "Inheritance" says: > bq. By default, only the basic settings are inherited. > However it does not say what "basic settings" are. > It appears to be any items outside the body, but this is not very obvious, as > some of these are definitely not "basic" - e.g. and . If it > really means all top-level child elements of the , apart from > , then it would be helpful to say so. -- 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-5009) StackOverflowError in DefaultProjectBuilder.build when points at current aggregator POM
[
http://jira.codehaus.org/browse/MNG-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-5009:
---
Component/s: (was: Inheritance and Interpolation)
Reactor and workspace
POM
Affects Version/s: 2.2.1
Summary: StackOverflowError in DefaultProjectBuilder.build when
points at current aggregator POM (was: StackOverflowError in
DefaultProjectBuilder.build)
> StackOverflowError in DefaultProjectBuilder.build when points at
> current aggregator POM
>
>
> Key: MNG-5009
> URL: http://jira.codehaus.org/browse/MNG-5009
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM, Reactor and workspace
>Affects Versions: 2.2.1, 3.0.2
>Reporter: Igor Fedorenko
> Attachments: pom.xml
>
>
> I was refactoring m2e unit tests and got the following StackOverflowError
> when rebuilding test artifact repository (see below). To reproduce, run "mvn
> clean" from testLifecycleMappingMetadata of the attached project. I'll
> provide more info when I figure out what causes this.
> {noformat}
> [INFO] Scanning for projects...
> ---
> constituent[0]: file:/opt/maven/lib/maven-embedder-3.0.2.jar
> constituent[1]: file:/opt/maven/lib/maven-settings-3.0.2.jar
> constituent[2]: file:/opt/maven/lib/plexus-utils-2.0.4.jar
> constituent[3]: file:/opt/maven/lib/maven-core-3.0.2.jar
> constituent[4]: file:/opt/maven/lib/maven-model-3.0.2.jar
> constituent[5]: file:/opt/maven/lib/maven-settings-builder-3.0.2.jar
> constituent[6]: file:/opt/maven/lib/plexus-interpolation-1.14.jar
> constituent[7]: file:/opt/maven/lib/plexus-component-annotations-1.5.5.jar
> constituent[8]: file:/opt/maven/lib/plexus-sec-dispatcher-1.3.jar
> constituent[9]: file:/opt/maven/lib/plexus-cipher-1.4.jar
> constituent[10]: file:/opt/maven/lib/maven-repository-metadata-3.0.2.jar
> constituent[11]: file:/opt/maven/lib/maven-artifact-3.0.2.jar
> constituent[12]: file:/opt/maven/lib/maven-plugin-api-3.0.2.jar
> constituent[13]: file:/opt/maven/lib/sisu-inject-plexus-1.4.3.1.jar
> constituent[14]: file:/opt/maven/lib/sisu-inject-bean-1.4.3.1.jar
> constituent[15]: file:/opt/maven/lib/sisu-guice-2.9.1-noaop.jar
> constituent[16]: file:/opt/maven/lib/maven-model-builder-3.0.2.jar
> constituent[17]: file:/opt/maven/lib/maven-aether-provider-3.0.2.jar
> constituent[18]: file:/opt/maven/lib/aether-api-1.9.jar
> constituent[19]: file:/opt/maven/lib/aether-spi-1.9.jar
> constituent[20]: file:/opt/maven/lib/aether-util-1.9.jar
> constituent[21]: file:/opt/maven/lib/aether-impl-1.9.jar
> constituent[22]: file:/opt/maven/lib/maven-compat-3.0.2.jar
> constituent[23]: file:/opt/maven/lib/wagon-provider-api-1.0-beta-7.jar
> constituent[24]: file:/opt/maven/lib/commons-cli-1.2.jar
> constituent[25]: file:/opt/maven/lib/wagon-http-lightweight-1.0-beta-7.jar
> constituent[26]: file:/opt/maven/lib/wagon-http-shared-1.0-beta-7.jar
> constituent[27]: file:/opt/maven/lib/xercesMinimal-1.9.6.2.jar
> constituent[28]: file:/opt/maven/lib/nekohtml-1.9.6.2.jar
> constituent[29]: file:/opt/maven/lib/wagon-file-1.0-beta-7.jar
> constituent[30]: file:/opt/maven/lib/aether-connector-wagon-1.9.jar
> ---
> Exception in thread "main" java.lang.StackOverflowError
> at java.util.Vector.size(Vector.java:268)
> at java.util.Stack.pop(Stack.java:65)
> at
> org.codehaus.plexus.interpolation.PrefixAwareRecursionInterceptor.expressionResolutionFinished(PrefixAwareRecursionInterceptor.java:85)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:246)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:124)
> at
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.interpolateInternal(AbstractStringBasedModelInterpolator.java:241)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:158)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:305)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.run(StringSearchModelInterpolator.java:122)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateObject(StringSearchModelInterpolator.java:75)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator
[jira] Created: (MSITE-553) Incomplete documentation site descriptor inheritance
Incomplete documentation site descriptor inheritance Key: MSITE-553 URL: http://jira.codehaus.org/browse/MSITE-553 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site descriptor Environment: http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html Reporter: SebbASF Priority: Minor The page http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html section "Inheritance" says: bq. By default, only the basic settings are inherited. However it does not say what "basic settings" are. It appears to be any items outside the body, but this is not very obvious, as some of these are definitely not "basic" - e.g. and . If it really means all top-level child elements of the , apart from , then it would be helpful to say so. -- 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-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255767#action_255767
]
Fabien Bousquet commented on SCM-606:
-
Thanks !!!
I can't review now. So I will review and test tomorrow.
For difference between author and commiter, I don't understand. What is this
difference ?
For my case, I want the last developer which has modified the line (for each
line).
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
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: (MNGSITE-133) Inadequate documentation on Maven modules
Inadequate documentation on Maven modules - Key: MNGSITE-133 URL: http://jira.codehaus.org/browse/MNGSITE-133 Project: Maven Project Web Site Issue Type: Bug Environment: http://maven.apache.org/guides/mini/guide-multiple-modules.html Reporter: SebbASF The page http://maven.apache.org/guides/mini/guide-multiple-modules.html is very brief, considering that it is about the Maven module system. It contains a link for further information, but the link is broken: http://www.sonatype.com/books/maven-book/reference/multimodule.html";> Chapter 6. A Multi-module Project (Maven: The Definitive Guide) I had a look in the guide, but cannot find a suitable target for the link; there appears to be no definitive documentation on modules. Please can this be fixed ASAP as otherwise there is no official documentation for modules AFAICT. -- 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] Issue Comment Edited: (MSITE-490) [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please update this plugin.
[
http://jira.codehaus.org/browse/MSITE-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227043#action_227043
]
Herve Boutemy edited comment on MSITE-490 at 2/12/11 3:19 AM:
--
fixed in maven-site-plugin 3.0-beta-1
[r958428|http://svn.apache.org/viewvc?view=revision&revision=958428]
still need to investigate if this can be fixed in 2.x branch
was (Author: hboutemy):
fixed in maven-site-plugin 3.0-beta-1 r958428
still need to investigate if this can be fixed in 2.x branch
> [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
> instance and no SinkFactory available. Please update this plugin.
>
>
> Key: MSITE-490
> URL: http://jira.codehaus.org/browse/MSITE-490
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0, 2.0.1, 2.1, 2.1.1
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 2.2, 3.0-beta-1
>
>
> ReportDocumentRenderer.renderDocument(...) contains:
> {code:java}if ( report instanceof MavenMultiPageReport )
> {
> ( (MavenMultiPageReport) report ).generate( sink, sf, locale );
> }{code}
> then this message should not be displayed by any plugin using
> maven-reporting-impl 2.2 like seen in MPIR-194
> (note: this wasn't seen before because there was no warning, but this problem
> was already there in 2.0)
--
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] Issue Comment Edited: (MSITE-490) [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please update this plugin.
[
http://jira.codehaus.org/browse/MSITE-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227333#action_227333
]
Herve Boutemy edited comment on MSITE-490 at 2/12/11 3:19 AM:
--
fixed in [r960703|http://svn.apache.org/viewvc?view=revision&revision=960703]
for trunk (2.x)
was (Author: hboutemy):
fixed in r960703 for trunk (2.x)
> [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
> instance and no SinkFactory available. Please update this plugin.
>
>
> Key: MSITE-490
> URL: http://jira.codehaus.org/browse/MSITE-490
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0, 2.0.1, 2.1, 2.1.1
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 2.2, 3.0-beta-1
>
>
> ReportDocumentRenderer.renderDocument(...) contains:
> {code:java}if ( report instanceof MavenMultiPageReport )
> {
> ( (MavenMultiPageReport) report ).generate( sink, sf, locale );
> }{code}
> then this message should not be displayed by any plugin using
> maven-reporting-impl 2.2 like seen in MPIR-194
> (note: this wasn't seen before because there was no warning, but this problem
> was already there in 2.0)
--
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] Issue Comment Edited: (MSITE-465) Add a site:effective-site goal (similar to help:effective-pom)
[
http://jira.codehaus.org/browse/MSITE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226967#action_226967
]
Herve Boutemy edited comment on MSITE-465 at 2/12/11 3:18 AM:
--
done in [r959794|http://svn.apache.org/viewvc?view=revision&revision=959794]
for 2.2 and
[r959796|http://svn.apache.org/viewvc?view=revision&revision=959796] for 3.x
was (Author: hboutemy):
done in r959794 for 2.2 and r959796 for 3.x
> Add a site:effective-site goal (similar to help:effective-pom)
> --
>
> Key: MSITE-465
> URL: http://jira.codehaus.org/browse/MSITE-465
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: New Feature
>Reporter: Andreas Sewe
>Assignee: Herve Boutemy
>Priority: Minor
> Fix For: 2.2, 3.0-beta-1
>
>
> As the {{site.xml}} descriptor supports, just like the POM, property
> expansion and inheritance, it would be helpful to have a
> {{site:effective-site}} goal that shows the {{site.xml}} after property
> expansion and inheritance.
--
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: (MSITE-459) More than one version of 'org.apache.commons.logging.Log' visible in the classpath
[
http://jira.codehaus.org/browse/MSITE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSITE-459:
Description:
site:deploy fails as follows (related to wagon-webdav dependencies?
Commons-logging?).
Reverting to maven-site-plugin:2.0.x works around the issue.
I attach the project zip (appropriate server/dav configuration needed to
reproduce the problem).
{noformat}[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'site'.
[INFO] org.apache.maven.plugins: checking for updates from
maven2-repo-dev-java-net
[INFO] org.apache.maven.plugins: checking for updates from
maven-repository.dev.java.net
[INFO] org.apache.maven.plugins: checking for updates from hosted.repos
[INFO] org.codehaus.mojo: checking for updates from maven2-repo-dev-java-net
[INFO] org.codehaus.mojo: checking for updates from
maven-repository.dev.java.net
[INFO] org.codehaus.mojo: checking for updates from hosted.repos
[INFO]
[INFO] Building CheckboxTree
[INFO]task-segment: [site:deploy]
[INFO]
[INFO] [site:deploy {execution: default-cli}]
WAGON_VERSION: 1.0-beta-2
http://zeus.pin.unifi.it/projectsSites/lablib-checkboxtree_snap - Session:
Disconnecting
http://zeus.pin.unifi.it/projectsSites/lablib-checkboxtree_snap - Session:
Disconnected
[FATAL ERROR] org.apache.maven.plugins.site.SiteDeployMojo#execute() caused a
linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date.
Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1]
urls[0] =
file:/Users/bigagli/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1/maven-site-plugin-2.1.jar
urls[1] =
file:/Users/bigagli/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[2] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jar
urls[3] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2/doxia-core-1.1.2.jar
urls[4] =
file:/Users/bigagli/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
urls[5] =
file:/Users/bigagli/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
urls[6] =
file:/Users/bigagli/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar
urls[7] =
file:/Users/bigagli/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] =
file:/Users/bigagli/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] =
file:/Users/bigagli/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
urls[10] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2/doxia-module-apt-1.1.2.jar
urls[11] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2/doxia-module-xdoc-1.1.2.jar
urls[12] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2/doxia-module-fml-1.1.2.jar
urls[13] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2/doxia-decoration-model-1.1.2.jar
urls[14] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2/doxia-site-renderer-1.1.2.jar
urls[15] =
file:/Users/bigagli/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] =
file:/Users/bigagli/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
urls[17] =
file:/Users/bigagli/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
urls[18] =
file:/Users/bigagli/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
urls[19] = file:/Users/bigagli/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
urls[20] =
file:/Users/bigagli/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.2/maven-doxia-tools-1.2.jar
urls[21] =
file:/Users/bigagli/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
urls[22] =
file:/Users/bigagli/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
urls[23] =
file:/Users/bigagli/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar
urls[24] =
file:/Users/bigagli/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar
urls[25] =
file:/Users/bigagli/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/Users/bigagli/maven/lib/maven-2.2.1-uber.jar
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
Invalid class loader hierarchy. You have more than one version of
'
[jira] Issue Comment Edited: (MSITE-369) remove copy of reporting-api MavenMultiPageReport class
[ http://jira.codehaus.org/browse/MSITE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227334#action_227334 ] Herve Boutemy edited comment on MSITE-369 at 2/12/11 3:17 AM: -- done in [r960704|http://svn.apache.org/viewvc?view=revision&revision=960704] in fact, this class was useless since it was not available in reporting plugins due to Maven class loading separation between plugins was (Author: hboutemy): done in r960704 in fact, this class was useless since it was not available in reporting plugins due to Maven class loading separation between plugins > remove copy of reporting-api MavenMultiPageReport class > --- > > Key: MSITE-369 > URL: http://jira.codehaus.org/browse/MSITE-369 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Task >Affects Versions: 2.0-beta-7 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Minor > Fix For: 2.2 > > > this will force the plugin to have Maven 3.0 as a prerequisite, since this > interface was added in reporting-api 3.0 -- 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
