[jira] Created: (MINSTALL-23) Issue tracking URL points to maven 2 jira.
Issue tracking URL points to maven 2 jira. -- Key: MINSTALL-23 URL: http://jira.codehaus.org/browse/MINSTALL-23 Project: Maven 2.x Install Plugin Type: Bug Reporter: Shinobu Kawai Priority: Trivial http://maven.apache.org/plugins/maven-install-plugin/issue-tracking.html The issue tracking URL should be http://jira.codehaus.org/browse/MINSTALL -- 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: (MINSTALL-22) Add ability to produce checksums for install:install-file
Add ability to produce checksums for install:install-file - Key: MINSTALL-22 URL: http://jira.codehaus.org/browse/MINSTALL-22 Project: Maven 2.x Install Plugin Type: Wish Reporter: Shinobu Kawai Priority: Minor It would be great if the checksums were also created in install:install-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: (MAVENUPLOAD-929) [NOT AN UPLOAD REQUEST] pom.xml is not uploaded for cactus 13-1.7.2
[NOT AN UPLOAD REQUEST] pom.xml is not uploaded for cactus 13-1.7.2 --- Key: MAVENUPLOAD-929 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-929 Project: maven-upload-requests Type: Bug Reporter: Shinobu Kawai The pom.xml is not uploaded for cactus 13-1.7.2. http://www.ibiblio.org/maven2/cactus/cactus/13-1.7.2/ -- 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: (MEV-404) pom for cactus:cactus-ant:13-1.7.2
pom for cactus:cactus-ant:13-1.7.2 -- Key: MEV-404 URL: http://jira.codehaus.org/browse/MEV-404 Project: Maven Evangelism Type: Bug Components: Missing POM Reporter: Shinobu Kawai initial pom suggestion for cactus:cactus-ant:13-1.7.2 -- 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: (MEV-405) pom for cactus:cactus:13-1.7.2
pom for cactus:cactus:13-1.7.2 -- Key: MEV-405 URL: http://jira.codehaus.org/browse/MEV-405 Project: Maven Evangelism Type: Bug Components: Missing POM Reporter: Shinobu Kawai initial pom suggestion for cactus:cactus:13-1.7.2 -- 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] Updated: (MEV-404) pom for cactus:cactus-ant:13-1.7.2
[ http://jira.codehaus.org/browse/MEV-404?page=all ] Shinobu Kawai updated MEV-404: -- Attachment: cactus-ant-13-1.7.2.pom > pom for cactus:cactus-ant:13-1.7.2 > -- > > Key: MEV-404 > URL: http://jira.codehaus.org/browse/MEV-404 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Shinobu Kawai > Attachments: cactus-ant-13-1.7.2.pom > > > initial pom suggestion for cactus:cactus-ant:13-1.7.2 -- 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] Updated: (MEV-405) pom for cactus:cactus:13-1.7.2
[ http://jira.codehaus.org/browse/MEV-405?page=all ] Shinobu Kawai updated MEV-405: -- Attachment: cactus-13-1.7.2.pom > pom for cactus:cactus:13-1.7.2 > -- > > Key: MEV-405 > URL: http://jira.codehaus.org/browse/MEV-405 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Shinobu Kawai > Attachments: cactus-13-1.7.2.pom > > > initial pom suggestion for cactus:cactus:13-1.7.2 -- 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: (MAVEN-1763) Maven - Guide to Maven Evangelism has wrong svn URL
Maven - Guide to Maven Evangelism has wrong svn URL --- Key: MAVEN-1763 URL: http://jira.codehaus.org/browse/MAVEN-1763 Project: Maven Type: Bug Components: documentation Reporter: Shinobu Kawai In the "Maven - Guide to Maven Evangelism" page, the svn URL is stated "svn://svn.codehaus.org/maven/scm/repository", but it is actually "svn://svn.codehaus.org/maven/repository". -- 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] Updated: (MAVEN-1763) Maven - Guide to Maven Evangelism has wrong svn URL
[ http://jira.codehaus.org/browse/MAVEN-1763?page=all ] Shinobu Kawai updated MAVEN-1763: - Attachment: MAVEN-1763 > Maven - Guide to Maven Evangelism has wrong svn URL > --- > > Key: MAVEN-1763 > URL: http://jira.codehaus.org/browse/MAVEN-1763 > Project: Maven > Type: Bug > Components: documentation > Reporter: Shinobu Kawai > Attachments: MAVEN-1763 > > > In the "Maven - Guide to Maven Evangelism" page, the svn URL is stated > "svn://svn.codehaus.org/maven/scm/repository", but it is actually > "svn://svn.codehaus.org/maven/repository". -- 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] Updated: (MAVEN-1763) Maven - Guide to Maven Evangelism has wrong svn URL
[ http://jira.codehaus.org/browse/MAVEN-1763?page=all ] Shinobu Kawai updated MAVEN-1763: - Attachment: MAVEN-1763 > Maven - Guide to Maven Evangelism has wrong svn URL > --- > > Key: MAVEN-1763 > URL: http://jira.codehaus.org/browse/MAVEN-1763 > Project: Maven > Type: Bug > Components: documentation > Reporter: Shinobu Kawai > Attachments: MAVEN-1763, MAVEN-1763 > > > In the "Maven - Guide to Maven Evangelism" page, the svn URL is stated > "svn://svn.codehaus.org/maven/scm/repository", but it is actually > "svn://svn.codehaus.org/maven/repository". -- 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: (CONTINUUM-667) need a way to limit the mount of time a unit test runs for
[ http://jira.codehaus.org/browse/CONTINUUM-667?page=comments#action_67167 ] Shinobu Kawai commented on CONTINUUM-667: - Since CONTINUUM-669 was marked as a duplicate of this issue, I would like this to be expanded to a more generic scope. A timeout should be able to be set per build, not only testing phase, as any phase of the build has a potential to hang. > need a way to limit the mount of time a unit test runs for > -- > > Key: CONTINUUM-667 > URL: http://jira.codehaus.org/browse/CONTINUUM-667 > Project: Continuum > Type: Bug > Components: Web interface, Core system > Versions: 1.0.3 > Reporter: james strachan > Priority: Blocker > > > We get lots of builds hanging in CI due to test cases with timing issues on > different platforms. (You'd be amazed how easy that is to do). We need a way > to put in a maximum amount of time (say 5 minutes) for a single unit test - > or a max time per entire test run (say 1 hour) so that we can be alerted if a > test hangs. > If a test hangs it normally hoses the entire CI server. The worst thing is > this makes the entire CI useless since it does no more builds and we don't > know its failed. > I understand there are complications in killing stuff in Java. (Though > java.lang.Process.destroy() works for most things). One option is to just > have a status XML file we can poll for on a canoncial URL > http;//serverhost/module/status.xml > then we can look to see if any of the builds are blocked and if they are we > can get nagios or something to reboot the box / restart the CI server etc. -- 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: (CONTINUUM-748) Build Now button on Build Definitions does not get grayed out.
Build Now button on Build Definitions does not get grayed out. -- Key: CONTINUUM-748 URL: http://jira.codehaus.org/browse/CONTINUUM-748 Project: Continuum Type: Bug Components: Web interface Versions: 1.0.3 Reporter: Shinobu Kawai "Build Now" button on Build Definitions does not get grayed out when another build is already running. This is inconsistant with the Show Projects screen, where you are not able to run a build on an already running 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
[jira] Created: (CONTINUUM-770) Abitily to manually kick off a schedule and all of it's builds
Abitily to manually kick off a schedule and all of it's builds -- Key: CONTINUUM-770 URL: http://jira.codehaus.org/browse/CONTINUUM-770 Project: Continuum Type: Wish Components: Web interface Reporter: Shinobu Kawai Priority: Minor It would be great if there was a 'Build Now' button on the Schedules page. The button would kick off the schedule, and run all the builds associated with it. -- 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: (MPJUNITREPORT-13) Ability to group packages and show in summary section
Ability to group packages and show in summary section - Key: MPJUNITREPORT-13 URL: http://jira.codehaus.org/browse/MPJUNITREPORT-13 Project: maven-junitreport-plugin Issue Type: Wish Reporter: Shinobu Kawai It would be great if you could specify package groups, and have summaries per group. Something like the -group option in javadoc. http://java.sun.com/j2se/1.3/docs/tooldocs/win32/javadoc.html#group -- 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: (MPTEST-67) maven.compile.target is not considered in test:compile
maven.compile.target is not considered in test:compile -- Key: MPTEST-67 URL: http://jira.codehaus.org/browse/MPTEST-67 Project: maven-test-plugin Issue Type: Bug Affects Versions: 1.8 Reporter: Shinobu Kawai Priority: Blocker Attachments: MPTEST-67 Since maven.compile.target is not used to compile, forking with a lower version JVM does not work. -- 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] Updated: (MPTEST-67) maven.compile.target is not considered in test:compile
[ http://jira.codehaus.org/browse/MPTEST-67?page=all ] Shinobu Kawai updated MPTEST-67: Attachment: MPTEST-67 Patch to use maven.compile.target > maven.compile.target is not considered in test:compile > -- > > Key: MPTEST-67 > URL: http://jira.codehaus.org/browse/MPTEST-67 > Project: maven-test-plugin > Issue Type: Bug >Affects Versions: 1.8 >Reporter: Shinobu Kawai >Priority: Blocker > Attachments: MPTEST-67 > > > Since maven.compile.target is not used to compile, forking with a lower > version JVM does not work. -- 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: (MPMULTIPROJECT-66) pre/postGoal defined in plugins are only called once during multiproject goals
pre/postGoal defined in plugins are only called once during multiproject goals -- Key: MPMULTIPROJECT-66 URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-66 Project: maven-multiproject-plugin Issue Type: Bug Affects Versions: 1.5 Reporter: Shinobu Kawai Priority: Critical pre/postGoal defined in plugins are only called once during multiproject goals. You can reproduce this problem by the following: maven genapp -Dmaven.genapp.template=default -Dmaven.genapp.template.id=parent -Dmaven.genapp.template.name=Parent -Dmaven.genapp.template.package=parent create child1 and child2 directories in child1 directory: maven genapp -Dmaven.genapp.template=default -Dmaven.genapp.template.id=child1 -Dmaven.genapp.template.name=Child1 -Dmaven.genapp.template.package=child1 in child2 directory: maven genapp -Dmaven.genapp.template=default -Dmaven.genapp.template.id=child2 -Dmaven.genapp.template.name=Child2 -Dmaven.genapp.template.package=child2 running maven multiproject:goal -Dgoal=clean in the parent project gives the following: + | Executing clean Child1 | Memory: 3M/4M + build:start: clean:clean: Running post goal: clean:clean + | Executing clean Child2 | Memory: 3M/4M + clean: build:end: build:start: clean:clean: clean: build:end: The "Running post goal: clean:clean" appears only once. (If you run maven multiproject:clean, you will see that it only gets run on the parent project.) As a workaround, you need to copy the pre/postGoal from the plugin.jelly to each (except for the first) project's maven.xml. However, this will cause multiple runs when you do individual child runs. -- 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: (MPMULTIPROJECT-67) maven-multiproject-plugin:deregister does not work
maven-multiproject-plugin:deregister does not work -- Key: MPMULTIPROJECT-67 URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-67 Project: maven-multiproject-plugin Issue Type: Bug Affects Versions: 1.5 Reporter: Shinobu Kawai maven-multiproject-plugin:deregister is trying to deregister "Multiproject Dependency Convergence Report". It should be "Dependency Convergence". -- 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] Updated: (MPMULTIPROJECT-67) maven-multiproject-plugin:deregister does not work
[ http://jira.codehaus.org/browse/MPMULTIPROJECT-67?page=all ] Shinobu Kawai updated MPMULTIPROJECT-67: Attachment: MPMULTIPROJECT-67 Patch to fix bug. > maven-multiproject-plugin:deregister does not work > -- > > Key: MPMULTIPROJECT-67 > URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-67 > Project: maven-multiproject-plugin > Issue Type: Bug >Affects Versions: 1.5 >Reporter: Shinobu Kawai > Attachments: MPMULTIPROJECT-67 > > > maven-multiproject-plugin:deregister is trying to deregister "Multiproject > Dependency Convergence Report". It should be "Dependency Convergence". -- 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: (MPMULTIPROJECT-68) maven-multiproject-plugin:register should not register if no child projects
maven-multiproject-plugin:register should not register if no child projects --- Key: MPMULTIPROJECT-68 URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-68 Project: maven-multiproject-plugin Issue Type: Wish Affects Versions: 1.5 Reporter: Shinobu Kawai Priority: Minor It would be great if the report was registered only if there were child projects. -- 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] Updated: (MPMULTIPROJECT-68) maven-multiproject-plugin:register should not register if no child projects
[ http://jira.codehaus.org/browse/MPMULTIPROJECT-68?page=all ] Shinobu Kawai updated MPMULTIPROJECT-68: Attachment: MPMULTIPROJECT-68 Patch to grant wish. > maven-multiproject-plugin:register should not register if no child projects > --- > > Key: MPMULTIPROJECT-68 > URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-68 > Project: maven-multiproject-plugin > Issue Type: Wish >Affects Versions: 1.5 >Reporter: Shinobu Kawai >Priority: Minor > Attachments: MPMULTIPROJECT-68 > > > It would be great if the report was registered only if there were child > projects. -- 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: (MPMULTIPROJECT-68) maven-multiproject-plugin:register should not register if no child projects
[ http://jira.codehaus.org/browse/MPMULTIPROJECT-68?page=comments#action_70796 ] Shinobu Kawai commented on MPMULTIPROJECT-68: - It worked with a fresh maven 1.0.2 + multiproject 1.5 + my patch. :) > maven-multiproject-plugin:register should not register if no child projects > --- > > Key: MPMULTIPROJECT-68 > URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-68 > Project: maven-multiproject-plugin > Issue Type: Wish >Affects Versions: 1.5 >Reporter: Shinobu Kawai >Priority: Minor > Attachments: MPMULTIPROJECT-68 > > > It would be great if the report was registered only if there were child > projects. -- 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] Updated: (MPEJB-23) ejb:init does not compile java code if tests are not run
[ http://jira.codehaus.org/browse/MPEJB-23?page=all ] Shinobu Kawai updated MPEJB-23: --- Attachment: MPEJB-23 Patch to fix bug. > ejb:init does not compile java code if tests are not run > > > Key: MPEJB-23 > URL: http://jira.codehaus.org/browse/MPEJB-23 > Project: maven-ejb-plugin > Issue Type: Bug >Reporter: Shinobu Kawai >Priority: Critical > Attachments: MPEJB-23 > > > When there are no tests, or maven.test.skip=true, then the build classes and > resources are not included in the ejb jar file. > As a workaround, you can set java:compile and java:jar-resources as preGoals > for ejb:ejb in your maven.xml: > > > > > > -- 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: (MPEJB-23) ejb:init does not compile java code if tests are not run
ejb:init does not compile java code if tests are not run Key: MPEJB-23 URL: http://jira.codehaus.org/browse/MPEJB-23 Project: maven-ejb-plugin Issue Type: Bug Reporter: Shinobu Kawai Priority: Critical Attachments: MPEJB-23 When there are no tests, or maven.test.skip=true, then the build classes and resources are not included in the ejb jar file. As a workaround, you can set java:compile and java:jar-resources as preGoals for ejb:ejb in your maven.xml: -- 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: (MPTEST-67) maven.compile.target is not considered in test:compile
[ http://jira.codehaus.org/browse/MPTEST-67?page=comments#action_70999 ] Shinobu Kawai commented on MPTEST-67: - Good point. You might want to create a new issue for that. The test plugin is recycling many of the java plugin properties (including maven.compile.source, too). It might be good to have test properties defaulting to the java properties. > maven.compile.target is not considered in test:compile > -- > > Key: MPTEST-67 > URL: http://jira.codehaus.org/browse/MPTEST-67 > Project: maven-test-plugin > Issue Type: Bug >Affects Versions: 1.8 >Reporter: Shinobu Kawai > Assigned To: Lukas Theussl >Priority: Blocker > Fix For: 1.8.1 > > Attachments: MPTEST-67 > > > Since maven.compile.target is not used to compile, forking with a lower > version JVM does not work. -- 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] Updated: (MPWAR-62) maven-war-plugin doesn't compile java sources when used with maven-test-plugin 1.8
[ http://jira.codehaus.org/browse/MPWAR-62?page=all ] Shinobu Kawai updated MPWAR-62: --- Attachment: MPWAR-62 Patch to fix bug against latest in SVN. > maven-war-plugin doesn't compile java sources when used with > maven-test-plugin 1.8 > --- > > Key: MPWAR-62 > URL: http://jira.codehaus.org/browse/MPWAR-62 > Project: maven-war-plugin > Issue Type: Bug >Affects Versions: 1.6.2 >Reporter: nicolas de loof > Assigned To: Lukas Theussl > Fix For: 1.6.3 > > Attachments: MPWAR-62, MPWAR-62.patch > > > I've found an issue when using latest versions of maven-test-plugin (1.8) : > when maven.test.skip=true is set, the goal is not executed. > This sounds good, BUT the maven-war-plugin use "test:test" goal to attain the > "java:compile" goal, so the generated war has no classes ! > The war:resources plugin should have > prereqs="war:war-resources,*java:compile*,test:test". -- 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: (MJAVADOC-81) Additional doclets do not run.
Additional doclets do not run. -- Key: MJAVADOC-81 URL: http://jira.codehaus.org/browse/MJAVADOC-81 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Shinobu Kawai Priority: Critical Although it is stated in the docs [1] that you can generate alternate doclet in addition to the project javadocs, only the first reportSet is run. This is due to the fact that JavadocReport#getOutputName(...) returns a fixed value, "apidocs/index". This should be configurable per reportSet. [1] http://maven.apache.org/plugins/maven-javadoc-plugin/configuration.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
[jira] Updated: (MJAVADOC-81) Additional doclets do not run.
[ http://jira.codehaus.org/browse/MJAVADOC-81?page=all ] Shinobu Kawai updated MJAVADOC-81: -- Attachment: pom.xml The pom that doesn't work. I get the following in the log: [INFO] Skipped "JavaDocs" report, file "apidocs/index.html" already exists for the English version. > Additional doclets do not run. > -- > > Key: MJAVADOC-81 > URL: http://jira.codehaus.org/browse/MJAVADOC-81 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Shinobu Kawai >Priority: Critical > Attachments: pom.xml > > > Although it is stated in the docs [1] that you can generate alternate doclet > in addition to the project javadocs, only the first reportSet is run. > This is due to the fact that JavadocReport#getOutputName(...) returns a fixed > value, "apidocs/index". This should be configurable per reportSet. > [1] http://maven.apache.org/plugins/maven-javadoc-plugin/configuration.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
[jira] Updated: (MJAVADOC-81) Additional doclets do not run.
[ http://jira.codehaus.org/browse/MJAVADOC-81?page=all ] Shinobu Kawai updated MJAVADOC-81: -- Attachment: MJAVADOC-81 Patch to expose name, description, and outputName. Applied, I can add the following to my pom to make it work: ... DocCheck DocCheck documentation doccheck/index ... > Additional doclets do not run. > -- > > Key: MJAVADOC-81 > URL: http://jira.codehaus.org/browse/MJAVADOC-81 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Shinobu Kawai >Priority: Critical > Attachments: MJAVADOC-81, pom.xml > > > Although it is stated in the docs [1] that you can generate alternate doclet > in addition to the project javadocs, only the first reportSet is run. > This is due to the fact that JavadocReport#getOutputName(...) returns a fixed > value, "apidocs/index". This should be configurable per reportSet. > [1] http://maven.apache.org/plugins/maven-javadoc-plugin/configuration.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
[jira] Created: (MPJUNITREPORT-14) Don't run test:test if not needed.
Don't run test:test if not needed. -- Key: MPJUNITREPORT-14 URL: http://jira.codehaus.org/browse/MPJUNITREPORT-14 Project: maven-junitreport-plugin Issue Type: Wish Reporter: Shinobu Kawai Priority: Minor Currently, test:test is called even if it has already run with the ignore failure option. It would be great if the report plugin didn't call test:test if the tests were completed. -- 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: (MJAVADOC-85) allow only one taglet
[ http://jira.codehaus.org/browse/MJAVADOC-85?page=comments#action_72576 ]
Shinobu Kawai commented on MJAVADOC-85:
---
Unfortunately, the plugin currently only allows one taglet.
> allow only one taglet
> --
>
> Key: MJAVADOC-85
> URL: http://jira.codehaus.org/browse/MJAVADOC-85
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Reporter: Martin Desruisseaux
>
> The {{}} configuration element in the javadoc plugin allows for only
> one taglet, or doesn't document how to add more than one taglet.
> * I tried to put one than one {{}} element in the {{pom.xml}} file,
> but the last one seems to override all the previous ones.
> * I tried space, coma, : and ; as separator, without success.
> It should be possible to add an arbitrary amount of {{}} elements,
> and each of them should register a new taglet (through a new occurence of
> {{-taglet}} argument given to the {{javadoc}} command line I guess). I tested
> that multiple occurence of {{}} works as expected with Ant.
--
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: (MPTEST-66) 1.8 version introduces bug in other plugins
[ http://jira.codehaus.org/browse/MPTEST-66?page=comments#action_72972 ] Shinobu Kawai commented on MPTEST-66: - I like nicolas' solution for backward compatability, but I'm not sure if it is "right" to assume that test:test will always compile and copy resources. If other plugins need the java:compile and java:jar-resouces to be run, I think it should explicitly state that, like the JAR plugin example given. (Having said that, I don't like the idea of compiling twice, either...) > 1.8 version introduces bug in other plugins > --- > > Key: MPTEST-66 > URL: http://jira.codehaus.org/browse/MPTEST-66 > Project: maven-test-plugin > Issue Type: Bug >Affects Versions: 1.8 >Reporter: nicolas de loof > Assigned To: Lukas Theussl > Attachments: MPTEST-66.patch > > > When maven-war-plugin is run with maven.test.skip=true, the sources are not > compiled. > Latest version of test-plugin has removed prereqs on java:compile & > java:jar-resources. > Assuming other plugins themself run the java:compile goal may have impact on > lots of plugin and can break many application builds. I think the "test:test" > goal may have a prereqs="java:compile,java:jar-resources", and the > "test:compile" goal only prereqs="test:prepare-filesystem,test:test-resources" -- 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: (MPTEST-66) 1.8 version introduces bug in other plugins
[ http://jira.codehaus.org/browse/MPTEST-66?page=comments#action_72976 ] Shinobu Kawai commented on MPTEST-66: - Actually, it's going to compile twice anyways (unless we revert the whole MPTEST-46 fix) because test:compile is being attainGoal-ed, and that will call java:compile. java:compile and java:jar-resources will do nothing on the second time, so the only impact would be if pre/postGoal's were set in maven.xml. > 1.8 version introduces bug in other plugins > --- > > Key: MPTEST-66 > URL: http://jira.codehaus.org/browse/MPTEST-66 > Project: maven-test-plugin > Issue Type: Bug >Affects Versions: 1.8 >Reporter: nicolas de loof > Assigned To: Lukas Theussl > Attachments: MPTEST-66.patch > > > When maven-war-plugin is run with maven.test.skip=true, the sources are not > compiled. > Latest version of test-plugin has removed prereqs on java:compile & > java:jar-resources. > Assuming other plugins themself run the java:compile goal may have impact on > lots of plugin and can break many application builds. I think the "test:test" > goal may have a prereqs="java:compile,java:jar-resources", and the > "test:compile" goal only prereqs="test:prepare-filesystem,test:test-resources" -- 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: (MPTEST-66) 1.8 version introduces bug in other plugins
[ http://jira.codehaus.org/browse/MPTEST-66?page=comments#action_73116 ] Shinobu Kawai commented on MPTEST-66: - Not clear how the whole prereqs stuff work, but I was wondering if adding an attribute to call attainGoal with the same werkz session would work. Something like . > 1.8 version introduces bug in other plugins > --- > > Key: MPTEST-66 > URL: http://jira.codehaus.org/browse/MPTEST-66 > Project: maven-test-plugin > Issue Type: Bug >Affects Versions: 1.8 >Reporter: nicolas de loof > Assigned To: Lukas Theussl > Fix For: 1.8.1 > > Attachments: MPTEST-66.patch > > > When maven-war-plugin is run with maven.test.skip=true, the sources are not > compiled. > Latest version of test-plugin has removed prereqs on java:compile & > java:jar-resources. > Assuming other plugins themself run the java:compile goal may have impact on > lots of plugin and can break many application builds. I think the "test:test" > goal may have a prereqs="java:compile,java:jar-resources", and the > "test:compile" goal only prereqs="test:prepare-filesystem,test:test-resources" -- 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: (MPWAR-62) maven-war-plugin doesn't compile java sources when used with maven-test-plugin 1.8
[ http://jira.codehaus.org/browse/MPWAR-62?page=comments#action_74214 ] Shinobu Kawai commented on MPWAR-62: This should be revisited once MPTEST-66 is fixed one way or another. > maven-war-plugin doesn't compile java sources when used with > maven-test-plugin 1.8 > --- > > Key: MPWAR-62 > URL: http://jira.codehaus.org/browse/MPWAR-62 > Project: maven-war-plugin > Issue Type: Bug >Affects Versions: 1.6.2 >Reporter: nicolas de loof > Assigned To: Lukas Theussl > Fix For: 1.6.3 > > Attachments: MPWAR-62, MPWAR-62.patch, MPWAR-62.patch > > > I've found an issue when using latest versions of maven-test-plugin (1.8) : > when maven.test.skip=true is set, the goal is not executed. > This sounds good, BUT the maven-war-plugin use "test:test" goal to attain the > "java:compile" goal, so the generated war has no classes ! > The war:resources plugin should have > prereqs="war:war-resources,*java:compile*,test:test". -- 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] Closed: (MPEJB-23) ejb:init does not compile java code if tests are not run
[ http://jira.codehaus.org/browse/MPEJB-23?page=all ] Shinobu Kawai closed MPEJB-23. -- Resolution: Fixed This should be revisited once MPTEST-66 is fixed one way or another. > ejb:init does not compile java code if tests are not run > > > Key: MPEJB-23 > URL: http://jira.codehaus.org/browse/MPEJB-23 > Project: maven-ejb-plugin > Issue Type: Bug >Reporter: Shinobu Kawai >Priority: Critical > Fix For: 1.7.3 > > Attachments: MPEJB-23 > > > When there are no tests, or maven.test.skip=true, then the build classes and > resources are not included in the ejb jar file. > As a workaround, you can set java:compile and java:jar-resources as preGoals > for ejb:ejb in your maven.xml: > > > > > > -- 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: (MPXDOC-200) [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6
[ http://jira.codehaus.org/browse/MPXDOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87869 ] Shinobu Kawai commented on MPXDOC-200: -- This is due to a jelly bug [1] due to a change in the java6 ClassLoader implementation [2]. [1] https://issues.apache.org/jira/browse/JELLY-274 [2] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6446627 > [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6 > > > Key: MPXDOC-200 > URL: http://jira.codehaus.org/browse/MPXDOC-200 > Project: maven-xdoc-plugin > Issue Type: Bug > Environment: java version "1.6.0-beta2" > Java(TM) SE Runtime Environment (build 1.6.0-beta2-b86) > Java HotSpot(TM) Client VM (build 1.6.0-beta2-b86, mixed mode, sharing) > Win 2K > Maven 1.1 RC 1 from Oct 2006 >Reporter: Benoit Xhenseval >Priority: Critical > > Hi > Issue discussed on > http://www.nabble.com/-m1.1-rc1--javadoc-does-not-generate-anything...-tf2220969.html > Here is the log: > xdoc:init: > [echo] Generates the directory structure required for xdocs > xdoc:i18n-validation: > [echo] Validation of the locale entries > BUILD FAILED > File.. file:/C:/Documents and > Settings/xhensevb/.maven/cache/maven-xdoc-plugin-1.10.1-SNAPSHOT/plugin.jelly > Element... j:arg > Line.. 666 > Column 70 > [Ljava.lang.Object; > Total time : 1 minutes 9 seconds > Finished at : 12 October 2006 13:54:00 BST > --- > I though that the issue may be related to generics and calling this > invokeStatic on java.util.Arrays > but this seems to work when I try at home with JDK 1.5.08 however, I'm having > trouble with JDK 6-b2 > May be the interface has changed or one cannot use the following jelly code: > var="availableLocales"/> > var="availableLocalesAsList"> > > > I have checked the API for JDK6 and it seems to be the same... > A simple maven site or maven multiproject:site under JDK 6 should confirm the > issue, works fine under 1.5 > Definitely something around this "asList" call... > Benoit -- 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: (MPXDOC-200) [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6
[ http://jira.codehaus.org/browse/MPXDOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87872 ] Shinobu Kawai commented on MPXDOC-200: -- I applied a workaround to SVN, but looks like I don't have permission to resolve this bug... > [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6 > > > Key: MPXDOC-200 > URL: http://jira.codehaus.org/browse/MPXDOC-200 > Project: maven-xdoc-plugin > Issue Type: Bug > Environment: java version "1.6.0-beta2" > Java(TM) SE Runtime Environment (build 1.6.0-beta2-b86) > Java HotSpot(TM) Client VM (build 1.6.0-beta2-b86, mixed mode, sharing) > Win 2K > Maven 1.1 RC 1 from Oct 2006 >Reporter: Benoit Xhenseval >Priority: Critical > > Hi > Issue discussed on > http://www.nabble.com/-m1.1-rc1--javadoc-does-not-generate-anything...-tf2220969.html > Here is the log: > xdoc:init: > [echo] Generates the directory structure required for xdocs > xdoc:i18n-validation: > [echo] Validation of the locale entries > BUILD FAILED > File.. file:/C:/Documents and > Settings/xhensevb/.maven/cache/maven-xdoc-plugin-1.10.1-SNAPSHOT/plugin.jelly > Element... j:arg > Line.. 666 > Column 70 > [Ljava.lang.Object; > Total time : 1 minutes 9 seconds > Finished at : 12 October 2006 13:54:00 BST > --- > I though that the issue may be related to generics and calling this > invokeStatic on java.util.Arrays > but this seems to work when I try at home with JDK 1.5.08 however, I'm having > trouble with JDK 6-b2 > May be the interface has changed or one cannot use the following jelly code: > var="availableLocales"/> > var="availableLocalesAsList"> > > > I have checked the API for JDK6 and it seems to be the same... > A simple maven site or maven multiproject:site under JDK 6 should confirm the > issue, works fine under 1.5 > Definitely something around this "asList" call... > Benoit -- 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] Resolved: (MPXDOC-200) [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6
[ http://jira.codehaus.org/browse/MPXDOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinobu Kawai resolved MPXDOC-200. -- Assignee: Shinobu Kawai Resolution: Fixed Fix Version/s: 1.10.1 Resolved! :) > [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6 > > > Key: MPXDOC-200 > URL: http://jira.codehaus.org/browse/MPXDOC-200 > Project: maven-xdoc-plugin > Issue Type: Bug > Environment: java version "1.6.0-beta2" > Java(TM) SE Runtime Environment (build 1.6.0-beta2-b86) > Java HotSpot(TM) Client VM (build 1.6.0-beta2-b86, mixed mode, sharing) > Win 2K > Maven 1.1 RC 1 from Oct 2006 >Reporter: Benoit Xhenseval > Assigned To: Shinobu Kawai >Priority: Critical > Fix For: 1.10.1 > > > Hi > Issue discussed on > http://www.nabble.com/-m1.1-rc1--javadoc-does-not-generate-anything...-tf2220969.html > Here is the log: > xdoc:init: > [echo] Generates the directory structure required for xdocs > xdoc:i18n-validation: > [echo] Validation of the locale entries > BUILD FAILED > File.. file:/C:/Documents and > Settings/xhensevb/.maven/cache/maven-xdoc-plugin-1.10.1-SNAPSHOT/plugin.jelly > Element... j:arg > Line.. 666 > Column 70 > [Ljava.lang.Object; > Total time : 1 minutes 9 seconds > Finished at : 12 October 2006 13:54:00 BST > --- > I though that the issue may be related to generics and calling this > invokeStatic on java.util.Arrays > but this seems to work when I try at home with JDK 1.5.08 however, I'm having > trouble with JDK 6-b2 > May be the interface has changed or one cannot use the following jelly code: > var="availableLocales"/> > var="availableLocalesAsList"> > > > I have checked the API for JDK6 and it seems to be the same... > A simple maven site or maven multiproject:site under JDK 6 should confirm the > issue, works fine under 1.5 > Definitely something around this "asList" call... > Benoit -- 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: (CONTINUUM-668) Build history not showing after 1.0.2 to 1.0.3 migration
Build history not showing after 1.0.2 to 1.0.3 migration Key: CONTINUUM-668 URL: http://jira.codehaus.org/browse/CONTINUUM-668 Project: Continuum Type: Bug Components: Web interface Versions: 1.0.3 Environment: hpux, winxp Reporter: Shinobu Kawai After following the instructions at http://maven.apache.org/continuum/upgrade.html and upgrading to 1.0.3, the build history screen shows nothing. Builds after the upgrade are showing. However, if I directly put the URL for a specific build, I can view the results. Like this: http://localhost:8080/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=534&id=14 -- 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: (CONTINUUM-669) Ability to set timeout to a build
Ability to set timeout to a build - Key: CONTINUUM-669 URL: http://jira.codehaus.org/browse/CONTINUUM-669 Project: Continuum Type: Wish Components: Core system Versions: 1.0.3 Reporter: Shinobu Kawai Priority: Minor It would be great if we could set a timeout to a build. I am scheduling nightly builds, but if one build doesn't come back, all the projects after will not get built. -- 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: (MPCHANGELOG-87) Ability to set timezone for the report's Date column.
Ability to set timezone for the report's Date column. - Key: MPCHANGELOG-87 URL: http://jira.codehaus.org/browse/MPCHANGELOG-87 Project: maven-changelog-plugin Type: Wish Reporter: Shinobu Kawai It would be great if we were able to specify timezone for the report's Date column. Something like a "maven.changelog.timezone" property. e.g. Setting the below will show the dates in U.S. Pacific Time: maven.changelog.timezone=America/Los_Angeles -- 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] Closed: (CONTINUUM-497) Ability to download from the Working Copy page.
[ http://jira.codehaus.org/browse/CONTINUUM-497?page=all ] Shinobu Kawai closed CONTINUUM-497: --- Resolution: Fixed Fix Version: 1.0.3 Looks fixed in 1.0.3. :) > Ability to download from the Working Copy page. > --- > > Key: CONTINUUM-497 > URL: http://jira.codehaus.org/browse/CONTINUUM-497 > Project: Continuum > Type: Wish > Components: Web interface > Reporter: Shinobu Kawai > Priority: Trivial > Fix For: 1.0.3 > > > It would be great if there was an interface to download a file from the > Working Copy page. -- 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: (CONTINUUM-675) Add Working Copy to the Legends
Add Working Copy to the Legends --- Key: CONTINUUM-675 URL: http://jira.codehaus.org/browse/CONTINUUM-675 Project: Continuum Type: Improvement Components: Web interface Versions: 1.0.3 Reporter: Shinobu Kawai Priority: Trivial Add "Working Copy" to the Legends on the left -- 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: (CONTINUUM-676) Typo in Legend : "Build In Progess"
Typo in Legend : "Build In Progess" --- Key: CONTINUUM-676 URL: http://jira.codehaus.org/browse/CONTINUUM-676 Project: Continuum Type: Bug Components: Web interface Versions: 1.0.3 Reporter: Shinobu Kawai Priority: Trivial Should be "Build In Progress" with an 'r'. -- 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: (CONTINUUM-677) Developer access not showing https
Developer access not showing https -- Key: CONTINUUM-677 URL: http://jira.codehaus.org/browse/CONTINUUM-677 Project: Continuum Type: Bug Components: Documentation Reporter: Shinobu Kawai Priority: Minor In the Source Repository section [1] of the web site, "Developer access" and "Access from behind a firewall" both show http URLs. It should be https. The pom shows https, so maybe a newer project-info-report plugin is needed... [1] http://maven.apache.org/continuum/source-repository.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
[jira] Created: (MSITE-130) Site generation fails for site.xml in UTF8 with BOM
Site generation fails for site.xml in UTF8 with BOM --- Key: MSITE-130 URL: http://jira.codehaus.org/browse/MSITE-130 Project: Maven 2.x Site Plugin Type: Improvement Reporter: Shinobu Kawai Priority: Critical I get the following error if I edit site.xml with Windows Notepad. [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Can't read site descriptor. only whitespace content allowed before start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1) This is due to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058 . Since Sun is saying they won't fix this "RFE" (which I think is a bug), we need a workaround. -- 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: (CONTINUUM-695) Ability to edit Notifier from Project.
Ability to edit Notifier from Project. -- Key: CONTINUUM-695 URL: http://jira.codehaus.org/browse/CONTINUUM-695 Project: Continuum Type: Wish Components: Web interface Versions: 1.0.3 Reporter: Shinobu Kawai Priority: Minor It would be great if you could edit the Notifier added from the Project. As a workaround, I am updating the table in the database: ij> update sa.ProjectNotifier set send_On_Success='N'; -- 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: (CONTINUUM-702) Ability to show build output only if build fails
Ability to show build output only if build fails Key: CONTINUUM-702 URL: http://jira.codehaus.org/browse/CONTINUUM-702 Project: Continuum Type: Wish Components: Mail Notifier Reporter: Shinobu Kawai Priority: Minor It would be great if it was possible to toggle whether the build output is put in the notification. Depending on the project, build outputs can be several MBs, and we already have a link to the online report. Instead of clogging the developer's mailboxes with success outputs, an option to show the output only if the build fails would be nice. -- 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: (CONTINUUM-712) Download as text link in Build result page does not work from URL send in notification mails
Download as text link in Build result page does not work from URL send in
notification mails
-
Key: CONTINUUM-712
URL: http://jira.codehaus.org/browse/CONTINUUM-712
Project: Continuum
Type: Bug
Components: Web interface
Versions: 1.0.3
Reporter: Shinobu Kawai
When you go to the Build result page from the link sent by the notification
mail, the URL is something like this:
http://localhost:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/21/buildId/704
Since the id and buildId are not in request parameter form, the "Download as
text" link becomes something like this:
http://localhost:8080/continuum/servlet/browse?file=$requestUtil.getParameter('id')/${requestUtil.getParameter('buildId')}.log.txt
Therefore, failing to download.
--
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
