[jira] Created: (MIDEA-68) if a dependency is not found, it doesn't fail but excludes legitimate dependencies
if a dependency is not found, it doesn't fail but excludes legitimate dependencies -- Key: MIDEA-68 URL: http://jira.codehaus.org/browse/MIDEA-68 Project: Maven 2.x Idea Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Brett Porter to reproduce: - have a multiproject with a module not installed - mvn idea:idea from the root - it will succeed, but the module file for the module that depends on the missing artifact contains module dependencies, but no jar dependencies -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-74) Added muse format to doxia-core
[ http://jira.codehaus.org/browse/DOXIA-74?page=comments#action_75992 ] Arnaud Bailly commented on DOXIA-74: Here comes a new patch with I hope all issues resolved. This patch links to 1.0-rc3 version of muse-parser. Added muse format to doxia-core --- Key: DOXIA-74 URL: http://jira.codehaus.org/browse/DOXIA-74 Project: doxia Issue Type: New Feature Components: Core Affects Versions: 1.0-alpha-8 Reporter: Arnaud Bailly Priority: Minor Fix For: 1.0-alpha-8 Attachments: patch-doxia-1.0-alpha-8 As a workaround to DOXIA-68 bug, I have m\ade a patch to doxia-core-1.0-alpha-8 that include necessary code for generating maven sites from muse syntax and add a dependency to muse-parser from doxia-core pom.xml. This patch may be useful for people who wish to write their documentation using Emacs muse mode. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=all ] Richard van Nieuwenhoven updated MECLIPSE-137: -- Attachment: maven-rad-plugin.zip I have not much time to spend for support on this plugin, i made/appened it for a customer (UNIQA Austria). But still any extentions are welcome, and as long as there is no own project and it is not integerated in the eclipse plugin we should post them here. i have not the time to make and support a seperate project. Because the project (i worked on) ended successfuly, i do not work on this plugin anymore (for now). Please feel free to contact me, i will give you an email kontact of the responsible person in UNIQA Austria. They are happy to meet and work together with others also using Maven-2, RAD6 and websphere. They also ported or working on porting a lot of the was-5/6 admin ant tasks to maven-2 goals for websphere-6 integration tests. in this updated version i deleted the localreposetorys (sorry for that) so it should build anywhere now. Developed RAD-6 Plugin Extention Key: MECLIPSE-137 URL: http://jira.codehaus.org/browse/MECLIPSE-137 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Reporter: Richard van Nieuwenhoven Attachments: maven-rad-plugin.tar.gz, maven-rad-plugin.zip I just finisched developing a RAD-6 (IBM Rational Application Developer 6.0) extention to the eclipse plugin. It supports J2EE projects with the websphere development envorment, supported are - EJB projects - Web projects - EAR- projects all these projects are recognized by rad-6 as what they. The websphere development enviorment including hot-deployment features funktions out of the box. i wrote writers for: - the .j2ee files - the application.xml and the modulemaps file - copying the extrenal libs in the ear project root - adapting the MANIFEST.MF of the projects (nessesary for the websphere development enviorment) - the .websettings file - the .websiteconfig file - the .project (only alternative project natures/builders) do you want to include it the the eclipse plugin or sould it be an extra plugin? i should not be complicated to include it because i did the real work in writer-classes. should i add a tgz with the sources? or how do you want the sources? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MIDEA-64) Provided dependencies are also copied to /WEB-INF/lib
[ http://jira.codehaus.org/browse/MIDEA-64?page=comments#action_75996 ] Stephen Connolly commented on MIDEA-64: --- I can confirm this bug exists in IDEA 4.5.4, IDEA 5.1.2, and IDEA 6.0 beta. In all cases I regenerated the IDEA project files mvn idea:clean mvn idea:idea before loading in the IDE in order to eliminate contamination between IDEA versions. In our case the dependency in our pom.xml is: dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.3/version scopeprovided/scope /dependency I have checked all the poms for all of our dependencies and any that list servlet-api as a dependency also have scope set to provided. In all three versions of the IDE the WAR packaging is incorrectly set to Copy files to. Provided dependencies are also copied to /WEB-INF/lib - Key: MIDEA-64 URL: http://jira.codehaus.org/browse/MIDEA-64 Project: Maven 2.x Idea Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Geoffrey De Smet Attachments: screenshot-1.jpg A dependency with the scope provided (and probably system too) is also marked as to be copied to /WEB-INF/lib for webapp modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2579) Let META-INF/maven/../pom.properties|pom.xml be generated in generate-resources
Let META-INF/maven/../pom.properties|pom.xml be generated in generate-resources --- Key: MNG-2579 URL: http://jira.codehaus.org/browse/MNG-2579 Project: Maven 2 Issue Type: Improvement Reporter: Kenney Westerhof Some applications use the META-INF/maven/../pom.properties to read the application/jar version at runtime. This file is generated in the package phase. During unit tests, or running applications from the workspace (project tree), these files are not available, which causes problems. Suggest to move the pom.(properties|xml) generating code in the maven-jar-plugin to a separate mojo that's bound to generate-resources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SCM-239) svn-commons doesn't support svn 1.4 working copy format
[ http://jira.codehaus.org/browse/SCM-239?page=all ] Brett Porter updated SCM-239: - Attachment: entries svn-commons doesn't support svn 1.4 working copy format --- Key: SCM-239 URL: http://jira.codehaus.org/browse/SCM-239 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-svn Reporter: Brett Porter Attachments: entries testSvnFromPath(org.apache.maven.scm.provider.svn.repository.SvnScmProviderRepositoryTest) Time elapsed: 0.022 sec ERROR! org.apache.maven.scm.repository.ScmRepositoryException: Can't read /Users/brett/scm/mergere/maestro/maven-scm/maven-scm-providers/ma ven-scm-providers-svn/maven-scm-provider-svn-commons/.svn/entries at org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1516) at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392) at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090) at org.apache.maven.scm.provider.svn.util.EntriesReader.read(EntriesReader.java:57) at org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.makeProviderScmRepository(AbstractSvnScmProvider.java:119) at org.apache.maven.scm.provider.svn.repository.SvnScmProviderRepositoryTest.testSvnFromPath(SvnScmProviderRepositoryTest.ja va:134) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2580) UNC in MAVEN_HOME not working
UNC in MAVEN_HOME not working - Key: MNG-2580 URL: http://jira.codehaus.org/browse/MNG-2580 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.0.4 Environment: Windows XP Reporter: Remy COQUEUGNIOT Priority: Blocker Maven2 is installed in a corporate server : SERVER From my computer, this installation is accesible on a network share : \\SERVER\MAVEN2 From a command line I setup MAVEN_HOME with this UNC: set MAVEN_HOME=\\SERVER\MAVEN2 And put it in the PATH set PATH=%MAVEN_HOME%\bin;%PATH% When I try to build any projects, maven is unable to acces my global settings which is stored in %MAVEN_HOME%\conf\settings.xml But when I mount a network share to this UNC: net use Z: \\SERVER\MAVEN2 ...Setup MAVEN_HOME ... set MAVEN_HOME=Z:\ ...And put it in the PATH ... set PATH=%MAVEN_HOME%\bin;%PATH% The global settings.xml is read. This useCase seems OK with Maven 1. mvn -X doesn't give too any informations about the final %MAVEN_HOME%\conf which is used. But it prints the plugin-registry.xml locations which are based on the %MAVEN_HOME% In this case \\SERVER\MAVEN2 is badly transformed in C:\SERVER\MAVEN2 : set MAVEN_HOME=\\frmlefsi20\inet_dev\DEVPLATFORM\maven-2.0.4 mvn clean -X (...) [DEBUG] Building Maven global-level plugin registry from: 'C:\frmlefsi20\inet_dev\DEVPLATFORM\maven-2.0.4\bin\..\conf\plugin-registry.xml' (...) Thanks for your support and this great tool ! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-940) Provide a mechanism to pass in an scm tag parameter from the web interface
Provide a mechanism to pass in an scm tag parameter from the web interface -- Key: CONTINUUM-940 URL: http://jira.codehaus.org/browse/CONTINUUM-940 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.0.3 Environment: Platform independent Reporter: Kevin Slater Priority: Trivial It would be a good thing to have the ability to pass in a parameter to the scm layer from the projects page such that the code could be pulled from the repository based on that tag. This way a user of the web application could build an arbitrary prior (tagged) version of the artifact. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-132) Class not found when run/debug JUnit tests
[ http://jira.codehaus.org/browse/MECLIPSE-132?page=comments#action_76030 ] Brian Keyser commented on MECLIPSE-132: --- Our environment is susceptible to this enviroment as well using Eclipse 3.2 and the Maven2 Eclipse Plugin 0.0.9. I have been able to create a small test case the mirrors our environment. We separate our projects into both a source and a test project. We do this because we weave different aspects in our production and test environments. However, this configuration does expose the problem. The two projects included in the following attachment are a source (maven-sample) project and a test (maven-sample-test) project. If the JUnit dependency is removed from the maven-sample project, the NoClassDefFoundError appears when attempting to run the test cases. If the JUnit dependency is present in the maven-sample project, then the test cases can be run. However, this trick does not work for our configuration. I was also able to get Diego's suggestion to work if I added a Maven2 Dependencies above the JRE System Library in the Classpath - Bootstrap Entries of the target I was trying to run. However, this is less than ideal if you wish to choose a single test case to execute. Class not found when run/debug JUnit tests Key: MECLIPSE-132 URL: http://jira.codehaus.org/browse/MECLIPSE-132 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: dependency resolution Environment: gentoo linux 2006, kernel 2.6, sun-jdk-1.5.0.06, maven 2.0.4, eclipse sdk 3.2, myeclipse 5 m2 Reporter: Diego Ballve Attachments: maven-sample.zip This is for the behavior described in http://www.nabble.com/Keep-getting-%22Class-not-found%22-when-running-debugging-JUnit-tests-tf1851758.html#a5442440 You get Class not found when running/debuging JUnit tests. For me it happened when I was importing another project and its dependencies (both m2 projects). Clean compile works fine, problem is with run. The workaround to get it working is: In the project containing your tests, edit Java Build Path | Order and Export: Make sure M2 Dependencies appears BEFORE JRE System Library. Thanks, Diego -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-132) Class not found when run/debug JUnit tests
[ http://jira.codehaus.org/browse/MECLIPSE-132?page=all ] Brian Keyser updated MECLIPSE-132: -- Attachment: maven-sample.zip Two Eclipse projects (maven-sample and maven-sample-test) to reproduce the problem. Class not found when run/debug JUnit tests Key: MECLIPSE-132 URL: http://jira.codehaus.org/browse/MECLIPSE-132 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: dependency resolution Environment: gentoo linux 2006, kernel 2.6, sun-jdk-1.5.0.06, maven 2.0.4, eclipse sdk 3.2, myeclipse 5 m2 Reporter: Diego Ballve Attachments: maven-sample.zip This is for the behavior described in http://www.nabble.com/Keep-getting-%22Class-not-found%22-when-running-debugging-JUnit-tests-tf1851758.html#a5442440 You get Class not found when running/debuging JUnit tests. For me it happened when I was importing another project and its dependencies (both m2 projects). Clean compile works fine, problem is with run. The workaround to get it working is: In the project containing your tests, edit Java Build Path | Order and Export: Make sure M2 Dependencies appears BEFORE JRE System Library. Thanks, Diego -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-132) Class not found when run/debug JUnit tests
[ http://jira.codehaus.org/browse/MECLIPSE-132?page=comments#action_76034 ] Brian Keyser commented on MECLIPSE-132: --- Our project structure is organized into a hierarchy of projects. I have found that the complete set of libraries needs to be specified for each of the individual projects. In other words, if Project A needs libraries aa, ab, ac and Project B needs ba, bb, bc, you would need to specify aa, ab, ac, ba, bb, bc for both Project A and Project B. Looks like the plugin might be having trouble determining library dependencies. Class not found when run/debug JUnit tests Key: MECLIPSE-132 URL: http://jira.codehaus.org/browse/MECLIPSE-132 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: dependency resolution Environment: gentoo linux 2006, kernel 2.6, sun-jdk-1.5.0.06, maven 2.0.4, eclipse sdk 3.2, myeclipse 5 m2 Reporter: Diego Ballve Attachments: maven-sample.zip This is for the behavior described in http://www.nabble.com/Keep-getting-%22Class-not-found%22-when-running-debugging-JUnit-tests-tf1851758.html#a5442440 You get Class not found when running/debuging JUnit tests. For me it happened when I was importing another project and its dependencies (both m2 projects). Clean compile works fine, problem is with run. The workaround to get it working is: In the project containing your tests, edit Java Build Path | Order and Export: Make sure M2 Dependencies appears BEFORE JRE System Library. Thanks, Diego -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MWAR-78) War overlay can overwrite files in dependant war artifact
War overlay can overwrite files in dependant war artifact - Key: MWAR-78 URL: http://jira.codehaus.org/browse/MWAR-78 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0.1 Reporter: Brian Reilly Attachments: maven-war-plugin-2.0.1-overlay-bug.diff Suppose there is a war artifact A that is depended on by war artifact B. If they contain files with the same name in src/main/webapp and the timestamp in A is more recent than the timestamp in B, the file from A will be used. I don't know if it's officially stated in the docs, but I think the intention is that files in B should always win regardless of timestamp. I've attached a diff (based on the maven-war-plugin-2.0.1 tag) that adds a test case to WarExplodedMojoTest.java to demonstrate the problem. The cause seems to be the use of copyFileIfModified in AbstractWarMojo.copyDependentWarContents(). I'm not sure why this should be done (except in the case of trying to avoid triggering a hot redeploy, which doesn't apply to all files). The diff also includes changes to AbstractWarMojo.java that fix the test failures. I've created a copyFile method that is a clone of copyFileIfModified without the timestamp check. That method is then used in copyDependentWarContents instead. Additionally, I pulled in the !new File( warSourceDirectory, files[j] ).exists() check from trunk. Lastly, I had to change copyResources(File, File) to use copyFile as well in order to get the tests to pass. There may be other places where copyFileIfModified could be replaced with copyFile, but I haven't done an extensive audit of every place where copyFileIfModified is being used. I also modified the last condition of testExplodedWarMergeWarUpdated because it seemed incorrect to me and the fix that I made necessitated it. The test was explicitly making sure that the version of org/sample/company/test.jsp from simple-updated.war remained even after changing the dependency back to simple.war. Put another way, the result of the last test would be different depending on whether or not `mvn clean` is run after each dependency change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SCM-240) add support for tagging a revision
add support for tagging a revision -- Key: SCM-240 URL: http://jira.codehaus.org/browse/SCM-240 Project: Maven SCM Issue Type: Improvement Components: maven-plugin, maven-scm-api Reporter: Sharmarke Aden I am not sure if this functionality can be supported by all scm providers but in subversion one can tag a revision using the copy command. I would love to see support added to SCM so that a) one can determine the current working revision and b) based on the working revision ID create a tag. In subversion on can do this by using the following set of commands. #get the working copy revision information svn info #create a tag from the trunk using revision 1204 svn copy -r1204 http://svn.example.com/repos/calc/trunk http://svn.example.com/repos/calc/tags/release-1.0 -m revision tag Notes: My understanding is that SCM API currently does support getting the revision of the current working copy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSUREFIRE-77) Service providers are not available during unit testing when defined by dependencies
[ http://jira.codehaus.org/browse/MSUREFIRE-77?page=all ] Brett Porter updated MSUREFIRE-77: -- Attachment: MSUREFIRE-77.tar.bz2 ok, reproducible. Here's a tarball that is easier to test with as its self contained Service providers are not available during unit testing when defined by dependencies Key: MSUREFIRE-77 URL: http://jira.codehaus.org/browse/MSUREFIRE-77 Project: Maven 2.x Surefire Plugin Issue Type: Bug Reporter: Christian Schulte Attachments: jcharset-1.2.1.jar, MSUREFIRE-77.tar.bz2, MSUREFIRE77TestCase.java, pom.xml If a dependency defines some service provider by e.g. a file like META-INF/services/java.nio.charset.spi.CharsetProvider these providers are not available during unit testing. For this example an UnsupportedEncodingException would be thrown when using a charset defined in the file during unit testing. For Reference see: http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Service%20Provider or http://java.sun.com/j2se/1.5.0/docs/api/java/nio/charset/spi/CharsetProvider.html. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-939) admin configuration page on trunk isn't validated
[ http://jira.codehaus.org/browse/CONTINUUM-939?page=all ] Maria Odea Ching updated CONTINUUM-939: --- Due Date: 29/Sep/06 (was: 28/Sep/06) admin configuration page on trunk isn't validated - Key: CONTINUUM-939 URL: http://jira.codehaus.org/browse/CONTINUUM-939 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Brett Porter Assigned To: Maria Odea Ching Fix For: 1.1 Original Estimate: 10 hours Remaining Estimate: 10 hours 1) the guests checkbox is not saved 2) there is no validation - leaving fields empty does nothing -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-165) add Last-Modified header in proxy response
[ http://jira.codehaus.org/browse/MRM-165?page=all ] Brett Porter updated MRM-165: - Fix Version/s: 1.0-beta-1 add Last-Modified header in proxy response -- Key: MRM-165 URL: http://jira.codehaus.org/browse/MRM-165 Project: Archiva Issue Type: Improvement Components: remote proxy, web application Environment: maven 1.1-beta-3 Reporter: nicolas de loof Fix For: 1.0-beta-1 When used as a maven1 proxy, Archiva doesn't send Last-modified header. This cause maven 1.1-beta3 to fail due to a bug in Wagon. The wagon bug is corrected in SVN but there is no corrected maven 1.1 distribution available yet. Setting a Last-Modifier header in proxy response can solve this issue. I don't know webwork enough to add support for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-164) add a friendly cron editor for repository manager
[ http://jira.codehaus.org/browse/MRM-164?page=all ] Brett Porter closed MRM-164. Resolution: Fixed Fix Version/s: 1.0-beta-1 add a friendly cron editor for repository manager - Key: MRM-164 URL: http://jira.codehaus.org/browse/MRM-164 Project: Archiva Issue Type: Improvement Components: web application Reporter: Maria Odea Ching Assigned To: Maria Odea Ching Fix For: 1.0-beta-1 Original Estimate: 14 hours Time Spent: 23 hours, 30 minutes Remaining Estimate: 0 minutes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-169) incorrect validation on register page
[ http://jira.codehaus.org/browse/MRM-169?page=all ] Brett Porter updated MRM-169: - Fix Version/s: 1.0-beta-1 incorrect validation on register page - Key: MRM-169 URL: http://jira.codehaus.org/browse/MRM-169 Project: Archiva Issue Type: Bug Components: web application Reporter: Brett Porter Fix For: 1.0-beta-1 I noticed the following problems: - validation is not done with javascript - only username full name validation work. - if I omit email, I get a successful registration, *and* and error that email is required - if I omit confirm password, I get a successful registration - if I use an incorrect confirm password, I get a successful registration - if I reuse an email already in the system, I think I should get a failed registration -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-188) clean up security implementation
[ http://jira.codehaus.org/browse/MRM-188?page=all ] Brett Porter closed MRM-188. Assignee: Brett Porter Resolution: Fixed Fix Version/s: 1.0-beta-1 clean up security implementation Key: MRM-188 URL: http://jira.codehaus.org/browse/MRM-188 Project: Archiva Issue Type: Task Reporter: Brett Porter Assigned To: Brett Porter Fix For: 1.0-beta-1 some files got left around (eg, plexus-security.properties) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-185) revise logging granularity
[ http://jira.codehaus.org/browse/MRM-185?page=all ] Brett Porter updated MRM-185: - Fix Version/s: 1.0-beta-1 revise logging granularity -- Key: MRM-185 URL: http://jira.codehaus.org/browse/MRM-185 Project: Archiva Issue Type: Improvement Reporter: Brett Porter Fix For: 1.0-beta-1 in particular, check that JPOX logging is at the correct level, but generally turn the noise down. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1154) WSDL4J 1.6.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1154?page=all ] maomaode closed MAVENUPLOAD-1154. - Resolution: Duplicate WSDL4J 1.6.1 Key: MAVENUPLOAD-1154 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1154 Project: maven-upload-requests Issue Type: Task Reporter: maomaode http://people.apache.org/~ningjiang/m2/repository/wsdl4j/1.6.1/wsdl4j-1.6.1.jar http://wsdl4j.sourceforge.net http://sourceforge.net/project/memberlist.php?group_id=128811 The Web Services Description Language for Java Toolkit (WSDL4J) allows the creation, representation, and manipulation of WSDL documents. Is the reference implementation for JSR110 'JWSDL' (jcp.org). Post questions/bugs to [EMAIL PROTECTED] Please upload. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1158) WSDL4J 1.6.1
WSDL4J 1.6.1 Key: MAVENUPLOAD-1158 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1158 Project: maven-upload-requests Issue Type: Task Reporter: maomaode http://people.apache.org/~ningjiang/m2/repository/wsdl4j/1.6.1/wsdl4j-1.6.1-bundle.jar http://wsdl4j.sourceforge.net http://sourceforge.net/project/memberlist.php?group_id=128811 The Web Services Description Language for Java Toolkit (WSDL4J) allows the creation, representation, and manipulation of WSDL documents. Is the reference implementation for JSR110 'JWSDL' (jcp.org). Post questions/bugs to [EMAIL PROTECTED] Please upload. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-256) trace memory leak with yourkit
[ http://jira.codehaus.org/browse/CONTINUUM-256?page=comments#action_76050 ] Brett Porter commented on CONTINUUM-256: I think the issues are all resolved except that the project loader never releases memory. That's a known issue - leaving open until we can update for a version that isn't affected. trace memory leak with yourkit -- Key: CONTINUUM-256 URL: http://jira.codehaus.org/browse/CONTINUUM-256 Project: Continuum Issue Type: Bug Components: Core system Reporter: Brett Porter Fix For: 1.1 continuum has been spitting OOME in our test environment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-760) Update Derby
[ http://jira.codehaus.org/browse/CONTINUUM-760?page=all ] Brett Porter closed CONTINUUM-760. -- Assignee: Brett Porter Resolution: Fixed Update Derby Key: CONTINUUM-760 URL: http://jira.codehaus.org/browse/CONTINUUM-760 Project: Continuum Issue Type: Task Components: Database Reporter: Emmanuel Venisse Assigned To: Brett Porter Fix For: 1.1 http://db.apache.org/derby/releases/release-10.1.3.1.cgi#Release+Notes This version includes some fixes on lock deadlocks/lock timeout that we can see in some issues -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-69) Make sure /webapp only contains web resources and not classes.
[ http://jira.codehaus.org/browse/CONTINUUM-69?page=all ] Brett Porter closed CONTINUUM-69. - Resolution: Won't Fix Fix Version/s: (was: 1.1) its far more convenient during dev@ with webwork to have the action classes in the webapp. Make sure /webapp only contains web resources and not classes. -- Key: CONTINUUM-69 URL: http://jira.codehaus.org/browse/CONTINUUM-69 Project: Continuum Issue Type: Task Affects Versions: 1.0-alpha-3 Reporter: Trygve Laugstol Assigned To: Trygve Laugstol We'll need to deal with this next version, it's not critical in any way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-580) Fails to build on OS X
[ http://jira.codehaus.org/browse/CONTINUUM-580?page=all ] Brett Porter closed CONTINUUM-580. -- Assignee: Brett Porter Resolution: Fixed I can build on OS X. Fails to build on OS X -- Key: CONTINUUM-580 URL: http://jira.codehaus.org/browse/CONTINUUM-580 Project: Continuum Issue Type: Bug Components: Core system Environment: OS X Reporter: Henri Yandell Assigned To: Brett Porter Fix For: 1.1 Attachments: org.apache.maven.continuum.it.ShellIntegrationTest.txt The build currently does not complete from the 1.0.x branch of Continuum. An error occurs in the ShellIntegrationTest (see attachment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-888) Merge all fixes done in acegi branch with trunk without the acegi security features
[ http://jira.codehaus.org/browse/CONTINUUM-888?page=all ] Brett Porter closed CONTINUUM-888. -- Resolution: Fixed this was done Merge all fixes done in acegi branch with trunk without the acegi security features --- Key: CONTINUUM-888 URL: http://jira.codehaus.org/browse/CONTINUUM-888 Project: Continuum Issue Type: Bug Reporter: Marvin King Assigned To: Carlos Sanchez -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1159) WSDL4J-QNAME 1.6.1 upload
WSDL4J-QNAME 1.6.1 upload - Key: MAVENUPLOAD-1159 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1159 Project: maven-upload-requests Issue Type: Sub-task Reporter: maomaode http://people.apache.org/~ningjiang/m2/repository/wsdl4j/1.6.1/wsdl4j-qname-1.6.1-bundle.jar http://wsdl4j.sourceforge.net http://sourceforge.net/project/memberlist.php?group_id=128811 The Web Services Description Language for Java Toolkit (WSDL4J) allows the creation, representation, and manipulation of WSDL documents. Is the reference implementation for JSR110 'JWSDL' (jcp.org). Post questions/bugs to [EMAIL PROTECTED] Please upload. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
