[jira] (MDEPLOY-173) Enhance the Maven Deploy Plugin to support Flat POM
[ https://jira.codehaus.org/browse/MDEPLOY-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Jia updated MDEPLOY-173: - Description: *Problem* The pom.xml has dual purpose. 1. Building and distributing a jar 2. Used by another project for dependency management. For #1 build and distribution, pom.xml makes good sense with many sections and hierarchies. In this case the main objective is dealing with sources and various aspects of build. For #2, lets say project B needs the jar produced by project A ( #1), the only things B needs from A are, 1. jar files 2. dependencies of this jar file For #2 use-case, none of the sections or hierarchies of pom.xml make sense, except for .sections and GAV. Unfortunately maven simply copies the same pom.xml used for build to the repository for distribution. This problem gets complicated when there are pom hierarchies and sections In such cases, to resolve the dependencies of an artifact, maven needs to use more than one pom.xml. This results in complex release and patch process and potential build time issues. *Solution* Enhance the maven deploy plugin to deploy a "flattened" pom that contains only GAV and section. The section contains, properly resolved direct dependencies of the artifact, which are the same of "pom hierarchy" direct dependencies. "flattened" pom means it cannot have any parent or any other sections that are not necessary while deploying the artifact. Note that we may need to add removeMetadata method to org.apache.maven.artifact.Artifact interface to remove the original pom metadata and then add the "flattened" pom metadata. I have created jira issue http://jira.codehaus.org/browse/MNG-5544 for this function *Acceptance Criteria* 1. "mvn deploy" could deploy "flatten" pom onto maven repo and its "flatten" pom's dependencies version should be the same as versions of "pom hierachy". 2. "flatten" pom only contains GAV and section. 3. "flatten" pom only contains original direct dependencies, not including transitive dependencies. 4. "flatten" pom won't inherit from any parent pom. 5. The pom artifact (packaging is pom) will not be uploaded to repo because it has no meaning for "flatten" pom. was: *Problem* The pom.xml has dual purpose. 1. Building and distributing a jar 2. Used by another project for dependency management. For #1 build and distribution, pom.xml makes good sense with many sections and hierarchies. In this case the main objective is dealing with sources and various aspects of build. For #2, lets say project B needs the jar produced by project A ( #1), the only things B needs from A are, 1. jar files 2. dependencies of this jar file For #2 use-case, none of the sections or hierarchies of pom.xml make sense, except for .sections and GAV. Unfortunately maven simply copies the same pom.xml used for build to the repository for distribution. This problem gets complicated when there are pom hierarchies and sections In such cases, to resolve the dependencies of an artifact, maven needs to use more than one pom.xml. This results in complex release and patch process and potential build time issues. *Solution* Enhance the maven deploy plugin to deploy a "flattened" pom that contains only GAV and section. The section contains, properly resolved direct dependencies of the artifact, which are the same of "pom hierarchy" direct dependencies. "flattened" pom means it cannot have any parent or any other sections that are not necessary while deploying the artifact. Note that we may need to add removeMetadata method to org.apache.maven.artifact.Artifact interface to remove the original pom metadata and then add the "flattened" pom metadata. I have created jira issue http://jira.codehaus.org/browse/MNG-5544 for this function *Acceptance Criteria* 1. "mvn deploy" could deploy "flatten" pom onto maven repo and its "flatten" pom's dependencies version should be the same as versions of "pom hierachy". 2. "flatten" pom only contains GAV and section. 3. "flatten" pom only contains original direct dependencies, not including transitive dependencies. 4. "flatten" pom won't inherit from any parent pom. > Enhance the Maven Deploy Plugin to support Flat POM > --- > > Key: MDEPLOY-173 > URL: https://jira.codehaus.org/browse/MDEPLOY-173 > Project: Maven Deploy Plugin > Issue Type: New Feature > Components: deploy:deploy >Reporter: Jack Jia > > *Problem* > The pom.xml has dual purpose. > 1. Building and distributing a jar > 2. Used by another project for dependency management. > For #1 build and distribution, pom.xml makes good sense with many sections > and hierarchies. In this case the main objective is dealing with sources and > various aspects of build. > For #2, let
[jira] (MASSEMBLY-463) Assembly fails Problem creating war: JAR entry not found
[ https://jira.codehaus.org/browse/MASSEMBLY-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337628#comment-337628 ] Victor Williams Stafusa da Silva commented on MASSEMBLY-463: I think I'd run into this problem too. My builds sometimes randomly and non-deterministically fails claiming that it can't find a file inside my WAR package, but the file is always clearly there. If my build fails, I may run it once again and it might work. Sometimes it works right on the first try. Sometimes I need 2, 3 or 4 tries. Since (at least for me) it's random and non-deterministic, I think that some race condition might be the underlying cause. BTW, I am using Windows 7. > Assembly fails Problem creating war: JAR entry not found > > > Key: MASSEMBLY-463 > URL: https://jira.codehaus.org/browse/MASSEMBLY-463 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-5 > Environment: CentOS or Debian, Java 6.0-16 >Reporter: Mike Key > Attachments: distribution.xml, massembly-463.log, pom.xml > > > When doing a build through hudson on either a Debian or CentOS machine (the > only two I've tested) the assembly plugin fails with a message like this: > Failed to create assembly: Error creating assembly archive distribution: > Problem creating war: JAR entry [[filename.random]] not found in > /path/to/war/extracted/from > In this depending on what maven options are used, various different files > show up as not found in the war being extracted from to create the assembly. > However, the file ALWAYS exists. > This issue ONLY occurs when the build goals include the 'deploy' goal. In > other words, if I run 'mvn clean package' or mvn clean install' the issue > does not exist, but if I run 'mvn clean package deploy' or 'mvn clean install > deploy' the assembly fails. > Note that USUALLY, running another build seems to clear up the issue, but not > always. But the issue does break out CI process. > Attached is the assembly itself. I was never able to associate any change to > this assembly contributing to the start of this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-301) use plexus java 5 annotations instead of plexus javadoc tags
[ https://jira.codehaus.org/browse/MSHARED-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337627#comment-337627 ] Herve Boutemy commented on MSHARED-301: --- done in [r1541091|http://svn.apache.org/r1541091] > use plexus java 5 annotations instead of plexus javadoc tags > > > Key: MSHARED-301 > URL: https://jira.codehaus.org/browse/MSHARED-301 > Project: Maven Shared Components > Issue Type: Task > Components: maven-jarsigner >Affects Versions: maven-jarsigner-1.1 >Reporter: Herve Boutemy >Assignee: Tony Chemit >Priority: Minor > Fix For: maven-jarsigner-1.2 > > > Java 5 annotations ease maintenance > see http://plexus.codehaus.org/plexus-containers/plexus-component-annotations/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-301) use plexus java 5 annotations instead of plexus javadoc tags
[ https://jira.codehaus.org/browse/MSHARED-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-301: Issue Type: Task (was: Bug) > use plexus java 5 annotations instead of plexus javadoc tags > > > Key: MSHARED-301 > URL: https://jira.codehaus.org/browse/MSHARED-301 > Project: Maven Shared Components > Issue Type: Task > Components: maven-jarsigner >Affects Versions: maven-jarsigner-1.1 >Reporter: Herve Boutemy >Assignee: Tony Chemit >Priority: Minor > Fix For: maven-jarsigner-1.2 > > > Java 5 annotations ease maintenance > see http://plexus.codehaus.org/plexus-containers/plexus-component-annotations/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-304) Create a API for java tool
[ https://jira.codehaus.org/browse/MSHARED-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-304. --- Resolution: Fixed > Create a API for java tool > -- > > Key: MSHARED-304 > URL: https://jira.codehaus.org/browse/MSHARED-304 > Project: Maven Shared Components > Issue Type: New Feature >Affects Versions: maven-shared-utils-0.4 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-shared-utils-0.5 > > > While using the commandline API to invoke java tool (*jarsigner*, *keytool*, > *javadoc*), we always write the same boilerplate code: > - find the java tool executable location > - build a new command line > - invoke it and deal with invocation errors > - ... > Let's have a simple API for this! As a first improvement then let's add to it > also the support for toolchain (asked in maven-jarsigner-plugin). > I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-305. --- Resolution: Fixed > Use maven-shared-utils javatool API > --- > > Key: MSHARED-305 > URL: https://jira.codehaus.org/browse/MSHARED-305 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-jarsigner-1.1 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-jarsigner-1.2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reopened MSHARED-305: - > Use maven-shared-utils javatool API > --- > > Key: MSHARED-305 > URL: https://jira.codehaus.org/browse/MSHARED-305 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-jarsigner-1.1 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-jarsigner-1.2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5552) Classified artifacts are missing from ${project.artifactMap}
[
https://jira.codehaus.org/browse/MNG-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5552:
---
Description: Classified artifacts are missing from
{{$\{project.artifactMap}}}, so I can't inject them all in my plugins or use
$\{project.artifactMap(group:artifact:classifier)} to pick individual
dependencies. (was: Classified artifacts are missing from
$\{project.artifactMap}, so I can't inject them all in my plugins or use
$\{project.artifactMap(group:artifact:classifier)} to pick individual
dependencies.)
> Classified artifacts are missing from ${project.artifactMap}
>
>
> Key: MNG-5552
> URL: https://jira.codehaus.org/browse/MNG-5552
> Project: Maven 2 & 3
> Issue Type: Bug
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.1.2
>
>
> Classified artifacts are missing from {{$\{project.artifactMap}}}, so I can't
> inject them all in my plugins or use
> $\{project.artifactMap(group:artifact:classifier)} to pick individual
> dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5552) Classified artifacts are missing from ${project.artifactMap}
[
https://jira.codehaus.org/browse/MNG-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5552:
---
Description: Classified artifacts are missing from
{{$\{project.artifactMap}}}, so I can't inject them all in my plugins or use
{{$\{project.artifactMap(group:artifact:classifier)}}} to pick individual
dependencies. (was: Classified artifacts are missing from
{{$\{project.artifactMap}}}, so I can't inject them all in my plugins or use
$\{project.artifactMap(group:artifact:classifier)} to pick individual
dependencies.)
> Classified artifacts are missing from ${project.artifactMap}
>
>
> Key: MNG-5552
> URL: https://jira.codehaus.org/browse/MNG-5552
> Project: Maven 2 & 3
> Issue Type: Bug
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.1.2
>
>
> Classified artifacts are missing from {{$\{project.artifactMap}}}, so I can't
> inject them all in my plugins or use
> {{$\{project.artifactMap(group:artifact:classifier)}}} to pick individual
> dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5552) Classified artifacts are missing from ${project.artifactMap}
[
https://jira.codehaus.org/browse/MNG-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5552:
---
Description: Classified artifacts are missing from $\{project.artifactMap},
so I can't inject them all in my plugins or use
$\{project.artifactMap(group:artifact:classifier)} to pick individual
dependencies. (was: Classified artifacts are missing from
$\{project.artifactMap}, so I can't inject them all in my plugins or use
${project.artifactMap(group:artifact:classifier)} to pick individual
dependencies.)
> Classified artifacts are missing from ${project.artifactMap}
>
>
> Key: MNG-5552
> URL: https://jira.codehaus.org/browse/MNG-5552
> Project: Maven 2 & 3
> Issue Type: Bug
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.1.2
>
>
> Classified artifacts are missing from $\{project.artifactMap}, so I can't
> inject them all in my plugins or use
> $\{project.artifactMap(group:artifact:classifier)} to pick individual
> dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5552) Classified artifacts are missing from ${project.artifactMap}
[
https://jira.codehaus.org/browse/MNG-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5552:
---
Description: Classified artifacts are missing from \${project.artifactMap},
so I can't inject them all in my plugins or use
${project.artifactMap(group:artifact:classifier)} to pick individual
dependencies. (was: Classified artifacts are missing from
${project.artifactMap}, so I can't inject them all in my plugins or use
${project.artifactMap(group:artifact:classifier)} to pick individual
dependencies.)
> Classified artifacts are missing from ${project.artifactMap}
>
>
> Key: MNG-5552
> URL: https://jira.codehaus.org/browse/MNG-5552
> Project: Maven 2 & 3
> Issue Type: Bug
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.1.2
>
>
> Classified artifacts are missing from \${project.artifactMap}, so I can't
> inject them all in my plugins or use
> ${project.artifactMap(group:artifact:classifier)} to pick individual
> dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5552) Classified artifacts are missing from ${project.artifactMap}
[
https://jira.codehaus.org/browse/MNG-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5552:
---
Description: Classified artifacts are missing from $\{project.artifactMap},
so I can't inject them all in my plugins or use
${project.artifactMap(group:artifact:classifier)} to pick individual
dependencies. (was: Classified artifacts are missing from
\${project.artifactMap}, so I can't inject them all in my plugins or use
${project.artifactMap(group:artifact:classifier)} to pick individual
dependencies.)
> Classified artifacts are missing from ${project.artifactMap}
>
>
> Key: MNG-5552
> URL: https://jira.codehaus.org/browse/MNG-5552
> Project: Maven 2 & 3
> Issue Type: Bug
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.1.2
>
>
> Classified artifacts are missing from $\{project.artifactMap}, so I can't
> inject them all in my plugins or use
> ${project.artifactMap(group:artifact:classifier)} to pick individual
> dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-304) Create a API for java tool
[ https://jira.codehaus.org/browse/MSHARED-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reopened MSHARED-304: - > Create a API for java tool > -- > > Key: MSHARED-304 > URL: https://jira.codehaus.org/browse/MSHARED-304 > Project: Maven Shared Components > Issue Type: New Feature >Affects Versions: maven-shared-utils-0.4 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-shared-utils-0.5 > > > While using the commandline API to invoke java tool (*jarsigner*, *keytool*, > *javadoc*), we always write the same boilerplate code: > - find the java tool executable location > - build a new command line > - invoke it and deal with invocation errors > - ... > Let's have a simple API for this! As a first improvement then let's add to it > also the support for toolchain (asked in maven-jarsigner-plugin). > I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-146) Release tag with SVN under Cygwin fails when sending the svn command a bad absolute path
[
https://jira.codehaus.org/browse/MRELEASE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337614#comment-337614
]
Robert Scholte commented on MRELEASE-146:
-
@[~ahoehma], the problem is not of the maven-release-plugin. If it is still an
issue, it's of the
[maven-scm-providers-svn|http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-svn/index.html].
Any clue where this path is coming from?
{{/cygdrive/d/DEV/ws_hscm/goos-tools/D:/DEV/ws_hscm}}
> Release tag with SVN under Cygwin fails when sending the svn command a bad
> absolute path
>
>
> Key: MRELEASE-146
> URL: https://jira.codehaus.org/browse/MRELEASE-146
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: scm
>Affects Versions: 2.0-beta-4
> Environment: Windows XP
>Reporter: Christian Gruber
>
> When release:prepare is invoked, on a cygwin system using svn provided with
> cygwin, the following error occurs.
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --non-interactive commit --file
> E:\DOCUME~1\CGRUBE~1.DJI\LOCALS~1\Temp\maven-scm-1141263545.commit
> E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml
> [INFO] Working directory: E:\projects\israfil-fw\net.israfil.foundation-JDK1.4
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn:
> '/projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4'
> is not a working copy
> ...
> SVN on cygwin interprets
> E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml to be
> /projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4,
> essentially appending the absolute path on the current working driectory as
> if it were a relative path.
> This is very odd, since "svn
> E:/projects/israfil-fw/net.israfil.foundation-JDK1.4" works like a charm. I
> tried it with E: and e: to no avail.
> Proposed solution: Use relative paths
> Alternative - really really bad alternative: detect the presence of cygwin
> and re-structure the file path to use /cygdrive/e/blah/blah format.
> Ultimate remedy: Figure out why SVN is interpreting this way and fix in svn.
> -Christian.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-355) Expose PreferredAuthentications property of jsch in some way
[
https://jira.codehaus.org/browse/WAGON-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337616#comment-337616
]
Anthony Whitford commented on WAGON-355:
Actually, it seems that the default value for {{PreferredAuthentications}} is:
{noformat}gssapi-with-mic,publickey,keyboard-interactive,password{noformat}
The
[logic|http://maven.apache.org/wagon/wagon-providers/wagon-ssh/xref/org/apache/maven/wagon/providers/ssh/jsch/AbstractJschWagon.html#224]
is revising it if a password is detected -- it changes it to:
{noformat}gssapi-with-mic,publickey,password,keyboard-interactive{noformat}
(Now, password is specified before a keyboard prompt.)
> Expose PreferredAuthentications property of jsch in some way
>
>
> Key: WAGON-355
> URL: https://jira.codehaus.org/browse/WAGON-355
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-ssh
>Affects Versions: 2.0
> Environment: Any. I happened to test with Maven 2.2.1 and jdk 1.7
>Reporter: Lester Ward
>Priority: Minor
>
> Deploy using scp. Under jdk 1.7, support for gssapi-with-mic works
> differently than it did under jdk 1.6, to the point where we do not want to
> use it. Ultimately, the deploy plugin uses the jsch library to deploy using
> scp. This library has an property called PreferredAuthentications which
> controls which authentications get used, in which order. The code in
> AbstractJschWagon hard-codes
> "gssapi-with-mic,publickey,password,keyboard-interactive" into this property.
> I'd like a way to somehow override that, preferably in my project's pom file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5552) Classified artifacts are missing from ${project.artifactMap}
[
https://jira.codehaus.org/browse/MNG-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Fedorenko closed MNG-5552.
---
Resolution: Fixed
Fix Version/s: 3.1.2
Assignee: Igor Fedorenko
Fixed.
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=f35698c790da5329590d1ceba0502c02f942efdf
> Classified artifacts are missing from ${project.artifactMap}
>
>
> Key: MNG-5552
> URL: https://jira.codehaus.org/browse/MNG-5552
> Project: Maven 2 & 3
> Issue Type: Bug
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.1.2
>
>
> Classified artifacts are missing from ${project.artifactMap}, so I can't
> inject them all in my plugins or use
> ${project.artifactMap(group:artifact:classifier)} to pick individual
> dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5552) Classified artifacts are missing from ${project.artifactMap}
Igor Fedorenko created MNG-5552:
---
Summary: Classified artifacts are missing from
${project.artifactMap}
Key: MNG-5552
URL: https://jira.codehaus.org/browse/MNG-5552
Project: Maven 2 & 3
Issue Type: Bug
Reporter: Igor Fedorenko
Classified artifacts are missing from ${project.artifactMap}, so I can't inject
them all in my plugins or use ${project.artifactMap(group:artifact:classifier)}
to pick individual dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-146) Release tag with SVN under Cygwin fails when sending the svn command a bad absolute path
[ https://jira.codehaus.org/browse/MRELEASE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337593#comment-337593 ] Andreas Höhmann edited comment on MRELEASE-146 at 12/17/13 4:31 AM: Please reopen this bug. I'm using version 2.4.2. and still have this problem. I tried C:\Users\hoehmann\.scm\svn-settings.xml I tried /home/hoehmann/.scm/svn-settings.xml true /cygwin mvn release:prepare crash with [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on project goos-tools: Unable to commit files [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: E155010: Commit failed (details follow): [ERROR] svn: E155010: The node '/cygdrive/d/DEV/ws_hscm/goos-tools/D:/DEV/ws_hscm' was not found. [ERROR] -> [Help 1] was (Author: ahoehma): Please reopen this bug. I'm using version 2.4.2. and still have this problem. I tried C:\Users\hoehmann\.scm\svn-settings.xml I tried /home/hoehmann/.scm/svn-settings.xml mvn release:prepare crash with [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on project goos-tools: Unable to commit files [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: E155010: Commit failed (details follow): [ERROR] svn: E155010: The node '/cygdrive/d/DEV/ws_hscm/goos-tools/D:/DEV/ws_hscm' was not found. [ERROR] -> [Help 1] > Release tag with SVN under Cygwin fails when sending the svn command a bad > absolute path > > > Key: MRELEASE-146 > URL: https://jira.codehaus.org/browse/MRELEASE-146 > Project: Maven Release Plugin > Issue Type: Bug > Components: scm >Affects Versions: 2.0-beta-4 > Environment: Windows XP >Reporter: Christian Gruber > > When release:prepare is invoked, on a cygwin system using svn provided with > cygwin, the following error occurs. > [INFO] Checking in modified POMs... > [INFO] Executing: svn --non-interactive commit --file > E:\DOCUME~1\CGRUBE~1.DJI\LOCALS~1\Temp\maven-scm-1141263545.commit > E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml > [INFO] Working directory: E:\projects\israfil-fw\net.israfil.foundation-JDK1.4 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Unable to commit files > Provider message: > The svn command failed. > Command output: > svn: > '/projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4' > is not a working copy > ... > SVN on cygwin interprets > E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml to be > /projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4, > essentially appending the absolute path on the current working driectory as > if it were a relative path. > This is very odd, since "svn > E:/projects/israfil-fw/net.israfil.foundation-JDK1.4" works like a charm. I > tried it with E: and e: to no avail. > Proposed solution: Use relative paths > Alternative - really really bad alternative: detect the presence of cygwin > and re-structure the file path to use /cygdrive/e/blah/blah format. > Ultimate remedy: Figure out why SVN is interpreting this way and fix in svn. > -Christian. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-146) Release tag with SVN under Cygwin fails when sending the svn command a bad absolute path
[ https://jira.codehaus.org/browse/MRELEASE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337593#comment-337593 ] Andreas Höhmann commented on MRELEASE-146: -- Please reopen this bug. I'm using version 2.4.2. and still have this problem. I tried C:\Users\hoehmann\.scm\svn-settings.xml I tried /home/hoehmann/.scm/svn-settings.xml mvn release:prepare crash with [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on project goos-tools: Unable to commit files [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: E155010: Commit failed (details follow): [ERROR] svn: E155010: The node '/cygdrive/d/DEV/ws_hscm/goos-tools/D:/DEV/ws_hscm' was not found. [ERROR] -> [Help 1] > Release tag with SVN under Cygwin fails when sending the svn command a bad > absolute path > > > Key: MRELEASE-146 > URL: https://jira.codehaus.org/browse/MRELEASE-146 > Project: Maven Release Plugin > Issue Type: Bug > Components: scm >Affects Versions: 2.0-beta-4 > Environment: Windows XP >Reporter: Christian Gruber > > When release:prepare is invoked, on a cygwin system using svn provided with > cygwin, the following error occurs. > [INFO] Checking in modified POMs... > [INFO] Executing: svn --non-interactive commit --file > E:\DOCUME~1\CGRUBE~1.DJI\LOCALS~1\Temp\maven-scm-1141263545.commit > E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml > [INFO] Working directory: E:\projects\israfil-fw\net.israfil.foundation-JDK1.4 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Unable to commit files > Provider message: > The svn command failed. > Command output: > svn: > '/projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4' > is not a working copy > ... > SVN on cygwin interprets > E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml to be > /projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4, > essentially appending the absolute path on the current working driectory as > if it were a relative path. > This is very odd, since "svn > E:/projects/israfil-fw/net.israfil.foundation-JDK1.4" works like a charm. I > tried it with E: and e: to no avail. > Proposed solution: Use relative paths > Alternative - really really bad alternative: detect the presence of cygwin > and re-structure the file path to use /cygdrive/e/blah/blah format. > Ultimate remedy: Figure out why SVN is interpreting this way and fix in svn. > -Christian. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-433) outputType=graphml does not work when verbose is set
[ https://jira.codehaus.org/browse/MDEP-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Schaefer updated MDEP-433: -- Priority: Minor (was: Major) > outputType=graphml does not work when verbose is set > > > Key: MDEP-433 > URL: https://jira.codehaus.org/browse/MDEP-433 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: tree >Affects Versions: 2.8 > Environment: Apache Maven 3.0.5 > (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) > Java version: 1.7.0_21, vendor: Oracle Corporation > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" >Reporter: Max Schaefer >Priority: Minor > > Creating dependency tree with parameter "verbose" and outputType set to > graphml does not generate graphml format. > E.g. > mvn dependency:tree -DoutputType=graphml -DoutputFile=dependency.graphml > -Dverbose > generates the txt format. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-433) outputType=graphml does not work when verbose is set
Max Schaefer created MDEP-433: - Summary: outputType=graphml does not work when verbose is set Key: MDEP-433 URL: https://jira.codehaus.org/browse/MDEP-433 Project: Maven Dependency Plugin Issue Type: Bug Components: tree Affects Versions: 2.8 Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Java version: 1.7.0_21, vendor: Oracle Corporation Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" Reporter: Max Schaefer Creating dependency tree with parameter "verbose" and outputType set to graphml does not generate graphml format. E.g. mvn dependency:tree -DoutputType=graphml -DoutputFile=dependency.graphml -Dverbose generates the txt format. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
