[jira] Commented: (MJARSIGNER-13) signing in multi-module project fails on windows

2011-04-29 Thread Juan Pablo (JIRA)

[ 
http://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=265235#action_265235
 ] 

Juan Pablo commented on MJARSIGNER-13:
--

Hello all,

I've this problem too and it seems to be (in my case), a problem when defining 
plugin configuration from parent's. POM.
I have a 3 level multimodule project with many modules inside and i choosed to 
configure jarsigner in topmost one (just to avoid duplicate configurations), 
and when using relative paths (or even ${basedir}), it always tries to load the 
keystore from withing current module path:

H:\opt\java\jdk1.6.0_24_x86\jre\..\bin\jarsigner.exe -keystore 
H:\projects\ยทยทยท\java\trunk\client\launcher\workspace\keystore\signing-jar.keystore
 -storepass '*' -keypass '*' 
H:\projects\java\trunk\client\launcher\target\client-launcher-04.08..jar 
'*''
: java.lang.RuntimeException: keystore load: 
H:\projects\java\trunk\client\launcher\workspace\keystore\signing-jar.keystore 
(The system cannot find the path specified)

(seen when running maven with -X option (thanks, btw ;) ;))

Hope this helps ;)

jp


 signing in multi-module project fails on windows
 

 Key: MJARSIGNER-13
 URL: http://jira.codehaus.org/browse/MJARSIGNER-13
 Project: Maven 2.x Jar Signer Plugin
  Issue Type: Bug
Affects Versions: 1.2
 Environment: Windows XP, android sdk 
Reporter: Anna Gadomska
 Attachments: pom.xml


 I got multi-module (6 modules) android project with .pom file and sign 
 profile defined. When I execute with 'sign' profile:
 - in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution 
 (mv goal -rf) it signs another 3 modules and fails again. The reason for 
 failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig 
 failed.
 - in Maven 2.2.1 - it doesn't work at all, even for first module; it returns 
 error code 1
 However, I tried the same .pom - everything works perfectly in Linux 
 (Ubuntu). 
 I was afraid that it might be the issue with spaces, so I hardcoded the paths 
 - the error I got from maven than was:
 {noformat}
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project 
 MyProject: Failed executing 'cmd.exe /X /C 
 C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore 
 C:\tmp\debug.keystore -storepass '*' -keypass '*' xxx.jar 
 '*'debugkey' - exitcode 1 - [Help 1]
 {noformat}
 Attaching pom file which I am using.
 Please help?

-- 
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: (SUREFIRE-653) java.lang.NoClassDefFoundError: org/apache/maven/surefire/booter/SurefireBooter when use toolchains with jdk 1.3

2010-10-20 Thread Gardella Juan Pablo (JIRA)
java.lang.NoClassDefFoundError: org/apache/maven/surefire/booter/SurefireBooter 
when use toolchains with jdk 1.3


 Key: SUREFIRE-653
 URL: http://jira.codehaus.org/browse/SUREFIRE-653
 Project: Maven Surefire
  Issue Type: Bug
  Components: classloading
Affects Versions: 2.5
 Environment: Apache Maven 3.0 (r1004208; 2010-10-04 08:50:56-0300)
Java version: 1.5.0_12
Java home: C:\bea\jdk150_12\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows

With Maven 2 fail too.
Reporter: Gardella Juan Pablo
 Attachments: proyect_to_reproduce.zip

I have a project that I must compile with JDK 1.3. I use toolchains but when I 
try to test fail.

My workaround is use surefire 2.4.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




[jira] Commented: (MNG-2258) Wrong execution order of plugins in same phase

2009-12-31 Thread Pablo (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204741#action_204741
 ] 

Pablo commented on MNG-2258:


@wargre: My workaround is to run JXR twice:
* first time in the pre-site phase (with the POM snippet below), so you're sure 
it's done before the rest.
* second time in the standard reporting section, so you get the XREF links in 
the site menu.

{code}
build
  plugins
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-jxr-plugin/artifactId
  executions
execution
  idjxr-pre-site/id
  phasepre-site/phase
  goals
goaljxr/goal
goaltest-jxr/goal
  /goals
