[jira] Commented: (MNG-3139) The skin does not exist: Unable to determine the release version
[ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263551#action_263551 ] Bram commented on MNG-3139: --- Another workaround for now (as the others don't work for me / anymore): Install the downloaded skin as version DEFAULT, so you get: /org/apache/maven/skins/maven-default-skin/DEFAULT/maven-default-skin-DEFAULT.jar > The skin does not exist: Unable to determine the release version > > > Key: MNG-3139 > URL: http://jira.codehaus.org/browse/MNG-3139 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.7 >Reporter: eyal david >Assignee: John Casey > Fix For: 2.0.11, 2.1.0, 3.0-alpha-3 > > Attachments: cached-metadata.patch, mvn_site_debug.zip > > > hi I have problem generating site when im using the command mvn site > it performs all stagegs and when it came to site generation the message is > shown : > The skin does not exist: Unable to determine the release version > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.skins > -DartifactId=maven > -default-skin \ > -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file > org.apache.maven.skins:maven-default-skin:jar:RELEASE > do u have an idea what is the problem ? > p.s the jar is registered in my local repository and in the remote repository > thank u -- 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-3139) The skin does not exist: Unable to determine the release version
[ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263463#action_263463 ] Bram commented on MNG-3139: --- I'm also experiencing the same bug on our Jenkins server (v 1.405) with Maven 2.2.1. Removing LOCAL-REPO/org/apache/maven/skins/* does help for a few days, but not for long > The skin does not exist: Unable to determine the release version > > > Key: MNG-3139 > URL: http://jira.codehaus.org/browse/MNG-3139 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.7 >Reporter: eyal david >Assignee: John Casey > Fix For: 2.0.11, 2.1.0, 3.0-alpha-3 > > Attachments: cached-metadata.patch, mvn_site_debug.zip > > > hi I have problem generating site when im using the command mvn site > it performs all stagegs and when it came to site generation the message is > shown : > The skin does not exist: Unable to determine the release version > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.skins > -DartifactId=maven > -default-skin \ > -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file > org.apache.maven.skins:maven-default-skin:jar:RELEASE > do u have an idea what is the problem ? > p.s the jar is registered in my local repository and in the remote repository > thank u -- 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-511) release:prepare "Error parsing version, cannot determine next version: Unable to parse the version string" when running in batch mode.
[
http://jira.codehaus.org/browse/MRELEASE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252814#action_252814
]
Bram commented on MRELEASE-511:
---
It looks like MapVersionsPhase.getNextVersion() is trying to be a bit too
smart. It tries to parse the current version number when it really shouldn't.
It should first check ReleaseDescriptor's releaseVersions map to see if it
contains a value for the next release. If not, then it should execute the
current flow.
I don't have time to create a patch for this now, and I don't know the release
plugin well enough to say if my above explanation is completely accurate, but
at first glance, I think it's close enough.
> release:prepare "Error parsing version, cannot determine next version: Unable
> to parse the version string" when running in batch mode.
> --
>
> Key: MRELEASE-511
> URL: http://jira.codehaus.org/browse/MRELEASE-511
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-9
> Environment: Win Xp Pro 64bit Java 1.6
>Reporter: David Cloutier
>Priority: Critical
> Attachments: patch_release_version_patterns.txt
>
>
> When I try to run release:prepare in batch mode, I get the error below (can't
> parse version string) even though I supply the version number by argument. If
> I do the same thing with the same versions in interactive mode, it works fine.
> Here is the output:
>
> C:\workspaces\head\MyClient>mvn -B -e -Dresume=false -Dtag=PPX
> -DdevelopmentVersion=MYB_200909-SNAPSHOT -DreleaseVersion=PPX release:prepare
> release:perform
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Unnamed - com.mycie:MyClient:jar:MYB_200909-SNAPSHOT
> [INFO]task-segment: [release:prepare, release:perform] (aggregator-style)
> [INFO]
>
> Downloading:
> http://myrepo.int.mycie.com:8081/artifactory/repo/org/apache/ws/security/wss4j/1.5.3/wss4j-1.5.3.pom
> [INFO] Unable to find resource 'org.apache.ws.security:wss4j:pom:1.5.3' in
> repository libs-releases (http://myrepo.int.mycie.com:8081/artifactory/repo)
> Downloading:
> http://myrepo.int.mycie.com/artifactory/libs-releases-local/org/apache/ws/security/wss4j/1.5.3/wss4j-1.5.3.pom
> [INFO] Unable to find resource 'org.apache.ws.security:wss4j:pom:1.5.3' in
> repository libs-releases-local
> (http://myrepo.int.mycie.com/artifactory/libs-releases-local)
> Downloading:
> http://repo1.maven.org/maven2/org/apache/ws/security/wss4j/1.5.3/wss4j-1.5.3.pom
> [INFO] Unable to find resource 'org.apache.ws.security:wss4j:pom:1.5.3' in
> repository central (http://repo1.maven.org/maven2)
> [INFO] [release:prepare {execution: default-cli}]
> [INFO] Verifying that there are no local modifications...
> [INFO] Executing: cmd.exe /X /C "cvs -z3 -f -t -d
> :pserver:usrbuild@mycvshost:/data/cvs/libcvs_web -n -q update -d"
> [INFO] Working directory: C:\workspaces\head\MyClient
> [INFO] Checking dependencies and plugins for snapshots ...
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error parsing version, cannot determine next version: Unable to parse
> the version string: "MYB_200909-SNAPSHOT"
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error parsing
> version, cannot determine next version: Unable to parse the version string:
> "MYB_200909-SNAPSHOT"
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.
[jira] Commented: (MRELEASE-511) release:prepare "Error parsing version, cannot determine next version: Unable to parse the version string" when running in batch mode.
[
http://jira.codehaus.org/browse/MRELEASE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252808#action_252808
]
Bram commented on MRELEASE-511:
---
Still present in 3.0 indeed. It fails on even the simplest versions, like
Test-1 or Test-1.0
What I don't get it why on earth the plugin tries to parse the version string
in the first place. I provided all required parameters (scm tag, release
version, next version) as command line options.
> release:prepare "Error parsing version, cannot determine next version: Unable
> to parse the version string" when running in batch mode.
> --
>
> Key: MRELEASE-511
> URL: http://jira.codehaus.org/browse/MRELEASE-511
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-9
> Environment: Win Xp Pro 64bit Java 1.6
>Reporter: David Cloutier
>Priority: Critical
> Attachments: patch_release_version_patterns.txt
>
>
> When I try to run release:prepare in batch mode, I get the error below (can't
> parse version string) even though I supply the version number by argument. If
> I do the same thing with the same versions in interactive mode, it works fine.
> Here is the output:
>
> C:\workspaces\head\MyClient>mvn -B -e -Dresume=false -Dtag=PPX
> -DdevelopmentVersion=MYB_200909-SNAPSHOT -DreleaseVersion=PPX release:prepare
> release:perform
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Unnamed - com.mycie:MyClient:jar:MYB_200909-SNAPSHOT
> [INFO]task-segment: [release:prepare, release:perform] (aggregator-style)
> [INFO]
>
> Downloading:
> http://myrepo.int.mycie.com:8081/artifactory/repo/org/apache/ws/security/wss4j/1.5.3/wss4j-1.5.3.pom
> [INFO] Unable to find resource 'org.apache.ws.security:wss4j:pom:1.5.3' in
> repository libs-releases (http://myrepo.int.mycie.com:8081/artifactory/repo)
> Downloading:
> http://myrepo.int.mycie.com/artifactory/libs-releases-local/org/apache/ws/security/wss4j/1.5.3/wss4j-1.5.3.pom
> [INFO] Unable to find resource 'org.apache.ws.security:wss4j:pom:1.5.3' in
> repository libs-releases-local
> (http://myrepo.int.mycie.com/artifactory/libs-releases-local)
> Downloading:
> http://repo1.maven.org/maven2/org/apache/ws/security/wss4j/1.5.3/wss4j-1.5.3.pom
> [INFO] Unable to find resource 'org.apache.ws.security:wss4j:pom:1.5.3' in
> repository central (http://repo1.maven.org/maven2)
> [INFO] [release:prepare {execution: default-cli}]
> [INFO] Verifying that there are no local modifications...
> [INFO] Executing: cmd.exe /X /C "cvs -z3 -f -t -d
> :pserver:usrbuild@mycvshost:/data/cvs/libcvs_web -n -q update -d"
> [INFO] Working directory: C:\workspaces\head\MyClient
> [INFO] Checking dependencies and plugins for snapshots ...
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error parsing version, cannot determine next version: Unable to parse
> the version string: "MYB_200909-SNAPSHOT"
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error parsing
> version, cannot determine next version: Unable to parse the version string:
> "MYB_200909-SNAPSHOT"
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> s
[jira] Commented: (MSITE-521) Since 2010-10-28 around 0:00 GM+1, site-deploy fails on org.apache.maven.surefire:surefire-booter:jar:2.7-SNAPSHOT
[ http://jira.codehaus.org/browse/MSITE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241422#action_241422 ] Bram commented on MSITE-521: If I force the version to 2.6 it runs fine. Could there be something wrong in 2.7-SNAPSHOT? > Since 2010-10-28 around 0:00 GM+1, site-deploy fails on > org.apache.maven.surefire:surefire-booter:jar:2.7-SNAPSHOT > -- > > Key: MSITE-521 > URL: http://jira.codehaus.org/browse/MSITE-521 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: Maven 2.2.1 > Hudson > Artifactory >Reporter: Bram > > I get the following log: > "C:\Program Files\Java\jdk1.6.0_20/bin/java" -Xms256m -Xmx512m > -XX:MaxPermSize=512m -cp > C:\Hudson\plugins\maven-plugin\WEB-INF\lib\maven-agent-1.363.jar;C:\Hudson\tools\Maven\boot\classworlds-1.1.jar > hudson.maven.agent.Main C:\Hudson\tools\Maven "C:\ApacheTomcat\Tomcat > 6.0\webapps\hudson\WEB-INF\lib\remoting-1.363.jar" > C:\Hudson\plugins\maven-plugin\WEB-INF\lib\maven-interceptor-1.363.jar 3598 > C:\Hudson\plugins\maven-plugin\WEB-INF\lib\maven2.1-interceptor-1.2.jar > <===[HUDSON REMOTING CAPACITY]===>channel started > Executing Maven: -B -f C:\Hudson\jobs\site-deploy > notes-interfaces\workspace\notes-interfaces\pom.xml site-deploy > .. > ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) org.apache.maven.surefire:surefire-booter:jar:2.7-SNAPSHOT > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.surefire > -DartifactId=surefire-booter -Dversion=2.7-20101010.190052-17 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.apache.maven.surefire > -DartifactId=surefire-booter -Dversion=2.7-20101010.190052-17 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) > org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.7-SNAPSHOT > 2) org.apache.maven.surefire:surefire-booter:jar:2.7-SNAPSHOT > 2) org.apache.maven.surefire:maven-surefire-common:jar:2.7-SNAPSHOT > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.surefire > -DartifactId=maven-surefire-common -Dversion=2.7-20101010.190052-17 > -Dpackaging=jar -Dfile=/path/to/file -- 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-521) Since 2010-10-28 around 0:00 GM+1, site-deploy fails on org.apache.maven.surefire:surefire-booter:jar:2.7-SNAPSHOT
Since 2010-10-28 around 0:00 GM+1, site-deploy fails on org.apache.maven.surefire:surefire-booter:jar:2.7-SNAPSHOT -- Key: MSITE-521 URL: http://jira.codehaus.org/browse/MSITE-521 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.2 Environment: Maven 2.2.1 Hudson Artifactory Reporter: Bram I get the following log: "C:\Program Files\Java\jdk1.6.0_20/bin/java" -Xms256m -Xmx512m -XX:MaxPermSize=512m -cp C:\Hudson\plugins\maven-plugin\WEB-INF\lib\maven-agent-1.363.jar;C:\Hudson\tools\Maven\boot\classworlds-1.1.jar hudson.maven.agent.Main C:\Hudson\tools\Maven "C:\ApacheTomcat\Tomcat 6.0\webapps\hudson\WEB-INF\lib\remoting-1.363.jar" C:\Hudson\plugins\maven-plugin\WEB-INF\lib\maven-interceptor-1.363.jar 3598 C:\Hudson\plugins\maven-plugin\WEB-INF\lib\maven2.1-interceptor-1.2.jar <===[HUDSON REMOTING CAPACITY]===>channel started Executing Maven: -B -f C:\Hudson\jobs\site-deploy notes-interfaces\workspace\notes-interfaces\pom.xml site-deploy .. ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.maven.surefire:surefire-booter:jar:2.7-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.surefire -DartifactId=surefire-booter -Dversion=2.7-20101010.190052-17 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.surefire -DartifactId=surefire-booter -Dversion=2.7-20101010.190052-17 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.7-SNAPSHOT 2) org.apache.maven.surefire:surefire-booter:jar:2.7-SNAPSHOT 2) org.apache.maven.surefire:maven-surefire-common:jar:2.7-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.surefire -DartifactId=maven-surefire-common -Dversion=2.7-20101010.190052-17 -Dpackaging=jar -Dfile=/path/to/file -- 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-235) The web.xml file included twice into the result war
[ http://jira.codehaus.org/browse/MWAR-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238372#action_238372 ] Bram commented on MWAR-235: --- Build with 092327-2.jar works fine for me. No more duplicate web.xml in the war. > The web.xml file included twice into the result war > --- > > Key: MWAR-235 > URL: http://jira.codehaus.org/browse/MWAR-235 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: WinXP 32bit sp3, sun JDK .6.0.20, maven 2.2.1 >Reporter: Siarhei_Yarkavy >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.2 > > Attachments: asmModule.zip, MWAR-235-test.patch, pom.xml, > screenshot.jpg, WarArchiver.java.patch > > > Please have a look to the attached demo project and screen-shot -- 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-235) The web.xml file included twice into the result war
[ http://jira.codehaus.org/browse/MWAR-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238371#action_238371 ] Bram commented on MWAR-235: --- Hi, the last two builds do not have a jar. I'm trying to force my local mvn to just pick the 092327-2.jar but could the 142853-36.jar also be published? Tnx > The web.xml file included twice into the result war > --- > > Key: MWAR-235 > URL: http://jira.codehaus.org/browse/MWAR-235 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: WinXP 32bit sp3, sun JDK .6.0.20, maven 2.2.1 >Reporter: Siarhei_Yarkavy >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.2 > > Attachments: asmModule.zip, MWAR-235-test.patch, pom.xml, > screenshot.jpg, WarArchiver.java.patch > > > Please have a look to the attached demo project and screen-shot -- 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-235) The web.xml file included twice into the result war
[ http://jira.codehaus.org/browse/MWAR-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238360#action_238360 ] Bram commented on MWAR-235: --- Uhm, which repo should I add to be able to download this? > The web.xml file included twice into the result war > --- > > Key: MWAR-235 > URL: http://jira.codehaus.org/browse/MWAR-235 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: WinXP 32bit sp3, sun JDK .6.0.20, maven 2.2.1 >Reporter: Siarhei_Yarkavy >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.2 > > Attachments: asmModule.zip, MWAR-235-test.patch, pom.xml, > screenshot.jpg, WarArchiver.java.patch > > > Please have a look to the attached demo project and screen-shot -- 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-235) The web.xml file included twice into the result war
[ http://jira.codehaus.org/browse/MWAR-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237644#action_237644 ] Bram commented on MWAR-235: --- Same problems here, when will the fix be released as a new Maven War plugin? > The web.xml file included twice into the result war > --- > > Key: MWAR-235 > URL: http://jira.codehaus.org/browse/MWAR-235 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: WinXP 32bit sp3, sun JDK .6.0.20, maven 2.2.1 >Reporter: Siarhei_Yarkavy >Priority: Critical > Attachments: asmModule.zip, MWAR-235-test.patch, pom.xml, > screenshot.jpg, WarArchiver.java.patch > > > Please have a look to the attached demo project and screen-shot -- 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: (MPMD-86) Using JDK 1.5 causes ParseException: Can't use generics unless running in JDK 1.5 mode!
[ http://jira.codehaus.org/browse/MPMD-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224054#action_224054 ] Bram commented on MPMD-86: -- Same here, I've configured the PMD plugin with: org.apache.maven.plugins maven-pmd-plugin 1.6 /rulesets/basic.xml /rulesets/controversial.xml xml true utf-8 100 And my source builds towards JDK 1.6: org.apache.maven.plugins maven-compiler-plugin 1.6 1.6 With that, I get a lot of warnings on non-1.4 issues like annotations and generics. After configuring the following project property, these warnings disappeared: ... 1.6 > Using JDK 1.5 causes ParseException: Can't use generics unless running in JDK > 1.5 mode! > --- > > Key: MPMD-86 > URL: http://jira.codehaus.org/browse/MPMD-86 > Project: Maven 2.x PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 2.4 > Environment: JAVA 1.5, Maven 2.0.9 >Reporter: Debabrat Panda >Assignee: Benjamin Bentmann > > While running PMD with Maven i am getting parsing error "Error while parsing > ../../../java file" > The errors are > 1. Can't use generics unless running in JDK 1.5 mode! > 2. Can't use static imports when running in JDK 1.4 mode! > Can't use annotations when running in JDK 1.4 mode! > Any help will be appreciated. > Thanks in advance. -- 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: (MWAR-192) Conflict with workspace resoutlion in m2eclipse
[ http://jira.codehaus.org/browse/MWAR-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175394#action_175394 ] Christophe Bram edited comment on MWAR-192 at 5/7/09 8:33 AM: -- IMHO it's not a war-plugin bug, but a m2eclipse bug. I've experienced it using m2eclipse, but not using command-line mvn. As indicated, the real root bug is http://jira.codehaus.org/browse/MNGECLIPSE-1224 was (Author: blackbird): IMHO it's not a war-plugin bug, but a m2eclipse bug. I've experienced it using m2eclipse, but not using command-line mvn. > Conflict with workspace resoutlion in m2eclipse > --- > > Key: MWAR-192 > URL: http://jira.codehaus.org/browse/MWAR-192 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1-alpha-2 > Environment: windows vista >Reporter: Max Powers > > While building my webapp in eclipse using a launch configuration (goals clean > install) and having 'Resolve Workspace Artifacts' checked, the war plugin > cant assemble the war file properly. Note that disabled 'Resolve Workspace > Artifacts' and the war is assembled fine > [DEBUG] Processing: nexus-lvo-plugin-1.3.3-SNAPSHOT.jar > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to copy file for > artifact[org.sonatype.nexus.plugins:nexus-lvo-plugin:jar:1.3.3-SNAPSHOT:compile] > > Embedded error: > C:\Development\Code\nexus-1.3.x\nexus-core-plugins\nexus-lvo-plugin\target\classes > (Access is denied) > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to copy file > for > artifact[org.sonatype.nexus.plugins:nexus-lvo-plugin:jar:1.3.3-SNAPSHOT:compile] > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) > 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: Failed to copy > file for > artifact[org.sonatype.nexus.plugins:nexus-lvo-plugin:jar:1.3.3-SNAPSHOT:compile] > at > org.apache.maven.plugin.war.packaging.ArtifactsPackagingTask.performPackaging(ArtifactsPackagingTask.java:125) > at > org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.handleArtifacts(WarProjectPackagingTask.java:183) > at > org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.performPackaging(WarProjectPackagingTask.java:103) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375) > at > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) > ... 16 more > Caused by: java.io.FileNotFoundException: > C:\Development\Code\nexus-1.3.x\nexus-core-plugins\nexus-lvo-plugin\target\classes > (Access is denied) > at java.io.FileInputStream.open(Native Method) > at java.io.F
[jira] Commented: (MWAR-192) Conflict with workspace resoutlion in m2eclipse
[ http://jira.codehaus.org/browse/MWAR-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175394#action_175394 ] Christophe Bram commented on MWAR-192: -- IMHO it's not a war-plugin bug, but a m2eclipse bug. I've experienced it using m2eclipse, but not using command-line mvn. > Conflict with workspace resoutlion in m2eclipse > --- > > Key: MWAR-192 > URL: http://jira.codehaus.org/browse/MWAR-192 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1-alpha-2 > Environment: windows vista >Reporter: Max Powers > > While building my webapp in eclipse using a launch configuration (goals clean > install) and having 'Resolve Workspace Artifacts' checked, the war plugin > cant assemble the war file properly. Note that disabled 'Resolve Workspace > Artifacts' and the war is assembled fine > [DEBUG] Processing: nexus-lvo-plugin-1.3.3-SNAPSHOT.jar > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to copy file for > artifact[org.sonatype.nexus.plugins:nexus-lvo-plugin:jar:1.3.3-SNAPSHOT:compile] > > Embedded error: > C:\Development\Code\nexus-1.3.x\nexus-core-plugins\nexus-lvo-plugin\target\classes > (Access is denied) > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to copy file > for > artifact[org.sonatype.nexus.plugins:nexus-lvo-plugin:jar:1.3.3-SNAPSHOT:compile] > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) > 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: Failed to copy > file for > artifact[org.sonatype.nexus.plugins:nexus-lvo-plugin:jar:1.3.3-SNAPSHOT:compile] > at > org.apache.maven.plugin.war.packaging.ArtifactsPackagingTask.performPackaging(ArtifactsPackagingTask.java:125) > at > org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.handleArtifacts(WarProjectPackagingTask.java:183) > at > org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.performPackaging(WarProjectPackagingTask.java:103) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375) > at > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) > ... 16 more > Caused by: java.io.FileNotFoundException: > C:\Development\Code\nexus-1.3.x\nexus-core-plugins\nexus-lvo-plugin\target\classes > (Access is denied) > at java.io.FileInputStream.open(Native Method) > at java.io.FileInputStream.(FileInputStream.java:106) > at > org.codehaus.plexus.util.io.FileInputStreamFacade.getInputStream(FileInputStreamFacade.java:78) > at > org.codehaus.plexus.util.FileUtils.copyStreamToFile(FileUtils.java:1057) > at org.codehaus.plexus.util.FileUtils.copyFil
