[jira] Commented: (MIDEA-29) Wrong JDK selected (Maven 2.0.2/IDEA 5.1)
[ http://jira.codehaus.org/browse/MIDEA-29?page=comments#action_60097 ] Wendy Smoak commented on MIDEA-29: -- This seems to be a duplicate of MIDEA-9 Both of these issues are fixed in the trunk. If you build maven-idea-plugin from source, and run 'mvn idea:idea', you'll get the right JDK and language level. (Presumably based on JAVA_HOME and the config for maven-compiler-plugin.) Wrong JDK selected (Maven 2.0.2/IDEA 5.1) - Key: MIDEA-29 URL: http://jira.codehaus.org/browse/MIDEA-29 Project: Maven 2.x Idea Plugin Type: Bug Reporter: Aaron Mulder I used mvn idea:idea on an EAR project with several modules. I'm using JDK 1.4.2_10 (same in Maven and Idea). The generated Idea project shows it's configured for java version 1.4.2_10 [Invalid]. My Idea has 2 JDKs defined: - '1.4 (java version 1.4.2_10)' - '1.5 (java version 1.5.0_06)' -- 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: (MPJALOPY-10) Jalopy removes import statements
Jalopy removes import statements Key: MPJALOPY-10 URL: http://jira.codehaus.org/browse/MPJALOPY-10 Project: maven-jalopy-plugin Type: Bug Versions: 1.4.1 Environment: WinXP, JDK 1.5 Reporter: Wendy Smoak Upgrading to the latest 1.4.1 snapshot results in import statements being removed from code. Steps to reproduce: maven plugin:download -DgroupId=maven -DartifactId=maven-jalopy-plugin -Dversion=1.4.1-SNAPSHOT -Dmaven.repo.remote=http://cvs.apache.org/repository/ mkdir testapp cd testapp maven genapp (answer questions) maven jar(works fine) maven jalopy (output lists 'removing unused import...') maven jar(tests fail-- import statements have been removed) Advice on how to revert to Jalopy 1.0b11 would be appreciated, as the 1.3.1 release fails with a NoClassDefFound error. Relevant mailing list threads: * http://www.nabble.com/Jalopy-plugin-problem-t1098724.html * http://www.nabble.com/-m1-Jalopy-plugin-problems-t1080969.html -- 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: (MJAVADOC-52) locale error
[ http://jira.codehaus.org/browse/MJAVADOC-52?page=all ] Wendy Smoak updated MJAVADOC-52: Attachment: javadoc-locale.diff locale error Key: MJAVADOC-52 URL: http://jira.codehaus.org/browse/MJAVADOC-52 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: windows 2000 maven 2.01 Reporter: pinghe Priority: Critical Attachments: javadoc-locale.diff plugin artifactIdmaven-javadoc-plugin/artifactId configuration localezh_CN.UTF8/locale encodingUTF-8/encoding charsetUTF-8/charset docencodingUTF-8/docencoding /configuration /plugin output: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in JavaDocs report generation. Embedded error: Exit code: 1 - javadoc: option -locale must be first on the command line. -- 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: (MPJAVADOC-70) Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath
[ http://jira.codehaus.org/browse/MPJAVADOC-70?page=comments#action_55923 ] Wendy Smoak commented on MPJAVADOC-70: -- I think this belongs in MJAVADOC (Maven 2.x Javadoc Plugin). If so, the problem with -sourcepath was corrected on January 10th in r367728. Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath - Key: MPJAVADOC-70 URL: http://jira.codehaus.org/browse/MPJAVADOC-70 Project: maven-javadoc-plugin Type: Bug Environment: Windows XP java 1.4.2_05 Reporter: Sebastian Bloch Priority: Blocker [INFO] c:\bea81sp4\jdk142_05\jre\..\bin\javadoc.exe -J-Xmx512m -J-Xms128m @options @files usage: javadoc [options] [packagenames] [sourcefiles] [classnames] [EMAIL PROTECTED] -overview file Read overview documentation from HTML file -public Show only public classes and members -protectedShow protected/public classes and members (default) -package Show package/protected/public classes and members -private Show all classes and members -help Display command line options and exit -doclet class Generate output via alternate doclet -docletpath pathSpecify where to find doclet class files -sourcepath pathlistSpecify where to find source files -classpath pathlist Specify where to find user class files -exclude pkglistSpecify a list of packages to exclude -subpackages subpkglist Specify subpackages to recursively load -breakiteratorCompute 1st sentence with BreakIterator -bootclasspath pathlist Override location of class files loaded by the bootstrap class loader -source release Provide source compatibility with specified release -extdirs dirlistOverride location of installed extensions -verbose Output messages about what Javadoc is doing -locale nameLocale to be used, e.g. en_US or en_US_WIN -encoding name Source file encoding name -Jflag Pass flag directly to the runtime system 1 error [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in JavaDocs report generation. Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Sun Jan 15 20:27:35 CET 2006 [INFO] Final Memory: 3M/7M may be -sourcepath would 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MJAVADOC-50) Allow configuration for whether images and css are copied to destDir
Allow configuration for whether images and css are copied to destDir Key: MJAVADOC-50 URL: http://jira.codehaus.org/browse/MJAVADOC-50 Project: Maven 2.x Javadoc Plugin Type: New Feature Reporter: Wendy Smoak Priority: Minor Not all doclets produce HTML output, so copying the css and images should be configurable. For example, the UMLGraph doclet produces .dot files which can be transformed into images. In addition, the plugin behaves differently when configured in the build and reporting sections: * When run with 'mvn javadoc:javadoc' from the build section, stylesheet.css, the 'images' directory and the 'css' directory are copied to destDir. * When run with 'mvn site' from the reporting section, only stylesheet.css is copied in (and destDir is ignored, see MJAVADOC-47). -- 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-46) Allow -docletpath to be specified as an artifact
Allow -docletpath to be specified as an artifact Key: MJAVADOC-46 URL: http://jira.codehaus.org/browse/MJAVADOC-46 Project: Maven 2.x Javadoc Plugin Type: New Feature Reporter: Wendy Smoak Priority: Minor Attachments: javadoc-docletArtifact.diff As suggested (and written!) by Brett Porter on [EMAIL PROTECTED], in this thread: http://marc.theaimsgroup.com/?l=turbine-maven-devm=113694865002748w=2 Allow the doclet path to be specified as an artifact with docletArtifact. Currently the only option is docletPath which must be the local path to the jar file and is not portable. Comments welcome, I'm happy to rework it if necessary. -- 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-47) Javadoc plugin ignores destDir when used in reporting section
Javadoc plugin ignores destDir when used in reporting section
-
Key: MJAVADOC-47
URL: http://jira.codehaus.org/browse/MJAVADOC-47
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Wendy Smoak
When used in the reporting section of the pom and 'mvn site', output always
goes to target/apidocs, even if you specify an outputDir.
Having outputDir work correctly would by useful with alternate doclets, for
example sending the output of the UMLGraph doclet to target/uml so that it can
be further transformed.
This seems to be the code that's doing it:
if ( !javadocDirectory.getAbsolutePath().equals( getOutputDirectory() )
)
{
// we're in site-embedded report mode, so Doxia has set the
// reportOutputDirectory to the basedir of the site.
// Append 'apidocs'.
javadocDirectory = new File( javadocDirectory, apidocs );
}
--
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: (MEV-251) struts 1.1 pom has servlet-api in compile scope (patch attached)
[ http://jira.codehaus.org/browse/MEV-251?page=all ] Wendy Smoak updated MEV-251: Attachment: struts-1.1.diff struts 1.1 pom has servlet-api in compile scope (patch attached) Key: MEV-251 URL: http://jira.codehaus.org/browse/MEV-251 Project: Maven Evangelism Type: Bug Reporter: Brian Fox Attachments: struts-1.1.diff, struts1.1.patch servlet-api is in the compile scope and causes conflicts when used in a war. Should be: dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.3/version scopeprovided/scope /dependency -- 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: (MEV-251) struts 1.1 pom has servlet-api in compile scope (patch attached)
[ http://jira.codehaus.org/browse/MEV-251?page=comments#action_53017 ] Wendy Smoak commented on MEV-251: - Struts 1.1 should depend on Servlet 2.2. Actually it looks like the version numbers are wrong for several of the dependencies. I'll take a look at it and provide a more complete patch. -- Wendy Smoak (Struts committer) http://www.ibiblio.org/maven2/struts/struts/1.1/struts-1.1.pom http://struts.apache.org/struts-doc-1.1/userGuide/installation.html struts 1.1 pom has servlet-api in compile scope (patch attached) Key: MEV-251 URL: http://jira.codehaus.org/browse/MEV-251 Project: Maven Evangelism Type: Bug Reporter: Brian Fox Attachments: struts1.1.patch servlet-api is in the compile scope and causes conflicts when used in a war. Should be: dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.3/version scopeprovided/scope /dependency -- 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: (MEV-136) MyFaces requires commons-digester and commons-el
[ http://jira.codehaus.org/browse/MEV-136?page=comments#action_52873 ] Wendy Smoak commented on MEV-136: - Both the 1.1.1 and 1.1.0 POMs on ibiblio still have the extra '' after 'provided' for the JSP api artifact. (See Matt's 23/Nov/05 comment.) http://ibiblio.org/maven2/myfaces/myfaces-parent/1.1.1/myfaces-parent-1.1.1.pom http://ibiblio.org/maven2/myfaces/myfaces-parent/1.1.0/myfaces-parent-1.1.0.pom Thanks! MyFaces requires commons-digester and commons-el Key: MEV-136 URL: http://jira.codehaus.org/browse/MEV-136 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Matt Raible Assignee: Edwin Punzalan Here's a revised version: project modelVersion4.0.0/modelVersion groupIdmyfaces/groupId artifactIdmyfaces-all/artifactId version1.1.0/version dependencies dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId version1.5/version /dependency dependency groupIdcommons-el/groupId artifactIdcommons-el/artifactId version1.0/version /dependency /dependencies /project -- 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: (MEV-227) struts 1.2.4 and 1.2.8 dependencies still broken
[ http://jira.codehaus.org/browse/MEV-227?page=comments#action_52144 ] Wendy Smoak commented on MEV-227: - The 1.2.8 pom is in now the Apache repo: http://www.apache.org/dist/java-repository/struts/poms/ Please re-generate the m2 pom and let's see what we get. struts 1.2.4 and 1.2.8 dependencies still broken Key: MEV-227 URL: http://jira.codehaus.org/browse/MEV-227 Project: Maven Evangelism Type: Sub-task Reporter: denis Cabasson Assignee: Carlos Sanchez Looks like the dependencies are still broken -- 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: (MEV-227) struts 1.2.4 and 1.2.8 dependencies still broken
[ http://jira.codehaus.org/browse/MEV-227?page=comments#action_52100 ] Wendy Smoak commented on MEV-227: - The corrected m1 pom (with dependency scope hints added) for 1.2.8 is in the Struts repository: https://svn.apache.org/repos/asf/struts/action/branches/STRUTS_1_2_BRANCH/project.xml It has not yet been uploaded to the Apache repo; I'm hoping the release manager will do that tomorrow. struts 1.2.4 and 1.2.8 dependencies still broken Key: MEV-227 URL: http://jira.codehaus.org/browse/MEV-227 Project: Maven Evangelism Type: Sub-task Reporter: denis Cabasson Assignee: Carlos Sanchez Looks like the dependencies are still broken -- 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: (MEV-227) struts 1.2.4 and 1.2.8 dependencies still broken
[ http://jira.codehaus.org/browse/MEV-227?page=comments#action_51811 ] Wendy Smoak commented on MEV-227: - I think we can fix this from the Apache side (in java-repository). We'll try, anyway. :) If you don't see what you're expecting in ibiblio by Monday, please let me know. struts 1.2.4 and 1.2.8 dependencies still broken Key: MEV-227 URL: http://jira.codehaus.org/browse/MEV-227 Project: Maven Evangelism Type: Sub-task Reporter: denis Cabasson Looks like the dependencies are still broken -- 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: (MEV-230) Struts POM should have Cactus dependencies listed with scopetest/scope
[ http://jira.codehaus.org/browse/MEV-230?page=comments#action_51867 ] Wendy Smoak commented on MEV-230: - See also: http://jira.codehaus.org/browse/MEV-227 Struts POM should have Cactus dependencies listed with scopetest/scope -- Key: MEV-230 URL: http://jira.codehaus.org/browse/MEV-230 Project: Maven Evangelism Type: Improvement Components: Invalid POM Reporter: Matt Raible [DEBUG] struts:struts:jar:1.2.4 (selected for compile) [DEBUG] junit:junit:jar:3.8.1 (not setting scope to: compile; local scope test wins) [WARNING] Artifact junit:junit:jar:3.8.1 retains local scope 'test' overriding broader scope 'compile' given by a dependency. If this is not intended, modify or remove the local scope. [DEBUG] junit:junit:jar:3.8.1 (selected for compile) [DEBUG] oro:oro:jar:2.0.7 (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.0.4 (selected for compile) [DEBUG] commons-collections:commons-collections:jar:2.1 (removed - nearer found: 2.1.1) [DEBUG] commons-collections:commons-collections:jar:2.1 (selected for compile) [DEBUG] xalan:xalan:jar:2.5.1 (selected for compile) [DEBUG] commons-digester:commons-digester:jar:1.5 (selected for compile) [DEBUG] commons-beanutils:commons-beanutils:jar:1.6.1 (setting scope to: compile) [DEBUG] commons-beanutils:commons-beanutils:jar:1.6 (removed - nearer found: 1.6.1) [DEBUG] commons-beanutils:commons-beanutils:jar:1.6 (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.0 (removed - nearer found: 1.0.4) [DEBUG] commons-logging:commons-logging:jar:1.0 (selected for compile) [DEBUG] commons-collections:commons-collections:jar:2.1 (removed - nearer found: 2.1.1) [DEBUG] commons-collections:commons-collections:jar:2.1 (selected for compile) [DEBUG] cactus:cactus:jar:12-1.4.1 (selected for compile) [DEBUG] commons-lang:commons-lang:jar:2.0 (selected for compile) [DEBUG] commons-validator:commons-validator:jar:1.1.3 (selected for compile) [DEBUG] cactus:cactus-ant:jar:1.4.1 (selected for compile) [DEBUG] commons-fileupload:commons-fileupload:jar:1.0 (selected for compile) [DEBUG] commons-beanutils:commons-beanutils:jar:1.6.1 (selected for compile) [DEBUG] antlr:antlr:jar:2.7.2 (selected for compile) [DEBUG] struts:struts-el:jar:1.2.4 (selected for compile) -- 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: (MEV-227) struts 1.2.4 and 1.2.8 dependencies still broken
[ http://jira.codehaus.org/browse/MEV-227?page=comments#action_51871 ] Wendy Smoak commented on MEV-227: - The 1.2.7 pom can be duplicated for 1.2.8. I was going to put it in the Apache repo, but Carlos' comment says 'a maven1 pom' which this is not. I want to do whatever is easiest for the Maven team, just let me know what that is. It looks like the 1.2.4 pom used to be in maven/repository/struts/struts/1.2.4, but was removed. That has caused it to be regenerated from the one in the Apache repo, which is missing some dependency scopes. I've modified struts-1.2.4.pom from ibiblio and have asked Matt Raible to take a look before I attach it here. (See: MEV-230) struts 1.2.4 and 1.2.8 dependencies still broken Key: MEV-227 URL: http://jira.codehaus.org/browse/MEV-227 Project: Maven Evangelism Type: Sub-task Reporter: denis Cabasson Looks like the dependencies are still broken -- 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: (MEV-136) MyFaces requires commons-digester and commons-el
[ http://jira.codehaus.org/browse/MEV-136?page=comments#action_51539 ] Wendy Smoak commented on MEV-136: - http://marc.theaimsgroup.com/?l=myfaces-devm=113259460719576w=2 The portlet jar is only required for compiling. If you are running a MyFaces portlet application then the portlet API will be provided by the portlet container. -- Stan Silvert (MyFaces committer) And from an earlier discussion when I was working on the Commons Chain pom... http://www.nabble.com/Re%3A-chain-dependencies-p1507516.html It *can* work that way. However, the portlet API is not a required part of the J2EE (now Java EE) platform, so you cannot be guaranteed that it will be in your average servlet container. For example, the portlet API jar is not shipped with Tomcat by default. -- Craig McClanahan That's why I went with 'optional,' but I wouldn't argue with 'provided' either. Thanks for your help! MyFaces requires commons-digester and commons-el Key: MEV-136 URL: http://jira.codehaus.org/browse/MEV-136 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Matt Raible Assignee: Edwin Punzalan Here's a revised version: project modelVersion4.0.0/modelVersion groupIdmyfaces/groupId artifactIdmyfaces-all/artifactId version1.1.0/version dependencies dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId version1.5/version /dependency dependency groupIdcommons-el/groupId artifactIdcommons-el/artifactId version1.0/version /dependency /dependencies /project -- 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: (MEV-136) MyFaces requires commons-digester and commons-el
[ http://jira.codehaus.org/browse/MEV-136?page=comments#action_51480 ] Wendy Smoak commented on MEV-136: - Please make the portlet api optional, otherwise it's going to end up in all of our webapps. Thanks! Index: myfaces-parent/1.1.0/myfaces-parent-1.1.0.pom === --- myfaces-parent/1.1.0/myfaces-parent-1.1.0.pom (revision 132) +++ myfaces-parent/1.1.0/myfaces-parent-1.1.0.pom (working copy) @@ -69,6 +69,7 @@ groupIdjavax.portlet/groupId artifactIdportlet-api/artifactId version1.0/version + optionaltrue/optional /dependency dependency groupIdjavax.servlet/groupId MyFaces requires commons-digester and commons-el Key: MEV-136 URL: http://jira.codehaus.org/browse/MEV-136 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Matt Raible Assignee: Edwin Punzalan Here's a revised version: project modelVersion4.0.0/modelVersion groupIdmyfaces/groupId artifactIdmyfaces-all/artifactId version1.1.0/version dependencies dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId version1.5/version /dependency dependency groupIdcommons-el/groupId artifactIdcommons-el/artifactId version1.0/version /dependency /dependencies /project -- 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: (MEV-197) Improvements for Commons Chain pom
[ http://jira.codehaus.org/browse/MEV-197?page=comments#action_51123 ] Wendy Smoak commented on MEV-197: - Actually, I'm just stuck in the middle. My project depends on Struts, which depends on Chain, which is making a mess of WEB-INF/lib. Craig clarified that the Portlet API may not be provided depending on the situation, so the patch as it stands (plus provided for Servlet) should do. Thanks. Improvements for Commons Chain pom -- Key: MEV-197 URL: http://jira.codehaus.org/browse/MEV-197 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Wendy Smoak Assignee: Edwin Punzalan Attachments: chain-1.0-20051115.diff Making some dependencies optional, changing to standard groupId for Sun jars -- 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: (MEV-197) Improvements for Commons Chain pom
[ http://jira.codehaus.org/browse/MEV-197?page=comments#action_50987 ] Wendy Smoak commented on MEV-197: - Quotes from the Commons Chain docs [0]: The context abstraction is designed to isolate command implementations from the environment in which they are run (such as a command that can be used in either a Servlet or Portlet, without being tied directly to the API contracts of either of these environments). ... Convenience base class implementations of these APIs are provided, as well as more specialized (but optional) implementations for the web environment (i.e. servlets and portlets). So Servlet really is optional in this case, not provided. (And MyFaces would only work in a Servlet environment, so it's optional as well.) I did miss 'test' scope for JUnit, though, so I'll attach another patch. Thanks! [0] http://jakarta.apache.org/commons/chain/ Improvements for Commons Chain pom -- Key: MEV-197 URL: http://jira.codehaus.org/browse/MEV-197 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Wendy Smoak Attachments: chain-1.0.diff Making some dependencies optional, changing to standard groupId for Sun jars -- 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: (MEV-197) Improvements for Commons Chain pom
[ http://jira.codehaus.org/browse/MEV-197?page=all ] Wendy Smoak updated MEV-197: Attachment: chain-1.0.diff Replacement diff -- this one also marks JUnit as test scope. Improvements for Commons Chain pom -- Key: MEV-197 URL: http://jira.codehaus.org/browse/MEV-197 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Wendy Smoak Attachments: chain-1.0.diff, chain-1.0.diff Making some dependencies optional, changing to standard groupId for Sun jars -- 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: (MEV-197) Improvements for Commons Chain pom
[ http://jira.codehaus.org/browse/MEV-197?page=all ] Wendy Smoak updated MEV-197: Attachment: chain-1.0-20051115.diff Apparently you can't reuse filenames, trying again. :) Improvements for Commons Chain pom -- Key: MEV-197 URL: http://jira.codehaus.org/browse/MEV-197 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Wendy Smoak Attachments: chain-1.0-20051115.diff, chain-1.0.diff, chain-1.0.diff Making some dependencies optional, changing to standard groupId for Sun jars -- 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: (MEV-197) Improvements for Commons Chain pom
[ http://jira.codehaus.org/browse/MEV-197?page=comments#action_51080 ] Wendy Smoak commented on MEV-197: - Then shouldn't Portlet also be 'provided'? I don't do portlets, but I assume the api is provided by the Portal. (I need to know in order to patch the Chain m1 build file, so it will be converted correctly in the future.) Improvements for Commons Chain pom -- Key: MEV-197 URL: http://jira.codehaus.org/browse/MEV-197 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Wendy Smoak Assignee: Edwin Punzalan Attachments: chain-1.0-20051115.diff Making some dependencies optional, changing to standard groupId for Sun jars -- 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: (MEV-197) Improvements for Commons Chain pom
Improvements for Commons Chain pom -- Key: MEV-197 URL: http://jira.codehaus.org/browse/MEV-197 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Wendy Smoak Making some dependencies optional, changing to standard groupId for Sun jars -- 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: (MEV-197) Improvements for Commons Chain pom
[ http://jira.codehaus.org/browse/MEV-197?page=all ] Wendy Smoak updated MEV-197: Attachment: chain-1.0.diff Improvements for Commons Chain pom -- Key: MEV-197 URL: http://jira.codehaus.org/browse/MEV-197 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Wendy Smoak Attachments: chain-1.0.diff Making some dependencies optional, changing to standard groupId for Sun jars -- 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: (MPPDF-53) Title and dates are incorrect when used with Maven 1.0.2
Title and dates are incorrect when used with Maven 1.0.2 Key: MPPDF-53 URL: http://jira.codehaus.org/browse/MPPDF-53 Project: maven-pdf-plugin Type: Bug Versions: 2.5 Environment: Maven 1.0.2 maven-pdf-plugin-2.5-SNAPSHOT Reporter: Wendy Smoak See http://struts.apache.org/struts-tiles/struts-tiles.pdf for an example of a PDF generated with Maven 1.0.2 and the latest development snapshot of the plugin. The title, current date, and inception date are not correct. From Lukas in http://marc.theaimsgroup.com/?t=11316844423r=1w=2 : Apparently this is another m1.0 - 1.1 compatibility issue. I reproduce it with m1.0.2 and pdf plugin 2.5-SNAPSHOT, but not with any other combination. Somehow the dummy values in project2fo.xslt are not overridden by the default ones. It doesn't even work if I specify the properties explicitly in project.properties. I have no idea why this happens since it works with pdf plugin 2.4 and I don't see what has changed with this respect since. -- 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: (MPPDF-54) Duplicate ids in tables in different documents cause a problem
Duplicate ids in tables in different documents cause a problem -- Key: MPPDF-54 URL: http://jira.codehaus.org/browse/MPPDF-54 Project: maven-pdf-plugin Type: Bug Versions: 2.5 Environment: Maven 1.0.2 maven-pdf-plugin-2.5-SNAPSHOT Reporter: Wendy Smoak 'maven pdf' in struts/current/taglib results in: [java] [ERROR] file:/e:/svn/struts/current/taglib/target/pdf/project.fo:9279 :1971 The id #define_id already exists in this document The offending anchors are coming from Taglib Reference pages generated by the taglib plugin, so this isn't something I can modify in our docs to remove the duplicate. It's happening because both bean:define and nested:define have an 'id' attribute. In http://marc.theaimsgroup.com/?t=11316844423r=1w=2, Lukas replied: I'm afraid you hit another bug here. I was a bit puzzled first because the corresponding id's came from different source documents and identical id's are only a problem within one xdoc. However, in your case the anchors appear in a table, and apparently somewhere in the xslt stylesheet we loose the reference to the current document when processing tables. -- 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: (MNG-1309) Site archetype should not need archetypeVersion parameter
[ http://jira.codehaus.org/browse/MNG-1309?page=comments#action_49161 ] Wendy Smoak commented on MNG-1309: -- This is a duplicate of http://jira.codehaus.org/browse/MNG-1284 Site archetype should not need archetypeVersion parameter - Key: MNG-1309 URL: http://jira.codehaus.org/browse/MNG-1309 Project: Maven 2 Type: Bug Components: maven-archetype-plugin Versions: 2.0 Reporter: Eduardo Rocha Tthe following command, found in maven 2's Getting Started Guide: mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-site The error is: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.archetypes ArtifactId: maven-archetype-site Version: RELEASE Reason: Unable to determine the release version org.apache.maven.archetypes:maven-archetype-site:RELEASE:jar Currently I am using -DarchetypeVersion=1.0-alpha-2 to make it work, but I think this is only because there is no maven-metadata.xml in folder /maven2/org/apache/maven/archetypes/maven-archetype-site at www.ibiblio.org. -- 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: (MPXDOC-159) Allow users to provide 'href' attribute to be used a section or subsection anchor
Allow users to provide 'href' attribute to be used a section or subsection anchor - Key: MPXDOC-159 URL: http://jira.codehaus.org/browse/MPXDOC-159 Project: maven-xdoc-plugin Type: New Feature Reporter: Wendy Smoak Assigned to: Arnaud Heritier Fix For: 1.8 The xdoc plugin uses the 'name' attribute of section and subsection tags as the named anchor for that section. If two sections have the same name, then, you get duplicate anchors. In addition, depending on the text of the section name, the anchors are often very long with many underscores. I would like to see something like: section name=Some Long Description href=desc be allowed. The 'href' attribute can be optional-- if it does not exist, then the section name can be used as the anchor, as usual. If it is present, then the contents of the href attribute should be used instead. This has worked well for the Struts website in the past-- I'm currently converting it over to the Jakarta/Anakia format, and really miss the ability to pick the anchor name that we had in our custom stylesheet. This will also allow duplicate section names _without_ creating duplicate anchors. Duplicate anchors (and so, duplicate ids for FOP) are causing a problem with the Maven PDF Plugin. See: http://jira.codehaus.org/browse/MPPDF-40 -- 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: (MPPDF-40) Can't use 2 subsections with the same name
[ http://jira.codehaus.org/browse/MPPDF-40?page=comments#action_44823 ] Wendy Smoak commented on MPPDF-40: -- I agree that this needs to be fixed in xdoc first. I didn't see that anyone had yet reported it, so I opened a feature request to allow section name=Some Long Description href=desc to allow users to pick the anchor name they want. See: http://jira.codehaus.org/browse/MPXDOC-159 Can't use 2 subsections with the same name -- Key: MPPDF-40 URL: http://jira.codehaus.org/browse/MPPDF-40 Project: maven-pdf-plugin Type: Bug Versions: 2.3 Reporter: Arnaud Heritier Assignee: Arnaud Heritier Priority: Critical If 2 subsections have the same name the pdf generation fails because they have the same id. For exemple : section name=Section 1 subsection name=SubSection /subsection /section section name=Section2 subsection name=SubSection /subsection /section -- 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]
