[jira] Commented: (MPCLOVER-56) Upgrade to Clover 1.3.13
[ http://jira.codehaus.org/browse/MPCLOVER-56?page=comments#action_75515 ] Vincent Massol commented on MPCLOVER-56: Thanks for fixing the problem I introduced Lukas! > Upgrade to Clover 1.3.13 > > > Key: MPCLOVER-56 > URL: http://jira.codehaus.org/browse/MPCLOVER-56 > Project: maven-clover-plugin > Issue Type: Improvement >Affects Versions: 1.11 >Reporter: Vincent Massol > Assigned To: Vincent Massol > Fix For: 1.12 > > -- 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: (MRM-181) Codehaus Snapshots Repository missing in POM
[ http://jira.codehaus.org/browse/MRM-181?page=all ] Brett Porter closed MRM-181. Resolution: Cannot Reproduce I removed plexus-naming and it was downloaded again. I'm not able to reproduce the failure. > Codehaus Snapshots Repository missing in POM > > > Key: MRM-181 > URL: http://jira.codehaus.org/browse/MRM-181 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 > Environment: Linux, Java 1.5.* >Reporter: Wilfred Springer > Assigned To: Brett Porter > Attachments: repository.patch > > > The Codehaus Snapshots Repository is missing from the root POM. As a result, > the build fails to locate certain Plexus 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: (MINSTALL-34) Make the install plugin work due the repository-manager has been moved to archiva.
[ http://jira.codehaus.org/browse/MINSTALL-34?page=all ] Brett Porter closed MINSTALL-34. Assignee: Brett Porter Resolution: Fixed applied, thanks! > Make the install plugin work due the repository-manager has been moved to > archiva. > -- > > Key: MINSTALL-34 > URL: http://jira.codehaus.org/browse/MINSTALL-34 > Project: Maven 2.x Install Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: WinXp, Java5 >Reporter: Martin Zeltner > Assigned To: Brett Porter >Priority: Blocker > Fix For: 2.2 > > Attachments: > patch_maven-install-plugin_make-it-work-with-archiva.patch > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > I've made some changes to make the today's version in svn repo (revision > 448538) work with the other parts of "current" maven in svn repo. The > repository-manager has been renamed to archiva project. In patch I use > revision 439992 of the archiva project > (https://svn.apache.org/repos/asf/maven/archiva/trunk). See appended patch. -- 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-2570) Maven needs to support multiple logging levels
Maven needs to support multiple logging levels -- Key: MNG-2570 URL: http://jira.codehaus.org/browse/MNG-2570 Project: Maven 2 Issue Type: Improvement Components: Logging Affects Versions: 2.0.4 Reporter: Brian Fox The current logging levels are essentially verbose (default) and debug (-X). We need a slightly less verbose output so that things like compiler warnings and other output is actually visable to the developer. Currently it gets buried in all the noise. -- 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-183) Archiva Plexus Runtime works only when copying tools.jar to the core directory
[ http://jira.codehaus.org/browse/MRM-183?page=comments#action_75509 ] Brett Porter commented on MRM-183: -- ah, the perils of me being on a mac system. Thanks - I'll test this out soon. There's actually a way to configure it into the startup scripts. How are you running the application? > Archiva Plexus Runtime works only when copying tools.jar to the core directory > -- > > Key: MRM-183 > URL: http://jira.codehaus.org/browse/MRM-183 > Project: Archiva > Issue Type: Bug > Components: web application >Reporter: Wilfred Springer > > Archiva Plexus Runtime works only when copying tools.jar to the core > directory. Othwerwise it will complain about the fact that is unable to find > the compiler classes from the JDK, and suggests to set JAVA_HOME. -- 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-1148) Upload jboss-seam-debug-1.0.1.jar
Upload jboss-seam-debug-1.0.1.jar - Key: MAVENUPLOAD-1148 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1148 Project: maven-upload-requests Issue Type: Task Reporter: Phillip Singer Attachments: jboss-seam-debug-1.0.1.jar, pom.xml Note: I am not one of the developers. I would like to have this jar uploaded, however, because the developers of the project refuse to do so (please see http://jira.jboss.org/jira/browse/JBSEAM-225). The jar that I have attached has simply been renamed from the one in the seam download at http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=163777&release_id=425718 to conform to your naming standards. The pom.xml file I have attached is one which I have created using the most accurate information I could find. I will be publishing an archetype to create a JBoss Seam application soon and would appreciate having the dependencies readily availble to anyone who uses the archetype. -- 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-1149) Upload jboss-seam-ui-1.0.1.jar
Upload jboss-seam-ui-1.0.1.jar -- Key: MAVENUPLOAD-1149 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1149 Project: maven-upload-requests Issue Type: Task Reporter: Phillip Singer Attachments: jboss-seam-ui-1.0.1.jar, pom.xml Note: I am not one of the developers. I would like to have this jar uploaded, however, because the developers of the project refuse to do so (please see http://jira.jboss.org/jira/browse/JBSEAM-225). The jar that I have attached has simply been renamed from the one in the seam download at http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=163777&release_id=425718 to conform to your naming standards. The pom.xml file I have attached is one which I have created using the most accurate information I could find. I will be publishing an archetype to create a JBoss Seam application soon and would appreciate having the dependencies readily availble to anyone who uses the archetype. -- 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-1147) Upload jboss-seam-1.0.1.jar
Upload jboss-seam-1.0.1.jar --- Key: MAVENUPLOAD-1147 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1147 Project: maven-upload-requests Issue Type: Task Reporter: Phillip Singer Attachments: jboss-seam-1.0.1.jar, pom.xml Note: I am not one of the developers. I would like to have this jar uploaded, however, because the developers of the project refuse to do so (please see http://jira.jboss.org/jira/browse/JBSEAM-225). The jar that I have attached has simply been renamed from the one in the seam download at http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=163777&release_id=425718 to conform to your naming standards. The pom.xml file I have attached is one which I have created using the most accurate information I could find. I will be publishing an archetype to create a JBoss Seam application soon and would appreciate having the dependencies readily availble to anyone who uses the archetype. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-937) NPE in DefaultContinuumScm.getValidationMessages, e.g. when maven-scm-local cannot access files
[ http://jira.codehaus.org/browse/CONTINUUM-937?page=all ] Emmanuel Venisse closed CONTINUUM-937. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1 Fixed. > NPE in DefaultContinuumScm.getValidationMessages, e.g. when maven-scm-local > cannot access files > --- > > Key: CONTINUUM-937 > URL: http://jira.codehaus.org/browse/CONTINUUM-937 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.0.3 >Reporter: Arne Degenring > Assigned To: Emmanuel Venisse >Priority: Minor > Fix For: 1.1 > > > We experience the following NPE when maven-scm-local cannot access the > filesystem, e.g. because a server is down. This is due to a missing > null-check for variable "messages" in > DefaultContinuumScm.getValidationMessages. We use Continuum 1.0.3, but the > check is even missing in SVN trunk. > java.lang.NullPointerException > at > org.apache.maven.continuum.scm.DefaultContinuumScm.getValidationMessages(DefaultContinuumScm.java:286) > at > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:266) > at > org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) > at java.lang.Thread.run(Thread.java:534) -- 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: (MCOMPILER-22) Compilation fails: "The command line is too long."
[ http://jira.codehaus.org/browse/MCOMPILER-22?page=all ]
Brahim Bakayoko updated MCOMPILER-22:
-
Attachment: plexus-compiler-javac-1.5.2.jar
I have fixed this bug some time ago.
Sorry if I did not post the fix early enough.
Copy the jar file to:
{local maven repository folder}\org\codehaus\plexus\plexus-compiler-javac\1.5.2
That's it.
Question: How do I submit the fix the the main development branch?
> Compilation fails: "The command line is too long."
> --
>
> Key: MCOMPILER-22
> URL: http://jira.codehaus.org/browse/MCOMPILER-22
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Reporter: Matthew Beermann
>Priority: Critical
> Fix For: 2.0.2
>
> Attachments: maven-compiler-plugin.patch, MCOMPILER-22.patch,
> MNG-MCCOMPILER-22-maven-compiler-plugin.patch,
> MNG-MCCOMPILER-22-plexus-compilers-noformatting.patch,
> MNG-MCCOMPILER-22-plexus-compilers.patch, plexus-compiler-javac-1.5.2.jar,
> plexus-compiler-javac.patch
>
>
> For one of my project, compilation fails with the message "The command line
> is too long". As far as I can tell, it's listing each and every source file,
> one at a time, in the -sourcepath attribute. (?!?) Here's the log:
> [DEBUG] Source roots:
> [DEBUG] C:\continuum-1.0.2\apps\continuum\working-directory\26\src
> [DEBUG] Command line options:
> [DEBUG] -d
> C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes
> -classpath -sourcepath SOURCE FILES HERE> -g -nowarn -target 1.4 -source 1.4
> Compiling 167 source files to
> C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Compilation failure
> Failure executing javac, but could not parse the error:
> The command line is too long.
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: Compilation failure
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:551)
> 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)
> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
> failure
> at
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:429)
> at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:110)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530)
> ... 16 more
--
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: (MANTRUN-59) Taskdef/Typedef and Plugin dependencies
[ http://jira.codehaus.org/browse/MANTRUN-59?page=comments#action_75471 ] Zarar Siddiqi commented on MANTRUN-59: -- I'm having the exact same issue. There needs to be a way to "convert" the maven classpath into one readable by the ant fragment. If there is a suggested workaround or a better way to do this, I'd like to hear it. Here is an example of this issue. In the xdoclet task that I'm about to run, I need a dependency on velocity and velocity is declared in the pom.xml like this: velocity velocity 1.4 This is automatically added to the maven classpath maven.compile.classpath. But if I use the taskdef like the following, it will fail (java.lang.NoClassDefFoundError) Even if I enter a hardcoded path, it will not work. > Taskdef/Typedef and Plugin dependencies > --- > > Key: MANTRUN-59 > URL: http://jira.codehaus.org/browse/MANTRUN-59 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: ttest > > I'm trying to run an ant task during a Maven run. The classes for that Ant > task are included in my Maven runtime dependencies(maven.runtime.classpath). > Here the relevant snippet from my POM: > > > > > >classname="com.bmw.most.generator.AntTask" > classpathref="maven.runtime.classpath"/> > >targetDirectory="target/generated-sources/most"/> > > This works if I don't provide depedencies in the POM for my plugin. But if I > do provide depedencies it doesn't work. I consider this to be a bug since > that should have no effect on the behaviour of "maven.runtime.classpath". My > first guess is that this is a classloading issue. Probably by providing > dependencies the classloaders get messed up and that causes the taskdef to > not load the classes from maven.runtime.classpath because echoing the value > of maven.runtime.classpath still gives the right classpath. > I have tried all variants of dereferencing maven.runtime.classpath. Didn't > work. > Also which is very interesting if I hardcode the classpath in the taskdef to > absolute pathnames it also does not work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MINSTALL-34) Make the install plugin work due the repository-manager has been moved to archiva.
Make the install plugin work due the repository-manager has been moved to archiva. -- Key: MINSTALL-34 URL: http://jira.codehaus.org/browse/MINSTALL-34 Project: Maven 2.x Install Plugin Issue Type: Bug Affects Versions: 2.2 Environment: WinXp, Java5 Reporter: Martin Zeltner Priority: Blocker Fix For: 2.2 Attachments: patch_maven-install-plugin_make-it-work-with-archiva.patch I've made some changes to make the today's version in svn repo (revision 448538) work with the other parts of "current" maven in svn repo. The repository-manager has been renamed to archiva project. In patch I use revision 439992 of the archiva project (https://svn.apache.org/repos/asf/maven/archiva/trunk). See appended patch. -- 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-183) Archiva Plexus Runtime works only when copying tools.jar to the core directory
[ http://jira.codehaus.org/browse/MRM-183?page=comments#action_75469 ] Milos Kleint commented on MRM-183: -- I encountered the same problem. for reasons unknown to me, running the plexus runtime by ./bin/linux/run.sh start script works. > Archiva Plexus Runtime works only when copying tools.jar to the core directory > -- > > Key: MRM-183 > URL: http://jira.codehaus.org/browse/MRM-183 > Project: Archiva > Issue Type: Bug > Components: web application >Reporter: Wilfred Springer > > Archiva Plexus Runtime works only when copying tools.jar to the core > directory. Othwerwise it will complain about the fact that is unable to find > the compiler classes from the JDK, and suggests to set JAVA_HOME. -- 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-183) Archiva Plexus Runtime works only when copying tools.jar to the core directory
Archiva Plexus Runtime works only when copying tools.jar to the core directory -- Key: MRM-183 URL: http://jira.codehaus.org/browse/MRM-183 Project: Archiva Issue Type: Bug Components: web application Reporter: Wilfred Springer Archiva Plexus Runtime works only when copying tools.jar to the core directory. Othwerwise it will complain about the fact that is unable to find the compiler classes from the JDK, and suggests to set JAVA_HOME. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-55) Add ability to turn off download URL in email
[ http://jira.codehaus.org/browse/MCHANGES-55?page=comments#action_75466 ] Eric Bernstein commented on MCHANGES-55: This wouldn't be a terrible thing if it was easy to alter the announcement.vm, but for the life of me, I can't seem to make that happen without actually altering the plugin. I'd be happy to look into what it takes to make the changes plugin handle an external template, but since it is documented that you can do it, I'm somewhat fearful that there is something I'm missing and it actually does work. Today, I've got my own changes plugin with a different template in the jar - this seems like a poor solution. > Add ability to turn off download URL in email > - > > Key: MCHANGES-55 > URL: http://jira.codehaus.org/browse/MCHANGES-55 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement >Reporter: Eric Bernstein > > If you are releasing a library, you may not want to provide a way to download > except through the maven repository. Building that URL in the pom is > non-trivial (unless you hardcode). It would be nice to be able to just remove > that part from the email altogether. -- 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: (MEAR-42) General setting of dependency filenames
[ http://jira.codehaus.org/browse/MEAR-42?page=all ] Stephane Nicoll updated MEAR-42: Fix Version/s: (was: 2.3) > General setting of dependency filenames > --- > > Key: MEAR-42 > URL: http://jira.codehaus.org/browse/MEAR-42 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Jonas Olsson >Priority: Minor > > When adding dependencies to the EAR, the "brief" filename from the repository > is used (i.e. -.jar). > I some cases this will result in a name collision, required to be manually > resolved with bundleFilename, but wouldn't an option to use the "full" > filename (i.e. --.jar) be better, allowing > automatic re-use of the already established namespace? -- 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-75) Sink#figureCaption() writes an "alt" attribute, but a "title" attribute would also be appropriate
Sink#figureCaption() writes an "alt" attribute, but a "title" attribute would also be appropriate - Key: DOXIA-75 URL: http://jira.codehaus.org/browse/DOXIA-75 Project: doxia Issue Type: Improvement Components: Core Affects Versions: 1.0-alpha-8 Reporter: Fabrice BELLINGARD Assigned To: Fabrice BELLINGARD Priority: Trivial It's nice to see the figure caption in a tooltip, so maybe both "alt" and "title" should be written. -- 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: (DOXIA-75) XhtmlSink#figureCaption() writes an "alt" attribute, but a "title" attribute would also be appropriate
[ http://jira.codehaus.org/browse/DOXIA-75?page=all ] Fabrice BELLINGARD updated DOXIA-75: Summary: XhtmlSink#figureCaption() writes an "alt" attribute, but a "title" attribute would also be appropriate (was: Sink#figureCaption() writes an "alt" attribute, but a "title" attribute would also be appropriate) > XhtmlSink#figureCaption() writes an "alt" attribute, but a "title" attribute > would also be appropriate > -- > > Key: DOXIA-75 > URL: http://jira.codehaus.org/browse/DOXIA-75 > Project: doxia > Issue Type: Improvement > Components: Core >Affects Versions: 1.0-alpha-8 >Reporter: Fabrice BELLINGARD > Assigned To: Fabrice BELLINGARD >Priority: Trivial > > It's nice to see the figure caption in a tooltip, so maybe both "alt" and > "title" should be written. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-901) Add a link in projectView to projectGroupSummary
[ http://jira.codehaus.org/browse/CONTINUUM-901?page=all ] Emmanuel Venisse closed CONTINUUM-901. -- Assignee: Emmanuel Venisse (was: Marvin King) Resolution: Fixed Applied. Thanks. > Add a link in projectView to projectGroupSummary > > > Key: CONTINUUM-901 > URL: http://jira.codehaus.org/browse/CONTINUUM-901 > Project: Continuum > Issue Type: Improvement >Reporter: Marvin King > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > Attachments: CONTINUUM901-continuum-webapp-09222006.patch, > CONTINUUM901-continuum-webapp.patch > > Time Spent: 11 hours > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-901) Add a link in projectView to projectGroupSummary
[ http://jira.codehaus.org/browse/CONTINUUM-901?page=all ] Marvin King updated CONTINUUM-901: -- Attachment: CONTINUUM901-continuum-webapp-09222006.patch > Add a link in projectView to projectGroupSummary > > > Key: CONTINUUM-901 > URL: http://jira.codehaus.org/browse/CONTINUUM-901 > Project: Continuum > Issue Type: Improvement >Reporter: Marvin King > Assigned To: Marvin King > Fix For: 1.1 > > Attachments: CONTINUUM901-continuum-webapp-09222006.patch, > CONTINUUM901-continuum-webapp.patch > > Time Spent: 6 hours > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-937) NPE in DefaultContinuumScm.getValidationMessages, e.g. when maven-scm-local cannot access files
NPE in DefaultContinuumScm.getValidationMessages, e.g. when maven-scm-local cannot access files --- Key: CONTINUUM-937 URL: http://jira.codehaus.org/browse/CONTINUUM-937 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.0.3 Reporter: Arne Degenring Priority: Minor We experience the following NPE when maven-scm-local cannot access the filesystem, e.g. because a server is down. This is due to a missing null-check for variable "messages" in DefaultContinuumScm.getValidationMessages. We use Continuum 1.0.3, but the check is even missing in SVN trunk. java.lang.NullPointerException at org.apache.maven.continuum.scm.DefaultContinuumScm.getValidationMessages(DefaultContinuumScm.java:286) at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:266) at org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:534) -- 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: (MRESOURCES-33) testResources & testResource were not mentioned in the docck-acceptable maven-resources-plugin documentation
testResources & testResource were not mentioned in the docck-acceptable maven-resources-plugin documentation Key: MRESOURCES-33 URL: http://jira.codehaus.org/browse/MRESOURCES-33 Project: Maven 2.x Resources Plugin Issue Type: Improvement Reporter: Franz Allan Valencia See Priority: Minor testResources & testResource were not mentioned in the docck-acceptable maven-resources-plugin documentation. -- 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: (MANTRUN-51) Can't find plugin dependency in multiproject
[ http://jira.codehaus.org/browse/MANTRUN-51?page=comments#action_75458 ]
Alexey Kharlamov commented on MANTRUN-51:
-
I have the same problem. Any progress since 06/May?
> Can't find plugin dependency in multiproject
>
>
> Key: MANTRUN-51
> URL: http://jira.codehaus.org/browse/MANTRUN-51
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.0, 1.1
> Environment: maven 2.0.4, antrun 1.0 & 1.1, jdk 1.5.0_06, windows xp
>Reporter: Fredrik Vraalsen
>
> I'm using antrun in my project to create an IzPack installation. The plugin
> configuration is below.
> When maven is run from the top-level project, the ant taskdef fails because
> it cannot find the IzPackTask class. However, when I run maven from the
> subproject itself, it works fine. Not sure if this is related to
> http://jira.codehaus.org/browse/MANTRUN-49. The error message from maven is
> at the bottom.
> {noformat}
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> package
>
>
>classname="com.izforge.izpack.ant.IzPackTask"/>
>input="${project.build.directory}/classes/izPack.xml"
> output="${project.build.directory}/CorasTool-${coras.version}-installer.jar"
> basedir="${project.build.directory}"/>
>
>
>
> run
>
>
>
>
>
> izpack
> standalone-compiler
> 3.8.0
>
>
>
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error executing ant tasks
> Embedded error: taskdef class com.izforge.izpack.ant.IzPackTask cannot be
> found
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
> tasks
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> 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:256)
> 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: Error executing
> ant tasks
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:77)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:72)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: taskdef class com.izforge.izpack.ant.IzPackTask cannot be found
> at
> org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:483)
> at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:183)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.a
[jira] Created: (MDEPLOY-40) Make problems with remote deployment explicit
Make problems with remote deployment explicit - Key: MDEPLOY-40 URL: http://jira.codehaus.org/browse/MDEPLOY-40 Project: Maven 2.x Deploy Plugin Issue Type: Improvement Affects Versions: 2.2.1 Reporter: Peter Troeger Priority: Minor The deployment to a remote repository might lead to some server-side problem - in my case, the utilized SFTP account did not had enough permissions in the repository path. It would be good if the info message: --- snip --- [INFO] Error deploying artifact: Error occured while deploying 'j2ee/j2ee/1.4/j2 ee-1.4.jar' to remote repository: sftp://maven.asg-platform.org/opt/maven/maven2 /repository --- snip --- could say something more about the original problem. The stack trace (maven -e) knows the answer, at the very end: --- snip --- [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact : Error occured while deploying 'j2ee/j2ee/1.4/j2ee-1.4.jar' to remote repositor y: sftp://maven.asg-platform.org/opt/maven/maven2/repository at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:219) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) 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:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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: Error deploying artif act: Error occured while deploying 'j2ee/j2ee/1.4/j2ee-1.4.jar' to remote reposi tory: sftp://maven.asg-platform.org/opt/maven/maven2/repository at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo. java:240) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Error occured while deploying 'j2ee/j2ee/1.4/j2ee-1.4.jar' to remote repository: sftp://maven.asg-platform.org/opt/maven/maven2/repository at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Def aultArtifactDeployer.java:91) at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo. java:236) ... 18 more Caused by: org.apache.maven.wagon.TransferFailedException: Error occured while d eploying 'j2ee/j2ee/1.4/j2ee-1.4.jar' to remote repository: sftp://maven.asg-pla tform.org/opt/maven/maven2/repository at org.apache.maven.wagon.providers.ssh.SftpWagon.put(SftpWagon.java:145 ) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(D efaultWagonManager.java:180) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Def aultWagonManager.java:109) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Def aultArtifactDeployer.java:77) ... 19 more Caused by: Permission denied at com.jcraft.jsch.ChannelSftp.throwStatusError(Unknown Source) at com.jcraft.jsch.ChannelSftp.mkdir(Unknown Source) at org.apache.maven.wagon.providers.ssh.SftpWagon.mkdir(SftpWagon.java:2 20) at org.apache.maven.wagon.providers.ssh.SftpWagon.mkdirs(SftpWagon.java: 200) at org.apache.maven.wagon.providers.ssh.SftpWagon.put(SftpWagon.java:96) ... 22 more [INFO] [INFO] Total time: 6 seconds -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http:
[jira] Commented: (CONTINUUM-904) Release integration improvements
[ http://jira.codehaus.org/browse/CONTINUUM-904?page=comments#action_75456 ] Edwin Punzalan commented on CONTINUUM-904: -- Updates: *Done* * verify that the goals are executed both in prepare and perform * add form validations *In Progress* * do not prompt for tag base for non-svn scm providers > Release integration improvements > > > Key: CONTINUUM-904 > URL: http://jira.codehaus.org/browse/CONTINUUM-904 > Project: Continuum > Issue Type: Improvement >Reporter: Edwin Punzalan > Assigned To: Edwin Punzalan >Priority: Critical > Fix For: 1.1 > > Attachments: CONTINUUM-904-continuum-webapp.patch > > Original Estimate: 10 hours > Time Spent: 4 hours > Remaining Estimate: 6 hours > > First, rerun and test everything from trunk. > Verify/Add/Fix the following: > 1] use the tag/tagBase configuration from the release plugin configuration in > the project to be released. Keep existing default if there's none configured > in pom. > 2] check error handling so continuum won't hang in a "progress" state > 3] the progress phase should be a redirect-action, so a post dialog won't > show when using the browser refresh > 4] verify that the goals are executed both in prepare and perform > 5] add form validations -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-933) Build result page doesn't show changes
[ http://jira.codehaus.org/browse/CONTINUUM-933?page=comments#action_75455 ] Emmanuel Venisse commented on CONTINUUM-933: What is the locale used by svn? > Build result page doesn't show changes > -- > > Key: CONTINUUM-933 > URL: http://jira.codehaus.org/browse/CONTINUUM-933 > Project: Continuum > Issue Type: Bug > Components: Web interface, SCM >Affects Versions: 1.1 > Environment: acegi branch >Reporter: Carlos Sanchez > Assigned To: Teodoro Cue Jr. >Priority: Critical > > I have Plexus XWork Integration in continuum, a build was triggered due some > changes to the pom, > I see no author, date or comment in the changes section > Changes > > AuthorDateComment Files > pom.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-933) Build result page doesn't show changes
[ http://jira.codehaus.org/browse/CONTINUUM-933?page=comments#action_75454 ] Teodoro Cue Jr. commented on CONTINUUM-933: --- I've done some investigation on this issue. It seems that result changes returned from the scm manager are empty. I've printed out the result from this line in DefaultContinuumScm: scmManager.getProviderByRepository( repository ).update( repository, fileSet, tag, getLatestUpdateDate( project ) ); And this line in DefaultBuildController: performAction( "update-working-directory-from-scm", buildContext ); Both results contains an empty list when printing: scmResult.getChanges().size(). > Build result page doesn't show changes > -- > > Key: CONTINUUM-933 > URL: http://jira.codehaus.org/browse/CONTINUUM-933 > Project: Continuum > Issue Type: Bug > Components: Web interface, SCM >Affects Versions: 1.1 > Environment: acegi branch >Reporter: Carlos Sanchez > Assigned To: Teodoro Cue Jr. >Priority: Critical > > I have Plexus XWork Integration in continuum, a build was triggered due some > changes to the pom, > I see no author, date or comment in the changes section > Changes > > AuthorDateComment Files > pom.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-181) Codehaus Snapshots Repository missing in POM
[ http://jira.codehaus.org/browse/MRM-181?page=comments#action_75453 ] Brett Porter commented on MRM-181: -- I'll check that one, but it should come from the same repo. Maybe you need -U? BTW, you don't need to build the runtime to run the webapp - the app and runtime are optional. > Codehaus Snapshots Repository missing in POM > > > Key: MRM-181 > URL: http://jira.codehaus.org/browse/MRM-181 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 > Environment: Linux, Java 1.5.* >Reporter: Wilfred Springer > Assigned To: Brett Porter > Attachments: repository.patch > > > The Codehaus Snapshots Repository is missing from the root POM. As a result, > the build fails to locate certain Plexus 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] Reopened: (MRM-181) Codehaus Snapshots Repository missing in POM
[ http://jira.codehaus.org/browse/MRM-181?page=all ] Milos Kleint reopened MRM-181: -- i've just update the sources or archiva trunk and still cannot completely build. it seems that a snapshot is not deployed in the repo? [INFO] Path to dependency: [INFO] 1) org.apache.maven.archiva:archiva-plexus-runtime:jar:1.0-SNAPSHOT [INFO] 2) org.codehaus.plexus:plexus-naming:jar:1.0-SNAPSHOT > Codehaus Snapshots Repository missing in POM > > > Key: MRM-181 > URL: http://jira.codehaus.org/browse/MRM-181 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 > Environment: Linux, Java 1.5.* >Reporter: Wilfred Springer > Assigned To: Brett Porter > Attachments: repository.patch > > > The Codehaus Snapshots Repository is missing from the root POM. As a result, > the build fails to locate certain Plexus 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] Updated: (CONTINUUM-903) In groupSummary, put build status icons on the same line
[ http://jira.codehaus.org/browse/CONTINUUM-903?page=all ] Maria Odea Ching updated CONTINUUM-903: --- Due Date: 26/Sep/06 Remaining Estimate: 15 hours Original Estimate: 15 hours > In groupSummary, put build status icons on the same line > > > Key: CONTINUUM-903 > URL: http://jira.codehaus.org/browse/CONTINUUM-903 > Project: Continuum > Issue Type: Improvement >Reporter: Marvin King > Assigned To: Maria Odea Ching > Original Estimate: 15 hours > Remaining Estimate: 15 hours > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-894) Users must have a default group
[ http://jira.codehaus.org/browse/CONTINUUM-894?page=all ] Maria Odea Ching closed CONTINUUM-894. -- Resolution: Fixed This improvement is already applied in trunk. > Users must have a default group > --- > > Key: CONTINUUM-894 > URL: http://jira.codehaus.org/browse/CONTINUUM-894 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Marvin King > Assigned To: Maria Odea Ching > Original Estimate: 10 hours > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 8 hours, 30 minutes > > - admin for the user that initialize continuum > - guest for others -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-929) The value in the Description field of the Edit User Group page is truncated until the first comma symbol
[ http://jira.codehaus.org/browse/CONTINUUM-929?page=all ] Maria Odea Ching closed CONTINUUM-929. -- Resolution: Fixed This issue is already fixed in trunk. The reporter was building the project from the acegi branch when he encountered the problem :) > The value in the Description field of the Edit User Group page is truncated > until the first comma symbol > > > Key: CONTINUUM-929 > URL: http://jira.codehaus.org/browse/CONTINUUM-929 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 > Environment: Linux FC4, JDK1.5, Maven 2.0.4, Jetty 6.0.0beta17 >Reporter: Napoleon Esmundo C. Ramirez > Assigned To: Maria Odea Ching > Original Estimate: 13 hours > Time Spent: 4 hours > Remaining Estimate: 9 hours > > When adding or editing the Description field of the User Group, the value is > truncated on the first occurence of the comma symbol. -- 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: (MRM-182) Archiva-plexus-runtime doesn't run
[ http://jira.codehaus.org/browse/MRM-182?page=all ] Brett Porter closed MRM-182. Assignee: Brett Porter Resolution: Fixed > Archiva-plexus-runtime doesn't run > -- > > Key: MRM-182 > URL: http://jira.codehaus.org/browse/MRM-182 > Project: Archiva > Issue Type: Bug > Environment: Linux, Java 1.5 >Reporter: Wilfred Springer > Assigned To: Brett Porter >Priority: Critical > > Without changing any of the configuration files, I get the log included > belog. Fiddling with the database configuration doesn't really help at all. > Running jetty:run in archiva-webapp gives a java.lang.NoSuchMethodError: > org.codehaus.plexus.DefaultPlexusContainer.(Ljava/lang/String;Ljava/lang/ClassLoader;Ljava/io/Reader;Ljava/util/Map;)V > Using PLEXUS_HOME: > /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva > Using PLEXUS_CONF: > /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/conf > Using PLEXUS_TMPDIR: > /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/temp > Using JAVA_HOME: /usr/java/jdk1.5.0_06 > [INFO] Services will be deployed in: > '/home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/services'. > [INFO] Applications will be deployed in: > '/home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps'. > [INFO] Service Supervisor is deploying > plexus-appserver-service-jetty-2.0-alpha-3-SNAPSHOT. > [INFO] Loading on start [role,roleHint]: > [org.codehaus.plexus.appserver.service.PlexusService,jetty] > Sep 21, 2006 9:44:37 PM org.mortbay.http.HttpServer doStart > INFO: Version Jetty/5.1.10 > Sep 21, 2006 9:44:37 PM org.mortbay.util.Container start > INFO: Started [EMAIL PROTECTED] > [INFO] Application Supervisor is deploying > archiva-plexus-application-1.0-SNAPSHOT. > [INFO] Extracting > /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva-plexus-application-1.0-SNAPSHOT.jar > to > '/home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva'. > [INFO] Deploying application 'archiva' at > '/home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva'. > [INFO] Using application configurator file > /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva/conf/application.xml. > [INFO] Using appDir = > /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva > [INFO] Deploying > /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva/webapp > with context path of / > [INFO] Using standard webapp classloader for webapp. > [INFO] Deploying appserver 'archiva'. > [INFO] Adding HTTP listener on *:8080 > Sep 21, 2006 9:44:40 PM org.mortbay.http.SocketListener start > INFO: Started SocketListener on 0.0.0.0:8080 > [INFO] Starting Jetty Context / > Sep 21, 2006 9:44:41 PM org.mortbay.util.FileResource > INFO: Checking Resource aliases > Sep 21, 2006 9:44:41 PM org.mortbay.util.Container start > INFO: Started [EMAIL PROTECTED] > Sep 21, 2006 9:44:41 PM org.mortbay.jetty.servlet.ServletHandler$Context log > INFO: Loading plexus context properties from: '/WEB-INF/plexus.properties' > Sep 21, 2006 9:44:42 PM org.mortbay.jetty.servlet.ServletHandler$Context log > INFO: Could not load plexus context properties from: > '/WEB-INF/plexus.properties' > 2006-09-21 21:44:42,447 [main] INFO PlexusContainer- Loading > on start [role]: [org.apache.maven.archiva.scheduler.RepositoryTaskScheduler] > 2006-09-21 21:44:42,633 [main] INFO RAMJobStore- > RAMJobStore initialized. > 2006-09-21 21:44:42,634 [main] INFO StdSchedulerFactory- Quartz > scheduler 'defaultScheduler' initialized from an externally provided > properties instance. > 2006-09-21 21:44:42,634 [main] INFO StdSchedulerFactory- Quartz > scheduler version: 1.4.5 > 2006-09-21 21:44:42,634 [main] INFO QuartzScheduler- > Scheduler defaultScheduler_$_NON_CLUSTERED started. > 2006-09-21 21:44:43,085 [main] WARN ConfigurationStore - > Configuration file: /home/wilfred/.m2/archiva.xml not found. Using defaults. > 2006-09-21 21:44:43,086 [main] INFO RepositoryTaskScheduler- Not > scheduling indexer - index path is not configured > 2006-09-21 21:44:43,086 [main] INFO PlexusContainer- Loading > on start [role]: [org.apache.maven.archiva.web.ArchivaSecurityDefaults] > Sep 21, 2006 9:44:43 PM org.mortbay.jetty.servlet.ServletHandler$Context log > INFO: ** FATAL ERROR STARTING UP PLEXUS-WEBWORK INTEGRATION ** > Looks like the Plexus
[jira] Created: (MEJB-20) Custom manifestEntries broken
Custom manifestEntries broken - Key: MEJB-20 URL: http://jira.codehaus.org/browse/MEJB-20 Project: Maven 2.x Ejb Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Windows XP, JDK 5, maven 2.0.4 Reporter: Legolas Greenleaf I need to add custom entries to the manifest of my EJB jar. I have added the following to the pom: org.apache.maven.plugins maven-ejb-plugin Custom manifest entry true META-INF/ejb-jar.xml 2.1 maven reports the following error: There was a problem creating the EJB archive: The attribute "MY-CUSTOM-ENTRY" may not occur more than once in the same section But the attribute is added only once. This does work when setting the version attribute of the ejb plugin to 2.0, but then my client jar contains the ejb-jar.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-181) Codehaus Snapshots Repository missing in POM
[ http://jira.codehaus.org/browse/MRM-181?page=all ] Brett Porter closed MRM-181. Assignee: Brett Porter Resolution: Fixed thanks, my bad when I changed the plexus container version > Codehaus Snapshots Repository missing in POM > > > Key: MRM-181 > URL: http://jira.codehaus.org/browse/MRM-181 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 > Environment: Linux, Java 1.5.* >Reporter: Wilfred Springer > Assigned To: Brett Porter > Attachments: repository.patch > > > The Codehaus Snapshots Repository is missing from the root POM. As a result, > the build fails to locate certain Plexus 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: (CONTINUUM-755) Add field validations with webwork field validator
[ http://jira.codehaus.org/browse/CONTINUUM-755?page=all ] Emmanuel Venisse closed CONTINUUM-755. -- Resolution: Fixed Applied. Thanks > Add field validations with webwork field validator > -- > > Key: CONTINUUM-755 > URL: http://jira.codehaus.org/browse/CONTINUUM-755 > Project: Continuum > Issue Type: Task > Components: Web interface >Affects Versions: 1.1 >Reporter: Emmanuel Venisse > Assigned To: Maria Odea Ching > Fix For: 1.1 > > Attachments: CONTINUUM-755-complete-continuum-webapp.patch, > CONTINUUM-755-continuum-webapp-09202006.patch, > CONTINUUM-755-continuum-webapp-09222006.patch, > CONTINUUM-755-continuum-webapp-userValidation.patch, > CONTINUUM-755-continuum-webapp.patch > > Original Estimate: 1 day, 6 hours > Time Spent: 1 day, 14 hours, 30 minutes > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-894) Users must have a default group
[ http://jira.codehaus.org/browse/CONTINUUM-894?page=all ] Maria Odea Ching updated CONTINUUM-894: --- Description: - admin for the user that initialize continuum - guest for others was: - admin for the user that initialize continuum - guest for others Due Date: 26/Sep/06 Remaining Estimate: 10 hours Original Estimate: 10 hours > Users must have a default group > --- > > Key: CONTINUUM-894 > URL: http://jira.codehaus.org/browse/CONTINUUM-894 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Marvin King > Assigned To: Maria Odea Ching > Original Estimate: 10 hours > Remaining Estimate: 10 hours > > - admin for the user that initialize continuum > - guest for others -- 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