/execution
  /executions
/plugin
  /plugins
/build
{code}

 Wrong execution order of plugins in same phase
 --

 Key: MNG-2258
 URL: http://jira.codehaus.org/browse/MNG-2258
 Project: Maven 2  3
  Issue Type: Bug
Affects Versions: 2.0.4
 Environment: N/A
Reporter: David J. M. Karlsen
Priority: Blocker
 Attachments: mavenTest.zip


 AFAIK plugins should be execute in the same order as they are listed in the 
 POM, when bound to the same phase. This does not happen, the execution order 
 is arbitrary.

-- 
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: (MWAR-187) regression running war packaging with maven 2.1

2009-06-04 Thread Pablo (JIRA)

 [ 
http://jira.codehaus.org/browse/MWAR-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pablo updated MWAR-187:
---

Attachment: MWAR-187-bad_webapp_cache.zip

Please have a look at the project {{MWAR-187-bad_webapp_cache.zip}}.
I'm not really sure how this badly formatted {{webapp-cache.xml}} file (i.e. 
containing a {{modelEncoding}} node) ended up in my target folder, but this was 
the cause of my problem.

Here is how to reproduce the problem with Maven 2.1.0:
* Run {{mvn install}} and the exception described above will occur.
* Run {{mvn clean install}} and the packaging will work fine (because the 
target folder containing the badly formatted file will be deleted)


 regression running war packaging with maven 2.1
 ---

 Key: MWAR-187
 URL: http://jira.codehaus.org/browse/MWAR-187
 Project: Maven 2.x WAR Plugin
  Issue Type: Bug
Affects Versions: 2.1-beta-1
 Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100)
 Java version: 1.6.0_11
 Java home: D:\platina\java\jdk6\jre
 Default locale: fr_FR, platform encoding: Cp1252
 OS name: windows xp version: 5.1 arch: x86 Family: windows
Reporter: nicolas de loof
Priority: Minor
 Fix For: 2.1

 Attachments: MWAR-187-bad_webapp_cache.zip


 Using plugin version 2.1-beta-1, my webapp can't get packaged.
 It can be fixed by downgrading the plugin to 2.0.2
 {code} 
 [DEBUG] Configuring mojo 
 'org.apache.maven.plugins:maven-war-plugin:2.1-beta-1:w
 ar' --
 [DEBUG]   (s) archiveClasses = false
 [DEBUG]   (s) attachClasses = false
 [DEBUG]   (s) cacheFile = D:\...\target\war\work\webapp-cache.xml
 [DEBUG]   (s) classesClassifier = classes
 [DEBUG]   (s) classesDirectory = D:\...\target\classes
 [DEBUG]   (f) escapedBackslashesInFilePath = false
 [DEBUG]   (s) failOnMissingWebXml = true
 [DEBUG]   (f) filteringDeploymentDescriptors = false
 [DEBUG]   (s) outputDirectory = D:\...\target
 [DEBUG]   (s) primaryArtifact = true
 [DEBUG]   (s) project = MavenProject: 
 com.sfr.bios.pdc:bios-pdc-webservices:1.0.
 0-SNAPSHOT @ D:\...\pom.xml
 [DEBUG]   (f) session = org.apache.maven.execution.mavensess...@10f0a0
 [DEBUG]   (s) useCache = true
 [DEBUG]   (s) warName = bios-pdc
 [DEBUG]   (s) warSourceDirectory = D:\...\src\main\webapp
 [DEBUG]   (s) webappDirectory = 
 D:\...\target\bios-pdc-webservices-1.0.0-SNAPSHOT
 [DEBUG]   (s) workDirectory = D:\...\target\war\work
 [DEBUG] -- end configuration --
 [INFO] [war:war]
 [INFO] Packaging webapp
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] modelEncoding : modelEncoding : modelEncoding : modelEncoding
  Debugging information 
 message : modelEncoding : modelEncoding
 cause-exception : 
 com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
 n
 cause-message   : modelEncoding : modelEncoding
 class   : org.apache.maven.plugin.war.util.WebappStructure
 required-type   : org.apache.maven.model.Dependency
 path: 
 /webapp-structure/dependenciesInfo/org.apache.maven.plugin
 .war.util.DependencyInfo/dependency/modelEncoding
 line number : 156
 ---
 [INFO] 
 
 [INFO] Trace
 com.thoughtworks.xstream.converters.ConversionException: modelEncoding : 
 modelEn
 coding : modelEncoding : modelEncoding
  Debugging information 
 message : modelEncoding : modelEncoding
 cause-exception : 
 com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
 n
 cause-message   : modelEncoding : modelEncoding
 class   : org.apache.maven.plugin.war.util.WebappStructure
 required-type   : org.apache.maven.model.Dependency
 path: 
 /webapp-structure/dependenciesInfo/org.apache.maven.plugin
 .war.util.DependencyInfo/dependency/modelEncoding
 line number : 156
 ---
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
 er.java:89)
 at 
 com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(A
 bstractReferenceUnmarshaller.java:63)
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
 arshaller.java:76)
 at 
 com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
 erter.unmarshallField(AbstractReflectionConverter.java:246)
 at 
 com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
 erter.doUnmarshal(AbstractReflectionConverter.java:218)
 at 
 com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
 erter.unmarshal(AbstractReflectionConverter.java:162)
 at 
 

