[jira] Commented: (MWAR-120) Option containerConfigXML doesn't work
[ http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108422 ] Stephane Nicoll commented on MWAR-120: -- No that's ok. I can have a look. > Option containerConfigXML doesn't work > -- > > Key: MWAR-120 > URL: http://jira.codehaus.org/browse/MWAR-120 > Project: Maven 2.x War Plugin > Issue Type: Bug >Reporter: Aaron Digulla > Attachments: context-bug.zip > > > The file specified with containerConfigXML is copied to the exploded WAR > directory but it will not end up in the final WAR. -- 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-1493) Data migration site documentation improvement
[ http://jira.codehaus.org/browse/CONTINUUM-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1493: Fix Version/s: 1.1-beta-4 > Data migration site documentation improvement > - > > Key: CONTINUUM-1493 > URL: http://jira.codehaus.org/browse/CONTINUUM-1493 > Project: Continuum > Issue Type: Improvement > Components: Data Management, Documentation >Affects Versions: 1.1-beta-3 >Reporter: Tomislav Stojcevich >Priority: Minor > Fix For: 1.1-beta-4 > > Attachments: CONTINUUM-1493-continuum-site.patch > > > The documentation for the Data Management tool is vague with respect to some > things. Attached is an updated version. It's specific for the 1.1 beta2 to > beta3 migration but can be adjusted to fit 1.0 to 1.1 when the time comes. -- 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-1491) Build history screen should show build definition description
[ http://jira.codehaus.org/browse/CONTINUUM-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1491: Description: I have a build that contains many build definitions( site, integration test per database, etc ) running in group ( ie using one scheduler) Without the build definition description, it is quite difficult to figure out which result belonging to which definition was: I have a build that contains many build definitions( site, integration test per database, etc ) running in group ( ie using one scheduler) Without the build definition description, it is quite difficult to figure out which result belonging to which definition Fix Version/s: 1.1-beta-4 > Build history screen should show build definition description > - > > Key: CONTINUUM-1491 > URL: http://jira.codehaus.org/browse/CONTINUUM-1491 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Affects Versions: 1.1-beta-3 > Environment: xp,svn >Reporter: Dan Tran > Fix For: 1.1-beta-4 > > > I have a build that contains many build definitions( site, integration test > per database, etc ) running in group ( ie using one scheduler) > Without the build definition description, it is quite difficult to figure out > which result belonging to which definition -- 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: (MCOMPILER-22) Compilation fails: "The command line is too long."
[ http://jira.codehaus.org/browse/MCOMPILER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108419 ] Carlos Sanchez commented on MCOMPILER-22: - you need to use the 2.0.2 version of the compiler plugin, no patches or anything like that, ask in the mailing list if you need help http://maven.apache.org/users/getting-help.html > Compilation fails: "The command line is too long." > -- > > Key: MCOMPILER-22 > URL: http://jira.codehaus.org/browse/MCOMPILER-22 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.0.1 >Reporter: Matthew Beermann >Assignee: Carlos Sanchez >Priority: Critical > Fix For: 2.0.2 > > Attachments: maven-compiler-plugin-space-fix.patch, > maven-compiler-plugin.patch, MCOMPILER-22.patch, > MNG-MCCOMPILER-22-maven-compiler-plugin.patch, > MNG-MCCOMPILER-22-plexus-compilers-noformatting.patch, > MNG-MCCOMPILER-22-plexus-compilers.patch, plexus-compiler-javac-1.5.2.jar, > plexus-compiler-javac.patch > > > For one of my project, compilation fails with the message "The command line > is too long". As far as I can tell, it's listing each and every source file, > one at a time, in the -sourcepath attribute. (?!?) Here's the log: > [DEBUG] Source roots: > [DEBUG] C:\continuum-1.0.2\apps\continuum\working-directory\26\src > [DEBUG] Command line options: > [DEBUG] -d > C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes > -classpath -sourcepath SOURCE FILES HERE> -g -nowarn -target 1.4 -source 1.4 > Compiling 167 source files to > C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > Failure executing javac, but could not parse the error: > The command line is too long. > [INFO] > > [DEBUG] Trace > org.apache.maven.BuildFailureException: Compilation failure > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:551) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation > failure > at > org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:429) > at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:110) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) > ... 16 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-528) just-in-time consumption of repository changes
[ http://jira.codehaus.org/browse/MRM-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108418 ] Brett Porter commented on MRM-528: -- Also need to consider impact on design - do not want to highly couple other modules to the consumers architecture. Review current dependencies, consider being able to push these onto a queue instead of running them exactly just-in-time. > just-in-time consumption of repository changes > --- > > Key: MRM-528 > URL: http://jira.codehaus.org/browse/MRM-528 > Project: Archiva > Issue Type: Improvement > Components: repository scanning >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > > need to have a simple, reusable way to be able to trigger consumers for a > given artifact just-in-time for things like addition via a proxy, removal via > purge, etc. -- 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-528) just-in-time consumption of repository changes
[ http://jira.codehaus.org/browse/MRM-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108417 ] Brett Porter commented on MRM-528: -- it seems like the best thing to do here is: - wait until completion of any known batch of operations (eg, for purge, collect a list of artifacts removed) - for each consumer, execute beginScan; then for each file execute processFile; then for each consumer execute completeScan - rinse and repeat for database consumers Things to check: - fault tolerance of running consumers at the same time (in case a scheduled scan occurs) > just-in-time consumption of repository changes > --- > > Key: MRM-528 > URL: http://jira.codehaus.org/browse/MRM-528 > Project: Archiva > Issue Type: Improvement > Components: repository scanning >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > > need to have a simple, reusable way to be able to trigger consumers for a > given artifact just-in-time for things like addition via a proxy, removal via > purge, etc. -- 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-527) Create tests for discovering deleted artifacts
[ http://jira.codehaus.org/browse/MRM-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-527 started by Maria Odea Ching. > Create tests for discovering deleted artifacts > -- > > Key: MRM-527 > URL: http://jira.codehaus.org/browse/MRM-527 > Project: Archiva > Issue Type: Sub-task > Components: repository scanning >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 1.0-beta-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-114) Different builds for ejb-client optional with parent
[ http://jira.codehaus.org/browse/MWAR-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108416 ] Tim Reilly commented on MWAR-114: - I think the underlying issue is a possible false assumption. The WAR plugin assumes that all of it's dependencies will be resolved to artifacts from _it's_ pom. But in a multimodule build, some artifact's such as an attached an attached ejb-client artifact are not resolved from the war's dependency list. It's already attached to the project. Due to this declaring the ejb-client as optional has no effect. I will attach the patch we are using as a candidate patch. The patch iterates the dependency list to develop an optional artifacts sub-list. It then iterates the optional artifacts list and ensures the resolved artifacts reflect the optional attribute. > Different builds for ejb-client optional with parent > > > Key: MWAR-114 > URL: http://jira.codehaus.org/browse/MWAR-114 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Tim Reilly > Attachments: mytime.zip > > > When trying to package a j2ee project's ejb-client artifact in the ear /lib > directory the war plugin's optional attribute is ignored if building from the > parent app project. If you build from the parent project you get the > ejb-client packaged in the web-inf/lib directory. If you build the ejb, war, > and ear independently you get the ejb-client packaged in the ear /lib > directory. It seems when run from the parent project the dependency/artifact > doesn't have the optional attribute set. > Perhaps this is b/c the artifact is a project artifact that was attached from > the ejb plugin it is not resolved as optional when the dependency is resolved > from the war project. > Attaching Geronimo's mytime sample with modifications to reproduce the > behavior. -- 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-158) automatically index proxied artifacts
[ http://jira.codehaus.org/browse/MRM-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-158. Assignee: Brett Porter Resolution: Duplicate Fix Version/s: (was: 1.x) > automatically index proxied artifacts > - > > Key: MRM-158 > URL: http://jira.codehaus.org/browse/MRM-158 > Project: Archiva > Issue Type: Improvement > Components: indexing, remote proxy >Reporter: Brett Porter >Assignee: Brett Porter >Priority: Critical > > currently the proxied artifacts will only be indexed when the indexer is next > run. > We should automatically index them, but some care needs to be taken: > - make sure the indexer is thread safe and won't regularly fail with a failed > lock > - find the best way to hook this up by design (need to separate proxied > artifacts from proxied files as this is internal to the proxy code, and don't > want the indexer into the proxy code but rather in the core). -- 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-527) Create tests for discovering deleted artifacts
[ http://jira.codehaus.org/browse/MRM-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-527: - Assignee: Maria Odea Ching Fix Version/s: 1.0-beta-3 > Create tests for discovering deleted artifacts > -- > > Key: MRM-527 > URL: http://jira.codehaus.org/browse/MRM-527 > Project: Archiva > Issue Type: Sub-task > Components: repository scanning >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 1.0-beta-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-528) just-in-time consumption of repository changes
just-in-time consumption of repository changes --- Key: MRM-528 URL: http://jira.codehaus.org/browse/MRM-528 Project: Archiva Issue Type: Improvement Components: repository scanning Affects Versions: 1.0-beta-2 Reporter: Brett Porter need to have a simple, reusable way to be able to trigger consumers for a given artifact just-in-time for things like addition via a proxy, removal via purge, etc. -- 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-527) Create tests for discovering deleted artifacts
Create tests for discovering deleted artifacts -- Key: MRM-527 URL: http://jira.codehaus.org/browse/MRM-527 Project: Archiva Issue Type: Sub-task Components: repository scanning Reporter: Maria Odea Ching -- 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-1738) Upload ZK Commons-EL Library to the central repository
Upload ZK Commons-EL Library to the central repository -- Key: MAVENUPLOAD-1738 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1738 Project: maven-upload-requests Issue Type: Task Reporter: Dennis Chen http://www.zkoss.org/maven/bundles/zkforge/zcommons-el-1.0.0-bundle.jar http://www.zkoss.org http://sourceforge.net/users/waterbottle/ ZK is an open-source Ajax Web framework that enables rich user interface for Web applications with no JavaScript and little programming. -- 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-491) paginate report pages
[ http://jira.codehaus.org/browse/MRM-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-491: --- Fix Version/s: (was: 1.0-beta-3) 1.x Postponed till after 1.0 then. Paging is non-trivial to add. > paginate report pages > - > > Key: MRM-491 > URL: http://jira.codehaus.org/browse/MRM-491 > Project: Archiva > Issue Type: Improvement > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.x > > > - artifact dependencies > - artifact used by -- 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-1737) Java Bean Library
Java Bean Library - Key: MAVENUPLOAD-1737 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1737 Project: maven-upload-requests Issue Type: Task Reporter: Hanson Char Attachments: beanlib-3.3.0beta10.jar, beanlib-hibernate-3.3.0beta10.jar Java Bean Library (beanlib) is a utilities library for use with JavaBean's. It makes life easy for bean replication. Java Bean Library for Hibernate (beanlib-hibernate) is particularly handy when used with Hibernate. It allows developers to easily reuse the same pojo classes for both persistence instances and data transfer objects. -- 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-491) paginate report pages
[ http://jira.codehaus.org/browse/MRM-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108413 ] Brett Porter commented on MRM-491: -- these pages don't currently use jasper reports - they are more like the current search page. I wouldn't think that getting into an unknown technology this late in the release cycle is a good idea, myself. > paginate report pages > - > > Key: MRM-491 > URL: http://jira.codehaus.org/browse/MRM-491 > Project: Archiva > Issue Type: Improvement > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-3 > > > - artifact dependencies > - artifact used by -- 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-521) No validation for the repository purge fields in repo config
[ http://jira.codehaus.org/browse/MRM-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-521 started by Maria Odea Ching. > No validation for the repository purge fields in repo config > > > Key: MRM-521 > URL: http://jira.codehaus.org/browse/MRM-521 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-1, 1.0-beta-2 >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 1.0-beta-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MRM-37) discover the deletion of artifacts
[ http://jira.codehaus.org/browse/MRM-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-37 started by Maria Odea Ching. > discover the deletion of artifacts > -- > > Key: MRM-37 > URL: http://jira.codehaus.org/browse/MRM-37 > Project: Archiva > Issue Type: Improvement > Components: repository scanning >Reporter: Brett Porter >Assignee: Maria Odea Ching > Fix For: 1.0-beta-3 > > > currently, the discovery mechanism is geared to walking a source repository > and insert into the target repository. However, there is no way to determine > if an artifact has been removed. We may need to track this - potentially > using metadata or the repository index. -- 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-1493) Data migration site documentation improvement
[ http://jira.codehaus.org/browse/CONTINUUM-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomislav Stojcevich updated CONTINUUM-1493: --- Attachment: CONTINUUM-1493-continuum-site.patch > Data migration site documentation improvement > - > > Key: CONTINUUM-1493 > URL: http://jira.codehaus.org/browse/CONTINUUM-1493 > Project: Continuum > Issue Type: Improvement > Components: Data Management, Documentation >Affects Versions: 1.1-beta-3 >Reporter: Tomislav Stojcevich >Priority: Minor > Attachments: CONTINUUM-1493-continuum-site.patch > > > The documentation for the Data Management tool is vague with respect to some > things. Attached is an updated version. It's specific for the 1.1 beta2 to > beta3 migration but can be adjusted to fit 1.0 to 1.1 when the time comes. -- 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-1493) Data migration site documentation improvement
Data migration site documentation improvement - Key: CONTINUUM-1493 URL: http://jira.codehaus.org/browse/CONTINUUM-1493 Project: Continuum Issue Type: Improvement Components: Data Management, Documentation Affects Versions: 1.1-beta-3 Reporter: Tomislav Stojcevich Priority: Minor The documentation for the Data Management tool is vague with respect to some things. Attached is an updated version. It's specific for the 1.1 beta2 to beta3 migration but can be adjusted to fit 1.0 to 1.1 when the time comes. -- 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: (MCOMPILER-22) Compilation fails: "The command line is too long."
[ http://jira.codehaus.org/browse/MCOMPILER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108383 ] GenDyn commented on MCOMPILER-22: - I am having the same problem as mentioned in this Jira issue. I have downloaded the patch and installed gnu Win32 tool. I don't have any experience with maven as well as installing patches into a plugin. Can someone please give me the step-by-step process for the upgrade? Thank you. > Compilation fails: "The command line is too long." > -- > > Key: MCOMPILER-22 > URL: http://jira.codehaus.org/browse/MCOMPILER-22 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.0.1 >Reporter: Matthew Beermann >Assignee: Carlos Sanchez >Priority: Critical > Fix For: 2.0.2 > > Attachments: maven-compiler-plugin-space-fix.patch, > maven-compiler-plugin.patch, MCOMPILER-22.patch, > MNG-MCCOMPILER-22-maven-compiler-plugin.patch, > MNG-MCCOMPILER-22-plexus-compilers-noformatting.patch, > MNG-MCCOMPILER-22-plexus-compilers.patch, plexus-compiler-javac-1.5.2.jar, > plexus-compiler-javac.patch > > > For one of my project, compilation fails with the message "The command line > is too long". As far as I can tell, it's listing each and every source file, > one at a time, in the -sourcepath attribute. (?!?) Here's the log: > [DEBUG] Source roots: > [DEBUG] C:\continuum-1.0.2\apps\continuum\working-directory\26\src > [DEBUG] Command line options: > [DEBUG] -d > C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes > -classpath -sourcepath SOURCE FILES HERE> -g -nowarn -target 1.4 -source 1.4 > Compiling 167 source files to > C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > Failure executing javac, but could not parse the error: > The command line is too long. > [INFO] > > [DEBUG] Trace > org.apache.maven.BuildFailureException: Compilation failure > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:551) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation > failure > at > org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:429) > at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:110) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) > ... 16 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-510) In Repository Browse, the first unique snapshot version clicked is getting persisted in the request resulting to 'version does not match' error
[ http://jira.codehaus.org/browse/MRM-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-510. -- Resolution: Fixed Fixed in archiva/trunk revision 579856. > In Repository Browse, the first unique snapshot version clicked is getting > persisted in the request resulting to 'version does not match' error > --- > > Key: MRM-510 > URL: http://jira.codehaus.org/browse/MRM-510 > Project: Archiva > Issue Type: Bug > Components: browser >Affects Versions: 1.0-beta-2 >Reporter: Maria Odea Ching >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > The first unique snapshot version you clicked is getting persisted in the > request that's why the DatabaseUnprocessedArtifactConsumer gets the 'version > does not match' error when the actual requested artifact's pom file is > compared with the version in the request. > Let's say you have the following in your repository, so from the Browse page.. > [top] / org / jruby / plugins / jruby-rake-plugin > Versions > * 1.0RC1-20070504.153317-1/ > * 1.0RC1-20070504.160758-2/ > * 1.0RC1-20070505.090015-3/ > * 1.0RC1-20070506.090132-4/ > * 1.0RC1-SNAPSHOT/ > 1. Click 1.0RC1-20070504.160758-2, the artifact info will be displayed. > 2. Now go back to the previous page and click 1.0RC1-20070504.153317-1, this > would be displayed 'Unable to find project model for > [org.jruby.plugins:jruby-rake-plugin:1.0RC1-20070504.153317-1].' in the > page.. and from the logs you will see the following error: > jvm 1| 2007-09-19 10:08:29,594 [SocketListener0-1] WARN > org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project > - Project Model groupId = 'org.jruby.plugins' > jvm 1| artifactId = 'jruby-rake-plugin' > jvm 1| version = '1.0RC1-20070504.160758-2' version: > 1.0RC1-20070504.160758-2 does not match the pom file's version: > 1.0RC1-20070504.153317-1 > jvm 1| 2007-09-19 10:08:29,597 [SocketListener0-1] WARN > org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project > - Invalid or corrupt pom. Project model groupId = 'org.jruby.plugins' > 3. Go back again to the previous page and click 1.0RC1-20070506.090132-4, > this would be displayed 'Unable to find project model for > [org.jruby.plugins:jruby-rake-plugin:1.0RC1-20070506.090132-4].' in the > page.. and from the logs you will see the following error: > jvm 1| 2007-09-19 10:08:05,957 [SocketListener0-1] WARN > org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project > - Project Model groupId = 'org.jruby.plugins' > jvm 1| artifactId = 'jruby-rake-plugin' > jvm 1| version = '1.0RC1-20070504.160758-2' version: > 1.0RC1-20070504.160758-2 does not match the pom file's version: > 1.0RC1-20070506.090132-4 > jvm 1| 2007-09-19 10:08:06,350 [SocketListener0-1] WARN > org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project > - Invalid or corrupt pom. Project model groupId = 'org.jruby.plugins' > Notice that the one being added in the database is still the first unique > version you clicked, which is 1.0RC1-20070504.160758-2. -- 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-526) cache-failure policy timeout should be easily configurable
cache-failure policy timeout should be easily configurable -- Key: MRM-526 URL: http://jira.codehaus.org/browse/MRM-526 Project: Archiva Issue Type: Improvement Reporter: JR Boyens set in a plexus.xml deep in archiva-policy.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-513) Support remote repositories with passwords
[ http://jira.codehaus.org/browse/MRM-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James William Dumay updated MRM-513: Attachment: archiva-remote-auth.patch Here is an implementation of password auth. > Support remote repositories with passwords > -- > > Key: MRM-513 > URL: http://jira.codehaus.org/browse/MRM-513 > Project: Archiva > Issue Type: Wish > Components: remote proxy >Affects Versions: 1.0-beta-1, 1.0-beta-2 >Reporter: James William Dumay >Assignee: James William Dumay > Fix For: 1.0-beta-3 > > Attachments: archiva-remote-auth.patch > > > Support remote repositories with passwords. > Currently archiva cannot authenticate to other http auth protected > repositories. -- 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: (MDEP-115) Dependency sort mojo
[ http://jira.codehaus.org/browse/MDEP-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108374 ] Brian Fox commented on MDEP-115: Interesting. Can you include some unit tests and site docs? > Dependency sort mojo > > > Key: MDEP-115 > URL: http://jira.codehaus.org/browse/MDEP-115 > Project: Maven 2.x Dependency Plugin > Issue Type: New Feature >Affects Versions: 2.0-alpha-4 >Reporter: Paul Gier >Assignee: Brian Fox > Attachments: maven-dependency-plugin-r579844.patch > > > I have a few projects that have a large number of dependencies. I would like > to be able to sort them into alphabetical order for easier readability. Also > sometimes the same dependency gets copied and pasted and there is a > duplicate. I created the sort mojo to sort dependencies in alphabetical > order and optionally remove duplicates and group the dependencies by their > scope. -- 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: (MDEP-115) Dependency sort mojo
Dependency sort mojo Key: MDEP-115 URL: http://jira.codehaus.org/browse/MDEP-115 Project: Maven 2.x Dependency Plugin Issue Type: New Feature Affects Versions: 2.0-alpha-4 Reporter: Paul Gier Assignee: Brian Fox Attachments: maven-dependency-plugin-r579844.patch I have a few projects that have a large number of dependencies. I would like to be able to sort them into alphabetical order for easier readability. Also sometimes the same dependency gets copied and pasted and there is a duplicate. I created the sort mojo to sort dependencies in alphabetical order and optionally remove duplicates and group the dependencies by their scope. -- 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-583) Show the build queue on the web/xmlrpc interface
[ http://jira.codehaus.org/browse/CONTINUUM-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108373 ] Olivier Lamy commented on CONTINUUM-583: svn rev 579843 start this. But not xmlrpc interface and improvement on rev 579843 to display the "in progress" build. > Show the build queue on the web/xmlrpc interface > > > Key: CONTINUUM-583 > URL: http://jira.codehaus.org/browse/CONTINUUM-583 > Project: Continuum > Issue Type: New Feature > Components: Web interface, XMLRPC Interface >Reporter: Henri Yandell >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > It would be very nice to be able to see the build queue on the web interface. > The current interface shows whether things are in progress, or in queue; but > not what the order is. -- 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-1287) editable build queue
[ http://jira.codehaus.org/browse/CONTINUUM-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1287. --- Resolution: Fixed svn rev 579843 > editable build queue > > > Key: CONTINUUM-1287 > URL: http://jira.codehaus.org/browse/CONTINUUM-1287 > Project: Continuum > Issue Type: New Feature >Affects Versions: 1.1-alpha-1 >Reporter: Eirik Maus >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > It should be possible to interact with the build queue. > - to see the order of the modules in queue > - to remove entries if you want to cancel the build. -- 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-1331) create new page: show current build queue with project name, next build time
[ http://jira.codehaus.org/browse/CONTINUUM-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1331. --- Resolution: Fixed svn rev 579843. > create new page: show current build queue with project name, next build time > > > Key: CONTINUUM-1331 > URL: http://jira.codehaus.org/browse/CONTINUUM-1331 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Affects Versions: 1.1-alpha-2 >Reporter: tony nys >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > show current build queue with project name, next build time -- 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: (MWAR-119) Update plexus-utils to 1.2
[ http://jira.codehaus.org/browse/MWAR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108363 ] Aaron Digulla commented on MWAR-119: If you use the plugin with maven 2.0.6+, it will throw funny error messages if plexus-utils is out of date, so I can't see how you can avoid this (except maybe by patching plexus to work with all versions of maven 2.0.x). > Update plexus-utils to 1.2 > -- > > Key: MWAR-119 > URL: http://jira.codehaus.org/browse/MWAR-119 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Aaron Digulla >Assignee: Stephane Nicoll > > Please update plexus-utils to 1.2 (see > [http://jira.codehaus.org/browse/MRESOURCES-10]). -- 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-1492) error when trying to run data management tool when behind a proxied firewall
[ http://jira.codehaus.org/browse/CONTINUUM-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108365 ] Tomislav Stojcevich commented on CONTINUUM-1492: A workaround was to download data-management-cli.1.1-beta-3-app.pom manually from the repo, save it as pom.xml, than run mvn dependency:resolve. That downloads all required dependencies into my local repo and does use the proxy settings in settings.xml. > error when trying to run data management tool when behind a proxied firewall > > > Key: CONTINUUM-1492 > URL: http://jira.codehaus.org/browse/CONTINUUM-1492 > Project: Continuum > Issue Type: Bug > Components: Data Management >Affects Versions: 1.1-beta-3 >Reporter: Tomislav Stojcevich > > Using -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80 > -Dproxy.User=myuserid -Dhttp.proxyPassword=mypassword doesn't work > Setting -Djava.net.useSystemProxies=true doesn't work > Setting -Dhttp.auth.ntlm.domain=mydomain doesn't work > Nor does it pick up the proxy settings in my settings.xml file. > 0 [main] INFO org.apache.maven.continuum.management.DataManagementCli - > Processing Continuum database... > Exception in thread "main" > org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: > Missing: > -- > 1) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.continuum > -DartifactId=data-management-jdo \ > -Dversion=1.1-beta-3 -Dpackaging=jar -Dfile=/path/to/file > Path to dependency: > 1) dummy:dummy:pom:1.0 > 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3 > -- > 1 required artifact is missing. > for artifact: > dummy:dummy:pom:1.0 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243) > at > org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:292) > at > org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:173) > at > org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:146) -- 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-525) Typos on the hacking page
[
http://jira.codehaus.org/browse/MRM-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Mayorga Adame closed MRM-525.
--
Resolution: Fixed
Fix Version/s: 1.0-beta-3
> Typos on the hacking page
> -
>
> Key: MRM-525
> URL: http://jira.codehaus.org/browse/MRM-525
> Project: Archiva
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 1.0-beta-2
>Reporter: Alex Mayorga Adame
>Assignee: Alex Mayorga Adame
>Priority: Trivial
> Fix For: 1.0-beta-3
>
> Attachments: MRM-525.patch
>
>
> Julien Graglia reported the following typos on the [mailing list |
> http://www.nabble.com/forum/ViewPost.jtp?post=12896988]
> {quote}
> Hi,
> I'am not sure it's the correct place but there are 2 little mistakes in
> http://maven.apache.org/archiva/hacking/index.html
> in section "Building Archiva"
> 1/the links to dl the connector and jta are broken : they include the
> corrects url but with a "download from..." prefix
> 2/the install command of jta is broken : a '-' is missing before
> Dversion=1.0.1B
> mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta
> -Dversion=1.0.1B -Dpackaging=jar -Dfile=jta-1_0_1B-classes.zip
> thats no real pbs, because if you start building archiva, you surely
> found (and correct) easyly those problems!
> --
> Julien Graglia
> {quote}
--
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-525) Typos on the hacking page
[
http://jira.codehaus.org/browse/MRM-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Mayorga Adame updated MRM-525:
---
Attachment: MRM-525.patch
Attaching this small patch.
> Typos on the hacking page
> -
>
> Key: MRM-525
> URL: http://jira.codehaus.org/browse/MRM-525
> Project: Archiva
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 1.0-beta-2
>Reporter: Alex Mayorga Adame
>Assignee: Alex Mayorga Adame
>Priority: Trivial
> Fix For: 1.0-beta-3
>
> Attachments: MRM-525.patch
>
>
> Julien Graglia reported the following typos on the [mailing list |
> http://www.nabble.com/forum/ViewPost.jtp?post=12896988]
> {quote}
> Hi,
> I'am not sure it's the correct place but there are 2 little mistakes in
> http://maven.apache.org/archiva/hacking/index.html
> in section "Building Archiva"
> 1/the links to dl the connector and jta are broken : they include the
> corrects url but with a "download from..." prefix
> 2/the install command of jta is broken : a '-' is missing before
> Dversion=1.0.1B
> mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta
> -Dversion=1.0.1B -Dpackaging=jar -Dfile=jta-1_0_1B-classes.zip
> thats no real pbs, because if you start building archiva, you surely
> found (and correct) easyly those problems!
> --
> Julien Graglia
> {quote}
--
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-1492) error when trying to run data management tool when behind a proxied firewall
error when trying to run data management tool when behind a proxied firewall Key: CONTINUUM-1492 URL: http://jira.codehaus.org/browse/CONTINUUM-1492 Project: Continuum Issue Type: Bug Components: Data Management Affects Versions: 1.1-beta-3 Reporter: Tomislav Stojcevich Using -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80 -Dproxy.User=myuserid -Dhttp.proxyPassword=mypassword doesn't work Setting -Djava.net.useSystemProxies=true doesn't work Setting -Dhttp.auth.ntlm.domain=mydomain doesn't work Nor does it pick up the proxy settings in my settings.xml file. 0 [main] INFO org.apache.maven.continuum.management.DataManagementCli - Processing Continuum database... Exception in thread "main" org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.continuum -DartifactId=data-management-jdo \ -Dversion=1.1-beta-3 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) dummy:dummy:pom:1.0 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3 -- 1 required artifact is missing. for artifact: dummy:dummy:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243) at org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:292) at org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:173) at org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:146) -- 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-525) Typos on the hacking page
Typos on the hacking page
-
Key: MRM-525
URL: http://jira.codehaus.org/browse/MRM-525
Project: Archiva
Issue Type: Improvement
Components: documentation
Affects Versions: 1.0-beta-2
Reporter: Alex Mayorga Adame
Priority: Trivial
Julien Graglia reported the following typos on the [mailing list |
http://www.nabble.com/forum/ViewPost.jtp?post=12896988]
{quote}
Hi,
I'am not sure it's the correct place but there are 2 little mistakes in
http://maven.apache.org/archiva/hacking/index.html
in section "Building Archiva"
1/the links to dl the connector and jta are broken : they include the
corrects url but with a "download from..." prefix
2/the install command of jta is broken : a '-' is missing before
Dversion=1.0.1B
mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta
-Dversion=1.0.1B -Dpackaging=jar -Dfile=jta-1_0_1B-classes.zip
thats no real pbs, because if you start building archiva, you surely
found (and correct) easyly those problems!
--
Julien Graglia
{quote}
--
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: (MWAR-120) Option containerConfigXML doesn't work
[ http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108362 ] Aaron Digulla commented on MWAR-120: Maybe this is a regression because of an update of plexus? I tried to plexus-utils 1.1 and 1.2 (just replaced the version in the pom of the war plugin) but it works with neither version. If you could give me some pointers where the file ought to be included, I can try to debug this if you can't reproduce it. > Option containerConfigXML doesn't work > -- > > Key: MWAR-120 > URL: http://jira.codehaus.org/browse/MWAR-120 > Project: Maven 2.x War Plugin > Issue Type: Bug >Reporter: Aaron Digulla > Attachments: context-bug.zip > > > The file specified with containerConfigXML is copied to the exploded WAR > directory but it will not end up in the final WAR. -- 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: (MRELEASE-217) BUILD FAILURE: The version could not be updated: ${version}
[
http://jira.codehaus.org/browse/MRELEASE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108361
]
Ian Springer commented on MRELEASE-217:
---
I am still getting this error with v2.0-beta-6 (mvn 2.0.7). I am doing the same
thing David was - using a custom version property in internal dependencies.
This custom version property is set in my root pom, which the pom in question
inherits from. What do I need to do to make this work?
Thanks,
Ian
> BUILD FAILURE: The version could not be updated: ${version}
> ---
>
> Key: MRELEASE-217
> URL: http://jira.codehaus.org/browse/MRELEASE-217
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-5
> Environment: XP Pro SP2
>Reporter: David Hoffer
>Assignee: Emmanuel Venisse
>Priority: Critical
> Fix For: 2.0-beta-6
>
> Attachments: buildlog.txt, poms-for-release-plugin.zip
>
>
> I manually built 2.0-beta-5 from maven-release-1 tag because of bug in
> 2.0-beta-4. I have found a problem using 2.0-beta-5 with a large
> multi-module project which makes heavy use of ${version} macros. This macro
> is used for the version for any dependency on modules within each module.
> For example in one module where I have a dependency on 3 other modules I have
> this:
>
>
> com.xrite
> xdsiii-driver-api
> ${version}
>
>
> com.xrite
> xdsiii-driver
> ${version}
>
>
> com.xrite
> xdsiii-instrument-dtp22
> ${version}
>
> When I run the prepare phase I get the following error:
> [INFO] Transforming 'X-Rite XDSIII Instrument Drivers'...
> [INFO] Transforming 'X-Rite XDSIII Base Instrument'...
> [INFO] Transforming 'X-Rite XDSIII DTP22 Instrument'...
> [INFO] Updating xdsiii-instrument-base to 1.84
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] The version could not be updated: ${version}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: The version could not be updated:
> ${version}
> It starts updating the poms with the new release version and then fails part
> way through the process.
> I will attach some files:
--
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-510) In Repository Browse, the first unique snapshot version clicked is getting persisted in the request resulting to 'version does not match' error
[ http://jira.codehaus.org/browse/MRM-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-510 started by Joakim Erdfelt. > In Repository Browse, the first unique snapshot version clicked is getting > persisted in the request resulting to 'version does not match' error > --- > > Key: MRM-510 > URL: http://jira.codehaus.org/browse/MRM-510 > Project: Archiva > Issue Type: Bug > Components: browser >Affects Versions: 1.0-beta-2 >Reporter: Maria Odea Ching >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > The first unique snapshot version you clicked is getting persisted in the > request that's why the DatabaseUnprocessedArtifactConsumer gets the 'version > does not match' error when the actual requested artifact's pom file is > compared with the version in the request. > Let's say you have the following in your repository, so from the Browse page.. > [top] / org / jruby / plugins / jruby-rake-plugin > Versions > * 1.0RC1-20070504.153317-1/ > * 1.0RC1-20070504.160758-2/ > * 1.0RC1-20070505.090015-3/ > * 1.0RC1-20070506.090132-4/ > * 1.0RC1-SNAPSHOT/ > 1. Click 1.0RC1-20070504.160758-2, the artifact info will be displayed. > 2. Now go back to the previous page and click 1.0RC1-20070504.153317-1, this > would be displayed 'Unable to find project model for > [org.jruby.plugins:jruby-rake-plugin:1.0RC1-20070504.153317-1].' in the > page.. and from the logs you will see the following error: > jvm 1| 2007-09-19 10:08:29,594 [SocketListener0-1] WARN > org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project > - Project Model groupId = 'org.jruby.plugins' > jvm 1| artifactId = 'jruby-rake-plugin' > jvm 1| version = '1.0RC1-20070504.160758-2' version: > 1.0RC1-20070504.160758-2 does not match the pom file's version: > 1.0RC1-20070504.153317-1 > jvm 1| 2007-09-19 10:08:29,597 [SocketListener0-1] WARN > org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project > - Invalid or corrupt pom. Project model groupId = 'org.jruby.plugins' > 3. Go back again to the previous page and click 1.0RC1-20070506.090132-4, > this would be displayed 'Unable to find project model for > [org.jruby.plugins:jruby-rake-plugin:1.0RC1-20070506.090132-4].' in the > page.. and from the logs you will see the following error: > jvm 1| 2007-09-19 10:08:05,957 [SocketListener0-1] WARN > org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project > - Project Model groupId = 'org.jruby.plugins' > jvm 1| artifactId = 'jruby-rake-plugin' > jvm 1| version = '1.0RC1-20070504.160758-2' version: > 1.0RC1-20070504.160758-2 does not match the pom file's version: > 1.0RC1-20070506.090132-4 > jvm 1| 2007-09-19 10:08:06,350 [SocketListener0-1] WARN > org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project > - Invalid or corrupt pom. Project model groupId = 'org.jruby.plugins' > Notice that the one being added in the database is still the first unique > version you clicked, which is 1.0RC1-20070504.160758-2. -- 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-1491) Build history screen should show build definition description
Build history screen should show build definition description - Key: CONTINUUM-1491 URL: http://jira.codehaus.org/browse/CONTINUUM-1491 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1-beta-3 Environment: xp,svn Reporter: Dan Tran I have a build that contains many build definitions( site, integration test per database, etc ) running in group ( ie using one scheduler) Without the build definition description, it is quite difficult to figure out which result belonging to which definition -- 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: (MENFORCER-16) Small changes to generated site
[ http://jira.codehaus.org/browse/MENFORCER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MENFORCER-16. -- Resolution: Fixed Fix Version/s: 1.0-alpha-3 I've been meaning to fix that. Thanks, patch applied and site deployed (will take a bit to sync) > Small changes to generated site > --- > > Key: MENFORCER-16 > URL: http://jira.codehaus.org/browse/MENFORCER-16 > Project: Maven 2.x Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Affects Versions: 1.0-alpha-3 >Reporter: Paul Gier >Assignee: Brian Fox >Priority: Minor > Fix For: 1.0-alpha-3 > > Attachments: maven-enforcer-plugin-r579780.patch > > > I noticed that some of the standard rules were not included in the main site > menu. This is probably because as the number of rules increases, the menu > starts to get too big. Maybe it would be better to just have a single menu > item that links to the rules index page. That way the menu won't keep > growing if more standard rules are added. > I also attached a small formatting fix to the RequireProperty page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1490) Include data-management-cli jar in the distribution
Include data-management-cli jar in the distribution
---
Key: CONTINUUM-1490
URL: http://jira.codehaus.org/browse/CONTINUUM-1490
Project: Continuum
Issue Type: Improvement
Components: Data Management
Affects Versions: 1.1-beta-3
Reporter: Tomislav Stojcevich
It's kind of painful to have to go to the repo to download the data-managment
jar, especially since there is no working direct link
http://maven.apache.org/continuum/guides/mini/guide-data-management.html
The link has ${version} so you have to copy the link, go to url and manually
modify the version in 2 places.
--
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: (MENFORCER-16) Small changes to generated site
Small changes to generated site --- Key: MENFORCER-16 URL: http://jira.codehaus.org/browse/MENFORCER-16 Project: Maven 2.x Enforcer Plugin Issue Type: Improvement Components: Plugin Affects Versions: 1.0-alpha-3 Reporter: Paul Gier Assignee: Brian Fox Priority: Minor Attachments: maven-enforcer-plugin-r579780.patch I noticed that some of the standard rules were not included in the main site menu. This is probably because as the number of rules increases, the menu starts to get too big. Maybe it would be better to just have a single menu item that links to the rules index page. That way the menu won't keep growing if more standard rules are added. I also attached a small formatting fix to the RequireProperty page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1736) jMesa 2.2.1 upload
jMesa 2.2.1 upload -- Key: MAVENUPLOAD-1736 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1736 Project: maven-upload-requests Issue Type: Bug Reporter: Olivier Lamy jMesa is the new version of extremeTable taglib -- 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-1489) replace use of MungedHttpsURL with commons-httpclient
[ http://jira.codehaus.org/browse/CONTINUUM-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108350 ] Emmanuel Venisse commented on CONTINUUM-1489: - plexus registry must be use in continuum-configuration like it's done in archiva-configuration > replace use of MungedHttpsURL with commons-httpclient > -- > > Key: CONTINUUM-1489 > URL: http://jira.codehaus.org/browse/CONTINUUM-1489 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-beta-2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > Actually it's impossible to download a project via http through a proxy. > Related threads > * > http://www.nabble.com/Configure-Continuum-to-use-an-HTTP-proxy-tf4514961s177.html > * > http://mail-archives.apache.org/mod_mbox/maven-continuum-dev/200709.mbox/[EMAIL > PROTECTED] > Configuring proxy values via plexus registry. -- 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-524) Determine HTTP Cache-Control rules for all repository content.
Determine HTTP Cache-Control rules for all repository content. -- Key: MRM-524 URL: http://jira.codehaus.org/browse/MRM-524 Project: Archiva Issue Type: Task Components: repository interface Affects Versions: 1.0-beta-2 Reporter: Joakim Erdfelt With the recently added Cache-Control on maven-metadata.xml files from MRM-503, it becomes apparent that we need to investigate the Cache-Control rules for other repository content such as ... * Release Artifacts * Snapshot Artifacts * Hashcodes (sha1, md5) -- 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-503) Metadata files need Pragma:no-cache response header.
[ http://jira.codehaus.org/browse/MRM-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-503. -- Resolution: Fixed Applied 2 headers on HTTP Response for maven-metadata.xml files. Pragma: no-cache Cache-Control: no-cache Commited in revision 579747 > Metadata files need Pragma:no-cache response header. > > > Key: MRM-503 > URL: http://jira.codehaus.org/browse/MRM-503 > Project: Archiva > Issue Type: Bug > Components: repository interface >Affects Versions: 1.0-beta-1 >Reporter: Joakim Erdfelt >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > The Pragma:no-cache header on the HTTP response should be set on responses of > maven-metadata.xml files. > This should be done to be friendly to network-proxies that are in the path > between the client and the archiva server. -- 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-1484) Allow customization of email subject
[ http://jira.codehaus.org/browse/CONTINUUM-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1484: Summary: Allow customization of email subject (was: Add project version to email subject) > Allow customization of email subject > > > Key: CONTINUUM-1484 > URL: http://jira.codehaus.org/browse/CONTINUUM-1484 > Project: Continuum > Issue Type: Improvement > Components: Notifier - Mail >Affects Versions: 1.1-beta-3 >Reporter: Tomislav Stojcevich >Assignee: Emmanuel Venisse >Priority: Trivial > Fix For: 1.1-beta-4 > > Attachments: CONTINUUM-1484-continuum-core-2.patch, > CONTINUUM-1484-continuum-core.patch, CONTINUUM-1484-continuum-webapp.patch, > CONTINUUM-1484.patch > > > The addition of the version of the project in the mail notification subject > would be helpful in the case where there are multiple versions of the same > project defined within continuum. > Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1484) Add project version to email subject
[ http://jira.codehaus.org/browse/CONTINUUM-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108336 ] Tomislav Stojcevich commented on CONTINUUM-1484: Not sure if it's possible but if you could change the subject of this issue to something like: Allow customization of email subject It might make is stand out better in the change log for the next release since it's more than just the version. > Add project version to email subject > > > Key: CONTINUUM-1484 > URL: http://jira.codehaus.org/browse/CONTINUUM-1484 > Project: Continuum > Issue Type: Improvement > Components: Notifier - Mail >Affects Versions: 1.1-beta-3 >Reporter: Tomislav Stojcevich >Assignee: Emmanuel Venisse >Priority: Trivial > Fix For: 1.1-beta-4 > > Attachments: CONTINUUM-1484-continuum-core-2.patch, > CONTINUUM-1484-continuum-core.patch, CONTINUUM-1484-continuum-webapp.patch, > CONTINUUM-1484.patch > > > The addition of the version of the project in the mail notification subject > would be helpful in the case where there are multiple versions of the same > project defined within continuum. > Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1484) Add project version to email subject
[ http://jira.codehaus.org/browse/CONTINUUM-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108335 ] Emmanuel Venisse commented on CONTINUUM-1484: - Thanks, I'll review it > Add project version to email subject > > > Key: CONTINUUM-1484 > URL: http://jira.codehaus.org/browse/CONTINUUM-1484 > Project: Continuum > Issue Type: Improvement > Components: Notifier - Mail >Affects Versions: 1.1-beta-3 >Reporter: Tomislav Stojcevich >Assignee: Emmanuel Venisse >Priority: Trivial > Fix For: 1.1-beta-4 > > Attachments: CONTINUUM-1484-continuum-core-2.patch, > CONTINUUM-1484-continuum-core.patch, CONTINUUM-1484-continuum-webapp.patch, > CONTINUUM-1484.patch > > > The addition of the version of the project in the mail notification subject > would be helpful in the case where there are multiple versions of the same > project defined within continuum. > Patch 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: (CONTINUUM-1484) Add project version to email subject
[ http://jira.codehaus.org/browse/CONTINUUM-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomislav Stojcevich updated CONTINUUM-1484: --- Attachment: CONTINUUM-1484.patch Try this one from the continuum parent level, it combines changes to both webapp and core. > Add project version to email subject > > > Key: CONTINUUM-1484 > URL: http://jira.codehaus.org/browse/CONTINUUM-1484 > Project: Continuum > Issue Type: Improvement > Components: Notifier - Mail >Affects Versions: 1.1-beta-3 >Reporter: Tomislav Stojcevich >Assignee: Emmanuel Venisse >Priority: Trivial > Fix For: 1.1-beta-4 > > Attachments: CONTINUUM-1484-continuum-core-2.patch, > CONTINUUM-1484-continuum-core.patch, CONTINUUM-1484-continuum-webapp.patch, > CONTINUUM-1484.patch > > > The addition of the version of the project in the mail notification subject > would be helpful in the case where there are multiple versions of the same > project defined within continuum. > Patch 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] Closed: (MRM-522) https remote repository is added as managed repository
[ http://jira.codehaus.org/browse/MRM-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-522. -- Assignee: Joakim Erdfelt Resolution: Duplicate Fix Version/s: 1.0-beta-2 This has been fixed already in 1.0-beta-2. Please upgrade. > https remote repository is added as managed repository > -- > > Key: MRM-522 > URL: http://jira.codehaus.org/browse/MRM-522 > Project: Archiva > Issue Type: Bug > Components: repository interface >Affects Versions: 1.0-beta-1 > Environment: Solaris >Reporter: Dennis Kieselhorst >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-2 > > > Tried to add https://maven-repository.dev.java.net/nonav/repository/ as Maven > 1.x repository...result is a managed repository: > Directory > /maven/archiva/apache-archiva-1.0-beta-1/bin/solaris-sparc-32/https:/maven-repository.dev.java.net/nonav/repository/ > It works if I use http instead of https. Copied it from: > http://repo1.maven.org/maven2/log4j/log4j/1.2.15/log4j-1.2.15.pom -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-523) Appearance Actions do not work when ${user.home} is invalid.
[
http://jira.codehaus.org/browse/MRM-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt updated MRM-523:
---
Assignee: Brett Porter
Affects Version/s: 1.0-beta-2
Fix Version/s: 1.0-beta-3
Component/s: system
> Appearance Actions do not work when ${user.home} is invalid.
>
>
> Key: MRM-523
> URL: http://jira.codehaus.org/browse/MRM-523
> Project: Archiva
> Issue Type: Bug
> Components: system
>Affects Versions: 1.0-beta-2
>Reporter: Joakim Erdfelt
>Assignee: Brett Porter
> Fix For: 1.0-beta-3
>
>
> The reliance on maven core components with regards to Appearance / Company
> Info / Edit Pom actions, prevents server installations without a valid user
> $HOME directory. ( such as /dev/null )
> We should migrate away from maven core components at our earliest opportunity.
--
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-523) Appearance Actions do not work when ${user.home} is invalid.
Appearance Actions do not work when ${user.home} is invalid.
Key: MRM-523
URL: http://jira.codehaus.org/browse/MRM-523
Project: Archiva
Issue Type: Bug
Reporter: Joakim Erdfelt
The reliance on maven core components with regards to Appearance / Company Info
/ Edit Pom actions, prevents server installations without a valid user $HOME
directory. ( such as /dev/null )
We should migrate away from maven core components at our earliest opportunity.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-189) Coordinate the efforts of several users to write a Dashboard Plugin for Maven 2
[ http://jira.codehaus.org/browse/MSITE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gisbert Amm closed MSITE-189. - Resolution: Fixed obsolete because of http://mojo.codehaus.org/dashboard-maven-plugin/ Absolutely great news! Thanks to the French Postal Service (La Poste)! > Coordinate the efforts of several users to write a Dashboard Plugin for Maven > 2 > --- > > Key: MSITE-189 > URL: http://jira.codehaus.org/browse/MSITE-189 > Project: Maven 2.x Site Plugin > Issue Type: Task >Reporter: Gisbert Amm > Attachments: dashboard.zip, screenshot-1.jpg > > > Coordinate the efforts of several users to write a Dashboard Plugin for Maven > 2 > Several people started their own Dashboard plugins (see > http://jira.codehaus.org/browse/MSITE-188 and discussions on the users > mailing list). It would be better, if one of those implementations would be > adopted by the Maven team and the various development efforts would be > coordinated and focused to that one. -- 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-522) https remote repository is added as managed repository
https remote repository is added as managed repository -- Key: MRM-522 URL: http://jira.codehaus.org/browse/MRM-522 Project: Archiva Issue Type: Bug Components: repository interface Affects Versions: 1.0-beta-1 Environment: Solaris Reporter: Dennis Kieselhorst Tried to add https://maven-repository.dev.java.net/nonav/repository/ as Maven 1.x repository...result is a managed repository: Directory /maven/archiva/apache-archiva-1.0-beta-1/bin/solaris-sparc-32/https:/maven-repository.dev.java.net/nonav/repository/ It works if I use http instead of https. Copied it from: http://repo1.maven.org/maven2/log4j/log4j/1.2.15/log4j-1.2.15.pom -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1484) Add project version to email subject
[ http://jira.codehaus.org/browse/CONTINUUM-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108323 ] Emmanuel Venisse commented on CONTINUUM-1484: - Can you regenerate your patch from trunk, I can't apply it. > Add project version to email subject > > > Key: CONTINUUM-1484 > URL: http://jira.codehaus.org/browse/CONTINUUM-1484 > Project: Continuum > Issue Type: Improvement > Components: Notifier - Mail >Affects Versions: 1.1-beta-3 >Reporter: Tomislav Stojcevich >Assignee: Emmanuel Venisse >Priority: Trivial > Fix For: 1.1-beta-4 > > Attachments: CONTINUUM-1484-continuum-core-2.patch, > CONTINUUM-1484-continuum-core.patch, CONTINUUM-1484-continuum-webapp.patch > > > The addition of the version of the project in the mail notification subject > would be helpful in the case where there are multiple versions of the same > project defined within continuum. > Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108312 ] Arnaud Heritier commented on MECLIPSE-264: -- ok, thanks a lot. I'll review and apply them ASAP. > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.4 >Reporter: Geir Pettersen >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: maven-264.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-264: - Affects Version/s: 2.4 Fix Version/s: 2.5 > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.4 >Reporter: Geir Pettersen >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: maven-264.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-264: - Patch Submitted: [Yes] > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.4 >Reporter: Geir Pettersen >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: maven-264.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108311 ] Cris Daniluk commented on MECLIPSE-264: --- Great. I'll probably get to redoing the patch for the latest revision later on in the week. I'll include some tests in that patch and a separate patch for docs. That page actually could use some more info on configuring the plugin via the POM, etc as well. I will open a separate issue to improve that page and include docs for this in that. > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Reporter: Geir Pettersen > Attachments: maven-264.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108310 ] Arnaud Heritier commented on MECLIPSE-264: -- yes, this is this one. No never !!! this is the only one supporting WTP ;-) > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Reporter: Geir Pettersen > Attachments: maven-264.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108309 ] Cris Daniluk commented on MECLIPSE-264: --- Would this be the correct SVN target: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/wtp.apt It looks like that is the correct site module for this one. By the way, I hope this project isn't going away because of m2eclipse. I personally far prefer this plugin. > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Reporter: Geir Pettersen > Attachments: maven-264.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108308 ] Arnaud Heritier commented on MECLIPSE-264: -- In fact this the problem of the chicken and the egg. Committers don't spent time to look at patches without docs/tests and users don't want to loose the time to create tests and update doc if they aren't sure that the patch will be applied :-) I'm not sure that this is the only page to update but this one should be to add the suport of wtp 2.0 : http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Reporter: Geir Pettersen > Attachments: maven-264.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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: (MWAR-120) Option containerConfigXML doesn't work
[ http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108306 ] Stephane Nicoll commented on MWAR-120: -- Funny. I guess it has something to do with the way plexus build the archive. Thanks for the report > Option containerConfigXML doesn't work > -- > > Key: MWAR-120 > URL: http://jira.codehaus.org/browse/MWAR-120 > Project: Maven 2.x War Plugin > Issue Type: Bug >Reporter: Aaron Digulla > Attachments: context-bug.zip > > > The file specified with containerConfigXML is copied to the exploded WAR > directory but it will not end up in the final WAR. -- 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: (MWAR-119) Update plexus-utils to 1.2
[ http://jira.codehaus.org/browse/MWAR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108305 ] Stephane Nicoll commented on MWAR-119: -- If we do this, we are forced to use mvn 2.0.6+ Not sure if it's appropriate even though we're working on maven war plugin 2.1 > Update plexus-utils to 1.2 > -- > > Key: MWAR-119 > URL: http://jira.codehaus.org/browse/MWAR-119 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Aaron Digulla > > Please update plexus-utils to 1.2 (see > [http://jira.codehaus.org/browse/MRESOURCES-10]). -- 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: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108304 ] Cris Daniluk commented on MECLIPSE-264: --- I can put together some tests. I wasn't really interested in going the extra mile if it wasn't going to be applied :) As far as doc... where should some be added? I didn't really see any anywhere to update, but would be happy to. > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Reporter: Geir Pettersen > Attachments: maven-264.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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-3221) Infinite loop in DefaultLifecycleExecutor
[
http://jira.codehaus.org/browse/MNG-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MNG-3221:
-
Fix Version/s: 2.0.8
> Infinite loop in DefaultLifecycleExecutor
> -
>
> Key: MNG-3221
> URL: http://jira.codehaus.org/browse/MNG-3221
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.7
>Reporter: Vincent Siveton
> Fix For: 2.0.8
>
> Attachments: infinite-loop.diff
>
>
> Defining this following report:
> {code:title=MyReport.java|borderStyle=solid}
> /**
> * @goal mygoal
> * @execute phase="site"
> */
> public class MyReport
> extends AbstractMavenReport{}
> {code}
> I got this following loop:
> {noformat}
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifec
[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_108302 ] Michael Lee commented on MNG-3086: -- We have also hit this problem in our environment. All of our projects have a mix of internal and external dependencies Running: "mvn clean install" on Project A caused the problem. Running "mvn dependency:resolve" also causes the problment In our case we isolated our problem to a change in the version dependencies of our internal project WORKING CASE: Project A depends directly on exact version 1.2.4 of Project B Project A depends directly on exact version 1.1.2 of Project C Project C depends directly on exact version 1.2.4 of Project B i.e. Project A, and it's dedendency C, both agree on the specific version of B required. FAILING CASE 1: We build a new version of Project B to make it vesion 1.2.5 We change the Project A dependency to depend on version 1.2.5 of Project B Project A depends directly on exact version 1.1.2 of Project C Project C continues to depend directly on exact version 1.2.4 of Project B The difference in version now triggers the getTrail error FAILING CASE 2: We change the Project A dependency to depend on version 1.2.5 of Project B We update Project C to depend on range of Project B i.e. [1.2.5,) and we rebuild Project C to create version 1.1.3 (i.e. new build just to change the dependency) We update Project A to depent directly on exact version 1.1.3 of Project C I was expecting this to work, but it still triggers the getTrail exception TEMPORARY RESOLUTION Building on failing case 2, I: Updated Project A to depend on a range of Project B i.e. [1.2.5,) instead of 1.2.5 Updated Project A to depend on a range of Project C i.e. [1.1.3,) instead of 1.1.3 This now works correctly. Whoever gets assigned to this bug - keep up the great work. > 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.
[jira] Commented: (MRM-519) fail to resolve artifactId for libs that contain versionKeyword in artifactId, like "maven-test-plugin"
[ http://jira.codehaus.org/browse/MRM-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108301 ] nicolas de loof commented on MRM-519: - I just discovered my patch is not applicable as it breaks use of classifiers with "-", like the official "java-with-dependencies" packaged with the assembly plugin. I quick&dirty solved this for my archiva instance by removing "test[09]*" from the versionKeyword list. Any better solution is welcome. > fail to resolve artifactId for libs that contain versionKeyword in > artifactId, like "maven-test-plugin" > --- > > Key: MRM-519 > URL: http://jira.codehaus.org/browse/MRM-519 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: nicolas de loof >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > Attachments: RepositoryLayoutUtils.patch > > > Trying to get maven-test-plugin (using maven1) fails in 404. Archiva is > searching for > "\maven\maven\test-plugin-1.8.2\maven-test-plugin-1.8.2.jar" > RepositoryLayoutUtils tries to detect the artifact Id by searching for some > version keyword in the request string. As "test[09]*" is a version keyword, > it resolves to "maven". > The attached path add the feature of checking that all tokens in the version > part - all after artifactId expect the latest (classifier) - are valid > version keywords. -- 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-1735) Esper upload to Maven
Esper upload to Maven - Key: MAVENUPLOAD-1735 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1735 Project: maven-upload-requests Issue Type: Bug Reporter: Thomas Bernhardt http://dist.codehaus.org/esper/esper-1.11.0-bundle.jar http://esper.codehaus.org http://http://xircles.codehaus.org/projects/esper/members -- 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-521) No validation for the repository purge fields in repo config
[ http://jira.codehaus.org/browse/MRM-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-521: - Fix Version/s: 1.0-beta-3 > No validation for the repository purge fields in repo config > > > Key: MRM-521 > URL: http://jira.codehaus.org/browse/MRM-521 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-1, 1.0-beta-2 >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 1.0-beta-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-521) No validation for the repository purge fields in repo config
No validation for the repository purge fields in repo config Key: MRM-521 URL: http://jira.codehaus.org/browse/MRM-521 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2, 1.0-beta-1 Reporter: Maria Odea Ching -- 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-520) Proxy Connectors are not deleted with the deletion of a Repository.
[ http://jira.codehaus.org/browse/MRM-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108289 ] Maria Odea Ching commented on MRM-520: -- Results to Error 500 when deleting the default remote repository in beta-2 version, while NPE in trunk. The repository is still deleted even with the error. > Proxy Connectors are not deleted with the deletion of a Repository. > --- > > Key: MRM-520 > URL: http://jira.codehaus.org/browse/MRM-520 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > When you delete a repository (managed or remote) if there is a proxy > connector established for that former repository, then the proxy connector > itself remains. > Desired Outcome: > # When you delete a repository, associated Proxy Connectors should be deleted > too. > # If a proxy connector is going to be deleted, this should also be outlined > in the delete confirmation screens. -- 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
