[jira] Created: (MAVENUPLOAD-2783) Rsync wikbook releases to central
Rsync wikbook releases to central - Key: MAVENUPLOAD-2783 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2783 Project: Maven Upload Requests Issue Type: Task Reporter: Arnaud Heritier Assignee: Arnaud Heritier Hosted in eXo Nexus server : http://repository.exoplatform.org/content/repositories/wikbook-releases/ Rsync entry : "org.wikbook","mavens...@repository.exoplatform.org:/home/nexus/data/storage/hosted/wikbook-releases","rsync_ssh","Arnaud Heritier","aherit...@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: (MAVENUPLOAD-2783) Rsync wikbook releases to central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MAVENUPLOAD-2783. Resolution: Fixed Done > Rsync wikbook releases to central > - > > Key: MAVENUPLOAD-2783 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2783 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Arnaud Heritier >Assignee: Arnaud Heritier > > Hosted in eXo Nexus server : > http://repository.exoplatform.org/content/repositories/wikbook-releases/ > Rsync entry : > "org.wikbook","mavens...@repository.exoplatform.org:/home/nexus/data/storage/hosted/wikbook-releases","rsync_ssh","Arnaud > Heritier","aherit...@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] Commented: (DOXIA-393) Unable to deploy site for fml and xdoc modules
[
http://jira.codehaus.org/browse/DOXIA-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222953#action_222953
]
Lukas Theussl commented on DOXIA-393:
-
I deployed without problems to a local directory. However, the directory it
tries to create in your case looks weird. Those tasks are executed by the
antrun plugin in the xdoc and fml poms, I don't think it has anything to do
specificly with xsddoc.
> Unable to deploy site for fml and xdoc modules
> --
>
> Key: DOXIA-393
> URL: http://jira.codehaus.org/browse/DOXIA-393
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Fml, Module - Xdoc
>Affects Versions: 1.1.3
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.5.0_22
> Java home: C:\Program\Java\jdk1.5.0_22\jre
> Default locale: sv_SE, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Dennis Lundberg
>
> When trying to deploy the site for version 1.1.3 I get the following failure
> in the FML and XDoc modules. It seems to have something to do with "xsddoc".
> Command line is:
> mvn site-deploy -Preporting -e
> {noformat}
> [INFO] Generating "Surefire Report" report.
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An Ant BuildException has occured: Directory
> G:\apache\maven\trunks\doxia\doxia\target\checkout\doxia-modules\doxia-module-fml\G:\apache\maven\trunks\doxia\doxia\target\checkout\doxia-modules\doxia-module-fml\target\site\xsddoc
> creation was not successful for an unknown reason
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An Ant BuildException
> has occured: Directory
> G:\apache\maven\trunks\doxia\doxia\target\checkout\doxia-modules\doxia-module-fml\G:\apache\maven\trunks\doxia\doxia\target\checkout\doxia-modules\doxia-module-fml\target\site\xsddoc
> creation was not successful for an unknown reason
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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:592)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant
> BuildException has occured: Directory
> G:\apache\maven\trunks\doxia\doxia\target\checkout\doxia-modules\doxia-module-fml\G:\apache\maven\trunks\doxia\doxia\target\checkout\doxia-modules\doxia-module-fml\target\site\xsddoc
> creation was not successful for an unknown reason
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:131)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: Directory
> G:\apache\maven\trunks\doxia\doxia\target\checkout\doxia-modules\doxia-module-fml\G:\apache\maven\trunks\doxia\
[jira] Reopened: (MGPG-20) Error with classifiers
[ http://jira.codehaus.org/browse/MGPG-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clement escoffier reopened MGPG-20: --- The issue is still valid. I'm going to upload a pom file to reproduce it. > Error with classifiers > -- > > Key: MGPG-20 > URL: http://jira.codehaus.org/browse/MGPG-20 > Project: Maven 2.x GPG Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-4 >Reporter: clement escoffier >Assignee: Benjamin Bentmann > > I've a project creating two artifacts with different classifiers. > When I try to sign them, I get : > gpg: .../target/classes: read error: Is a directory > Here is the stack trace in verbose mode: > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Exit code: 2 > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Exit code: 2 > at > org.apache.maven.plugin.gpg.GpgSigner.generateSignatureForArtifact(GpgSigner.java:179) > at > org.apache.maven.plugin.gpg.GpgSignAttachedMojo.execute(GpgSignAttachedMojo.java:228) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > ... 17 more > If I change the configuration to generate only one artifact, it works (and > the artifacts are signed). -- 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: (MGPG-20) Error with classifiers
[ http://jira.codehaus.org/browse/MGPG-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clement escoffier updated MGPG-20: -- Attachment: GPG-Classifier-Test.zip pom.xml Upload a pom file reproducing the issue (as well as a project). The issue comes when the project does not generate an artifact named regularly but always use classifier (in the project -jdk13 and -jdk15). Launching mvn clean package gpg:sign failed Removing the jdk15 classifier fixes the issue. > Error with classifiers > -- > > Key: MGPG-20 > URL: http://jira.codehaus.org/browse/MGPG-20 > Project: Maven 2.x GPG Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-4 >Reporter: clement escoffier >Assignee: Benjamin Bentmann > Attachments: GPG-Classifier-Test.zip, pom.xml > > > I've a project creating two artifacts with different classifiers. > When I try to sign them, I get : > gpg: .../target/classes: read error: Is a directory > Here is the stack trace in verbose mode: > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Exit code: 2 > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Exit code: 2 > at > org.apache.maven.plugin.gpg.GpgSigner.generateSignatureForArtifact(GpgSigner.java:179) > at > org.apache.maven.plugin.gpg.GpgSignAttachedMojo.execute(GpgSignAttachedMojo.java:228) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > ... 17 more > If I change the configuration to generate only one artifact, it works (and > the artifacts are signed). -- 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: (MDEP-265) Add classifier option for dependency:get
Add classifier option for dependency:get Key: MDEP-265 URL: http://jira.codehaus.org/browse/MDEP-265 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Andreas Kohn Assignee: Brian Fox The dependency:get mojo is really helpful, but it currently seems to be unable to get an artifact that uses a non-default classifier. Please add a classifier configuration option for the get mojo. -- 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: (MDEP-265) Add classifier option for dependency:get
[ http://jira.codehaus.org/browse/MDEP-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Kohn updated MDEP-265: -- Attachment: MDEP-265.diff Trivial implementation. > Add classifier option for dependency:get > > > Key: MDEP-265 > URL: http://jira.codehaus.org/browse/MDEP-265 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Andreas Kohn >Assignee: Brian Fox > Attachments: MDEP-265.diff > > > The dependency:get mojo is really helpful, but it currently seems to be > unable to get an artifact that uses a non-default classifier. > Please add a classifier configuration option for the get mojo. -- 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: (MDEP-266) Add parameter to configure copy-dependencies to also copy optional dependencies
Add parameter to configure copy-dependencies to also copy optional dependencies --- Key: MDEP-266 URL: http://jira.codehaus.org/browse/MDEP-266 Project: Maven 2.x Dependency Plugin Issue Type: New Feature Components: copy-dependencies Affects Versions: 2.1 Reporter: Andreas Sewe Assignee: Brian Fox Priority: Minor At the moment, copy-dependencies only copies non-optional dependencies. However, one sometimes wants to copy *all* dependencies -- even the optional ones. -- 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-4692) Maven choose the wrong transitive dependency
Maven choose the wrong transitive dependency Key: MNG-4692 URL: http://jira.codehaus.org/browse/MNG-4692 Project: Maven 2 & 3 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 2.2.1 Environment: Ubuntu Linux, JVM 1.6.0_18 OpenJdk Reporter: Jean-Eric Cuendet Attachments: bugmaven.tar.gz I have a dependency used by 2 sub-projects (spring-core) but with 2 different versions (2.5.5 and 2.5.6.SEC01) My project which uses theses 2 sub-projects gets spring-core 2.5.5 instead of the more recent 2.5.6.SEC01 I attach a test project which illustrates this case. To reproduce: 1. untar proj.tar.gz 2. Run ./build.sh 3. Have a look at the xxx-tree.log generated files The dep for apireg is 2.5.5 -> OK The dep for rcpers-core is 2.5.6.SEC01 -> OK The dep for adam-services is 2.5.5 -> NOK (Should be 2.5.6.SEC01 since it depends on rcpers-core) -- 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-657) eclipse:myeclipse generates wrong .classpath file while eclipse:eclipse generates correct one
eclipse:myeclipse generates wrong .classpath file while eclipse:eclipse
generates correct one
-
Key: MECLIPSE-657
URL: http://jira.codehaus.org/browse/MECLIPSE-657
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: MyEclipse support
Affects Versions: 2.8
Environment: Windows XP, Maven 2.2.1
Reporter: Wayne Fuller
Priority: Minor
In my pom.xml file for a war project, I have the following entry in the
section
{code:xml|title=pom.xml|borderStyle = solid}
src/main/resources
true
src/test/resources
{code}
When I generate the eclipse project and classpath files using mvn
eclipse:eclipse the following is generated which is correct.
{code:title=.classpath|borderStype = solid}
{code}
But if I generate using eclipse:myeclipse the following is generated where the
output is wrong.
{code:title=.classpath|borderStype = solid}
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-267) AnalyzeDepMgt Check if DepMgt overrides a (parent's) Transitive Dependency
AnalyzeDepMgt Check if DepMgt overrides a (parent's) Transitive Dependency -- Key: MDEP-267 URL: http://jira.codehaus.org/browse/MDEP-267 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Cole Mickens Assignee: Brian Fox Attachments: test-case.zip Unzip the test-case. In testArtifactParent, run `mvn -DskipTests=true install`. In testArtifactChild, run `mvn -DskipTests=true dependency:tree`. When it lists the tree, it prints: [INFO] testGroup:testArtifactChild:jar:0.0.1-SNAPSHOT [INFO] +- commons-beanutils:commons-beanutils:jar:1.8.3:compile [INFO] +- commons-logging:commons-logging:jar:1.0.4:compile [INFO] \- junit:junit:jar:4.8.1:test If you remove 'commons-logging:commons-logging:jar' from the section of the child pom, you get: [INFO] +- commons-beanutils:commons-beanutils:jar:1.8.3:compile [INFO] | \- commons-logging:commons-logging:jar:1.0.4:compile (version managed from 1.1.1) [INFO] \- junit:junit:jar:4.8.1:test As you can see, the warning "version managed from x.x.x" is only printed out when the child doesn't declare a dependency on that package. (Possibly due to how DependencyNode render's itself based on whether or not it is a duplicate). I'm trying to write a new mojo for the Dependency plugin but I'm having trouble getting a list of ALL project dependencies. Clearly the Dependency plugin has access to this because (at least in one case) it is aware that a dependency was overriden by the section. I think that the AnalyzeDepMgt mojo should probably be updated to include a warning if a managed dependency is overriding a transitive dependency. Ironically it was originally meant to do more or less the opposite. That maybe confusing and I already have a skeleton for a new mojo to add, but like I said, I'm having difficulties getting that "full list of dependencies". Hopefully this gives some more context. I'm going to pour through the DependencyNode stuff, try to figure out where that "version managed from" logic comes from and then implement/call that in the new AnalyzeDepMgtOverrides mojo I'm working on. Any input on how this list might be easily discovered would be appreciated! -- 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-477) href's drop the leading character in the href when staging a site
[
http://jira.codehaus.org/browse/MSITE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MSITE-477:
---
Fix Version/s: 3.0-alpha-1
> href's drop the leading character in the href when
> staging a site
> ---
>
> Key: MSITE-477
> URL: http://jira.codehaus.org/browse/MSITE-477
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0.1, 2.1
>Reporter: Andrew Hughes
>Assignee: Dennis Lundberg
> Fix For: 2.1.1, 3.0-alpha-1
>
> Attachments: MSITE-477-site-deploy-output.rar, MSITE-477.rar
>
>
> parent pom.xml:
> {noformat}
> module-a
> {noformat}
> parent site.xml:
> {noformat}
>
> {noformat}
> The generated html links to "module-a" look like this
> {noformat}
> module-a
> {noformat}
> Note, the href is missing the leading character "m", it should be..
> {noformat}
> module-a
> {noformat}
> I tried to run this wil 2.0.1 and 2.1 - but got the same result with both.
> Hopfully this is a mis-configuration on my part, but if it is then perhaps it
> can be tested by the plugin and can fail the build.
> Thanks for reading :)
--
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
