[jira] Created: (MAVENUPLOAD-1732) upload xSocket V2.0-alpha-1
upload xSocket V2.0-alpha-1 --- Key: MAVENUPLOAD-1732 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1732 Project: maven-upload-requests Issue Type: New Feature Reporter: greg xSocket is a easy to use NIO-based library to build high performance, high scalable network applications. -- 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-513) Support remote repositories with passwords
Support remote repositories with passwords -- Key: MRM-513 URL: http://jira.codehaus.org/browse/MRM-513 Project: Archiva Issue Type: Wish Affects Versions: 1.0-beta-1, 1.0-beta-2 Reporter: James William Dumay 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: (MCLOVER-71) Cannot resolve license file
[ http://jira.codehaus.org/browse/MCLOVER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108087 ] Tom Davies commented on MCLOVER-71: --- This is fixed in 3.0-beta-4 -- see http://confluence.atlassian.com/x/K4CDBQ for details of this version. Cannot resolve license file --- Key: MCLOVER-71 URL: http://jira.codehaus.org/browse/MCLOVER-71 Project: Maven 2.x Clover Plugin Issue Type: Bug Affects Versions: 2.4 Reporter: Bryan Madsen Attachments: MavenLoader_24.diff, MCLOVER-71.diff, MCLOVER-71.diff The license file cannot be found when the license location is a URL. This works with version 2.3. [INFO] [clover:instrumentInternal] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to load license file [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] Embedded error: Could not find resource 'http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license'. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to load license file [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:896) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to load license file [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] at org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:164) at org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:134) at org.apache.maven.plugin.clover.internal.AbstractCloverMojo.execute(AbstractCloverMojo.java:119) at org.apache.maven.plugin.clover.CloverInstrumentInternalMojo.execute(CloverInstrumentInternalMojo.java:132) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 20 more Caused by: org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not find resource 'http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license'. at org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsInputStream(DefaultResourceManager.java:91) at org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:117) at org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:100) at org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:159) ... 25 more
[jira] Updated: (CONTINUUM-1397) ability to customise web templates
[ http://jira.codehaus.org/browse/CONTINUUM-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1397: Fix Version/s: 1.1 ability to customise web templates -- Key: CONTINUUM-1397 URL: http://jira.codehaus.org/browse/CONTINUUM-1397 Project: Continuum Issue Type: Improvement Components: Web - UI Affects Versions: 1.1-beta-2 Reporter: Brett Porter Fix For: 1.1 it'd be good to be able to customise the footer - for the ASF install on vmbuild I'd like to be able to link to the correct place to report issues/get help. -- 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-102) CLONE -still broken - Module filepath is generated incorrectly
[
http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108101
]
Geoffrey De Smet commented on MIDEA-102:
Confirming it doesn't work for idea 2.0 or 2.1. It's maven 2.0.7 and win xp
combination that is breaking.
Workaround
==
Make sure you still have maven 2.0.6 still installed.
Do this in your cygwin shell:
export M2_HOME=/cygdrive/c/develop/build/maven-2.0.6
mvn idea:idea
or if you're using cmd:
set M2_HOME=C:\develop\build\maven-2.0.6
mvn idea:idea
Afterwards throw away that shell instance, as it won't be using maven 2.0.7.
CLONE -still broken - Module filepath is generated incorrectly
--
Key: MIDEA-102
URL: http://jira.codehaus.org/browse/MIDEA-102
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: $ mvn -v
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: windows xp version: 5.1 arch: x86
cygwin
Reporter: Joern Huxhorn
Assignee: Dennis Lundberg
Fix For: 2.2
Attachments: maven-idea-plugin-MIDEA-102.patch
I have a multi-module mvn project.
When I do an mvn idea:clean idea:idea, the following ProjectModuleManager
snippet in the top level .ipr is generated:
component name=ProjectModuleManager
modules
!-- module filepath=$$PROJECT_DIR$$/${pom.artifactId}.iml/ --
module filepath=$PROJECT_DIR$/gateway.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml/
/modules
/component
The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
But this path is being appended in a hard-coded fashion after the
$PROJECT_DIR entry.
The symptom in Intellij is the following error message:
Cannot load module: File
C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not
exist
Would you like to remove the module from the project?
The workaround is to delete the extra appended file path from each module
entry in the above mentioned snippet.
--
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-789) Show SCM branch/tag on summary screen
[ http://jira.codehaus.org/browse/CONTINUUM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-789: --- Affects Version/s: (was: 1.0.3) 1.1-beta-3 Fix Version/s: (was: Future) 1.1-beta-4 Patch Submitted: [Yes] Show SCM branch/tag on summary screen - Key: CONTINUUM-789 URL: http://jira.codehaus.org/browse/CONTINUUM-789 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-beta-3 Reporter: thierry lach Priority: Minor Fix For: 1.1-beta-4 Attachments: CONTINUUM-789-continuum-webapp.patch Since there may be multiple revisions of a project. -- 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-409) Email notifications could still include build stats when includeBuildResult is false
[ http://jira.codehaus.org/browse/CONTINUUM-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-409: --- Affects Version/s: (was: 1.0) 1.1-beta-3 Fix Version/s: (was: Future) 1.1-beta-4 Patch Submitted: [Yes] Email notifications could still include build stats when includeBuildResult is false Key: CONTINUUM-409 URL: http://jira.codehaus.org/browse/CONTINUUM-409 Project: Continuum Issue Type: Wish Components: Notifier - Mail Affects Versions: 1.1-beta-3 Reporter: David Blevins Fix For: 1.1-beta-4 Attachments: CONTINUUM-409-continuum-core.patch I really like the Build statistics and Changes sections continuum creates in the emails and definitely want them in every email. It's really just the section that contains the output generated from the build itself that I don't want as that will consistently be several megs of text for our project. Basically, I assumed 'includeBuildResults=false' would just exclude out everything after these lines Output: I really don't care what the option is called as long as I can get an email as described. Maybe you want to do something like this includeBuildStatisticstrue/includeBuildStatistics includeChangestrue/includeChanges includeBuildOutputfalse/includeBuildOutput -- 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 ] Emmanuel Venisse updated CONTINUUM-1484: Fix Version/s: 1.1-beta-4 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 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: (CONTINUUM-1485) CVS checkout is considerably slower
[ http://jira.codehaus.org/browse/CONTINUUM-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108106 ] Emmanuel Venisse commented on CONTINUUM-1485: - do you have lot of files changed between each build? After a cvs update, continuum run a cvs log to get authors, modification dates and commit messages. CVS checkout is considerably slower --- Key: CONTINUUM-1485 URL: http://jira.codehaus.org/browse/CONTINUUM-1485 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.1-beta-2 Environment: Running on Windows XP inside Tomcat 5.5.17, communicating with CVSNT server, using CVSNT client. Reporter: Adrian Sox The project tree we are building is fairly large (5,000 files, 220 MB). It normally takes 5-6 minutes to perform a cvs update on this tree when executing from the command line or Eclipse. With Continuum 1.0.3, it took 5-6 minutes to update the project from CVS, before the actual build began. With 1.1-beta-2, it takes much longer - 15-20 minutes - to perform the same update. Build Fresh is not checked. The two versions of Continuum are set up identically in all other regards, except that 1.0.3 is run standalone, not from Tomcat. Both run on the same box, as the same user, use the same CVS executable, hit the same CVS server, use the same Java version, the same Maven 2 version, the same disk drive, ... and of course, with only one version of Continuum running at any given time. Aside from this issue, we very much like the changes in 1.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-789) Show SCM branch/tag on summary screen
[ http://jira.codehaus.org/browse/CONTINUUM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-789. -- Assignee: Emmanuel Venisse Resolution: Fixed Applied. Thanks Show SCM branch/tag on summary screen - Key: CONTINUUM-789 URL: http://jira.codehaus.org/browse/CONTINUUM-789 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-beta-3 Reporter: thierry lach Assignee: Emmanuel Venisse Priority: Minor Fix For: 1.1-beta-4 Attachments: CONTINUUM-789-continuum-webapp.patch Since there may be multiple revisions of a project. -- 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-1473) Server Id in wagon notifier edit pages is required but doesn't have validation
[ http://jira.codehaus.org/browse/CONTINUUM-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1473. --- Assignee: Emmanuel Venisse Resolution: Fixed Applied. Thanks Server Id in wagon notifier edit pages is required but doesn't have validation -- Key: CONTINUUM-1473 URL: http://jira.codehaus.org/browse/CONTINUUM-1473 Project: Continuum Issue Type: Bug Components: Notification Subsystem Affects Versions: 1.1-beta-3 Reporter: Teodoro Cue Jr. Assignee: Emmanuel Venisse Priority: Minor Fix For: 1.1-beta-4 Attachments: CONTINUUM-1473-continuum-webapp.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3042) Extending a Mojo Class and used in a new Mojo Project, parameter fields in the parent mojo are not set, this disables reuse of existing mojo project.
[ http://jira.codehaus.org/browse/MNG-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108111 ] Marvin Froeder commented on MNG-3042: - On the same boat... Have the same need too. Extending a Mojo Class and used in a new Mojo Project, parameter fields in the parent mojo are not set, this disables reuse of existing mojo project. - Key: MNG-3042 URL: http://jira.codehaus.org/browse/MNG-3042 Project: Maven 2 Issue Type: Bug Components: Plugin API Reporter: Leopoldo Agdeppa III Fix For: Reviewed Pending Version Assignment I have an Existing maven-plugin-a and I want to extend its functionality and put it in maven-plugin-b, so what i did is I put the the maven-plugin-a as a dependecy in maven-plugin-b and extended the mojo class from A, the issue on this is that paramter fields from A is not set, when I used plugin-B, I think this disables reusing and extending of mojos -- 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-172) Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer.
[ http://jira.codehaus.org/browse/MECLIPSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108112 ] Carlos Sanchez commented on MECLIPSE-172: - the patch no longer applies to latest code in trunk, can you provide an update? Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer. - Key: MECLIPSE-172 URL: http://jira.codehaus.org/browse/MECLIPSE-172 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.2, 2.3 Environment: Maven 2.0.4, Eclipse 3.2.1, Windows XP Reporter: Markus Grieder Attachments: patch.txt If have a Eclipse Workspace with Projects where some use Java 1.5 (Default JRE) and some Java 1.3 For 1.3-Projects i have configured the following ClasspathContainer: classpathContainers classpathContainerorg.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre/classpathContainer /classpathContainers This generates in .classpath: classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre/ Which is wrong, because the Default JRE is Java 1.5, but the Project should only see Java 1.3-Libraries and not both. - The Default ClasspathContainer should only be added if no JRE_CONTAINER (alternate JRE or a Execution Environment (=Eclipse 3.2)) was specified. The attached Patch replace the contains-match with a starts-with-match, which only adds the Default ClasspathContainer if no classpathContainer is configured which starts with the JRE_CONTAINER-Path. -- 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-1481) datamanagement-cli must support more db
[ http://jira.codehaus.org/browse/CONTINUUM-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1481. --- Assignee: Emmanuel Venisse Resolution: Fixed Applied. Thanks. datamanagement-cli must support more db --- Key: CONTINUUM-1481 URL: http://jira.codehaus.org/browse/CONTINUUM-1481 Project: Continuum Issue Type: Bug Components: Data Management Affects Versions: 1.1-beta-3 Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Priority: Critical Fix For: 1.1-beta-4 Attachments: CONTINUUM-1481-1.patch only derby DB is supported for now -- 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-1483) Better support for SCM like clearcase or SYNERGY
[ http://jira.codehaus.org/browse/CONTINUUM-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1483: Assignee: Emmanuel Venisse Fix Version/s: 1.1-beta-4 Better support for SCM like clearcase or SYNERGY Key: CONTINUUM-1483 URL: http://jira.codehaus.org/browse/CONTINUUM-1483 Project: Continuum Issue Type: Improvement Components: SCM Affects Versions: 1.1-beta-4 Reporter: David Causse Assignee: Emmanuel Venisse Fix For: 1.1-beta-4 Attachments: relative_path.diff SCM providers that honour the relativePath in the scm checkout result are not treated correctly. It is impossible to use group builds for these providers. The patch included tries to adress this issue and allow group builds to work with relative path. -- 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-1487) should not be allowed to delete a build result that is still executing
should not be allowed to delete a build result that is still executing -- Key: CONTINUUM-1487 URL: http://jira.codehaus.org/browse/CONTINUUM-1487 Project: Continuum Issue Type: Bug Affects Versions: 1.1-beta-3 Reporter: Brett Porter note that deleting the build result from on the build result page also seems to skip confirmation. All I did was hit the space bar... -- 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-213) cannot undeploy archiva webapp
[ http://jira.codehaus.org/browse/MRM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108119 ] Arnaud Heritier commented on MRM-213: - Another tip: Use antiResourceLocking=true and antiJARLocking=true in the context declaration cannot undeploy archiva webapp -- Key: MRM-213 URL: http://jira.codehaus.org/browse/MRM-213 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-1 Environment: I'm running Archiva webapp under tomcat 5.5 / windows 2003 server Reporter: nicolas de loof Assignee: Joakim Erdfelt Priority: Minor Fix For: 1.0-beta-3 I'd like to undeploy without restarting Tomcat (as I don't have admin acces to the server). When I undelploy archiva webapp using tomcat manager, the webapp/archiva directory is not removed and WEB-INF/lib still contains: jpox-1.1.1.jar plexus-container-default-1.0-alpha-10.jar plexus-security-authorization-rbac-store-jdo-1.0-alpha-6-20061013.204855-1.jar plexus-security-keys-jdo-1.0-alpha-6-20061013.204855-1.jar plexus-security-user-management-provider-jdo-1.0-alpha-6-20061013.204855-1.jar webwork-2.2.4.jar xwork-1.2.1.jar I cannot remove those jars (files locked) Maybe some background thread is not stopped at application undeploy ? -- 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-213) cannot undeploy archiva webapp
[ http://jira.codehaus.org/browse/MRM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108120 ] Joakim Erdfelt commented on MRM-213: Arnaud, Those 2 options are not available on Tomcat 5.0.x (at least I can't find them). They appear to be present on Tomcat 5.5.x and Tomcat 6.0.x though. cannot undeploy archiva webapp -- Key: MRM-213 URL: http://jira.codehaus.org/browse/MRM-213 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-1 Environment: I'm running Archiva webapp under tomcat 5.5 / windows 2003 server Reporter: nicolas de loof Assignee: Joakim Erdfelt Priority: Minor Fix For: 1.0-beta-3 I'd like to undeploy without restarting Tomcat (as I don't have admin acces to the server). When I undelploy archiva webapp using tomcat manager, the webapp/archiva directory is not removed and WEB-INF/lib still contains: jpox-1.1.1.jar plexus-container-default-1.0-alpha-10.jar plexus-security-authorization-rbac-store-jdo-1.0-alpha-6-20061013.204855-1.jar plexus-security-keys-jdo-1.0-alpha-6-20061013.204855-1.jar plexus-security-user-management-provider-jdo-1.0-alpha-6-20061013.204855-1.jar webwork-2.2.4.jar xwork-1.2.1.jar I cannot remove those jars (files locked) Maybe some background thread is not stopped at application undeploy ? -- 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: (MPH-22) inherited profiles are not displayed when showing effective-pom
[ http://jira.codehaus.org/browse/MPH-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108122 ] Gisbert Amm commented on MPH-22: This is a duplicate of http://jira.codehaus.org/browse/MPH-16 inherited profiles are not displayed when showing effective-pom --- Key: MPH-22 URL: http://jira.codehaus.org/browse/MPH-22 Project: Maven 2.x Help Plugin Issue Type: Bug Reporter: Roman Cerny when executing: mvn help:effective-pom the inherited profiles are NEVER shown. Only the leaf-profiles are displayed. But all profiles are currently existing, and can be activated. Maybe this is no bug, and the inherited profiles are left out (when displaying) for a reason, but to me it looks like a bug. -- 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: (MPH-16) help:active-profiles doesn't include profiles derived from the parent pom.
[ http://jira.codehaus.org/browse/MPH-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108124 ] Gisbert Amm commented on MPH-16: Duplicated in http://jira.codehaus.org/browse/MPH-22 help:active-profiles doesn't include profiles derived from the parent pom. -- Key: MPH-16 URL: http://jira.codehaus.org/browse/MPH-16 Project: Maven 2.x Help Plugin Issue Type: Bug Reporter: David Boden Priority: Critical Attachments: helptest.zip, patch.txt Effects the current HEAD revision. helptest.zip contains very simple child and parent pom files. When you extract this zip file into a directory and execute: mvn help:active-profiles The should-be-listed-as-active profile which is listed in the parent is mentioned in the report. Please see patch.txt for a naive fix. -- 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: (MPH-16) help:active-profiles doesn't include profiles derived from the parent pom.
[ http://jira.codehaus.org/browse/MPH-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108126 ] Gisbert Amm commented on MPH-16: http://jira.codehaus.org/browse/MPH-12 seems to be an attempt to fix this issue. help:active-profiles doesn't include profiles derived from the parent pom. -- Key: MPH-16 URL: http://jira.codehaus.org/browse/MPH-16 Project: Maven 2.x Help Plugin Issue Type: Bug Reporter: David Boden Priority: Critical Attachments: helptest.zip, patch.txt Effects the current HEAD revision. helptest.zip contains very simple child and parent pom files. When you extract this zip file into a directory and execute: mvn help:active-profiles The should-be-listed-as-active profile which is listed in the parent is mentioned in the report. Please see patch.txt for a naive fix. -- 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-409) Email notifications could still include build stats when includeBuildResult is false
[ http://jira.codehaus.org/browse/CONTINUUM-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-409. -- Assignee: Emmanuel Venisse Resolution: Fixed Applied with includeBuildSummary in application.xml. Thanks. Email notifications could still include build stats when includeBuildResult is false Key: CONTINUUM-409 URL: http://jira.codehaus.org/browse/CONTINUUM-409 Project: Continuum Issue Type: Wish Components: Notifier - Mail Affects Versions: 1.1-beta-3 Reporter: David Blevins Assignee: Emmanuel Venisse Fix For: 1.1-beta-4 Attachments: CONTINUUM-409-continuum-core.patch I really like the Build statistics and Changes sections continuum creates in the emails and definitely want them in every email. It's really just the section that contains the output generated from the build itself that I don't want as that will consistently be several megs of text for our project. Basically, I assumed 'includeBuildResults=false' would just exclude out everything after these lines Output: I really don't care what the option is called as long as I can get an email as described. Maybe you want to do something like this includeBuildStatisticstrue/includeBuildStatistics includeChangestrue/includeChanges includeBuildOutputfalse/includeBuildOutput -- 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-489) Repositories are read only even for repository managers
[ http://jira.codehaus.org/browse/MRM-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-489. -- Resolution: Cannot Reproduce Fix Version/s: 1.0-beta-3 I cannot reproduce the errors that Andy has reported, I'm closing this jira in the meantime. I have copied the documentation in here to the confluence space at http://docs.codehaus.org/display/MAVENUSER/Archiva+WebDAV+Implementation I will continue to strive to keep that wiki page up to date on any changes / deviations from the WebDAV protocol in use by Archiva. Repositories are read only even for repository managers --- Key: MRM-489 URL: http://jira.codehaus.org/browse/MRM-489 Project: Archiva Issue Type: Bug Components: WebDAV interface Affects Versions: 1.0-alpha-2 Environment: OSX Reporter: Andrew Williams Assignee: Joakim Erdfelt Fix For: 1.0-beta-3 Both the OSX client and the litmus test suite report that the repositories are read only and cannot be deployed to. -- 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-1485) CVS checkout is considerably slower
[ http://jira.codehaus.org/browse/CONTINUUM-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108138 ] Adrian Sox commented on CONTINUUM-1485: --- There aren't usually too many changes in any given build - the average change between builds would be around 10 files, and changes to 50 or more files in a single build are rare. However, we've performed around 20,000 builds in the past three years. As the numbers would indicate, many files do have a large number of revisions, so there is a large amount of information for a cvs log command to sort through. In this case, it would be considerably faster to execute a cvs log against just those files that changed. I would think this situation is typical for a large project. CVS checkout is considerably slower --- Key: CONTINUUM-1485 URL: http://jira.codehaus.org/browse/CONTINUUM-1485 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.1-beta-2 Environment: Running on Windows XP inside Tomcat 5.5.17, communicating with CVSNT server, using CVSNT client. Reporter: Adrian Sox The project tree we are building is fairly large (5,000 files, 220 MB). It normally takes 5-6 minutes to perform a cvs update on this tree when executing from the command line or Eclipse. With Continuum 1.0.3, it took 5-6 minutes to update the project from CVS, before the actual build began. With 1.1-beta-2, it takes much longer - 15-20 minutes - to perform the same update. Build Fresh is not checked. The two versions of Continuum are set up identically in all other regards, except that 1.0.3 is run standalone, not from Tomcat. Both run on the same box, as the same user, use the same CVS executable, hit the same CVS server, use the same Java version, the same Maven 2 version, the same disk drive, ... and of course, with only one version of Continuum running at any given time. Aside from this issue, we very much like the changes in 1.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-419) WebDAV functionality not working for Internet Explorer / Windows Network Places
[
http://jira.codehaus.org/browse/MRM-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108141
]
Joakim Erdfelt commented on MRM-419:
I was able to duplicate this issue.
I've captured the traffic between Internet Explorer running on my Windows XP
(SP2) Laptop and my installation of Archiva on my Linux box.
Here's what I see.
URL provided to Windows Network Places (by hand)
http://192.168.1.145:8080/archiva/repository/internal//
What happens is a few probes from the Windows machine asking for options, and
even a request for a windows specific feature, all to the WRONG PATHS.
*First Request*
{noformat}
OPTIONS / HTTP/1.1
User-Agent: Microsoft Data Access Internet Publishing Provider Cache Manager
Host: 192.168.1.145:8080
Content-Length: 0
Connection: Keep-Alive
HTTP/1.1 200 OK
Content-Type: text/html;charset=ISO-8859-1
Transfer-Encoding: chunked
Date: Mon, 24 Sep 2007 18:00:00 GMT
Server: Apache-Coyote/1.1
{noformat}
*Second Request*
{noformat}
GET /_vti_inf.html HTTP/1.1
Date: Mon, 24 Sep 2007 17:59:40 GMT
MIME-Version: 1.0
Accept: */*
User-Agent: Mozilla/2.0 (compatible; MS FrontPage 4.0)
Host: 192.168.1.145:8080
Accept: auth/sicily
Content-Length: 0
Connection: Keep-Alive
Cache-Control: no-cache
HTTP/1.1 404 /_vti_inf.html
Content-Type: text/html;charset=utf-8
Content-Length: 994
Date: Mon, 24 Sep 2007 18:00:00 GMT
Server: Apache-Coyote/1.1
{noformat}
*Third Request*
{noformat}
POST /_vti_bin/shtml.exe/_vti_rpc HTTP/1.1
Date: Mon, 24 Sep 2007 17:59:40 GMT
MIME-Version: 1.0
User-Agent: MSFrontPage/4.0
Host: 192.168.1.145:8080
Accept: auth/sicily
Content-Length: 41
Content-Type: application/x-www-form-urlencoded
X-Vermeer-Content-Type: application/x-www-form-urlencoded
Connection: Keep-Alive
Cache-Control: no-cache
method=server+version%3a4%2e0%2e2%2e4715
HTTP/1.1 404 /_vti_bin/shtml.exe/_vti_rpc
Content-Type: text/html;charset=utf-8
Content-Length: 1036
Date: Mon, 24 Sep 2007 18:00:00 GMT
Server: Apache-Coyote/1.1
{noformat}
*Fourth Request*
{noformat}
OPTIONS /archiva HTTP/1.1
Accept-Language: en-us
User-Agent: Microsoft Data Access Internet Publishing Provider DAV 1.1
Host: 192.168.1.145:8080
Content-Length: 0
Connection: Keep-Alive
HTTP/1.1 302 Moved Temporarily
Location: http://192.168.1.145:8080/archiva/
Transfer-Encoding: chunked
Date: Mon, 24 Sep 2007 18:00:00 GMT
Server: Apache-Coyote/1.1
{noformat}
And that's the last request to the Archiva server, not once even asking the
Repository Root http://192.168.1.145:8080/archiva/repository/internal/ about
it's OPTIONS.
That is why it fails. Unfortunately, I don't see a way that Archiva can fix
this odd behavior of Windows.
WebDAV functionality not working for Internet Explorer / Windows Network
Places
---
Key: MRM-419
URL: http://jira.codehaus.org/browse/MRM-419
Project: Archiva
Issue Type: Bug
Components: WebDAV interface
Affects Versions: 1.0-alpha-2
Reporter: John Didion
Assignee: Joakim Erdfelt
Fix For: 1.0.x
I am using archiva built from source (r548493). I set up a managed repository
and several proxied repositories.
Browsing the WebDAV url from Firefox works just fine, but it appears the IE
doesn't recognize the url - it asks me if I want to save this file, and its
type is unknown.
When I try to set up a Network Place using the url, it shows me the top level
of the repository, but if I try to browse to any folder, I get the error:
Documents in this folder are not available. The folder may have been moved
or deleted, or network problems may be preventing a connection to the server.
There is a problem with the web server. Please try again later or contact the
server administrator.
I notice that the url it's trying to browse to is incorrect. The root URL of
the repository is:
http://[host]/archiva/repository/internal/
but when I double-click on, say, commons-collections, it tries to browse to:
http://repository.muze.com/archiva/repository/commons-collections
--
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-481) Artifact requests with a .xml.zip extension fail with a 404 Error
[ http://jira.codehaus.org/browse/MRM-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-481: --- Fix Version/s: 1.0-beta-3 Artifact requests with a .xml.zip extension fail with a 404 Error - Key: MRM-481 URL: http://jira.codehaus.org/browse/MRM-481 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-1 Reporter: Cédric Vidal Priority: Critical Fix For: 1.0-beta-3 Attachments: multi-dots-ext-404-error.htm This issue might also apply to any multi dots extension request but I didn't check. Regards, Cédric -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-487) pom version is not resolved
[
http://jira.codehaus.org/browse/MRM-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt updated MRM-487:
---
Assignee: Joakim Erdfelt
Fix Version/s: 1.0-beta-3
pom version is not resolved
---
Key: MRM-487
URL: http://jira.codehaus.org/browse/MRM-487
Project: Archiva
Issue Type: Bug
Affects Versions: 1.0-beta-1
Reporter: Libor Kramolis
Assignee: Joakim Erdfelt
Priority: Critical
Fix For: 1.0-beta-3
Attachments: archiva.log, pom-version-is-not-resolved.png, pom.xml
I compose pom.version from 4 properties:
--
version${prj.ver.maj}.${prj.ver.min}.${prj.ver.inc}${prj.ver.suf}/version
properties
prj.ver.maj2/prj.ver.maj
prj.ver.min0/prj.ver.min
prj.ver.inc5/prj.ver.inc
prj.ver.suf-SNAPSHOT/prj.ver.suf
/properties
--
But it looks Archiva does not resolve pom.version and it is not possible to
browse this artifact (see attached screenshot).
Attached archiva.log, mentioned project's pom.xml and screenshot of browse
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] Updated: (MRM-443) it'd be nice to have a wizard interface to set up some common settings
[ http://jira.codehaus.org/browse/MRM-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-443: --- Fix Version/s: 1.0.x it'd be nice to have a wizard interface to set up some common settings -- Key: MRM-443 URL: http://jira.codehaus.org/browse/MRM-443 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.0-alpha-2 Reporter: Brett Porter Fix For: 1.0.x for example - setting up guest access to all repositories could be a simple yes/no instead of having to go in and do configuration on a new set up. -- 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-454) Index not updated after repository purge
[ http://jira.codehaus.org/browse/MRM-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-454: --- Fix Version/s: 1.0-beta-3 Index not updated after repository purge Key: MRM-454 URL: http://jira.codehaus.org/browse/MRM-454 Project: Archiva Issue Type: Bug Components: repository scanning Affects Versions: 1.0-beta-1 Reporter: Maria Odea Ching Fix For: 1.0-beta-3 Please see comments MRM-294 for more info -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-455) Repository Browse not updated after repository purge although the database is updated during the purge
[ http://jira.codehaus.org/browse/MRM-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-455: --- Fix Version/s: 1.0-beta-3 Repository Browse not updated after repository purge although the database is updated during the purge -- Key: MRM-455 URL: http://jira.codehaus.org/browse/MRM-455 Project: Archiva Issue Type: Bug Components: browser Affects Versions: 1.0-beta-1 Reporter: Maria Odea Ching Fix For: 1.0-beta-3 Please see comments on MRM-294 for more info -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-468) incorrect URL reported from failures in WebDAV
[ http://jira.codehaus.org/browse/MRM-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-468: --- Fix Version/s: 1.0-beta-3 incorrect URL reported from failures in WebDAV -- Key: MRM-468 URL: http://jira.codehaus.org/browse/MRM-468 Project: Archiva Issue Type: Bug Components: WebDAV interface Affects Versions: 1.0-beta-1 Reporter: Brett Porter Fix For: 1.0-beta-3 eg. hit a URL that doesn't exist. The HTML response resembles: Resource in error: http://localhost:8080/archiva/repository/org/codehaus/cargo/cargo-ant/0.8/cargo-ant-0.8.jar/org/codehaus/cargo/cargo-ant/0.8/cargo-ant-0.8.jar Note that the path is incorrect - it is appended again after .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] Closed: (MRM-469) Test failure in MavenProjectInfoReportsPluginDependencyGraphTest in archiva-dependency-graph
[ http://jira.codehaus.org/browse/MRM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-469. -- Resolution: Fixed Do not use JDK 1.6 Test failure in MavenProjectInfoReportsPluginDependencyGraphTest in archiva-dependency-graph Key: MRM-469 URL: http://jira.codehaus.org/browse/MRM-469 Project: Archiva Issue Type: Bug Components: indexing Affects Versions: 1.0-alpha-2 Environment: - Ubuntu Linux - Java 1.6 - Maven 2.0.6 Reporter: Maria Odea Ching Assignee: Joakim Erdfelt I commented the assert(...) in testResolvedDepsToNodes() to be able to release 1.0-beta-1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-470) Test failures in BytecodeIndexTest due to NPE in AbstractIndexCreationTestCase
[ http://jira.codehaus.org/browse/MRM-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-470. -- Resolution: Fixed Fix Version/s: 1.0-beta-3 Do not use JDK 1.6 Test failures in BytecodeIndexTest due to NPE in AbstractIndexCreationTestCase -- Key: MRM-470 URL: http://jira.codehaus.org/browse/MRM-470 Project: Archiva Issue Type: Bug Components: indexing Affects Versions: 1.0-alpha-2 Environment: - Ubuntu Linux - Java 1.6 - Maven 2.0.6 Reporter: Maria Odea Ching Assignee: Joakim Erdfelt Fix For: 1.0-beta-3 Commented out the following tests to be able to release 1.0-beta-1: - testAddRecordNoIndex() - testAddRecordExistingEmptyIndex() - testAddRecordInIndex() - testDeleteRecordInIndex() -- 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-514) Archiva cannot compile and pass tests on JDK 1.6
Archiva cannot compile and pass tests on JDK 1.6 Key: MRM-514 URL: http://jira.codehaus.org/browse/MRM-514 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0.x Reporter: Joakim Erdfelt Priority: Minor When using JDK 1.6, Archiva cannot compile and pass all of its unit tests. -- 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-514) Archiva cannot compile and pass tests on JDK 1.6
[ http://jira.codehaus.org/browse/MRM-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-514: --- Affects Version/s: (was: 1.0.x) 1.0-beta-2 Fix Version/s: 1.0.x Archiva cannot compile and pass tests on JDK 1.6 Key: MRM-514 URL: http://jira.codehaus.org/browse/MRM-514 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0-beta-2 Reporter: Joakim Erdfelt Priority: Minor Fix For: 1.0.x When using JDK 1.6, Archiva cannot compile and pass all of its unit tests. -- 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-483) verify thread safety of Configuration object
[ http://jira.codehaus.org/browse/MRM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-483: --- Fix Version/s: 1.0.x verify thread safety of Configuration object Key: MRM-483 URL: http://jira.codehaus.org/browse/MRM-483 Project: Archiva Issue Type: Bug Reporter: Brett Porter Fix For: 1.0.x Deng discovered a thread-safety bug in the re-initialisation of the Configuration object when saving and consequently re-initialising. While that has been fixed, and DefaultArchivaConfiguration is now thread safe, it does pass out the shared Configuration object. We need to audit places that the object may be modified in a way that is not thread safe (if it is being modified, it should not be used by another thread until the save() method has completed and those threads have called get() again - perhaps anything that intends to modify it should get back a copy of the configuration object instead). -- 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-466) NPE on DatabaseJob.execute()
[ http://jira.codehaus.org/browse/MRM-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-466. -- Assignee: Joakim Erdfelt Resolution: Fixed Fix Version/s: 1.0-beta-3 The null guard is in place (just swapped the .equals() comparison around) NPE on DatabaseJob.execute() Key: MRM-466 URL: http://jira.codehaus.org/browse/MRM-466 Project: Archiva Issue Type: Bug Components: scheduling Affects Versions: 1.0-beta-2 Reporter: Joakim Erdfelt Assignee: Joakim Erdfelt Fix For: 1.0-beta-3 From archiva.log 30778389 [defaultScheduler_Worker-13] ERROR org.quartz.core.JobRunShell - Job database-group.database-job threw an unhandled Exception: java.lang.NullPointerException at org.apache.maven.archiva.scheduled.DatabaseTaskJob.execute(DatabaseTaskJob.java:57) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) 30778390 [defaultScheduler_Worker-13] ERROR org.quartz.core.ErrorLogger - Job (database-group.database-job threw an exception. org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException] at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) -- 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-486) Can not deploy artifact test.maven-arch:test-arch
[ http://jira.codehaus.org/browse/MRM-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-486. -- Resolution: Fixed Fix Version/s: 1.0-beta-3 Verified that recent work around DefaultBidirectionalLayout have fixed this issue too. Added Test Case to revision 578897 on archiva/trunk. Can not deploy artifact test.maven-arch:test-arch - Key: MRM-486 URL: http://jira.codehaus.org/browse/MRM-486 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-1 Reporter: Libor Kramolis Assignee: Joakim Erdfelt Fix For: 1.0-beta-3 Attachments: archiva.log, no-artifact-id-detected.png, pom.xml I have test artifact with groupId = test.maven-arch and artifactId = test-arch. But Archiva does not work with this project - I can not browse thsi project. There is No Artifact Id detected. in archiva.log. Attached archiva.log, mentioned project's pom.xml and screenshot of browse 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] Updated: (MRM-488) properties in pom are not resolved (at least while browsing)
[ http://jira.codehaus.org/browse/MRM-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-488: --- Fix Version/s: 1.0-beta-3 properties in pom are not resolved (at least while browsing) Key: MRM-488 URL: http://jira.codehaus.org/browse/MRM-488 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-1 Reporter: Libor Kramolis Assignee: Joakim Erdfelt Fix For: 1.0-beta-3 Attachments: pom-configuration-is-not-resolved.png, pom.xml I extensively use properties in pom.xml (see attached one). But Archiva does not resolve pom configuration. When I browse my project I see not resolved values. Attached mentioned project's pom.xml and screenshot of browse 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] Updated: (MRM-493) Downloaded artifacts are stored in incorrect archiva-managed repository
[ http://jira.codehaus.org/browse/MRM-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-493: --- Priority: Critical (was: Major) Fix Version/s: 1.0-beta-3 Downloaded artifacts are stored in incorrect archiva-managed repository --- Key: MRM-493 URL: http://jira.codehaus.org/browse/MRM-493 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0-beta-2 Environment: Linux 2.6.20-16-server i686 GNU/Linux, Sun Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03), apache-archiva-1.0-beta-2-SNAPSHOT (2007-09-11) Reporter: Jo Vandermeeren Priority: Critical Fix For: 1.0-beta-3 I have added a new local directory as archiva-managed repository with id repo-trax. Although no proxy connector has been setup for this new archiva-managed repository, downloaded artifacts seem to be stored in this repository instead of the default internal repository. The only proxy connector configuration is the one that comes by default (internal connected to dev.java.net and repo1.maven.org). -- 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-494) leaving repository ID blank on the add repository page goes to the edit page where ID cannot be edited
[ http://jira.codehaus.org/browse/MRM-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-494: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0-beta-3 Verified as problem in Managed and Remote Repository add screens. leaving repository ID blank on the add repository page goes to the edit page where ID cannot be edited -- Key: MRM-494 URL: http://jira.codehaus.org/browse/MRM-494 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter 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] Closed: (MRM-500) Failure in PathUtilTest under windows because the test uses slashes in path but test File.separator in PathUtil
[ http://jira.codehaus.org/browse/MRM-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-500. -- Assignee: Joakim Erdfelt Resolution: Fixed Fix Version/s: 1.0-beta-3 This was fixed in trunk already. Failure in PathUtilTest under windows because the test uses slashes in path but test File.separator in PathUtil --- Key: MRM-500 URL: http://jira.codehaus.org/browse/MRM-500 Project: Archiva Issue Type: Bug Components: build Affects Versions: 1.0-beta-2 Reporter: Emmanuel Venisse Assignee: Joakim Erdfelt Fix For: 1.0-beta-3 --- Test set: org.apache.maven.archiva.common.utils.PathUtilTest --- Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec FAILURE! testToRelativeWithSlash(org.apache.maven.archiva.common.utils.PathUtilTest) Time elapsed: 0.016 sec FAILURE! junit.framework.ComparisonFailure: expected:p... but was:... at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.apache.maven.archiva.common.utils.PathUtilTest.testToRelativeWithSlash(PathUtilTest.java:45) -- 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-502) Error 500 when searching an artifact by the checksum
[
http://jira.codehaus.org/browse/MRM-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt updated MRM-502:
---
Affects Version/s: 1.0-beta-2
Fix Version/s: 1.0-beta-3
Environment: (was: Maestro 1.3.1 (@devzuz))
Error 500 when searching an artifact by the checksum
Key: MRM-502
URL: http://jira.codehaus.org/browse/MRM-502
Project: Archiva
Issue Type: Bug
Components: web application
Affects Versions: 1.0-beta-2
Reporter: Arnaud Heritier
Fix For: 1.0-beta-3
Trying to search some artifacts with their checksum I receive this error :
{code}
HTTP ERROR: 500
Exception in JSP: /WEB-INF/jsp/results.jsp:95
92:
version=${artifactModel.version}/
93: /h3
94: p
95: my:showArtifactLink
groupId=${artifactModel.groupId} artifactId=${artifactModel.artifactId}
96:
version=${artifactModel.version} versions=${artifactModel.versions}/
97: /p
98: /c:when
Stacktrace:
RequestURI=/archiva/checksumSearch.action
Powered by Jetty://
{code}
4a61c9f221ebed45e4006f2f8fa0 *bsf-2.3.0.jar
No results found
8d4a9cf34eb4e374b41b6b98960028d0 *jsp-api-2.0.jar
No results found ?
db561232e47050e15572fa0b01e08569 *jstl-2.3.jar
No results found ?
c2ced5f8505fe9d1cae685201e9cba07 *jstl-2.4.jar
No results found ?
f6cf3fde0b992589ed3d87fa9674015f *servletapi-2.4.jar
No results found
--
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-495) search fields should be weighted to improve search results
[ http://jira.codehaus.org/browse/MRM-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-495: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0.x search fields should be weighted to improve search results -- Key: MRM-495 URL: http://jira.codehaus.org/browse/MRM-495 Project: Archiva Issue Type: Improvement Components: indexing Affects Versions: 1.0-beta-2 Reporter: Brett Porter Fix For: 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-501) Saving configuration fails through the webapp.
[
http://jira.codehaus.org/browse/MRM-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt updated MRM-501:
---
Priority: Blocker (was: Major)
Fix Version/s: 1.0-beta-3
Saving configuration fails through the webapp.
--
Key: MRM-501
URL: http://jira.codehaus.org/browse/MRM-501
Project: Archiva
Issue Type: Bug
Components: web application
Affects Versions: 1.0-beta-2
Environment: JDK-1.5.0
Geronimo-2.0.1
PostgreSQL-8.2.4
Reporter: Aleksandr Tarutin
Priority: Blocker
Fix For: 1.0-beta-3
When modifying Proxy Connector through the web UI the following error occured:
{code}
Unable to save configuration: Unable to create configuration file:
/dev/null/.m2/archiva.xml (Not a directory)
{code}
Geronimo runs as a user without login and with home dir set to /dev/null.
--
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-507) Create LicenseTypeMapper library
[ http://jira.codehaus.org/browse/MRM-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-507: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0.x Create LicenseTypeMapper library Key: MRM-507 URL: http://jira.codehaus.org/browse/MRM-507 Project: Archiva Issue Type: Sub-task Affects Versions: 1.0-beta-2 Reporter: Teodoro Cue Jr. Fix For: 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-504) Find Artifact page needs more onscreen information/instructions
[ http://jira.codehaus.org/browse/MRM-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-504: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0-beta-3 Find Artifact page needs more onscreen information/instructions --- Key: MRM-504 URL: http://jira.codehaus.org/browse/MRM-504 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.0-beta-2 Reporter: Teodoro Cue Jr. Fix For: 1.0-beta-3 Find Artifact Search for: Checksum: Select the file you would like to locate in the remote repository. The entire file will not be uploaded to the server. See the progress bar below for progress of locally creating a checksum that is uploaded to the server after you hit Go!. This page and text and the 'Go' button do not help the user understand what they can/need to do. If they should do only one or the other, only one option should be available at a time. Recommend changing 'Go' to 'Submit', for consistency w/ Search 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] Updated: (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 updated MRM-503: --- Assignee: Joakim Erdfelt Fix Version/s: 1.0-beta-3 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: (MRM-506) [REPORT] Repository Statistics
[ http://jira.codehaus.org/browse/MRM-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-506: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0.x [REPORT] Repository Statistics -- Key: MRM-506 URL: http://jira.codehaus.org/browse/MRM-506 Project: Archiva Issue Type: Sub-task Components: reporting Affects Versions: 1.0-beta-2 Reporter: Teodoro Cue Jr. Fix For: 1.0.x The repository statistics screen should contain the following |Type|In Corporate Repo|In Snapshots Repo|Total| |File Count|#|#|#| |File Size Totals|#|#|#| |Project Count|#|#|#| |Group Id Count|#|#|#| |Artifact Count|#|#|#| |Plugin Count|#|#|#| |Archetype Count|#|#|#| |Jar Count|#|#|#| |War Count|#|#|#| -- 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-507) Create LicenseTypeMapper library
[ http://jira.codehaus.org/browse/MRM-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108152 ] Joakim Erdfelt commented on MRM-507: Can you expand on this? I don't understand this jira. Create LicenseTypeMapper library Key: MRM-507 URL: http://jira.codehaus.org/browse/MRM-507 Project: Archiva Issue Type: Sub-task Affects Versions: 1.0-beta-2 Reporter: Teodoro Cue Jr. Fix For: 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-508) Create LicenseTypeMapper management screens.
[ http://jira.codehaus.org/browse/MRM-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-508: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0.x Component/s: reporting Create LicenseTypeMapper management screens. Key: MRM-508 URL: http://jira.codehaus.org/browse/MRM-508 Project: Archiva Issue Type: Sub-task Components: reporting Affects Versions: 1.0-beta-2 Reporter: Teodoro Cue Jr. Fix For: 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-507) Create LicenseTypeMapper library
[ http://jira.codehaus.org/browse/MRM-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-507: --- Component/s: reporting Create LicenseTypeMapper library Key: MRM-507 URL: http://jira.codehaus.org/browse/MRM-507 Project: Archiva Issue Type: Sub-task Components: reporting Affects Versions: 1.0-beta-2 Reporter: Teodoro Cue Jr. Fix For: 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-508) Create LicenseTypeMapper management screens.
[ http://jira.codehaus.org/browse/MRM-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108153 ] Joakim Erdfelt commented on MRM-508: Can you provide more details on what this is? Create LicenseTypeMapper management screens. Key: MRM-508 URL: http://jira.codehaus.org/browse/MRM-508 Project: Archiva Issue Type: Sub-task Components: reporting Affects Versions: 1.0-beta-2 Reporter: Teodoro Cue Jr. Fix For: 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-511) Maven IT 94 fails when using Archiva as a proxy
[ http://jira.codehaus.org/browse/MRM-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-511: --- Fix Version/s: 1.0-beta-3 Maven IT 94 fails when using Archiva as a proxy --- Key: MRM-511 URL: http://jira.codehaus.org/browse/MRM-511 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0-beta-2 Reporter: Brett Porter Fix For: 1.0-beta-3 looks like a metadata bug - it fails to resolve log4j with version [1.2.9,] - the same thing works when I stop using it as a proxy. -- 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-505) Ability to Aggregate/Report on a variety of artifact criterium
[ http://jira.codehaus.org/browse/MRM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-505: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0.x Ability to Aggregate/Report on a variety of artifact criterium -- Key: MRM-505 URL: http://jira.codehaus.org/browse/MRM-505 Project: Archiva Issue Type: New Feature Components: reporting Affects Versions: 1.0-beta-2 Reporter: Teodoro Cue Jr. Fix For: 1.0.x In addition to basic summary information on the total # of files in the Maestro Repository Manager (MRM) - we need to support the following other basic summary information: a) number of unique/discrete projects (based on combo of GroupID and ArtifactID - or is it just ArtifactID) b) number of unique community/company projects (based on GroupID) c) number of wars, jars, ears, etc. (by file extension type) d) number of source files e) number of metadata files f) number of artifacts w/ a certain license type (also number of artifacts with no license info) g) number of projects RELATED to a unique community/company there are other stats, but they are more historical, qualitative vs. quantitative - should I put them all here? or separate as another issue? -- 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 ] Joakim Erdfelt updated MRM-513: --- Fix Version/s: 1.0-beta-3 Component/s: remote proxy 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 Fix For: 1.0-beta-3 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] Updated: (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 updated MRM-510: --- Fix Version/s: 1.0-beta-3 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 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] Updated: (MRM-461) Warning message for non existent resources should include what resource it failed to locate.
[
http://jira.codehaus.org/browse/MRM-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt updated MRM-461:
---
Fix Version/s: 1.0-beta-3
Warning message for non existent resources should include what resource it
failed to locate.
Key: MRM-461
URL: http://jira.codehaus.org/browse/MRM-461
Project: Archiva
Issue Type: Bug
Affects Versions: 1.0-alpha-2
Reporter: Barrie Treloar
Priority: Minor
Fix For: 1.0-beta-3
I've modified my logging to cut down on the debug spam.
This means that I get the following warning but no context:
{panel:title=log output}
08/08/2007 12:56:07 [SocketListener0-8] WARN
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Resource
does not exist: Unable to locate resource in repository
{panel}
The warning message should also include what resource was unable to be
located.
--
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-445) search functions should show a notification message if an initial scan is still in progress
[ http://jira.codehaus.org/browse/MRM-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-445: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0-beta-3 search functions should show a notification message if an initial scan is still in progress --- Key: MRM-445 URL: http://jira.codehaus.org/browse/MRM-445 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter Priority: Minor Fix For: 1.0-beta-3 currently, on first run against a new repo, it might take some time for the relevant index or database to be up to date. Any functions that rely on them should be aware that the data is not yet complete and be able to show an appropriate warning instead of the misleading no results found. -- 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-490) add xwork exception handling pages for presentable error reporting
[ http://jira.codehaus.org/browse/MRM-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-490: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0-beta-3 add xwork exception handling pages for presentable error reporting -- Key: MRM-490 URL: http://jira.codehaus.org/browse/MRM-490 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter Fix For: 1.0-beta-3 if anyone gets a stack trace, they should have an easy way to report it as a bug (though this should also be configurable since in a production environment the admin would want to be contacted instead) -- 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-482) Saving a proxy connector after adding a new property results to HTTP 500 error
[ http://jira.codehaus.org/browse/MRM-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-482: --- Priority: Critical (was: Major) Fix Version/s: 1.0-beta-3 Saving a proxy connector after adding a new property results to HTTP 500 error -- Key: MRM-482 URL: http://jira.codehaus.org/browse/MRM-482 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-1 Reporter: Maria Odea Ching Priority: Critical Fix For: 1.0-beta-3 This was the stack trace: HTTP ERROR: 500 [Ljava.lang.String; cannot be cast to java.lang.String RequestURI=/admin/saveProxyConnector.action Caused by: java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String at org.apache.maven.archiva.configuration.io.registry.ConfigurationRegistryWriter.writeProxyConnectorConfiguration(ConfigurationRegistryWriter.java:326) at org.apache.maven.archiva.configuration.io.registry.ConfigurationRegistryWriter.writeConfiguration(ConfigurationRegistryWriter.java:67) at org.apache.maven.archiva.configuration.io.registry.ConfigurationRegistryWriter.write(ConfigurationRegistryWriter.java:31) at org.apache.maven.archiva.configuration.DefaultArchivaConfiguration.save(DefaultArchivaConfiguration.java:183) at org.apache.maven.archiva.web.action.admin.connectors.proxy.ConfigureProxyConnectorAction.saveConfiguration(ConfigureProxyConnectorAction.java:600) at org.apache.maven.archiva.web.action.admin.connectors.proxy.ConfigureProxyConnectorAction.save(ConfigureProxyConnectorAction.java:480) 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:597) at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:364) at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:216) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:81) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:103) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:159) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:122) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at
[jira] Created: (CONTINUUM-1488) Add Build, Release and Delete icons/links to groupSummary page
Add Build, Release and Delete icons/links to groupSummary page -- Key: CONTINUUM-1488 URL: http://jira.codehaus.org/browse/CONTINUUM-1488 Project: Continuum Issue Type: Improvement Components: Web - UI Affects Versions: 1.1-beta-3 Reporter: Tomislav Stojcevich Priority: Minor Attachments: CONTINUUM-1487-continuum-webapp.patch It would save some clicks if the Build, Release and Delete icons were present on the groupSummary 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: (MRM-515) Replace jasperreports with DataVision due to licensing.
Replace jasperreports with DataVision due to licensing. --- Key: MRM-515 URL: http://jira.codehaus.org/browse/MRM-515 Project: Archiva Issue Type: Improvement Components: reporting Affects Versions: 1.0-beta-2 Reporter: Joakim Erdfelt Due to the license of JasperReports, we need to remove it from the codebase. We can use the DataVision library in place of Jasper Reports. Available Here: http://datavision.sourceforge.net/ -- 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-492) repository failures can present as a 404 from proxy
[ http://jira.codehaus.org/browse/MRM-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-492: --- Affects Version/s: 1.0-beta-2 Fix Version/s: 1.0-beta-3 repository failures can present as a 404 from proxy --- Key: MRM-492 URL: http://jira.codehaus.org/browse/MRM-492 Project: Archiva Issue Type: Improvement Components: remote proxy Affects Versions: 1.0-beta-2 Reporter: Brett Porter Fix For: 1.0-beta-3 if multiple repositories are a proxy source and it is not found on some, and an error occurs on one or more - the end result is a not found, where there should be some indication of error in case the artifact may exist on the repository with the error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-515) Replace jasperreports with DataVision due to licensing.
[ http://jira.codehaus.org/browse/MRM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-515: --- Fix Version/s: 1.0.x Replace jasperreports with DataVision due to licensing. --- Key: MRM-515 URL: http://jira.codehaus.org/browse/MRM-515 Project: Archiva Issue Type: Improvement Components: reporting Affects Versions: 1.0-beta-2 Reporter: Joakim Erdfelt Fix For: 1.0.x Due to the license of JasperReports, we need to remove it from the codebase. We can use the DataVision library in place of Jasper Reports. Available Here: http://datavision.sourceforge.net/ -- 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-172) Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer.
[ http://jira.codehaus.org/browse/MECLIPSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Grieder updated MECLIPSE-172: Attachment: EclipsePlugin.java.patch Updated patch for latest trunk-revision (578921). Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer. - Key: MECLIPSE-172 URL: http://jira.codehaus.org/browse/MECLIPSE-172 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.2, 2.3 Environment: Maven 2.0.4, Eclipse 3.2.1, Windows XP Reporter: Markus Grieder Attachments: EclipsePlugin.java.patch, patch.txt If have a Eclipse Workspace with Projects where some use Java 1.5 (Default JRE) and some Java 1.3 For 1.3-Projects i have configured the following ClasspathContainer: classpathContainers classpathContainerorg.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre/classpathContainer /classpathContainers This generates in .classpath: classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre/ Which is wrong, because the Default JRE is Java 1.5, but the Project should only see Java 1.3-Libraries and not both. - The Default ClasspathContainer should only be added if no JRE_CONTAINER (alternate JRE or a Execution Environment (=Eclipse 3.2)) was specified. The attached Patch replace the contains-match with a starts-with-match, which only adds the Default ClasspathContainer if no classpathContainer is configured which starts with the JRE_CONTAINER-Path. -- 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: (MGPG-8) Build error when plugin tries to sign nonexistent jar file in a war module
[
http://jira.codehaus.org/browse/MGPG-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp closed MGPG-8.
--
Resolution: Cannot Reproduce
Fix Version/s: 1.0-alpha-4
It's most likely fixed in the latest code. I cannot reproduce it so I assume
it fixed.
Build error when plugin tries to sign nonexistent jar file in a war module
--
Key: MGPG-8
URL: http://jira.codehaus.org/browse/MGPG-8
Project: Maven 2.x GPG Plugin
Issue Type: Bug
Affects Versions: 1.0-alpha-3
Reporter: Wendy Smoak
Assignee: Daniel Kulp
Fix For: 1.0-alpha-4
During release:perform for Archiva 0.9-alpha-1, the gpg plugin is complaining
that a jar is not found, when the module has packaging=war
[INFO] [gpg:sign {execution: default}]
gpg: can't open
`e:\svn\maven\archiva\target\checkout\archiva-webapp\target\archiva-webapp-0.9-alpha-1.jar':
No such file or directory
gpg: signing failed: file open error
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Exit code: 2
[INFO]
-
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-494) leaving repository ID blank on the add repository page goes to the edit page where ID cannot be edited
[ http://jira.codehaus.org/browse/MRM-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108175 ] Joakim Erdfelt commented on MRM-494: Fixed on managed repo screens. Now to fix on remote repo screens. leaving repository ID blank on the add repository page goes to the edit page where ID cannot be edited -- Key: MRM-494 URL: http://jira.codehaus.org/browse/MRM-494 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter Assignee: Joakim Erdfelt 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] Updated: (MRM-516) Search results return results for all repositories, regardless of security.
[ http://jira.codehaus.org/browse/MRM-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-516: --- Fix Version/s: 1.0-beta-3 Search results return results for all repositories, regardless of security. --- Key: MRM-516 URL: http://jira.codehaus.org/browse/MRM-516 Project: Archiva Issue Type: Bug Components: indexing Affects Versions: 1.0-beta-2 Reporter: Joakim Erdfelt Priority: Critical Fix For: 1.0-beta-3 The UserAllowedToSearchRepositoryPredicate needs to be finished. It should take the current user, their RBAC roles, and filter based on the roles available to the user. -- 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-516) Search results return results for all repositories, regardless of security.
[ http://jira.codehaus.org/browse/MRM-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108177 ] Joakim Erdfelt commented on MRM-516: The predicate now returns true to all archiva repositories. Search results return results for all repositories, regardless of security. --- Key: MRM-516 URL: http://jira.codehaus.org/browse/MRM-516 Project: Archiva Issue Type: Bug Components: indexing Affects Versions: 1.0-beta-2 Reporter: Joakim Erdfelt Priority: Critical Fix For: 1.0-beta-3 The UserAllowedToSearchRepositoryPredicate needs to be finished. It should take the current user, their RBAC roles, and filter based on the roles available to the user. -- 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: (MDEP-50) dependency:unpack doesn't seem to handle version ranges
[
http://jira.codehaus.org/browse/MDEP-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MDEP-50:
--
Fix Version/s: (was: 2.0-alpha-5)
dependency:unpack doesn't seem to handle version ranges
---
Key: MDEP-50
URL: http://jira.codehaus.org/browse/MDEP-50
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: copy, unpack
Affects Versions: 1.0
Environment: Java 1.5
Reporter: Martin Goldhahn
Assignee: Brian Fox
When I use the dependency unpack goal and a version range as shown below,
Maven cannot download the artifact from the repository. There is a version
1.4.1 in the repository. If I use the specific version number 1.4.1. It works.
build
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddependency-maven-plugin/artifactId
executions
execution
idunpack/id
phasecompile/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdmy.package/groupId
artifactIdconcept/artifactId
version[1.4,1.5)/version
classifierres/classifier
outputDirectory${project.build.sourceDirectory}/../webapp/res/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
--
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-3220) Allow managed dependencies to be imported into other projects
Allow managed dependencies to be imported into other projects - Key: MNG-3220 URL: http://jira.codehaus.org/browse/MNG-3220 Project: Maven 2 Issue Type: New Feature Components: Dependencies Affects Versions: 2.0.7 Reporter: Ralph Goers Managed dependencies can currently only be incorporated into a project from another project via inheritance. This is problematic as it is often not possible to include projects that have required dependencies as a parent. This issue is being created to track proposals and the resolution of this issue. -- 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-494) leaving repository ID blank on the add repository page goes to the edit page where ID cannot be edited
[ http://jira.codehaus.org/browse/MRM-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-494. Assignee: Brett Porter (was: Joakim Erdfelt) Resolution: Fixed fixed on both and simplified the code to remove duplication and align names better leaving repository ID blank on the add repository page goes to the edit page where ID cannot be edited -- Key: MRM-494 URL: http://jira.codehaus.org/browse/MRM-494 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter Assignee: Brett Porter 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
