[jira] Commented: (MJAVADOC-60) option -locale must be first on the command line.
[ http://jira.codehaus.org/browse/MJAVADOC-60?page=comments#action_59846 ] YOKOTA Takehiko commented on MJAVADOC-60: - [MJAVADOC-25] is closed but the issue is still not resolved, so I have cloned the issue entry. > option -locale must be first on the command line. > - > > Key: MJAVADOC-60 > URL: http://jira.codehaus.org/browse/MJAVADOC-60 > Project: Maven 2.x Javadoc Plugin > Type: Bug > Environment: Windows XP > Reporter: YOKOTA Takehiko > Assignee: Brett Porter > Priority: Minor > > > Providing a parameter currently cause a javadoc failure because the > maven-javadoc-plugin put the -locale option after some other options like > -encoding. According the javadoc tool documentation > (http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#locale), > the -locale parameter must be first. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MJAVADOC-60) option -locale must be first on the command line.
option -locale must be first on the command line. - Key: MJAVADOC-60 URL: http://jira.codehaus.org/browse/MJAVADOC-60 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: YOKOTA Takehiko Assigned to: Brett Porter Priority: Minor Providing a parameter currently cause a javadoc failure because the maven-javadoc-plugin put the -locale option after some other options like -encoding. According the javadoc tool documentation (http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#locale), the -locale parameter must be first. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MJAVADOC-25) option -locale must be first on the command line.
[ http://jira.codehaus.org/browse/MJAVADOC-25?page=comments#action_59767 ] YOKOTA Takehiko commented on MJAVADOC-25: - I encountered the same problem, and I've found out the cause. org.apache.maven.plugin.javadoc.JavadocReport adds -locale argument after -classpath option, so the first option of Generated command line arguments is '-classpath' option, not '-locale' option. Could you change the order of these arguments? > javadoc-plugin's committers > option -locale must be first on the command line. > - > > Key: MJAVADOC-25 > URL: http://jira.codehaus.org/browse/MJAVADOC-25 > Project: Maven 2.x Javadoc Plugin > Type: Bug > Environment: Windows XP > Reporter: Martin Desruisseaux > Assignee: Brett Porter > Priority: Minor > > > Providing a parameter currently cause a javadoc failure because the > maven-javadoc-plugin put the -locale option after some other options like > -encoding. According the javadoc tool documentation > (http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#locale), > the -locale parameter must be first. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_54159 ] YOKOTA Takehiko commented on MNGECLIPSE-15: --- You may be right about resources for actual code, but how about resources for testing? For example, assume that each subproject has log4j.properties in src/test/resources folder and those contents are different from others. I have no idea about a way to put those files in a single place. About target build path, even if I set output folder to the same folder as source one, the setting will be deleted after invoking 'Update Source Folder' action. X-< > Output folders are not set correctly by 'Update Sources' action > --- > > Key: MNGECLIPSE-15 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Reporter: YOKOTA Takehiko > Assignee: Eugene Kuleshov > Attachments: patch.txt > > > Although source folders on build path are updated correctly by 'Update > Sources' action, > output folders are not updated at all. > For example, it is expected that output folder for 'src/test/java' and > 'src/test/resources' > is set to 'target/test-classes', but not set. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_54074 ] YOKOTA Takehiko commented on MNGECLIPSE-15: --- In fact, my strongest motivation to separate output folders per subprojects is to suppress Eclipse's warning messages about conflict of resources by copying into single output folder. So it may not be critical issue not to separate output folder, but lots of meaningless warning messages disturb development because they jam other important error messages up. > As a side note, when resources are placed in a separate folder we may use > resource folder as an output folder for Eclipse, so it won't even need to copy > anything. I'm sorry but I could not see what you meant. Could you please explain "use resource folder as an output folder for Eclipse" in detail? > Output folders are not set correctly by 'Update Sources' action > --- > > Key: MNGECLIPSE-15 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Reporter: YOKOTA Takehiko > Assignee: Eugene Kuleshov > Attachments: patch.txt > > > Although source folders on build path are updated correctly by 'Update > Sources' action, > output folders are not updated at all. > For example, it is expected that output folder for 'src/test/java' and > 'src/test/resources' > is set to 'target/test-classes', but not set. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=all ] YOKOTA Takehiko updated MNGECLIPSE-15: -- Attachment: patch.txt > Output folders are not set correctly by 'Update Sources' action > --- > > Key: MNGECLIPSE-15 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Reporter: YOKOTA Takehiko > Assignee: Eugene Kuleshov > Attachments: patch.txt > > > Although source folders on build path are updated correctly by 'Update > Sources' action, > output folders are not updated at all. > For example, it is expected that output folder for 'src/test/java' and > 'src/test/resources' > is set to 'target/test-classes', but not set. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_53966 ] YOKOTA Takehiko commented on MNGECLIPSE-15: --- Sorry, I noticed that the example was wrong. What I meant was I didn't want to gather resources of all *subprojects* into single output folder. As you said, main resource and test resource will gather into the same classpath at certain subproject, but I think that some resources of subproject-A and independent subproject-B's one should not be gathered into single classpath. How about this? So I'd like to separate output folders per subproject, but currently I have no idea for realize this. > Output folders are not set correctly by 'Update Sources' action > --- > > Key: MNGECLIPSE-15 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Reporter: YOKOTA Takehiko > Assignee: Eugene Kuleshov > > > Although source folders on build path are updated correctly by 'Update > Sources' action, > output folders are not updated at all. > For example, it is expected that output folder for 'src/test/java' and > 'src/test/resources' > is set to 'target/test-classes', but not set. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_53909 ] YOKOTA Takehiko commented on MNGECLIPSE-15: --- I understand what you want to say. Output folder may not be shared by Eclipse and others. But what I'd like to say more is an inconvenient behavior that 'Update Source Folders' action completely deletes all custom output folder settings. For instance, src/main/resources/log4j.properties and src/test/resources/log4j.properties (for testing) are conflicted by being copied into single output folder. So, I hope alternative function to specify output folders for main resources and test resources respectively on each subproject. > Output folders are not set correctly by 'Update Sources' action > --- > > Key: MNGECLIPSE-15 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Reporter: YOKOTA Takehiko > Assignee: Eugene Kuleshov > > > Although source folders on build path are updated correctly by 'Update > Sources' action, > output folders are not updated at all. > For example, it is expected that output folder for 'src/test/java' and > 'src/test/resources' > is set to 'target/test-classes', but not set. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action
Output folders are not set correctly by 'Update Sources' action --- Key: MNGECLIPSE-15 URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 Project: Maven 2.x Plug-in for Eclipse Type: Bug Reporter: YOKOTA Takehiko Assigned to: Eugene Kuleshov Although source folders on build path are updated correctly by 'Update Sources' action, output folders are not updated at all. For example, it is expected that output folder for 'src/test/java' and 'src/test/resources' is set to 'target/test-classes', but not set. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1480) archetype-plugin copies sub-packaged source template files into wrong location
archetype-plugin copies sub-packaged source template files into wrong location -- Key: MNG-1480 URL: http://jira.codehaus.org/browse/MNG-1480 Project: Maven 2 Type: Bug Versions: 2.0 Environment: WindowsXP, Sun JDK1.4.2_08, Maven2.0 Reporter: YOKOTA Takehiko When generating project skelton using archetype-plugin and a custom archetype which has sub-packaged source template files, the plugin copies the source template files into wrong location. For example, let a custom archetype have the following source template files: archetype-resources/src/main/java/App.java archetype-resources/src/main/java/impl/AppImpl.java I expect the source files copied as the following: PROJECTTOP/src/main/java/PACKAGE/App.java PROJECTTOP/src/main/java/PACKAGE/impl/AppImpl.java But the actual result is like the following: PROJECTTOP/src/main/java/PACKAGE/App.java PROJECTTOP/src/main/java/impl/PACKAGE/AppImpl.java AFAIK, Maven1.x's genapp plugin behaves like I expect. Can you fix the behavior If possible? -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