[jira] Issue Comment Edited: (MWAR-187) regression running war packaging with maven 2.1

2009-06-04 Thread Pablo (JIRA)

[ 
http://jira.codehaus.org/browse/MWAR-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=179180#action_179180
 ] 

Pablo edited comment on MWAR-187 at 6/4/09 2:59 AM:


-I tried to downgrade to 2.0.2 but I encountered this issue: MWAR-134-
-Downgrading to 2.0 fixed my problem.-
-(I can provide an example project if needed.)-

  was (Author: pablo):
I tried to downgrade to 2.0.2 but I encountered this issue: MWAR-134
Downgrading to 2.0 fixed my problem.
(I can provide an example project if needed.)
  
 regression running war packaging with maven 2.1
 ---

 Key: MWAR-187
 URL: http://jira.codehaus.org/browse/MWAR-187
 Project: Maven 2.x WAR Plugin
  Issue Type: Bug
Affects Versions: 2.1-beta-1
 Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100)
 Java version: 1.6.0_11
 Java home: D:\platina\java\jdk6\jre
 Default locale: fr_FR, platform encoding: Cp1252
 OS name: windows xp version: 5.1 arch: x86 Family: windows
Reporter: nicolas de loof
Priority: Minor
 Fix For: 2.1

 Attachments: MWAR-187-bad_webapp_cache.zip


 Using plugin version 2.1-beta-1, my webapp can't get packaged.
 It can be fixed by downgrading the plugin to 2.0.2
 {code} 
 [DEBUG] Configuring mojo 
 'org.apache.maven.plugins:maven-war-plugin:2.1-beta-1:w
 ar' --
 [DEBUG]   (s) archiveClasses = false
 [DEBUG]   (s) attachClasses = false
 [DEBUG]   (s) cacheFile = D:\...\target\war\work\webapp-cache.xml
 [DEBUG]   (s) classesClassifier = classes
 [DEBUG]   (s) classesDirectory = D:\...\target\classes
 [DEBUG]   (f) escapedBackslashesInFilePath = false
 [DEBUG]   (s) failOnMissingWebXml = true
 [DEBUG]   (f) filteringDeploymentDescriptors = false
 [DEBUG]   (s) outputDirectory = D:\...\target
 [DEBUG]   (s) primaryArtifact = true
 [DEBUG]   (s) project = MavenProject: 
 com.sfr.bios.pdc:bios-pdc-webservices:1.0.
 0-SNAPSHOT @ D:\...\pom.xml
 [DEBUG]   (f) session = org.apache.maven.execution.mavensess...@10f0a0
 [DEBUG]   (s) useCache = true
 [DEBUG]   (s) warName = bios-pdc
 [DEBUG]   (s) warSourceDirectory = D:\...\src\main\webapp
 [DEBUG]   (s) webappDirectory = 
 D:\...\target\bios-pdc-webservices-1.0.0-SNAPSHOT
 [DEBUG]   (s) workDirectory = D:\...\target\war\work
 [DEBUG] -- end configuration --
 [INFO] [war:war]
 [INFO] Packaging webapp
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] modelEncoding : modelEncoding : modelEncoding : modelEncoding
  Debugging information 
 message : modelEncoding : modelEncoding
 cause-exception : 
 com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
 n
 cause-message   : modelEncoding : modelEncoding
 class   : org.apache.maven.plugin.war.util.WebappStructure
 required-type   : org.apache.maven.model.Dependency
 path: 
 /webapp-structure/dependenciesInfo/org.apache.maven.plugin
 .war.util.DependencyInfo/dependency/modelEncoding
 line number : 156
 ---
 [INFO] 
 
 [INFO] Trace
 com.thoughtworks.xstream.converters.ConversionException: modelEncoding : 
 modelEn
 coding : modelEncoding : modelEncoding
  Debugging information 
 message : modelEncoding : modelEncoding
 cause-exception : 
 com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
 n
 cause-message   : modelEncoding : modelEncoding
 class   : org.apache.maven.plugin.war.util.WebappStructure
 required-type   : org.apache.maven.model.Dependency
 path: 
 /webapp-structure/dependenciesInfo/org.apache.maven.plugin
 .war.util.DependencyInfo/dependency/modelEncoding
 line number : 156
 ---
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
 er.java:89)
 at 
 com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(A
 bstractReferenceUnmarshaller.java:63)
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
 arshaller.java:76)
 at 
 com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
 erter.unmarshallField(AbstractReflectionConverter.java:246)
 at 
 com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
 erter.doUnmarshal(AbstractReflectionConverter.java:218)
 at 
 com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
 erter.unmarshal(AbstractReflectionConverter.java:162)
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
 er.java:82)
 at 
 

