[jira] Commented: (MINVOKER-28) Cant find mvn command
[ http://jira.codehaus.org/browse/MINVOKER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130619#action_130619 ] Paul Cager commented on MINVOKER-28: This was due to a bug in the Debian packaging of Maven2, which is now fixed. There should have been a symlink from /usr/share/maven2 to /usr/bin/mvn. The fix should percolate into Ubuntu in due course. > Cant find mvn command > - > > Key: MINVOKER-28 > URL: http://jira.codehaus.org/browse/MINVOKER-28 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: Ubuntu Linux Gutsy Gibbon with the Maven 2.0.8 package > from debian testing >Reporter: Manfred Moser > Attachments: invoker.log > > > When running an invoker plugin build a null pointer exception occurs because > the mvn command is not found with the above configuration. The issue is that > the plugin assumes that the mvn command is in M2_HOME/bin. This is not the > case with the maven debian package since it complies to the standards and has > the mvn command in /usr/bin where as M2_HOME points to /usr/share/maven2/. -- 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: (MINVOKER-28) Cant find mvn command
[ http://jira.codehaus.org/browse/MINVOKER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MINVOKER-28. Resolution: Won't Fix > Cant find mvn command > - > > Key: MINVOKER-28 > URL: http://jira.codehaus.org/browse/MINVOKER-28 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: Ubuntu Linux Gutsy Gibbon with the Maven 2.0.8 package > from debian testing >Reporter: Manfred Moser > Attachments: invoker.log > > > When running an invoker plugin build a null pointer exception occurs because > the mvn command is not found with the above configuration. The issue is that > the plugin assumes that the mvn command is in M2_HOME/bin. This is not the > case with the maven debian package since it complies to the standards and has > the mvn command in /usr/bin where as M2_HOME points to /usr/share/maven2/. -- 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-3518) Handle date qualifier in DefaultArtifactVersion
Handle date qualifier in DefaultArtifactVersion
---
Key: MNG-3518
URL: http://jira.codehaus.org/browse/MNG-3518
Project: Maven 2
Issue Type: Improvement
Components: Artifacts and Repositories
Affects Versions: 2.0.9
Reporter: Vincent Siveton
Attachments: DefaultArtifactVersion-handledate.diff
Eclipse artifacts use a date pattern in version qualifier and build fail with
the following error
{noformat}
[INFO] Failed to resolve artifact.
Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0)
org.eclipse.equinox:app:jar:null
{noformat}
The following patch adds javadoc for compareTo() to be more clear.
Also, it handles date pattern in the version to allow "1.0.0" <
"1.0.0-v20070606". Internally, it compares "1.0.0-19068845215" (ie new
Date(Integer.MAX_VALUE, 12, 31 )) to "1.0.0-20070606"
--
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-2018) Upload OpenOffice.org Java/Uno 2.4.0
Upload OpenOffice.org Java/Uno 2.4.0 Key: MAVENUPLOAD-2018 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2018 Project: maven-upload-requests Issue Type: Task Reporter: Mirko Nasato OpenOffice.org includes some JARs that can be used in a standalone Java app to connect to a running OpenOffice.org instance. Please find the bundles here: http://artofsolving.com/files/m2/juh-2.4.0-bundle.jar http://artofsolving.com/files/m2/jurt-2.4.0-bundle.jar http://artofsolving.com/files/m2/ridl-2.4.0-bundle.jar http://artofsolving.com/files/m2/unoil-2.4.0-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: (MNG-3519) Artifact finalName is not propagated to other modules.
Artifact finalName is not propagated to other modules.
--
Key: MNG-3519
URL: http://jira.codehaus.org/browse/MNG-3519
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 2.0.9
Environment: Maven 2.0.9, JDK 6, WinXP SP2
Reporter: Michael Osipov
Attachments: example.png
I have a multimodule project.
groupId: net.fckeditor
Parent ArtifactId: fckeditor-java
1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}"
though => e.g. fckeditor-java-core-2.4-SNAPSHOT
2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}"
though
module one is a jar artifact, module 2 a war artifact which has a dependency on
module 2.
the final WAR file contains all dependencies included the java-core but the jar
name is not fckeditor-java-core-2.4-SNAPSHOT.jar but java-core-2.4-SNAPSHOT.jar
The same happens in assembly and moduleSets.
An example picture is attached and the project can be checked out at our [trac
|http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4] and the
[SVN|http://svn.fckeditor.net/FCKeditor.Java/branches/2.4/] directly
--
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-3509) Make "mvn -v" output locale/encoding
[ http://jira.codehaus.org/browse/MNG-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-3509. -- Assignee: Herve Boutemy Resolution: Fixed fixed in trunk r647626 and 2.0.x branch r647627 > Make "mvn -v" output locale/encoding > > > Key: MNG-3509 > URL: http://jira.codehaus.org/browse/MNG-3509 > Project: Maven 2 > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.0.8 >Reporter: Benjamin Bentmann >Assignee: Herve Boutemy >Priority: Minor > Fix For: 2.0.10 > > Attachments: locale-output.patch > > > Printing a platform's locale and file encoding might be worth to add when > Maven is requested to show version information since these parameters can > affect text/string handling 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: (MNG-3520) Korean message resource
Korean message resource --- Key: MNG-3520 URL: http://jira.codehaus.org/browse/MNG-3520 Project: Maven 2 Issue Type: Improvement Components: Multiple Language Support Affects Versions: 2.0.9 Reporter: Keesun Baik Attachments: messages_ko.properties If I translate the message proeries to Korean, Can you add Korean message properies? I attached a Korean message properties, and I hope this file will be added to next release. Have a good day! -- 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: (MASSEMBLY-308) Syntax Problem in Example Doco
Syntax Problem in Example Doco
--
Key: MASSEMBLY-308
URL: http://jira.codehaus.org/browse/MASSEMBLY-308
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Environment:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/filtering-some-distribution-files.html
Reporter: Andrew Hughes
Priority: Minor
There's a problem with the examples
{noformat}
*.txt
{noformat}
should read
{noformat}
*.txt
{noformat}
in the example...
{noformat}
distribution
jar
${basedir}
*.txt
README.txt
NOTICE.txt
README.txt
/
true
NOTICE.txt
/
true
{noformat}
--
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: (MASSEMBLY-234) Artifacts not deployed
[
http://jira.codehaus.org/browse/MASSEMBLY-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130681#action_130681
]
thomas diesler commented on MASSEMBLY-234:
--
Actually, this is not well commented at all.
The FAQ page
http://maven.apache.org/plugins/maven-assembly-plugin/faq.html
reads
Q: If the Assembly Plugin is run during the package phase, do my assemblies get
deployed during the deploy phase?
A: Yes. The assemblies created by the Assembly Plugin is attached to your
project so it gets deployed too.
and does not mention the assembly:attached nor the assembly:single goal
> Artifacts not deployed
> --
>
> Key: MASSEMBLY-234
> URL: http://jira.codehaus.org/browse/MASSEMBLY-234
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-1
> Environment: Windows XP, Maven 2.0.7, Java 1.5.0_09, latest version
> of all conspiring Maven plugins
>Reporter: Brian Williams
>Assignee: John Casey
> Fix For: 2.2-beta-2
>
>
> I attached my two assembly descriptors to the package phase, they get created
> correctly, but only the original JAR of my project gets deployed when I run
> "mvn deploy". Each of my descriptors makes a ZIP containing the JAR my
> project compiles plus other resources (don't ask me why they don't want them
> as part of the JAR).
> When I declared version 2.1 for the assembly plugin, my two assemblies
> deployed with my original JAR. This is the relevant section of my POM.xml:
> {{
> maven-assembly-plugin
> 2.1
>
>
> package
>
>
> assembly/windows.xml
> assembly/linux.xml
>
>
> assembly
>
>
> }}
--
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
