[jira] Commented: (MSITE-339) site:deploy fails on HP-UX due to invalid chmod option
[
http://jira.codehaus.org/browse/MSITE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139100#action_139100
]
Lukas Theussl commented on MSITE-339:
-
This was fixed in m1: MPSITE-31
> site:deploy fails on HP-UX due to invalid chmod option
> --
>
> Key: MSITE-339
> URL: http://jira.codehaus.org/browse/MSITE-339
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 2.0-beta-6
> Environment: HP-UX v11.33 or HP-UX 11.11
>Reporter: Paul Spencer
>
> Deploying a site to an HP server running HP-UX version 11i Release 3 or
> Release 1 fails because the chmod does not support the "f" option.
> {code}
> ###
> Transfer finished. 108804 bytes copied in 0.141 seconds
> Executing command: cd /internal/geotab-webapp/1.0.2-SNAPSHOT/.; unzip -q -o
> wagon13079.zip; rm -f wagon1
> Executing command: chmod -Rf g+w,a+rX /internal/geotab-webapp/1.0.2-SNAPSHOT
> scp://projects.foo.com/internal/geotab-webapp/1.0.2-SNAPSHOT - Session:
> Disconnecting
> scp://projects.foo.com/internal/geotab-webapp/1.0.2-SNAPSHOT - Session:
> Disconnected
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error uploading site
> Embedded error: Exit code: 255 - chmod: invalid mode
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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:585)
> 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: Error uploading
> site
> at
> org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:216)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: org.apache.maven.wagon.CommandExecutionException: Exit code: 255 -
> chmod: invalid mode
> at
> org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.executeCommand(AbstractJschWagon.java:237)
> at
> org.apache.maven.wagon.providers.ssh.AbstractSshWagon.executeCommand(AbstractSshWagon.java:239)
> at
> org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:191)
> ... 18 more
> [INFO]
>
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Jun 19 12:25:05 EDT 2008
> [INFO] Final Memory: 6M/11M
> [INFO]
>
> {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
regarding creating new maven project
Hi I have download the maven2.0.9 and I have set the maven path. Then I have created one folder my-app, in that I have created pom.xml file. Then I executed this command like this C:\mvnapp>mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app I am getting the following error: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 32 seconds [INFO] Finished at: Fri Jun 20 12:03:47 IST 2008 [INFO] Final Memory: 1M/254M [INFO] My pom.xml file looks like this: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 com.mycompany.app my-app jar 1.0-SNAPSHOT Maven Quick Start Archetype http://maven.apache.org junit junit 3.8.1 test So please anything else need to configure and anything else modify to it pom.xml file. Please help in this I need urgent. Is there any required to additional configuration. Thanks in Advance. Regards, KRReddy DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.
[jira] Commented: (SCM-182) git provider
[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139099#action_139099
]
Torbjørn Vatn commented on SCM-182:
I'm having some issues getting this provider to work sadly. So far I've tried
this:
1. git cloning http://ns1.backwork.net/git/maven-scm-providers-git.git and
running mvn clean install
2. vim'ing into
.m2/repository/org/apache/maven/scm/maven-scm-providers/1.0/maven-scm-providers-1.0.pom
and adding maven-scm-providers-git in the modules section of
the file.
3. Adding this to my projects pom.xml:
scm:git:git://github.com/torbjornvatn/fitnesse-pom-widget.git
scm:git:git://github.com/torbjornvatn/fitnesse-pom-widget.git
4. running scm:status only gives my the error message:
[ERROR] BUILD ERROR
[INFO]
[INFO] Cannot run status command :
Embedded error: Can't load the scm provider.
No such provider: 'git'.
Can anyone give my some pointers to what I'm doing wrong. I'm a big fan of git
and really wants to get this maven provider working.
Thanks in advance!
> git provider
>
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
>Reporter: Dominik Winter
>Assignee: Jason van Zyl
> Fix For: 1.1
>
> Attachments: git.patch, git.tar.bz2, SCM-182.patch, update1.patch.bz2
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.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] Updated: (MAVENUPLOAD-2111) SAT4J bundles ready for inclusion in Maven Central repository
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Le Berre updated MAVENUPLOAD-2111:
-
Attachment: pom.xml
Jason,
Here is the parent pom.
Am I supposed to add it in my bundles by hand?
I tried to run respository:bundle-create on my parent folder but I got the
following error:
[EMAIL PROTECTED] MAVEN]$ mvn -Dmaven.test.skip=true repository:bundle-create
Warning: JAVA_HOME environment variable is not set.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] SAT4J
[INFO] SAT4J core
[INFO] SAT4J pseudo
[INFO] SAT4J multicore
[INFO] SAT4J maxsat
[INFO] SAT4J sat
[INFO] SAT4J csp xml parser
[INFO] SAT4J csp
[INFO] Searching repository for plugin with prefix: 'repository'.
WAGON_VERSION: 1.0-beta-2
[INFO]
[INFO] Building SAT4J
[INFO]task-segment: [repository:bundle-create]
[INFO]
[INFO] Preparing repository:bundle-create
[INFO] [site:attach-descriptor]
[INFO] Preparing javadoc:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [javadoc:jar {execution: attach-javadocs}]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable
package
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] [repository:bundle-create]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Packaging cannot be POM when creating an upload bundle.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 10 seconds
[INFO] Finished at: Fri Jun 20 07:36:23 CEST 2008
[INFO] Final Memory: 11M/21M
[INFO]
[
> SAT4J bundles ready for inclusion in Maven Central repository
> -
>
> Key: MAVENUPLOAD-2111
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2111
> Project: Maven Upload Requests
> Issue Type: New Feature
>Reporter: Daniel Le Berre
>Assignee: Jason van Zyl
> Attachments: pom.xml
>
>
> I am the leader of the SAT4J project.
> SAT4J will be used in the next release of Maven to manage dependencies, in a
> way similar to Eclipse p2.
> Here are bundles of SAT4J core and SAT4J pb ready to be consumed by Maven
> developers (Oleg and Jason).
> The version is 2.0.1 and not 2.0.0 since I fixed two small issues in that
> code, that will not affect the current 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] Issue Comment Edited: (MANTRUN-75) tasks if or unless does not work properly
[
http://jira.codehaus.org/browse/MANTRUN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139096#action_139096
]
baerrach edited comment on MANTRUN-75 at 6/20/08 12:19 AM:
-
A work around is to use a profile:
{code:xml}
your-id-here
property-to-use-to-turn-on
org.apache.maven.plugins
maven-antrun-plugin
your-execution-id-here
generate-resources
run
{code}
Then to get this antrun profile use
{code} mvn install -Dproperty-to-use-to-turn-on{code}
which will enable this profile and hence run your antrun task.
was (Author: baerrach):
A work around is to use a profile:
your-id-here
property-to-use-to-turn-on
org.apache.maven.plugins
maven-antrun-plugin
your-execution-id-here
generate-resources
run
Then to get this antrun profile use
mvn install -Dproperty-to-use-to-turn-on
which will enable this profile and hence run your antrun task.
> tasks if or unless does not work properly
> --
>
> Key: MANTRUN-75
> URL: http://jira.codehaus.org/browse/MANTRUN-75
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
> Environment: Win XP ( CYGWIN) JDK 1.5 update 7
>Reporter: Alan Mehio
> Attachments: mantrun-75.diff
>
>
> the below
>
>
>
> does not work from the example at
> http://maven.apache.org/plugins/maven-antrun-plugin/examples/tasksAttributes.html
> The complete POM file ; please see below
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://vmaven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> mygr
> myartifact
> pom
> 1.1.0
> myartifact
> http://maven.apache.org
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.5
> 1.5
>
>
>
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
>
>
> true
>
> ./
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
>
> commons-net
>
> commons-net
> 1.4.1
>
>
> ant
>
> ant-commons-net
> 1.6.5
>
>
>
>
> install
> install
>
>unless="maven.test.skip">
>
> message="To
[jira] Commented: (MANTRUN-75) tasks if or unless does not work properly
[
http://jira.codehaus.org/browse/MANTRUN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139096#action_139096
]
Barrie Treloar commented on MANTRUN-75:
---
A work around is to use a profile:
your-id-here
property-to-use-to-turn-on
org.apache.maven.plugins
maven-antrun-plugin
your-execution-id-here
generate-resources
run
Then to get this antrun profile use
mvn install -Dproperty-to-use-to-turn-on
which will enable this profile and hence run your antrun task.
> tasks if or unless does not work properly
> --
>
> Key: MANTRUN-75
> URL: http://jira.codehaus.org/browse/MANTRUN-75
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
> Environment: Win XP ( CYGWIN) JDK 1.5 update 7
>Reporter: Alan Mehio
> Attachments: mantrun-75.diff
>
>
> the below
>
>
>
> does not work from the example at
> http://maven.apache.org/plugins/maven-antrun-plugin/examples/tasksAttributes.html
> The complete POM file ; please see below
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://vmaven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> mygr
> myartifact
> pom
> 1.1.0
> myartifact
> http://maven.apache.org
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.5
> 1.5
>
>
>
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
>
>
> true
>
> ./
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
>
> commons-net
>
> commons-net
> 1.4.1
>
>
> ant
>
> ant-commons-net
> 1.6.5
>
>
>
>
> install
> install
>
>unless="maven.test.skip">
>
> message="To skip me, just call mvn -Dmaven.test.skip=true" />
>
> message="Alan Mehio ---: project.build.finalName: ${basedir}/build.xml" />
>
>
>
> run
>
>
>
>
>
>
>
> the command I run is
> mvn clean install -Dmaven.test.skip=true
> it did not skip the "tasks" and it always go through the tasks
> I use t
[jira] Commented: (MAVENUPLOAD-2111) SAT4J bundles ready for inclusion in Maven Central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139093#action_139093 ] Jason van Zyl commented on MAVENUPLOAD-2111: Daniel, you are referring to a parent POM but where is the parent POM? I don't see if in the bundles, and if the parent is not deployed the resolution is not going to work. > SAT4J bundles ready for inclusion in Maven Central repository > - > > Key: MAVENUPLOAD-2111 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2111 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Daniel Le Berre >Assignee: Jason van Zyl > > I am the leader of the SAT4J project. > SAT4J will be used in the next release of Maven to manage dependencies, in a > way similar to Eclipse p2. > Here are bundles of SAT4J core and SAT4J pb ready to be consumed by Maven > developers (Oleg and Jason). > The version is 2.0.1 and not 2.0.0 since I fixed two small issues in that > code, that will not affect the current 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: (MECLIPSE-462) Allow generating elements in .project via eclipse:eclipse
Allow generating elements in .project via eclipse:eclipse
---
Key: MECLIPSE-462
URL: http://jira.codehaus.org/browse/MECLIPSE-462
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: Core : Dependencies resolution and build path
Affects Versions: 2.5.1
Reporter: MG
Example:
src-2
2
${base_dir}/common/common-coreui/src/main/java
src-1
2
${base_dir}/tiger/tiger-ui/src/main/java
--
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-2113) maven-license-plugin-1.3.1 upload request
maven-license-plugin-1.3.1 upload request - Key: MAVENUPLOAD-2113 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2113 Project: Maven Upload Requests Issue Type: Wish Reporter: Mathieu Carbou Attachments: maven-license-plugin-1.3.1-bundle.jar http://maven-license-plugin.googlecode.com/files/maven-license-plugin-1.3.1-bundle.jar http://code.google.com/p/maven-license-plugin/ I'm the developer of the maven license plugin, please upload! Mathieu Carbou. -- 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-2112) GWT-Widgets: Setup Unofficial Maintainer
GWT-Widgets: Setup Unofficial Maintainer Key: MAVENUPLOAD-2112 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2112 Project: Maven Upload Requests Issue Type: Bug Reporter: Ryan Heaton "net.sf.gwt-widget","[EMAIL PROTECTED]:/home/users/s/st/stoicflame/m2","rsync_ssh","Ryan Heaton","[EMAIL PROTECTED]",, I would like to take the responsibility of being the "unofficial maintainer" of the GWT Widget library in the m2 repo according to the "Guide to uploading artifacts to the Central Repository". The open-source project I work on leverages GWT. -- 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-3626) Improve pom to handle i18n fields
Improve pom to handle i18n fields
-
Key: MNG-3626
URL: http://jira.codehaus.org/browse/MNG-3626
Project: Maven 2
Issue Type: Improvement
Components: POM
Affects Versions: 2.0.x
Reporter: Vincent Siveton
Some fields like name or description could be internationalized. I see the
following:
{noformat}
...
English description.
Deutsch description.
French description.
...
{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] Created: (MSITE-339) site:deploy fails on HP-UX due to invalid chmod option
site:deploy fails on HP-UX due to invalid chmod option
--
Key: MSITE-339
URL: http://jira.codehaus.org/browse/MSITE-339
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: site:deploy
Affects Versions: 2.0-beta-6
Environment: HP-UX v11.33 or HP-UX 11.11
Reporter: Paul Spencer
Deploying a site to an HP server running HP-UX version 11i Release 3 or Release
1 fails because the chmod does not support the "f" option.
{code}
###
Transfer finished. 108804 bytes copied in 0.141 seconds
Executing command: cd /internal/geotab-webapp/1.0.2-SNAPSHOT/.; unzip -q -o
wagon13079.zip; rm -f wagon1
Executing command: chmod -Rf g+w,a+rX /internal/geotab-webapp/1.0.2-SNAPSHOT
scp://projects.foo.com/internal/geotab-webapp/1.0.2-SNAPSHOT - Session:
Disconnecting
scp://projects.foo.com/internal/geotab-webapp/1.0.2-SNAPSHOT - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Exit code: 255 - chmod: invalid mode
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:585)
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: Error uploading site
at
org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:216)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.apache.maven.wagon.CommandExecutionException: Exit code: 255 -
chmod: invalid mode
at
org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.executeCommand(AbstractJschWagon.java:237)
at
org.apache.maven.wagon.providers.ssh.AbstractSshWagon.executeCommand(AbstractSshWagon.java:239)
at
org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:191)
... 18 more
[INFO]
[INFO] Total time: 7 seconds
[INFO] Finished at: Thu Jun 19 12:25:05 EDT 2008
[INFO] Final Memory: 6M/11M
[INFO]
{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] Commented: (MSITE-330) Wagon nukes the permission bits of uploaded files.
[
http://jira.codehaus.org/browse/MSITE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139045#action_139045
]
Paul Spencer commented on MSITE-330:
1) The command "chmod -Rf g+w,a+rX" fails on HP-UX servers because "f", which
is for silent output, is not an option.
2) I would prefer the file permissions, directory permissions, and chmod
options be in the tag since the values are
specific to the server. Each user should not have different values for the
tags.
{code:xml|title=pom.xml}
...
projects.foo.com
Foo.Com Project Site
scp://projectsfoo.com/${project.artifactId}/${project.version}
775
664
{code}
> Wagon nukes the permission bits of uploaded files.
> --
>
> Key: MSITE-330
> URL: http://jira.codehaus.org/browse/MSITE-330
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Reporter: Henning Schmiedehausen
>
> Uploading a site using wagon might nuke permission bits of e.g. CGI scripts
> thus making these unavailable.
> For Apache webserver, a CGI script can have the permission bit set and is
> then executed. This is e.g. used for the "download.cgi" script on many Apache
> project sites.
> The wagon uploader (at least ssh and ssh-external) unconditionally change the
> permissions of all files to be 664. Which kills the execution bits. Which is
> bad (TM).
--
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: (SCM-387) CvsScmProviderRepository returns wrong CVSROOT for local repository
[
http://jira.codehaus.org/browse/SCM-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139039#action_139039
]
Sergey Zakusov commented on SCM-387:
To reproduce just specify SCM URL like {{scm:cvs|local|c:/cvsroot|test}}
> CvsScmProviderRepository returns wrong CVSROOT for local repository
> ---
>
> Key: SCM-387
> URL: http://jira.codehaus.org/browse/SCM-387
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-cvs
>Affects Versions: 1.1
>Reporter: Sergey Zakusov
>Priority: Blocker
>
> For local repository getCvsRoot() returns just the root path without
> transport type - see getCvsRootForCvsPass:
> {code:title=CvsScmProviderRepository.java|borderStyle=solid}
> /**
> * @return The cvs root
> */
> public String getCvsRoot()
> {
> String root = getCvsRootForCvsPass();
> return removeDefaultPortFromCvsRoot( root );
> }
> private String removeDefaultPortFromCvsRoot( String root )
> {
> if ( root != null && root.indexOf( ":2401" ) > 0 )
> {
> root = root.substring( 0, root.indexOf( ":2401" ) ) + ":" +
> root.substring( root.indexOf( ":2401" ) + 5 );
> }
> return root;
> }
> /**
> * @return The cvs root stored in .cvspass
> */
> public String getCvsRootForCvsPass()
> {
> if ( getUser() != null )
> {
> return getCvsRootWithCorrectUser( getUser() );
> }
> else
> {
> if ( AbstractCvsScmProvider.TRANSPORT_LOCAL.equals(
> getTransport() ) )
> {
> return cvsroot;
> }
> else
> {
> throw new IllegalArgumentException( "Username isn't defined."
> );
> }
> }
> }
> /**
> * @param user user name
> * @return
> */
> private String getCvsRootWithCorrectUser( String user )
> {
> //:transport:rest_of_cvsroot
> int indexOfUsername = getTransport().length() + 2;
> int indexOfAt = cvsroot.indexOf( "@" );
> String userString = user == null ? "" : ":" + user;
> if ( indexOfAt > 0 )
> {
> cvsroot = ":" + getTransport() + userString + cvsroot.substring(
> indexOfAt );
> }
> else
> {
> cvsroot = ":" + getTransport() + userString + "@" +
> cvsroot.substring( indexOfUsername );
> }
> return cvsroot;
> }
> {code}
> And if user was set directly, then the getCvsRootWithCorrectUser logic will
> be wrong.
> So the method should be changed like:
> {code:title=CvsScmProviderRepository.java|borderStyle=solid}
> /**
> * @return The cvs root stored in .cvspass
> */
> public String getCvsRootForCvsPass()
> {
> String result;
> String transport = getTransport();
> if ( AbstractCvsScmProvider.TRANSPORT_LOCAL.equals( transport ) )
> {
> result = ":" + transport + ":" + cvsroot;
> }
> else if ( getUser() != null )
> {
> result = getCvsRootWithCorrectUser( getUser() );
> }
> else
> {
> throw new IllegalArgumentException( "Username isn't defined." );
> }
> return result;
> }
> {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] Commented: (SCM-387) CvsScmProviderRepository returns wrong CVSROOT for local repository
[
http://jira.codehaus.org/browse/SCM-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139037#action_139037
]
Emmanuel Venisse commented on SCM-387:
--
Can you add more informations about the issue?
> CvsScmProviderRepository returns wrong CVSROOT for local repository
> ---
>
> Key: SCM-387
> URL: http://jira.codehaus.org/browse/SCM-387
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-cvs
>Affects Versions: 1.1
>Reporter: Sergey Zakusov
>Priority: Blocker
>
> For local repository getCvsRoot() returns just the root path without
> transport type - see getCvsRootForCvsPass:
> {code:title=CvsScmProviderRepository.java|borderStyle=solid}
> /**
> * @return The cvs root
> */
> public String getCvsRoot()
> {
> String root = getCvsRootForCvsPass();
> return removeDefaultPortFromCvsRoot( root );
> }
> private String removeDefaultPortFromCvsRoot( String root )
> {
> if ( root != null && root.indexOf( ":2401" ) > 0 )
> {
> root = root.substring( 0, root.indexOf( ":2401" ) ) + ":" +
> root.substring( root.indexOf( ":2401" ) + 5 );
> }
> return root;
> }
> /**
> * @return The cvs root stored in .cvspass
> */
> public String getCvsRootForCvsPass()
> {
> if ( getUser() != null )
> {
> return getCvsRootWithCorrectUser( getUser() );
> }
> else
> {
> if ( AbstractCvsScmProvider.TRANSPORT_LOCAL.equals(
> getTransport() ) )
> {
> return cvsroot;
> }
> else
> {
> throw new IllegalArgumentException( "Username isn't defined."
> );
> }
> }
> }
> /**
> * @param user user name
> * @return
> */
> private String getCvsRootWithCorrectUser( String user )
> {
> //:transport:rest_of_cvsroot
> int indexOfUsername = getTransport().length() + 2;
> int indexOfAt = cvsroot.indexOf( "@" );
> String userString = user == null ? "" : ":" + user;
> if ( indexOfAt > 0 )
> {
> cvsroot = ":" + getTransport() + userString + cvsroot.substring(
> indexOfAt );
> }
> else
> {
> cvsroot = ":" + getTransport() + userString + "@" +
> cvsroot.substring( indexOfUsername );
> }
> return cvsroot;
> }
> {code}
> And if user was set directly, then the getCvsRootWithCorrectUser logic will
> be wrong.
> So the method should be changed like:
> {code:title=CvsScmProviderRepository.java|borderStyle=solid}
> /**
> * @return The cvs root stored in .cvspass
> */
> public String getCvsRootForCvsPass()
> {
> String result;
> String transport = getTransport();
> if ( AbstractCvsScmProvider.TRANSPORT_LOCAL.equals( transport ) )
> {
> result = ":" + transport + ":" + cvsroot;
> }
> else if ( getUser() != null )
> {
> result = getCvsRootWithCorrectUser( getUser() );
> }
> else
> {
> throw new IllegalArgumentException( "Username isn't defined." );
> }
> return result;
> }
> {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: (SCM-387) CvsScmProviderRepository returns wrong CVSROOT for local repository
CvsScmProviderRepository returns wrong CVSROOT for local repository
---
Key: SCM-387
URL: http://jira.codehaus.org/browse/SCM-387
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-cvs
Affects Versions: 1.1
Reporter: Sergey Zakusov
Priority: Blocker
For local repository getCvsRoot() returns just the root path without transport
type - see getCvsRootForCvsPass:
{code:title=CvsScmProviderRepository.java|borderStyle=solid}
/**
* @return The cvs root
*/
public String getCvsRoot()
{
String root = getCvsRootForCvsPass();
return removeDefaultPortFromCvsRoot( root );
}
private String removeDefaultPortFromCvsRoot( String root )
{
if ( root != null && root.indexOf( ":2401" ) > 0 )
{
root = root.substring( 0, root.indexOf( ":2401" ) ) + ":" +
root.substring( root.indexOf( ":2401" ) + 5 );
}
return root;
}
/**
* @return The cvs root stored in .cvspass
*/
public String getCvsRootForCvsPass()
{
if ( getUser() != null )
{
return getCvsRootWithCorrectUser( getUser() );
}
else
{
if ( AbstractCvsScmProvider.TRANSPORT_LOCAL.equals( getTransport()
) )
{
return cvsroot;
}
else
{
throw new IllegalArgumentException( "Username isn't defined." );
}
}
}
/**
* @param user user name
* @return
*/
private String getCvsRootWithCorrectUser( String user )
{
//:transport:rest_of_cvsroot
int indexOfUsername = getTransport().length() + 2;
int indexOfAt = cvsroot.indexOf( "@" );
String userString = user == null ? "" : ":" + user;
if ( indexOfAt > 0 )
{
cvsroot = ":" + getTransport() + userString + cvsroot.substring(
indexOfAt );
}
else
{
cvsroot = ":" + getTransport() + userString + "@" +
cvsroot.substring( indexOfUsername );
}
return cvsroot;
}
{code}
And if user was set directly, then the getCvsRootWithCorrectUser logic will be
wrong.
So the method should be changed like:
{code:title=CvsScmProviderRepository.java|borderStyle=solid}
/**
* @return The cvs root stored in .cvspass
*/
public String getCvsRootForCvsPass()
{
String result;
String transport = getTransport();
if ( AbstractCvsScmProvider.TRANSPORT_LOCAL.equals( transport ) )
{
result = ":" + transport + ":" + cvsroot;
}
else if ( getUser() != null )
{
result = getCvsRootWithCorrectUser( getUser() );
}
else
{
throw new IllegalArgumentException( "Username isn't defined." );
}
return result;
}
{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] Commented: (MRELEASE-326) Doens't resolve multiproject dependencies properly
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139028#action_139028 ] Paul Gier commented on MRELEASE-326: Anyone have a sample project that they can upload that reproduces this? > Doens't resolve multiproject dependencies properly > --- > > Key: MRELEASE-326 > URL: http://jira.codehaus.org/browse/MRELEASE-326 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-7 > Environment: Windows, JDK 1.6, Maven 2.08 >Reporter: Kuno Baeriswyl > Attachments: Stacktrace_release-plugin.txt > > > I'd try to make a release:prepare from a multiproject: > A (Multiproject POM) > B (Core Interfaces) > C (Component) > D (Core Impl) > E (Standalone Client) > F (EJB) > G (Client) > A is the parent project and contains the other project from B to G. Following > dependencies are defined : G -> F -> D -> B -> A > However, when it comes to build the Artifact G, the release plugin aborts, > because of missing Artifact F. But it's part of the Multiproject and was just > build before. The release plugin checks the remote repository for an existing > version. Which is non-sense, since I'm actually try to buld it right now... > Since the release plugin has already changed the pom from Snapshot to stable > version labels. I can now do "mvn install" and the missing Artefact will be > installed. And the second run of mvn release:prepare will succeed! Though, I > don't like this workaround and hope this can be fixed. > Thanks > Kuno -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-338) URLs in site.xml banner tags not rendered by site plugin if host not resolved by "nslookup"
URLs in site.xml banner tags not rendered by site plugin if host not resolved by "nslookup" --- Key: MSITE-338 URL: http://jira.codehaus.org/browse/MSITE-338 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-6 Reporter: Paul Spencer Absolute URL's in the banner tags of site.xml are translated to relative URLs by the maven-site-plugin when the hostname is not found by nslookup. In my case the hostname only exists in my hosts files on a the Windows machine running "mvn site". In the example below, the generated URLs for bannerLeft will be absolute and the URL's for bannerRight will be relative. Adding "badhost.apache.org" to the hosts file will not change the outcome. Maven http://maven.apache.org/images/apache-maven-project.png http://maven.apache.org/ Maven http://badhost.apache.org/images/apache-maven-project.png http://badhost.apache.org/ It appears the plugin is validating the hostname. Is their a way of turning this validation off? -- 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: (MENFORCER-37) 'noSnapshots' rule do not check version of parent
[ http://jira.codehaus.org/browse/MENFORCER-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139022#action_139022 ] Nick Stolwijk commented on MENFORCER-37: The "noSnapshots" rules is deprecated and replaced by the "RequireReleaseDeps" rule. I've attached a patch to change this rule to also check for the parent. This is turned on by default, and it is possible to turn it off. Maybe the default should be turned off, but I'll leave that to Brian. > 'noSnapshots' rule do not check version of parent > - > > Key: MENFORCER-37 > URL: http://jira.codehaus.org/browse/MENFORCER-37 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.0-alpha-3 >Reporter: Tomasz Pik >Assignee: Brian Fox > Fix For: 1.0 > > Attachments: RequireReleaseDeps.patch > > > 'noSnapshots' is passing when parent is defined to be SNAPSHOT, IMHO parent > is also a dependency so it should be checked and rule should throw an error > if parent is a SNAPSHOT. -- 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: (MENFORCER-37) 'noSnapshots' rule do not check version of parent
[ http://jira.codehaus.org/browse/MENFORCER-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MENFORCER-37: --- Attachment: RequireReleaseDeps.patch > 'noSnapshots' rule do not check version of parent > - > > Key: MENFORCER-37 > URL: http://jira.codehaus.org/browse/MENFORCER-37 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.0-alpha-3 >Reporter: Tomasz Pik >Assignee: Brian Fox > Fix For: 1.0 > > Attachments: RequireReleaseDeps.patch > > > 'noSnapshots' is passing when parent is defined to be SNAPSHOT, IMHO parent > is also a dependency so it should be checked and rule should throw an error > if parent is a SNAPSHOT. -- 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] Moved: (MANTRUN-94) Ant process not killed if I kill the mvn process
[ http://jira.codehaus.org/browse/MANTRUN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MANT-43 to MANTRUN-94: Key: MANTRUN-94 (was: MANT-43) Project: Maven 2.x Antrun Plugin (was: Maven 2.x Ant Plugin) > Ant process not killed if I kill the mvn process > > > Key: MANTRUN-94 > URL: http://jira.codehaus.org/browse/MANTRUN-94 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug > Environment: Win XP >Reporter: Bruno Duarte > > I'm using the plugin to execute an ant script to call a bat file that, among > other things, will execute a java application (don't ask why!!). > The problem is when I kill the mvn process, the java application (called by > the ant script) isn't killed. Is this a bug or a feature?! Any workaround? -- 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: (MANTRUN-94) Ant process not killed if I kill the mvn process
[ http://jira.codehaus.org/browse/MANTRUN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MANTRUN-94. -- Resolution: Not A Bug Please understand that the issue tracker is not intended to answer questions about Maven's usage, its purpose is to track bugs and feature requests. Please raise your question on the [user mailing list|http://maven.apache.org/mail-lists.html]. > Ant process not killed if I kill the mvn process > > > Key: MANTRUN-94 > URL: http://jira.codehaus.org/browse/MANTRUN-94 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug > Environment: Win XP >Reporter: Bruno Duarte > > I'm using the plugin to execute an ant script to call a bat file that, among > other things, will execute a java application (don't ask why!!). > The problem is when I kill the mvn process, the java application (called by > the ant script) isn't killed. Is this a bug or a feature?! Any workaround? -- 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] Moved: (MANT-43) Ant process not killed if I kill the mvn process
[ http://jira.codehaus.org/browse/MANT-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MPLUGIN-122 to MANT-43: - Component/s: (was: Plugin Plugin) Key: MANT-43 (was: MPLUGIN-122) Project: Maven 2.x Ant Plugin (was: Maven 2.x Plugin Tools) > Ant process not killed if I kill the mvn process > > > Key: MANT-43 > URL: http://jira.codehaus.org/browse/MANT-43 > Project: Maven 2.x Ant Plugin > Issue Type: Bug > Environment: Win XP >Reporter: Bruno Duarte > > I'm using the plugin to execute an ant script to call a bat file that, among > other things, will execute a java application (don't ask why!!). > The problem is when I kill the mvn process, the java application (called by > the ant script) isn't killed. Is this a bug or a feature?! Any workaround? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MENFORCER-29) Enforcer complains about its own version
[
http://jira.codehaus.org/browse/MENFORCER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138999#action_138999
]
nick_stolwijk edited comment on MENFORCER-29 at 6/19/08 6:46 AM:
-
I've tested this with maven 2.0.9 against the current trunk (r669424) and had
to change the jar plugin to version 2.2 (from 2.0.2, which could not be found)
but then the commands "mvn install" and "mvn compile -Penforce" worked
perfectly.
Not reproducible.
was (Author: nick_stolwijk):
I've tested this against the current trunk (r669424) and had to change the
jar plugin to version 2.2 (from 2.0.2, which could not be found) but then the
commands "mvn install" and "mvn compile -Penforce" worked perfectly.
Not reproducible.
> Enforcer complains about its own version
>
>
> Key: MENFORCER-29
> URL: http://jira.codehaus.org/browse/MENFORCER-29
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 1.0
> Environment: GNU/Linux
>Reporter: Hilco Wijbenga
>Assignee: Brian Fox
> Fix For: 1.0
>
> Attachments: pom.xml
>
>
> The attached POM uses the latest version of the Enforcer (revision 611262),
> i.e. 1.0-SNAPSHOT. I've called it 1.0-Local-1, so that's what's defined in
> the POM.
> If I use the Enforcer normally, without a profile, everything works
> beautifully. The attached POM, however, tries to use the Enforcer from a
> profile ("enforce"). If you now try something like "mvn compile -Penforce" it
> complains about its own version not being set, even though it's specified
> *twice*.
--
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-331) assembly descriptor doesn't seem to property substitute properties
assembly descriptor doesn't seem to property substitute properties
--
Key: MASSEMBLY-331
URL: http://jira.codehaus.org/browse/MASSEMBLY-331
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Reporter: Jon Osborn
For the following assembly.xml:
tar.gz
false
src/main/resources/appcontent
${build.environment}/${build.view}/appcontent
**
${build.environment} and ${build.view} are declared as in parent
POM. They retain their 'default' value and cannot be overridden from the
command line using the -D (-Dbuild.environment=UAT) syntax.
The intent of the properties is to build the tar.gz file with different paths
based on the two variables.
--
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: (MDOAP-6) Support more repositories
[ http://jira.codehaus.org/browse/MDOAP-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-6. --- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 1.0 fixed in r669454 > Support more repositories > - > > Key: MDOAP-6 > URL: http://jira.codehaus.org/browse/MDOAP-6 > Project: Maven 2.x DOAP Plugin > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 1.0 > > > Actually, the beta-1 supports only the SVN repository. We should update the > mojo to include more repositories. -- 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: (MDOAP-6) Support more repositories
[ http://jira.codehaus.org/browse/MDOAP-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MDOAP-6: Description: Actually, the beta-1 supports only the SVN repository. We should update the mojo to include more repositories. (was: The beta-1 supports only SVN repository. We should update the mojo to include more repository) Summary: Support more repositories (was: Support more repository) > Support more repositories > - > > Key: MDOAP-6 > URL: http://jira.codehaus.org/browse/MDOAP-6 > Project: Maven 2.x DOAP Plugin > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Vincent Siveton > > Actually, the beta-1 supports only the SVN repository. We should update the > mojo to include more repositories. -- 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: (MPIR-104) Regression in 2.1-SNAPSHOT: SVN is no more recognized
[ http://jira.codehaus.org/browse/MPIR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-104. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.1 fixed in r669449, snapshot deployed > Regression in 2.1-SNAPSHOT: SVN is no more recognized > - > > Key: MPIR-104 > URL: http://jira.codehaus.org/browse/MPIR-104 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: scm >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > It is due to missing dependencies -- 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: (MPIR-104) Regression in 2.1-SNAPSHOT: SVN is no more recognized
Regression in 2.1-SNAPSHOT: SVN is no more recognized - Key: MPIR-104 URL: http://jira.codehaus.org/browse/MPIR-104 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: scm Affects Versions: 2.1 Reporter: Vincent Siveton It is due to missing dependencies -- 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: (MPLUGIN-122) Ant process not killed if I kill the mvn process
Ant process not killed if I kill the mvn process Key: MPLUGIN-122 URL: http://jira.codehaus.org/browse/MPLUGIN-122 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: Plugin Plugin Environment: Win XP Reporter: Bruno Duarte I'm using the plugin to execute an ant script to call a bat file that, among other things, will execute a java application (don't ask why!!). The problem is when I kill the mvn process, the java application (called by the ant script) isn't killed. Is this a bug or a feature?! Any workaround? -- 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: (MENFORCER-29) Enforcer complains about its own version
[
http://jira.codehaus.org/browse/MENFORCER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138999#action_138999
]
Nick Stolwijk commented on MENFORCER-29:
I've tested this against the current trunk (r669424) and had to change the jar
plugin to version 2.2 (from 2.0.2, which could not be found) but then the
commands "mvn install" and "mvn compile -Penforce" worked perfectly.
Not reproducible.
> Enforcer complains about its own version
>
>
> Key: MENFORCER-29
> URL: http://jira.codehaus.org/browse/MENFORCER-29
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 1.0
> Environment: GNU/Linux
>Reporter: Hilco Wijbenga
>Assignee: Brian Fox
> Fix For: 1.0
>
> Attachments: pom.xml
>
>
> The attached POM uses the latest version of the Enforcer (revision 611262),
> i.e. 1.0-SNAPSHOT. I've called it 1.0-Local-1, so that's what's defined in
> the POM.
> If I use the Enforcer normally, without a profile, everything works
> beautifully. The attached POM, however, tries to use the Enforcer from a
> profile ("enforce"). If you now try something like "mvn compile -Penforce" it
> complains about its own version not being set, even though it's specified
> *twice*.
--
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: (MENFORCER-31) Incorrect documentation for writing a custom rule
[
http://jira.codehaus.org/browse/MENFORCER-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138997#action_138997
]
Nick Stolwijk commented on MENFORCER-31:
The documentation on the site is for 1.0-SNAPSHOT, which has changed GroupId /
ArtifactId from version 1.0-alpha-2 to the current SNAPSHOT. So for the current
version (SNAPSHOT) the site is right, but for the current alpha release it is
not right.
Also the method you've mentioned are necessary in current SNAPSHOT.
> Incorrect documentation for writing a custom rule
> -
>
> Key: MENFORCER-31
> URL: http://jira.codehaus.org/browse/MENFORCER-31
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Rule API
>Affects Versions: 1.0-alpha-3
>Reporter: Ben Lidgey
>Assignee: Brian Fox
> Fix For: 1.0
>
>
> The documentation at
> http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html has
> the wrong dependencies and code examples for creating a custom rule.
> It defines
> {code:xml}
>
> org.apache.maven.enforcer
> enforcer-api
> ${api.version}
>
> {code}
> instead of
> {code:xml}
>
> org.apache.maven.shared
> maven-enforcer-rule-api
> 1.0-alpha-2
>
> {code}
> and so the code examples are incorrect because:
> # Incorrect imports:
> #* The imports are for
> #** {{org.apache.maven.enforcer.rule.api.EnforcerRule}}
> #** {{org.apache.maven.enforcer.rule.api.EnforcerRuleException}}
> #** {{org.apache.maven.enforcer.rule.api.EnforcerRuleHelper}}
> #* instead of
> #** {{org.apache.maven.shared.enforcer.rule.api.EnforcerRule}}
> #** {{org.apache.maven.shared.enforcer.rule.api.EnforcerRuleException}}
> #** {{org.apache.maven.shared.enforcer.rule.api.EnforcerRuleHelper}}.
> #* Implementing {{import org.apache.maven.enforcer.rule.api.EnforcerRule}}
> causes the custom plugin invocation to fail with an ArrayStoreException as
> the expected type is {{import
> org.apache.maven.shared.enforcer.rule.api.EnforcerRule}} instead.
> # It shows implementing {{public String getCacheId()}}, {{public boolean
> isCacheable()}}, {{public boolean isResultValid( EnforcerRule arg0 )}} which
> are no longer needed.
--
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-330) LICENSE/NOTICE modification/generation based on included dependencies
[ http://jira.codehaus.org/browse/MASSEMBLY-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138996#action_138996 ] Stefano Bagnara commented on MASSEMBLY-330: --- Daniel, great point! It would be cool if this could be someway be managed automatically by a collaboration between the remote-resources-plugin and the assembly-plugin. I think this would give us an very good out-of-the-box solution! I don't know maven so I don't know if it is easy/feasible for 2 plugins to collaborate for a given result, but this would be cool for sure... Maybe the assembly plugin could invoke the remote-resources-plugin with configurations given by his assembly descriptor? > LICENSE/NOTICE modification/generation based on included dependencies > - > > Key: MASSEMBLY-330 > URL: http://jira.codehaus.org/browse/MASSEMBLY-330 > Project: Maven 2.x Assembly Plugin > Issue Type: New Feature >Affects Versions: 2.2-beta-2 >Reporter: Stefano Bagnara > > I create jar, javadoc-jar and sources-jar using maven jar plugin. > The maven remote resources plugin together with the > apache-jar-resource-bundle allow me to have a good LICENSE/NOTICE file for > that jars. > The problem is that I also have a src\assemble\src.xml and > src\assemble\bin.xml files to create a sources + compile/test/runtime > dependencies (all of them) zip file and a binary + runtime dependencies zip > file. > Assembly plugin make a grea job in allowing me using this for the binary > dependencies: > dependencySets> > > /lib/ > runtime > > > For the src distribution I instead copy files manually not using the > dependencies (because I need them in the same structure I already have), and > this is another issue, but let's fix one issue at a time. > currently I put a LICENSE/NOTICE files in the zips by adding this: > > target/maven-shared-archive-resources/META-INF/ > / > > NOTICE > LICENSE > > > But they are now wrong for a binary distribution including the runtime > dependencies. > It would be cool to have the assembly plugin automatically manage this (I > don't even know how) by altering (or interacting with the remote resources > plugin) to add snippets related to the included dependencies. -- 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-2111) SAT4J bundles ready for inclusion in Maven Central repository
SAT4J bundles ready for inclusion in Maven Central repository - Key: MAVENUPLOAD-2111 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2111 Project: Maven Upload Requests Issue Type: New Feature Reporter: Daniel Le Berre I am the leader of the SAT4J project. SAT4J will be used in the next release of Maven to manage dependencies, in a way similar to Eclipse p2. Here are bundles of SAT4J core and SAT4J pb ready to be consumed by Maven developers (Oleg and Jason). The version is 2.0.1 and not 2.0.0 since I fixed two small issues in that code, that will not affect the current 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