[jira] Commented: (MWAR-187) regression running war packaging with maven 2.1

2009-06-04 Thread Pablo (JIRA)

[ 
http://jira.codehaus.org/browse/MWAR-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=179274#action_179274
 ] 

Pablo commented on MWAR-187:


I know what JIRA is, thanks.
My aim was just to provide a test case for this issue (as good JIRA users 
usually do), not to ask for help as a newbie would do in a forum.

Are you sure that NOTHING is the appropriate word?
Forcing the plugin version to 2.1-beta-1, the stack trace is EXACTLY the same 
as the one provided in the description (feel free to do a diff).
{code}
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-war-plugin:2.1-beta-1:w
ar' --
[DEBUG]   (s) archiveClasses = false
[DEBUG]   (s) attachClasses = false
[DEBUG]   (s) cacheFile = D:\Work\Dev\Projects\MWAR-187-bad_webapp_cache\target\
war\work\webapp-cache.xml
[DEBUG]   (s) classesClassifier = classes
[DEBUG]   (s) classesDirectory = D:\Work\Dev\Projects\MWAR-187-bad_webapp_cache\
target\classes
[DEBUG]   (f) escapedBackslashesInFilePath = false
[DEBUG]   (s) failOnMissingWebXml = true
[DEBUG]   (f) filteringDeploymentDescriptors = false
[DEBUG]   (s) outputDirectory = D:\Work\Dev\Projects\MWAR-187-bad_webapp_cache\t
arget
[DEBUG]   (s) primaryArtifact = true
[DEBUG]   (s) project = MavenProject: blabla:blabla:0.1 @ D:\Work\Dev\Projects\M
WAR-187-bad_webapp_cache\pom.xml
[DEBUG]   (f) session = org.apache.maven.execution.mavensess...@1d4d493
[DEBUG]   (s) useCache = true
[DEBUG]   (s) warName = blabla-0.1
[DEBUG]   (s) warSourceDirectory = D:\Work\Dev\Projects\MWAR-187-bad_webapp_cach
e\src\main\webapp
[DEBUG]   (s) webappDirectory = D:\Work\Dev\Projects\MWAR-187-bad_webapp_cache\t
arget\blabla-0.1
[DEBUG]   (s) workDirectory = D:\Work\Dev\Projects\MWAR-187-bad_webapp_cache\tar
get\war\work
[DEBUG] -- end configuration --
[INFO] [war:war]
[INFO] Packaging webapp
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] modelEncoding : modelEncoding : modelEncoding : modelEncoding
 Debugging information 
