[jira] Closed: (MJAVADOC-184) Unable to differentiate JavaDoc reports when using multiple doclets
[
http://jira.codehaus.org/browse/MJAVADOC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-184.
Resolution: Not A Bug
Like I said, you need to add name and description parameters, similar to the
following:
{noformat}
jDoc1
javadoc
jdoc1
jdoc1
jdoc2
en_US
apidocs2
jdoc2
jdoc2
javadoc
{noformat}
> Unable to differentiate JavaDoc reports when using multiple doclets
> ---
>
> Key: MJAVADOC-184
> URL: http://jira.codehaus.org/browse/MJAVADOC-184
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Anthony Whitford
> Attachments: MJAVADOC-184 result.jpg, my-app.zip
>
>
> If you configure the javadoc plugin with a reportSet using 2 doclets (like
> the YDoc doclet, and the PDF doclet, for example), both reports appear on
> projects-reports.html with the same Document and Description. There is
> presently no way to differentiate them.
> I think a reasonable solution is to have the ability to overwrite the
> Document and Description for the generated reports page, so that I can label
> the PDF version as such.
--
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-184) Unable to differentiate JavaDoc reports when using multiple doclets
[ http://jira.codehaus.org/browse/MJAVADOC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-184: - Attachment: MJAVADOC-184 result.jpg > Unable to differentiate JavaDoc reports when using multiple doclets > --- > > Key: MJAVADOC-184 > URL: http://jira.codehaus.org/browse/MJAVADOC-184 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Anthony Whitford > Attachments: MJAVADOC-184 result.jpg, my-app.zip > > > If you configure the javadoc plugin with a reportSet using 2 doclets (like > the YDoc doclet, and the PDF doclet, for example), both reports appear on > projects-reports.html with the same Document and Description. There is > presently no way to differentiate them. > I think a reasonable solution is to have the ability to overwrite the > Document and Description for the generated reports page, so that I can label > the PDF version as such. -- 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-184) Unable to differentiate JavaDoc reports when using multiple doclets
[ http://jira.codehaus.org/browse/MJAVADOC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-184: - Attachment: MJAVADOC-184 result.jpg > Unable to differentiate JavaDoc reports when using multiple doclets > --- > > Key: MJAVADOC-184 > URL: http://jira.codehaus.org/browse/MJAVADOC-184 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Anthony Whitford > Attachments: MJAVADOC-184 result.jpg, my-app.zip > > > If you configure the javadoc plugin with a reportSet using 2 doclets (like > the YDoc doclet, and the PDF doclet, for example), both reports appear on > projects-reports.html with the same Document and Description. There is > presently no way to differentiate them. > I think a reasonable solution is to have the ability to overwrite the > Document and Description for the generated reports page, so that I can label > the PDF version as such. -- 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-184) Unable to differentiate JavaDoc reports when using multiple doclets
[ http://jira.codehaus.org/browse/MJAVADOC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-184: - Attachment: (was: MJAVADOC-184 result.jpg) > Unable to differentiate JavaDoc reports when using multiple doclets > --- > > Key: MJAVADOC-184 > URL: http://jira.codehaus.org/browse/MJAVADOC-184 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Anthony Whitford > Attachments: MJAVADOC-184 result.jpg, my-app.zip > > > If you configure the javadoc plugin with a reportSet using 2 doclets (like > the YDoc doclet, and the PDF doclet, for example), both reports appear on > projects-reports.html with the same Document and Description. There is > presently no way to differentiate them. > I think a reasonable solution is to have the ability to overwrite the > Document and Description for the generated reports page, so that I can label > the PDF version as such. -- 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: (MJAVADOC-163) excludePAckageNAmes don't work with antlr plugin
[ http://jira.codehaus.org/browse/MJAVADOC-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-163. Resolution: Cannot Reproduce Without any responses from you, we cant work on this issue, so I close it. > excludePAckageNAmes don't work with antlr plugin > > > Key: MJAVADOC-163 > URL: http://jira.codehaus.org/browse/MJAVADOC-163 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: maven 2.0.8 > jdk 1.5.14 >Reporter: Claudio D'Angelo >Priority: Minor > Attachments: pom.xml > > > In my pom is configurated antlr plugin. > When i start javadoc:javadoc the javadoc plugin documents all package althouh > the excludePackageNames is configurated. > If i comment the antlr plugin javadoc work correctly. > In attachment my pom -- 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: (MJAVADOC-126) Add the ability to load the stylesheet from a jar (resource)
[ http://jira.codehaus.org/browse/MJAVADOC-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-126. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.5 Fixed in r662003, snapshot deployed. Thanks! > Add the ability to load the stylesheet from a jar (resource) > > > Key: MJAVADOC-126 > URL: http://jira.codehaus.org/browse/MJAVADOC-126 > Project: Maven 2.x Javadoc Plugin > Issue Type: Wish >Affects Versions: 2.2 >Reporter: Julien S >Assignee: Vincent Siveton >Priority: Minor > Fix For: 2.5 > > Attachments: > 20080520-maven-javadoc-plugin-external-resources-integration-tests.zip, > 20080520-maven-javadoc-plugin-external-resources.patch, > 20080530-maven-javadoc-plugin-external-resources-integration-tests.zip, > 20080530-maven-javadoc-plugin-external-resources.patch > > > Currently, the stylesheetfile has to be given as a path on the filesystem, > which makes sharing quite difficult. > It would be nice to be able to retrieve it from a jar (like the checkstyle > and the pmd plugins). -- 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: (MJAVADOC-140) test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool
[
http://jira.codehaus.org/browse/MJAVADOC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-140.
Resolution: Cannot Reproduce
I cannot reproduce it in 2.4 and 2.5-SNAPSHOT
> test-javadoc run in aggregate mode does not pass correct classpath to javadoc
> tool
> --
>
> Key: MJAVADOC-140
> URL: http://jira.codehaus.org/browse/MJAVADOC-140
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: John Allen
>Priority: Blocker
>
> compare - local build of test-javadoc for a project:
> {code}
> -classpath
> 'D:/APT/projects/apt-examples/calculator/calculator-engine/target/classes;
> D:/APT/projects/apt-examples/calculator/calculator-engine/target/test-classes;
> D:/PROFILES/allenj4/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar'
> -protected
> -sourcepath
> 'D:/APT/projects/apt-examples/calculator/calculator-engine/src/test/java'
> -author
> -charset
> 'ISO-8859-1'
> -d
> 'D:/APT/projects/apt-examples/calculator/calculator-engine/target/site/testapidocs'
> -doctitle
> 'Calculator Engine 1.1-SNAPSHOT Test API'
> -linkoffline
> 'http://java.sun.com/j2se/1.4.2/docs/api' null
> -use
> -version
> -windowtitle
> 'Calculator Engine 1.1-SNAPSHOT Test API'
> {code}
> with the one produced at the root project. It obviously contains many more
> classpath details but critically you'll see junit JAR
> {code}
> -classpath
> 'D:/APT/projects/apt-examples/calculator/calculator-root/target/classes;
> D:/APT/projects/apt-examples/calculator/calculator-root/target/test-classes;
> D:/APT/projects/apt-examples/calculator/calculator-skin/target/classes;
> D:/APT/projects/apt-examples/calculator/calculator-skin/target/test-classes;
> D:/APT/projects/apt-examples/calculator/calculator-engine/target/classes;
> D:/APT/projects/apt-examples/calculator/calculator-engine/target/test-classes;
> D:/APT/projects/apt-examples/calculator/calculator-ejb/target/classes;
> D:/APT/projects/apt-examples/calculator/calculator-ejb/target/test-classes;
> D:/APT/projects/apt-examples/calculator/calculator-servlets/target/classes;
> D:/APT/projects/apt-examples/calculator/calculator-servlets/target/test-classes;
> D:/APT/projects/apt-examples/calculator/calculator-webapp/target/classes;
> D:/APT/projects/apt-examples/calculator/calculator-webapp/target/test-classes;
> D:/APT/projects/apt-examples/calculator/calculator-ear/target/classes;
> D:/APT/projects/apt-examples/calculator/calculator-ear/target/test-classes;
> D:/PROFILES/allenj4/.m2/repository/com/fujitsu/fs/apt/examples/calculator/calculator-ejb/1.1-SNAPSHOT/calculator-ejb-1.1-SNAPSHOT.jar;
> D:/PROFILES/allenj4/.m2/repository/com/fujitsu/fs/apt/examples/calculator/calculator-servlets/1.1-SNAPSHOT/calculator-servlets-1.1-SNAPSHOT.jar;
> D:/PROFILES/allenj4/.m2/repository/com/fujitsu/fs/apt/examples/calculator/calculator-ejb/1.1-SNAPSHOT/calculator-ejb-1.1-SNAPSHOT-client.jar;
> D:/PROFILES/allenj4/.m2/repository/javax/j2ee/j2ee/1.4/j2ee-1.4.jar;
> D:/PROFILES/allenj4/.m2/repository/tomcat/jasper-runtime/5.5.12/jasper-runtime-5.5.12.jar;
> D:/PROFILES/allenj4/.m2/repository/com/fujitsu/fs/apt/examples/calculator/calculator-engine/1.1-SNAPSHOT/calculator-engine-1.1-SNAPSHOT.jar'
> -protected
> -sourcepath
> 'D:/APT/projects/apt-examples/calculator/calculator-engine/src/test/java'
> -author
> -charset
> 'ISO-8859-1'
> -d
> 'D:/APT/projects/apt-examples/calculator/calculator-root/target/site/testapidocs'
> -doctitle
> 'Calculator 1.1-SNAPSHOT Test API'
> -linkoffline
> 'http://java.sun.com/j2se/1.4.2/docs/api' null
> -use
> -version
> -windowtitle
> 'Calculator 1.1-SNAPSHOT Test API'
> {code}
> Which of course gives us:
> {code}
> [INFO] Javadoc Warnings
> [WARNING]
> D:\APT\projects\apt-examples\calculator\calculator-engine\src\test\java\com\fujitsu\calculator\engine\CalculatorTest.java:6:
> package junit.framework does not exist
> [WARNING] import junit.framework.TestCase;
> [WARNING] ^
> [WARNING]
> D:\APT\projects\apt-examples\calculator\calculator-engine\src\test\java\com\fujitsu\calculator\engine\CalculatorTest.java:13:
> cannot find symbol
> [WARNING] symbol: class TestCase
> [WARNING] extends TestCase
> [WARNING] ^
> {code}
--
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: (MJAVADOC-138) javadoc:test-javadoc failed if target/classes not already created
[
http://jira.codehaus.org/browse/MJAVADOC-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-138.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.5
Should be closed by MJAVADOC-168
> javadoc:test-javadoc failed if target/classes not already created
> -
>
> Key: MJAVADOC-138
> URL: http://jira.codehaus.org/browse/MJAVADOC-138
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Vincent Siveton
>Assignee: Vincent Siveton
> Fix For: 2.5
>
>
> Using
> {noformat}
> mvn clean javadoc:test-javadoc
> {noformat}
> it could produce unsuccessful build or warning (depending the javadoc version
> used, i.e 1.4 vs 1.5)
> The options file contains:
> {noformat}
> -classpath '[SNIP]/target/classes;[SNIP]/target/tests-classes;...'
> {noformat}
> The explanation is that no target\classes was created before executing
> test-javadoc
--
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: (MSITE-242) remove copy of plexus-utils sources from site plugin sources since it is a dependency
[ http://jira.codehaus.org/browse/MSITE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136896#action_136896 ] Dennis Lundberg commented on MSITE-242: --- Beacuse of MSITE-332, and the fix for PLXUTILS-60 in r662007, we need to depend on plexus-utils-1.5 or newer. > remove copy of plexus-utils sources from site plugin sources since it is a > dependency > - > > Key: MSITE-242 > URL: http://jira.codehaus.org/browse/MSITE-242 > Project: Maven 2.x Site Plugin > Issue Type: Task >Affects Versions: 2.0-beta-6 >Reporter: Herve Boutemy >Assignee: Dennis Lundberg > Fix For: 2.0-beta-8 > > > the dependency has been uncommented, but the source code copy hasn't been > removed > classes copied are: > - o.c.p.u.cli > - o.c.p.u.interpolation > - o.c.p.u.introspection > - o.c.p.u.xml (partial: XML encoding support) -- 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: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSITE-332.
-
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.0-beta-7
I've incorporated the fix for PLXUTILS-60 into the site plugin and deployed a
new 2.0-beta-7-SNAPSHOT.
Can you please verify that things are working for you now?
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> ... 20 more
> Caused by: java.io.UnsupportedEncodingException: ${OUTPUTENCODING}
> at sun.io.Converters.getConverterClass(Converters.java:218)
> at sun.io.Converters.newConverter(Converters.java:251)
> at
> sun.io.ByteToCharConverter.getConverter(ByteToCha
[jira] Closed: (MJAVADOC-106) Dependencies with scope "runtime" or "provided" are not used in the javadoc classpath
[ http://jira.codehaus.org/browse/MJAVADOC-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-106. Resolution: Cannot Reproduce I tried the test zip and changed the scope of junit to provided. The build is successful with 2.4 and 2.5-SNAPSHOT. > Dependencies with scope "runtime" or "provided" are not used in the javadoc > classpath > - > > Key: MJAVADOC-106 > URL: http://jira.codehaus.org/browse/MJAVADOC-106 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Christophe DENEUX > Attachments: javadocBug.zip > > > Hi, > I have a class inherited from an hibernate class. So my project contains a > dependency onto Hibernate with the default scope, and an other dependencies > needed by Hibernate with scope=runtime and/or provided. > My javadoc plugin is configured to use the doclet Umlgraph. > At the report generation I have an error telling that classes are not found. > These classes are contained in dependencies with scope=runtime/provided. If I > change the scope to compile, that works fine. > After investigation in the source code, it seems to me that only dependencies > with scope=compile are used. > Can you take into account dependencies with scope=runtime/provided, or > propose configuration parameters to set these artifacts. > Christophe DENEUX > Capgemini Sud - France - 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] Closed: (MJAVADOC-99) No java doc generated for package jboss-sar
[ http://jira.codehaus.org/browse/MJAVADOC-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-99. --- Resolution: Cannot Reproduce Cannot reproduce it in 2.5-SNAPSHOT > No java doc generated for package jboss-sar > --- > > Key: MJAVADOC-99 > URL: http://jira.codehaus.org/browse/MJAVADOC-99 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement > Environment: Maven version: 2.0.4 >Reporter: Weiwen Chen > > Package: > jboss-sar > Plugin: > true > com.hp.ov.nms.codehaus > jboss-packaging-maven-plugin > 2.0 > Build errors: > [INFO] [javadoc:javadoc] > [INFO] Not executing Javadoc as the project is not a Java > classpath-capable package > No java doc is generated for this 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] Closed: (MNG-3581) stage:copy ClassCastException with maven 2.0.9
[ http://jira.codehaus.org/browse/MNG-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3581. - Resolution: Fixed > stage:copy ClassCastException with maven 2.0.9 > -- > > Key: MNG-3581 > URL: http://jira.codehaus.org/browse/MNG-3581 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 > Environment: tested on cygwin and freebsd >Reporter: Olivier Lamy >Assignee: Brett Porter >Priority: Blocker > Fix For: 2.0.10 > > > Using stage:copy with maven 2.0.9 generates a ClassCastException. (works fine > with 2.0.8) > The relevant part of the log say : > [INFO] > > [INFO] org.apache.maven.wagon.providers.ssh.jsch.ScpWagon > [INFO] > > [DEBUG] Trace > java.lang.ClassCastException: > org.apache.maven.wagon.providers.ssh.jsch.ScpWagon > at > org.apache.maven.plugins.stage.DefaultRepositoryCopier.copy(DefaultRepositoryCopier.java:252) > at > org.apache.maven.plugins.stage.CopyRepositoryMojo.execute(CopyRepositoryMojo.java:93) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecuto > > See > http://www.nabble.com/stage%3Acopy-ClassCastException-with-maven-2.0.9-to17292204.html > I add this issue in MNG as it looks more a core issue than a stage plugin > issue. -- 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-3608) Reporting Encoding Configuration: ${project.reporting.outputEncoding}
Reporting Encoding Configuration: ${project.reporting.outputEncoding}
--
Key: MNG-3608
URL: http://jira.codehaus.org/browse/MNG-3608
Project: Maven 2
Issue Type: Sub-task
Reporter: Herve Boutemy
see [Reporting Encoding Configuration
proposalhttp://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration]
--
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: (MNG-3608) Reporting Encoding Configuration: ${project.reporting.outputEncoding}
[
http://jira.codehaus.org/browse/MNG-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-3608:
---
Description: see [Reporting Encoding Configuration
proposal|http://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration]
(was: see [Reporting Encoding Configuration
proposalhttp://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration])
> Reporting Encoding Configuration: ${project.reporting.outputEncoding}
> --
>
> Key: MNG-3608
> URL: http://jira.codehaus.org/browse/MNG-3608
> Project: Maven 2
> Issue Type: Sub-task
>Reporter: Herve Boutemy
>
> see [Reporting Encoding Configuration
> proposal|http://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration]
--
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-111) Announcement Mojo doesn't respect Jira authentication settings
[ http://jira.codehaus.org/browse/MCHANGES-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Basil James Whitehouse III updated MCHANGES-111: Attachment: MCHANGES-111.patch Patch for accessing a JIRA instance that requires authentication, mostly following what was done in the JiraMojo. > Announcement Mojo doesn't respect Jira authentication settings > -- > > Key: MCHANGES-111 > URL: http://jira.codehaus.org/browse/MCHANGES-111 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: announcement >Affects Versions: 2.0 >Reporter: Michael Johns > Attachments: MCHANGES-111.patch > > > The announcement mojo doesn't respect the Jira authentication settings > (jiraUser and jiraPassword). It instantiates a JiraDownloader but never > applies these settings. It should do something like JiraMojo, which calls > setJiraDownloaderParameters() to make sure all values are set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHECKSTYLE-63) The local absolute path to the headerLocation file is output in the report
[ http://jira.codehaus.org/browse/MCHECKSTYLE-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-63. -- Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.2 Fixed in r662065. > The local absolute path to the headerLocation file is output in the report > -- > > Key: MCHECKSTYLE-63 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-63 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.2 > > > When using maven_checks.xml (and possibly others as well) the fully expanded > value of the headerLocation parameter is output in the report. In my case it > looks like this in the "Rules summary" section, when I have run "mvn site" > for the maven-checkstyle-plugin: > RegexpHeader > * headerFile: > "G:\apache\maven\plugins\trunk\maven-checkstyle-plugin\target\checkstyle-header.txt" > This is not only very long, it might be so long that the page is wider thatn > the screen, it is also not something that one want's to show to the world. > The value that is put in the report should be whatever is in the > configuration section of the plugin. -- 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: (MAVENUPLOAD-2076) Upload jSDP 1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2076. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload jSDP 1.1 > --- > > Key: MAVENUPLOAD-2076 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2076 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Claudio Di Vita >Assignee: Carlos Sanchez > Attachments: jsdp-info.txt > > > jSDP is a Java library that enable users to manipulate SDP messages. > I'm the developer of jSDP, please upload its artifacts. -- 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: (MAVENUPLOAD-2078) Adding Atlassian central repository sync
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2078. --- Assignee: Carlos Sanchez Resolution: Fixed not sure i should trust this people ;) > Adding Atlassian central repository sync > > > Key: MAVENUPLOAD-2078 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2078 > Project: Maven Upload Requests > Issue Type: Improvement >Reporter: James William Dumay >Assignee: Carlos Sanchez > > Hey guys, > I would like to add our central synchronization repository to the automatic > setup. > In accordance with the rules, this repository contains no snapshot releases. > Here is our details setup in CSV: > "com.atlassian","[EMAIL PROTECTED]:/home/maven/incoming/","rsync_ssh","James > William Dumay","[EMAIL PROTECTED]",, > "com.cenqua","[EMAIL PROTECTED]:/home/maven/incoming/","rsync_ssh","James > William Dumay","[EMAIL PROTECTED]",, > For verification of the com.cenqua groupId you may or may have not noticed > that Atlassian recently aquired Cenqua. > See the following URL for more information: > http://blogs.atlassian.com/news/2007/08/welcome_cenqua.html > Thanks > James -- 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: (MAVENUPLOAD-2081) grails-maven-plugin 0.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136915#action_136915 ] Carlos Sanchez commented on MAVENUPLOAD-2081: - can you guys setup a sync repo at apache/sf/... and just add it to https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv > grails-maven-plugin 0.3 > --- > > Key: MAVENUPLOAD-2081 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2081 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Trygve Laugstol > > The upload bundles was created by me from: > http://forge.octo.com/archiva/browse/com.octo.mtg/grails-maven-plugin/0.3 > I'm a developer on the project, see -- 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: (MAVENUPLOAD-2085) rsync_ssh request for yac-io.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2085. --- Assignee: Carlos Sanchez Resolution: Fixed > rsync_ssh request for yac-io.sourceforge.net > > > Key: MAVENUPLOAD-2085 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2085 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Kenji Tayama >Assignee: Carlos Sanchez > > "org.apache.maven","[EMAIL > PROTECTED]:/home/groups/y/ya/yac-io/htdocs/m2repo/release","rsync_ssh","Kenji > Tayama","[EMAIL PROTECTED]",, -- 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: (MAVENUPLOAD-2075) upload jgraph 5.10.2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136916#action_136916 ] Carlos Sanchez commented on MAVENUPLOAD-2075: - you need to follow the instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > upload jgraph 5.10.2.0 > -- > > Key: MAVENUPLOAD-2075 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2075 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: David Delbecq > > Please upload jgraph 5.10.2.0, and, optionnally, it's source package. JGraph > is, unfortunately, not build using maven. However, it's quite usefull in a > broad range of app. net.sf.jped:2.0 was uploaded to central maven repo 2 days > ago, and we didn't notice that broken dependency (was available locally > during build). putting 5.10.2.0 of jgraph in central repository would solve > this broken dependency. > group ID: jgraph > artifact ID: jgraph > The groupId already exist in central repo with older versions of jgraph. -- 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: (MAVENUPLOAD-2070) rsync_ssh request for caelum-stella.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2070. --- Resolution: Fixed > rsync_ssh request for caelum-stella.sourceforge.net > --- > > Key: MAVENUPLOAD-2070 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2070 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Cauê Haucke Porta Guerra >Assignee: Carlos Sanchez > > "net.sf.caelum-stella","[EMAIL > PROTECTED]:/home/groups/c/ca/caelum-stella/htdocs/m2repo","rsync_ssh","Caue > Guerra","[EMAIL PROTECTED]",, > Project page generated by maven hosted at project domain: > http://stella.caelum.com.br/dev/team-list.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: (MAVENUPLOAD-2049) plexian-1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2049. --- Assignee: Carlos Sanchez Resolution: Incomplete > plexian-1.1 > --- > > Key: MAVENUPLOAD-2049 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2049 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Alexander Schwid >Assignee: Carlos Sanchez > Attachments: plexian-core-1.1-bundle.jar, > plexian-indexator-1.1-bundle.jar > > > http://schwid.com/plexian/plexian-core-1.1-bundle.jar > http://schwid.com/plexian/plexian-indexator-1.1-bundle.jar > http://plexian.sourceforge.net > I'm a developer in plexian, please upload! -- 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: (MAVENUPLOAD-2071) rsync_ssh request for seleniumdsl.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2071. --- Resolution: Fixed > rsync_ssh request for seleniumdsl.sourceforge.net > - > > Key: MAVENUPLOAD-2071 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2071 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Cauê Haucke Porta Guerra >Assignee: Carlos Sanchez > > "net.sf.seleniumdsl","[EMAIL > PROTECTED]:/home/groups/s/se/seleniumdsl/htdocs/m2repo","rsync_ssh","Caue > Guerra","[EMAIL PROTECTED]",, > Project page generated by maven hosted at project domain: > http://seleniumdsl.sourceforge.net/team-list.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: (MAVENUPLOAD-2077) Upload Request for fixedformat4j
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2077. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload Request for fixedformat4j > > > Key: MAVENUPLOAD-2077 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2077 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jacob von Eyben >Assignee: Carlos Sanchez > > Bundles: > http://fixedformat4j.googlecode.com/files/fixedformat4j-1.0.0-bundle.jar > http://fixedformat4j.googlecode.com/files/fixedformat4j-1.1.0-bundle.jar > Authentication: > http://fixedformat4j.ancientprogramming.com/ > http://fixedformat4j.ancientprogramming.com/team-list.html > I'm a developer on fixedformat4j, and want to use the com.ancientprogramming > groupId > I own ancientprogramming.com domain, you can see my name on the blog at > www.ancientprogramming.com -- 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: (MAVENUPLOAD-2083) Upload Request for fixedformat4j - version 1.1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2083. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload Request for fixedformat4j - version 1.1.1 > > > Key: MAVENUPLOAD-2083 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2083 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jacob von Eyben >Assignee: Carlos Sanchez > > http://fixedformat4j.googlecode.com/files/fixedformat4j-1.1.1-bundle.jar > http://fixedformat4j.ancientprogramming.com/ > http://fixedformat4j.ancientprogramming.com/team-list.html > I'm a developer on fixedformat4j, please upload! -- 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: (MAVENUPLOAD-2082) SubEtha SMTP 2.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136918#action_136918 ] Carlos Sanchez commented on MAVENUPLOAD-2082: - Retrieving URL: 'http://spatium/artifactory/repo/org/subethamail/subethasmtp/2.0.1/subethasmtp-2.0.1-bundle.jar' --20:15:20-- http://spatium/artifactory/repo/org/subethamail/subethasmtp/2.0.1/subethasmtp-2.0.1-bundle.jar => `subethasmtp-2.0.1-bundle.jar' Resolving spatium... failed: Name or service not known. > SubEtha SMTP 2.0.1 > -- > > Key: MAVENUPLOAD-2082 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2082 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Geoffrey Wiseman > > http://spatium/artifactory/repo/org/subethamail/subethasmtp/2.0.1/subethasmtp-2.0.1-bundle.jar > http://subethasmtp.tigris.org/ > I'm not a member of the subetha team, although I do have their blessing to > send this up (http://subethasmtp.tigris.org/issues/show_bug.cgi?id=11). -- 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: (MAVENUPLOAD-2086) Upload latest version of JFlex.de (1.4.2)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2086. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload latest version of JFlex.de (1.4.2) > - > > Key: MAVENUPLOAD-2086 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2086 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Régis Décamps >Assignee: Carlos Sanchez > > JFlex is a parser generator. Given a grammar, JFlex generate Java (TM) code > to parse documents that follow this grammar. > Central repo contains 1.4.1. > Version 1.4.2 released May 28. -- 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: (MAVENUPLOAD-2079) Uploading jbossall-client-4.0.5GA.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136917#action_136917 ] Carlos Sanchez commented on MAVENUPLOAD-2079: - I could copy it from http://repository.jboss.com/maven2/ if you find what needs to be copied > Uploading jbossall-client-4.0.5GA.jar > - > > Key: MAVENUPLOAD-2079 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2079 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Sathish Kumar > > Hi, >I am using the maven repository http://repo1.maven.org as primary > repository. I want to use the 4.0.5GA version of jbossall-client.jar. It is > not present in above mentioned repository. But it is present in the following > url http://www.andromda.org/maven2/org/jboss/jbossall-client/4.0.5-GA/. > Please, Can you upload this version jar to http://repo1.maven.org > repository. > Thanks, > P.Sathish Kumar -- 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: (MAVENUPLOAD-1968) JDom 1.1 is out
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136919#action_136919 ] Carlos Sanchez commented on MAVENUPLOAD-1968: - what do the "JDOM originally shipped with..." messages mean? > JDom 1.1 is out > --- > > Key: MAVENUPLOAD-1968 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1968 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Mirko Steinle >Assignee: Carlos Sanchez > Attachments: jdom-1.1-bundle.jar, pom-relocation.xml > > > Hello! > JDom has released a major version (1.1) last november. Could you please > upload it? > All files can be found at http://www.jdom.org/ > Thank you very much. > Mirko > P.S. I am only a user of JDom, but I guess the team won't have anything > against seeing their latest release uploaded... -- 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: (MAVENUPLOAD-2084) FitNesse and FitLibrary 20070619
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2084. --- Assignee: Carlos Sanchez Resolution: Fixed > FitNesse and FitLibrary 20070619 > > > Key: MAVENUPLOAD-2084 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2084 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pål Brattberg >Assignee: Carlos Sanchez > > FitNesse is a fully integrated standalone wiki and acceptance testing > framework using FIT. > FitLibrary is an extension for FIT/FitNesse > I'm not a developer of FitNesse, but I am for DbFit which is dependant on > FitNesse. > The official JAR's are found at: http://www.fitnesse.org/FitNesse.DownLoad > The JAR's packaged for Maven (with POM) are found at: > http://www.palbrattberg.com/wp-content/uploads/2008/05/30/fitnesse-20070619-bundle.jar > http://www.palbrattberg.com/wp-content/uploads/2008/05/30/fitlibrary-20070619-bundle.jar -- 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: (WAGON-217) dav:http:// and dav:https:// do not conform to URI spec
[ http://jira.codehaus.org/browse/WAGON-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136922#action_136922 ] Joakim Erdfelt commented on WAGON-217: -- Note: the existing protocols of dav:http:// and dav:https:// are still in place, this change is backward compatible. It merely adds more protocol prefixes that WebdavWagon wlil respond to. This should ease the integration points for wagon. These extra protocols should also reduce the number of incidents of issues and support requests around using webdav with wagon. > dav:http:// and dav:https:// do not conform to URI spec > --- > > Key: WAGON-217 > URL: http://jira.codehaus.org/browse/WAGON-217 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-webdav >Reporter: Joakim Erdfelt >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > The dav:http:// and dav:https:// protocol "prefix" defined for wagon-webdav > does not conform to the URI spec. > This adds a layer of extra work for wagon integrators. > Proposal: > * Add more mappings to the WebdavWagon to allow use of protocols that conform > to the URI spec. > Existing Protocols > * dav:http:// = http:// > * dav:https:// = https:// > > New Mappings > * dav:// = http:// > * davs:// = https:// > * dav+http:// = http:// > * dav+https:// = https:// -- 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: (WAGON-217) dav:http:// and dav:https:// do not conform to URI spec
[ http://jira.codehaus.org/browse/WAGON-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed WAGON-217. Resolution: Fixed Fix Version/s: 1.0-beta-3 Work completed on revision: 662092 > dav:http:// and dav:https:// do not conform to URI spec > --- > > Key: WAGON-217 > URL: http://jira.codehaus.org/browse/WAGON-217 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-webdav >Reporter: Joakim Erdfelt >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > The dav:http:// and dav:https:// protocol "prefix" defined for wagon-webdav > does not conform to the URI spec. > This adds a layer of extra work for wagon integrators. > Proposal: > * Add more mappings to the WebdavWagon to allow use of protocols that conform > to the URI spec. > Existing Protocols > * dav:http:// = http:// > * dav:https:// = https:// > > New Mappings > * dav:// = http:// > * davs:// = https:// > * dav+http:// = http:// > * dav+https:// = https:// -- 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: (WAGON-217) dav:http:// and dav:https:// do not conform to URI spec
dav:http:// and dav:https:// do not conform to URI spec --- Key: WAGON-217 URL: http://jira.codehaus.org/browse/WAGON-217 Project: Maven Wagon Issue Type: New Feature Components: wagon-webdav Reporter: Joakim Erdfelt The dav:http:// and dav:https:// protocol "prefix" defined for wagon-webdav does not conform to the URI spec. This adds a layer of extra work for wagon integrators. Proposal: * Add more mappings to the WebdavWagon to allow use of protocols that conform to the URI spec. Existing Protocols * dav:http:// = http:// * dav:https:// = https:// New Mappings * dav:// = http:// * davs:// = https:// * dav+http:// = http:// * dav+https:// = https:// -- 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: (WAGON-209) Extend Wagon API to support the Stage Plugin
[
http://jira.codehaus.org/browse/WAGON-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed WAGON-209.
--
Assignee: Brett Porter
Resolution: Not A Bug
Fix Version/s: (was: 1.0-beta-3)
wagon api 1.0-beta-2 already includes "CommandExecutor", the correct one to use.
> Extend Wagon API to support the Stage Plugin
>
>
> Key: WAGON-209
> URL: http://jira.codehaus.org/browse/WAGON-209
> Project: Maven Wagon
> Issue Type: New Feature
> Components: wagon-provider-api
>Affects Versions: 1.0-beta-2
>Reporter: Benjamin Bentmann
>Assignee: Brett Porter
>
> From the source of the [Maven Stage
> Plugin|http://maven.apache.org/plugins/maven-stage-plugin/]:
> {code:java}
> ( (ScpWagon) targetWagon ).executeCommand( command );
> {code}
> This smells: The plugin is downcasting to an implementation class, happily
> breaking the interface design and making the target wagon non-interchangeable.
> The atomic Wagon operations required by the plugin should be identified and
> added to the Wagon API. Wagons that can't support these new operations could
> simply implement the methods by throwing an {{UnsupportedOperationException}}
> exception.
--
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: (WAGON-218) Link Parsing in http is flawed
[ http://jira.codehaus.org/browse/WAGON-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed WAGON-218. Resolution: Fixed Work completed in revision 662070 After a sample LinkParser replacement is P.o.C. in a wagon-http-with-webdav branch, and a discussion in the [EMAIL PROTECTED] mailing list. The following changes have been made. 1) Replaced jtidy with nekohtml This resulted in a smaller dependency list and improved memory utilization. 2) Replaces reliance of String URL manipulation with use of java.net.URI This change makes the detection of content that belongs to the page more accurate, as well as enables some complex relative uri resolution almost trivial. 3) Added more unit tests for real world scenarios encountered since the original implementation was loose on the world. > Link Parsing in http is flawed > -- > > Key: WAGON-218 > URL: http://jira.codehaus.org/browse/WAGON-218 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http, wagon-http-lightweight >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Assignee: Joakim Erdfelt > > The link parsing in wagon http has a few issues. > a) not all links detected. > b) the various ways that page content is identified via url string > manipulation isn't working in many example cases. > c) the use of jtidy introduces a large dependency and high memory usage. -- 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: (WAGON-218) Link Parsing in http is flawed
Link Parsing in http is flawed -- Key: WAGON-218 URL: http://jira.codehaus.org/browse/WAGON-218 Project: Maven Wagon Issue Type: Improvement Components: wagon-http, wagon-http-lightweight Affects Versions: 1.0-beta-2 Reporter: Joakim Erdfelt The link parsing in wagon http has a few issues. a) not all links detected. b) the various ways that page content is identified via url string manipulation isn't working in many example cases. c) the use of jtidy introduces a large dependency and high memory usage. -- 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
