[jira] Commented: (MCHANGES-165) Using type=update but the result says Fixes [bug...]
[ http://jira.codehaus.org/browse/MCHANGES-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184947#action_184947 ] Lukas Theussl commented on MCHANGES-165: Olivier, I understand that this is still a valid request for improvement. Ie, if type=update, the text linking to an issue should say See [ticket] instead of Fixes [ticket]. Or did you mean that this is 'Won't fix'? Using type=update but the result says Fixes [bug...] Key: MCHANGES-165 URL: http://jira.codehaus.org/browse/MCHANGES-165 Project: Maven 2.x Changes Plugin Issue Type: Improvement Affects Versions: 2.1 Environment: All Reporter: Karl Heinz Marbaise Assignee: Olivier Lamy Priority: Minor If i use the type=updated in an entry of the changes.xml file the result site will show the word Fixes . IMHO it should be Refs or something different than Fixes cause that issue is not fixed yet it is updated instead. -- 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: (MWAR-209) modelEncoding com.thoughtworks.xstream.mapper.CannotResolveClassException
[ http://jira.codehaus.org/browse/MWAR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MWAR-209. Assignee: Stephane Nicoll Resolution: Duplicate Fix Version/s: 2.1 modelEncoding com.thoughtworks.xstream.mapper.CannotResolveClassException - Key: MWAR-209 URL: http://jira.codehaus.org/browse/MWAR-209 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1-beta-1 Environment: Mac OS X 10.5, Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02-83, mixed mode) Reporter: Benjamin Reed Assignee: Stephane Nicoll Fix For: 2.1 Attachments: model-failure.zip I get the same error as MWAR-191, a CannotResolveClassException using Maven 2.2.0 and the maven 2.x WAR plugin. Originally we were getting the maven war plugin 2.1-alpha-2 because of some other build environment stuff, but I've tried forcing it to 2.1-beta-1 for this build and it still happens. If I force it to the 2.0.2 plugin, it passes building. Attached is mvn -X output using the 2.1-beta-1 WAR plugin. -- 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-4257) Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version
[ http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184951#action_184951 ] Joerg Schaible commented on MNG-4257: - @Brian: Actually there is really an issue with this! Please have a look at all the discussion regarding naming schemes on commons-dev on what to do about upcoming commons releases (e.g. like commons-lang-3.0) that will make use of the JDK 5, improve and optimize API itself and drop all the old deprecated stuff. Basically we agreed that we will release a version that can be used side-by-side with a jar from the commons-lang-2.x series (well, we have no real choice here, the library is used in a lot of deps), but the current naming scheme will force us to name the next version with something along to org.apache.commons:commons-lang3:3.x. Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version Key: MNG-4257 URL: http://jira.codehaus.org/browse/MNG-4257 Project: Maven 2 Issue Type: New Feature Reporter: Alexandre Navarro Assignee: Brian Fox Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version. For instance, when you have two versions of a jar with a refactoring of a package like dozer 4 and 5. In my application, I use dozer 5 but I have a dependency which uses dozer 4. As maven considers by default all libs are ascendant compatibility, I don't have dozer 4 in my classpath and so my depency does not work. It can be useful to force not to resolve some conflict. I don't think it is possible to do that with maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-433) Add parameter remoteTagging to release:branch (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184953#action_184953 ] Boris Maras commented on MRELEASE-433: -- I think this is a duplicate of MRELEASE-461 Add parameter remoteTagging to release:branch (to prevent issue with svn 1.5.0) - Key: MRELEASE-433 URL: http://jira.codehaus.org/browse/MRELEASE-433 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0-beta-9 Environment: svn version 1.5.0 Reporter: Pablo I have the same problem than [http://jira.codehaus.org/browse/MRELEASE-427] when executing mvn release:branch. It would be useful for me to add the -DremoteTagging argument also when making branches. Thank you. -- 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: (MRELEASE-433) Add parameter remoteTagging to release:branch (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-433. - Assignee: Olivier Lamy Resolution: Duplicate Fix Version/s: 2.0-beta-10 Add parameter remoteTagging to release:branch (to prevent issue with svn 1.5.0) - Key: MRELEASE-433 URL: http://jira.codehaus.org/browse/MRELEASE-433 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0-beta-9 Environment: svn version 1.5.0 Reporter: Pablo Assignee: Olivier Lamy Fix For: 2.0-beta-10 I have the same problem than [http://jira.codehaus.org/browse/MRELEASE-427] when executing mvn release:branch. It would be useful for me to add the -DremoteTagging argument also when making branches. Thank you. -- 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] Reopened: (MNG-4184) [regression] maven2.1 fails with cyclic dependency in case of extension/dependency for report-plugin to reactor-project
[
http://jira.codehaus.org/browse/MNG-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Hohwiller reopened MNG-4184:
-
Same problem occurs in maven 2.2 if you have 3 levels of poms:
* root (with dependency on module setup)
* child1
* setup
[regression] maven2.1 fails with cyclic dependency in case of
extension/dependency for report-plugin to reactor-project
---
Key: MNG-4184
URL: http://jira.codehaus.org/browse/MNG-4184
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.1.0
Reporter: Jörg Hohwiller
Assignee: John Casey
Fix For: 2.2.0
In my project (https://m-m-m.svn.sourceforge.net/svnroot/m-m-m/trunk/)
I am doing exactly what maven-checkstyle-plugin suggests as best practice for
multi-module-builds:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
Howerver when I upgrade to maven 2.1 my build does not work anymore, while
maven 2.0.10 works fine:
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='net.sf.m-
m-m:mmm-setup'}' and 'Vertex{label='net.sf.m-m-m:mmm-setup'}' introduces to
cycle in the graph net.s
f.m-m-m:mmm-setup -- net.sf.m-m-m:mmm-setup
Indeed the module mmm-setup inherits from the toplevel-pom and therefore has
a maven-checkstyle-plugin
with a dependency on itself. However this worked with maven 2.0.x and if this
is NOT going to be
fixed in 2.1, you need to supply an acceptable workaround and update
instructions such as
the one linked above. Please also note that such config-moudles
(net.sf.m-m-m:mmm-setup or
com.example.whizbang:build-tools) should typically be available in IDE and
other modules might
depend on them so they have to be part of the reactor for eclipse:eclipse.
--
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: (MNG-4184) [regression] maven2.1 fails with cyclic dependency in case of extension/dependency for report-plugin to reactor-project
[
http://jira.codehaus.org/browse/MNG-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184954#action_184954
]
Jörg Hohwiller edited comment on MNG-4184 at 7/27/09 2:55 AM:
--
Same problem occurs in maven 2.2 if you have 3 levels of poms:
* root (with dependency on module setup, modules=child1, ...)
* child1 (parent=root, modules=setup,...)
* setup (root=child1)
was (Author: joerg.hohwil...@sdm.de):
Same problem occurs in maven 2.2 if you have 3 levels of poms:
* root (with dependency on module setup)
* child1
* setup
[regression] maven2.1 fails with cyclic dependency in case of
extension/dependency for report-plugin to reactor-project
---
Key: MNG-4184
URL: http://jira.codehaus.org/browse/MNG-4184
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.1.0
Reporter: Jörg Hohwiller
Assignee: John Casey
Fix For: 2.2.0
In my project (https://m-m-m.svn.sourceforge.net/svnroot/m-m-m/trunk/)
I am doing exactly what maven-checkstyle-plugin suggests as best practice for
multi-module-builds:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
Howerver when I upgrade to maven 2.1 my build does not work anymore, while
maven 2.0.10 works fine:
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='net.sf.m-
m-m:mmm-setup'}' and 'Vertex{label='net.sf.m-m-m:mmm-setup'}' introduces to
cycle in the graph net.s
f.m-m-m:mmm-setup -- net.sf.m-m-m:mmm-setup
Indeed the module mmm-setup inherits from the toplevel-pom and therefore has
a maven-checkstyle-plugin
with a dependency on itself. However this worked with maven 2.0.x and if this
is NOT going to be
fixed in 2.1, you need to supply an acceptable workaround and update
instructions such as
the one linked above. Please also note that such config-moudles
(net.sf.m-m-m:mmm-setup or
com.example.whizbang:build-tools) should typically be available in IDE and
other modules might
depend on them so they have to be part of the reactor for eclipse:eclipse.
--
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-4260) Remove old-school reactor mode
Remove old-school reactor mode -- Key: MNG-4260 URL: http://jira.codehaus.org/browse/MNG-4260 Project: Maven 2 Issue Type: Task Components: Command Line Affects Versions: 3.0-alpha-3 Reporter: Benjamin Bentmann Priority: Minor With the introduction of the make-like reactor mode in MNG-2576, there's little to no use for the old-style reactor mode with glob patterns, see also [Removal of old-school reactor mode from Maven 3.x|http://markmail.org/thread/7ztzhcg62yjcqmpb] -- 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-4260) Remove old-school reactor mode
[ http://jira.codehaus.org/browse/MNG-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4260. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 3.0-alpha-3 Done in [r798081|http://svn.apache.org/viewvc?view=revrevision=798081]. Remove old-school reactor mode -- Key: MNG-4260 URL: http://jira.codehaus.org/browse/MNG-4260 Project: Maven 2 Issue Type: Task Components: Command Line Affects Versions: 3.0-alpha-3 Reporter: Benjamin Bentmann Assignee: Benjamin Bentmann Priority: Minor Fix For: 3.0-alpha-3 With the introduction of the make-like reactor mode in MNG-2576, there's little to no use for the old-style reactor mode with glob patterns, see also [Removal of old-school reactor mode from Maven 3.x|http://markmail.org/thread/7ztzhcg62yjcqmpb] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-338) Section numbering and links
[ http://jira.codehaus.org/browse/DOXIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184963#action_184963 ] Nathan Sowatskey commented on DOXIA-338: Hi What is the status on this patch please? Thanks Nathan Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Assignee: Vincent Siveton Attachments: DOXIA-338.diff, doxia-site-test.zip, doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- 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-338) Section numbering and links
[ http://jira.codehaus.org/browse/DOXIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIA-338: Fix Version/s: 1.1.2 Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Assignee: Vincent Siveton Fix For: 1.1.2 Attachments: DOXIA-338.diff, doxia-site-test.zip, doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- 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: (DOXIASITETOOLS-29) PathUtils.getRelativePath returns different results on Windows and Linux
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIASITETOOLS-29: Assignee: Lukas Theussl Fix Version/s: 1.1.2 PathUtils.getRelativePath returns different results on Windows and Linux Key: DOXIASITETOOLS-29 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-29 Project: Maven Doxia Sitetools Issue Type: Bug Components: Decoration model Affects Versions: 1.1.1 Reporter: Lukas Theussl Assignee: Lukas Theussl Priority: Critical Fix For: 1.1.2 If one of the arguments is a relative path already, results are different. This is due to PLXUTILS-116 and causes MSITE-404. -- 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: (DOXIASITETOOLS-29) PathUtils.getRelativePath returns different results on Windows and Linux
PathUtils.getRelativePath returns different results on Windows and Linux Key: DOXIASITETOOLS-29 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-29 Project: Maven Doxia Sitetools Issue Type: Bug Components: Decoration model Affects Versions: 1.1.1 Reporter: Lukas Theussl Priority: Critical If one of the arguments is a relative path already, results are different. This is due to PLXUTILS-116 and causes MSITE-404. -- 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: (MDEPLOY-101) Deploying javadoc or sources file without generating POM causes NPE in VersionExpressionTransformation.transformVersions(VersionExpressionTransformation.java:203)
[ http://jira.codehaus.org/browse/MDEPLOY-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184984#action_184984 ] rt15 commented on MDEPLOY-101: -- Same as http://jira.codehaus.org/browse/MDEPLOY-84. Deploying javadoc or sources file without generating POM causes NPE in VersionExpressionTransformation.transformVersions(VersionExpressionTransformation.java:203) -- Key: MDEPLOY-101 URL: http://jira.codehaus.org/browse/MDEPLOY-101 Project: Maven 2.x Deploy Plugin Issue Type: Bug Components: deploy:deploy-file Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) Java version: 1.6.0_07 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.5.6 arch: x86_64 Family: mac Reporter: Martin Burger If I deploy a sources or javadoc file (with proper classifier set) without generating a POM (generatePom=false), Maven throws a NullPointerException: $ mvn deploy:deploy-file \ -Dfile=javassist-sources.jar \ -Dclassifier=sources \ -DgroupId=javassist \ -DartifactId=javassist \ -Dversion=3.10.0.GA \ -Dpackaging=jar \ -DgeneratePom=false \ -DrepositoryId=thirdparty \ -Durl=dav:https://***/nexus/content/repositories/thirdparty [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] [INFO] Building Javassist [INFO]task-segment: [deploy:deploy-file] (aggregator-style) [INFO] [INFO] [deploy:deploy-file] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.project.artifact.VersionExpressionTransformation.transformVersions(VersionExpressionTransformation.java:203) at org.apache.maven.project.artifact.VersionExpressionTransformation.transformForDeployment(VersionExpressionTransformation.java:94) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForDeployment(DefaultArtifactTransformationManager.java:78) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86) at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:240) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) If I set generatePom to true, it will work. -- 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: (MDEPLOY-101) Deploying javadoc or sources file without generating POM causes NPE in VersionExpressionTransformation.transformVersions(VersionExpressionTransformation.java:203)
[ http://jira.codehaus.org/browse/MDEPLOY-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184985#action_184985 ] rt15 commented on MDEPLOY-101: -- However I also would be very interested in a workaround, because I cannot update my maven version... Deploying javadoc or sources file without generating POM causes NPE in VersionExpressionTransformation.transformVersions(VersionExpressionTransformation.java:203) -- Key: MDEPLOY-101 URL: http://jira.codehaus.org/browse/MDEPLOY-101 Project: Maven 2.x Deploy Plugin Issue Type: Bug Components: deploy:deploy-file Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) Java version: 1.6.0_07 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.5.6 arch: x86_64 Family: mac Reporter: Martin Burger If I deploy a sources or javadoc file (with proper classifier set) without generating a POM (generatePom=false), Maven throws a NullPointerException: $ mvn deploy:deploy-file \ -Dfile=javassist-sources.jar \ -Dclassifier=sources \ -DgroupId=javassist \ -DartifactId=javassist \ -Dversion=3.10.0.GA \ -Dpackaging=jar \ -DgeneratePom=false \ -DrepositoryId=thirdparty \ -Durl=dav:https://***/nexus/content/repositories/thirdparty [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] [INFO] Building Javassist [INFO]task-segment: [deploy:deploy-file] (aggregator-style) [INFO] [INFO] [deploy:deploy-file] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.project.artifact.VersionExpressionTransformation.transformVersions(VersionExpressionTransformation.java:203) at org.apache.maven.project.artifact.VersionExpressionTransformation.transformForDeployment(VersionExpressionTransformation.java:94) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForDeployment(DefaultArtifactTransformationManager.java:78) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86) at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:240) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) If I set generatePom to true, it will work. -- 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:
[jira] Closed: (DOXIASITETOOLS-29) PathUtils.getRelativePath returns different results on Windows and Linux
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIASITETOOLS-29. --- Resolution: Fixed Fixed in [r798148|http://svn.apache.org/viewvc?view=revrevision=798148] PathUtils.getRelativePath returns different results on Windows and Linux Key: DOXIASITETOOLS-29 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-29 Project: Maven Doxia Sitetools Issue Type: Bug Components: Decoration model Affects Versions: 1.1.1 Reporter: Lukas Theussl Assignee: Lukas Theussl Priority: Critical Fix For: 1.1.2 If one of the arguments is a relative path already, results are different. This is due to PLXUTILS-116 and causes MSITE-404. -- 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: (MDEPLOY-101) Deploying javadoc or sources file without generating POM causes NPE in VersionExpressionTransformation.transformVersions(VersionExpressionTransformation.java:203)
[ http://jira.codehaus.org/browse/MDEPLOY-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184994#action_184994 ] rt15 commented on MDEPLOY-101: -- Same as http://jira.codehaus.org/browse/MDEPLOY-84. Deploying javadoc or sources file without generating POM causes NPE in VersionExpressionTransformation.transformVersions(VersionExpressionTransformation.java:203) -- Key: MDEPLOY-101 URL: http://jira.codehaus.org/browse/MDEPLOY-101 Project: Maven 2.x Deploy Plugin Issue Type: Bug Components: deploy:deploy-file Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) Java version: 1.6.0_07 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.5.6 arch: x86_64 Family: mac Reporter: Martin Burger If I deploy a sources or javadoc file (with proper classifier set) without generating a POM (generatePom=false), Maven throws a NullPointerException: $ mvn deploy:deploy-file \ -Dfile=javassist-sources.jar \ -Dclassifier=sources \ -DgroupId=javassist \ -DartifactId=javassist \ -Dversion=3.10.0.GA \ -Dpackaging=jar \ -DgeneratePom=false \ -DrepositoryId=thirdparty \ -Durl=dav:https://***/nexus/content/repositories/thirdparty [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] [INFO] Building Javassist [INFO]task-segment: [deploy:deploy-file] (aggregator-style) [INFO] [INFO] [deploy:deploy-file] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.project.artifact.VersionExpressionTransformation.transformVersions(VersionExpressionTransformation.java:203) at org.apache.maven.project.artifact.VersionExpressionTransformation.transformForDeployment(VersionExpressionTransformation.java:94) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForDeployment(DefaultArtifactTransformationManager.java:78) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86) at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:240) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) If I set generatePom to true, it will work. -- 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-4184) [regression] maven2.1 fails with cyclic dependency in case of extension/dependency for report-plugin to reactor-project
[
http://jira.codehaus.org/browse/MNG-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184995#action_184995
]
Paul Benedict commented on MNG-4184:
This issue was reopened, but I created MNG-4253 to track the extension bug
because 2.2 was already in RC mode. Anyway, if the new issue is not needed,
please close.
[regression] maven2.1 fails with cyclic dependency in case of
extension/dependency for report-plugin to reactor-project
---
Key: MNG-4184
URL: http://jira.codehaus.org/browse/MNG-4184
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.1.0
Reporter: Jörg Hohwiller
Assignee: John Casey
Fix For: 2.2.0
In my project (https://m-m-m.svn.sourceforge.net/svnroot/m-m-m/trunk/)
I am doing exactly what maven-checkstyle-plugin suggests as best practice for
multi-module-builds:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
Howerver when I upgrade to maven 2.1 my build does not work anymore, while
maven 2.0.10 works fine:
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='net.sf.m-
m-m:mmm-setup'}' and 'Vertex{label='net.sf.m-m-m:mmm-setup'}' introduces to
cycle in the graph net.s
f.m-m-m:mmm-setup -- net.sf.m-m-m:mmm-setup
Indeed the module mmm-setup inherits from the toplevel-pom and therefore has
a maven-checkstyle-plugin
with a dependency on itself. However this worked with maven 2.0.x and if this
is NOT going to be
fixed in 2.1, you need to supply an acceptable workaround and update
instructions such as
the one linked above. Please also note that such config-moudles
(net.sf.m-m-m:mmm-setup or
com.example.whizbang:build-tools) should typically be available in IDE and
other modules might
depend on them so they have to be part of the reactor for eclipse:eclipse.
--
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-2530) TestNG 5.10
TestNG 5.10 --- Key: MAVENUPLOAD-2530 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2530 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Beust Attachments: testng-5.10beta-bundle.jar -- 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: (MSITE-419) Update to Doxia 1.1.2
Update to Doxia 1.1.2 - Key: MSITE-419 URL: http://jira.codehaus.org/browse/MSITE-419 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0 Reporter: Lukas Theussl -- 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-419) Update to Doxia 1.1.2
[ http://jira.codehaus.org/browse/MSITE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-419: Fix Version/s: 2.1 Update to Doxia 1.1.2 - Key: MSITE-419 URL: http://jira.codehaus.org/browse/MSITE-419 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0 Reporter: Lukas Theussl Fix For: 2.1 -- 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-121) Generated html files contain inconsistent new lines
[ http://jira.codehaus.org/browse/MSITE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-121: Fix Version/s: (was: 2.1) Generated html files contain inconsistent new lines --- Key: MSITE-121 URL: http://jira.codehaus.org/browse/MSITE-121 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-4 Reporter: Carlos Sanchez -- 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-94) http://maven.apache.org/guides/mini/guide-embedding-m2.html does not exist
http://maven.apache.org/guides/mini/guide-embedding-m2.html does not exist -- Key: MNGSITE-94 URL: http://jira.codehaus.org/browse/MNGSITE-94 Project: Maven 2 Project Web Site Issue Type: Bug Environment: All Reporter: Karl Heinz Marbaise Priority: Critical The link to on the guides page (http://maven.apache.org/guides/) to the embedding Maven 2 is targeting on a complete empty site. Not 404 etc. Just a clean page. -- 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-4052) import scope dependencies prefer to download pom rather than find it in the current project
[
http://jira.codehaus.org/browse/MNG-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4052.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 3.0-alpha-3
Fixed in [r798221|http://svn.apache.org/viewvc?view=revrevision=798221].
import scope dependencies prefer to download pom rather than find it in the
current project
---
Key: MNG-4052
URL: http://jira.codehaus.org/browse/MNG-4052
Project: Maven 2
Issue Type: Bug
Components: Reactor and workspace
Affects Versions: 2.0.9
Reporter: David Jencks
Assignee: Benjamin Bentmann
Fix For: 3.0-alpha-3
Attachments: MNG-4052.zip
I've run into this in geronimo trunk.
Initial project state:
root pom includes dependency A in dependencyManagement.
this dependency is used (in dependencies) in several places including
plugins/clustering/plugin-farm-datasource/
Snapshots for this project are deployed (at apache snapshot repo)
project update:
move A to dependencyManagement of plugins/system-database/pom.xml (also a pom
packaging)
include in plugins/clustering/plugin-farm-datasource/pom.xml
dependencyManagement
dependencies
dependency
groupIdorg.apache.geronimo.plugins/groupId
artifactIdsystem-database/artifactId
version${version}/version
typepom/type
scopeimport/scope
/dependency
/dependencies
/dependencyManagement
(this is a car packaging project, using the geronimo car-maven-plugin)
now, clean the local repo and try to build the project from root.
we see:
pb:trunk david$ mvn clean install -Pit
[INFO] Scanning for projects...
[INFO] snapshot org.apache.geronimo.plugins:system-database:2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.plugins:system-database:2.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.plugins:system-database:2.2-SNAPSHOT:
checking for updates from codehaus-snapshots
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/plugins/system-database/2.2-SNAPSHOT/system-database-2.2-SNAPSHOT.pom
rather than using the system-database pom in the local project it is
downloading the obsolete snapshot.
I've worked around this by uploading the system-database pom by hand.
I may try to write a sample project but since seeing the bug depends on
having a deployed snapshot and then changing it locally I have no idea how to
write an automated test.
--
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: (MNGSITE-94) http://maven.apache.org/guides/mini/guide-embedding-m2.html does not exist
[ http://jira.codehaus.org/browse/MNGSITE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185015#action_185015 ] Karl Heinz Marbaise commented on MNGSITE-94: I have taken a look into the repos but there is content for the embedder page [http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-embedding-m2.apt?revision=797757]. http://maven.apache.org/guides/mini/guide-embedding-m2.html does not exist -- Key: MNGSITE-94 URL: http://jira.codehaus.org/browse/MNGSITE-94 Project: Maven 2 Project Web Site Issue Type: Bug Environment: All Reporter: Karl Heinz Marbaise Priority: Critical The link to on the guides page (http://maven.apache.org/guides/) to the embedding Maven 2 is targeting on a complete empty site. Not 404 etc. Just a clean page. -- 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-95) http://maven.apache.org/guides/ to Reporting API is wrong
http://maven.apache.org/guides/ to Reporting API is wrong - Key: MNGSITE-95 URL: http://jira.codehaus.org/browse/MNGSITE-95 Project: Maven 2 Project Web Site Issue Type: Bug Environment: All Reporter: Karl Heinz Marbaise The link on the [http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/index.apt?revision=745364] site to http://maven.apache.org/ref/2.1.0/maven-reporting/apidocs/ produces an Page not Found The given link in the [http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/index.apt?revision=745364] file is simply wrong it should be linked to [http://maven.apache.org/ref/2.1.0/maven-reporting/maven-reporting-api/apidocs/] instead. -- 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: (MAVENUPLOAD-2530) TestNG 5.10
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cedric Beust closed MAVENUPLOAD-2530. - Resolution: Fixed I attached the wrong bundle, please ignore this and I'll file a new upload request. TestNG 5.10 --- Key: MAVENUPLOAD-2530 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2530 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Beust Attachments: testng-5.10beta-bundle.jar -- 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-2531) TestNG 5.10
TestNG 5.10 --- Key: MAVENUPLOAD-2531 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2531 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Beust Attachments: testng-5.10-bundle.jar I am the TestNG creator. -- 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: (MSITE-404) site:stage creates wrong links on Linux
[ http://jira.codehaus.org/browse/MSITE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-404. --- Assignee: Lukas Theussl Resolution: Fixed Trunk has been bumped to doxia-1.1.2-SNAPSHOT ([r798235|http://svn.apache.org/viewvc?view=revrevision=798235), snapshot is deployed for testing. 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 Assignee: Lukas Theussl Fix For: 2.1 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] 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-tabpanelfocusedCommentId=185018#action_185018 ] Lukas Theussl edited comment on MSITE-404 at 7/27/09 12:56 PM: --- Trunk has been bumped to doxia-1.1.2-SNAPSHOT ( [r798235|http://svn.apache.org/viewvc?view=revrevision=798235 ]), snapshot is deployed for testing. was (Author: lukas): Trunk has been bumped to doxia-1.1.2-SNAPSHOT ([r798235|http://svn.apache.org/viewvc?view=revrevision=798235), snapshot is deployed for testing. 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 Assignee: Lukas Theussl Fix For: 2.1 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] Closed: (MSITE-395) Maven site multi module url problem
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-395. --- Assignee: Lukas Theussl Resolution: Fixed Seems fixed with MSITE-404, please test. Maven site multi module url problem --- Key: MSITE-395 URL: http://jira.codehaus.org/browse/MSITE-395 Project: Maven 2.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0 Reporter: valsho Assignee: Lukas Theussl Priority: Blocker Fix For: 2.1 Attachments: genesis-2.0-SNAPSHOT-source-release.tar.gz, genesis-2.0-SNAPSHOT-source-release.tar.gz The generated maven (2.0.10) site for a multi module project is different on windows and linux. The difference is the relative url for the modules. -- Here's the project structure : myProject/ trunk/ pom.xml module1/ pom.xml src/ module2/ pom.xml src/ -- Here's myProject/trunk/pom.xml definition : groupIdcom.myProject/groupId artifactIdmodulepom/artifactId packagingpom/packaging namePOM myProject/name version1.0-SNAPSHOT/version modules modulemodule1/module modulemodule2/module /modules distributionManagement site idsite/id nameMaven site/name urlfile:///url /site /distributionManagement build plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.0/version /plugin /build -- On module1 and module2 pom, I didn't declare any distributionManagement information. I've only declared the parent parent groupIdcom.myProject/groupId artifactIdmodulepom/artifactId version1.0-SNAPSHOT/version /parent groupIdcom.myProject/groupId artifactIdmodule1/artifactId packagingjar/packaging version1.0-SNAPSHOT/version namemodule1 name/name -- Here are the index.html files generated on windows and linux in myProject/trunk/target/staging/localhost/ after launching mvn site:stage in directory myProject/trunk/ -- Site deployed on Windows which is correct h5Modules/h5ul li class=none a href=module1/index.htmlmodule1 name/a /li li class=none a href=module2/index.htmlmodule2 name/a /li ... -- Site deployed on Linux which isn't correct ... h5Modules/h5ul li class=none a href=../../tmp/testProject/myProject/trunk/../localhostmodule1 name/a /li li class=none a href=../../tmp/testProject/myProject/trunk/../localhostmodule2 name/a /li ... where /tmp/testProject/ is the absolute path where is stored myProject/ on linux -- Any idea ? Maybe i should use something different in distributionManagement than urlfile:///url Thanks for your help -- 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-276) Links on Modules are completely broken on site:stage
[ http://jira.codehaus.org/browse/MSITE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185020#action_185020 ] Lukas Theussl commented on MSITE-276: - This looks like a dupe of MSITE-404, but you didn't a attach a test project so I can't check. Please test with site-plugin-2.1-SNAPSHOT. Links on Modules are completely broken on site:stage Key: MSITE-276 URL: http://jira.codehaus.org/browse/MSITE-276 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-6 Reporter: Jörg Hohwiller Assignee: Lukas Theussl Fix For: 2.1 The latest maven-site-plugin 2.0-beta-6 seems to to introduce a new bug that was NOT present in 2.0-beta-5: Now all my modules point to the same url which is ../../opt/project/build/development/projects/../dummyhost.de Something goes very wrong here: 1. The link should not contain pathnames specific for the environment where it was build (/opt/project/build/development/projects) nor the hostname and path of the distributionManagement. 2. The modulename itself is totally lost and all module-links in the menu have the same href Whatever has happend here, made it a lot worse. The site is now totally unuseable. It seems that only mvn site was tested before the 2.0-beta-6 was released. Multimodule-Builds need to be tested with site:stage or site:deploy. -- 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-23) Definition Lists are not formatted correctly
Definition Lists are not formatted correctly Key: MPDF-23 URL: http://jira.codehaus.org/browse/MPDF-23 Project: Maven 2.x PDF Plugin Issue Type: Improvement Affects Versions: 1.0 Environment: OS: Mac OS X (10.5.7) Java Version: (1.6.0_13) PDF Plugin Implementation: itext Documentation Source Format: APT Reporter: Steven Swor Priority: Trivial When creating a definition list using APT, the resulting PDF is formatted incorrectly. For example: [Term 1] Definition 1. [Term 2] Definition 2. [Term 3] Definition 3. [] produces the following output Term 1 Definition 1. Term 2. Definition 2. Term 3. Definition 3. The two problems I have with this are that 1) new terms are on the same line as the definition of the previous term, and 2) there is not enough formatting difference between terms and their definitions. It'd be nice to make the terms bold-face, or indent the definitions, or something like that, to make the PDF more human-readable. -- 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-23) Definition Lists are not formatted correctly
[ http://jira.codehaus.org/browse/MPDF-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185025#action_185025 ] Steven Swor commented on MPDF-23: - In my APT files, the definition lists are indented in accordance with http://maven.apache.org/doxia/references/apt-format.html (the extra whitespace was stripped out by JIRA) Definition Lists are not formatted correctly Key: MPDF-23 URL: http://jira.codehaus.org/browse/MPDF-23 Project: Maven 2.x PDF Plugin Issue Type: Improvement Affects Versions: 1.0 Environment: OS: Mac OS X (10.5.7) Java Version: (1.6.0_13) PDF Plugin Implementation: itext Documentation Source Format: APT Reporter: Steven Swor Priority: Trivial When creating a definition list using APT, the resulting PDF is formatted incorrectly. For example: [Term 1] Definition 1. [Term 2] Definition 2. [Term 3] Definition 3. [] produces the following output Term 1 Definition 1. Term 2. Definition 2. Term 3. Definition 3. The two problems I have with this are that 1) new terms are on the same line as the definition of the previous term, and 2) there is not enough formatting difference between terms and their definitions. It'd be nice to make the terms bold-face, or indent the definitions, or something like that, to make the PDF more human-readable. -- 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-2472) New sychronization request for org.bushe (EventBus)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185034#action_185034 ] Michael Bushe commented on MAVENUPLOAD-2472: Hello? Anyone? While I was waiting for a response I had a security expert (and Linux expert) take a look at my setup and my security logs. He confirmed that my side is set up properly. There's the possibility that your side cached a bad host key since the email has host key verification failed but my host key hasn't changed in 18 months, and that would likely produce an error such as someone could be doing something nasty, man in the middle, etc. etc. Can we get this solved, please? Thanks, Michael New sychronization request for org.bushe (EventBus) --- Key: MAVENUPLOAD-2472 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2472 Project: Maven Upload Requests Issue Type: Wish Reporter: Michael Bushe Assignee: Carlos Sanchez I'd like to add my repo to synchronize releases of the EventBus (and future projects) of bushe.org to the Central Maven Repository. Thank you for supplying this essential service. My comma delimited info for rsync over ssh is: org.bushe,rs...@bushe.com:/home/rsync/m2repo/releases,rsync_ssh,Michael Bushe,mich...@bushe.com,, The repo is browesable here: http://www.bushe.com:8081/nexus/content/repositories/Bushe.orgSyncToCentral/ Here's proof that I own bushe.org: http://reports.internic.net/cgi/whois?whois_nic=bushe.orgtype=domain Let me know if you have any trouble syncing. I expect it to be set up correctly, but you never know. Thank you again! Michael Bushe -- 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-338) Section numbering and links
[ http://jira.codehaus.org/browse/DOXIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed DOXIA-338. - Resolution: Fixed fixed in [r798303|http://svn.apache.org/viewvc?rev=798303view=rev], snapshot deployed Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Assignee: Vincent Siveton Fix For: 1.1.2 Attachments: DOXIA-338.diff, doxia-site-test.zip, doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- 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: (MECLIPSE-178) symbolic links need to able to be specified in the pom
[
http://jira.codehaus.org/browse/MECLIPSE-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier updated MECLIPSE-178:
-
Component/s: Core : .project
Remaining Estimate: 0 minutes
Original Estimate: 0 minutes
Applied the patch from ashok to not remove links manually added in project
I also modified the eclipse mojo to allow to setup links in the pom and I added
new ITs to test it
Here is a sample of the configuration :
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.8/version
configuration
linkedResources
linkedResource
namesrc/test/resources/oracle-ds.xml/name
type1/type
locationC://jboss/server/default/deploy/oracle-ds.xml/location
/linkedResource
linkedResource
namesrc/test/resources/mysql-ds.xml/name
type1/type
locationC://jboss/server/default/deploy/mysql-ds.xml/location
/linkedResource
/linkedResources
/configuration
/plugin
{code}
symbolic links need to able to be specified in the pom
--
Key: MECLIPSE-178
URL: http://jira.codehaus.org/browse/MECLIPSE-178
Project: Maven 2.x Eclipse Plugin
Issue Type: New Feature
Components: Core : .project
Reporter: Jim Sellers
Fix For: 2.8
Attachments: EclipseProjectWriter.java,
EclipseProjectWriterTest.java, LinkedResourceCommand.java,
MECLIPSE-178.patch, mylyn-context.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
In eclipse, you can make a symbolic link to a file.
create new file - advanced - link to file in the system.
This will create a part in the .project file like this:
linkedResources
link
namesrc/test/resources/oracle-ds.xml/name
type1/type
locationC://jboss/server/default/deploy/oracle-ds.xml/location
/link
/linkedResources
When you run mvn eclipse:eclipse this gets wipped out. It would be great
if this soft link didn't have to be re-created someone runs the command.
--
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: (MECLIPSE-178) symbolic links need to able to be specified in the pom
[
http://jira.codehaus.org/browse/MECLIPSE-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier closed MECLIPSE-178.
Assignee: Arnaud Heritier
Resolution: Fixed
Applied the patch from ashok to not remove links manually added in project
I also modified the eclipse mojo to allow to setup links in the pom and I added
new ITs to test it
Here is a sample of the configuration :
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.8/version
configuration
linkedResources
linkedResource
namesrc/test/resources/oracle-ds.xml/name
type1/type
locationC://jboss/server/default/deploy/oracle-ds.xml/location
/linkedResource
linkedResource
namesrc/test/resources/mysql-ds.xml/name
type1/type
locationC://jboss/server/default/deploy/mysql-ds.xml/location
/linkedResource
/linkedResources
/configuration
/plugin
{code}
symbolic links need to able to be specified in the pom
--
Key: MECLIPSE-178
URL: http://jira.codehaus.org/browse/MECLIPSE-178
Project: Maven 2.x Eclipse Plugin
Issue Type: New Feature
Components: Core : .project
Reporter: Jim Sellers
Assignee: Arnaud Heritier
Fix For: 2.8
Attachments: EclipseProjectWriter.java,
EclipseProjectWriterTest.java, LinkedResourceCommand.java,
MECLIPSE-178.patch, mylyn-context.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
In eclipse, you can make a symbolic link to a file.
create new file - advanced - link to file in the system.
This will create a part in the .project file like this:
linkedResources
link
namesrc/test/resources/oracle-ds.xml/name
type1/type
locationC://jboss/server/default/deploy/oracle-ds.xml/location
/link
/linkedResources
When you run mvn eclipse:eclipse this gets wipped out. It would be great
if this soft link didn't have to be re-created someone runs the command.
--
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-3402) MavenArtifactFilterManager needs to not filtering doxia-sink-api
[ http://jira.codehaus.org/browse/MNG-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MNG-3402. - Resolution: Fixed I close it as it's done in trunk. I will open a separate issue concerning site plugin with current trunk. MavenArtifactFilterManager needs to not filtering doxia-sink-api Key: MNG-3402 URL: http://jira.codehaus.org/browse/MNG-3402 Project: Maven 2 Issue Type: Improvement Components: Artifacts and Repositories Affects Versions: 2.0.8 Reporter: Vincent Siveton Assignee: Brett Porter Fix For: 3.0-alpha-3 Attachments: MavenArtifactFilterManager.diff A plugin (like pdf-plugin) needs to use the most recent sink API and not the API embedded in maven. -- 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-4261) site plugin doesn't generate reports
site plugin doesn't generate reports
Key: MNG-4261
URL: http://jira.codehaus.org/browse/MNG-4261
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 3.0-alpha-3
Reporter: Olivier Lamy
With the current trunk (rev 798335), reports mojo are not populated anymore in
the site mojo. (expression ${reports} )
--
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-4261) site plugin doesn't generate reports
[
http://jira.codehaus.org/browse/MNG-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MNG-4261:
--
Priority: Blocker (was: Major)
Fix Version/s: 3.0-alpha-3
site plugin doesn't generate reports
Key: MNG-4261
URL: http://jira.codehaus.org/browse/MNG-4261
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 3.0-alpha-3
Reporter: Olivier Lamy
Priority: Blocker
Fix For: 3.0-alpha-3
With the current trunk (rev 798335), reports mojo are not populated anymore
in the site mojo. (expression ${reports} )
--
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: (MECLIPSE-593) Reorganize / rewrite documentation
Reorganize / rewrite documentation -- Key: MECLIPSE-593 URL: http://jira.codehaus.org/browse/MECLIPSE-593 Project: Maven 2.x Eclipse Plugin Issue Type: Task Components: PDE support Affects Versions: 2.7 Reporter: Arnaud Heritier Our users are often complaining about our documentation. A too important part of the documentation is in the mojo description (in each parameter). I think we can improve it by reorganizing it like that : * Basic Features ** Project Descriptor : Everything about project name, build commands, natures, ** Classpath : Its order, how to dl javadocs and sources, cross-project references, includes, excludes, cache, ... * Extensions ** WTP ** AJDT (AspectJ co) ** PDE * M2Eclipse / Q4E * Custom versions ** RAD ** MyEclipse -- 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: (MECLIPSE-593) Reorganize / rewrite documentation
[ http://jira.codehaus.org/browse/MECLIPSE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-593: - Fix Version/s: 2.8 Reorganize / rewrite documentation -- Key: MECLIPSE-593 URL: http://jira.codehaus.org/browse/MECLIPSE-593 Project: Maven 2.x Eclipse Plugin Issue Type: Task Components: PDE support Affects Versions: 2.7 Reporter: Arnaud Heritier Assignee: Arnaud Heritier Fix For: 2.8 Our users are often complaining about our documentation. A too important part of the documentation is in the mojo description (in each parameter). I think we can improve it by reorganizing it like that : * Basic Features ** Project Descriptor : Everything about project name, build commands, natures, ** Classpath : Its order, how to dl javadocs and sources, cross-project references, includes, excludes, cache, ... * Extensions ** WTP ** AJDT (AspectJ co) ** PDE * M2Eclipse / Q4E * Custom versions ** RAD ** MyEclipse -- 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: (MPDF-23) Definition Lists are not formatted correctly
[
http://jira.codehaus.org/browse/MPDF-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MPDF-23:
--
Description:
When creating a definition list using APT, the resulting PDF is formatted
incorrectly. For example:
{noformat}
[Term 1] Definition 1.
[Term 2] Definition 2.
[Term 3] Definition 3.
[]
{noformat}
produces the following output
{noformat}
Term 1
Definition 1. Term 2.
Definition 2. Term 3.
Definition 3.
{noformat}
The two problems I have with this are that 1) new terms are on the same line as
the definition of the previous term, and 2) there is not enough formatting
difference between terms and their definitions. It'd be nice to make the terms
bold-face, or indent the definitions, or something like that, to make the PDF
more human-readable.
was:
When creating a definition list using APT, the resulting PDF is formatted
incorrectly. For example:
[Term 1] Definition 1.
[Term 2] Definition 2.
[Term 3] Definition 3.
[]
produces the following output
Term 1
Definition 1. Term 2.
Definition 2. Term 3.
Definition 3.
The two problems I have with this are that 1) new terms are on the same line as
the definition of the previous term, and 2) there is not enough formatting
difference between terms and their definitions. It'd be nice to make the terms
bold-face, or indent the definitions, or something like that, to make the PDF
more human-readable.
Definition Lists are not formatted correctly
Key: MPDF-23
URL: http://jira.codehaus.org/browse/MPDF-23
Project: Maven 2.x PDF Plugin
Issue Type: Improvement
Affects Versions: 1.0
Environment: OS: Mac OS X (10.5.7)
Java Version: (1.6.0_13)
PDF Plugin Implementation: itext
Documentation Source Format: APT
Reporter: Steven Swor
Priority: Trivial
When creating a definition list using APT, the resulting PDF is formatted
incorrectly. For example:
{noformat}
[Term 1] Definition 1.
[Term 2] Definition 2.
[Term 3] Definition 3.
[]
{noformat}
produces the following output
{noformat}
Term 1
Definition 1. Term 2.
Definition 2. Term 3.
Definition 3.
{noformat}
The two problems I have with this are that 1) new terms are on the same line
as the definition of the previous term, and 2) there is not enough formatting
difference between terms and their definitions. It'd be nice to make the
terms bold-face, or indent the definitions, or something like that, to make
the PDF more human-readable.
--
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-23) Definition Lists are not formatted correctly
[
http://jira.codehaus.org/browse/MPDF-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185063#action_185063
]
Lukas Theussl commented on MPDF-23:
---
I cannot reproduce that, my definition lists are ok. Please attach a test
document that you are using so I can try to reproduce it.
Definition Lists are not formatted correctly
Key: MPDF-23
URL: http://jira.codehaus.org/browse/MPDF-23
Project: Maven 2.x PDF Plugin
Issue Type: Improvement
Affects Versions: 1.0
Environment: OS: Mac OS X (10.5.7)
Java Version: (1.6.0_13)
PDF Plugin Implementation: itext
Documentation Source Format: APT
Reporter: Steven Swor
Priority: Trivial
When creating a definition list using APT, the resulting PDF is formatted
incorrectly. For example:
{noformat}
[Term 1] Definition 1.
[Term 2] Definition 2.
[Term 3] Definition 3.
[]
{noformat}
produces the following output
{noformat}
Term 1
Definition 1. Term 2.
Definition 2. Term 3.
Definition 3.
{noformat}
The two problems I have with this are that 1) new terms are on the same line
as the definition of the previous term, and 2) there is not enough formatting
difference between terms and their definitions. It'd be nice to make the
terms bold-face, or indent the definitions, or something like that, to make
the PDF more human-readable.
--
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-273) Wrong url in banner left url when page has more 2 sub directories
[ http://jira.codehaus.org/browse/MSITE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185064#action_185064 ] Lukas Theussl commented on MSITE-273: - Vincent, I believe this is fixed in current 2.1-SNAPSHOT, can you confirm? Btw, the links in the deployed pages above are already different than what you describe but still not correct... Wrong url in banner left url when page has more 2 sub directories - Key: MSITE-273 URL: http://jira.codehaus.org/browse/MSITE-273 Project: Maven 2.x Site Plugin Issue Type: Bug Components: relative links Affects Versions: 2.0-beta-6 Environment: svn rev 599447 Reporter: Vincent Siveton Fix For: 2.1 Follow the following steps: 1. go to http://maven.apache.org/repository/index.html or http://maven.apache.org/developers/committer-environment.html 2. and click on the Maven logo (top left) 3. the page is http://maven.apache.org/ which is the correct behaviour But try to reproduce the same with 2 sub directories in the url, like http://maven.apache.org/guides/mini/guide-central-repository-upload.html The url is http://maven.apache.org/guides/ instead of http://maven.apache.org/ -- 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: (MSITE-381) Multi-project site navigation suddenly broken
[ http://jira.codehaus.org/browse/MSITE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-381. --- Assignee: Lukas Theussl Resolution: Fixed This is fixed with MSITE-404, but it's difficult to test with the tapestry site... please attach a simple test case if there is anything I missed. Multi-project site navigation suddenly broken - Key: MSITE-381 URL: http://jira.codehaus.org/browse/MSITE-381 Project: Maven 2.x Site Plugin Issue Type: Bug Components: inheritance Affects Versions: 2.0-beta-6 Reporter: Howard M. Lewis Ship Assignee: Lukas Theussl Fix For: 2.1 Not exactly sure when this started, but the generated site navigation for my multiproject site is broken; sub-modules now use the same navigation links as the master project ... thus per-module files are inaccessible and many links are broken., See http://tapestry.formos.com/nightly/tapestry5 for an example. Using maven-site-plugin verson 2.0-beta-6. It seems to work correctly if I downgrade to 2.0-beta-5. -- 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-409) Incorrect URLs in multi-module project
[
http://jira.codehaus.org/browse/MSITE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185067#action_185067
]
Lukas Theussl commented on MSITE-409:
-
The links issue is fixed with MSITE-404, please test with
site-plugin-2.1-SNAPSHOT.
The hierarchy problem is more general, it should get it's own issue. However,
my impression is that you should be able to fix it by adjusting your document
structure, eg
{noformat}
pom.xml
|
parent
|
--
|| |
mod1 mod2mod3
{noformat}
or
{noformat}
parent
|
---
| | | |
pom.xml mod1 mod2mod3
{noformat}
and setting the modules accordingly.
Incorrect URLs in multi-module project
--
Key: MSITE-409
URL: http://jira.codehaus.org/browse/MSITE-409
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: multi module
Affects Versions: 2.0
Reporter: Benson Margulies
Fix For: 2.1
Attachments: tc.patch.diff
I have a top-level pom and some modules. One of the modules serves as a
parent for most, but not all, of the rest.
Thus, for most, the parent is ../parent, and for that the parent is the
top-level project itself.
I ran:
mvn site:stage -DstagingDirectory=/Users/benson/stage
It takes a very long time.
All of my child links came out incorrectly: e.g:
a
href=../../Users/benson/x/trunk/greenhouse/etrog/../../../../hudson.basistech.net/home/projects/etrogRLPJ
Buildtools/a
There aren't distinct subdirectories in the staged dir for those of my
modules that use the parent. Actually, now that I look, I see that the ones
that parent into ../parent are subdirectories of 'parent' instead of
subdirectories of the top-level. But the links are still all wrong.
--
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-358) site.xml urls are not always correct
[
http://jira.codehaus.org/browse/MSITE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185068#action_185068
]
Lukas Theussl commented on MSITE-358:
-
Brian,
I believe this is working with current 2.1-SNAPSHOT, at least on the few maven
sites I have tested. Please give me a concrete example if I missed something.
site.xml urls are not always correct
Key: MSITE-358
URL: http://jira.codehaus.org/browse/MSITE-358
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-6
Reporter: Brian Fox
Priority: Blocker
Fix For: 2.1
This is so completely broken that it must be fixed before another release
occurs.
The maven-parent site.xml defines some images as:
{noformat}
bannerLeft
name${project.name}/name
srchttp://maven.apache.org/images/apache-maven-project-2.png/src
hrefhttp://maven.apache.org//href
/bannerLeft
bannerRight
srchttp://maven.apache.org/images/maven-logo-2.gif/src
/bannerRight
{noformat}
The site plugin somewhere along the line replaces these urls with ../../
repeated based on how far down the inheritence tree you are from
maven-parent. This means you can't stage or deploy a site to a different
location than the maven-parent because all urls will point back to
maven-parent's /images. Worse, every module has its own copy of the css and
images so there's no reason for it to depend on the parent at all.
--
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