message : modelEncoding : modelEncoding
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
n
cause-message   : modelEncoding : modelEncoding
class   : org.apache.maven.plugin.war.util.WebappStructure
required-type   : org.apache.maven.model.Dependency
path: /webapp-structure/dependenciesInfo/org.apache.maven.plugin
.war.util.DependencyInfo/dependency/modelEncoding
line number : 23
---
[INFO] 
[DEBUG] Trace
com.thoughtworks.xstream.converters.ConversionException: modelEncoding : modelEn
coding : modelEncoding : modelEncoding
 Debugging information 
message : modelEncoding : modelEncoding
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
n
cause-message   : modelEncoding : modelEncoding
class   : org.apache.maven.plugin.war.util.WebappStructure
required-type   : org.apache.maven.model.Dependency
path: /webapp-structure/dependenciesInfo/org.apache.maven.plugin
.war.util.DependencyInfo/dependency/modelEncoding
line number : 23
---
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
er.java:89)
at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(A
bstractReferenceUnmarshaller.java:63)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
arshaller.java:76)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
erter.unmarshallField(AbstractReflectionConverter.java:246)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
erter.doUnmarshal(AbstractReflectionConverter.java:218)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
erter.unmarshal(AbstractReflectionConverter.java:162)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
er.java:82)
at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(A
bstractReferenceUnmarshaller.java:63)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
arshaller.java:76)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
arshaller.java:60)
at com.thoughtworks.xstream.converters.collections.AbstractCollectionCon
verter.readItem(AbstractCollectionConverter.java:71)
at com.thoughtworks.xstream.converters.collections.CollectionConverter.p
opulateCollection(CollectionConverter.java:68)
at com.thoughtworks.xstream.converters.collections.CollectionConverter.u
nmarshal(CollectionConverter.java:61)
at 

[jira] Commented: (MWAR-187) regression running war packaging with maven 2.1

2009-06-03 Thread Pablo (JIRA)

[ 
http://jira.codehaus.org/browse/MWAR-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=179180#action_179180
 ] 

Pablo commented on MWAR-187:


I tried to downgrade to 2.0.2 but I encountered this issue: MWAR-134
Downgrading to 2.0 fixed my problem.
(I can provide an example project if needed.)

 regression running war packaging with maven 2.1
 ---

 Key: MWAR-187
 URL: http://jira.codehaus.org/browse/MWAR-187
 Project: Maven 2.x WAR Plugin
  Issue Type: Bug
Affects Versions: 2.1-beta-1
 Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100)
 Java version: 1.6.0_11
 Java home: D:\platina\java\jdk6\jre
 Default locale: fr_FR, platform encoding: Cp1252
 OS name: windows xp version: 5.1 arch: x86 Family: windows
