[jira] Commented: (MEAR-114) Properties in task not taken into consideration when defining an execution id for an auto generating application.xml
[
http://jira.codehaus.org/browse/MEAR-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195084#action_195084
]
Stephane Nicoll commented on MEAR-114:
--
uh? What is this test tag?
Attach a test project that reproduces your problem.
> Properties in task not taken into consideration when defining an
> execution id for an auto generating application.xml
> -
>
> Key: MEAR-114
> URL: http://jira.codehaus.org/browse/MEAR-114
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.3.2
> Environment: Windows XP, M2Eclipse, Eclipse Galileo
>Reporter: Anthony BOUQUET
>
> {code:xml}
>
>
>
>
>
>
> com.logic.silogisme.pidi
>
> TransfertOT-WAR
>
> my-custom-context-root
>
>
>
>
>
> {code}
> But this doesn't work (it produce an application.xml with default contextRoot)
> {code:xml}
>
>execution-1
>
>
>
>
> com.logic.silogisme.pidi
>
> TransfertOT-WAR
>
> my-custom-context-root
>
>
>
>
> {code}
> This is problematic if we want to use multiple executions .
--
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-505) Linux Synergy client fails to execute scm:update command
Linux Synergy client fails to execute scm:update command Key: SCM-505 URL: http://jira.codehaus.org/browse/SCM-505 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-synergy Affects Versions: 1.2 Environment: Redhat Linux 5 CM/Synergy 7.0 Apache Maven 2.1.0 (r755702; 2009-03-19 00:40:27+0530) Java version: 1.6.0_13 Reporter: Subir S Priority: Blocker The linux synergy client using remote client option does not work when using scm:update goal. Error is "ccm start -nogui -m -q -n user -pw password" cannot find the appropriate database '/cm/dbs/testdb/db' On command line if '-rc' option is used along with ccm start then everything works. Is there something additional to be done to make scm:update goal understand that remote client is in use? If there are some pointers, then i would like to help and send a patch or test it -- 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: (MWAR-168) "Dependency Has Changed" Incorrectly Reported
[
http://jira.codehaus.org/browse/MWAR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195116#action_195116
]
Stevo Slavic commented on MWAR-168:
---
This seems to be fixed in current 2.1-beta-1. To use it one should specify the
version in project's plugin settings:
{code}
...
...
...
org.apache.maven.plugins
maven-war-plugin
2.1-beta-1
...
...
...
{code}
> "Dependency Has Changed" Incorrectly Reported
> -
>
> Key: MWAR-168
> URL: http://jira.codehaus.org/browse/MWAR-168
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-2
>Reporter: gotama
>Assignee: Stephane Nicoll
>
> In maven-war-plugin 2.1-alpha-2, execute the following on a war project:
> mvn clean;
> mvn install;
> mvn install;
> The 3rd command incorrectly lists messages for each dependency as follows:
> [INFO] Dependency[Dependency {groupId=com.mycompany, artifactId=myartifact,
> version=8.6.1, type=jar}]
> has changed (was Dependency {groupId=com.mycompany, artifactId=myartifact,
> version=8.6.1, type=jar}).
> The first time that mvn install is run, dependencies are added to:
> target\myapp-war-1.1-SNAPSHOT\WEB-INF\lib
> The second invocation of mvn install appears to fail in comparing the
> existing jars in the above path with what is in the repository. The message
> states the dependencies have changed when in fact they have not.
> This problem does not exist in maven-war-plugin 2.0.2.
--
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
