Re: archetype:create brokes encoding
Alexandre Poitras napisał(a): A lot of people have complained about it, myself included so your best beat would to search in the archives. From what I remember, I think the problem is Velocity is not set to use UTF-8. Also check out your pom files are encoded using UTF-8 but I think you have already done it. I've found it. It is a known bug. http://jira.codehaus.org/browse/ARCHETYPE-19 -- Michał Steiner -- Nie przychodz! Nie przyjezdzaj! Nie dzwon! Zamow ogloszenie drobne do "Gazety Wyborczej" przez internet wchodzac na http://www.aaaby.pl/wyborcza i wygraj nawet 10.000 zl! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Generating site - outputEncoding=utf-8 doesn't work with menu and links names
My pom.xml: (...) org.apache.maven.plugins maven-site-plugin UTF-8 (...) Site's charset is ok: and content from xdoc is proper UTF-8, but menu name, menu items names and links names have broken encoding. I have in site.xml I am doing something wrong or it is a bug ? maven-site-plugin 2.0-beta-4 maven 2.0.4 -- Michael Steiner -- Nie przychodz! Nie przyjezdzaj! Nie dzwon! Zamow ogloszenie drobne do "Gazety Wyborczej" przez internet wchodzac na http://www.aaaby.pl/wyborcza i wygraj nawet 10.000 zl! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
archetype:create brokes encoding
I have created my archetype with files encoded in UTF-8. archetype:create creates project but polish chars are broken (for example: should be ż but is ż). Files in archetype's jar are OK. Where is the problem ? Fedora Core (system encoding UTF-8), Maven version: 2.0.4 org.apache.maven:maven-archetype::1.0-alpha-3 -- Michał Steiner -- Juz 22 i 23 kwietnia castingi miedzynarodowego Konkursu modelek Elite Model Look. Wiecej informacji na stronie http://www.gazeta.pl/elitemodellook - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 xdoclet jsptaglib How?
Allison, Bob napisał(a): I am not sure what the problem is, but it is definitely an XDoclet problem, not a Maven problem. You might get better answers on an XDoclet forum. YES! It was not Maven problem! My tag classes extend Struts BaseHandlerTag class. I changed it to TagSupport and xdoclet generated correct tld file. It is strange but it looks like xdoclet silently ignores classes that don't extends TagSupport directly (BaseHandlerTag also extends TagSupport). Thanks for your help. -- Michał Steiner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 xdoclet jsptaglib How?
Allison, Bob napisał(a): I am not sure what the problem is, but it is definitely an XDoclet problem, not a Maven problem. You might get better answers on an XDoclet forum. I am not sure. xdoclet-maven-plugin is based on antrun plugin. Children of element tasks in configuration are ant task. I have copied them from my ant script. Before I moved to maven I had used this script and it worked fine. From other hand I use similiar configuration to generate ejb descriptors and it works... It looks like xdoclet don't find java files. Does anyone know how to make xdoclet to print which files it scans for tags ? -- Michał Steiner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 xdoclet jsptaglib How?
Grégory Joseph napisał(a): Hi, I could only advise to try out xdoclet2 and its fresh maven2 plugin ;-) See http://xdoclet.codehaus.org/Maven2+Plugin for some incomplete info. I'll be glad to hear your comments. Can't update the docs right now though, our confluence seems to be having a hard time. I have downloaded http://dist.codehaus.org/xdoclet/maven2-xdoclet2-plugin/2.0.5-SNAPSHOT/ (newest version) I have added configuration from http://xdoclet.codehaus.org/Maven2+Plugin with one exception I've changed version xdoclet-plugin-web from 1.0.3-SNAPSHOT to 1.0.3 And I get this message: + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building Web Utils [INFO]task-segment: [package] [INFO] - this realm = app0.child-container[xdoclet:maven2-xdoclet2-plugin] urls[0] = file:/home/msteiner/.m2/repository/xdoclet/maven2-xdoclet2-plugin/2.0.5-SNAPSHOT/maven2-xdoclet2-plugin-2.0.5-SNAPSHOT.jar urls[1] = file:/home/msteiner/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar urls[2] = file:/home/msteiner/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar urls[3] = file:/home/msteiner/.m2/repository/xdoclet-plugins/xdoclet-plugin-qtags/1.0.3/xdoclet-plugin-qtags-1.0.3.jar urls[4] = file:/home/msteiner/.m2/repository/xdoclet-plugins/xdoclet-plugin-web/1.0.3/xdoclet-plugin-web-1.0.3.jar Number of imports: 0 this realm = plexus.core.maven urls[0] = file:/opt/maven/lib/maven-artifact-manager-2.0.2.jar urls[1] = file:/opt/maven/lib/wagon-file-1.0-alpha-6-SNAPSHOT.jar urls[2] = file:/opt/maven/lib/maven-plugin-parameter-documenter-2.0.2.jar urls[3] = file:/opt/maven/lib/maven-project-2.0.2.jar urls[4] = file:/opt/maven/lib/maven-reporting-api-2.0.2.jar urls[5] = file:/opt/maven/lib/maven-plugin-descriptor-2.0.2.jar urls[6] = file:/opt/maven/lib/doxia-sink-api-1.0-alpha-7.jar urls[7] = file:/opt/maven/lib/jsch-0.1.24.jar urls[8] = file:/opt/maven/lib/maven-model-2.0.2.jar urls[9] = file:/opt/maven/lib/wagon-ssh-external-1.0-alpha-6.jar urls[10] = file:/opt/maven/lib/maven-plugin-api-2.0.2.jar urls[11] = file:/opt/maven/lib/maven-core-2.0.2.jar urls[12] = file:/opt/maven/lib/wagon-ssh-1.0-alpha-6.jar urls[13] = file:/opt/maven/lib/maven-repository-metadata-2.0.2.jar urls[14] = file:/opt/maven/lib/maven-settings-2.0.2.jar urls[15] = file:/opt/maven/lib/wagon-provider-api-1.0-alpha-6.jar urls[16] = file:/opt/maven/lib/maven-error-diagnostics-2.0.2.jar urls[17] = file:/opt/maven/lib/maven-core-2.0.2-javadoc.jar urls[18] = file:/opt/maven/lib/maven-profile-2.0.2.jar urls[19] = file:/opt/maven/lib/wagon-http-lightweight-1.0-alpha-6.jar urls[20] = file:/opt/maven/lib/maven-artifact-2.0.2.jar urls[21] = file:/opt/maven/lib/maven-plugin-registry-2.0.2.jar urls[22] = file:/opt/maven/lib/maven-monitor-2.0.2.jar urls[23] = file:/opt/maven/lib/commons-cli-1.0.jar urls[24] = file:/opt/maven/lib/plexus-interactivity-api-1.0-alpha-4.jar urls[25] = file:/home/msteiner/.m2/repository/commons-net/commons-net/1.1.0/commons-net-1.1.0.jar urls[26] = file:/home/msteiner/.m2/repository/oro/oro/2.0.7/oro-2.0.7.jar urls[27] = file:/home/msteiner/.m2/repository/org/apache/maven/wagon/wagon-ftp/1.0-alpha-5/wagon-ftp-1.0-alpha-5.jar Number of imports: 0 this realm = plexus.core urls[0] = file:/opt/maven/core/plexus-container-default-1.0-alpha-9.jar urls[1] = file:/opt/maven/core/plexus-utils-1.1.jar Number of imports: 0 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'xdoclet:maven2-xdoclet2-plugin:2.0.5-SNAPSHOT:xdoclet': Unable to find the mojo 'xdoclet:maven2-xdoclet2-plugin:2.0.5-SNAPSHOT:xdoclet' in the plugin 'xdoclet:maven2-xdoclet2-plugin' org/nanocontainer/integrationkit/ContainerComposer [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'xdoclet:maven2-xdoclet2-plugin:2.0.5-SNAPSHOT:xdoclet': Unable to find the mojo 'xdoclet:maven2-xdoclet2-plugin:2.0.5-SNAPSHOT:xdoclet' in the plugin 'xdoclet:maven2-xdoclet2-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
Maven2 xdoclet jsptaglib How?
I am trying to generate tld files with xdoclet plugin , but I get tld
file only with name and version but without definitions.
I have got three java files with jsp tags.
Problem exists in maven 2.0, 2.0.1, 2.0.2
My pom.xml:
org.codehaus.mojo
xdoclet-maven-plugin
generate-resources
xdoclet
dir="${project.build.directory}/generated-resources/MATA-INF"/>
destdir="${project.build.directory}/generated-resources/MATA-INF"
excludedtags="" verbose="true" force="true"
addedTags="">
shortname="jsp-utils" filename="jsp-utils.tld" />
Generated jsp-utils.tld file :
1.1//EN" "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd";>
1.2
1.1
jsp-utils
Maven messages:
[DEBUG] Configuring mojo
'org.codehaus.mojo:xdoclet-maven-plugin:1.0-alpha-2:xdoclet' -->
[DEBUG] (f) classRealm = [EMAIL PROTECTED]
[DEBUG] (f) generatedSourcesDirectory =
/home/mist/workspace/web_utils/target/generated-sources/xdoclet
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) sourceDirectory = /home/mist/workspace/web_utils/src/main/java
[DEBUG] (f) tasks =
[DEBUG] -- end configuration --
[INFO] [xdoclet:xdoclet {execution: default}]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
[DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
[mkdir] Created dir:
/home/mist/workspace/web_utils/target/generated-resources/MATA-INF
2006-01-18 11:27:30 xdoclet.XDocletMain start
INFO: Running
Generating jsp-utils.tld.
[INFO] Executed tasks
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 7 seconds
[INFO] Finished at: Wed Jan 18 11:27:30 CET 2006
[INFO] Final Memory: 4M/8M
[INFO]
--
Michał Steiner
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: With maven 2.0.2 site:deploy doesn't work
Scokart Gilles napisał(a): Did you have write access on /home/mist/public_html/myApp/ ? Yes. If I use maven 2.0.1 it works perfect If yes, try to run maven with the option -X -e. Output of mvn -X -e clean site site:deploy : (...) [DEBUG] maven-site-plugin: resolved to version 2.0-beta-4 from repository central (...) wagon-file: resolved to version 1.0-alpha-6 from repository central (...) [INFO] [site:deploy] file:///home/mist/public_html/myApp/ - Session: Opened file:///home/mist/public_html/myApp/ - Session: Disconnecting file:///home/mist/public_html/myApp/ - Session: Disconnected [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error uploading site Embedded error: Could not make directory '/home/mist/public_html/myApp/.'. [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:324) 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:142) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531) ... 16 more Caused by: org.apache.maven.wagon.TransferFailedException: Could not make directory '/home/mist/public_html/myApp/.'. at org.apache.maven.wagon.providers.file.FileWagon.putDirectory(FileWagon.java:113) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:134) ... 18 more (...) This '.' at the end of '/home/mist/public_html/myApp/.' is strange. mkdir /home/mist/public_html/myApp - works but mkdir /home/mist/public_html/myApp/. - doesn't work -- Michał Steiner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
With maven 2.0.2 site:deploy doesn't work
error message: (...) [INFO] [site:deploy] file:///home/mist/public_html/myApp - Session: Opened file:///home/mist/public_html/myApp - Session: Disconnecting file:///home/mist/public_html/myApp - Session: Disconnected [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error uploading site Embedded error: Could not make directory '/home/mist/public_html/myApp/.'. My pom.xml: (...) website file:///home/mist/public_html/myApp/ (...) With maven 2.0.1 works fine. It is a bug ? -- Michał Steiner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to dealing with chinese characters in the site.xml file of maven 2 site plugin?
HezhiQiang napisał(a): I am using a site.xml file for project doc site layout,there is some chinese character,utf-8 encode for site.xml,but that generated html files can not dispaly chinese characters correctly. why? anybody can help me! Try add this to pom.xml. (...) org.apache.maven.plugins maven-site-plugin UTF-8 (...) -- Michał Steiner 0880 346 436 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
