[jira] Closed: (MEAR-41) publish 2.3-SNAPSHOT to snapshots repo
[ http://jira.codehaus.org/browse/MEAR-41?page=all ] Stephane Nicoll closed MEAR-41. --- Assignee: Stephane Nicoll Resolution: Fixed Done: http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-ear-plugin/2.3-SNAPSHOT/ > publish 2.3-SNAPSHOT to snapshots repo > --- > > Key: MEAR-41 > URL: http://jira.codehaus.org/browse/MEAR-41 > Project: Maven 2.x Ear Plugin > Issue Type: Task >Affects Versions: 2.3 >Reporter: Ian Springer > Assigned To: Stephane Nicoll > > Would someone please publish a 2.3-SNAPSHOT build to > http://people.apache.org/maven-snapshot-repository/? > Thanks, > Ian -- 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: (JXR-6) Javadoc linked incorrectly
[ http://jira.codehaus.org/browse/JXR-6?page=comments#action_77616 ] Roland Kofler commented on JXR-6: - i am the seon person at maven user list who is complaining this bug again, for multi projects with non aggregated javadoc this does not work > Javadoc linked incorrectly > -- > > Key: JXR-6 > URL: http://jira.codehaus.org/browse/JXR-6 > Project: Maven JXR > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Mike Perham > Assigned To: fabrizio giustina > Fix For: 1.0 > > Attachments: jxr.javadoc.txt > > > Javadocs are being linked incorrectly from the JXR output. This patch fixes > the links on our 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: (MJAVADOC-82) 'sourcepath' should not be mandatory when using 'subpackages' configuration
[ http://jira.codehaus.org/browse/MJAVADOC-82?page=all ]
Vincent Siveton updated MJAVADOC-82:
Attachment: MJAVADOC-82.rar
I tried it on dummy projects (see file) with jdk 1.4&1.5 and all seems to work.
Could you send us a true project?
Also, could you tried with -Ddebug=true and verify the content of 'options' and
'package-list' files in target\site\apidocs
Let me know.
> 'sourcepath' should not be mandatory when using 'subpackages' configuration
> ---
>
> Key: MJAVADOC-82
> URL: http://jira.codehaus.org/browse/MJAVADOC-82
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Damien Lecan
> Assigned To: Vincent Siveton
> Fix For: 2.1
>
> Attachments: MJAVADOC-82.rar
>
>
> It is impossible to use 'subpackages' configuration without specifying
> 'sourcepath' directory.
> This works :
> maven-javadoc-plugin
>
> ${basedir}/src/main/java
>
> my.package:my.package2
>
>
>
> but this one doesn't works (without sourcepath with sources default path)
>
> maven-javadoc-plugin
>
>
> my.package:my.package2
>
>
>
--
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: (MNG-2603) Reactor project sorting broken for plugins
[ http://jira.codehaus.org/browse/MNG-2603?page=all ] Kenney Westerhof closed MNG-2603. - Assignee: Kenney Westerhof Resolution: Fixed fixed in revision 463922. This bug was introduced by an accidental commit I made on the ProjectSorter. Sorry about that! > Reactor project sorting broken for plugins > -- > > Key: MNG-2603 > URL: http://jira.codehaus.org/browse/MNG-2603 > Project: Maven 2 > Issue Type: Bug >Reporter: Kenney Westerhof > Assigned To: Kenney Westerhof > > it0042 demonstrates this. The plugin is put at the end of the reactor list > (because it's last in ). > It0092 is basically the same test, but the plugin is listed first, so this > one works. > If you move the test-plugin to the top of the modules in > it0042, the build succeeds (with mvn clean install, after rm -rf > ~/.m2/repository/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] Updated: (MCHANGES-60) The jira report should handle the nonProxyHosts specified in settings.xml
[ http://jira.codehaus.org/browse/MCHANGES-60?page=all ] Dennis Lundberg updated MCHANGES-60: Affects Version/s: (was: 2.0) Fix Version/s: (was: 2.0-beta-2) (was: 2.0) > The jira report should handle the nonProxyHosts specified in settings.xml > - > > Key: MCHANGES-60 > URL: http://jira.codehaus.org/browse/MCHANGES-60 > Project: Maven 2.x Changes Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-2 > Environment: A network with a proxy to access the outside, and a JIRA > inside the network. >Reporter: Pierre-Antoine Grégoire > > These nonProxyHosts can be retrieved with the > settings.getActiveProxy().getNonProxyHosts(); > This returns a String containing a (usually?)comma-separated list of > nonProxyHosts. > If the jira URL matches one of these hosts, it should not use any proxy of > course ;). > I haven't found a nonProxyHosts concept in commons-httpclient, so it should > be checked in the determineProxy Method of AbstractJiraDownloader. > This is quickly fixed and would be very useful ;) > Thanks in advance -- 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: (MCHANGES-54) jira-report with filter specified gives 500 error
[ http://jira.codehaus.org/browse/MCHANGES-54?page=comments#action_77630 ] Dennis Lundberg commented on MCHANGES-54: - Have you tried to use "&" instead of just "&" in your configuration? > jira-report with filter specified gives 500 error > - > > Key: MCHANGES-54 > URL: http://jira.codehaus.org/browse/MCHANGES-54 > Project: Maven 2.x Changes Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-2 >Reporter: Roald Bankras > > I run into a problem when I try to add a filter to my report configuration. > When I add the following filter to the pom, > running changes gives a 500 error. > > &sorter/field=priority&sorter/order=DESC&sorter/field=updated&sorter/order=DESC&sorter/field=fixVersions&sorter/order=ASC > > It seems that the leading & is removed from the url. -- 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: (MCHANGELOG-50) Changes are not sorted by date properly
[ http://jira.codehaus.org/browse/MCHANGELOG-50?page=all ] Dennis Lundberg closed MCHANGELOG-50. - Resolution: Fixed Fixed in revision 463930. > Changes are not sorted by date properly > --- > > Key: MCHANGELOG-50 > URL: http://jira.codehaus.org/browse/MCHANGELOG-50 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Fabrice BELLINGARD > Assigned To: Dennis Lundberg >Priority: Minor > Fix For: 2.0 > > Attachments: ChangeLogReport-sortEntries.txt > > > A new variable for the sorted entries is missing In > ChangeLogReport#doChangedSetTable(...) when sorting the entries array. See > the iterator: it uses the "entries" variable. > I'll fix 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] Updated: (MCHANGELOG-49) Add a text that explain that no developers are in pom
[ http://jira.codehaus.org/browse/MCHANGELOG-49?page=all ] Dennis Lundberg updated MCHANGELOG-49: -- Summary: Add a text that explain that no developers are in pom (was: Add a text that explain that no developpers are in pom) > Add a text that explain that no developers are in pom > - > > Key: MCHANGELOG-49 > URL: http://jira.codehaus.org/browse/MCHANGELOG-49 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement > Environment: Windows XP >Reporter: Rémy Sanlaville > Assigned To: Dennis Lundberg > > I have to add the section in my pom for the Developer Activity > Report else this report is empty. > Emmanuel Venisse > developers are necessary, because we use them in the 3 > reports of changelog plugin. But instead of > an empty screen, we must have a text that explain that no developers are in > pom. Can you file an issue for this? > It could be nice also to update the changelog web site to add this > information. > http://maven.apache.org/plugins/maven-changelog-plugin/howto.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] Closed: (MCHANGELOG-49) Add a text that explain that no developers are in pom
[ http://jira.codehaus.org/browse/MCHANGELOG-49?page=all ] Dennis Lundberg closed MCHANGELOG-49. - Resolution: Fixed Fix Version/s: 2.0 Fixed in revision 463944. > Add a text that explain that no developers are in pom > - > > Key: MCHANGELOG-49 > URL: http://jira.codehaus.org/browse/MCHANGELOG-49 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement > Environment: Windows XP >Reporter: Rémy Sanlaville > Assigned To: Dennis Lundberg > Fix For: 2.0 > > > I have to add the section in my pom for the Developer Activity > Report else this report is empty. > Emmanuel Venisse > developers are necessary, because we use them in the 3 > reports of changelog plugin. But instead of > an empty screen, we must have a text that explain that no developers are in > pom. Can you file an issue for this? > It could be nice also to update the changelog web site to add this > information. > http://maven.apache.org/plugins/maven-changelog-plugin/howto.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] Closed: (MCHANGELOG-47) Cannot find .cvspass file. Documentation not up-to-date.
[ http://jira.codehaus.org/browse/MCHANGELOG-47?page=all ] Dennis Lundberg closed MCHANGELOG-47. - Resolution: Won't Fix Closing this as it is not relevant to the changelog plugin. If you are still having problems with the .cvspass file please file a JIRA issue for Maven SCM. > Cannot find .cvspass file. Documentation not up-to-date. > - > > Key: MCHANGELOG-47 > URL: http://jira.codehaus.org/browse/MCHANGELOG-47 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 > Environment: Maven2 on Windows in Eclipse with CVS (anonymous pserver) > Maven2 on GenToo in CruiseControl with CVS (anonymous pserver) >Reporter: Paul R. Saxman > > I've run into a few issues while using this plugin, which are as follows: > - When I try to run the Maven 2 changelog plugin in Eclipse or using > CruiseControl, I get an error that the file .cvspass cannot be found. > - I've found a reference to the .cvspass file on the Maven 1 plugin > documentation, but not in the Maven 2 documentation. > - The Maven 2 documentation specifies to use the groupId > org.apache.maven.plugins for the plugin, which doesn't exist on ibiblio. The > plugin actually exists at org.codehaus.mojo; HOWEVER, it is not documented as > being part of Mojo at http://mojo.codehaus.org. > - When I follow the Maven 1 instructions to generate the .cvspass file, I get > the error "The plugin 'org.apache.maven.plugins:maven-changelog-plugin' does > not exist or no valid version could be found". > - Passing in a password (which doesn't really exist since I'm using an > anonymous pserver) using the Maven 2 plugin "password" parameter has no > effect, which is consistent with the documentation. Is there any way to not > bother with a password or to specify an empty password? -- 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: (MCHANGELOG-48) The link generated in the report contain only one occurrence if a duplicated word is used in the scm repository url.
[ http://jira.codehaus.org/browse/MCHANGELOG-48?page=comments#action_77637 ] Dennis Lundberg commented on MCHANGELOG-48: --- I have done some testing on this and have come to the conclusion that the plugin is working as expected. I have not been able to reproduce the problem you are describing. The method you mention take two parameters. Here's a fake example that I have used for testing: base: 'http://svn.sourceforge.net/viewvc/dbunit/dbunit/trunk/' target: '/trunk/pom.xml' It takes the first token from target: "trunk" and tries to find it in base. It will not find it until it looks at the last token. Then the two are merged into: http://svn.sourceforge.net/viewvc/dbunit/dbunit/trunk/pom.xml With your config this would translate into: base: 'http://mysubversion/viewvc/lgrefapp/lgrefapp/trunk' target: '/trunk/pom.xml' Please try the latest SNAPSHOT and see you still experience this problem. > The link generated in the report contain only one occurrence if a duplicated > word is used in the scm repository url. > > > Key: MCHANGELOG-48 > URL: http://jira.codehaus.org/browse/MCHANGELOG-48 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Giorgio Urto >Priority: Minor > > We have chose this svn repository layout > > > . > > where is a svn repository, and are directory > having each one it's trunk, tags and branch. > If the product have only one component, we have product and component with > equals names. > es: http://mysubversion/workarea/lgrefapp/lgrefapp/trunk > where: >- workarea is the root directory of all the products >- the first occurrence of lgrefapp is the product >- the second occurrence of lgrefapp is the component > > The link generated by changelog report contains only one occurrence of > lgrefapp > es: http://mysubversion/workarea/lgrefapp/trunk/. > So the links are broken. > Thank you > Giorgio > Here are my configurations: > > http://mysubversion/viewvc/lgrefapp/lgrefapp/trunk > > scm:svn:http://mysubversion/workarea/lgrefapp/lgrefapp/trunk > scm:svn:http://[EMAIL > PROTECTED]/workarea/lgrefapp/lgrefapp/trunk > > > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-SNAPSHOT > > > dual-report > > range > 365 > > > > > changelog > file-activity > dev-activity > > > > -- 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: (MCHANGES-21) Dependency on javax.mail should not be fixed on 1.3.2
[ http://jira.codehaus.org/browse/MCHANGES-21?page=comments#action_77639 ] Andrew Williams commented on MCHANGES-21: - Fixed in PLX-178 > Dependency on javax.mail should not be fixed on 1.3.2 > - > > Key: MCHANGES-21 > URL: http://jira.codehaus.org/browse/MCHANGES-21 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Environment: 2.0-beta-2-SNAPSHOT of the plugin, actually >Reporter: Grégory Joseph > Assigned To: fabrizio giustina > Fix For: 2.0-beta-2 > > > ... since javax.mail-1.3.2 is not available from sun anymore.. The dependency > should probably be [1.3,) -- 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: (MCHANGELOG-16) when using svn, links are wrong
[ http://jira.codehaus.org/browse/MCHANGELOG-16?page=all ] Dennis Lundberg closed MCHANGELOG-16. - Resolution: Won't Fix Closing as "Won't Fix" beacuse the web presentation system for SCM used in this example seems to be extremely rare. Google turned up 123 hits for "websvncommons" most of which comes from our JIRA or mailing lists. > when using svn, links are wrong > --- > > Key: MCHANGELOG-16 > URL: http://jira.codehaus.org/browse/MCHANGELOG-16 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 >Reporter: Julian Wood >Priority: Minor > Attachments: MCHANGELOG-16.patch, test.zip > > > Here's my setup: > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk > > ... > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-beta-2-SNAPSHOT > > > changes > > > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= > range > 90 > > > changelog > file-activity > dev-activity > > > > > With that displayFileDetailUrl, I get links like this in the resultant > changelog in my site: > http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= > but it should be like this: > link = > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- 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: (MNG-2612) antrun's exec task breaks in 2.0.5-SNAPSHOT
antrun's exec task breaks in 2.0.5-SNAPSHOT --- Key: MNG-2612 URL: http://jira.codehaus.org/browse/MNG-2612 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.5 Environment: windows Reporter: Dan Tran Attachments: pom.xml I have no problem run the below pom in 2.0.4, but in 2.0.5-SNAPSHOT. mvn package throws this [INFO] Error executing ant tasks Embedded error: Execute failed: java.io.IOException: CreateProcess: mvn.bat --he lp error=5 Here is the pom http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 org.codehaus.mojo.pde m2eclipse 1.0-SNAPSHOT pom AntRun break in 2.0.5-SNAPSHOT Build maven-antrun-plugin build compile run --- -- 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: (MCHANGELOG-16) when using svn, links are wrong
[ http://jira.codehaus.org/browse/MCHANGELOG-16?page=comments#action_77647 ] Julian Wood commented on MCHANGELOG-16: --- Dennis, I think you are missing a lot of information. I haven't had time to look in detail, but let me fill you in from what I know, and what I suspect. 1. The decision to close - websvncommons? That is just our URL. Not the name of the presentation system, which is websvn (http://websvn.tigris.org/) Try looking that up in google :-) As far as I know, not just svn, but every web presentation system has a different url for to show the listing of a directory vs the detailed changes or the printout of a file, which was the point of this change. I don't know how you can justify forcing a single URL on developers to cover all potential cases. 2. I suspect that your conclusion that it breaks other systems is wrong. We basically add one 'if' clause to a number of others, to account for this case in particular. The other cases were untouched. That in itself should give you confidence in the patch. We tested it with other systems and it was fine with everyone for over 6 months. So I think there was some other coincidental problem that you encountered. And if there was a problem, how could it be anything more than a trivial fix? Why was the problem never described, at all? I'm sure your new problem would be easy to fix. So, I'm going to reopen the issue, because I think it's incredibly valuable to be able to click on the link in the changelog, and actually see the file you clicked on (which does not work without such a patch). > when using svn, links are wrong > --- > > Key: MCHANGELOG-16 > URL: http://jira.codehaus.org/browse/MCHANGELOG-16 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 >Reporter: Julian Wood >Priority: Minor > Attachments: MCHANGELOG-16.patch, test.zip > > > Here's my setup: > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk > > ... > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-beta-2-SNAPSHOT > > > changes > > > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= > range > 90 > > > changelog > file-activity > dev-activity > > > > > With that displayFileDetailUrl, I get links like this in the resultant > changelog in my site: > http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= > but it should be like this: > link = > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- 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] Reopened: (MCHANGELOG-16) when using svn, links are wrong
[ http://jira.codehaus.org/browse/MCHANGELOG-16?page=all ] Julian Wood reopened MCHANGELOG-16: --- The issue is still at large. You should be able to click on a link in your changelog and have it show the file in your web presentation system. Currently, this does not work. > when using svn, links are wrong > --- > > Key: MCHANGELOG-16 > URL: http://jira.codehaus.org/browse/MCHANGELOG-16 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 >Reporter: Julian Wood >Priority: Minor > Attachments: MCHANGELOG-16.patch, test.zip > > > Here's my setup: > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk > > ... > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-beta-2-SNAPSHOT > > > changes > > > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= > range > 90 > > > changelog > file-activity > dev-activity > > > > > With that displayFileDetailUrl, I get links like this in the resultant > changelog in my site: > http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= > but it should be like this: > link = > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- 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: (MCHANGELOG-16) when using svn, links are wrong
[ http://jira.codehaus.org/browse/MCHANGELOG-16?page=comments#action_77650 ] Dennis Lundberg commented on MCHANGELOG-16: --- Hi Julian Glad your're still with us. 1. Well then, now we have something more to go on. I agree that such a presentation system is worth supporting. That was not apparent in the original report though. Ideally I would like to do something similar to the changes plugin where you can configure a pattern for displayFileDetailUrl with special markers for "file" and "revision" so that you could use: http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=%REVISION%&sc=0&path=%FILE% But that I think that requires a lot of plumbing to be replaced. So I would like to wait with such a feature until the next version (2.1) of the plugin. 2. The "if cluse" that is added by the patch hijacks all SVN SCM connections resulting in, at least the ones using viewvc not working properly. For the time being the "if clause" solution is the way to go, until something similar to 1. is implemented, but it has to be transparent to other systems. Is there a distinct signature in URLs for websvn that we can use to check against? > when using svn, links are wrong > --- > > Key: MCHANGELOG-16 > URL: http://jira.codehaus.org/browse/MCHANGELOG-16 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 >Reporter: Julian Wood >Priority: Minor > Attachments: MCHANGELOG-16.patch, test.zip > > > Here's my setup: > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk > > ... > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-beta-2-SNAPSHOT > > > changes > > > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= > range > 90 > > > changelog > file-activity > dev-activity > > > > > With that displayFileDetailUrl, I get links like this in the resultant > changelog in my site: > http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= > but it should be like this: > link = > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- 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-958) Errors on accessing webapp
Errors on accessing webapp -- Key: CONTINUUM-958 URL: http://jira.codehaus.org/browse/CONTINUUM-958 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Rahul Thakur Looks like there has been a change in Plexus Security Policy module (SingleSignOnSettings). Webapp throws ComponentCreationException. This is becase a 'cookieDomain' property has been moved out of the DefaultSingleSignOnSetting impl. -- 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: (CONTINUUM-958) Errors on accessing webapp
[ http://jira.codehaus.org/browse/CONTINUUM-958?page=all ] Rahul Thakur updated CONTINUUM-958: --- Attachment: CONTINUUM-958.patch o Commented out 'cookieDomain' property configuration o updated Plexus Container snapshot version to '1.0-alpha-11-SNAPSHOT' > Errors on accessing webapp > -- > > Key: CONTINUUM-958 > URL: http://jira.codehaus.org/browse/CONTINUUM-958 > Project: Continuum > Issue Type: Bug > Components: Web interface >Reporter: Rahul Thakur > Attachments: CONTINUUM-958.patch > > > Looks like there has been a change in Plexus Security Policy module > (SingleSignOnSettings). Webapp throws ComponentCreationException. This is > becase a 'cookieDomain' property has been moved out of the > DefaultSingleSignOnSetting impl. -- 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: (MCHANGELOG-16) when using svn, links are wrong
[ http://jira.codehaus.org/browse/MCHANGELOG-16?page=comments#action_77666 ] Julian Wood commented on MCHANGELOG-16: --- I've linked to the original report. As I remember, we patched, then Maven changed somewhat substantially, which broke this patch, and so we patched again. That's what this report is (was) about. I think you're looking for the original report. As for distinct signatures, I don't really think there is one, but I also don't think that's necessary. The developer should simply be able to choose what URL they would like to use in order to present files out of their chosen scm. There's no reason why it should break any system at all. I think the original patch was designed to simply see if the displayFileDetailURL had been set, and only do something if it had. If it wasn't doing that, then there is a bug in the patch, which should be trivial to fix. That is a possible way forward. BTW your suggestion about the parallel with changes is exactly right. Thanks, J > when using svn, links are wrong > --- > > Key: MCHANGELOG-16 > URL: http://jira.codehaus.org/browse/MCHANGELOG-16 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 >Reporter: Julian Wood >Priority: Minor > Attachments: MCHANGELOG-16.patch, test.zip > > > Here's my setup: > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk > > ... > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-beta-2-SNAPSHOT > > > changes > > > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= > range > 90 > > > changelog > file-activity > dev-activity > > > > > With that displayFileDetailUrl, I get links like this in the resultant > changelog in my site: > http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= > but it should be like this: > link = > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- 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
