[jira] (SUREFIRE-914) NPE is thrown in the ConcurrentReporterManager
[ https://jira.codehaus.org/browse/SUREFIRE-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311463#comment-311463 ] Mark Zalavari commented on SUREFIRE-914: Some mistake: JBehave version is 3.7, not 3.6. > NPE is thrown in the ConcurrentReporterManager > -- > > Key: SUREFIRE-914 > URL: https://jira.codehaus.org/browse/SUREFIRE-914 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.12.4 >Reporter: Mark Zalavari > Attachments: log_bug_surefire2.txt > > > With JBehave 3.6 and jbehave-junit-runner 1.0.1 surefire thrown the attached > exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-914) NPE is thrown in the ConcurrentReporterManager
Mark Zalavari created SUREFIRE-914: -- Summary: NPE is thrown in the ConcurrentReporterManager Key: SUREFIRE-914 URL: https://jira.codehaus.org/browse/SUREFIRE-914 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.12.4 Reporter: Mark Zalavari Attachments: log_bug_surefire2.txt With JBehave 3.6 and jbehave-junit-runner 1.0.1 surefire thrown the attached exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSCMPUB-2) publish-scm can fail with many files on windows.
[
https://jira.codehaus.org/browse/MSCMPUB-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311459#comment-311459
]
Mark Hobson commented on MSCMPUB-2:
---
The NPE has gone away but I'm afraid we still have line length problems :(
{noformat}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:1.0-SNAPSHOT:publish-scm
(default-cli) on project X: Failed to add new files to SCM: The git-add command
failed. 'C:\Users\mark\AppData\Local\Temp\git-add9095034289317458180bat' is not
recognized as an internal or external command,
operable program or batch file.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to add new
files to SCM: The git-add command failed.
'C:\Users\mark\AppData\Local\Temp\git-add9095034289317458180bat' is not
recognized as an internal or external command,
operable program or batch file.
at
org.apache.maven.plugins.scmpublish.AbstractScmPublishMojo.checkScmResult(AbstractScmPublishMojo.java:634)
at
org.apache.maven.plugins.scmpublish.AbstractScmPublishMojo.addFiles(AbstractScmPublishMojo.java:617)
at
org.apache.maven.plugins.scmpublish.ScmPublishPublishScmMojo.scmPublishExecute(ScmPublishPublishScmMojo.java:269)
at
org.apache.maven.plugins.scmpublish.AbstractScmPublishMojo.execute(AbstractScmPublishMojo.java:485)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
{noformat}
The temporary file is 30646 characters long. Looks like this exceeds the 8192
limit of cmd.exe:
http://blogs.msdn.com/b/oldnewthing/archive/2003/12/10/56028.aspx
> publish-scm can fail with many files on windows.
>
>
> Key: MSCMPUB-2
> URL: https://jira.codehaus.org/browse/MSCMPUB-2
> Project: maven-scm-publish-plugin
> Issue Type: Bug
> Environment: Cygwin, Windows
>Reporter: Mark Hobson
>Assignee: Olivier Lamy
>
> Running publish-scm with a large site can cause the command process to fail
> due to the command line being too long. For example:
> {noformat}
> [INFO] --- maven-scm-publish-plugin:1.0-beta-1:publish-scm (scm-publish) @ X
> ---
> ...
> [INFO] Executing: cmd.exe /X /C "git add -- "
> {noformat}
> Results in:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-scm-publish-plugin:1.0-beta-1:publish-scm
> (scm-publish) on project X: Failed to add new files to SCM: Exception while
> executing SCM command. Error while executing command. Error while executing
> process. Cannot run program "cmd.exe" (in directory X): CreateProcess
> error=206, The filename or extension is too long -> [Help 1]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA
[jira] (MSCMPUB-2) publish-scm can fail with many files on windows.
[
https://jira.codehaus.org/browse/MSCMPUB-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311447#comment-311447
]
Olivier Lamy commented on MSCMPUB-2:
Must be fixed with last SNAPSHOT of maven-scm-provider-gitexe.
Can you try using -U ?
> publish-scm can fail with many files on windows.
>
>
> Key: MSCMPUB-2
> URL: https://jira.codehaus.org/browse/MSCMPUB-2
> Project: maven-scm-publish-plugin
> Issue Type: Bug
> Environment: Cygwin, Windows
>Reporter: Mark Hobson
>Assignee: Olivier Lamy
>
> Running publish-scm with a large site can cause the command process to fail
> due to the command line being too long. For example:
> {noformat}
> [INFO] --- maven-scm-publish-plugin:1.0-beta-1:publish-scm (scm-publish) @ X
> ---
> ...
> [INFO] Executing: cmd.exe /X /C "git add -- "
> {noformat}
> Results in:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-scm-publish-plugin:1.0-beta-1:publish-scm
> (scm-publish) on project X: Failed to add new files to SCM: Exception while
> executing SCM command. Error while executing command. Error while executing
> process. Cannot run program "cmd.exe" (in directory X): CreateProcess
> error=206, The filename or extension is too long -> [Help 1]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-659) 'relativizeDecorationLinks' relativizes too much.
[ https://jira.codehaus.org/browse/MSITE-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311445#comment-311445 ] Christian Schulte commented on MSITE-659: - This is a request to add a new 'site:offline-jar' goal supporting the use case mentioned above then :-). > 'relativizeDecorationLinks' relativizes too much. > - > > Key: MSITE-659 > URL: https://jira.codehaus.org/browse/MSITE-659 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 3.1 >Reporter: Christian Schulte > Attachments: MSITE-659-absolute.zip, MSITE-659.zip, MSITE-659.zip > > > When relativizing links, the plugin produces relative links to content not > generated by the plugin which should be kept absolute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-659) 'relativizeDecorationLinks' relativizes too much.
[ https://jira.codehaus.org/browse/MSITE-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311443#comment-311443 ] Lukas Theussl commented on MSITE-659: - I repeat what I said above, this is a feature not a bug :). Read http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site If you want to browse the site locally you have to use site:stage, site:jar is for deployment, in which case you should know where to put individual pieces. > 'relativizeDecorationLinks' relativizes too much. > - > > Key: MSITE-659 > URL: https://jira.codehaus.org/browse/MSITE-659 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 3.1 >Reporter: Christian Schulte > Attachments: MSITE-659-absolute.zip, MSITE-659.zip, MSITE-659.zip > > > When relativizing links, the plugin produces relative links to content not > generated by the plugin which should be kept absolute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-659) 'relativizeDecorationLinks' relativizes too much.
[
https://jira.codehaus.org/browse/MSITE-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311442#comment-311442
]
Christian Schulte commented on MSITE-659:
-
Put another way. Specifying relative links in the decoration model, inheriting
them as absolute is not possible. Specifying absolute links in the decoration
model, using 'relativizeDecorationLinks' is not possible since that will
relativize at the 'child' level in a way links will not work when browsing that
site locally (unzipped jar). Building a site for deployment and building a site
for browsing locally (unzipped jar) would need to be handled differently to get
this working. Let the jar goal update links in a way compatible with local
browsing ('absolutizeDecorationLinks') and let the site goal update links in a
way compatible with online browsing (already implemented).
> 'relativizeDecorationLinks' relativizes too much.
> -
>
> Key: MSITE-659
> URL: https://jira.codehaus.org/browse/MSITE-659
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: relative links
>Affects Versions: 3.1
>Reporter: Christian Schulte
> Attachments: MSITE-659-absolute.zip, MSITE-659.zip, MSITE-659.zip
>
>
> When relativizing links, the plugin produces relative links to content not
> generated by the plugin which should be kept absolute.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-659) 'relativizeDecorationLinks' relativizes too much.
[ https://jira.codehaus.org/browse/MSITE-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MSITE-659: Attachment: MSITE-659-absolute.zip Another example project demonstrating the issue. Unzip and execute 'mvn site'. Open 'target/site/index.html' from the parent project in a browser. The 'Inside Parent Jar' link got relativized correctly - that link is working ok at the deployed location and also inside the parent jar file. Now open the 'child/target/site/index.html' from the child project in a browser. The inherited 'Inside Parent Jar' link got relativized correctly but that link only works when actually deployed to a web server. It is not working inside the jar where it should be an absolute link. Absolute link in the jar - relative link in the deployed web site. Now repeat the above with the 'relativizeDecorationLinks' parameter set to 'false' (mvn clean site -DrelativizeDecorationLinks=false). The 'Inside Parent Jar' link in the 'target/site/index.html' from the parent site now is kept absolute. This is kind of useless in the parent site jar and in the deployed web site. That same link in the 'child/target/site/index.html' from the child site is absolute in the child. That link now is working in the child site jar file (when unzipped and used locally) but is again kind of useless in the deployed web site. To sum this up. There is nothing wrong with the 'relativizeDecorationLinks' feature when building a web-site you are actually going to deploy somewhere. The problem is when building a jar for use locally. Relative links pointing outside the jar file will not work there and need to be kept absolute and absolute links which are pointing to content inside the jar file should be relative otherwise the jar is quite useless. > 'relativizeDecorationLinks' relativizes too much. > - > > Key: MSITE-659 > URL: https://jira.codehaus.org/browse/MSITE-659 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 3.1 >Reporter: Christian Schulte > Attachments: MSITE-659-absolute.zip, MSITE-659.zip, MSITE-659.zip > > > When relativizing links, the plugin produces relative links to content not > generated by the plugin which should be kept absolute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-233) dependency-management is checking for SNAPSHOT updates
[
https://jira.codehaus.org/browse/MPIR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPIR-233:
---
Priority: Critical (was: Major)
Affects Version/s: 2.4
2.5.1
> dependency-management is checking for SNAPSHOT updates
> --
>
> Key: MPIR-233
> URL: https://jira.codehaus.org/browse/MPIR-233
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 2.4, 2.5.1
> Environment: java 6.0.27, maven 3.0.3
>Reporter: Martin Vanek
>Assignee: Herve Boutemy
>Priority: Critical
> Fix For: 2.6
>
>
> In my pom I have
> {code:xml}
>
>
> cz.komix.maven
> spring-security-deps
> pom
> 3.0.5
> import
>
>
> {code}
> cz.komix.maven:spring-security-deps:3.0.5 is simple pom with
> dependencyManagement section with spring artifacts versions
> Running mvn site with dependency-management cause version
> update checks for every of those spring artifact. Is there any reason for
> such update check?
> It is made for every artifact in dependency-management section, even for
> those that is are not even used as dependency! It should be possible to turn
> it off like false at
> least.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-233) dependency-management is checking for SNAPSHOT updates
[
https://jira.codehaus.org/browse/MPIR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPIR-233:
---
Description:
In my pom I have
{code:xml}
cz.komix.maven
spring-security-deps
pom
3.0.5
import
{code}
cz.komix.maven:spring-security-deps:3.0.5 is simple pom with
dependencyManagement section with spring artifacts versions
Running mvn site with dependency-management cause version
update checks for every of those spring artifact. Is there any reason for such
update check?
It is made for every artifact in dependency-management section, even for those
that is are not even used as dependency! It should be possible to turn it off
like false at least.
was:
In my pom I have
cz.komix.maven
spring-security-deps
pom
3.0.5
import
cz.komix.maven:spring-security-deps:3.0.5 is simple pom with
dependencyManagement section with spring artifacts versions
Running mvn site with dependency-management cause version
update checks for every of those spring artifact. Is there any reason for such
update check?
It is made for every artifact in dependency-management section, even for those
that is are not even used as dependency! It should be possible to turn it off
like false at least.
> dependency-management is checking for SNAPSHOT updates
> --
>
> Key: MPIR-233
> URL: https://jira.codehaus.org/browse/MPIR-233
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
> Environment: java 6.0.27, maven 3.0.3
>Reporter: Martin Vanek
>Assignee: Herve Boutemy
> Fix For: 2.6
>
>
> In my pom I have
> {code:xml}
>
>
> cz.komix.maven
> spring-security-deps
> pom
> 3.0.5
> import
>
>
> {code}
> cz.komix.maven:spring-security-deps:3.0.5 is simple pom with
> dependencyManagement section with spring artifacts versions
> Running mvn site with dependency-management cause version
> update checks for every of those spring artifact. Is there any reason for
> such update check?
> It is made for every artifact in dependency-management section, even for
> those that is are not even used as dependency! It should be possible to turn
> it off like false at
> least.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5350) improve @threadSafe error message: tell which goal
[ https://jira.codehaus.org/browse/MNG-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5350: --- Priority: Minor (was: Major) > improve @threadSafe error message: tell which goal > -- > > Key: MNG-5350 > URL: https://jira.codehaus.org/browse/MNG-5350 > Project: Maven 2 & 3 > Issue Type: Improvement >Affects Versions: 3.0.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Minor > Fix For: 3.1 > > > just got the problem in MBUILDHELPER-43 > most goals were marker @threadSafe, only one was missing the marker > finding the culprit would have been easier if the error message didn't speak > about the overall plugin but pointed to the goal -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5350) improve @threadSafe error message: tell which goal
[ https://jira.codehaus.org/browse/MNG-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-5350. -- Resolution: Fixed Fix Version/s: 3.1 Assignee: Herve Boutemy done in [r1398044|http://svn.apache.org/viewvc?rev=1398044&view=rev] goals will be shown if debug traces active (and a hint is printed if debug not active) > improve @threadSafe error message: tell which goal > -- > > Key: MNG-5350 > URL: https://jira.codehaus.org/browse/MNG-5350 > Project: Maven 2 & 3 > Issue Type: Improvement >Affects Versions: 3.0.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.1 > > > just got the problem in MBUILDHELPER-43 > most goals were marker @threadSafe, only one was missing the marker > finding the culprit would have been easier if the error message didn't speak > about the overall plugin but pointed to the goal -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-233) dependency-management is checking for SNAPSHOT updates
[ https://jira.codehaus.org/browse/MPIR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MPIR-233: Fix Version/s: 2.6 > dependency-management is checking for SNAPSHOT updates > -- > > Key: MPIR-233 > URL: https://jira.codehaus.org/browse/MPIR-233 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependency-management > Environment: java 6.0.27, maven 3.0.3 >Reporter: Martin Vanek >Assignee: Herve Boutemy > Fix For: 2.6 > > > In my pom I have > > > > cz.komix.maven > spring-security-deps > pom > 3.0.5 > import > > > > cz.komix.maven:spring-security-deps:3.0.5 is simple pom with > dependencyManagement section with spring artifacts versions > Running mvn site with dependency-management cause version > update checks for every of those spring artifact. Is there any reason for > such update check? > It is made for every artifact in dependency-management section, even for > those that is are not even used as dependency! It should be possible to turn > it off like false at > least. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-233) dependency-management is checking for SNAPSHOT updates
[ https://jira.codehaus.org/browse/MPIR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed MPIR-233. --- Resolution: Duplicate Assignee: Herve Boutemy > dependency-management is checking for SNAPSHOT updates > -- > > Key: MPIR-233 > URL: https://jira.codehaus.org/browse/MPIR-233 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependency-management > Environment: java 6.0.27, maven 3.0.3 >Reporter: Martin Vanek >Assignee: Herve Boutemy > > In my pom I have > > > > cz.komix.maven > spring-security-deps > pom > 3.0.5 > import > > > > cz.komix.maven:spring-security-deps:3.0.5 is simple pom with > dependencyManagement section with spring artifacts versions > Running mvn site with dependency-management cause version > update checks for every of those spring artifact. Is there any reason for > such update check? > It is made for every artifact in dependency-management section, even for > those that is are not even used as dependency! It should be possible to turn > it off like false at > least. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-250) add support for Maven 3.1/Eclipse Aether
[ https://jira.codehaus.org/browse/MSHARED-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHARED-250: -- Fix Version/s: maven-dependency-tree-2.1 Assignee: Herve Boutemy Summary: add support for Maven 3.1/Eclipse Aether (was: add support for Eclipse Aether) > add support for Maven 3.1/Eclipse Aether > > > Key: MSHARED-250 > URL: https://jira.codehaus.org/browse/MSHARED-250 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-dependency-tree >Affects Versions: maven-dependency-tree-2.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: maven-dependency-tree-2.1 > > > future Maven version should use Eclipse Aether: see MNG-5354 > This will cause incompatibility with Maven3DependencyGraphBuilder -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-250) add support for Eclipse Aether
[ https://jira.codehaus.org/browse/MSHARED-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311436#comment-311436 ] Herve Boutemy commented on MSHARED-250: --- code added in [r1398039|http://svn.apache.org/viewvc?rev=1398039&view=rev]: waiting for MNG-5354 to be able to test > add support for Eclipse Aether > -- > > Key: MSHARED-250 > URL: https://jira.codehaus.org/browse/MSHARED-250 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-dependency-tree >Affects Versions: maven-dependency-tree-2.0 >Reporter: Herve Boutemy > > future Maven version should use Eclipse Aether: see MNG-5354 > This will cause incompatibility with Maven3DependencyGraphBuilder -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-658) 'relativizeDecorationLinks' not working using multiple 'locales'.
[ https://jira.codehaus.org/browse/MSITE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-658. --- Resolution: Fixed Fix Version/s: 3.3 Assignee: Lukas Theussl Patch applied in [r1398031|http://svn.apache.org/viewvc?view=revision&revision=1398031] with minor modification to account for null urls, and added an IT. Thanks! > 'relativizeDecorationLinks' not working using multiple 'locales'. > - > > Key: MSITE-658 > URL: https://jira.codehaus.org/browse/MSITE-658 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 3.1 >Reporter: Christian Schulte >Assignee: Lukas Theussl >Priority: Critical > Fix For: 3.3 > > Attachments: MSITE-658.patch, MSITE-658.zip > > > The plugin does not take into account that output will be generated to > sub-directories of the location specified by the project URL for all > non-default languages setup using the 'locales' parameter and produces > incorrect relative links in all non-default language pages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
