[jira] Created: (MAVENUPLOAD-2413) Auto Sync for jsr107cache
Auto Sync for jsr107cache - Key: MAVENUPLOAD-2413 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2413 Project: Maven Upload Requests Issue Type: Wish Reporter: Greg Luck "net.sf.jsr107cache","mavens...@web.sourceforge.net:/home/groups/e/eh/ehcache/htdocs/repository","rsync_ssh","Greg Luck","gl...@gregluck.com",, Note:net.sf.ehcache is already being synced from this same place. I am deploying jsr107cache, (being the the JSR107 APIs) there as it is a lot easier for me. I was hoping my existing sync would bring it across to the Central Repo, but that did not happen. Thus the extra line. Right now, the ehcache-jcache module cannot resolve its dependency on v1.1 of net.sf.jsr107cache. -- 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: (MSHADE-30) duplicate entry error
[ http://jira.codehaus.org/browse/MSHADE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141623#action_141623 ] Greg Luck commented on MSHADE-30: - I have the same problem. It will sometimes do a mvn package for me. But I cannot ever get install or deploy to work. I tested versions going back to the 1.0 alphas. They all have the problem. It would be really really great to get this fixed. > duplicate entry error > - > > Key: MSHADE-30 > URL: http://jira.codehaus.org/browse/MSHADE-30 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Michael Mattox > > I receive this error: > Embedded error: duplicate entry: org/apache/xmlbeans/FilterXmlObject.class > It started with a javax.xml.namespace class. So I started putting excludes, > and then I kept getting one new class after another. If I exclude everything > then I doubt my application is going to work. > I really don't understand this error. I have never seen this type of error > with the fatjar eclipse plugin. I understand it's complaining about having > the same class twice, but if it's not a problem for my eclipse project or the > maven build, why is it a problem for shade? > I feel the shade plugin should be able to handle this gracefully. -- 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-1555) Sync script for ehcache
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96430 ] Greg Luck commented on MAVENUPLOAD-1555: Note that sync was suggested by Carlos in MAVENUPLOAD-1516. > Sync script for ehcache > --- > > Key: MAVENUPLOAD-1555 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1555 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > > Hi > Following please find my script to sync ehcache. I have studied the other > scripts and believe this to be correct. Can you please set it up. > #!/bin/sh > CONTACTS="Greg Luck <[EMAIL PROTECTED]>" > MODE=rsync_ssh > [EMAIL PROTECTED]:/home/groups/e/eh/ehcache/htdocs/repository > GROUP_DIR=/net/sf/ehcache/ -- 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-1555) Sync script for ehcache
Sync script for ehcache --- Key: MAVENUPLOAD-1555 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1555 Project: maven-upload-requests Issue Type: Task Reporter: Greg Luck Hi Following please find my script to sync ehcache. I have studied the other scripts and believe this to be correct. Can you please set it up. #!/bin/sh CONTACTS="Greg Luck <[EMAIL PROTECTED]>" MODE=rsync_ssh [EMAIL PROTECTED]:/home/groups/e/eh/ehcache/htdocs/repository GROUP_DIR=/net/sf/ehcache/ -- 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-113) docletPath not working in 2.2 - Cannot find doclet class ydoc.doclets.YStandard
[ http://jira.codehaus.org/browse/MJAVADOC-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Luck closed MJAVADOC-113. -- Resolution: Fixed Fix Version/s: 2.3 Thanks guys. This is working now for my use case using 2.3-SNAPSHOT from the Apache People repo. I have changed over to it. > docletPath not working in 2.2 - Cannot find doclet class > ydoc.doclets.YStandard > --- > > Key: MJAVADOC-113 > URL: http://jira.codehaus.org/browse/MJAVADOC-113 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Greg Luck > Fix For: 2.3 > > > I have two projects which use the javadoc plugin. Ehcache and JPam. > Both started giving this error in the last few days: > [INFO] Velocity successfully started. > [INFO] [javadoc:javadoc] > [WARNING] No docletpath option was found. Please review or > or . > 1 error > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - > javadoc: error - Cannot find doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred > in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot find > doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > 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:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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: An error has > occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot > find doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > at > org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:230) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - > javadoc: error - Cannot find doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > at > org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1200) > at > org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:128) > at > org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:216) > ... 18 more > [INFO] > > [INFO] Total time: 18 seconds > [INFO] Finished a
[jira] Commented: (MJAVADOC-113) docletPath not working in 2.2 - Cannot find doclet class ydoc.doclets.YStandard
[ http://jira.codehaus.org/browse/MJAVADOC-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96331 ] Greg Luck commented on MJAVADOC-113: Hi I am trying to test this. What repository and version number do I need to use? I tried 2.3-SNAPSHOT and SNAPSHOT but neither resolved. What repo do I need? Greg > docletPath not working in 2.2 - Cannot find doclet class > ydoc.doclets.YStandard > --- > > Key: MJAVADOC-113 > URL: http://jira.codehaus.org/browse/MJAVADOC-113 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Greg Luck > > I have two projects which use the javadoc plugin. Ehcache and JPam. > Both started giving this error in the last few days: > [INFO] Velocity successfully started. > [INFO] [javadoc:javadoc] > [WARNING] No docletpath option was found. Please review or > or . > 1 error > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - > javadoc: error - Cannot find doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred > in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot find > doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > 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:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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: An error has > occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot > find doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > at > org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:230) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - > javadoc: error - Cannot find doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > at > org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1200) > at > org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:128) > at > org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:216) > ... 18 more > [INFO] > > [INFO] Total time: 18 seconds > [INFO] Finished at: Sun Feb
[jira] Created: (MAVENUPLOAD-1516) Ehcache-1.3-beta2 released
Ehcache-1.3-beta2 released -- Key: MAVENUPLOAD-1516 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1516 Project: maven-upload-requests Issue Type: Task Reporter: Greg Luck Attachments: ehcache.zip Carlos The ehcache bundle is a bit more complicated now. It has a parent and multple modules. I tried mvn repository:bundle-create. If I run it in ehcache it errors out because the parent project type is pom. If I do it in core it leaves out the parent, which of course will cause people trying to use core to fail. So it looks like this tool will only work with single module projects. The right structure gets created if I do an install. I have manually zipped that up. Does that work for you? Greg -- 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-1411) ehcache-1.3-beta release bundle
ehcache-1.3-beta release bundle --- Key: MAVENUPLOAD-1411 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1411 Project: maven-upload-requests Issue Type: Task Reporter: Greg Luck Attachments: ehcache-1.3.0-beta-bundle.jar 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: (DOXIA-99) Figures require extension in APT and they should not
[
http://jira.codehaus.org/browse/DOXIA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89274
]
Greg Luck commented on DOXIA-99:
I checked the source code. The relevant bit is
XhtmlSink#figureGraphics
/**
* @see
org.apache.maven.doxia.sink.SinkAdapter#figureGraphics(java.lang.String)
*/
public void figureGraphics( String name )
{
write( " src=\"" + name + "\"" );
}
I do not see it writing an extension. I think that might be the problem.
> Figures require extension in APT and they should not
>
>
> Key: DOXIA-99
> URL: http://jira.codehaus.org/browse/DOXIA-99
> Project: doxia
> Issue Type: Bug
>Affects Versions: 1.0-alpha-5, 1.0-alpha-6, 1.0-alpha-7, 1.0-alpha-8
>Reporter: Greg Luck
>
> Figures require extension in APT and they should not.
> For example, http://ehcache.sourceforge.net/nameandlogo.html shows a broken
> image. The APT for this page is:
> [images/ehcache_logo]
> Now, if I change it to [images/ehcache_logo.gif] it works. However this
> breaks aptconvert. The reason is that it is illegal in APT to specify the
> figure extension. I use aptconvert to create a pdf and single HTML 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: (DOXIA-99) Figures require extension in APT and they should not
Figures require extension in APT and they should not Key: DOXIA-99 URL: http://jira.codehaus.org/browse/DOXIA-99 Project: doxia Issue Type: Bug Affects Versions: 1.0-alpha-8, 1.0-alpha-7, 1.0-alpha-6, 1.0-alpha-5 Reporter: Greg Luck Figures require extension in APT and they should not. For example, http://ehcache.sourceforge.net/nameandlogo.html shows a broken image. The APT for this page is: [images/ehcache_logo] Now, if I change it to [images/ehcache_logo.gif] it works. However this breaks aptconvert. The reason is that it is illegal in APT to specify the figure extension. I use aptconvert to create a pdf and single HTML 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: (MNG-2859) Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane
Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane -- Key: MNG-2859 URL: http://jira.codehaus.org/browse/MNG-2859 Project: Maven 2 Issue Type: Bug Components: Ant tasks, Embedding Affects Versions: 2.0.5 Reporter: Greg Luck I am moving my project from Maven plus Antlib to pure Maven, maybe. Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib. Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2. But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features. I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request. The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one. Re: Ant Maven Tasks Jason van Zyl Wed, 21 Feb 2007 06:40:26 -0800 On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote: Hi, I couldn't find any info regarding the status of the ant maven tasks wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4? As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though. Jason. Cheers, Paul. -- 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-213) site:deploy to support tar gzip
site:deploy to support tar gzip --- Key: MSITE-213 URL: http://jira.codehaus.org/browse/MSITE-213 Project: Maven 2.x Site Plugin Issue Type: Wish Reporter: Greg Luck Hi I am using sourceforge to host my site. They just removed unzip. Not sure if it is coming back. Wagon relies on unzip. It would be good if it could also use gzip by creating acrhives such as are created using "tar -zcf arhive_name dir" That way it would work in more environments. Thanks Greg -- 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-113) docletPath not working in 2.2 - Cannot find doclet class ydoc.doclets.YStandard
docletPath not working in 2.2 - Cannot find doclet class ydoc.doclets.YStandard --- Key: MJAVADOC-113 URL: http://jira.codehaus.org/browse/MJAVADOC-113 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Greg Luck I have two projects which use the javadoc plugin. Ehcache and JPam. Both started giving this error in the last few days: [INFO] Velocity successfully started. [INFO] [javadoc:javadoc] [WARNING] No docletpath option was found. Please review or or . 1 error [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot find doclet class ydoc.doclets.YStandard Command line was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc -J-Xmx512m -J-Xms128m @options @packages [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot find doclet class ydoc.doclets.YStandard Command line was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc -J-Xmx512m -J-Xms128m @options @packages 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:330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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: An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot find doclet class ydoc.doclets.YStandard Command line was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc -J-Xmx512m -J-Xms128m @options @packages at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:230) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - javadoc: error - Cannot find doclet class ydoc.doclets.YStandard Command line was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc -J-Xmx512m -J-Xms128m @options @packages at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1200) at org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:128) at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:216) ... 18 more [INFO] [INFO] Total time: 18 seconds [INFO] Finished at: Sun Feb 25 09:48:18 EST 2007 [INFO] Final Memory: 9M/17M [INFO] Reverting to 2.0 by adding a version identifier of 2 fixes the problem: org.apache.maven.plugins maven-javadoc-plugin 2.0 If 2.0 works and 2.2 does not, is this a bug in 2.2 javadoc, or is it a bug in the parent project: org.apache.maven.plugins. The version in 2.2 is 4, in 2.0 it was 3. maven-plugins org.apache.maven.plugins 4
[jira] Commented: (MAVENUPLOAD-1330) jsr107cache-1.0 release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85950 ] Greg Luck commented on MAVENUPLOAD-1330: Carlos Hi. Is there a problem with this. I really need it added. Greg > jsr107cache-1.0 release > --- > > Key: MAVENUPLOAD-1330 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1330 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Attachments: jsr107cache-1.0-bundle.jar > > > jsr107cache is a place for the evolving JCACHE API so that code can be > written to the spec before final release. > ehcache, another project available under this repository has a dependency on > jsr107cache. -- 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-1330) jsr107cache-1.0 release
jsr107cache-1.0 release --- Key: MAVENUPLOAD-1330 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1330 Project: maven-upload-requests Issue Type: Task Reporter: Greg Luck Attachments: jsr107cache-1.0-bundle.jar jsr107cache is a place for the evolving JCACHE API so that code can be written to the spec before final release. ehcache, another project available under this repository has a dependency on jsr107cache. -- 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: (MAVENUPLOAD-1261) ehcache-1.2.4 released
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1261?page=all ] Greg Luck updated MAVENUPLOAD-1261: --- Attachment: ehcache-1.2.4-bundle.jar > ehcache-1.2.4 released > -- > > Key: MAVENUPLOAD-1261 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1261 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Attachments: ehcache-1.2.4-bundle.jar > > > ehcache-1.2.4 released. Attached please find the maven bundle. -- 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-1261) ehcache-1.2.4 released
ehcache-1.2.4 released -- Key: MAVENUPLOAD-1261 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1261 Project: maven-upload-requests Issue Type: Task Reporter: Greg Luck ehcache-1.2.4 released. Attached please find the maven bundle. -- 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: (MANT-21) System scope not working properly in Maven Antlib
System scope not working properly in Maven Antlib - Key: MANT-21 URL: http://jira.codehaus.org/browse/MANT-21 Project: Maven 2.x Ant Plugin Issue Type: Bug Environment: Mac OS X Reporter: Greg Luck If I add the following javax.cache jcache not_released system /Users/gluck/work/ehcache/trunk/tools/jcache.jar When I so a run I get dropping /Users/gluck/.m2/repository/javax/cache/jcache/not_released/jcache-not_released.jar from path as it doesn't exist [javac] net/sf/ehcache/jcache/CacheListenerAdaptor.java added as net/sf/ehcache/jcache/CacheListenerAdaptor.class doesn't exist. [javac] net/sf/ehcache/jcache/Entry.java added as net/sf/ehcache/jcache/Entry.class doesn't exist. [javac] net/sf/ehcache/jcache/JCache.java added as net/sf/ehcache/jcache/JCache.class doesn't exist. [javac] net/sf/ehcache/jcache/JCacheFactory.java added as net/sf/ehcache/jcache/JCacheFactory.class doesn't exist. [javac] net/sf/ehcache/jcache/package.html skipped - don't know how to handle it dropping /Users/gluck/.m2/repository/javax/cache/jcache/not_released/jcache-not_released.jar from path as it doesn't exist It should not be looking for it there. To reproduce just try and use the system scope and systemPath. -- 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: (MRM-239) OutOfMemory error when running Arhiva for days at a time
[ http://jira.codehaus.org/browse/MRM-239?page=comments#action_81258 ] Greg Luck commented on MRM-239: --- I don't have them to paste. I will update my home Maven from and leave it running to see what shows up. > OutOfMemory error when running Arhiva for days at a time > > > Key: MRM-239 > URL: http://jira.codehaus.org/browse/MRM-239 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 > Environment: Linux and Mac OS X >Reporter: Greg Luck > Fix For: 1.0-beta-1 > > > I have been running Archiva as it existed in snapshot 20 November 2006. > When running in Tomcat with the standard memory setting it fails after a few > days. > Increasing -Xmx=128m increases the time but it still gets and OutOfMemory > error after a few days. > This is with no activity. I came back today after the weekend and hit refresh > on a Pom page and it gave the OOM. It seems to be time dependent. At home I > have been running it on Mac OS X. I saw an OutOfMemory error after a week. I > did even go to a page to check it. The running console had it. > To reproduce simply run up archiva and leave it running. > We are working around with a nightly restart. -- 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: (MRM-240) File Serving does not work unless you create a proxied repository
File Serving does not work unless you create a proxied repository - Key: MRM-240 URL: http://jira.codehaus.org/browse/MRM-240 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-1 Environment: Linux Reporter: Greg Luck I created a repository but could not get Archiva to serve the files. When I created a proxy repository pointing to central it started working. I then changed the url to a nonsense URL and it kept working. In other words, Archiva will not serve files for its local repository unless at least one proxy is set up, even if the proxy is rubbish. -- 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: (MRM-239) OutOfMemory error when running Arhiva for days at a time
OutOfMemory error when running Arhiva for days at a time Key: MRM-239 URL: http://jira.codehaus.org/browse/MRM-239 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-1 Environment: Linux and Mac OS X Reporter: Greg Luck I have been running Archiva as it existed in snapshot 20 November 2006. When running in Tomcat with the standard memory setting it fails after a few days. Increasing -Xmx=128m increases the time but it still gets and OutOfMemory error after a few days. This is with no activity. I came back today after the weekend and hit refresh on a Pom page and it gave the OOM. It seems to be time dependent. At home I have been running it on Mac OS X. I saw an OutOfMemory error after a week. I did even go to a page to check it. The running console had it. To reproduce simply run up archiva and leave it running. We are working around with a nightly restart. -- 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-1248) ehcache-1.2.4RC released
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1248?page=comments#action_81140 ] Greg Luck commented on MAVENUPLOAD-1248: New version with fixed pom.xml uploaded. > ehcache-1.2.4RC released > > > Key: MAVENUPLOAD-1248 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1248 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Attachments: ehcache-1.2.4RC-bundle.jar, ehcache-1.2.4RC-bundle.jar > > > See attached. -- 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: (MAVENUPLOAD-1248) ehcache-1.2.4RC released
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1248?page=all ] Greg Luck updated MAVENUPLOAD-1248: --- Attachment: ehcache-1.2.4RC-bundle.jar > ehcache-1.2.4RC released > > > Key: MAVENUPLOAD-1248 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1248 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Attachments: ehcache-1.2.4RC-bundle.jar > > > See attached. -- 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-1248) ehcache-1.2.4RC released
ehcache-1.2.4RC released Key: MAVENUPLOAD-1248 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1248 Project: maven-upload-requests Issue Type: Task Reporter: Greg Luck See attached. -- 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: (MRM-221) Webdav upload is not working
[ http://jira.codehaus.org/browse/MRM-221?page=comments#action_80183 ] Greg Luck commented on MRM-221: --- I created another new repository and retested. This time I could browse to it bu the webdav issue remains the same. > Webdav upload is not working > > > Key: MRM-221 > URL: http://jira.codehaus.org/browse/MRM-221 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1, 1.0 > Environment: Mac OS X using the default jetty container. Jetty > started with mvn jetty:run >Reporter: Greg Luck > > MRM-172 added webdav support. This is not working. > I have everything working scping to the repository. webdav via Archiva does > not work. > When I use > > > > > > url="dav://localhost:9091/repository/maven_repository"> > password="###"/> > > > > I get > upload-to-repository: > [artifact:install-provider] Installing provider: > org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-1 > [artifact:install-provider] Installing provider: > org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-1 > [artifact:install] [INFO] Installing > /Users/gluck/work/ehcache/trunk/target/dist/ehcache-1.2.4.jar to > /m2repository/net/sf/ehcache/ehcache/1.2.4/ehcache-1.2.4.jar > [artifact:deploy] Deploying to > dav://localhost:9091/repository/maven_repository > [artifact:deploy] WAGON_VERSION: 1.0-beta-1 > BUILD FAILED > /Users/gluck/work/ehcache/trunk/build.xml:364: > java.lang.IllegalArgumentException: id is null > If I click on the webdav link from archiva I get: > Error 404 Not Found > Resource in error: http://localhost:9091/repository/LOCAL/maven_repository > Exception details: > it.could.webdav.DAVException: Not found > at it.could.webdav.methods.HEAD.process(HEAD.java:52) > at it.could.webdav.methods.GET.process(GET.java:58) > at it.could.webdav.DAVProcessor.process(DAVProcessor.java:79) > at > org.apache.maven.archiva.web.servlet.repository.RepositoryAccess.servletRequest(RepositoryAccess.java:223) > at > org.apache.maven.archiva.web.servlet.PlexusComponentServlet.service(PlexusComponentServlet.java:126) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1049) > at > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040) > at > com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) > at > com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040) > at > com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:352) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:230) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141) > at org.mortbay.jetty.Server.handle(Server.java:286) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:444) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:701) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:203) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:340) > at > org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270) > at > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) -- 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: (MRM-221) Webdav upload is not working
Webdav upload is not working Key: MRM-221 URL: http://jira.codehaus.org/browse/MRM-221 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-1, 1.0 Environment: Mac OS X using the default jetty container. Jetty started with mvn jetty:run Reporter: Greg Luck MRM-172 added webdav support. This is not working. I have everything working scping to the repository. webdav via Archiva does not work. When I use I get upload-to-repository: [artifact:install-provider] Installing provider: org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-1 [artifact:install-provider] Installing provider: org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-1 [artifact:install] [INFO] Installing /Users/gluck/work/ehcache/trunk/target/dist/ehcache-1.2.4.jar to /m2repository/net/sf/ehcache/ehcache/1.2.4/ehcache-1.2.4.jar [artifact:deploy] Deploying to dav://localhost:9091/repository/maven_repository [artifact:deploy] WAGON_VERSION: 1.0-beta-1 BUILD FAILED /Users/gluck/work/ehcache/trunk/build.xml:364: java.lang.IllegalArgumentException: id is null If I click on the webdav link from archiva I get: Error 404 Not Found Resource in error: http://localhost:9091/repository/LOCAL/maven_repository Exception details: it.could.webdav.DAVException: Not found at it.could.webdav.methods.HEAD.process(HEAD.java:52) at it.could.webdav.methods.GET.process(GET.java:58) at it.could.webdav.DAVProcessor.process(DAVProcessor.java:79) at org.apache.maven.archiva.web.servlet.repository.RepositoryAccess.servletRequest(RepositoryAccess.java:223) at org.apache.maven.archiva.web.servlet.PlexusComponentServlet.service(PlexusComponentServlet.java:126) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1049) at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040) at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:352) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:230) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141) at org.mortbay.jetty.Server.handle(Server.java:286) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:444) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:701) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:203) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:340) at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) -- 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: (MAVENUPLOAD-1109) ehcache-1.2.3 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1109?page=all ] Greg Luck reopened MAVENUPLOAD-1109: Carlos I cannot find this anywhere ibiblio. Can you show me the path? I looked under ehcache top level and also under net/sf/ehcache Greg > ehcache-1.2.3 bundle > > > Key: MAVENUPLOAD-1109 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1109 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Assigned To: Carlos Sanchez > Attachments: ehcache-1.2.3-bundle.jar, ehcache-1.2.3-bundle.jar > > > ehcache-1.2.3 bundle. The tgz was released on sourceforge yesterday. -- 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-1109) ehcache-1.2.3 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1109?page=comments#action_74066 ] Greg Luck commented on MAVENUPLOAD-1109: Please use the smaller of the two files. It was uploaded on 4 September. The larger file contains clover classes. > ehcache-1.2.3 bundle > > > Key: MAVENUPLOAD-1109 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1109 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Attachments: ehcache-1.2.3-bundle.jar, ehcache-1.2.3-bundle.jar > > > ehcache-1.2.3 bundle. The tgz was released on sourceforge yesterday. -- 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: (MAVENUPLOAD-1109) ehcache-1.2.3 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1109?page=all ] Greg Luck updated MAVENUPLOAD-1109: --- Attachment: ehcache-1.2.3-bundle.jar Revised one without clover classes in it > ehcache-1.2.3 bundle > > > Key: MAVENUPLOAD-1109 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1109 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Attachments: ehcache-1.2.3-bundle.jar, ehcache-1.2.3-bundle.jar > > > ehcache-1.2.3 bundle. The tgz was released on sourceforge yesterday. -- 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-1109) ehcache-1.2.3 bundle
ehcache-1.2.3 bundle Key: MAVENUPLOAD-1109 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1109 Project: maven-upload-requests Issue Type: Task Reporter: Greg Luck Attachments: ehcache-1.2.3-bundle.jar ehcache-1.2.3 bundle. The tgz was released on sourceforge yesterday. -- 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-1022) ehcache-1.2.2 release
ehcache-1.2.2 release - Key: MAVENUPLOAD-1022 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1022 Project: maven-upload-requests Issue Type: Task Reporter: Greg Luck Attachments: ehcache-1.2.2-bundle.jar Please add to ibiblio -- 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-865) ehcache-1.2-bundle.jar
ehcache-1.2-bundle.jar -- Key: MAVENUPLOAD-865 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-865 Project: maven-upload-requests Type: Task Reporter: Greg Luck Attachments: ehcache-1.2-bundle.jar Ehcache-1.2 final release maven bundle. This bundle can be reproduced by running ant maven-bundle from a checked out ehcache subversion module. Please upload to ibiblio. -- 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: (MEV-350) ehcache pom for ehcache 1.2 beta 4 broken
[ http://jira.codehaus.org/browse/MEV-350?page=all ] Greg Luck reopened MEV-350: --- Carlos, ehcache-1.2 has been released. I really don't want the beta4 to be left in the repository because I do not want to support it. How do I go about removing the ehcache-1.2beta4 and put the new one up. It is all available from http://ehcache.sf.net > ehcache pom for ehcache 1.2 beta 4 broken > - > > Key: MEV-350 > URL: http://jira.codehaus.org/browse/MEV-350 > Project: Maven Evangelism > Type: Task > Reporter: Greg Luck > Assignee: Carlos Sanchez > Attachments: ehcache-1.2beta4.pom > > > The pom for ehcache-1.2beta4 is broken. > Trying to use it gives: > [WARNING] POM for 'ehcache:ehcache:pom:1.2beta4' is invalid. It will be > ignored for artifact resolution. Reason: Parse error reading POM. Reason: > Duplicated tag: 'groupId' (position: START_TAG seen ...\n > ... @20:16) > A corrected one is attached. -- 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-2155) ehcache is now using Maven 2.0. Can it be added to the powered by list?
ehcache is now using Maven 2.0. Can it be added to the powered by list? Key: MNG-2155 URL: http://jira.codehaus.org/browse/MNG-2155 Project: Maven 2 Type: Wish Components: Sites & Reporting Versions: 2.0.2 Reporter: Greg Luck Hi guys. I have uploaded the new ehcache web site: ehcache.sf.net, which is completely built and deployed using maven 2.0. It uses most of the plugins relevant to reporting and a web site and I think is a good example of what can be done. Any chance of being added to the powered by list on the powered-by-m2? I am not using the powered by logo because it does not suite the site but I am acknowledging the site was built using maven on the home 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: (MSITE-105) No line number for Doxia barfs makes using APT to write site documentation all but impossible
No line number for Doxia barfs makes using APT to write site documentation all but impossible - Key: MSITE-105 URL: http://jira.codehaus.org/browse/MSITE-105 Project: Maven 2.x Site Plugin Type: New Feature Versions: 2.0-beta-4 Environment: all Reporter: Greg Luck Priority: Critical The following is a typical error message complaining about the lack of a closing > tag. Also happens regularly with missing } tags when you are doing links. Getting a message like that in a 1000 line document is impossible to debug. It should specify the line number. and ideally the column number. [ERROR] Error rendering /Users/gluck/work/ehcache/src/site/apt/documentation/logging.apt: missing '>' org.codehaus.doxia.module.apt.AptParseException: missing '>' at org.codehaus.doxia.module.apt.AptParser.doTraverseText(AptParser.java:1011) at org.codehaus.doxia.module.apt.AptParser.access$500(AptParser.java:27) at org.codehaus.doxia.module.apt.AptParser$Block.traverseText(AptParser.java:1211) at org.codehaus.doxia.module.apt.AptParser$Block.traverseText(AptParser.java:1206) at org.codehaus.doxia.module.apt.AptParser$Paragraph.traverse(AptParser.java:1484) at org.codehaus.doxia.module.apt.AptParser.traverseSectionBlocks(AptParser.java:238) at org.codehaus.doxia.module.apt.AptParser.traverseBody(AptParser.java:148) at org.codehaus.doxia.module.apt.AptParser.parse(AptParser.java:110) at org.codehaus.doxia.DefaultDoxia.parse(DefaultDoxia.java:65) at org.codehaus.plexus.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:221) at org.codehaus.plexus.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:173) at org.codehaus.plexus.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:152) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:340) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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) Try parsing the following snippet to get the above error: +--+ +--+ -- 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
