[jira] Closed: (MASSEMBLY-246) The unpack setting, if set to false, results in total exclusion of the dependency .jar file from the assembly
[ http://jira.codehaus.org/browse/MASSEMBLY-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahender Didwania closed MASSEMBLY-246. --- Resolution: Fixed Duplicate of MASSEMBLY-240 > The unpack setting, if set to false, results in total exclusion of the > dependency .jar file from the assembly > - > > Key: MASSEMBLY-246 > URL: http://jira.codehaus.org/browse/MASSEMBLY-246 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: Ubuntu 7.04, i386, using the VirtualBox image >Reporter: Mahender Didwania > > > zip-me > > zip > > false > > > > > > false > runtime > > > > > target/classes > > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MASSEMBLY-246) The unpack setting, if set to false, results in total exclusion of the dependency .jar file from the assembly
The unpack setting, if set to false, results in total exclusion of the dependency .jar file from the assembly - Key: MASSEMBLY-246 URL: http://jira.codehaus.org/browse/MASSEMBLY-246 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-1 Environment: Ubuntu 7.04, i386, using the VirtualBox image Reporter: Mahender Didwania zip-me zip false false runtime target/classes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-356) Maven 2.x surefire plugin fails with null pointer exception
Maven 2.x surefire plugin fails with null pointer exception --- Key: SUREFIRE-356 URL: http://jira.codehaus.org/browse/SUREFIRE-356 Project: Maven Surefire Issue Type: Bug Components: plugin Affects Versions: 2.3 Environment: Ubuntu 7.04, i386, VirtualBox image Reporter: Mahender Didwania http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 Test Test 0.0.1 jar net.sourceforge.jexcelapi jxl 2.6 org.apache.maven.plugins maven-surefire-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-3234) org.apache.maven.lifecycle.LifecycleExecutionException
org.apache.maven.lifecycle.LifecycleExecutionException -- Key: MNG-3234 URL: http://jira.codehaus.org/browse/MNG-3234 Project: Maven 2 Issue Type: Bug Components: Plugin API Affects Versions: 2.0.7 Reporter: subin Balachandran Nair Hi , I am new to Maven. I installed maven in my local machine and add the maven path(C:\maven2.0.7.\bin) in the PATH also. This is my mvn version C:\maven-2.0.7\bin>mvn --version Maven version: 2.0.7 Java version: 1.5.0_13 OS name: "windows xp" version: "5.1" arch: "x86" But while running mvn -U compile, getting error C:\maven-2.0.7>mvn -U compile [INFO] Scanning for projects... [INFO] - --- [INFO] Building Maven Default Project [INFO]task-segment: [compile] [INFO] - --- [INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for up dates from central [WARNING] repository metadata for: 'artifact org.apache.maven.plugins:maven-reso urces-plugin' could not be retrieved from repository: central due to an error: E rror transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Wed Oct 10 16:18:28 IST 2007 [INFO] Final Memory: 1M/2M [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] Closed: (MJAVADOC-108) proxy support for plugin not complete enough
[
http://jira.codehaus.org/browse/MJAVADOC-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-108.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.4
fixed in r583461 which deprecated proxyHost/proxyPort in favor of the active
proxy defined in settings.xml
> proxy support for plugin not complete enough
>
>
> Key: MJAVADOC-108
> URL: http://jira.codehaus.org/browse/MJAVADOC-108
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Barrie Treloar
>Assignee: Vincent Siveton
> Fix For: 2.4
>
>
> AbstractJavadocMojo.java supports
> * @parameter expression="${proxyHost}"
> default-value="${settings.activeProxy.host}"
> * @parameter expression="${proxyPort}"
> default-value="${settings.activeProxy.port}"
> but does not include the full capabilities of settings.xml
> This needs extending.
> line 981:
> {code:language=java}
> if ( StringUtils.isNotEmpty( proxyHost ) && proxyPort > 0 )
> {
> cmd.createArgument().setValue( "-J-DproxyHost=" + proxyHost );
> cmd.createArgument().setValue( "-J-DproxyPort=" + proxyPort );
> }
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MJAVADOC-151) No support for 'noProxyHosts' specified in settings.xml
[ http://jira.codehaus.org/browse/MJAVADOC-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-151. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.4 fixed in r583461 which deprecated proxyHost/proxyPort in favor of the active proxy defined in settings.xml > No support for 'noProxyHosts' specified in settings.xml > --- > > Key: MJAVADOC-151 > URL: http://jira.codehaus.org/browse/MJAVADOC-151 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Lóránt Pintér >Assignee: Vincent Siveton >Priority: Minor > Fix For: 2.4 > > > The plugin sets -J-DproxyHost and -J-DproxyPort from the active proxy > specified in the settings.xml, but does not add a command line option for > nonProxyHosts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1760) Pls upload maven-jstools-plugin version 0.3 to central
Pls upload maven-jstools-plugin version 0.3 to central -- Key: MAVENUPLOAD-1760 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1760 Project: maven-upload-requests Issue Type: New Feature Reporter: Manos Batsis Attachments: maven-jstools-plugin-0.3-bundle.jar The Maven JSTools Plugin provides a Maven2 interface to a set of JavaScript development tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1760) Pls upload maven-jstools-plugin version 0.3 to central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109535 ] Dan Tran commented on MAVENUPLOAD-1760: --- the plugin itself includes zip files, one of those is a dup of other ( ie jsdoc_xyz.. .zipORIG ) can the zip file going thru dependency the mechanism? > Pls upload maven-jstools-plugin version 0.3 to central > -- > > Key: MAVENUPLOAD-1760 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1760 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Manos Batsis > Attachments: maven-jstools-plugin-0.3-bundle.jar > > > The Maven JSTools Plugin provides a Maven2 interface to a set of JavaScript > development tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPIR-73) Error when running task deploy en maven2.x
Error when running task deploy en maven2.x -- Key: MPIR-73 URL: http://jira.codehaus.org/browse/MPIR-73 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Reporter: Luiz Alberto da Cruz Rangel Junior java.lang.NullPointerException at org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:141) at org.apache.maven.plugins.site.AbstractSiteMojo.getAvailableLocales(AbstractSiteMojo.java:166) at org.apache.maven.plugins.site.SiteDescriptorAttachMojo.execute(SiteDescriptorAttachMojo.java:67) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MAVENUPLOAD-1760) Pls upload maven-jstools-plugin version 0.3 to central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manos Batsis updated MAVENUPLOAD-1760: -- Attachment: maven-jstools-plugin-0.3-bundle.jar Corrected bundle (without the *ORIG file > Pls upload maven-jstools-plugin version 0.3 to central > -- > > Key: MAVENUPLOAD-1760 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1760 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Manos Batsis > Attachments: maven-jstools-plugin-0.3-bundle.jar, > maven-jstools-plugin-0.3-bundle.jar > > > The Maven JSTools Plugin provides a Maven2 interface to a set of JavaScript > development tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1760) Pls upload maven-jstools-plugin version 0.3 to central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109540 ] Manos Batsis commented on MAVENUPLOAD-1760: --- Hi Dan, Thanks for pointing out the redundant file. I attached a new bundle that includes the main artifact without it. I'm afraid the jsdoc and jslint stuff included as resources in the main artifact are not built with Maven so we cannot use the deps mechanism to get those at runtime. However maven-jstools-plugin encourages mavenized javascript development so this may change in the future :-) Many thanks, Manos > Pls upload maven-jstools-plugin version 0.3 to central > -- > > Key: MAVENUPLOAD-1760 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1760 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Manos Batsis > Attachments: maven-jstools-plugin-0.3-bundle.jar, > maven-jstools-plugin-0.3-bundle.jar > > > The Maven JSTools Plugin provides a Maven2 interface to a set of JavaScript > development tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1760) Pls upload maven-jstools-plugin version 0.3 to central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109543 ] Manos Batsis commented on MAVENUPLOAD-1760: --- PS: The second bundle is larger as it includes both sources and javadoc. > Pls upload maven-jstools-plugin version 0.3 to central > -- > > Key: MAVENUPLOAD-1760 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1760 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Manos Batsis > Attachments: maven-jstools-plugin-0.3-bundle.jar, > maven-jstools-plugin-0.3-bundle.jar > > > The Maven JSTools Plugin provides a Maven2 interface to a set of JavaScript > development tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3194) logging changes prevent compilation failures from being shown (in the reactor)
[
http://jira.codehaus.org/browse/MNG-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-3194.
---
Resolution: Fixed
It's fixed, but because of the fact that it's in the CLI (triggered by a main
method, which is the only entry point for the class), and that main method
constructs a concrete MavenEmbedder instance, it's not reasonable to setup a
unit test for logging output. Maybe we can do something in the ITs.
> logging changes prevent compilation failures from being shown (in the reactor)
> --
>
> Key: MNG-3194
> URL: http://jira.codehaus.org/browse/MNG-3194
> Project: Maven 2
> Issue Type: Bug
> Components: Errors, Logging
>Affects Versions: 2.1-alpha-1
>Reporter: Brett Porter
>Assignee: John Casey
>Priority: Blocker
> Fix For: 2.1-alpha-1
>
>
> The Maven build is failing today due to a compilation error, and the output
> looks like:
> {code}
> [java] [INFO] [compiler:testCompile]
> [java] [INFO] Compiling 36 source files to
> /Users/brett/scm/maven/components/maven-project/target/test-classes
> [java] [INFO]
> [java] [INFO]
> [java] [INFO]
>
> [java] [INFO] Reactor Summary:
> [java] [INFO]
>
> [java] [INFO] Apache Maven ..
> SUCCESS [19.247s]
> [java] [INFO] Maven Build Context ...
> SUCCESS [7.503s]
> [java] [INFO] Maven Model ...
> SUCCESS [8.808s]
> [java] [INFO] Maven Local Settings Model
> SUCCESS [1.960s]
> [java] [INFO] Maven Profile Model ...
> SUCCESS [1.031s]
> [java] [INFO] Maven Lifecycle Model .
> SUCCESS [1.659s]
> [java] [INFO] Maven Project Builder .
> FAILED [9.732s]
> [java] [INFO] Maven Plugin API ..
> NOT BUILT
> [java] [INFO] Maven Core
> NOT BUILT
> [java] [INFO] Maven Reporting API ...
> NOT BUILT
> [java] [INFO] Maven Embedder
> NOT BUILT
> [java] [INFO]
>
> [java] [INFO] Error for project: Maven Project Builder (during
> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile)
> [java] [INFO]
>
> [java] [INFO] BUILD ERRORS
> [java] [INFO]
>
> [java] [INFO] Total time: 50 seconds
> [java] [INFO] Finished at: Fri Sep 07 05:13:55 EST 2007
> [java] [INFO] Final Memory: 17M/42M
> [java] [INFO]
>
> {code}
> The compilation errors are missing before the summary.
> I haven't tested this outside the reactor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-3235) Profiles in settings.xml not loaded when running maven without a POM
Profiles in settings.xml not loaded when running maven without a POM
Key: MNG-3235
URL: http://jira.codehaus.org/browse/MNG-3235
Project: Maven 2
Issue Type: Bug
Components: Settings
Affects Versions: 2.0.7
Reporter: Duncan Doyle
I've created a custom Maven2 plugin for our SCM system (CA Harvest). This
plugin is deployed in our internal remote repository. This remote repository is
configured as a pluginRepository in my 'settings.xml ' file. The in
which this repository is configured is loaded using the
section. The plugin's groupId ('org.test.tools.maven.harvest') has been
specified in the section in my 'settings.xml' file.
The plugin's 'checkout' goal needs to be executed from the commandline without
a POM (because the project's POM is in the SCM system). When I execute the
command 'mvn harvest:checkout' I get the following output:
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'harvest'.
[INFO] org.test.tools.maven.harvest: checking for updates from central
Returning NULL
[INFO] org.apache.maven.plugins : checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-harvest-plugin: checking for
updates from central
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The plugin 'org.apache.maven.plugins:maven-harvest-plugin' does not
exist or no valid version could be found
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Wed Oct 10 15:27:54 CEST 2007
[INFO] Final Memory: 3M/6M
[INFO]
It looks to me that only the 'central' repository is scanned for the plugin,
although I have correctly specified my internal remote repository in the
section of my ' settings.xml' file. Furthermore, when I specify my
internal remote repository as a mirrorOf 'central' the plugin is found. So, it
looks like maven doesn't scan my internal remote repository for the needed
plugin when the repository is specified as a pluginRepository in my '
settings.xml' file.
The plugin can be used when it is specified in the build section of a POM
(which is done to be able to run the harvest:update goal on a project to update
the sources from the SCM), which to me indicates that my configuration is
correct. It just doesn't look for the plugin when the maven command is issued
without a POM.
What to me indicates that it is a profile problem is the fact that when I
specify my internal remote repo as a mirrorOf central, it can find my custom
plugin, but it can't find other needed jars from central. When I then disable
the mirror section, all the jars from central are loaded, but the build fails
on a custom jar (the SCM utility jar) which is present in another local remote
repo (my third-party repo) which is also defined in my profile.
When using mvn commands on a POM, my configuration (including my profile
settings) works as expected.
I have tried to explicitly enable the needed profile using the -P option, but
that doesn't work either.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-3181) JDOM artifact filtering is causing problems
[ http://jira.codehaus.org/browse/MNG-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109545 ] John Casey commented on MNG-3181: - If the problem is pollution from extensions, can't we find a way to define standard extension points, then load extensions into separate realms and only put imports from those realms into the main realm for implementations of the standard extensions points? This seems a lot less severe than altering the entire classloading method, which could have severe ramifications for things trying to share project information, for instance... > JDOM artifact filtering is causing problems > --- > > Key: MNG-3181 > URL: http://jira.codehaus.org/browse/MNG-3181 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > For example in the release plug that requires JDOM which uses Jaxen. We are > cutting off resolution of Jaxen so the release plugin fails. Anything that > requires Jaxen via JDOM will fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-358) User Authentication via LDAP
[ http://jira.codehaus.org/browse/CONTINUUM-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109574 ] Preston Parkinson commented on CONTINUUM-358: - I've posted this to the user mailing list and haven't heard a reply. Was hoping someone here could point me in the right direction. I've gone through the process of enabling the Ldap integration. It authenticates the admin that I've defined in the security.properties file successfully. It queries Ldap successfully for all users and logins them in as a guest with basically no access to see anything at this point. Which is as I would expect. However, I could not find in the redback or continuum documentation where I can set the role base to query for in the config. Is that even possible? Guess the question is, how do I assign the default continuum roles to my Ldap users? > User Authentication via LDAP > > > Key: CONTINUUM-358 > URL: http://jira.codehaus.org/browse/CONTINUUM-358 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Reporter: Frank Zhao >Assignee: Jesse McConnell > Fix For: 1.1-beta-3 > > > Please add LDAP support for the user authentication in Continuum user > management function. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1516) Unable to send mail
Unable to send mail --- Key: CONTINUUM-1516 URL: http://jira.codehaus.org/browse/CONTINUUM-1516 Project: Continuum Issue Type: Bug Components: Notifier - Mail Affects Versions: 1.1-beta-3 Environment: xp, maven 2.0.7, jse 5 Reporter: Dan Tran here is the trace log 9884077 [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.ContinuumNotificationDispatcher:default - Error while trying to use the mail notifier. org.codehaus.plexus.notification.NotificationException: INTERNAL ERROR: The current build wasn't the first in the build list. Current build: '288', first build: '284'. at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.getPreviousBuild(MailContinuumNotifier.java:554) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:241) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:227) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) My build has quite a few build definitions running at the same scheduler. ie builds are serialized -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1516) Unable to send mail
[ http://jira.codehaus.org/browse/CONTINUUM-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109586 ] Dan Tran commented on CONTINUUM-1516: - I think it is relate to the following scenario: 1 project group with 2 shell project. Then create the 2 second project, the first project's build definition automatically become the second proejct' build definition. ie 2 projects share the same default build definition. My DB corrupted? > Unable to send mail > --- > > Key: CONTINUUM-1516 > URL: http://jira.codehaus.org/browse/CONTINUUM-1516 > Project: Continuum > Issue Type: Bug > Components: Notifier - Mail >Affects Versions: 1.1-beta-3 > Environment: xp, maven 2.0.7, jse 5 >Reporter: Dan Tran > > here is the trace log > 9884077 [pool-1-thread-1] ERROR > org.apache.maven.continuum.notification.ContinuumNotificationDispatcher:default > - Error while trying to use the mail notifier. > org.codehaus.plexus.notification.NotificationException: INTERNAL > ERROR: The current build wasn't the first in the build list. Current > build: '288', first build: '284'. >at > org.apache.maven.continuum.notification.mail.MailContinuumNotifier.getPreviousBuild(MailContinuumNotifier.java:554) >at > org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:241) >at > org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:227) >at > org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) >at > org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) > My build has quite a few build definitions running at the same scheduler. > ie builds are serialized -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-536) JVM Bug Triggered in archiva-metadata-reports
[
http://jira.codehaus.org/browse/MRM-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt updated MRM-536:
---
Description:
{noformat}
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/
archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/
archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar to
/home/joakim/.m2/repository-archiva/org/apache/maven/archiva/archiva-metadata-re
ports/1.0-beta-3-SNAPSHOT/archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
[INFO]
[INFO] Building Archiva Reporting :: Project Reports
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/classes
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/test-classes
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/site
[INFO] [plexus:descriptor {execution: generate}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb79a4afd, pid=30832, tid=3085063872
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode, sharing)
# Problematic frame:
# V [libjvm.so+0x324afd]
#
# An error report file with more information is saved as hs_err_pid30832.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted (core dumped)
{noformat}
was:
{noformat}
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
to
/home/joakim/.m2/repository-archiva/org/apache/maven/archiva/archiva-metadata-reports/1.0-beta-3-SNAPSHOT/archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
[INFO]
[INFO] Building Archiva Reporting :: Project Reports
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/classes
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/test-classes
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/site
[INFO] [plexus:descriptor {execution: generate}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb79a4afd, pid=30832, tid=3085063872
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode, sharing)
# Problematic frame:
# V [libjvm.so+0x324afd]
#
# An error report file with more information is saved as hs_err_pid30832.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted (core dumped)
{noformat}
Jira ticket is too wide. manual word wrap added.
> JVM Bug Triggered in archiva-metadata-reports
> -
>
> Key: MRM-536
> URL: http://jira.codehaus.org/browse/MRM-536
> Project: Archiva
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0-beta-3
>Reporter: Joakim Erdfelt
> Attachments: hs_err_pid30832.log
>
>
> {noformat}
> --
[jira] Created: (MRM-536) JVM Bug Triggered in archiva-metadata-reports
JVM Bug Triggered in archiva-metadata-reports
-
Key: MRM-536
URL: http://jira.codehaus.org/browse/MRM-536
Project: Archiva
Issue Type: Bug
Components: build
Affects Versions: 1.0-beta-3
Reporter: Joakim Erdfelt
Attachments: hs_err_pid30832.log
{noformat}
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
to
/home/joakim/.m2/repository-archiva/org/apache/maven/archiva/archiva-metadata-reports/1.0-beta-3-SNAPSHOT/archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
[INFO]
[INFO] Building Archiva Reporting :: Project Reports
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/classes
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/test-classes
[INFO] Deleting directory
/home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/site
[INFO] [plexus:descriptor {execution: generate}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb79a4afd, pid=30832, tid=3085063872
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode, sharing)
# Problematic frame:
# V [libjvm.so+0x324afd]
#
# An error report file with more information is saved as hs_err_pid30832.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted (core dumped)
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MCHANGELOG-67) Add parameter to allow errors during build
[
http://jira.codehaus.org/browse/MCHANGELOG-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109594
]
Shelley B commented on MCHANGELOG-67:
-
Another use case to validate this feature request is to allow local builds to
succeed when the scm is unavailable (if either the server is down or the build
is occurring offline).
> Add parameter to allow errors during build
> --
>
> Key: MCHANGELOG-67
> URL: http://jira.codehaus.org/browse/MCHANGELOG-67
> Project: Maven 2.x Changelog Plugin
> Issue Type: New Feature
>Reporter: Shelley B
>Priority: Minor
>
> Adding a parameter to prevent BUILD ERRORs when an error occurs in the
> changelog plugin could be quite convenient in certain cases. For example,
> when a project is copied or branched temporarily (or initially created), the
> SCM URLs defined in the POM may not always be updated. When the SCM path is
> not found, it causes the entire build to fail.
> {noformat}
> [INFO] Generate "Change Log" report.
> [INFO] Generating changed sets xml to: C:\the-project\target\changelog.xml
> [INFO] Executing: svn --non-interactive log -v -r "{2007-06-25 15:25:29
> +}:{2007-07-26 15:25:29 +}"
> https://scm.url/svn/the.group.id/trunk/the-project/
> [INFO] Working directory: C:\the-project\src\main\java
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on
> '/svn/!svn/bc/28239/the.group.id/trunk/the-project'
> svn: '/svn/!svn/bc/28239/the.group.id/trunk/the-project' path not found
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: An error is occurred during
> changelog command :
> Command failed.
> {noformat}
> An optional boolean parameter such as ${maven.changelog.error.ignore} could
> be quite convenient in such cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-2254) the encoding parameter in xml declaration of POM is ignored
[ http://jira.codehaus.org/browse/MNG-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109597 ] Brian Fox commented on MNG-2254: Can someone make an IT for this? See the instructions here: http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test > the encoding parameter in xml declaration of POM is ignored > > > Key: MNG-2254 > URL: http://jira.codehaus.org/browse/MNG-2254 > Project: Maven 2 > Issue Type: Bug > Components: POM::Encoding >Reporter: Naoki Nose >Assignee: Jason van Zyl > Fix For: 2.0.8 > > Attachments: DefaultMavenProjectBuilder.diff, MNG-2254-2.diff, > MNG-2254.diff, MNG-2254_artifact.diff, MNG-2254_components.diff, > modello-plugin-xpp3.diff > > > DefaultMavenProjectBuilder reads POM in system default character encoding, > and the encoding parameter in xml declartion is ignored. > to fix this problem, We should > - fix modello-plugin-xpp3 to use the xml parser which is able to handle the > encoding parameter properly > - regenerate maven-model using fixed modello-plugin-xpp3 > - fix DefaultMavenProjectBuilder to use regenerated maven-model properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-534) Test failure in RepositoryContentConsumerUtilTest
[
http://jira.codehaus.org/browse/MRM-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt closed MRM-534.
--
Assignee: Joakim Erdfelt
Resolution: Fixed
Made mock verification OS neutral.
Fixed in archiva/trunk.
> Test failure in RepositoryContentConsumerUtilTest
> -
>
> Key: MRM-534
> URL: http://jira.codehaus.org/browse/MRM-534
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
> Environment: JDK 1.5.0_11
> Windows XP
> Maven 2.0.7
>Reporter: ajbanck
>Assignee: Joakim Erdfelt
> Fix For: 1.0-beta-3
>
>
> Building from archiva/trunk, using 'mvn clean build' from the root, JDK
> 1.5.0_11
> 1 test is failing in RepositoryContentConsumerUtilTest:
> ---
> Test set:
> org.apache.maven.archiva.repository.scanner.RepositoryContentConsumerUtilTest
> ---
> Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<<
> FAILURE!
> testExecution(org.apache.maven.archiva.repository.scanner.RepositoryContentConsumerUtilTest)
> Time elapsed: 0.031 sec <<< FAILURE!
> junit.framework.AssertionFailedError:
> Expectation failure on verify:
> processFile("path/to/test-file.txt"): expected: 1, actual: 0
> at org.easymock.MockControl.verify(MockControl.java:205)
> at
> org.apache.maven.archiva.repository.scanner.RepositoryContentConsumerUtilTest.testExecution(RepositoryContentConsumerUtilTest.java:140)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MECLIPSE-252) Error trying to create an EAR project that contains one web module. It doesn't point to the local project, but only tries to find it in the local and remote
[ http://jira.codehaus.org/browse/MECLIPSE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109409 ] Daniel Bourgeois edited comment on MECLIPSE-252 at 10/10/07 5:24 PM: - Only workaround I can find is installing the artifacts locally. That shouldn't be necessary. was: I ran into this issue as well.. On a hunch I took a look at the order of my modules in my parent pom.xml, and noticed the ear was listed before one of my war projects. Normally maven figures out the correct order when doing a build, but for the eclipse plugin, looks like it doesn't resolve the order correctly based on the dependencies. At any rate, I made sure my ear project was the last one in the module order, and that seems to have done the trick. > Error trying to create an EAR project that contains one web module. It > doesn't point to the local project, but only tries to find it in the local > and remote repositories. > -- > > Key: MECLIPSE-252 > URL: http://jira.codehaus.org/browse/MECLIPSE-252 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution >Affects Versions: 2.3 >Reporter: Daniel Alheiros > > I have one structure that defines 3 projects: > project1-jar > project2-war > project3-ear > project2-war is just a WAR that contains the project1-jar as a library > (WEB-INF/lib) > project3-ear is an EAR that contains project2-war as its only web module. > When I run mvn package it works perfectly and creates the EAR containing the > proper WAR file and the application.xml, so it works fine, but when I run mvn > eclipse:eclipse to generate the projects, the ear project is not generated > properly as it tries to find the war in the local and remote repository as > the piece of logging show bellow: > [INFO] Building project3-ear > [INFO]task-segment: [eclipse:eclipse] > [INFO] > > [INFO] Preparing eclipse:eclipse > Downloading: > http://mycompany.central-repository/repo/com/mycompany/project2-war/1.0-SNAPSHOT/project2-war-1.0-SNAPSHOT.war > [WARNING] Unable to get resource > 'mycompanygroupid:project2-war:war:1.0-SNAPSHOT' from repository > mycompany.central-repository (http://mycompany.central-repository/repo) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) mycompanygroupid:project2-war:war:1.0-SNAPSHOT > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=mycompanygroupid > -DartifactId=project2-war \ > -Dversion=1.0-SNAPSHOT -Dpackaging=war -Dfile=/path/to/file > Path to dependency: > 1) mycompanygroupid:project3-ear:ear:1.0-SNAPSHOT > 2) mycompanygroupid:project2-war:war:1.0-SNAPSHOT > -- > 1 required artifact is missing. > for artifact: > mycompanygroupid:project3-ear:ear:1.0-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > mycompany.central-repository (http://mycompany.central-repository/repo) > If I follow this instructions and install my WAR file to my local repository, > it then works and makes my EAR project, but I believe it shouldn't be > necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-432) Proxy Connectors are unable to download artifacts with alpha numerical version numbers
[ http://jira.codehaus.org/browse/MRM-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-432. -- Resolution: Fixed Tested and verified as fixed with real project against standalone archiva server running codebase from current archiva/trunk. > Proxy Connectors are unable to download artifacts with alpha numerical > version numbers > -- > > Key: MRM-432 > URL: http://jira.codehaus.org/browse/MRM-432 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-alpha-2 > Environment: Solaris 5.9, java 1.5.0_11, maven 2.0.7 >Reporter: Mathias Arens >Assignee: Joakim Erdfelt >Priority: Critical > Fix For: 1.0-beta-3 > > > Archiva is unable to download this artifact: > > ch.ethz.ganymed > ganymed-ssh2 > build210 > > although it is in the central repository. I can download the artifact if a > switch the central mirror of, just downloading the artifact directly over > maven. I didn't had any problems with all the other artifacts from the > central repository. > I assume that there is a problem with alpha numerical version numbers. But > it's just a guess. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-519) fail to resolve artifactId for libs that contain versionKeyword in artifactId, like "maven-test-plugin"
[ http://jira.codehaus.org/browse/MRM-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-519. -- Resolution: Fixed Tested with several maven 1 (versions 1.0.2, 1.1-beta-3, and 1.1) projects. Added maven-test-plugin to each project's dependencies (just for giggles) Found a double slash bug that maven 1 introduces into the URL. Fixed in archiva/trunk revision 583638. > fail to resolve artifactId for libs that contain versionKeyword in > artifactId, like "maven-test-plugin" > --- > > Key: MRM-519 > URL: http://jira.codehaus.org/browse/MRM-519 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: nicolas de loof >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > Attachments: RepositoryLayoutUtils.patch > > > Trying to get maven-test-plugin (using maven1) fails in 404. Archiva is > searching for > "\maven\maven\test-plugin-1.8.2\maven-test-plugin-1.8.2.jar" > RepositoryLayoutUtils tries to detect the artifact Id by searching for some > version keyword in the request string. As "test[09]*" is a version keyword, > it resolves to "maven". > The attached path add the feature of checking that all tokens in the version > part - all after artifactId expect the latest (classifier) - are valid > version keywords. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (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 closed MRM-461.
--
Resolution: Fixed
Added URL + Resource Path to log message in archiva/trunk.
> 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
>Assignee: Joakim Erdfelt
>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] Closed: (MRM-518) Changing the internal repository directory has no effect
[
http://jira.codehaus.org/browse/MRM-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt closed MRM-518.
--
Resolution: Duplicate
Closing as duplicate of MRM-493
> Changing the internal repository directory has no effect
>
>
> Key: MRM-518
> URL: http://jira.codehaus.org/browse/MRM-518
> Project: Archiva
> Issue Type: Bug
> Components: repository interface
>Affects Versions: 1.0-beta-2
> Environment: solaris 5.10, jdk 6
>Reporter: Mathias Arens
>Assignee: Joakim Erdfelt
> Fix For: 1.0-beta-3
>
>
> I changed the directory for the internal archiva repository from the default
> setting
> ${ARCHIVA_HOME}/data/repositories/internal
> to a different location. But new dependencies were still downloaded to the
> default/old directory.
> But after I restarted archiva everything is fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-493) Downloaded artifacts are stored in incorrect archiva-managed repository
[
http://jira.codehaus.org/browse/MRM-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109606
]
Joakim Erdfelt commented on MRM-493:
MRM-518 has been marked as a duplicate of this issue.
> 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
>Assignee: Joakim Erdfelt
>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] Closed: (MRM-512) Unable to convert null repository config to archiva repository.
[ http://jira.codehaus.org/browse/MRM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-512. -- Resolution: Cannot Reproduce Tested with latest archiva/trunk, unable to reproduce anymore. I suspect the repositories and proxy connector admin cleanup from a week ago cleared this up. > Unable to convert null repository config to archiva repository. > --- > > Key: MRM-512 > URL: http://jira.codehaus.org/browse/MRM-512 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: James William Dumay >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > Attachments: proxy connector removal.log, > update-repository-consumers.log, wrapper.20070924.log > > > Unable to convert null repository config to archiva repository. > I just deleted the default repositories and got a whole bunch of exceptions. > There also seems to be some first start schema exceptions in the logs also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-525) Typos on the hacking page
[
http://jira.codehaus.org/browse/MRM-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt closed MRM-525.
--
Resolution: Fixed
Applied into archiva/trunk.
> Typos on the hacking page
> -
>
> Key: MRM-525
> URL: http://jira.codehaus.org/browse/MRM-525
> Project: Archiva
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 1.0-beta-2
>Reporter: Alex Mayorga Adame
>Assignee: Joakim Erdfelt
>Priority: Trivial
> Fix For: 1.0-beta-3
>
> Attachments: MRM-525.patch
>
>
> Julien Graglia reported the following typos on the [mailing list |
> http://www.nabble.com/forum/ViewPost.jtp?post=12896988]
> {quote}
> Hi,
> I'am not sure it's the correct place but there are 2 little mistakes in
> http://maven.apache.org/archiva/hacking/index.html
> in section "Building Archiva"
> 1/the links to dl the connector and jta are broken : they include the
> corrects url but with a "download from..." prefix
> 2/the install command of jta is broken : a '-' is missing before
> Dversion=1.0.1B
> mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta
> -Dversion=1.0.1B -Dpackaging=jar -Dfile=jta-1_0_1B-classes.zip
> thats no real pbs, because if you start building archiva, you surely
> found (and correct) easyly those problems!
> --
> Julien Graglia
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (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:comment-tabpanel#action_109607
]
Joakim Erdfelt commented on MRM-493:
Confirmed as still a problem in archiva/trunk.
This is configuration listener issue somewhere in ...
* RepositoryServlet (or)
* RepositoryContentFactory (or)
* DefaultRepositoryProxyConnectors (or)
* RepositoryContentConsumers
> 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
>Assignee: Joakim Erdfelt
>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] Closed: (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 closed MRM-493.
--
Resolution: Fixed
Fixed in archiva/trunk revision 583646.
> 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
>Assignee: Joakim Erdfelt
>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: (CONTINUUM-1516) Unable to send mail
[ http://jira.codehaus.org/browse/CONTINUUM-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated CONTINUUM-1516: Description: here is the trace log 9884077 [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.ContinuumNotificationDispatcher:default - Error while trying to use the mail notifier. org.codehaus.plexus.notification.NotificationException: INTERNAL ERROR: The current build wasn't the first in the build list. Current build: '288', first build: '284'. at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.getPreviousBuild(MailContinuumNotifier.java:554) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:241) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:227) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) My build has quite a few build definitions running at the same scheduler. ie builds are serialized was: here is the trace log 9884077 [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.ContinuumNotificationDispatcher:default - Error while trying to use the mail notifier. org.codehaus.plexus.notification.NotificationException: INTERNAL ERROR: The current build wasn't the first in the build list. Current build: '288', first build: '284'. at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.getPreviousBuild(MailContinuumNotifier.java:554) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:241) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:227) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) My build has quite a few build definitions running at the same scheduler. ie builds are serialized Fix Version/s: 1.1-beta-4 > Unable to send mail > --- > > Key: CONTINUUM-1516 > URL: http://jira.codehaus.org/browse/CONTINUUM-1516 > Project: Continuum > Issue Type: Bug > Components: Notifier - Mail >Affects Versions: 1.1-beta-3 > Environment: xp, maven 2.0.7, jse 5 >Reporter: Dan Tran > Fix For: 1.1-beta-4 > > > here is the trace log > 9884077 [pool-1-thread-1] ERROR > org.apache.maven.continuum.notification.ContinuumNotificationDispatcher:default > - Error while trying to use the mail notifier. > org.codehaus.plexus.notification.NotificationException: INTERNAL > ERROR: The current build wasn't the first in the build list. Current > build: '288', first build: '284'. >at > org.apache.maven.continuum.notification.mail.MailContinuumNotifier.getPreviousBuild(MailContinuumNotifier.java:554) >at > org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:241) >at > org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:227) >at > org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) >at > org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) > My build has quite a few build definitions running at the same scheduler. > ie builds are serialized -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1552) Upload mysql:mysql-connector-java:jar:5.0.6 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109614 ] Joshua Spiewak commented on MAVENUPLOAD-1552: - Is the rsync set up yet? 5.0.5 appears to be the latest version in the repo: http://repo1.maven.org/maven2/mysql/mysql-connector-java/ Is there another issue that should be watched for when this will be set up, and if not, is it appropriate for this one to be closed? > Upload mysql:mysql-connector-java:jar:5.0.6 to ibiblio > -- > > Key: MAVENUPLOAD-1552 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1552 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > > http://www.mattwhitlock.com/mysql-connector-java-5.0.6-bundle.jar > http://dev.mysql.com/downloads/connector/j/5.0.html > MySQL Connector/J is the official JDBC driver for MySQL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1516) Unable to send mail
[ http://jira.codehaus.org/browse/CONTINUUM-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109615 ] Dan Tran commented on CONTINUUM-1516: - I can surely confirm that 2 shell projects in the same group share the same default build. ie change the default configuration build def on one project will see the same settings on the other shell project > Unable to send mail > --- > > Key: CONTINUUM-1516 > URL: http://jira.codehaus.org/browse/CONTINUUM-1516 > Project: Continuum > Issue Type: Bug > Components: Notifier - Mail >Affects Versions: 1.1-beta-3 > Environment: xp, maven 2.0.7, jse 5 >Reporter: Dan Tran > Fix For: 1.1-beta-4 > > > here is the trace log > 9884077 [pool-1-thread-1] ERROR > org.apache.maven.continuum.notification.ContinuumNotificationDispatcher:default > - Error while trying to use the mail notifier. > org.codehaus.plexus.notification.NotificationException: INTERNAL > ERROR: The current build wasn't the first in the build list. Current > build: '288', first build: '284'. >at > org.apache.maven.continuum.notification.mail.MailContinuumNotifier.getPreviousBuild(MailContinuumNotifier.java:554) >at > org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:241) >at > org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:227) >at > org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) >at > org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) > My build has quite a few build definitions running at the same scheduler. > ie builds are serialized -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1552) Upload mysql:mysql-connector-java:jar:5.0.6 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109616 ] Mark Matthews commented on MAVENUPLOAD-1552: I haven't heard from the maven developers on this, since I posted the news in this issue, and on the mailing list. I've opened another issue to see if that gets any attention, so I'd suggest watching MAVENUPLOAD-1761. > Upload mysql:mysql-connector-java:jar:5.0.6 to ibiblio > -- > > Key: MAVENUPLOAD-1552 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1552 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > > http://www.mattwhitlock.com/mysql-connector-java-5.0.6-bundle.jar > http://dev.mysql.com/downloads/connector/j/5.0.html > MySQL Connector/J is the official JDBC driver for MySQL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1761) Please enable rsyncing of MySQL Connector/J
Please enable rsyncing of MySQL Connector/J Key: MAVENUPLOAD-1761 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1761 Project: maven-upload-requests Issue Type: Bug Reporter: Mark Matthews >From the dev mailing list - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Matthews wrote: > Hi folks, > > We've been handing you .jars for awhile, but I finally got our web team > to setup a rsync repository so that we can do this automagically. > > I have been working with Henri Yandell, through MAVENUPLOAD-1552, but I > wanted to see if you had any tools that could maintain the repository > structure based on the .jar files (with embedded POMs) that we've been > sending you. > > We don't use Maven to build our stuff, so I'm not really clued in on > what I have to do to get this all to work. I'm perfectly okay if you > tell me to "RTFM", I just don't know where in the manual to look this > stuff up. > > Thanks in advance! > > -Mark Hi! Okay, so I figured out how to do this. We've now got an rsync-able view of the repository that contains MySQL Connector/J ready for you to pull from at rsync.mysql.com:/web/sites/live/maven/ via SSH as user "maven " with your public key from http://www.ibiblio.org/maven/id_dsa.pub. Is this enough to go on, or do you need a shell script as well? Let me know if the layout works for you! -Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHBrO9tvXNTca6JD8RAv8hAJ4xFmrEJrU+HfUKG708tboFc2LsxgCfWP+S QpI6wIPdh8uUN6cqKOBj02c= =laWO -END PGP SIGNATURE- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-537) Deletion of artifacts from Archiva Managed Repositories not being detected
Deletion of artifacts from Archiva Managed Repositories not being detected -- Key: MRM-537 URL: http://jira.codehaus.org/browse/MRM-537 Project: Archiva Issue Type: Bug Components: repository scanning Affects Versions: 1.0-beta-2 Environment: Windows XP SP2 and Solaris - Default install run via plexus. Reporter: Graeme Steyn 1. Manually delete a tree of artifacts from the managed repository being used for testing, e.g. delete com.* tree. 2. In administration console select Repositories. 3. Click "Scan Repository Now" for test repository where artifacts were deleted. 4. Database > Update Database Now. 5. Browse. The index information has not been updated and the entire tree just deleted can still be browsed. Similarly, if you update a single POM for an artifact and its MD5/SHA files, then refresh, the changes are not reflected in the browser information for the POM -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-537) Deletion of artifacts from Archiva Managed Repositories not being detected
[ http://jira.codehaus.org/browse/MRM-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak closed MRM-537. --- Resolution: Duplicate > Deletion of artifacts from Archiva Managed Repositories not being detected > -- > > Key: MRM-537 > URL: http://jira.codehaus.org/browse/MRM-537 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 1.0-beta-2 > Environment: Windows XP SP2 and Solaris - Default install run via > plexus. >Reporter: Graeme Steyn > > 1. Manually delete a tree of artifacts from the managed repository being used > for testing, e.g. delete com.* tree. > 2. In administration console select Repositories. > 3. Click "Scan Repository Now" for test repository where artifacts were > deleted. > 4. Database > Update Database Now. > 5. Browse. > The index information has not been updated and the entire tree just deleted > can still be browsed. Similarly, if you update a single POM for an artifact > and its MD5/SHA files, then refresh, the changes are not reflected in the > browser information for the POM -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-537) Deletion of artifacts from Archiva Managed Repositories not being detected
[ http://jira.codehaus.org/browse/MRM-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109618 ] Wendy Smoak commented on MRM-537: - The deletion issue is already open as MRM-37, so I marked this as a duplicate based on the summary. I've also experienced the issue with POM changes not being picked up. You can open a separate issue for that, if there isn't one already. > Deletion of artifacts from Archiva Managed Repositories not being detected > -- > > Key: MRM-537 > URL: http://jira.codehaus.org/browse/MRM-537 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 1.0-beta-2 > Environment: Windows XP SP2 and Solaris - Default install run via > plexus. >Reporter: Graeme Steyn > > 1. Manually delete a tree of artifacts from the managed repository being used > for testing, e.g. delete com.* tree. > 2. In administration console select Repositories. > 3. Click "Scan Repository Now" for test repository where artifacts were > deleted. > 4. Database > Update Database Now. > 5. Browse. > The index information has not been updated and the entire tree just deleted > can still be browsed. Similarly, if you update a single POM for an artifact > and its MD5/SHA files, then refresh, the changes are not reflected in the > browser information for the POM -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-538) Browse > Info not synchronised with updated POM contents
Browse > Info not synchronised with updated POM contents Key: MRM-538 URL: http://jira.codehaus.org/browse/MRM-538 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-2 Environment: Windows XP SP2 and Solaris - Default install run via plexus. JDK1.6.0_03. Reporter: Graeme Steyn 1. Take an existing POM in the repository and modify its contents (I changed the description). 2. In administration console select Repositories. 3. Click "Scan Repository Now" for test repository where POM was changed. 4. Database > Update Database Now. 5. Browse to POM location. The index information has not been updated, the changes are not reflected in the browse > info section for the POM. Step 1 can be replaced with the modification of the POM outside of the repository, followed by the redeployment of the POM ad associated jar to the repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-512) Unable to convert null repository config to archiva repository.
[ http://jira.codehaus.org/browse/MRM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109622 ] Arnaud Heritier commented on MRM-512: - Personally I reproduced it one week ago with the trunk. I just removed all repositories and proxy connectors defined by default and archiva never restarted (was on win 2003 server / tomcat 5.5) > Unable to convert null repository config to archiva repository. > --- > > Key: MRM-512 > URL: http://jira.codehaus.org/browse/MRM-512 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: James William Dumay >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > Attachments: proxy connector removal.log, > update-repository-consumers.log, wrapper.20070924.log > > > Unable to convert null repository config to archiva repository. > I just deleted the default repositories and got a whole bunch of exceptions. > There also seems to be some first start schema exceptions in the logs also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
