[
https://jira.codehaus.org/browse/MGWT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275787#comment-275787
]
jieryn commented on MGWT-305:
-----------------------------
I have been testing this for a while now.. Run your build with -X and then
gwt-maven-plugin will give you the full command line issued. If you run this
manually, you will see that GWT itself is not handling the directory properly.
File a bug upstream please, you may want to reference
http://code.google.com/p/google-web-toolkit/issues/detail?id=1660 which was
fixed, but they regressed somewhere.
In the interim, it's probably a bad idea to have non-standard path names
regardless of whether the tooling /ought/ to support it. :-) Change your path
to bypass.
Please post the upstream ticket # here, then close. Thanks!
> Resources cannot be resolved when using special characters in directory name
> ----------------------------------------------------------------------------
>
> Key: MGWT-305
> URL: https://jira.codehaus.org/browse/MGWT-305
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.2.0, 2.3.0, 2.3.0-1
> Environment: CentOS 5.6 64bit
> Tomcat 7
> Jenkins 1.423
> Maven 3.0.3
> java version "1.6.0_25"
> Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
> Reporter: Croydon
> Priority: Minor
>
> If my project is within a directory that contains a special character such as
> a "+", the build fails during the i18n goal.
> {noformat}
> <===[JENKINS REMOTING CAPACITY]===>channel started
> Executing Maven: -B -f
> /home/jenkins_home/jobs/AdaptivBuildTomcat3.0+/workspace/3.0/pom.xml clean
> package -Ptomcat7x,deploy,env-test
> [INFO] Scanning for projects...
> .............
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Analytics 3.0.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ Analytics ---
> [TASKS] Scanning folder
> '/home/jenkins_home/jobs/AdaptivBuildTomcat3.0+/workspace/3.0/Analytics/src/main/java'
> for tasks ...
> [TASKS] Found 4.
> [TASKS] Scanning folder
> '/home/jenkins_home/jobs/AdaptivBuildTomcat3.0+/workspace/3.0/Analytics/src/test/java'
> for tasks ...
> [TASKS] Found 0.
> [TASKS] Scanning folder
> '/home/jenkins_home/jobs/AdaptivBuildTomcat3.0+/workspace/3.0/Analytics/src/main/resources'
> for tasks ...
> [TASKS] Found 0.
> [TASKS] Scanning folder
> '/home/jenkins_home/jobs/AdaptivBuildTomcat3.0+/workspace/3.0/Analytics/src/test/resources'
> for tasks ...
> [TASKS] Found 0.
> [TASKS] Using set difference to compute new warnings
> [TASKS] Not changing build status, since no threshold has been exceeded
> [INFO]
> [INFO] --- gwt-maven-plugin:2.2.0:i18n (default) @ Analytics ---
> [ERROR] Error: Properties file not found:
> /home/jenkins_home/jobs/AdaptivBuildTomcat3.0/workspace/3.0/Analytics/src/main/resources/com/ivstel/af/client/Messages.properties
> [ERROR] Google Web Toolkit 2.2.0
> [ERROR] I18NSync [-out fileName] [-createConstantsWithLookup]
> [-createMessages] name of the Constants/Messages interface to create
> [ERROR]
> [ERROR] where
> [ERROR] -out Java source
> directory, defaults to the resource's class path.
> [ERROR] -createConstantsWithLookup Create scripts
> for a ConstantsWithLookup interface rather than a Constants one
> [ERROR] -createMessages Create scripts
> for a Messages interface rather than a Constants one
> [ERROR] and
> [ERROR] name of the Constants/Messages interface to create Identifies the
> Constants/Messages class to be created. For example
> com.google.sample.i18n.client.Colors
> mojoFailed org.codehaus.mojo:gwt-maven-plugin:2.2.0(default)
> [TASKS] Skipping maven reporter: there is already a result available.
> projectFailed com.ivstel.analytics:Analytics:3.0.0.0
> [JENKINS] Archiving /home/jenkins_home/jobs/Adaptiv Build Tomcat
> 3.0+/workspace/3.0/Analytics/pom.xml to
> /home/jenkins_home/jobs/AdaptivBuildTomcat
> 3.0+/modules/com.ivstel.analytics$Analytics/builds/2011-07-28_02-01-17/archive/com.ivstel.analytics/Analytics/3.0.0.0/Analytics-3.0.0.0.pom
> sessionEnded
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Adaptiv ........................................... SUCCESS [1.975s]
> [INFO] af-olap ........................................... SUCCESS [2:26.229s]
> [INFO] cas ............................................... SUCCESS [2:07.066s]
> [INFO] JAdaptiv .......................................... SUCCESS [2:53.839s]
> [INFO] Analytics ......................................... FAILURE [4.674s]
> [INFO]
> ------------------------------------------------------------------------
> {noformat}
> It resolves
> /home/jenkins_home/jobs/AdaptivBuildTomcat3.0{color:red}+{color}/... to
> */home/jenkins_home/jobs/AdaptivBuildTomcat3.0/...* at this point
> {color:red}[ERROR] Error: Properties file not found:
> /home/jenkins_home/jobs/AdaptivBuildTomcat3.0/workspace/3.0/Analytics/src/main/resources/com/ivstel/af/client/Messages.properties{color}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
