[jira] Commented: (MINSTALL-41) Install with classifier does not install pom
[ http://jira.codehaus.org/browse/MINSTALL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110926 ] Libor Kramolis commented on MINSTALL-41: I think *it is a BUG* because it is recommended to use classifier to distinguish between different deployment environments. Look *Building For Different Environments with Maven 2* - [http://maven.apache.org/guides/mini/guide-building-for-different-environments.html]. I have similar experience with *ejb*, *war* and *ear* project types. > Install with classifier does not install pom > > > Key: MINSTALL-41 > URL: http://jira.codehaus.org/browse/MINSTALL-41 > Project: Maven 2.x Install Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Michele Lorenzini >Priority: Minor > > I have a project wich I need to build only specifying a classifier (in > detail: a war project which I need to build with different profiles to > include different > configurations. So I set up different filters and the package produces > different classified wars). > When I install the artifact, I've got the attached artifact installed but the > pom is NOT installed. > The log says "No primary artifact to install, installing attached artifacts > instead". > It's maybe related to MINSTALL-18 as it seems the mojo does not recognize the > presence of a primary artifact and goes to install the attached artifacts > (without installing the POM). > Don't know if this is really a bug or if I am trying a strange/not valid > project configuration (a project without a primary artifact). -- 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-564) Audit log is not populated when artifacts are deployed
Audit log is not populated when artifacts are deployed -- Key: MRM-564 URL: http://jira.codehaus.org/browse/MRM-564 Project: Archiva Issue Type: Improvement Reporter: Wendy Smoak The audit.log file should contain an entry when any of the following events occurs: create directory, remove directory, create file, modify file, remove file. After a release, the audit.log file only contained: 2007-09-13 19:27:55 - Logging Initialized. There are no other audit log files. (I would have expected to see some with dates in the filename, the others are configured to roll on a daily basis.) (Needs to be verified with 1.0-beta-3 or later.) -- 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: (MRM-440) If webdav URL lacks a trailing /, navigating to all links in the listing return 404.
[ http://jira.codehaus.org/browse/MRM-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-440: --- Fix Version/s: (was: 1.x) 1.0-beta-4 > If webdav URL lacks a trailing /, navigating to all links in the listing > return 404. > > > Key: MRM-440 > URL: http://jira.codehaus.org/browse/MRM-440 > Project: Archiva > Issue Type: Bug > Components: WebDAV interface >Affects Versions: 1.0-alpha-2 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.0-beta-4 > > > If you go to: > http://localhost:8080/archiva/repository/releases > then click a link, you get 404. > But if you go to: > http://localhost:8080/archiva/repository/releases/ > everything works as expected. -- 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-492) repository failures can present as a 404 from proxy
[ http://jira.codehaus.org/browse/MRM-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-492. -- Assignee: Joakim Erdfelt Resolution: Cannot Reproduce Cannot reproduce in archiva/trunk. I suspect the changes around MRM-563 fixed this. Reopen if it occurs again. > repository failures can present as a 404 from proxy > --- > > Key: MRM-492 > URL: http://jira.codehaus.org/browse/MRM-492 > Project: Archiva > Issue Type: Improvement > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-4 > > > if multiple repositories are a proxy source and it is not found on some, and > an error occurs on one or more - the end result is a "not found", where there > should be some indication of error in case the artifact may exist on the > repository with the 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
[jira] Commented: (MNG-2626) System scope dependencies in parent POM cause validation warnings for most plugins and errors in assembly plugin
[
http://jira.codehaus.org/browse/MNG-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110913
]
Brian Fox commented on MNG-2626:
Can we get updated patches and ITs for this? I can try to get it into 2.0.8
> System scope dependencies in parent POM cause validation warnings for most
> plugins and errors in assembly plugin
>
>
> Key: MNG-2626
> URL: http://jira.codehaus.org/browse/MNG-2626
> Project: Maven 2
> Issue Type: Bug
> Components: Errors
>Affects Versions: 2.0-alpha-1
>Reporter: Brian Topping
>Assignee: Jason van Zyl
>Priority: Blocker
> Fix For: Reviewed Pending Version Assignment
>
> Attachments: interpolation-good.patch, interpolation.patch,
> MNG-2626it.tgz
>
>
> When system scope dependencies are in a parent POM and the systemPath for
> those variables contain a variable to be interpolated as a root path, maven
> throws off a lot of spurious warnings that the POM does not validate because
> system paths need to be absolute. An example of this in a parent POM (where
> ${jboss.home} is defined in ~/.m2/settings.xml):
> {code:xml}
>
> jboss
> activation
> 4.0.4.GA
> system
>
> ${jboss.home}/server/default/lib/activation.jar
>
> {code}
> In discussing this with John and Jason online, both apparently have generic
> implementations that can go in at some point, but this is something I would
> like to get into 2.0.5. The patch is ~25 lines of new code with one
> replaced.
> It's marked as blocker because we use the assembly plugin, which fails the
> build on the validation problem where most other plugins just enumerate every
> system scope dependency. For now, I will distribute the patched version
> around the company though :-)
> thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-1420) When profile selected in command line doesn't exist print a warning/error
[ http://jira.codehaus.org/browse/MNG-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-1420. -- Resolution: Won't Fix I tried fixing this. At the time the CLI options are activated, the projects aren't processed yet. Even if they were, it is valid to have a profile defined somewhere in the tree, so this would warn in all the projects not implementing it. > When profile selected in command line doesn't exist print a warning/error > - > > Key: MNG-1420 > URL: http://jira.codehaus.org/browse/MNG-1420 > Project: Maven 2 > Issue Type: Improvement > Components: Errors, Profiles >Affects Versions: 2.0 >Reporter: Carlos Sanchez >Priority: Minor > Fix For: 2.0.x > > -- 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: (MNG-3086) NullPointerException in ResolutionNode.getTrail(ResolutionNode.java:136)
[ http://jira.codehaus.org/browse/MNG-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110910 ] Brian Fox commented on MNG-3086: Please create a core IT for this. http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test > NullPointerException in ResolutionNode.getTrail(ResolutionNode.java:136) > > > Key: MNG-3086 > URL: http://jira.codehaus.org/browse/MNG-3086 > Project: Maven 2 > Issue Type: Bug > Components: Errors >Affects Versions: 2.0.7 >Reporter: Thomas Leonard > > After upgrading from 2.0.6 to 2.0.7, our build fails with: > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.artifact.resolver.ResolutionNode.getTrail(ResolutionNode.java:136) > at > org.apache.maven.artifact.resolver.ResolutionNode.filterTrail(ResolutionNode.java:211) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:89) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:284) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Thanks, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3202) URL for mirror is not printed when a repository query fails
[ http://jira.codehaus.org/browse/MNG-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-3202. -- Assignee: Brian Fox Resolution: Duplicate > URL for mirror is not printed when a repository query fails > --- > > Key: MNG-3202 > URL: http://jira.codehaus.org/browse/MNG-3202 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.7 >Reporter: Jo Vandermeeren >Assignee: Brian Fox >Priority: Minor > > When a mirror for e.g. central has been set in settings.xml, the default URL > of central (http://repo1.maven.org/maven2) is still shown in the console. > In settings.xml: > > > central-mirror > http://trax-data:/archiva/repository/internal > central > > Example output: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > No versions are present in the repository for the artifact with a range [4.1,) > com.trax.platform:trax-coreServer:jar:null > from the specified remote repositories: > central (http://repo1.maven.org/maven2) -- 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: (MNG-2738) 1-char profile names cannot be activated with -P
[
http://jira.codehaus.org/browse/MNG-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110907
]
Brian Fox commented on MNG-2738:
This is a bug in the apache commons GnuParser:
{noformat}
CommandLineParser parser = new GnuParser();
return parser.parse( options, cleanArgs );
{noformat}
> 1-char profile names cannot be activated with -P
>
>
> Key: MNG-2738
> URL: http://jira.codehaus.org/browse/MNG-2738
> Project: Maven 2
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 2.0-alpha-1
>Reporter: Kenney Westerhof
>Priority: Minor
> Fix For: Reviewed Pending Version Assignment
>
>
> 'mvn install -Uc' gives;
> {noformat}
> Unable to parse command line options: no argument for:P
> usage: mvn [options] [] []
> Options:
> ...etc...
> {noformat}
> (same for mvn -Pc [whatever])
--
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: (MNG-2452) parameter parse error
[ http://jira.codehaus.org/browse/MNG-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110908 ] Brian Fox commented on MNG-2452: This is coming from the gnuparser. > parameter parse error > - > > Key: MNG-2452 > URL: http://jira.codehaus.org/browse/MNG-2452 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.3 > Environment: ubuntu linux >Reporter: Andrew Williams >Priority: Minor > Fix For: Reviewed Pending Version Assignment > > > typing "mvn -Uinstall" will result on a forced update and then an install > phase. > This is incorrect (if we wish to be compatible with GNU type arguments) it > should force "mvn -U install". > "-Uinstall" should imply 8 options, not 1 and the install command -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3201) org.apache.maven.project.MavenProject needs a toString()
[ http://jira.codehaus.org/browse/MNG-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-3201. -- Assignee: Brian Fox Resolution: Fixed Fix Version/s: 2.0.8 new output (f) project = MavenProject: org.apache.maven:maven:2.0.8-SNAPSHOT @ E:\svn\Maven\2.0.x\pom.xml > org.apache.maven.project.MavenProject needs a toString() > > > Key: MNG-3201 > URL: http://jira.codehaus.org/browse/MNG-3201 > Project: Maven 2 > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.0.7 >Reporter: Jo Vandermeeren >Assignee: Brian Fox > Fix For: 2.0.8 > > > This is completely useless: > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) reactorProjects = [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL > PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL > PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL > PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL > PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL > PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-561) Error 500 while deleting a proxy connector
[
http://jira.codehaus.org/browse/MRM-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt closed MRM-561.
--
Resolution: Fixed
Fixed in archiva/trunk revision 587351.
> Error 500 while deleting a proxy connector
> --
>
> Key: MRM-561
> URL: http://jira.codehaus.org/browse/MRM-561
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0-beta-3
> Environment: Linux, JDK 6
>Reporter: Arnaud Heritier
>Assignee: Joakim Erdfelt
>Priority: Blocker
> Fix For: 1.0-beta-4
>
>
> This error occurs when I try to remove the default proxy connector for
> maven2-repository.dev.java.net
> Web :
> {code}
> HTTP ERROR: 500
> Neither confirm() nor doConfirm() is found in action class
> org.apache.maven.archiva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
> RequestURI=/archiva/admin/deleteProxyConnector!confirm.action
> {code}
> Log :
> {code}
> INFO | jvm 1| 2007/10/22 12:17:40 | WARNING:
> /archiva/admin/deleteProxyConnector!confirm.action?source=internal&target=maven2-repository.dev.java.net:
> INFO | jvm 1| 2007/10/22 12:17:40 | java.lang.IllegalArgumentException:
> Neither confirm() nor doConfirm() is found in action class
> org.apache.maven.arch
> iva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:360)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
> 75)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:5
> 3)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInter
> ceptor.java:118)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.jav
> a:159)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:124
> )
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
> 75)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 |
[jira] Closed: (MNG-2685) mvn.bat detection of 4NT syntax error
[ http://jira.codehaus.org/browse/MNG-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-2685. -- Resolution: Fixed Fix Version/s: (was: Reviewed Pending Version Assignment) 2.0.8 patch already applied. Windows bat works fine. > mvn.bat detection of 4NT syntax error > - > > Key: MNG-2685 > URL: http://jira.codehaus.org/browse/MNG-2685 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.4 > Environment: Windows XP & 4NT 8.0 >Reporter: Mark DeLaFranier > Fix For: 2.0.8 > > Attachments: MNG-2685.patch > > > Copied from the 4NT 8.0 Documentation: > == > "Detecting 4NT or Take Command > From a batch file, you can determine if 4NT or TC is loaded by testing for > the variable function @EVAL, with a test like this: > if "[EMAIL PROTECTED] + 2]%" == "4" echo %_cmdproc is loaded! > This test can never succeed in CMD.EXE. (Other variable functions could also > be used for the same purpose.) The _CMDPROC internal variable tells you which > specific command processor is running. > === > The mvn.bat in 2.0.4 contains: > @REM -- 4NT shell > if "%eval[2+2]" == "4" goto 4NTArgs > It should be: > @REM -- 4NT shell > if "[EMAIL PROTECTED]" == "4" goto 4NTArgs > In case, you don't see it, the first one is missing the @ in between the % > and eval > I will attach a patch in a moment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2105) Enable remote debugging command line option (+ docs)
[ http://jira.codehaus.org/browse/MNG-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-2105. -- Resolution: Fixed Fix Version/s: (was: 2.x) 2.0.8 added mvnDebug scripts > Enable remote debugging command line option (+ docs) > > > Key: MNG-2105 > URL: http://jira.codehaus.org/browse/MNG-2105 > Project: Maven 2 > Issue Type: New Feature > Components: Command Line >Affects Versions: 2.0.2 >Reporter: Geoffrey De Smet >Priority: Minor > Fix For: 2.0.8 > > > [dev list mailing reference: Debugging maven with breakpoints feed-back: > --jdwp + docs] > Problem: > Currently its hard to enable remote debugging for a remote debugger of your > IDE. > Basically you need to set MAVEN_OPTS something like: > export MAVEN_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000" > mvn ... > and unset it again. > Solution: > 1) Make it easier, choices: > A) Provide a command line option to do this (--debug is already taken for > debug logging), choices: > a) mvn --jdpa > b) mvn --jdwp > B) Provide a different script: mvnDebug > to avoid parsing command line arguments in bat and shell > C) Find a generic way to give options on the command, like -mx etc to the > java process, possibly by namespacing them? > 2) Document it in mvn --help > 3) Document it on > http://maven.apache.org/guides/development/guide-m2-development.html > like so (APT): > Debugging with breakpoints > You can attach a remote debugger of your IDE to the maven process. > This will allow you to set breakpoints (line, exception, ...). > Start maven in debugger mode on port 8000: > +-- > mvn ??? install > +-- > If you want to change any of the debugger settings, > use MAVEN_OPTS instead. > Then connect to the correct port with a remote debugger in your IDE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2166) Provide the help listing as default when no arguments are provided
[
http://jira.codehaus.org/browse/MNG-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MNG-2166.
--
Assignee: Brian Fox
Resolution: Fixed
Fix Version/s: (was: 2.x)
2.0.8
New output:
{noformat}
[INFO] Scanning for projects...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO]
You must specify at least one goal. Try 'mvn install' to build or 'mvn -?' for
options
See http://maven.apache.org for more information.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Mon Oct 22 20:48:42 EDT 2007
[INFO] Final Memory: 1M/4M
[INFO]
{noformat}
> Provide the help listing as default when no arguments are provided
> --
>
> Key: MNG-2166
> URL: http://jira.codehaus.org/browse/MNG-2166
> Project: Maven 2
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 2.0, 2.0.1, 2.0.2
> Environment: Any
>Reporter: Andre Ranvik
>Assignee: Brian Fox
>Priority: Minor
> Fix For: 2.0.8
>
>
> When just writing "mvn" with no arguments on the command line I get a message
> such as this:
> >mvn
> [INFO] Scanning for projects...
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] You must specify at least one goal. Try 'install'
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: < 1 second
> [INFO] Finished at: Wed Mar 22 09:15:04 CET 2006
> [INFO] Final Memory: 1M/2M
> [INFO]
>
> Many new users to maven or any other such tools are used to getting at least
> some basic info of what is expected. How about just displaying the listing
> that shows up when a user writes "mvn -h" as default when no arguments are
> privided? This is also a feature that most other similar products have. I
> also would suggest printing a URL for where they can get basic information
> for how to use maven.
--
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-313) archiva fails to serve maven2 plugin from legacy repository
[ http://jira.codehaus.org/browse/MRM-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-313. -- Resolution: Fixed Fix Version/s: (was: 1.x) 1.0-beta-4 Fixed in archiva/trunk as a result of work done in MRM-557, MRM-562, MRM-563 > archiva fails to serve maven2 plugin from legacy repository > --- > > Key: MRM-313 > URL: http://jira.codehaus.org/browse/MRM-313 > Project: Archiva > Issue Type: Improvement > Components: remote proxy >Affects Versions: 1.0-alpha-1 >Reporter: nicolas de loof >Assignee: Joakim Erdfelt >Priority: Minor > Fix For: 1.0-beta-4 > > > Archiva is configured to proxy http://dist.codehaus.org/ (legacy layout) > the xdoclet2 maven2 plugin is deployed under /xdoclet/maven-plugins. This > looks right as the type is set to "maven-plugin". > trying to download > http://archiva/repository/maven/xdoclet/maven2-xdoclet2-plugin/2.0.5/maven2-xdoclet2-plugin-2.0.5.jar > fails > archiva has no info from the specified URL about trying to get a maven-plugin > ! > http://archiva/repository/maven/xdoclet/maven2-xdoclet2-plugin/2.0.5/maven2-xdoclet2-plugin-2.0.5.maven-plugin > works as expected. > 2 options (suggestions are wecome) : > - use a "-plugin" pattern that a plugin is required (just a hack, and > requires all plugin to follow this convention) > - read the requested artifact POM to get the artifact type. -- 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] Moved: (MINSTALL-43) install:install-file plugin to use file naming convention in place of most parameters
[ http://jira.codehaus.org/browse/MINSTALL-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox moved MNG-3149 to MINSTALL-43: Affects Version/s: (was: 2.0.7) 2.2 Component/s: (was: Command Line) (was: Plugins and Lifecycle) Key: MINSTALL-43 (was: MNG-3149) Project: Maven 2.x Install Plugin (was: Maven 2) > install:install-file plugin to use file naming convention in place of most > parameters > - > > Key: MINSTALL-43 > URL: http://jira.codehaus.org/browse/MINSTALL-43 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: James Drucza > > It would be really nice to have the install:install-file plugin support a > file naming convention instead of specifying all the parameters (and thus > maven support i.e. ignore the extra info in the file name). > eg: > instead of: > mvn install:install-file -DgroupId=MSSQLDriver -DartifactId=sqljdbc > -Dversion=1.1.1501.101 -Dpackaging=jar -Dfile=sqljdbc.jar > use: > mvn install:install-file -Dfile=MSSQLDriver-sqljdbc-1.1.1501.101.jar > > or some similar convention. -- 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-557) repair or remove commented out test cases in proxy module
[ http://jira.codehaus.org/browse/MRM-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-557. -- Resolution: Fixed Fixed with work in MRM-563 > repair or remove commented out test cases in proxy module > -- > > Key: MRM-557 > URL: http://jira.codehaus.org/browse/MRM-557 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-3 >Reporter: Brett Porter >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-4 > > > commit r583412 commented out two test cases: > archiva-base/archiva-proxy/src/test/java/org/apache/maven/archiva/proxy/ManagedDefaultTransferTest.java:392: > /* FIXME > archiva-base/archiva-proxy/src/test/java/org/apache/maven/archiva/proxy/ManagedLegacyTransferTest.java:129: > /* FIXME > The tests are broken if uncommented - we need to check why they were > commented out, and either fix the code, fix the tests, or remove them if they > are no longer valid. -- 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-563) Proxy connector logic for getIfModified is backwards.
[ http://jira.codehaus.org/browse/MRM-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-563. -- Resolution: Fixed Fixed in archiva/trunk revision 587318. > Proxy connector logic for getIfModified is backwards. > - > > Key: MRM-563 > URL: http://jira.codehaus.org/browse/MRM-563 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-3 >Reporter: Joakim Erdfelt >Assignee: Joakim Erdfelt >Priority: Critical > Fix For: 1.0-beta-4 > > > The logic for fetching content that exists locally, and remotely, but hasn't > changed remotely is backwards. > All fetches for new content results in a .getIfNewer() with a modified > timestamp of 0. > And all fetches for existing content results in .get() request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2508) mvn complains about missing Java 1.4 on Java 1.4.2
[ http://jira.codehaus.org/browse/MNG-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-2508: --- Fix Version/s: (was: Reviewed Pending Version Assignment) 2.0.7 > mvn complains about missing Java 1.4 on Java 1.4.2 > -- > > Key: MNG-2508 > URL: http://jira.codehaus.org/browse/MNG-2508 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.4 > Environment: java version "1.4.2" > gij (GNU libgcj) version 4.1.0 (SUSE Linux) > Copyright (C) 2006 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >Reporter: Markus KARG > Fix For: 2.0.7 > > > [EMAIL PROTECTED]:~> /opt/maven-2.0.4/bin/mvn > Sorry, but JDK 1.4 or above is required to execute Maven > You appear to be using Java version: 1.4.2 > [EMAIL PROTECTED]:~> java -version > java version "1.4.2" > gij (GNU libgcj) version 4.1.0 (SUSE Linux) > Copyright (C) 2006 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2508) mvn complains about missing Java 1.4 on Java 1.4.2
[
http://jira.codehaus.org/browse/MNG-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MNG-2508.
--
Resolution: Cannot Reproduce
I use maven on 1.4.2 all the time. It looks like your system is reporting the
wrong java spec version. Look at the source:
{noformat}
if ( "1.4".compareTo( System.getProperty( "java.specification.version"
) ) > 0 )
{
System.err.println( "Sorry, but JDK 1.4 or above is required to
execute Maven. You appear to be using "
+ "Java:" );
System.err.println( "java version \"" + System.getProperty(
"java.version", "" )
+ "\"" );
System.err.println( System.getProperty( "java.runtime.name",
"" ) + " (build "
+ System.getProperty( "java.runtime.version", "" ) + ")" );
System.err.println( System.getProperty( "java.vm.name", "" ) + " (build "
+ System.getProperty( "java.vm.version", ""
) + ", "
+ System.getProperty( "java.vm.info", "" ) +
")" );
return 1;
{noformat}
> mvn complains about missing Java 1.4 on Java 1.4.2
> --
>
> Key: MNG-2508
> URL: http://jira.codehaus.org/browse/MNG-2508
> Project: Maven 2
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 2.0.4
> Environment: java version "1.4.2"
> gij (GNU libgcj) version 4.1.0 (SUSE Linux)
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>Reporter: Markus KARG
> Fix For: Reviewed Pending Version Assignment
>
>
> [EMAIL PROTECTED]:~> /opt/maven-2.0.4/bin/mvn
> Sorry, but JDK 1.4 or above is required to execute Maven
> You appear to be using Java version: 1.4.2
> [EMAIL PROTECTED]:~> java -version
> java version "1.4.2"
> gij (GNU libgcj) version 4.1.0 (SUSE Linux)
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--
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-161) filename with dot have a false output name
[
http://jira.codehaus.org/browse/DOXIA-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110894
]
Steven Coco commented on DOXIA-161:
---
As per the comments on the <[EMAIL PROTECTED]> list ("Site Plugin
2.0-beta-6-SNAPSHOT ".vm" filtering fails now"), this seems to be fixed in the
latest snapshot available from
http://people.apache.org/repo/m2-snapshot-repository.
Thanks!
> filename with dot have a false output name
> --
>
> Key: DOXIA-161
> URL: http://jira.codehaus.org/browse/DOXIA-161
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Xhtml
>Affects Versions: 1.0-alpha-9
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Blocker
> Fix For: 1.0-beta-1
>
>
> Related to MSITE-265.
--
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-1774) Sync de.berlios.jsunit
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez reopened MAVENUPLOAD-1774: - I'm getting asked for password, you need to setup properly our public key for the mavensync user > Sync de.berlios.jsunit > -- > > Key: MAVENUPLOAD-1774 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1774 > Project: maven-upload-requests > Issue Type: Task >Reporter: Joerg Schaible >Assignee: Carlos Sanchez > > Please sync with de.berlios.jsunit, a JavaScript unit test library with Maven > 2 plugin and Ant task. Licensed with ASL 2.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1774) Sync de.berlios.jsunit
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1774. --- Assignee: Carlos Sanchez Resolution: Fixed > Sync de.berlios.jsunit > -- > > Key: MAVENUPLOAD-1774 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1774 > Project: maven-upload-requests > Issue Type: Task >Reporter: Joerg Schaible >Assignee: Carlos Sanchez > > Please sync with de.berlios.jsunit, a JavaScript unit test library with Maven > 2 plugin and Ant task. Licensed with ASL 2.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1749) QuickServer v1.4.7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1749. --- Assignee: Carlos Sanchez Resolution: Incomplete > QuickServer v1.4.7 > -- > > Key: MAVENUPLOAD-1749 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1749 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Akshathkumar Shetty >Assignee: Carlos Sanchez > > http://www.quickserver.org/maven_upload/QuickServer1.4.7-bundle.jar > > http://www.quickserver.org > http://www.quickserver.org/team.html > > QuickServer is an open source Java library/framework for quick creation > of robust multi-client TCP server applications. Please upload! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1758) Clickstream 1.0.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1758. --- Assignee: Carlos Sanchez Resolution: Won't Fix > Clickstream 1.0.3 > - > > Key: MAVENUPLOAD-1758 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1758 > Project: maven-upload-requests > Issue Type: Task >Reporter: fabrizio giustina >Assignee: Carlos Sanchez > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1773) Please upload Grester v1.0.1 to Maven Public Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1773. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload Grester v1.0.1 to Maven Public Repository > --- > > Key: MAVENUPLOAD-1773 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1773 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Michael Nyika >Assignee: Carlos Sanchez > > Changed the groupId to net.sf.grester; artifactId is now grester; version is > 1.0.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1764) Upload tagunit 1.0.1 to the repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1764. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload tagunit 1.0.1 to the repository > -- > > Key: MAVENUPLOAD-1764 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1764 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Ulrik Nilsson >Assignee: Carlos Sanchez > Attachments: tagunit.jar > > > In the same way that JUnit allows us to write unit tests for Java classes, > TagUnit allows us to unit test JSP custom tags, inside the container. In > essence, TagUnit is a tag library for testing custom tags within JSP pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1755) Extratags version 1.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1755. --- Assignee: Carlos Sanchez Resolution: Incomplete > Extratags version 1.0.2 > --- > > Key: MAVENUPLOAD-1755 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1755 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom Schneider >Assignee: Carlos Sanchez > Attachments: extratags-1.0.2-bundle.jar > > > http://extratags.googlecode.com/files/extratags-1.0.2-bundle.jar > http://code.google.com/p/extratags/ > http://cwiki.apache.org/S2PLUGINS/extratags-plugin.html > ExtraTags is a set of additional UI tags for struts2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1762) Joda Time 2007h upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1762. --- Assignee: Carlos Sanchez Resolution: Incomplete > Joda Time 2007h upload > -- > > Key: MAVENUPLOAD-1762 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1762 > Project: maven-upload-requests > Issue Type: Task >Reporter: Graham Lea >Assignee: Carlos Sanchez > > http://www.grlea.org/joda-time-1.4-tz2007h-maven.jar > http://joda-time.sourceforge.net > This is just version 1.4 of Joda Time built with the 2007h version of the > public timezone database, using the instructions at > http://joda-time.sourceforge.net/tz_update.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-563) Proxy connector logic for getIfModified is backwards.
[ http://jira.codehaus.org/browse/MRM-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-563: --- Priority: Critical (was: Major) Fix Version/s: 1.0-beta-4 > Proxy connector logic for getIfModified is backwards. > - > > Key: MRM-563 > URL: http://jira.codehaus.org/browse/MRM-563 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-3 >Reporter: Joakim Erdfelt >Assignee: Joakim Erdfelt >Priority: Critical > Fix For: 1.0-beta-4 > > > The logic for fetching content that exists locally, and remotely, but hasn't > changed remotely is backwards. > All fetches for new content results in a .getIfNewer() with a modified > timestamp of 0. > And all fetches for existing content results in .get() request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1775) Upload bndlib 0.0.205 to central repository (fixes bug introduced in 0.0.203)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1775. --- Assignee: Carlos Sanchez Resolution: Fixed synced 205 and 208 > Upload bndlib 0.0.205 to central repository (fixes bug introduced in 0.0.203) > - > > Key: MAVENUPLOAD-1775 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1775 > Project: maven-upload-requests > Issue Type: Task >Reporter: Stuart McCulloch >Assignee: Carlos Sanchez > > sorry, need another upload to fix a bug introduced in Bnd 0.0.203 (see > https://issues.apache.org/jira/browse/FELIX-401) > thanks in advance - it's much appreciated! -- 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-563) Proxy connector logic for getIfModified is backwards.
Proxy connector logic for getIfModified is backwards. - Key: MRM-563 URL: http://jira.codehaus.org/browse/MRM-563 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0-beta-3 Reporter: Joakim Erdfelt Fix For: 1.0-beta-4 The logic for fetching content that exists locally, and remotely, but hasn't changed remotely is backwards. All fetches for new content results in a .getIfNewer() with a modified timestamp of 0. And all fetches for existing content results in .get() request. -- 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-1777) please upload Log4Javascript
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110891 ] Carlos Sanchez commented on MAVENUPLOAD-1777: - please add a complete license section (see http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom ) and the scm section > please upload Log4Javascript > > > Key: MAVENUPLOAD-1777 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1777 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: nicolas de loof > > Log4Javascript is a js librarie comparable to log4j in javascript development. > This bundle contains a javascript archive, created for the javascript maven > tools currently in mojo sandbox. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1726) OpenDS Directory Server
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1726. --- Resolution: Fixed > OpenDS Directory Server > --- > > Key: MAVENUPLOAD-1726 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1726 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Jasper Blues >Assignee: Carlos Sanchez > Attachments: openDS-1.0.0-build005-bundle.jar, > openDS-1.0.0-build005-bundle.jar, openDS-1.0.0-build005-bundle.jar > > > OpenDS is an open source community project building a free and comprehensive > next generation directory service. OpenDS is designed to address large > deployments, to provide high performance, to be highly extensible, and to be > easy to deploy, manage and monitor. > Team List: https://opends.dev.java.net/public/misc/bios.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-549) Strange Groovy entries in the repository
[ http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110890 ] Carlos Sanchez commented on MEV-549: there's only m1 to m2 conversion What you see in http://repo1.maven.org/maven/groovy/jars/ comes directly from http://dist.codehaus.org/groovy/jars/ and is converted into http://repo1.maven.org/maven2/groovy So if you publish to http://repository.codehaus.org/org/codehaus/groovy/ I'd guess you have to stop doing it to http://dist.codehaus.org/groovy > Strange Groovy entries in the repository > > > Key: MEV-549 > URL: http://jira.codehaus.org/browse/MEV-549 > Project: Maven Evangelism > Issue Type: Task > Components: Relocation >Reporter: Paul King > > Hi, I am trying to track down why some spurious entries are showing up for > Groovy. Please let me know if this is not the appropriate forum. > Groovy used to publish into the maven1 repo and there was some magic in place > that "republished" artifacts into the maven 2 repo. > Groovy now publishes into the maven2 repo and some magic "republishes" the > jars back into repo1. > Unfortunately, the old magic still seems to be in place and a spurious entry > appears (under the old groupId) in the maven 2 repo. > Does anyone know how to turn off the old magic? I guess then we need to clean > up the spurious artifacts but I can submit separate issue(s) for that if > needed. > Here is my understanding of the trail: > (1) Project publishes to http://repository.codehaus.org/org/codehaus/groovy/ > (2) Sync happens to copy artifacts to > http://repo1.maven.org/maven2/org/codehaus/groovy/ > (3) Magic happens here to copy artifacts back to maven 1 land ending up at > http://repo1.maven.org/maven/groovy/jars/ > This is actually broken in that it should be being copied to > http://repo1.maven.org/maven/org.codehaus.groovy/jars/ > and also the copying of the poms to http://repo1.maven.org/maven/groovy/poms > (which of course should also > be changed to http://repo1.maven.org/maven/org.codehaus.groovy/poms) has > stopped working at some point. > (4) Additional magic which should be turned off now occurs at this point and > copies the artifacts back to the maven 2 > repo. An example of this from 1.1-rc-1 (12 Oct 2007) can be found here: > http://repo1.maven.org/maven2/groovy/groovy-all/1.1-rc-1/ > This is in the wrong place given the groupId and doesn't contain a POM. > I am trying to track this down so I can request that step (4) be turned off. > Thanks, 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] Reopened: (MSITE-265) filename with dot are considered as duplicate
[
http://jira.codehaus.org/browse/MSITE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reopened MSITE-265:
As DOXIA-161 has been reopened, this must be reopened.
The it must be completed with a test on file like download.apt.vm.
> filename with dot are considered as duplicate
> -
>
> Key: MSITE-265
> URL: http://jira.codehaus.org/browse/MSITE-265
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: doxia integration
>Affects Versions: 2.0-beta-6
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Blocker
> Fix For: 2.0-beta-6
>
>
> I have two files :
> src/site/xdoc/releases/release1.6.3.xml
> src/site/xdoc/releases/release1.6.xml
> The output is : Embedded error: Files 'releases\release1.6.xml' clashes with
> existing
> 'c:\projets\ServicesLayerServer\src\site\xdoc\releases\release1.6.3.xml'.
> As I see this comes from
> org.apache.maven.doxia.module.xhtml.decoration.render.RenderingContext.
> There is
> {noformat}
> this.outputName = document.substring( 0, document.indexOf( "." ) ).replace(
> '\\', '/' ) + ".html";
> {noformat}
> IMHO it should be :
> {noformat}
> this.outputName = document.substring( 0, document.lastIndexOf( "." )
> ).replace( '\\', '/' ) + ".html";
> {noformat}
> I have to try to update dependency in maven-site-plugin to last doxia to test
> this fix but I have some compilation error due to some changes in doxia
> c:\maven-svn\plugins\maven-site-plugin\src\main\java\org\apache\maven\plugins\site\ReportDocumentRenderer.java:[139,26]
> generate(org.codehaus.doxia.sink.Sink,java.util.Locale) in
> org.apache.maven.reporting.MavenReport cannot be applied to
> (org.apache.maven.doxia.siterenderer.sink.SiteRendererSink,java.util.Locale)
> This works with 2.0-beta-5.
--
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-161) filename with dot have a false output name
[
http://jira.codehaus.org/browse/DOXIA-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110887
]
Olivier Lamy commented on DOXIA-161:
Dennis can you deploy new snapshots or fix perms
{noformat}
$ pwd
/www/people.apache.org/repo/m2-snapshot-repository/org/apache/maven/doxia/doxia/1.0-alpha-10-SNAPSHOT
[EMAIL PROTECTED]
/www/people.apache.org/repo/m2-snapshot-repository/org/apache/maven/doxia/doxia/1.0-alpha-10-SNAPSHOT]$
ls -lrt maven-*
-rw-r--r-- 1 dennisl apcvs 368 Oct 22 21:31 maven-metadata.xml
-rw-r--r-- 1 dennisl apcvs 32 Oct 22 21:31 maven-metadata.xml.md5
-rw-r--r-- 1 dennisl apcvs 40 Oct 22 21:31 maven-metadata.xml.sha1
[EMAIL PROTECTED]
/www/people.apache.org/repo/m2-snapshot-repository/org/apache/maven/doxia/doxia-sitetools]$
pwd
/www/people.apache.org/repo/m2-snapshot-repository/org/apache/maven/doxia/doxia-sitetools
[EMAIL PROTECTED]
/www/people.apache.org/repo/m2-snapshot-repository/org/apache/maven/doxia/doxia-sitetools]$
ls -lrt maven-me*
-rw-r--r-- 1 dennisl apcvs 435 Oct 20 19:40 maven-metadata.xml
-rw-r--r-- 1 dennisl apcvs 32 Oct 20 19:40 maven-metadata.xml.md5
-rw-r--r-- 1 dennisl apcvs 40 Oct 20 19:40 maven-metadata.xml.sha1
{noformat}
If all is fine with you I will merge this to trunks.
Thanks.
> filename with dot have a false output name
> --
>
> Key: DOXIA-161
> URL: http://jira.codehaus.org/browse/DOXIA-161
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Xhtml
>Affects Versions: 1.0-alpha-9
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Blocker
> Fix For: 1.0-beta-1
>
>
> Related to MSITE-265.
--
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-161) filename with dot have a false output name
[ http://jira.codehaus.org/browse/DOXIA-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110885 ] Olivier Lamy commented on DOXIA-161: committed in rev 587277 for doxia-1.0-alpha-x branch. committed in rev 587278 for doxia-sitetools-1.0-alpha-x branch. Leave it open until merge in doxia/doxia-sitetools trunks. > filename with dot have a false output name > -- > > Key: DOXIA-161 > URL: http://jira.codehaus.org/browse/DOXIA-161 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Xhtml >Affects Versions: 1.0-alpha-9 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Blocker > Fix For: 1.0-beta-1 > > > Related to MSITE-265. -- 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-161) filename with dot have a false output name
[ http://jira.codehaus.org/browse/DOXIA-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110883 ] Olivier Lamy commented on DOXIA-161: Sorry didn't know this feature with velocity files. To really solve this we have to know the file extension in o.a.m.d.m.x.d.r.RenderingContext with adding a new constructor with this. This means a change o.a.m.d.s.DefaultSiteRenderer to use this new constructor with module.getExtension(). > filename with dot have a false output name > -- > > Key: DOXIA-161 > URL: http://jira.codehaus.org/browse/DOXIA-161 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Xhtml >Affects Versions: 1.0-alpha-9 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Blocker > Fix For: 1.0-beta-1 > > > Related to MSITE-265. -- 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-161) filename with dot have a false output name
[ http://jira.codehaus.org/browse/DOXIA-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated DOXIA-161: -- Fix Version/s: (was: 1.0-alpha-10) > filename with dot have a false output name > -- > > Key: DOXIA-161 > URL: http://jira.codehaus.org/browse/DOXIA-161 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Xhtml >Affects Versions: 1.0-alpha-9 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Blocker > Fix For: 1.0-beta-1 > > > Related to MSITE-265. -- 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: (DOXIA-161) filename with dot have a false output name
[ http://jira.codehaus.org/browse/DOXIA-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reopened DOXIA-161: --- This patch breaks the velocity template functionality. This new code changes the output filenames of these files so that they are different than before. An example of this is https://svn.apache.org/repos/asf/maven/site/trunk/src/site/apt/download.apt.vm, which with this code gets the output filename download.apt.html instead of download.html. I have reverted the patch on the alpha-branch, but this code is still present in trunk. > filename with dot have a false output name > -- > > Key: DOXIA-161 > URL: http://jira.codehaus.org/browse/DOXIA-161 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Xhtml >Affects Versions: 1.0-alpha-9 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Blocker > Fix For: 1.0-alpha-10, 1.0-beta-1 > > > Related to MSITE-265. -- 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-1534) Translate to French
[ http://jira.codehaus.org/browse/CONTINUUM-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1534. --- Resolution: Fixed committed in rev 587241 Thanks (Merci) ! > Translate to French > --- > > Key: CONTINUUM-1534 > URL: http://jira.codehaus.org/browse/CONTINUUM-1534 > Project: Continuum > Issue Type: Sub-task > Components: Web - UI >Reporter: Damien Blugeon >Assignee: Olivier Lamy >Priority: Minor > Fix For: 1.1-beta-4 > > Attachments: report_traduction.zip > > -- 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: (SUREFIRE-349) redirectTestOutputToFile truncates summary information
[ http://jira.codehaus.org/browse/SUREFIRE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated SUREFIRE-349: --- Attachment: SUREFIRE-349.patch Small patch for this issue. > redirectTestOutputToFile truncates summary information > -- > > Key: SUREFIRE-349 > URL: http://jira.codehaus.org/browse/SUREFIRE-349 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Jason T. Greene > Fix For: 2.3.1 > > Attachments: SUREFIRE-349.patch > > > In the current 2.4-SNAPSHOT, Instead of the normally expected > --- > T E S T S > --- > Running org.jboss.cache.FqnTest > Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.439 sec > Results : > Tests run: 26, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > You get: > --- > T E S T S > --- > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > -- 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: (SUREFIRE-315) The redirectTestOutputToFile does not handle output before tests, nor does it handle capturing output on both streams
[ http://jira.codehaus.org/browse/SUREFIRE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated SUREFIRE-315: --- Attachment: SUREFIRE-349.patch Another patch for this issue. This patch fixes the issue, and only changes a few lines of the code. > The redirectTestOutputToFile does not handle output before tests, nor does it > handle capturing output on both streams > - > > Key: SUREFIRE-315 > URL: http://jira.codehaus.org/browse/SUREFIRE-315 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Jason Dillon >Priority: Critical > Fix For: 2.4 > > Attachments: SUREFIRE-315.diff, SUREFIRE-349.patch > > > The redirectTestOutputToFile feature does not handle cases when output is > soaked up before the tests actually run, like output from static blocks or > from test case constructors. If output is detected before the > testSetStarting is invoked, then all further output will be due to a thrown > ISE, which gets eatten up somewhere in surefire. > Additionally, when a test outputs to STDOUT and STDERR, the output is not > muxed properly into the -output.txt file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3249) Profile resident POM element overrides do not effect inherited projects if the children have their own explicitly defined elements.
Profile resident POM element overrides do not effect inherited projects if the children have their own explicitly defined elements. --- Key: MNG-3249 URL: http://jira.codehaus.org/browse/MNG-3249 Project: Maven 2 Issue Type: Bug Components: Profiles Affects Versions: 2.0.7 Reporter: John Allen If i declare a profile in a base pom that overrides settings in the POM, those settings are only overridden in the base POM and not in the inherited children in a reactor build if the children also explicitly define their own values for those overridden settings. I almost didn't create this as you could argue that that is how children maintain control but I think the profile evaluation should be applied to each level of the hierarchy, as the inheritance model is built up, i.e. I expect the children to inherit the profile too, not just the application of that profile to it's ancestors state and thus that profile should applied to the child's model, after the rest of the child's inherited state has been established, and thus it should still override the child's settings. -- 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-562) Artifact type "maven-plugin" is not detected correctly in .toArtifactReference() methods.
[ http://jira.codehaus.org/browse/MRM-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-562. -- Resolution: Fixed Fixed in archiva/trunk revision 587224. > Artifact type "maven-plugin" is not detected correctly in > .toArtifactReference() methods. > - > > Key: MRM-562 > URL: http://jira.codehaus.org/browse/MRM-562 > Project: Archiva > Issue Type: Bug > Components: repository interface >Affects Versions: 1.0-beta-3 >Reporter: Joakim Erdfelt >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-4 > > > When working from a path to an ArtifactReference, the 'maven-plugin' type is > not detected correctly. -- 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-1534) Translate to French
[ http://jira.codehaus.org/browse/CONTINUUM-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Blugeon updated CONTINUUM-1534: -- Attachment: report_traduction.zip Hello everybody. I create this translation of continuum in the french. The zip contains any properties files for continuum. > Translate to French > --- > > Key: CONTINUUM-1534 > URL: http://jira.codehaus.org/browse/CONTINUUM-1534 > Project: Continuum > Issue Type: Sub-task > Components: Web - UI >Reporter: Damien Blugeon >Assignee: Olivier Lamy >Priority: Minor > Fix For: 1.1-beta-4 > > Attachments: report_traduction.zip > > -- 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-1534) Translate to French
Translate to French --- Key: CONTINUUM-1534 URL: http://jira.codehaus.org/browse/CONTINUUM-1534 Project: Continuum Issue Type: Sub-task Components: Web - UI Reporter: Damien Blugeon Assignee: Olivier Lamy Priority: Minor Fix For: 1.1-beta-4 -- 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: (SUREFIRE-359) surefire:surefire failes when there are spaces in directory names
surefire:surefire failes when there are spaces in directory names - Key: SUREFIRE-359 URL: http://jira.codehaus.org/browse/SUREFIRE-359 Project: Maven Surefire Issue Type: Bug Components: JUnit 3.x support Affects Versions: 2.4 Environment: linux maven 2.0.7 surefire-2.4-snapshot Reporter: Jeff Black This issue is similar to others filed, but specific enough I wanted to report it separately. On an ubunu linux system, if I checkout a maven project into a directory with spaces in the full path, surefire will fail the build before the tests are actually executed. (Spaces in the path occur, for example, when I build a Hudson job with spaces in the project name.) [INFO] [clean:clean] [INFO] Deleting directory /home/hudson/.hudson/jobs/sto dirspaces/workspace/persistence/target [INFO] Deleting directory /home/hudson/.hudson/jobs/sto dirspaces/workspace/persistence/target/classes [INFO] Deleting directory /home/hudson/.hudson/jobs/sto dirspaces/workspace/persistence/target/test-classes [INFO] Deleting directory /home/hudson/.hudson/jobs/sto dirspaces/workspace/persistence/target/site [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] [compiler:compile] [INFO] Compiling 50 source files to /home/hudson/.hudson/jobs/sto dirspaces/workspace/persistence/target/classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [compiler:testCompile] [INFO] Compiling 14 source files to /home/hudson/.hudson/jobs/sto dirspaces/workspace/persistence/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /home/hudson/.hudson/jobs/sto dirspaces/workspace/persistence/target/surefire-reports /bin/bash: line 0: cd: /home/hudson/.hudson/jobs/sto: No such file or directory [ERROR] There are test failures. -- 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-1533) Mapping of developer´s id to name in reports and e-mails
Mapping of developer´s id to name in reports and e-mails Key: CONTINUUM-1533 URL: http://jira.codehaus.org/browse/CONTINUUM-1533 Project: Continuum Issue Type: New Feature Affects Versions: 1.1-beta-3 Reporter: Kristoffer Moum Priority: Minor It would be a nice feature if the developer id could be mapped to the name attribute in reports and e-mails, i.e. reports would contain the full name rather than the svn user, ref. the snippet below. t527560 Kristoffer Moum [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-560) Dependency Tree causes an Exception
[
http://jira.codehaus.org/browse/MRM-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110859
]
Joakim Erdfelt commented on MRM-560:
Can you provide us with the project that you attempted to get the dep tree on
when this occured?
For now, I'll fix this to not flow the exception back to the user, but I'm
curious as to why the graph is null.
> Dependency Tree causes an Exception
> ---
>
> Key: MRM-560
> URL: http://jira.codehaus.org/browse/MRM-560
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0-beta-3
> Environment: solaris 9 + tomcat 6.0.14
>Reporter: Olivier Lamy
>Assignee: Joakim Erdfelt
>Priority: Blocker
> Fix For: 1.0-beta-4
>
>
> Using the Dependency Tree link generates the following stack trace :
> {noformat}
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it
> from fulfilling this request.
> exception
> javax.servlet.ServletException: org.apache.jasper.JasperException: An
> exception occurred processing JSP page
> /WEB-INF/jsp/artifact/dependencyTree.jsp at line 24
> 21: <%@ taglib prefix="my" tagdir="/WEB-INF/tags" %>
> 22: <%@ taglib prefix="archiva" uri="http://maven.apache.org/archiva"; %>
> 23:
> 24: version="${version}"
> 25: modelVersion="${model.version}">
> 26:artifactId="${node.artifactId}"
> 27:version="${node.version}"/>
> Stacktrace:
>
> com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:284)
>
> com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
>
> com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
> root cause
> org.apache.jasper.JasperException: An exception occurred processing JSP page
> /WEB-INF/jsp/artifact/dependencyTree.jsp at line 24
> 21: <%@ taglib prefix="my" tagdir="/WEB-INF/tags" %>
> 22: <%@ taglib prefix="archiva" uri="http://maven.apache.org/archiva"; %>
> 23:
> 24: version="${version}"
> 25: modelVersion="${model.version}">
> 26:artifactId="${node.artifactId}"
> 27:version="${node.version}"/>
> Stacktrace:
>
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:524)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:417)
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>
> com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:114)
>
> com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkResultSupport.java:143)
>
> com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:313)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:208)
>
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
>
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
>
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:53)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:118)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:178)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:124)
>
> com.opensym
[jira] Closed: (MRELEASE-250) release perform fails because it cannot find the distributionManagement in the base pom
[ http://jira.codehaus.org/browse/MRELEASE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MRELEASE-250. Resolution: Cannot Reproduce > release perform fails because it cannot find the distributionManagement in > the base pom > --- > > Key: MRELEASE-250 > URL: http://jira.codehaus.org/browse/MRELEASE-250 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: James William Dumay > Attachments: release-perform-log.txt > > > We have specified in our base pom the distribution repository for other maven > 2 projects to inherit from. > The trouble is when we run mvn release:perform, maven compains that there was > no distributionManagement set. > I have also check that the base pom is correct and that the child pom > inherits off of the base pom correctly. A small log 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] Updated: (MRM-561) Error 500 while deleting a proxy connector
[
http://jira.codehaus.org/browse/MRM-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt updated MRM-561:
---
Priority: Blocker (was: Major)
> Error 500 while deleting a proxy connector
> --
>
> Key: MRM-561
> URL: http://jira.codehaus.org/browse/MRM-561
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0-beta-3
> Environment: Linux, JDK 6
>Reporter: Arnaud Heritier
>Assignee: Joakim Erdfelt
>Priority: Blocker
> Fix For: 1.0-beta-4
>
>
> This error occurs when I try to remove the default proxy connector for
> maven2-repository.dev.java.net
> Web :
> {code}
> HTTP ERROR: 500
> Neither confirm() nor doConfirm() is found in action class
> org.apache.maven.archiva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
> RequestURI=/archiva/admin/deleteProxyConnector!confirm.action
> {code}
> Log :
> {code}
> INFO | jvm 1| 2007/10/22 12:17:40 | WARNING:
> /archiva/admin/deleteProxyConnector!confirm.action?source=internal&target=maven2-repository.dev.java.net:
> INFO | jvm 1| 2007/10/22 12:17:40 | java.lang.IllegalArgumentException:
> Neither confirm() nor doConfirm() is found in action class
> org.apache.maven.arch
> iva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:360)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
> 75)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:5
> 3)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInter
> ceptor.java:118)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.jav
> a:159)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:124
> )
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
> 75)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensympho
[jira] Reopened: (MRELEASE-250) release perform fails because it cannot find the distributionManagement in the base pom
[ http://jira.codehaus.org/browse/MRELEASE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reopened MRELEASE-250: -- Reopen to change the resolution. > release perform fails because it cannot find the distributionManagement in > the base pom > --- > > Key: MRELEASE-250 > URL: http://jira.codehaus.org/browse/MRELEASE-250 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: James William Dumay > Attachments: release-perform-log.txt > > > We have specified in our base pom the distribution repository for other maven > 2 projects to inherit from. > The trouble is when we run mvn release:perform, maven compains that there was > no distributionManagement set. > I have also check that the base pom is correct and that the child pom > inherits off of the base pom correctly. A small log 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] Updated: (MRM-560) Dependency Tree causes an Exception
[
http://jira.codehaus.org/browse/MRM-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt updated MRM-560:
---
Priority: Blocker (was: Major)
> Dependency Tree causes an Exception
> ---
>
> Key: MRM-560
> URL: http://jira.codehaus.org/browse/MRM-560
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0-beta-3
> Environment: solaris 9 + tomcat 6.0.14
>Reporter: Olivier Lamy
>Assignee: Joakim Erdfelt
>Priority: Blocker
> Fix For: 1.0-beta-4
>
>
> Using the Dependency Tree link generates the following stack trace :
> {noformat}
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it
> from fulfilling this request.
> exception
> javax.servlet.ServletException: org.apache.jasper.JasperException: An
> exception occurred processing JSP page
> /WEB-INF/jsp/artifact/dependencyTree.jsp at line 24
> 21: <%@ taglib prefix="my" tagdir="/WEB-INF/tags" %>
> 22: <%@ taglib prefix="archiva" uri="http://maven.apache.org/archiva"; %>
> 23:
> 24: version="${version}"
> 25: modelVersion="${model.version}">
> 26:artifactId="${node.artifactId}"
> 27:version="${node.version}"/>
> Stacktrace:
>
> com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:284)
>
> com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
>
> com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
> root cause
> org.apache.jasper.JasperException: An exception occurred processing JSP page
> /WEB-INF/jsp/artifact/dependencyTree.jsp at line 24
> 21: <%@ taglib prefix="my" tagdir="/WEB-INF/tags" %>
> 22: <%@ taglib prefix="archiva" uri="http://maven.apache.org/archiva"; %>
> 23:
> 24: version="${version}"
> 25: modelVersion="${model.version}">
> 26:artifactId="${node.artifactId}"
> 27:version="${node.version}"/>
> Stacktrace:
>
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:524)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:417)
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>
> com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:114)
>
> com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkResultSupport.java:143)
>
> com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:313)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:208)
>
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
>
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
>
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:53)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:118)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:178)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:124)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
>
[jira] Updated: (MRM-562) Artifact type "maven-plugin" is not detected correctly in .toArtifactReference() methods.
[ http://jira.codehaus.org/browse/MRM-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-562: --- Fix Version/s: 1.0-beta-4 > Artifact type "maven-plugin" is not detected correctly in > .toArtifactReference() methods. > - > > Key: MRM-562 > URL: http://jira.codehaus.org/browse/MRM-562 > Project: Archiva > Issue Type: Bug > Components: repository interface >Affects Versions: 1.0-beta-3 >Reporter: Joakim Erdfelt >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-4 > > > When working from a path to an ArtifactReference, the 'maven-plugin' type is > not detected correctly. -- 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-562) Artifact type "maven-plugin" is not detected correctly in .toArtifactReference() methods.
Artifact type "maven-plugin" is not detected correctly in .toArtifactReference() methods. - Key: MRM-562 URL: http://jira.codehaus.org/browse/MRM-562 Project: Archiva Issue Type: Bug Components: repository interface Affects Versions: 1.0-beta-3 Reporter: Joakim Erdfelt When working from a path to an ArtifactReference, the 'maven-plugin' type is not detected correctly. -- 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-176) Confluence parser doesn't strip leading space for section titles
Confluence parser doesn't strip leading space for section titles Key: DOXIA-176 URL: http://jira.codehaus.org/browse/DOXIA-176 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.0-alpha-9 Reporter: Vincent Massol For example for "h1. Hello", it'll send " Hello" to the text() Sink API instead of "Hello". -- 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-1528) Continuum gets slower over time and eventually crashes
[ http://jira.codehaus.org/browse/CONTINUUM-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110845 ] Emmanuel Venisse commented on CONTINUUM-1528: - Do you have modified the maxmemory parameter in wrapper.conf. The default value is 384m. With 260 projects, I think you should increase it to 512m or 1024m. > Continuum gets slower over time and eventually crashes > -- > > Key: CONTINUUM-1528 > URL: http://jira.codehaus.org/browse/CONTINUUM-1528 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3 >Reporter: Julien S >Priority: Critical > Attachments: ci.png > > > Our instance of continuum gets slower over time. > We counted the time needed to verify all projects at night when nothing has > changed in the SCM (hence, nothing is built). > During day time, the usage was quite intensive, however. > On day 1, it was about 3 minutes > On day 2, it was about 7 minutes > On day 3, it was about 10 minutes > And after a few more days (perhaps a week or so), Continuum would constantly > generate OutOfMemoryError and stop working. -- 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-1528) Continuum gets slower over time and eventually crashes
[ http://jira.codehaus.org/browse/CONTINUUM-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110842 ] Emmanuel Venisse commented on CONTINUUM-1528: - Today, I removed some unused datas in the db that was loaded with build results. Can you test the latest snapshot to see if it fix your OOME issue? > Continuum gets slower over time and eventually crashes > -- > > Key: CONTINUUM-1528 > URL: http://jira.codehaus.org/browse/CONTINUUM-1528 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3 >Reporter: Julien S >Priority: Critical > Attachments: ci.png > > > Our instance of continuum gets slower over time. > We counted the time needed to verify all projects at night when nothing has > changed in the SCM (hence, nothing is built). > During day time, the usage was quite intensive, however. > On day 1, it was about 3 minutes > On day 2, it was about 7 minutes > On day 3, it was about 10 minutes > And after a few more days (perhaps a week or so), Continuum would constantly > generate OutOfMemoryError and stop working. -- 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: (MWAR-126) It is not possible to package empty war.
It is not possible to package empty war. Key: MWAR-126 URL: http://jira.codehaus.org/browse/MWAR-126 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0.2 Reporter: Libor Kramolis Priority: Critical Attachments: war-bug.txt If there is no java sources and no resources (src/main/java and src/main/resources does not exist) it is not possible to package war application. But if I do NOT user classifier of war plugin there is no problem while war:war goal. -- org.apache.maven.lifecycle.LifecycleExecutionException: Error installing artifact: File d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error installing artifact: File d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist at org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:143) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.artifact.installer.ArtifactInstallationException: Error installing artifact: File d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist at org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:87) at org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:105) ... 18 more Caused by: java.io.IOException: File d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist at hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:845) at org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:73) ... 19 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: (CONTINUUM-1528) Continuum gets slower over time and eventually crashes
[ http://jira.codehaus.org/browse/CONTINUUM-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110837 ] Julien S commented on CONTINUUM-1528: - Most projects have one build result (but we also deploy sites), so we deploy one artifact and one site. A few projects have several artifacts. I have attached a image of the memory heap over time. I will attach an other one in a few days. There seem to be a upward trend, but it may be too early to confirm it. > Continuum gets slower over time and eventually crashes > -- > > Key: CONTINUUM-1528 > URL: http://jira.codehaus.org/browse/CONTINUUM-1528 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3 >Reporter: Julien S >Priority: Critical > Attachments: ci.png > > > Our instance of continuum gets slower over time. > We counted the time needed to verify all projects at night when nothing has > changed in the SCM (hence, nothing is built). > During day time, the usage was quite intensive, however. > On day 1, it was about 3 minutes > On day 2, it was about 7 minutes > On day 3, it was about 10 minutes > And after a few more days (perhaps a week or so), Continuum would constantly > generate OutOfMemoryError and stop working. -- 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-1528) Continuum gets slower over time and eventually crashes
[ http://jira.codehaus.org/browse/CONTINUUM-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien S updated CONTINUUM-1528: Attachment: ci.png > Continuum gets slower over time and eventually crashes > -- > > Key: CONTINUUM-1528 > URL: http://jira.codehaus.org/browse/CONTINUUM-1528 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3 >Reporter: Julien S >Priority: Critical > Attachments: ci.png > > > Our instance of continuum gets slower over time. > We counted the time needed to verify all projects at night when nothing has > changed in the SCM (hence, nothing is built). > During day time, the usage was quite intensive, however. > On day 1, it was about 3 minutes > On day 2, it was about 7 minutes > On day 3, it was about 10 minutes > And after a few more days (perhaps a week or so), Continuum would constantly > generate OutOfMemoryError and stop working. -- 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-1528) Continuum gets slower over time and eventually crashes
[ http://jira.codehaus.org/browse/CONTINUUM-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110835 ] Emmanuel Venisse commented on CONTINUUM-1528: - do you have lot of build results by project? > Continuum gets slower over time and eventually crashes > -- > > Key: CONTINUUM-1528 > URL: http://jira.codehaus.org/browse/CONTINUUM-1528 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3 >Reporter: Julien S >Priority: Critical > > Our instance of continuum gets slower over time. > We counted the time needed to verify all projects at night when nothing has > changed in the SCM (hence, nothing is built). > During day time, the usage was quite intensive, however. > On day 1, it was about 3 minutes > On day 2, it was about 7 minutes > On day 3, it was about 10 minutes > And after a few more days (perhaps a week or so), Continuum would constantly > generate OutOfMemoryError and stop working. -- 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] Issue Comment Edited: (MEAR-77) Duplicated jars in ear
[ http://jira.codehaus.org/browse/MEAR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110830 ] Stephane Nicoll edited comment on MEAR-77 at 10/22/07 9:08 AM: --- I didn't say it isn't a bug. I am saying that EAR plugin has nothing to do with that at a glance. If you're running mvn something from the parent project, the dependencies are taken from the reactor list (so the files in the target directory of each project). I've never seen a situation where they were duplicated, unless clean wasn't called of course). Please provide a project that reproduces your issue. was: I didn't say it isn't a bug. I am saying that EAR plugin has nothing to do with that at a glance. If you're running mvn something from the parent project, the dependencies are taken from the reactor result (so the files in the target directory of each project). I've never seen a situation when they were duplicated, unless clean wasn't called of course). Please provide a projet that reproduces your issue. > Duplicated jars in ear > -- > > Key: MEAR-77 > URL: http://jira.codehaus.org/browse/MEAR-77 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Win XP SP2, JDK 1.6.0, JRE 1.6.0_03, Maven 2.0.7 >Reporter: Tomek Matynia >Priority: Trivial > Attachments: poms.txt > > > Hi, this is my first issue submition, hope it is one, otherwise sorry for > bothering. If i did something wrong feel fre to teach me (I'm a beggining > software devloper, eager to learn). > I use Maven as an integration tool for an enterprise application with web, > ejb and simple jar modules. > I have poms like included in attachment, in my projects (I use Eclipse as > IDE, therefore its flat projects structure). I build the ear using > aggregation mechanism by calling goals 'clean package' on the > parent/aggregating project. It builds me an ear. That is ok. But when I > assign project.build.finalName on p5041a-krk-core (as "krk-core"), > p5041a-krk-ejb (as "krk-ejb") and p5041a-krk-web (as "krk-web"), for more > readable, then I get duplicated jars (core, ejb and web) in ear. In generated > application.xml, there are only those which I included in maven-ear-plugin's > configuration. I imagine, I get them from dependency, they are copied from my > local maven repo. > This is rather trivial issue, but i spent some time finding out what was > wrong. Now I don't use project.build.finalName. > Geetings to all Maven team, You're doing a great job, and sorry for my > english, if it's bad. -- 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: (MEAR-77) Duplicated jars in ear
[ http://jira.codehaus.org/browse/MEAR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110830 ] Stephane Nicoll commented on MEAR-77: - I didn't say it isn't a bug. I am saying that EAR plugin has nothing to do with that at a glance. If you're running mvn something from the parent project, the dependencies are taken from the reactor result (so the files in the target directory of each project). I've never seen a situation when they were duplicated, unless clean wasn't called of course). Please provide a projet that reproduces your issue. > Duplicated jars in ear > -- > > Key: MEAR-77 > URL: http://jira.codehaus.org/browse/MEAR-77 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Win XP SP2, JDK 1.6.0, JRE 1.6.0_03, Maven 2.0.7 >Reporter: Tomek Matynia >Priority: Trivial > Attachments: poms.txt > > > Hi, this is my first issue submition, hope it is one, otherwise sorry for > bothering. If i did something wrong feel fre to teach me (I'm a beggining > software devloper, eager to learn). > I use Maven as an integration tool for an enterprise application with web, > ejb and simple jar modules. > I have poms like included in attachment, in my projects (I use Eclipse as > IDE, therefore its flat projects structure). I build the ear using > aggregation mechanism by calling goals 'clean package' on the > parent/aggregating project. It builds me an ear. That is ok. But when I > assign project.build.finalName on p5041a-krk-core (as "krk-core"), > p5041a-krk-ejb (as "krk-ejb") and p5041a-krk-web (as "krk-web"), for more > readable, then I get duplicated jars (core, ejb and web) in ear. In generated > application.xml, there are only those which I included in maven-ear-plugin's > configuration. I imagine, I get them from dependency, they are copied from my > local maven repo. > This is rather trivial issue, but i spent some time finding out what was > wrong. Now I don't use project.build.finalName. > Geetings to all Maven team, You're doing a great job, and sorry for my > english, if it's bad. -- 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: (MEAR-77) Duplicated jars in ear
[ http://jira.codehaus.org/browse/MEAR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110828 ] Tomek Matynia commented on MEAR-77: --- Well, that's ok for me if the finalName isn't honored. I mean it shouldn't be included in the ear together with artifacts from local repository. I need only one of them - why artifacts from target directory of other projects (named with finalName) are also included in the bundle? And second thing is, what is the order of bundling: 1. copy artifacts from local repo to target of ear 2. overlay with artifacts form target's of other projects or inverse: 1. copy artifacts form target's of other projects to ear's target 2. overlay with artifacts from local repository I still think it's some kind of inconsistent. Of course, next time I ask... Regards > Duplicated jars in ear > -- > > Key: MEAR-77 > URL: http://jira.codehaus.org/browse/MEAR-77 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Win XP SP2, JDK 1.6.0, JRE 1.6.0_03, Maven 2.0.7 >Reporter: Tomek Matynia >Priority: Trivial > Attachments: poms.txt > > > Hi, this is my first issue submition, hope it is one, otherwise sorry for > bothering. If i did something wrong feel fre to teach me (I'm a beggining > software devloper, eager to learn). > I use Maven as an integration tool for an enterprise application with web, > ejb and simple jar modules. > I have poms like included in attachment, in my projects (I use Eclipse as > IDE, therefore its flat projects structure). I build the ear using > aggregation mechanism by calling goals 'clean package' on the > parent/aggregating project. It builds me an ear. That is ok. But when I > assign project.build.finalName on p5041a-krk-core (as "krk-core"), > p5041a-krk-ejb (as "krk-ejb") and p5041a-krk-web (as "krk-web"), for more > readable, then I get duplicated jars (core, ejb and web) in ear. In generated > application.xml, there are only those which I included in maven-ear-plugin's > configuration. I imagine, I get them from dependency, they are copied from my > local maven repo. > This is rather trivial issue, but i spent some time finding out what was > wrong. Now I don't use project.build.finalName. > Geetings to all Maven team, You're doing a great job, and sorry for my > english, if it's bad. -- 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-396) remove 'true' and 'false' from the descriptions on the repository admin page
[ http://jira.codehaus.org/browse/MRM-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-396. Assignee: Brett Porter Resolution: Fixed > remove 'true' and 'false' from the descriptions on the repository admin page > > > Key: MRM-396 > URL: http://jira.codehaus.org/browse/MRM-396 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter >Assignee: Brett Porter >Priority: Trivial > Fix For: 1.0-beta-4 > > > the (/) and (x) are sufficient -- 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-185) revise logging granularity
[ http://jira.codehaus.org/browse/MRM-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110825 ] Brett Porter commented on MRM-185: -- the proxy logging should also be revised to ensure it provides useful information for diagnosis and less noise > revise logging granularity > -- > > Key: MRM-185 > URL: http://jira.codehaus.org/browse/MRM-185 > Project: Archiva > Issue Type: Improvement > Components: system >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > in particular, check that JPOX logging is at the correct level, but generally > turn the noise down. -- 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: (MRM-560) Dependency Tree causes an Exception
[
http://jira.codehaus.org/browse/MRM-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-560:
-
Fix Version/s: 1.0-beta-4
> Dependency Tree causes an Exception
> ---
>
> Key: MRM-560
> URL: http://jira.codehaus.org/browse/MRM-560
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0-beta-3
> Environment: solaris 9 + tomcat 6.0.14
>Reporter: Olivier Lamy
> Fix For: 1.0-beta-4
>
>
> Using the Dependency Tree link generates the following stack trace :
> {noformat}
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it
> from fulfilling this request.
> exception
> javax.servlet.ServletException: org.apache.jasper.JasperException: An
> exception occurred processing JSP page
> /WEB-INF/jsp/artifact/dependencyTree.jsp at line 24
> 21: <%@ taglib prefix="my" tagdir="/WEB-INF/tags" %>
> 22: <%@ taglib prefix="archiva" uri="http://maven.apache.org/archiva"; %>
> 23:
> 24: version="${version}"
> 25: modelVersion="${model.version}">
> 26:artifactId="${node.artifactId}"
> 27:version="${node.version}"/>
> Stacktrace:
>
> com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:284)
>
> com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
>
> com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
> root cause
> org.apache.jasper.JasperException: An exception occurred processing JSP page
> /WEB-INF/jsp/artifact/dependencyTree.jsp at line 24
> 21: <%@ taglib prefix="my" tagdir="/WEB-INF/tags" %>
> 22: <%@ taglib prefix="archiva" uri="http://maven.apache.org/archiva"; %>
> 23:
> 24: version="${version}"
> 25: modelVersion="${model.version}">
> 26:artifactId="${node.artifactId}"
> 27:version="${node.version}"/>
> Stacktrace:
>
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:524)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:417)
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>
> com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:114)
>
> com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkResultSupport.java:143)
>
> com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:313)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:208)
>
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
>
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
>
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:53)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:118)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:178)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:124)
>
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
>
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
>
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(Metho
[jira] Closed: (MRM-551) the default scan cron expression is once a day, should be hourly
[ http://jira.codehaus.org/browse/MRM-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-551. Assignee: Brett Porter Resolution: Fixed > the default scan cron expression is once a day, should be hourly > > > Key: MRM-551 > URL: http://jira.codehaus.org/browse/MRM-551 > Project: Archiva > Issue Type: Bug > Components: system >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-4 > > > 0 0 0 * * -> 0 0 * * *, I think -- 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: (MRM-561) Error 500 while deleting a proxy connector
[
http://jira.codehaus.org/browse/MRM-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-561:
-
Fix Version/s: 1.0-beta-4
> Error 500 while deleting a proxy connector
> --
>
> Key: MRM-561
> URL: http://jira.codehaus.org/browse/MRM-561
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0-beta-3
> Environment: Linux, JDK 6
>Reporter: Arnaud Heritier
> Fix For: 1.0-beta-4
>
>
> This error occurs when I try to remove the default proxy connector for
> maven2-repository.dev.java.net
> Web :
> {code}
> HTTP ERROR: 500
> Neither confirm() nor doConfirm() is found in action class
> org.apache.maven.archiva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
> RequestURI=/archiva/admin/deleteProxyConnector!confirm.action
> {code}
> Log :
> {code}
> INFO | jvm 1| 2007/10/22 12:17:40 | WARNING:
> /archiva/admin/deleteProxyConnector!confirm.action?source=internal&target=maven2-repository.dev.java.net:
> INFO | jvm 1| 2007/10/22 12:17:40 | java.lang.IllegalArgumentException:
> Neither confirm() nor doConfirm() is found in action class
> org.apache.maven.arch
> iva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:360)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
> 75)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:5
> 3)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInter
> ceptor.java:118)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.jav
> a:159)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:124
> )
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
> 75)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INF
[jira] Closed: (MRM-558) html problem on repositories admin page causes footer to not be left aligned
[ http://jira.codehaus.org/browse/MRM-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-558. Assignee: Brett Porter Resolution: Fixed Fix Version/s: 1.0-beta-4 > html problem on repositories admin page causes footer to not be left aligned > > > Key: MRM-558 > URL: http://jira.codehaus.org/browse/MRM-558 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-3 >Reporter: Brett Porter >Assignee: Brett Porter >Priority: Minor > Fix For: 1.0-beta-4 > > -- 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-559) archiva version is not calculated correctly - always "Unknown"
[ http://jira.codehaus.org/browse/MRM-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-559. Assignee: Brett Porter Resolution: Fixed Fix Version/s: 1.0-beta-4 > archiva version is not calculated correctly - always "Unknown" > -- > > Key: MRM-559 > URL: http://jira.codehaus.org/browse/MRM-559 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-3 >Reporter: Brett Porter >Assignee: Brett Porter >Priority: Minor > Fix For: 1.0-beta-4 > > > in both the logs and the footer in beta-3 release candidate -- 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-546) Duplicate repositories show up while editing.
[ http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-546. Resolution: Fixed fixed by cleaning the registry > Duplicate repositories show up while editing. > - > > Key: MRM-546 > URL: http://jira.codehaus.org/browse/MRM-546 > Project: Archiva > Issue Type: Bug > Components: system >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Assignee: Brett Porter >Priority: Critical > Fix For: 1.0-beta-4 > > > Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to > 1.0-beta-2. > Situation: When editing the repositories, the repositories get duplicated. > This is likely due to the fact that the configuration "upgrade" technique > from to and is not > removing the section properly.. > Several efforts in the code have been made to correct this, but with no > success. See revision 583903 in archiva/trunk for details. -- 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: (MRM-546) Duplicate repositories show up while editing.
[ http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-546: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > Duplicate repositories show up while editing. > - > > Key: MRM-546 > URL: http://jira.codehaus.org/browse/MRM-546 > Project: Archiva > Issue Type: Bug > Components: system >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Assignee: Brett Porter >Priority: Critical > Fix For: 1.0-beta-4 > > > Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to > 1.0-beta-2. > Situation: When editing the repositories, the repositories get duplicated. > This is likely due to the fact that the configuration "upgrade" technique > from to and is not > removing the section properly.. > Several efforts in the code have been made to correct this, but with no > success. See revision 583903 in archiva/trunk for details. -- 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-546) Duplicate repositories show up while editing.
[ http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MRM-546: -- after cleaning target, the test fails now > Duplicate repositories show up while editing. > - > > Key: MRM-546 > URL: http://jira.codehaus.org/browse/MRM-546 > Project: Archiva > Issue Type: Bug > Components: system >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Assignee: Brett Porter >Priority: Critical > Fix For: 1.0-beta-3 > > > Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to > 1.0-beta-2. > Situation: When editing the repositories, the repositories get duplicated. > This is likely due to the fact that the configuration "upgrade" technique > from to and is not > removing the section properly.. > Several efforts in the code have been made to correct this, but with no > success. See revision 583903 in archiva/trunk for details. -- 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-481) Artifact requests with a .xml.zip extension fail with a 404 Error
[ http://jira.codehaus.org/browse/MRM-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110816 ] Brett Porter commented on MRM-481: -- confirmed to still be a problem > Artifact requests with a .xml.zip extension fail with a 404 Error > - > > Key: MRM-481 > URL: http://jira.codehaus.org/browse/MRM-481 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Cédric Vidal >Priority: Critical > Fix For: 1.0-beta-4 > > Attachments: multi-dots-ext-404-error.htm > > > This issue might also apply to any multi dots extension request but I didn't > check. > Regards, > Cédric -- 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-546) Duplicate repositories show up while editing.
[ http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-546. Resolution: Fixed Fix Version/s: (was: 1.0-beta-4) 1.0-beta-3 the tests have been fixed post beta-3, but the code remains the same - please reopen if you can reproduce with beta-3 > Duplicate repositories show up while editing. > - > > Key: MRM-546 > URL: http://jira.codehaus.org/browse/MRM-546 > Project: Archiva > Issue Type: Bug > Components: system >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Assignee: Brett Porter >Priority: Critical > Fix For: 1.0-beta-3 > > > Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to > 1.0-beta-2. > Situation: When editing the repositories, the repositories get duplicated. > This is likely due to the fact that the configuration "upgrade" technique > from to and is not > removing the section properly.. > Several efforts in the code have been made to correct this, but with no > success. See revision 583903 in archiva/trunk for details. -- 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: (MEAR-77) Duplicated jars in ear
[ http://jira.codehaus.org/browse/MEAR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110810 ] Stephane Nicoll commented on MEAR-77: - Weird but you need to take into account that project.build.finalName is never honored in the repository (this is the name of the archive in the target directory but the final file will still be named artifactId-version.extension). If you want to rename the artifacts in the EAR itself, you should use the bundleFilename functionnality which impacts only the EAR configuration. See http://maven.apache.org/plugins/maven-ear-plugin/examples/customizing-a-module-filename.html Next time, please ask this on the users list before creating an issue. > Duplicated jars in ear > -- > > Key: MEAR-77 > URL: http://jira.codehaus.org/browse/MEAR-77 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Win XP SP2, JDK 1.6.0, JRE 1.6.0_03, Maven 2.0.7 >Reporter: Tomek Matynia >Priority: Trivial > Attachments: poms.txt > > > Hi, this is my first issue submition, hope it is one, otherwise sorry for > bothering. If i did something wrong feel fre to teach me (I'm a beggining > software devloper, eager to learn). > I use Maven as an integration tool for an enterprise application with web, > ejb and simple jar modules. > I have poms like included in attachment, in my projects (I use Eclipse as > IDE, therefore its flat projects structure). I build the ear using > aggregation mechanism by calling goals 'clean package' on the > parent/aggregating project. It builds me an ear. That is ok. But when I > assign project.build.finalName on p5041a-krk-core (as "krk-core"), > p5041a-krk-ejb (as "krk-ejb") and p5041a-krk-web (as "krk-web"), for more > readable, then I get duplicated jars (core, ejb and web) in ear. In generated > application.xml, there are only those which I included in maven-ear-plugin's > configuration. I imagine, I get them from dependency, they are copied from my > local maven repo. > This is rather trivial issue, but i spent some time finding out what was > wrong. Now I don't use project.build.finalName. > Geetings to all Maven team, You're doing a great job, and sorry for my > english, if it's bad. -- 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-561) Error 500 while deleting a proxy connector
[
http://jira.codehaus.org/browse/MRM-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110809
]
Arnaud Heritier commented on MRM-561:
-
Same thing for the default central repo
> Error 500 while deleting a proxy connector
> --
>
> Key: MRM-561
> URL: http://jira.codehaus.org/browse/MRM-561
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0-beta-3
> Environment: Linux, JDK 6
>Reporter: Arnaud Heritier
>
> This error occurs when I try to remove the default proxy connector for
> maven2-repository.dev.java.net
> Web :
> {code}
> HTTP ERROR: 500
> Neither confirm() nor doConfirm() is found in action class
> org.apache.maven.archiva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
> RequestURI=/archiva/admin/deleteProxyConnector!confirm.action
> {code}
> Log :
> {code}
> INFO | jvm 1| 2007/10/22 12:17:40 | WARNING:
> /archiva/admin/deleteProxyConnector!confirm.action?source=internal&target=maven2-repository.dev.java.net:
> INFO | jvm 1| 2007/10/22 12:17:40 | java.lang.IllegalArgumentException:
> Neither confirm() nor doConfirm() is found in action class
> org.apache.maven.arch
> iva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:360)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
> 75)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:5
> 3)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInter
> ceptor.java:118)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.jav
> a:159)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:124
> )
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
> 75)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
> INFO | jvm 1| 2007/10/22 12:17:40 | at
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:19
[jira] Created: (MRM-561) Error 500 while deleting a proxy connector
Error 500 while deleting a proxy connector
--
Key: MRM-561
URL: http://jira.codehaus.org/browse/MRM-561
Project: Archiva
Issue Type: Bug
Components: web application
Affects Versions: 1.0-beta-3
Environment: Linux, JDK 6
Reporter: Arnaud Heritier
This error occurs when I try to remove the default proxy connector for
maven2-repository.dev.java.net
Web :
{code}
HTTP ERROR: 500
Neither confirm() nor doConfirm() is found in action class
org.apache.maven.archiva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
RequestURI=/archiva/admin/deleteProxyConnector!confirm.action
{code}
Log :
{code}
INFO | jvm 1| 2007/10/22 12:17:40 | WARNING:
/archiva/admin/deleteProxyConnector!confirm.action?source=internal&target=maven2-repository.dev.java.net:
INFO | jvm 1| 2007/10/22 12:17:40 | java.lang.IllegalArgumentException:
Neither confirm() nor doConfirm() is found in action class org.apache.maven.arch
iva.web.action.admin.connectors.proxy.DeleteProxyConnectorAction
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:360)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
75)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
INFO | jvm 1| 2007/10/22 12:17:40 | at
org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:5
3)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
INFO | jvm 1| 2007/10/22 12:17:40 | at
org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInter
ceptor.java:118)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
INFO | jvm 1| 2007/10/22 12:17:40 | at
org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.jav
a:159)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:124
)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:1
75)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
INFO | jvm 1| 2007/10/22 12:17:40 | at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(Aro
[jira] Closed: (CONTINUUM-1519) Continuum does not respect build order for flat projects
[ http://jira.codehaus.org/browse/CONTINUUM-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1519. --- Resolution: Cannot Reproduce > Continuum does not respect build order for flat projects > > > Key: CONTINUUM-1519 > URL: http://jira.codehaus.org/browse/CONTINUUM-1519 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3 > Environment: Windows XP/2003 Server, Maven 2.0.7 >Reporter: Siarhei Dudzin >Assignee: Emmanuel Venisse >Priority: Blocker > Fix For: 1.1-beta-4 > > Attachments: TEST-CONTINUUM-1519.zip > > > When adding maven 2 projects with flat project layout continuum sorts the > projects build sequence by alphabet thus braking builds. Previous version did > respect reactor build sequence and '--non-recursive' option allowed to build > flat projects independently but still in the right order. This is a very > blocking issue for us because we are forced atm to use flat project structure. -- 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: (CONTINUUM-1519) Continuum does not respect build order for flat projects
[ http://jira.codehaus.org/browse/CONTINUUM-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse reopened CONTINUUM-1519: - > Continuum does not respect build order for flat projects > > > Key: CONTINUUM-1519 > URL: http://jira.codehaus.org/browse/CONTINUUM-1519 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3 > Environment: Windows XP/2003 Server, Maven 2.0.7 >Reporter: Siarhei Dudzin >Assignee: Emmanuel Venisse >Priority: Blocker > Fix For: 1.1-beta-4 > > Attachments: TEST-CONTINUUM-1519.zip > > > When adding maven 2 projects with flat project layout continuum sorts the > projects build sequence by alphabet thus braking builds. Previous version did > respect reactor build sequence and '--non-recursive' option allowed to build > flat projects independently but still in the right order. This is a very > blocking issue for us because we are forced atm to use flat project structure. -- 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-560) Dependency Tree causes an Exception
Dependency Tree causes an Exception
---
Key: MRM-560
URL: http://jira.codehaus.org/browse/MRM-560
Project: Archiva
Issue Type: Bug
Components: web application
Affects Versions: 1.0-beta-3
Environment: solaris 9 + tomcat 6.0.14
Reporter: Olivier Lamy
Using the Dependency Tree link generates the following stack trace :
{noformat}
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from
fulfilling this request.
exception
javax.servlet.ServletException: org.apache.jasper.JasperException: An exception
occurred processing JSP page /WEB-INF/jsp/artifact/dependencyTree.jsp at line 24
21: <%@ taglib prefix="my" tagdir="/WEB-INF/tags" %>
22: <%@ taglib prefix="archiva" uri="http://maven.apache.org/archiva"; %>
23:
24:
26:
Stacktrace:
com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:284)
com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
root cause
org.apache.jasper.JasperException: An exception occurred processing JSP page
/WEB-INF/jsp/artifact/dependencyTree.jsp at line 24
21: <%@ taglib prefix="my" tagdir="/WEB-INF/tags" %>
22: <%@ taglib prefix="archiva" uri="http://maven.apache.org/archiva"; %>
23:
24:
26:
Stacktrace:
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:524)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:417)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:114)
com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkResultSupport.java:143)
com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:313)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:208)
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:53)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:118)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:178)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:124)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.AroundInterceptor.int
[jira] Closed: (CONTINUUM-1519) Continuum does not respect build order for flat projects
[
http://jira.codehaus.org/browse/CONTINUUM-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse closed CONTINUUM-1519.
---
Assignee: Emmanuel Venisse
Resolution: Fixed
Fix Version/s: 1.1-beta-4
The build order is correct on your test project. I get this in logs:
{noformat}
jvm 1| 2007-10-22 11:42:49,343 [SocketListener0-0] INFO
org.apache.maven.continuum.Continuum:default - Enqueuing 'a' with build
definition 'default maven2 buildDefinition' - id=6).
jvm 1| 2007-10-22 11:42:49,609 [SocketListener0-0] INFO
org.apache.maven.continuum.Continuum:default - Enqueuing 'e' with build
definition 'default maven2 buildDefinition' - id=6).
jvm 1| 2007-10-22 11:42:49,687 [SocketListener0-0] INFO
org.apache.maven.continuum.Continuum:default - Enqueuing 'd' with build
definition 'default maven2 buildDefinition' - id=6).
jvm 1| 2007-10-22 11:42:49,750 [SocketListener0-0] INFO
org.apache.maven.continuum.Continuum:default - Enqueuing 'c' with build
definition 'default maven2 buildDefinition' - id=6).
jvm 1| 2007-10-22 11:42:49,953 [SocketListener0-0] INFO
org.apache.maven.continuum.Continuum:default - Enqueuing 'b' with build
definition 'default maven2 buildDefinition' - id=6).
{noformat}
I don't know where you see the order a,b, c, d, e, if it is in the project
group summary page, it is normal because projects are sorted in alphabetical
order and this list is independant of the build order
> Continuum does not respect build order for flat projects
>
>
> Key: CONTINUUM-1519
> URL: http://jira.codehaus.org/browse/CONTINUUM-1519
> Project: Continuum
> Issue Type: Bug
>Affects Versions: 1.1-beta-3
> Environment: Windows XP/2003 Server, Maven 2.0.7
>Reporter: Siarhei Dudzin
>Assignee: Emmanuel Venisse
>Priority: Blocker
> Fix For: 1.1-beta-4
>
> Attachments: TEST-CONTINUUM-1519.zip
>
>
> When adding maven 2 projects with flat project layout continuum sorts the
> projects build sequence by alphabet thus braking builds. Previous version did
> respect reactor build sequence and '--non-recursive' option allowed to build
> flat projects independently but still in the right order. This is a very
> blocking issue for us because we are forced atm to use flat project structure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1776) please upload Log4Javascript
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MAVENUPLOAD-1776. Resolution: Duplicate > please upload Log4Javascript > > > Key: MAVENUPLOAD-1776 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1776 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: nicolas de loof > -- 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-1777) please upload Log4Javascript
please upload Log4Javascript Key: MAVENUPLOAD-1777 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1777 Project: maven-upload-requests Issue Type: New Feature Reporter: nicolas de loof Log4Javascript is a js librarie comparable to log4j in javascript development. This bundle contains a javascript archive, created for the javascript maven tools currently in mojo sandbox. -- 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-1776) please upload Log4Javascript
please upload Log4Javascript Key: MAVENUPLOAD-1776 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1776 Project: maven-upload-requests Issue Type: New Feature Reporter: nicolas de loof -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1770) please upload Jetty 5.1.10
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MAVENUPLOAD-1770. Resolution: Won't Fix > please upload Jetty 5.1.10 > -- > > Key: MAVENUPLOAD-1770 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1770 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: nicolas de loof > > jetty 5 is required by jsUnit, and no version is available on public repo > (for a strange reason, only 4.x and 6.x are deployed). > Thins bundle has been created from the distribution available at > ftp://ftp.mortbay.org/pub/jetty-5 -- 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] Work started: (MRM-546) Duplicate repositories show up while editing.
[ http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-546 started by Brett Porter. > Duplicate repositories show up while editing. > - > > Key: MRM-546 > URL: http://jira.codehaus.org/browse/MRM-546 > Project: Archiva > Issue Type: Bug > Components: system >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Assignee: Brett Porter >Priority: Critical > Fix For: 1.0-beta-4 > > > Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to > 1.0-beta-2. > Situation: When editing the repositories, the repositories get duplicated. > This is likely due to the fact that the configuration "upgrade" technique > from to and is not > removing the section properly.. > Several efforts in the code have been made to correct this, but with no > success. See revision 583903 in archiva/trunk for details. -- 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-509) Adding the same repository twice will be redirected to an Edit Repository page.
[ http://jira.codehaus.org/browse/MRM-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-509. Resolution: Fixed Fix Version/s: (was: 1.0-beta-4) 1.0-beta-3 > Adding the same repository twice will be redirected to an Edit Repository > page. > --- > > Key: MRM-509 > URL: http://jira.codehaus.org/browse/MRM-509 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: Maria Catherine Tan >Assignee: Brett Porter >Priority: Minor > Fix For: 1.0-beta-3 > > > 1. Create a new repository > 2. Create another repository with the same values as #1 > No error will occur after creating #2 since this will be treated as an edit > repository action instead of a create action. -- 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-559) archiva version is not calculated correctly - always "Unknown"
archiva version is not calculated correctly - always "Unknown" -- Key: MRM-559 URL: http://jira.codehaus.org/browse/MRM-559 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-3 Reporter: Brett Porter Priority: Minor in both the logs and the footer in beta-3 release candidate -- 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-558) html problem on repositories admin page causes footer to not be left aligned
html problem on repositories admin page causes footer to not be left aligned Key: MRM-558 URL: http://jira.codehaus.org/browse/MRM-558 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-3 Reporter: Brett Porter -- 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: (MRM-558) html problem on repositories admin page causes footer to not be left aligned
[ http://jira.codehaus.org/browse/MRM-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-558: - Priority: Minor (was: Major) > html problem on repositories admin page causes footer to not be left aligned > > > Key: MRM-558 > URL: http://jira.codehaus.org/browse/MRM-558 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-3 >Reporter: Brett Porter >Priority: Minor > -- 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: (MEAR-77) Duplicated jars in ear
Duplicated jars in ear -- Key: MEAR-77 URL: http://jira.codehaus.org/browse/MEAR-77 Project: Maven 2.x Ear Plugin Issue Type: Bug Affects Versions: 2.3.2 Environment: Win XP SP2, JDK 1.6.0, JRE 1.6.0_03, Maven 2.0.7 Reporter: Tomek Matynia Priority: Trivial Attachments: poms.txt Hi, this is my first issue submition, hope it is one, otherwise sorry for bothering. If i did something wrong feel fre to teach me (I'm a beggining software devloper, eager to learn). I use Maven as an integration tool for an enterprise application with web, ejb and simple jar modules. I have poms like included in attachment, in my projects (I use Eclipse as IDE, therefore its flat projects structure). I build the ear using aggregation mechanism by calling goals 'clean package' on the parent/aggregating project. It builds me an ear. That is ok. But when I assign project.build.finalName on p5041a-krk-core (as "krk-core"), p5041a-krk-ejb (as "krk-ejb") and p5041a-krk-web (as "krk-web"), for more readable, then I get duplicated jars (core, ejb and web) in ear. In generated application.xml, there are only those which I included in maven-ear-plugin's configuration. I imagine, I get them from dependency, they are copied from my local maven repo. This is rather trivial issue, but i spent some time finding out what was wrong. Now I don't use project.build.finalName. Geetings to all Maven team, You're doing a great job, and sorry for my english, if it's bad. -- 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-1532) Remove TestResult/SuiteResult/TestCaseFailure from the model
[ http://jira.codehaus.org/browse/CONTINUUM-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1532. --- Resolution: Fixed > Remove TestResult/SuiteResult/TestCaseFailure from the model > > > Key: CONTINUUM-1532 > URL: http://jira.codehaus.org/browse/CONTINUUM-1532 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3, 1.1-beta-4 >Reporter: Emmanuel Venisse >Assignee: Emmanuel Venisse > Fix For: 1.1-beta-4 > > > TestResult/SuiteResult/TestCaseFailure are populated in MavenTwoBuildExecutor > and never used. > It consume lot of resources to find surefire result, parse them but we don't > need them because surefire files are parsed directly by the > SurefireReportAction -- 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-1532) Remove TestResult/SuiteResult/TestCaseFailure from the model
[ http://jira.codehaus.org/browse/CONTINUUM-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110787 ] Emmanuel Venisse commented on CONTINUUM-1532: - We already copy xml files and we use them to generate the report. > Remove TestResult/SuiteResult/TestCaseFailure from the model > > > Key: CONTINUUM-1532 > URL: http://jira.codehaus.org/browse/CONTINUUM-1532 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3, 1.1-beta-4 >Reporter: Emmanuel Venisse >Assignee: Emmanuel Venisse > Fix For: 1.1-beta-4 > > > TestResult/SuiteResult/TestCaseFailure are populated in MavenTwoBuildExecutor > and never used. > It consume lot of resources to find surefire result, parse them but we don't > need them because surefire files are parsed directly by the > SurefireReportAction -- 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
