[jira] Created: (MENFORCER-76) Documentation for regex on requireProperty incorrectly includes quotes around regex
Documentation for regex on requireProperty incorrectly includes quotes around regex --- Key: MENFORCER-76 URL: http://jira.codehaus.org/browse/MENFORCER-76 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Components: Standard Rules Affects Versions: 1.0-beta-1 Environment: Documentation issue. Env. not pertinent. Reporter: Matthew McCullough Priority: Minor Attachments: regexdocumentationfix.diff The documentation page enforcer-rules/src/site/apt/requireProperty.apt (or http://maven.apache.org/enforcer/enforcer-rules/requireProperty.html) shows a demonstration of a regex for the requireProperty rule. It incorrectly includes quotes around the regex when none are required (in fact, causes the regex match to fail). I am including a patch that removes the incorrect quotes around the regex and also provides a second example with a more complex regex. -- 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-4201) Custom packaging break in trunk (rev 784628)
[
http://jira.codehaus.org/browse/MNG-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MNG-4201:
--
Summary: Custom packaging break in trunk (rev 784628) (was: Custom
packaging break in trunk (rev )
> Custom packaging break in trunk (rev 784628)
>
>
> Key: MNG-4201
> URL: http://jira.codehaus.org/browse/MNG-4201
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-3
>Reporter: Olivier Lamy
>Priority: Blocker
>
> Custom packaging doesn't.
> Log output :
> {code}
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecycleExecutor.java:784)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:58)
> at
> org.apache.maven.model.DefaultModelBuilder.build(DefaultModelBuilder.java:174)
> at
> org.apache.maven.model.DefaultModelBuilder.build(DefaultModelBuilder.java:100)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:109)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:84)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:193)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:239)
> at
> org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:181)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:91)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:534)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:167)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun{code}
> {code}
> By example try to run a hudson plugin or run its for the maven-zip-plugin
> which in the maven plugins sandbox.
--
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-4201) Custom packaging break in trunk (rev
Custom packaging break in trunk (rev
-
Key: MNG-4201
URL: http://jira.codehaus.org/browse/MNG-4201
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 3.0-alpha-3
Reporter: Olivier Lamy
Priority: Blocker
Custom packaging doesn't.
Log output :
{code}
java.lang.NullPointerException
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecycleExecutor.java:784)
at
org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:58)
at
org.apache.maven.model.DefaultModelBuilder.build(DefaultModelBuilder.java:174)
at
org.apache.maven.model.DefaultModelBuilder.build(DefaultModelBuilder.java:100)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:109)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:84)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:239)
at
org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:181)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:91)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:534)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:167)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:61)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun{code}
{code}
By example try to run a hudson plugin or run its for the maven-zip-plugin which
in the maven plugins sandbox.
--
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-4197) relocation doesn't work in trunk (rev 784345)
[ http://jira.codehaus.org/browse/MNG-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-4197: -- Attachment: MNG-4197-2.x-code.patch Here a patch which take code from 2.x branch. Let me know if this is ok. Or if someone has better idea with the current trunk code. > relocation doesn't work in trunk (rev 784345) > - > > Key: MNG-4197 > URL: http://jira.codehaus.org/browse/MNG-4197 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Dependencies >Affects Versions: 3.0-alpha-3 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Blocker > Fix For: 3.0-alpha-3 > > Attachments: MNG-4197-2.x-code.patch > > > see it MavenITmng0507ArtifactRelocationTest -- 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-281) Add macro support in FML
[ http://jira.codehaus.org/browse/DOXIA-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-281: -- Attachment: fml-1.0.1.xsd the xsd > Add macro support in FML > > > Key: DOXIA-281 > URL: http://jira.codehaus.org/browse/DOXIA-281 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Fml >Affects Versions: 1.1 >Reporter: Vincent Siveton > Fix For: 1.2 > > Attachments: DOXIA-281.patch, fml-1.0.1.xsd > > > Add macro support in fml files -- 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-4197) relocation doesn't work in trunk (rev 784345)
[ http://jira.codehaus.org/browse/MNG-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-4197: -- Priority: Blocker (was: Major) Fix Version/s: 3.0-alpha-3 > relocation doesn't work in trunk (rev 784345) > - > > Key: MNG-4197 > URL: http://jira.codehaus.org/browse/MNG-4197 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Dependencies >Affects Versions: 3.0-alpha-3 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Blocker > Fix For: 3.0-alpha-3 > > > see it MavenITmng0507ArtifactRelocationTest -- 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: (MNG-3293) Activating more than one profile with the same build plugin results in only one execution
[
http://jira.codehaus.org/browse/MNG-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180268#action_180268
]
Juan M. Tula commented on MNG-3293:
---
Thanks for the explanation, I don't know that is the expected behaviour.
> Activating more than one profile with the same build plugin results in only
> one execution
> -
>
> Key: MNG-3293
> URL: http://jira.codehaus.org/browse/MNG-3293
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle, Profiles
>Affects Versions: 2.0.7
>Reporter: Paudi Moriarty
>Assignee: Benjamin Bentmann
>
> For example:
> It is possible to activate both of these profiles (mvn -Dtest1=true
> -Dtest2=true help:active-profiles lists both profile1 and profile2) however
> only profile2 is run (test1 activated is not echoed)
> {code:xml}
>
> profile1
>
>
> test1
> true
>
>
>
>
>
> maven-antrun-plugin
>
>
> generate-sources
>
> run
>
>
>
> test1 activated
>
>
>
>
>
>
>
>
>
> profile2
>
>
> test2
> true
>
>
>
>
>
> maven-antrun-plugin
>
>
> generate-sources
>
> run
>
>
>
> test2 activated
>
>
>
>
>
>
>
>
> {code}
> Just a guess, but it looks like the executions are not being merged, rather
> the definition of the second plugin overwrites the first.
--
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: (MNG-4200) Build fails on system without svn client
[
http://jira.codehaus.org/browse/MNG-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180259#action_180259
]
Benjamin Bentmann commented on MNG-4200:
Switched plugin to use Java-based SVN provider in
[r784555|http://svn.apache.org/viewvc?view=rev&revision=784555]. Works here,
and for you?
> Build fails on system without svn client
>
>
> Key: MNG-4200
> URL: http://jira.codehaus.org/browse/MNG-4200
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1.0
> Environment: build.log attached
>Reporter: Jethrik
> Attachments: build.log
>
>
> I did a checkout (using TortoiseSVN) from
> https://svn.apache.org/repos/asf/maven/components/branches/maven-2.1.x/, on
> my system which doesn't have the command line svn client installed, causing
> the build to fail as in the attached build.log.
> This is caused by this issue: MOJO-936 in buildnumber-maven-plugin. The
> remedy is to modify maven-core/pom.xml and any other POMs where the plugin is
> used by upgrading the version of that plugin and adding the
> element like so:
> {code:xml}
>
> org.codehaus.mojo
> buildnumber-maven-plugin
> 1.0-beta-3
>
>
> generate-resources
>
> create
>
>
>
>
> false
> false
> 0
> NON-CANONICAL_{0,date,-MM-dd_HH-mm}_{1}
>
> timestamp
> ${user.name}
>
>
>
> {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] Updated: (MNG-4200) Build fails on system without svn client
[
http://jira.codehaus.org/browse/MNG-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4200:
---
Description:
I did a checkout (using TortoiseSVN) from
https://svn.apache.org/repos/asf/maven/components/branches/maven-2.1.x/, on my
system which doesn't have the command line svn client installed, causing the
build to fail as in the attached build.log.
This is caused by this issue: MOJO-936 in buildnumber-maven-plugin. The remedy
is to modify maven-core/pom.xml and any other POMs where the plugin is used by
upgrading the version of that plugin and adding the
element like so:
{code:xml}
org.codehaus.mojo
buildnumber-maven-plugin
1.0-beta-3
generate-resources
create
false
false
0
NON-CANONICAL_{0,date,-MM-dd_HH-mm}_{1}
timestamp
${user.name}
{code}
was:
I did a checkout (using TortoiseSVN) from
https://svn.apache.org/repos/asf/maven/components/branches/maven-2.1.x/, on my
system which doesn't have the command line svn client installed, causing the
build to fail as in the attached build.log.
This is caused by this issue: [#MOJO-936] in buildnumber-maven-plugin. The
remedy is to modify maven-core/pom.xml and any other POMs where the plugin is
used by upgrading the version of that plugin and adding the
element like so:
org.codehaus.mojo
buildnumber-maven-plugin
1.0-beta-3
generate-resources
create
false
false
0
NON-CANONICAL_{0,date,-MM-dd_HH-mm}_{1}
timestamp
${user.name}
> Build fails on system without svn client
>
>
> Key: MNG-4200
> URL: http://jira.codehaus.org/browse/MNG-4200
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1.0
> Environment: build.log attached
>Reporter: Jethrik
> Attachments: build.log
>
>
> I did a checkout (using TortoiseSVN) from
> https://svn.apache.org/repos/asf/maven/components/branches/maven-2.1.x/, on
> my system which doesn't have the command line svn client installed, causing
> the build to fail as in the attached build.log.
> This is caused by this issue: MOJO-936 in buildnumber-maven-plugin. The
> remedy is to modify maven-core/pom.xml and any other POMs where the plugin is
> used by upgrading the version of that plugin and adding the
> element like so:
> {code:xml}
>
> org.codehaus.mojo
> buildnumber-maven-plugin
> 1.0-beta-3
>
>
> generate-resources
>
> create
>
>
>
>
> false
> false
> 0
> NON-CANONICAL_{0,date,-MM-dd_HH-mm}_{1}
>
> timestamp
> ${user.name}
>
>
>
> {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] Updated: (DOXIA-281) Add macro support in FML
[ http://jira.codehaus.org/browse/DOXIA-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-281: -- Attachment: DOXIA-281.patch Here is the patch Notes: * we need to update Fml XSD references in the documentation and in some tests (doc/site renderer) * we need to redeploy the 1.0.1 Xsd > Add macro support in FML > > > Key: DOXIA-281 > URL: http://jira.codehaus.org/browse/DOXIA-281 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Fml >Affects Versions: 1.1 >Reporter: Vincent Siveton > Fix For: 1.2 > > Attachments: DOXIA-281.patch > > > Add macro support in fml files -- 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-3375) Repository entries with same id are ignored
[ http://jira.codehaus.org/browse/MNG-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-3375. -- Assignee: Benjamin Bentmann Resolution: Duplicate Fix Version/s: (was: 2.0.11) > Repository entries with same id are ignored > --- > > Key: MNG-3375 > URL: http://jira.codehaus.org/browse/MNG-3375 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Carlos Sanchez >Assignee: Benjamin Bentmann >Priority: Critical > Attachments: MNG-3375-IT.tar.gz, MNG-3375-maven-project.patch > > > If two entries have the same id one of them is ignored with no > warning or error. > IIRC this worked with previous versions of maven, giving the same id allowed > you to share the configuration in the settings.xml file (it may have been for > deployment only though) -- 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: (MINSTALL-62) version error
[ http://jira.codehaus.org/browse/MINSTALL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MINSTALL-62. - Assignee: Benjamin Bentmann Resolution: Cannot Reproduce > version error > - > > Key: MINSTALL-62 > URL: http://jira.codehaus.org/browse/MINSTALL-62 > Project: Maven 2.x Install Plugin > Issue Type: Bug > Environment: ERROR: JAVA_HOME is set to an invalid directory. > JAVA_HOME = "C:\Program Files\Java\jdk1.6.0_10" > Please set the JAVA_HOME variable in your environment to match the > location of your Java installation >Reporter: karunanayake >Assignee: Benjamin Bentmann > > After my installation mvn --version is correctly running.(mvn 2.0.10).Then, > when i'm going to create a package in my mvn project this error was displayed > & again my mvn --version not worked. -- 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-3293) Activating more than one profile with the same build plugin results in only one execution
[
http://jira.codehaus.org/browse/MNG-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-3293.
--
Assignee: Benjamin Bentmann
Resolution: Not A Bug
Fix Version/s: (was: 2.2.x)
This works as designed. The two {{}} elements don't have an {{}}
so their identifiers default to {{default}} (cf. [Maven Model
Spec|http://maven.apache.org/ref/current/maven-model/maven.html#class_execution].
It's the very purpose of these ids to enable merging of POM parts that have
the same id.
If you want the profiles to have additive effects, just assign distinct ids to
the executions.
> Activating more than one profile with the same build plugin results in only
> one execution
> -
>
> Key: MNG-3293
> URL: http://jira.codehaus.org/browse/MNG-3293
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle, Profiles
>Affects Versions: 2.0.7
>Reporter: Paudi Moriarty
>Assignee: Benjamin Bentmann
>
> For example:
> It is possible to activate both of these profiles (mvn -Dtest1=true
> -Dtest2=true help:active-profiles lists both profile1 and profile2) however
> only profile2 is run (test1 activated is not echoed)
> {code:xml}
>
> profile1
>
>
> test1
> true
>
>
>
>
>
> maven-antrun-plugin
>
>
> generate-sources
>
> run
>
>
>
> test1 activated
>
>
>
>
>
>
>
>
>
> profile2
>
>
> test2
> true
>
>
>
>
>
> maven-antrun-plugin
>
>
> generate-sources
>
> run
>
>
>
> test2 activated
>
>
>
>
>
>
>
>
> {code}
> Just a guess, but it looks like the executions are not being merged, rather
> the definition of the second plugin overwrites the first.
--
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-3293) Activating more than one profile with the same build plugin results in only one execution
[
http://jira.codehaus.org/browse/MNG-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3293:
---
Description:
For example:
It is possible to activate both of these profiles (mvn -Dtest1=true
-Dtest2=true help:active-profiles lists both profile1 and profile2) however
only profile2 is run (test1 activated is not echoed)
{code:xml}
profile1
test1
true
maven-antrun-plugin
generate-sources
run
test1 activated
profile2
test2
true
maven-antrun-plugin
generate-sources
run
test2 activated
{code}
Just a guess, but it looks like the executions are not being merged, rather the
definition of the second plugin overwrites the first.
was:
For example:
It is possible to activate both of these profiles (mvn -Dtest1=true
-Dtest2=true help:active-profiles lists both profile1 and profile2) however
only profile2 is run (test1 activated is not echoed)
profile1
test1
true
maven-antrun-plugin
generate-sources
run
test1 activated
profile2
test2
true
maven-antrun-plugin
generate-sources
run
test2 activated
Just a guess, but it looks like the executions are not being merged, rather the
definition of the second plugin overwrites the first.
> Activating more than one profile with the same build plugin results in only
> one execution
> -
>
> Key: MNG-3293
> URL: http://jira.codehaus.org/browse/MNG-3293
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle, Profiles
>Affects Versions: 2.0.7
>Reporter: Paudi Moriarty
> Fix For: 2.2.x
>
>
> For example:
> It is possible to activate both of these profiles (mvn -Dtest1=true
> -Dtest2=true help:active-profiles lists both profile1 and profile2) however
> only profile2 is run (test1 activated is not echoed)
> {code:xml}
>
> profile1
>
>
> test1
> true
>
>
>
>
>
> maven-antrun-plugin
>
>
> generate-sources
>
> run
>
>
>
> test1 activated
>
>
>
>
>
>
>
>
>
> profile2
>
>
> test2
> true
>
>
>
>
>
> maven-antrun-plugin
>
>
> generate-sources
>
> run
>
>
>
> test2 activated
>
>
>
>
>
>
>
>
> {code}
> Just a guess, but it looks like the executions are not being merged, rather
> the definition of the second plugin overwrites the first.
--
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: (DOXIA-342) title and author are not generated for XHTML output
[ http://jira.codehaus.org/browse/DOXIA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed DOXIA-342. - Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 1.1.1 fixed in [r784534|http://svn.apache.org/viewvc?rev=784534&view=rev], snapshot deployed > title and author are not generated for XHTML output > --- > > Key: DOXIA-342 > URL: http://jira.codehaus.org/browse/DOXIA-342 > Project: Maven Doxia > Issue Type: Bug > Components: Book >Affects Versions: 1.1, 1.1.1 >Reporter: Arne Limburg >Assignee: Vincent Siveton > Fix For: 1.1.1 > > Attachments: XHtmlBookRenderer.patch, XhtmlBookSink.patch > > > XHTML output of books generates an empty title-tag and no author-tag -- 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-404) site:stage creates wrong links on Linux
[
http://jira.codehaus.org/browse/MSITE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179715#action_179715
]
Dennis Lundberg edited comment on MSITE-404 at 6/14/09 5:06 AM:
I've traced this down to
DefaultDecorationModelInheritanceAssembler#resolvePaths( final DecorationModel
decoration, final String baseUrl ) in doxia-decoration-model. But then I'm
stuck. Two things happen in that method:
# The href part of a menuitem that is in the site.xml file is lost (might be
other elements containing paths as well)
# The path is resolved into something that is just plain weird:
{noformat}
..//../
{noformat}
was (Author: dennislundberg):
I've traced this down to
DefaultDecorationModelInheritanceAssembler#resolvePaths( final DecorationModel
decoration, final String baseUrl ) in doxia-decoration-model. But the I'm
stuck. Two things happen in that method:
# The href part of a menuitem that is in the site.xml file is lost (might be
other elements containing paths as well)
# The path is resolved into something that is just plain weird:
{noformat}
..//../
{noformat}
> site:stage creates wrong links on Linux
> ---
>
> Key: MSITE-404
> URL: http://jira.codehaus.org/browse/MSITE-404
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: relative links, site descriptor
>Affects Versions: 2.0
> Environment: Linux
>Reporter: Lukas Theussl
> Attachments: MSITE-404.tar.gz
>
>
> site:stage creates wrong links in the navigation menu, something is messed up
> with the relative-path resolution. The same links created with site:site are
> correct.
> Note that this has nothing to do with multi-module setups (as reported
> before: MSITE-275, MSITE-395), it happens on a simple project.
> Also it seems to be Unix specific as vsiveton told me it works on Windows.
--
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: (MAVENUPLOAD-2485) Upload PDF core font information
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180253#action_180253 ] Jukka Zitting commented on MAVENUPLOAD-2485: As a related note, see the following issues for a more background on the licensing status of the included files: https://issues.apache.org/jira/browse/LEGAL-35 https://issues.apache.org/jira/browse/LEGAL-36 > Upload PDF core font information > > > Key: MAVENUPLOAD-2485 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2485 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jukka Zitting > > I'd like to have the PDF core font information files from > http://www.adobe.com/devnet/font/#pcfi uploaded to the central Maven > repository. I have prepared an upload bundle with the coordinates > com.adobe.pdf:pcfi:2009.06.14 for this. Adobe gives permission to > redistribute the included files in unmodified form. See > http://jukka.zitting.name/2009/com.adobe.pdf/LICENSE.txt for the licensing > details (also available as META-INF/LICENSE.txt inside the bundled > pcfi-2009.06.14.jar). > Note that I am *not* affiliated with Adobe in any way, so I'm not sure if > it's OK for me to propose uploading stuff under the groupId com.adobe.pdf. As > an alternative, see > http://jukka.zitting.name/2009/name.zitting.jukka/pcfi-2009.06.14-bundle.jar > for an upload bundle with the coordinates name.zitting.jukka:pcfi:2009.06.14 > based on my personal domain name. Other than that the bundles are identical > (e.g. both store the font information files under com/adobe/pdf/pcfi). -- 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: (MAVENUPLOAD-2485) Upload PDF core font information
Upload PDF core font information Key: MAVENUPLOAD-2485 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2485 Project: Maven Upload Requests Issue Type: Wish Reporter: Jukka Zitting I'd like to have the PDF core font information files from http://www.adobe.com/devnet/font/#pcfi uploaded to the central Maven repository. I have prepared an upload bundle with the coordinates com.adobe.pdf:pcfi:2009.06.14 for this. Adobe gives permission to redistribute the included files in unmodified form. See http://jukka.zitting.name/2009/com.adobe.pdf/LICENSE.txt for the licensing details (also available as META-INF/LICENSE.txt inside the bundled pcfi-2009.06.14.jar). Note that I am *not* affiliated with Adobe in any way, so I'm not sure if it's OK for me to propose uploading stuff under the groupId com.adobe.pdf. As an alternative, see http://jukka.zitting.name/2009/name.zitting.jukka/pcfi-2009.06.14-bundle.jar for an upload bundle with the coordinates name.zitting.jukka:pcfi:2009.06.14 based on my personal domain name. Other than that the bundles are identical (e.g. both store the font information files under com/adobe/pdf/pcfi). -- 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