Reporter: nicolas de loof
Priority: Minor
 Fix For: 2.1


 Using plugin version 2.1-beta-1, my webapp can't get packaged.
 It can be fixed by downgrading the plugin to 2.0.2
 {code} 
 [DEBUG] Configuring mojo 
 'org.apache.maven.plugins:maven-war-plugin:2.1-beta-1:w
 ar' --
 [DEBUG]   (s) archiveClasses = false
 [DEBUG]   (s) attachClasses = false
 [DEBUG]   (s) cacheFile = D:\...\target\war\work\webapp-cache.xml
 [DEBUG]   (s) classesClassifier = classes
 [DEBUG]   (s) classesDirectory = D:\...\target\classes
 [DEBUG]   (f) escapedBackslashesInFilePath = false
 [DEBUG]   (s) failOnMissingWebXml = true
 [DEBUG]   (f) filteringDeploymentDescriptors = false
 [DEBUG]   (s) outputDirectory = D:\...\target
 [DEBUG]   (s) primaryArtifact = true
 [DEBUG]   (s) project = MavenProject: 
 com.sfr.bios.pdc:bios-pdc-webservices:1.0.
 0-SNAPSHOT @ D:\...\pom.xml
 [DEBUG]   (f) session = org.apache.maven.execution.mavensess...@10f0a0
 [DEBUG]   (s) useCache = true
 [DEBUG]   (s) warName = bios-pdc
 [DEBUG]   (s) warSourceDirectory = D:\...\src\main\webapp
 [DEBUG]   (s) webappDirectory = 
 D:\...\target\bios-pdc-webservices-1.0.0-SNAPSHOT
 [DEBUG]   (s) workDirectory = D:\...\target\war\work
 [DEBUG] -- end configuration --
 [INFO] [war:war]
 [INFO] Packaging webapp
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] modelEncoding : modelEncoding : modelEncoding : modelEncoding
  Debugging information 
 message : modelEncoding : modelEncoding
 cause-exception : 
 com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
 n
 cause-message   : modelEncoding : modelEncoding
 class   : org.apache.maven.plugin.war.util.WebappStructure
 required-type   : org.apache.maven.model.Dependency
 path: 
 /webapp-structure/dependenciesInfo/org.apache.maven.plugin
 .war.util.DependencyInfo/dependency/modelEncoding
 line number : 156
 ---
 [INFO] 
 
 [INFO] Trace
 com.thoughtworks.xstream.converters.ConversionException: modelEncoding : 
 modelEn
 coding : modelEncoding : modelEncoding
  Debugging information 
 message : modelEncoding : modelEncoding
 cause-exception : 
 com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
 n
 cause-message   : modelEncoding : modelEncoding
 class   : org.apache.maven.plugin.war.util.WebappStructure
 required-type   : org.apache.maven.model.Dependency
 path: 
 /webapp-structure/dependenciesInfo/org.apache.maven.plugin
 .war.util.DependencyInfo/dependency/modelEncoding
 line number : 156
 ---
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
 er.java:89)
 at 
 com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(A
 bstractReferenceUnmarshaller.java:63)
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
 arshaller.java:76)
 at 
 com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
 erter.unmarshallField(AbstractReflectionConverter.java:246)
 at 
 com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
 erter.doUnmarshal(AbstractReflectionConverter.java:218)
 at 
 com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
 erter.unmarshal(AbstractReflectionConverter.java:162)
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
 er.java:82)
 at 
 com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(A
 bstractReferenceUnmarshaller.java:63)
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
 arshaller.java:76)
 at 
 com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
 arshaller.java:60)
 at 
 

[jira] Commented: (MRELEASE-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0)

2009-04-01 Thread Pablo (JIRA)

[ 
http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=171732#action_171732
 ] 

Pablo commented on MRELEASE-427:


I have the same problem when executing mvn release:branch.

It would be useful to add the -DremoteTagging argument also when making 
branches. Thank you.



 Add a mojo parameter for using the new remote tagging for svn scm provider 
 (to prevent issue with svn  1.5.0)
 --

 Key: MRELEASE-427
 URL: http://jira.codehaus.org/browse/MRELEASE-427
 Project: Maven 2.x Release Plugin
  Issue Type: Improvement
  Components: scm
Affects Versions: 2.0-beta-8
 Environment: svn version  1.5.0
Reporter: Olivier Lamy
Assignee: Olivier Lamy
Priority: Critical
 Fix For: 2.0-beta-9


 Due to an issue with svn  1.5.0, release plugin doesn't work. The scm (1.2) 
 implements a new remote tagging mechanism as a 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] Created: (MRELEASE-433) Add parameter remoteTagging to release:branch (to prevent issue with svn 1.5.0)

2009-04-01 Thread Pablo (JIRA)
Add parameter remoteTagging to release:branch (to prevent issue with svn  
1.5.0)
-

 Key: MRELEASE-433
 URL: http://jira.codehaus.org/browse/MRELEASE-433
 Project: Maven 2.x Release Plugin
  Issue Type: Bug
  Components: branch
Affects Versions: 2.0-beta-9
 Environment:svn version  1.5.0 
Reporter: Pablo


I have the same problem than [http://jira.codehaus.org/browse/MRELEASE-427] 
when executing mvn release:branch.

It would be useful for me to add the -DremoteTagging argument also when making 
branches.

Thank you.


-- 
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