[jira] Updated: (MRM-728) After successful admin login archiva reacts as if user is guest
[ http://jira.codehaus.org/browse/MRM-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-728: - Priority: Critical (was: Major) After successful admin login archiva reacts as if user is guest --- Key: MRM-728 URL: http://jira.codehaus.org/browse/MRM-728 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: linux Reporter: Robin Roos Priority: Critical Fix For: 1.0.x Attachments: archiva.log I ran Archiva on my windows box and, after configuring the admin user, I was able to login. The header of the web page identified me as Administrator (admin) and I could see all the expected functions on the left hand frame. So far so good. I had Archiva installed on a linux box and started. I surfed to the box from Windows and configured the admin user. But when I logged in as admin I got a page with only Search/FindArtifact/Browse functions. The header page reads Login - Register. It is as if I am not logged in and am seeing the guest functions. Note that if I log in with a deliberately incorrect password then I get an error message as expected. But logging in with the right credentials appears to fail silently. As a result I cannot deploy any artifacts into Archiva, I cannot roll out the maven/subversion/archiva based edition of our in-house project, and I fear my time is limited! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-775) Support generation of pom for legacy artifacts in web upload form
[ http://jira.codehaus.org/browse/MRM-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-775: - Fix Version/s: 1.x Support generation of pom for legacy artifacts in web upload form - Key: MRM-775 URL: http://jira.codehaus.org/browse/MRM-775 Project: Archiva Issue Type: New Feature Components: web application Affects Versions: 1.1 Reporter: Maria Odea Ching Fix For: 1.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-774) Support inclusion of pom file when deploying an artifact via the web upload form
[ http://jira.codehaus.org/browse/MRM-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-774: - Fix Version/s: 1.x Support inclusion of pom file when deploying an artifact via the web upload form Key: MRM-774 URL: http://jira.codehaus.org/browse/MRM-774 Project: Archiva Issue Type: New Feature Components: web application Affects Versions: 1.1 Reporter: Maria Odea Ching Fix For: 1.x Currently the web upload form only supports pom generation when uploading M2 artifacts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPH-39) New target to display useful information from a project
New target to display useful information from a project --- Key: MPH-39 URL: http://jira.codehaus.org/browse/MPH-39 Project: Maven 2.x Help Plugin Issue Type: New Feature Affects Versions: 2.0.1 Reporter: Martin von Gagern When there is a bug in some library, you might wish to have a look at its issue tracking system, or at its source code repository to look if it has already been fixed. To do so, you need to know the group and artifact id of the library containing the bug, and then one can start looking at the pom in the local repository. In the case of multi-modules, this is likely to reference a parent, and not provide any URLs itself, so you repeat the steps for the parent, recursively. After doing so for three libraries today, I believe the help plugin should do this automatically. I could imagine three possibilities. 1. Integrate into the already lengthy help:describe output 2. Provide help:urls so you can do mvn help:urls -DgroupId=some.group -DartifactId=buggy-library and it would list all effective pom elements designed to contain URLs, probably excepting all developer and contributor URLs, and take care of proper inheritance. 3. Provide help:property so you can do mvn help:property -DgroupId=some.group -DartifactId=buggy-library -Dproperty=project.scm.url to get at single properties, again with inheritance handled by the mojo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3510) download with http 403 status code assumed by maven to be OK, then checksum failed error
[
http://jira.codehaus.org/browse/MNG-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130234#action_130234
]
Milos Kleint commented on MNG-3510:
---
I'm wondering if you could try the latest mevenide daily builds from
http://deadlock.netbeans.org/hudson/job/mevenide That version (3.1-SNAPSHOT) is
using the latest 2.1-SNAPSHOT of maven. while the currently released version
uses equivalent of 2.0.4 maven.
But since you state the version of maven is 2.0.6, I assume running on command
line with 2.0.6 is showing the same symptoms..
download with http 403 status code assumed by maven to be OK, then checksum
failed error
Key: MNG-3510
URL: http://jira.codehaus.org/browse/MNG-3510
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.6
Environment: Win xp pro., JDK6, mvn 2.0.6, netbeans 6, mevenide
plugin in netbeans.
Reporter: Bruce Chapman
Priority: Minor
Our firewall/cache is blocking access to
http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.jar becuase it
thinks it has a virus (that's the not the problem)
{{$ wget http://repo1.maven.org/maven2/javax/mail/mail
--14:13:46-- http://repo1.maven.org/maven2/javax/mail/mail
= `mail'
Resolving cache... done.
Connecting to cache[172.30.41.11]:8080... connected.
Proxy request sent, awaiting response... 403 Forbidden
14:13:47 ERROR 403: Forbidden.}}
but the firewall also returns content for the browser
{{
htmlheadMETA HTTP-EQUIV=Expires CONTENT=-1META HTTP-EQUIV=Pragma
CONTENT=no-cacheMETA HTTP-EQUIV=Cache-Control CONTENT=no-cachemeta
http-equiv=Content-Type content=text/html; charset=UTF-8titleSonicWALL
- Blocked by Application Firewall/title/headbody bgcolor=#011B4A
text=#FFbrbrbrbrbrtable align=center cellpadding=5 border=2
width=500 bgcolor=#9CBACEtrtd align=centertable align=center
cellpadding=5 width=450trtd align=centerbrbrfont face=arial
color=00 size=4bThis request is blocked by the SonicWALL Gateway
Anti-Virus Service. Name: WMF.Gen-2
(Exploit)/b/font/td/tr/table/td/tr/table/body/html
}}
The problem is that maven is ignoring the status code, goes ahead and
downloads the file then decides that the checksum for the content does not
match what is expected. This is misleading and makes it more difficult to
diagnose the cause of the failed download.
Here is what maven does
{{
Building Hudson core
task-segment: [install]
Maven Version: 2.0.6
JDK Version: 1.6.0_05 normalized as: 1.6.0-5
OS Info: Arch: x86 Family: windows Name: windows xp Version: 5.1
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.pom
993/993b
993b downloaded
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.jar
696/?
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'e0bb0f663e436cde3a6e1e5b8e8e80be43bde8a3'; remote =
'1aa1579ae5ecd41920c4f355b0a9ef40b68315dd' - RETRYING
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.jar
696/?
}}
Maven should only go on and download the file and compare checksums if the
http status is valid eg 200, in the case of a failing http status code, it
would be much more useful if maven failed earlier with the status code and
text as the error message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MASSEMBLY-304) Dependencies interpreted differently when running mvn on windows vs. linux
[ http://jira.codehaus.org/browse/MASSEMBLY-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Roos closed MASSEMBLY-304. Resolution: Fixed I am closing this issue because the discrepency was caused by inadvertantly running different versions of the assembly plugin (2.2-beta-1 on Windows, 2.2-beta-2 on Linux). I do, however, believe dependencySet:excludes/includes to be broken in 2.2-beta-2 and will open a new JIRA issue to examine this. Dependencies interpreted differently when running mvn on windows vs. linux -- Key: MASSEMBLY-304 URL: http://jira.codehaus.org/browse/MASSEMBLY-304 Project: Maven 2.x Assembly Plugin Issue Type: Bug Environment: C:\Documents and Settings\rroosmvn -version Maven version: 2.0.8 Java version: 1.5.0_14 OS name: windows xp version: 5.1 arch: x86 Family: windows $ mvn -version Maven version: 2.0.8 Java version: 1.5.0_15 OS name: linux version: 2.6.18-8.el5 arch: amd64 Family: unix Reporter: Robin Roos My project has a large number of .jar files WITHOUT classifiers, and a small number of .so and .dll files WITH classifiers. Using the dependency sets specified below I get different results running maven on windows vs. running on linux. When I run on Windows, my resulting .tar contains many .jar files in lib/ When I run on Linux, the same jars are absent from lib/ but all appear in both nativelib/linux_2x/ and nativelib/linux_3x/ and nativelib/solaris/ Furthermore, the classifier-based artifacts appear in all three nativelib folders and retain their classifier suffix, e.g. $ tar tf ./work/4/target/calypsoCustom-9.2.0-build-70-unix.tar | grep \.so calypso-9.2.0-build-70/nativelib/solaris/com.ibm.mq.soap-9.2.0.jar calypso-9.2.0-build-70/nativelib/solaris/libFDacsLib-5.1-solaris.so calypso-9.2.0-build-70/nativelib/solaris/libFDacsLib-5.1-linux_2x.so calypso-9.2.0-build-70/nativelib/solaris/libFDacsLib-5.1-linux_3x.so calypso-9.2.0-build-70/nativelib/solaris/libsass3j-5.1-solaris.so calypso-9.2.0-build-70/nativelib/solaris/libsass3j-5.1-linux_2x.so calypso-9.2.0-build-70/nativelib/solaris/libsass3j-5.1-linux_3x.so calypso-9.2.0-build-70/nativelib/linux_2x/com.ibm.mq.soap-9.2.0.jar calypso-9.2.0-build-70/nativelib/linux_2x/libFDacsLib-5.1-solaris.so calypso-9.2.0-build-70/nativelib/linux_2x/libFDacsLib-5.1-linux_2x.so calypso-9.2.0-build-70/nativelib/linux_2x/libFDacsLib-5.1-linux_3x.so calypso-9.2.0-build-70/nativelib/linux_2x/libsass3j-5.1-solaris.so calypso-9.2.0-build-70/nativelib/linux_2x/libsass3j-5.1-linux_2x.so calypso-9.2.0-build-70/nativelib/linux_2x/libsass3j-5.1-linux_3x.so calypso-9.2.0-build-70/nativelib/linux_3x/com.ibm.mq.soap-9.2.0.jar calypso-9.2.0-build-70/nativelib/linux_3x/libFDacsLib-5.1-solaris.so calypso-9.2.0-build-70/nativelib/linux_3x/libFDacsLib-5.1-linux_2x.so calypso-9.2.0-build-70/nativelib/linux_3x/libFDacsLib-5.1-linux_3x.so calypso-9.2.0-build-70/nativelib/linux_3x/libsass3j-5.1-solaris.so calypso-9.2.0-build-70/nativelib/linux_3x/libsass3j-5.1-linux_2x.so calypso-9.2.0-build-70/nativelib/linux_3x/libsass3j-5.1-linux_3x.so whereas when built on windows I get $ tar tf ./work/4/target/calypsoCustom-9.2.0-build-70-unix.tar | grep \.so calypso-9.2.0-build-70/nativelib/solaris/libFDacsLib-5.1.so calypso-9.2.0-build-70/nativelib/solaris/libsass3j-5.1.so calypso-9.2.0-build-70/nativelib/linux_2x/libFDacsLib-5.1.so calypso-9.2.0-build-70/nativelib/linux_2x/libsass3j-5.1.so calypso-9.2.0-build-70/nativelib/linux_3x/libFDacsLib-5.1.so calypso-9.2.0-build-70/nativelib/linux_3x/libsass3j-5.1.so (each .so exists in the appropriate nativelib subfolder and has had the classifier suffix removed, but each one is different and is the one applicable to the platform) dependencySets dependencySet outputDirectory/lib/outputDirectory excludes exclude*:*:so:solaris/exclude exclude*:*:so:linux_2x/exclude exclude*:*:so:linux_3x/exclude exclude*:*:dll:windows/exclude /excludes /dependencySet dependencySet outputDirectory/nativelib/solaris/outputDirectory includes include*:*:so:solaris/include /includes /dependencySet dependencySet outputDirectory/nativelib/linux_2x/outputDirectory includes include*:*:so:linux_2x/include /includes /dependencySet dependencySet outputDirectory/nativelib/linux_3x/outputDirectory includes include*:*:so:linux_3x/include /includes /dependencySet /dependencySets -- This message is automatically generated by JIRA. - If you
[jira] Created: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file
Ability to generate pom.xml file from an existing Visual Studio solution file - Key: NMAVEN-119 URL: http://jira.codehaus.org/browse/NMAVEN-119 Project: NMaven Issue Type: New Feature Affects Versions: 0.14 (Unreleased) Reporter: jan ancajas the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files then generate the pom for every module of the 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] Commented: (MRM-728) After successful admin login archiva reacts as if user is guest
[ http://jira.codehaus.org/browse/MRM-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130232#action_130232 ] Robin Roos commented on MRM-728: Any further update on this? My developers are having to use FireFox (which itslef is no bad thing) in violation of a corporate policy to use only IE. After successful admin login archiva reacts as if user is guest --- Key: MRM-728 URL: http://jira.codehaus.org/browse/MRM-728 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: linux Reporter: Robin Roos Fix For: 1.0.x Attachments: archiva.log I ran Archiva on my windows box and, after configuring the admin user, I was able to login. The header of the web page identified me as Administrator (admin) and I could see all the expected functions on the left hand frame. So far so good. I had Archiva installed on a linux box and started. I surfed to the box from Windows and configured the admin user. But when I logged in as admin I got a page with only Search/FindArtifact/Browse functions. The header page reads Login - Register. It is as if I am not logged in and am seeing the guest functions. Note that if I log in with a deliberately incorrect password then I get an error message as expected. But logging in with the right credentials appears to fail silently. As a result I cannot deploy any artifacts into Archiva, I cannot roll out the maven/subversion/archiva based edition of our in-house project, and I fear my time is limited! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSITE-159) Absolute URI rendered as relative URI if absolute URI related to domain of POM URI
[ http://jira.codehaus.org/browse/MSITE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130243#action_130243 ] Philip May commented on MSITE-159: -- This bug is realy ugly cause this way it's very difficult to have a sourceforge project site build by maven... With a Sorceforge project you have to link to them... Absolute URI rendered as relative URI if absolute URI related to domain of POM URI -- Key: MSITE-159 URL: http://jira.codehaus.org/browse/MSITE-159 Project: Maven 2.x Site Plugin Issue Type: Bug Components: relative links Reporter: Ted Husted Under site-beta5 if the POM references a URI like urlhttp://struts.apache.org/url absolute URLs used in the site.xml file are converted to relative references. For example a reference to to http://struts.apache.org/1.x; becomes 1.x, and a reference to just http://struts.apache.org; becomes an empty string. If the documentation is being used offline, there are many cases when we want to refer people back to the website, to be sure the current information is used. The best use case is a download page that determines the mirror via CGI. Another use case is referring to a sister site in the domain, that might refer to another version. If used locally, the other site might not be in the relative location. Switching back to beta4 cures the behavior, and absolute URIs remain absolute, as expected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-426) faces-config.xml graphic editor not works
faces-config.xml graphic editor not works
--
Key: MECLIPSE-426
URL: http://jira.codehaus.org/browse/MECLIPSE-426
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: WTP support
Affects Versions: 2.5.1
Environment: Windows-XP
Reporter: Marco Noto
In a jsf project with structure like this:
--src/main/java
--src/main/resources
I've faces-config.xml in /META-INF directory, placed under src/main/resources.
My pom.xml include this configuration:
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
configuration
wtpversion2.0/wtpversion
additionalProjectFacets
jst.web2.5/jst.web
jst.jsf1.2/jst.jsf
jst.ejb3.0/jst.ejb
/additionalProjectFacets
/configuration
/plugin
{code}
After mvn eclipse:eclipse i've under .project directory, the file
org.eclipse.wst.common.component:
{code}
project-modules id=moduleCoreId project-version=2.0
wb-module deploy-name=eos-components
wb-resource deploy-path=/ source-path=src/main/java/
wb-resource deploy-path=/ source-path=src/main/resources/
/wb-module
/project-modules
{code}
Now, if i open faces-config.xml with graphic editor, i've some error in eclipse
log, and i can't use it, neither i can save the file! (in the log: !MESSAGE
Resource '/eos-components/src/main/java/eos-components/src/main/resources' does
not exist.)
But if I manually invert the order of wb-resources, all works fine!
wb-resource deploy-path=/ source-path=src/main/resources/
wb-resource deploy-path=/ source-path=src/main/java/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-482) Surefire tries to run JUnit4 tests that contain no @Test annotations
Surefire tries to run JUnit4 tests that contain no @Test annotations Key: SUREFIRE-482 URL: http://jira.codehaus.org/browse/SUREFIRE-482 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.4.2 Reporter: Mark Hobson Attachments: test.zip Similar to SUREFIRE-346 but for JUnit4, Surefire tries to run classes that contain no @Test annotations as tests, resulting in the exception: java.lang.Exception: No runnable methods at org.junit.internal.runners.MethodValidator.validateInstanceMethods(MethodValidator.java:32) at org.junit.internal.runners.MethodValidator.validateMethodsForDefaultRunner(MethodValidator.java:43) at org.junit.internal.runners.JUnit4ClassRunner.validate(JUnit4ClassRunner.java:36) at org.junit.internal.runners.JUnit4ClassRunner.init(JUnit4ClassRunner.java:27) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.junit.internal.requests.ClassRequest.buildRunner(ClassRequest.java:33) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:28) at org.apache.maven.surefire.junit4.JUnit4TestSet.init(JUnit4TestSet.java:45) at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209) at org.apache.maven.surefire.Surefire.run(Surefire.java:156) 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) Such classes should be ignored by Surefire. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPIR-93) MPIR ignores reports set declared in child modules
[ http://jira.codehaus.org/browse/MPIR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130230#action_130230 ] Michael Osipov commented on MPIR-93: Thanks for your reply. are ypu proposing file this at maven jira or rather consider this as a won't fix? The desired behavior does seem the most reasonable to me. Mike MPIR ignores reports set declared in child modules -- Key: MPIR-93 URL: http://jira.codehaus.org/browse/MPIR-93 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Affects Versions: 2.0.1 Reporter: Michael Osipov I have declared my parent POM to produce selective reports only, see [here|http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4/pom.xml#L114]. Then I reclared the child modules to produces less reports but they still produce the same reports as the parent pom. See [here|http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4/fckeditor-java/pom.xml#L127] and [there|http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4/fckeditor-java-demo/pom.xml#L105]. this is a bug to me, breaking inheritance override. You may [checkout|http://svn.fckeditor.net/FCKeditor.Java/branches/2.4/] my project and try yourself. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-770) Archiva web client does not recognize classifier
[ http://jira.codehaus.org/browse/MRM-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130231#action_130231 ] Robin Roos commented on MRM-770: That matches my understanding which is why I was reluctant to hack the POM on the repository filesystem. Clearly Maven can resolve these from Archiva without dificulty, so we're just talking about a web visualization issue. Thanks. Archiva web client does not recognize classifier Key: MRM-770 URL: http://jira.codehaus.org/browse/MRM-770 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: Apache Archiva 1.0.1 $ uname -a Linux hostname 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14 EST 2007 x86_64 x86_64 x86_64 GNU/Linux $ java -version java version 1.5.0_15 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_15-b04, mixed mode) $ mvn -version Maven version: 2.0.8 Java version: 1.5.0_15 OS name: linux version: 2.6.18-8.el5 arch: amd64 Family: unix Reporter: Robin Roos Priority: Minor Fix For: 1.0.x I've started using classifiers with some of my native libraries. The Web application does not represent the classifier, and the artifact is not downloadable from the web application. My builds are occurring correctly, so Maven has no difficulty retrieving the artifacts. As an example, I have put the following into my local Archiva repository: reutersRFA:libFDacsLIB:5.1:solaris reutersRFA:libFDacsLIB:5.1:linux_2x reutersRFA:libFDacsLIB:5.1:linux_3x The deploy command I use to achieve this was: mvn deploy:deploy-file -Dfile=libFDacsLib.so -DgroupId=reutersRFA -DartifactId=libFDacsLib -Dversion=5.1 -Dpackaging=so -Dclassifier=solaris -DgeneratePom=true -DrepositoryId=archiva.default -Durl=http://invldnlspare1:9100/archiva/repository/internal/ et. sim for -Dclassifier=linux_2x and -Dclassifier=linux_3x In the archiva repository filesystem I see: $ find /appdata/archiva -name *libFDacsLib* ./data/repositories/internal/reutersRFA/libFDacsLib ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1.pom ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1-linux_3x.so.md5 ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1-solaris.so.sha1 ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1-linux_2x.so ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1.pom.sha1 ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1-linux_2x.so.sha1 ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1-linux_3x.so.sha1 ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1-linux_3x.so ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1-solaris.so ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1-linux_2x.so.md5 ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1.pom.md5 ./data/repositories/internal/reutersRFA/libFDacsLib/5.1/libFDacsLib-5.1-solaris.so.md5 $ Note that there is only one *.pom, and there is no .so without a classifier extension. In the web gui I can browse as far as [top] / reutersRFA / libFDacsLib / 5.1 Inside this I see a POM Dependency Snippet which does not mention the classifier: dependency groupIdreutersRFA/groupId artifactIdlibFDacsLib/artifactId version5.1/version typeso/type /dependency I have a link to download the POM, but I have no link to download any actual artifact. No mention is made of solaris, linux_2x or linux_3x anywhere on the web page. I suspect the POM has been stripped of the classifier by archiva when maven deployed the artifact. As far as Archiva is concerned, there is only one POM which references an artifact that does not exist on the filesystem (no libFDacsLib.so file) since it's looking without the classifier extension. Naturally I'd like to see a fix in a future version of Archiva if indeed Archiva is causing the problem. In the mean-time I would appreciate guidence as to whether I should create three separate POMs that specify the three classifier values to replace the existing POM in the archva repository filesystem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (WAGON-70) Deploying using scp:// hangs when proxy configured in settings.xml
[ http://jira.codehaus.org/browse/WAGON-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130250#action_130250 ] Thierry Bressure commented on WAGON-70: --- I got a similar error. I can't scp to deploy artifact with maven 2.0.8. All work fine with maven 2.0.4 After some investigation i find that maven 2.0.4 used jcraft 0.1.23 which simply ignore the response code of the proxy. But maven 2.0.8 use jcraft 0.1.37 which test the response code of the proxy. Since the class proxy used by wagon is proxyHTTP so in both case we should have an error. wagon should test if the proxy in settings.xml is enable and the protocol which the proxy is designed. Here are technical information: com.jcraft.jsch.ProcyHTTP.connect(122) version 0.1.37 Deploying using scp:// hangs when proxy configured in settings.xml -- Key: WAGON-70 URL: http://jira.codehaus.org/browse/WAGON-70 Project: wagon Issue Type: Bug Components: wagon-ssh Affects Versions: 1.0-beta-2 Environment: Windows XP in a corporate environment that is proxied and firewalled to everywhere Reporter: Stephen Coy For some reason, wagon-ssh is attempting to connect to the proxy defined in settings.xml (irrespective of whether it is enabled or not) in order to perform an scp transfer. This causes goals such as site:deploy to hang for some time before proceeding normally. A thread dump taken during the hang: [INFO] [site:deploy] Full thread dump Java HotSpot(TM) Client VM (1.4.2_13-b06 mixed mode): Signal Dispatcher daemon prio=10 tid=0x009cf600 nid=0xa7c waiting on condition [0x..0x] Finalizer daemon prio=9 tid=0x009ccbb8 nid=0xb84 in Object.wait() [0x02b6f000..0x02b6fd68] at java.lang.Object.wait(Native Method) - waiting on 0x104fb160 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111) - locked 0x104fb160 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) Reference Handler daemon prio=10 tid=0x009cb830 nid=0xf38 in Object.wait() [0x02b2f000..0x02b2fd68] at java.lang.Object.wait(Native Method) - waiting on 0x104fb1c8 (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:429) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115) - locked 0x104fb1c8 (a java.lang.ref.Reference$Lock) main prio=5 tid=0x00035b28 nid=0xe90 runnable [0x0007f000..0x0007fc38] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.net.SocketInputStream.read(SocketInputStream.java:182) at com.jcraft.jsch.ProxyHTTP.connect(Unknown Source) at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(AbstractSshWagon.java:181) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:149) 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.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) 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:324) 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
[jira] Created: (ARCHETYPE-156) Incorrect parent after using archetype:create
Incorrect parent after using archetype:create --- Key: ARCHETYPE-156 URL: http://jira.codehaus.org/browse/ARCHETYPE-156 Project: Maven Archetype Issue Type: Bug Components: Plugin Environment: Windows XP Maven 2.0.7 Reporter: Per Lindfors Priority: Minor Hi, I'm not sure if this is a bug or lack of functionality, but here it goes... It seems that the archetype plugin (2.0-alpha-2) and the create-goal somehow alters the information in the parent segment of the resulting pom compared to what we have in the template pom. In my case we would like to be able to have a root pom project with multiple modules(ejb, war, jar etc). Each module has a parent which points to a super pom in our repository instead of the root pom project. When creating the modules with our archetype the module gets registred in the modules segment in the root pom project, but the parent segment with groupId and artifactId etc referes not to the super pom in our repo, but to the root project. Why? Desired result: Root project pom.xml --- project xmlns=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; modelVersion4.0.0/modelVersion groupIdse.xxx.yyy/groupId artifactIdyyy/artifactId version1.0-SNAPSHOT/version packagingpom/packaging name/name build .. /build modules moduleproject1/module moduleproject2/module moduleproject3/module /modules Modules pom.xml -- project xmlns=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; modelVersion4.0.0/modelVersion parent groupIdsuperpom-groupid/groupId artifactIdsuperpom-artifactId/artifactId versionsuperpom-version/version /parent groupIdse.aaa.bbb/groupId artifactIdproject1/artifactId version1.0-SNAPSHOT/version packagingwar/packaging ... /Per -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2011) databene benerator 0.5.1
databene benerator 0.5.1 Key: MAVENUPLOAD-2011 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2011 Project: maven-upload-requests Issue Type: Task Reporter: Volker Bergmann -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3160) Several integration tests have been disabled
[ http://jira.codehaus.org/browse/MNG-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3160: -- Summary: Several integration tests have been disabled (was: IT 126 is failing on trunk and maven-2.0.x branch) Several integration tests have been disabled Key: MNG-3160 URL: http://jira.codehaus.org/browse/MNG-3160 Project: Maven 2 Issue Type: Bug Components: integration tests Affects Versions: 2.0.8, 2.1-alpha-1 Reporter: Brett Porter Priority: Blocker Fix For: 2.0.x [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.maven.its.it0126:model:test-jar:tests:1.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.its.it0126 -DartifactId=model \ -Dversion=1.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.its.it0126 -DartifactId=model \ -Dversion=1.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.maven.its.it0126:client:jar:1.0-SNAPSHOT 2) org.apache.maven.its.it0126:model:test-jar:tests:1.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.maven.its.it0126:client:jar:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-305) dependencySet includes include[groupId]:[artifactId]:[type]:[classifier]/include syntax doesn't work
dependencySet includes
include[groupId]:[artifactId]:[type]:[classifier]/include syntax doesn't
work
Key: MASSEMBLY-305
URL: http://jira.codehaus.org/browse/MASSEMBLY-305
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Reporter: David Jencks
create a project that generates 2 artifacts, say
org.apache.activemq:activemq-all:4.1-SNAPSHOT:jar and
org.apache.activemq:activemq-all:4.1-SNAPSHOT:jar:run
Then in a descriptor include something like
dependencySet
outputDirectory/bin/outputDirectory
unpackfalse/unpack
outputFileNameMappingrun.jar/outputFileNameMapping
includes
include${pom.groupId}:activemq-all:jar:run/include
/includes
/dependencySet
The main artifact, not the run-classified one, gets copied.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-2322) it0098 is failing on trunk/branch
[ http://jira.codehaus.org/browse/MNG-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-2322. - Resolution: Fixed Fix Version/s: (was: 2.0.x) 98 has been fixed... MNG-3160 supercedes this as the general task for fixing commented tests it0098 is failing on trunk/branch - Key: MNG-2322 URL: http://jira.codehaus.org/browse/MNG-2322 Project: Maven 2 Issue Type: Bug Components: Bootstrap Build Reporter: Brett Porter Priority: Blocker -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3366) site generation in 2.1 is totally messed up
[ http://jira.codehaus.org/browse/MNG-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3366: -- Fix Version/s: 2.1-alpha-1 site generation in 2.1 is totally messed up --- Key: MNG-3366 URL: http://jira.codehaus.org/browse/MNG-3366 Project: Maven 2 Issue Type: Bug Components: Sites Reporting Affects Versions: 2.1-alpha-1 Reporter: Brian Fox Fix For: 2.1-alpha-1 I tried generating the enforcer site with 2.1 and i get essentially empty pages after lots of warning. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3456) 2.1 fails when networks is unavailable
[ http://jira.codehaus.org/browse/MNG-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3456: -- Fix Version/s: 2.1-alpha-1 2.1 fails when networks is unavailable -- Key: MNG-3456 URL: http://jira.codehaus.org/browse/MNG-3456 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories, Embedding Affects Versions: 2.1 Reporter: Milos Kleint Assignee: John Casey Fix For: 2.1-alpha-1 Attachments: failed-output.txt the 2.1 snapshot from 5/March seems to fail for simple projects where 2.0.x works fine. The failure condition is unplugging the network.. setting offline to true in settings.xml file doesn't have visible effects and it should not matter anyway.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3281) revisit backwards compat of extensions in 2.1 (IT 0114)
[ http://jira.codehaus.org/browse/MNG-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3281: -- Fix Version/s: 2.1-alpha-1 revisit backwards compat of extensions in 2.1 (IT 0114) --- Key: MNG-3281 URL: http://jira.codehaus.org/browse/MNG-3281 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1-alpha-1 Reporter: Brett Porter Fix For: 2.1-alpha-1 currently, it 0114 doesn't pass due to the removal of extension support we need to either: - restore some form of backwards compat by loading the extension into the expected place - provide a graceful failure 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: (MNG-3422) [regression] deploy:deploy-file does not work
[ http://jira.codehaus.org/browse/MNG-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3422: -- Fix Version/s: 2.1-alpha-1 [regression] deploy:deploy-file does not work - Key: MNG-3422 URL: http://jira.codehaus.org/browse/MNG-3422 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1-alpha-1 Reporter: Brett Porter Fix For: 2.1-alpha-1 mvn deploy:deploy-file -Dfile=test.sh -DrepositoryId=testing -DartifactId=artifactId -DgroupId=groupId -Dversion=1.0 -Dpackaging=jar -Durl=http://vesuvius.devzuz.com/private/devzuz/releases [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] Attempting to resolve a version for plugin: org.apache.maven.plugins:maven-deploy-plugin using meta-version: LATEST [INFO] Using version: 2.3 of plugin: org.apache.maven.plugins:maven-deploy-plugin [INFO] Scanning for projects... [INFO] [INFO] Building Maven Default Project [INFO] [INFO] Id: org.apache.maven:super-pom:jar:2.1 [INFO] task-segment: [deploy:deploy-file] (aggregator-style) [INFO] [INFO] [deploy:deploy-file] [INFO] artifact groupId:artifactId: checking for updates from testing --- constituent[0]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/aspectjrt-1.5.3.jar constituent[1]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/backport-util-concurrent-3.0.jar constituent[2]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/commons-cli-1.0.jar constituent[3]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/doxia-sink-api-1.0-alpha-9.jar constituent[4]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jsch-0.1.27.jar constituent[5]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jtidy-4aug2000r7-dev.jar constituent[6]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-artifact-3.0-SNAPSHOT.jar constituent[7]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-core-2.1-SNAPSHOT.jar constituent[8]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-embedder-2.1-SNAPSHOT.jar constituent[9]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-lifecycle-2.1-SNAPSHOT.jar constituent[10]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-model-2.1-SNAPSHOT.jar constituent[11]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-plugin-api-2.1-SNAPSHOT.jar constituent[12]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-profile-2.1-SNAPSHOT.jar constituent[13]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-project-2.1-SNAPSHOT.jar constituent[14]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-reporting-api-2.1-SNAPSHOT.jar constituent[15]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-container-default-1.0-alpha-44.jar constituent[16]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-interactivity-api-1.0-alpha-6.jar constituent[17]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-utils-1.5.1.jar constituent[18]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/retrotranslator-runtime-1.2.1.jar constituent[19]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-file-1.0-beta-2.jar constituent[20]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-lightweight-1.0-beta-2.jar constituent[21]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-shared-1.0-beta-2.jar constituent[22]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-provider-api-1.0-beta-2.jar constituent[23]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-1.0-beta-2.jar constituent[24]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-common-1.0-beta-2.jar constituent[25]: file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-external-1.0-beta-2.jar --- java.lang.NullPointerException at org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOfRemoteRepositoryMetadata(DefaultArtifactRepository.java:123) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:390) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositoryMetadataManager.java:349) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:107) at
[jira] Closed: (MNG-3276) Review existing fix
[ http://jira.codehaus.org/browse/MNG-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3276. - Resolution: Won't Fix can you create a new issue, with clone if necessary? Review existing fix --- Key: MNG-3276 URL: http://jira.codehaus.org/browse/MNG-3276 Project: Maven 2 Issue Type: Sub-task Components: Command Line Reporter: Benjamin Bentmann Priority: Minor I could not re-open the original issue, so let's try it this way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3511) Review fix for MNG-2166
Review fix for MNG-2166
---
Key: MNG-3511
URL: http://jira.codehaus.org/browse/MNG-3511
Project: Maven 2
Issue Type: Improvement
Components: Command Line
Affects Versions: 2.0.8
Reporter: Benjamin Bentmann
Priority: Minor
Attachments: no-goal-help.patch
As requested by Brett in MNG-3276, here a new issue. My relevant comment over
at the other issue:
I still consider the output from Maven quite unhelpful in this case. Please
consider that Maven is just a tool/utility for developers and hence not
everybody out there will spend time to get through the documentation. Some
peoply simply want to use Maven, not understand how it works.
The Ant scripts that I am trying to replace in our organization all provided
some help about the current project and the available targets using the echo
task when the default target was executed. This allowed newbies to quickly
figure out how to perform build steps without ever reading the Ant manual.
Surely, once you know Maven's lifecycle you never need such help targets but
especially old Ant geeks need some easy way of migrating into Maven land.
The attached patch should provide the following console output:
{noformat}
[INFO] Scanning for projects...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO]
You must specify at least one goal or lifecycle phase to perform build steps.
The following list illustrates some commonly used build commands:
mvn clean
Deletes any build output (e.g. class files or JARs).
mvn test
Runs the unit tests for the project.
mvn install
Copies the project artifacts into your local repository.
mvn deploy
Copies the project artifacts into the remote repository.
mvn site
Creates project documentation (e.g. reports or Javadoc).
Please see
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
for a complete description of available lifecycle phases.
Use mvn -? to show general usage information about Maven's command line.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Mon Oct 22 20:48:42 EDT 2007
[INFO] Final Memory: 1M/4M
[INFO]
{noformat}
This output is intended to show further comon use-cases than just install.
Besides, the user is pointed to a concrete URL with helpful information for his
actual need (personally, I consider pointing people at home pages as helpful as
telling to use Google... information should be found, not searched)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MECLIPSE-427) .springBeans definition throws NullPointer if BaseDir does not exist
.springBeans definition throws NullPointer if BaseDir does not exist
Key: MECLIPSE-427
URL: http://jira.codehaus.org/browse/MECLIPSE-427
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: MyEclipse support
Affects Versions: 2.5.1, 2.5
Reporter: Joe Freeman
This is related to the fix submitted for MECLIPSE-359
We have an application with 40 eclipse projects in it. About half of them
have spring beans and 1/2 don't. The top level pom describes how the eclipse
plugin should function and includes the Spring configuration component for the
myeclipse target. A null pointer is thrown when running eclipse:myeclipse when
the base dir doesn't exist, in our case in one of the projects that doesn't
have any spring components. Our pom.xml fragment looks like
spring
version2.0/version
file-pattern*.xml/file-pattern
basedirsrc/main/resources/conf/basedir
/spring
The exception stack trace looks like
java.lang.NullPointerException
at
org.apache.maven.plugin.eclipse.writers.myeclipse.MyEclipseSpringBeansWriter.getConfigurationFilesList(MyEclipseSpringBeansWriter.java:142)
at
org.apache.maven.plugin.eclipse.writers.myeclipse.MyEclipseSpringBeansWriter.write(MyEclipseSpringBeansWriter.java:93)
The following code block with the problem throws NullPointer when
directory.listFiles() returns a null into subdirs. Wrap the for() loop in a
nullcheck
try
{
File directory = new File( basedir );
File[] subdirs = directory.listFiles( new FileFilter()
{
public boolean accept( File pathname )
{
return pathname.isDirectory();
}
} );
for ( int i = 0; i subdirs.length; i++ )
{
configFiles.addAll( getConfigurationFilesList(
subdirs[i].getPath(), pattern ) );
}
configFiles.addAll( FileUtils.getFileNames( directory, pattern,
null, true ) );
}
Testing:
Take one of the test cases and remove the directory that is pointed to by the
basedir attribute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-2005) Hessian Flex 3.1.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130291#action_130291 ] Carlos Sanchez commented on MAVENUPLOAD-2005: - the svn url is wrong, and there are no dependencies ? Hessian Flex 3.1.5 -- Key: MAVENUPLOAD-2005 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2005 Project: maven-upload-requests Issue Type: Task Reporter: evgeny Attachments: hessian-flex-3.1.5-bundle.jar The Hessian binary web service protocol makes web services usable without requiring a large framework, and without learning yet another alphabet soup of protocols. Because it is a binary protocol, it is well-suited to sending binary data without any need to extend the protocol with attachments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2008) Upload oval-1.20
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2008. --- Assignee: Carlos Sanchez Resolution: Fixed Upload oval-1.20 Key: MAVENUPLOAD-2008 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2008 Project: maven-upload-requests Issue Type: Task Reporter: Sebastian T Assignee: Carlos Sanchez OVal is a pragmatic and extensible validation framework for any kind of Java objects (not only JavaBeans). Constraints can be configured with annotations, POJOs or XML. Custom constraints can be expressed in pure Java or by using scripting languages such as JavaScript, Groovy, BeanShell, OGNL, MVEL or Ruby. Besides simple object validation OVal implements Programming by Contract features by utilizing AspectJ based aspects. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html Thanks in advance! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2006) Validator.nu HTML parser 1.0.7 to Maven repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2006. --- Assignee: Carlos Sanchez Resolution: Fixed Validator.nu HTML parser 1.0.7 to Maven repo Key: MAVENUPLOAD-2006 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2006 Project: maven-upload-requests Issue Type: Improvement Reporter: Henri Sivonen Assignee: Carlos Sanchez Attachments: htmlparser-1.0.7-bundle.jar For reference, the previous version was MAVENUPLOAD-1900. Changes * Adds optional support for heuristic encoding sniffing using the ICU4J sniffer, jchardet or both. * Adds support for rewinding and reparsing when becoming confident about the character encoding and the tentative encoding was wrong. * Performs encoding name matching per spec instead of using the JDK mechanism. * Implements spec changes up until just before SVG and MathML support. (Those will merit 1.1 or something.) * Warning: The semantics of the doctype token have changed in case you have your own token handler (unlikely). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1981) maven-license-plugin-1.2.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1981. --- Assignee: Carlos Sanchez Resolution: Fixed maven-license-plugin-1.2.3 -- Key: MAVENUPLOAD-1981 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1981 Project: maven-upload-requests Issue Type: Wish Reporter: Mathieu Carbou Assignee: Carlos Sanchez Attachments: maven-license-plugin-1.2.3-bundle.jar, maven-license-plugin-1.2.4-bundle.jar, maven-license-plugin-1.2.5-bundle.jar Hi, Can you please upload this new (and good) version of maven-license-plugin ? - groupId and packages are fixed to com.google.code.mojo (to conform to maven upload doc.) - I did what Guice did. - Little other fixes - See release notes at http://code.google.com/p/maven-license-plugin/wiki/ReleaseNotes Note: the plugin can be accessed temporary from this maven 2 repository: http://mc-repo.googlecode.com/svn/maven2/releases/ Thanks ! --- Mathieu Carbou [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2010) simple-jndi 0.11.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2010. --- Assignee: Carlos Sanchez Resolution: Fixed simple-jndi 0.11.3 -- Key: MAVENUPLOAD-2010 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2010 Project: maven-upload-requests Issue Type: Wish Reporter: Henri Yandell Assignee: Carlos Sanchez Version 0.11.3 of Simple-JNDI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2011) databene benerator 0.5.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2011. --- Assignee: Carlos Sanchez Resolution: Fixed databene benerator 0.5.1 Key: MAVENUPLOAD-2011 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2011 Project: maven-upload-requests Issue Type: Task Reporter: Volker Bergmann Assignee: Carlos Sanchez -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2009) Please sync net.sourceforge.htmlunit
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2009. --- Assignee: Carlos Sanchez Resolution: Fixed Please sync net.sourceforge.htmlunit Key: MAVENUPLOAD-2009 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2009 Project: maven-upload-requests Issue Type: Wish Reporter: Marc Guillemot Assignee: Carlos Sanchez net.sourceforge.htmlunit,[EMAIL PROTECTED]:/home/groups/h/ht/htmlunit/htdocs/m2-repo,rsync_ssh,Marc Guillemot,[EMAIL PROTECTED],, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-361) eclipse plugin and WTP generating warnings in Europa
[ http://jira.codehaus.org/browse/MECLIPSE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130293#action_130293 ] Kirill Petrov commented on MECLIPSE-361: Was the issue fixed? on my project it generates 40-50 warnings - I don't see the real ones. I am runing eclipse 3.2.2 (enterprise edition) and v.2.5 of the eclipse plugin. eclipse plugin and WTP generating warnings in Europa - Key: MECLIPSE-361 URL: http://jira.codehaus.org/browse/MECLIPSE-361 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: WTP support Affects Versions: 2.5 Environment: Eclipse 3.3.1.1 and WTP 2.0.1 Using Maven 2.0.7 and the last maven-eclipse-plugin 2.5-SNAPSHOT Reporter: Yann Albou Priority: Minor Attachments: wtpTest.zip The issue is regarding warnings in Europa and WTP: Classpath entry M2_REPO/log4j/log4j/1.2.13/log4j-1.2.13.jar will not be exported or published. Runtime ClassNotFoundExceptions may result. 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin version 2.5-SNAPSHOT = I get the same behaviour in EUROPA (WARNINGS) 2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin version 2.4 = I get the same behaviour in EUROPA (WARNINGS) 3) I then try using Eclipse 3.2.2 with WTP 1.5.3 (instead of Eclipse 3.3.1.1 and WTP 2.0.1) with maven-eclipse-plugin version 2.4 or 2.5-SNAPSHOT = Everything is perfect, no more warnings I create a simple test in order to reproduce the issue. This test is a multi module application composed of 1 Ejb module and 1 Ear module. So at the top level Just run mvn install eclipse:eclipse And then in an europa workspace import the projetcs and you should see the warnings on the EJB module. It will behave the same way if it exists other modules. I notice that, in the case you update parameters on the eclipse plugin you will need to remove projects from workspace and import them again. otherwise some old parameter will stay in the eclipse cache... let me know if you need other tests Yann. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (ARCHETYPE-157) Ability to generate empty directories
Ability to generate empty directories - Key: ARCHETYPE-157 URL: http://jira.codehaus.org/browse/ARCHETYPE-157 Project: Maven Archetype Issue Type: Improvement Components: Archetypes Environment: All Operating systems Reporter: nambi sankaran In my archetype, I would like to generate an empty directory that macthes with the package the user supplied The current version does not create the directory, if it is empty. As a workaround, I have added an empty file named .file to generate a directory with the package name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (ARCHETYPE-158) Create a directory with name artiactId
Create a directory with name artiactId -- Key: ARCHETYPE-158 URL: http://jira.codehaus.org/browse/ARCHETYPE-158 Project: Maven Archetype Issue Type: Improvement Components: Archetypes Environment: All operating systems Reporter: nambi sankaran I need to generate a list of directories with name artifactId under /src/main/resources/. artifactId is the name of the project the user supplies, during archetypeng:create After generation the directory structure should look like this, /src/main/resources/ -- contract- artifactId - file.4cc -- sources - en - artifactId - file.4cb -- sources - fr - artifactId - file.4cb -- sources - de - artifactId - file.4cb This feature would extremely valuable. thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2004) Hessian 3.1.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2004. --- Assignee: Carlos Sanchez Resolution: Fixed Hessian 3.1.5 - Key: MAVENUPLOAD-2004 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2004 Project: maven-upload-requests Issue Type: Task Reporter: evgeny Assignee: Carlos Sanchez Attachments: hessian-3.1.5-bundle.jar, hessian-3.1.5-bundle.jar The Hessian binary web service protocol makes web services usable without requiring a large framework, and without learning yet another alphabet soup of protocols. Because it is a binary protocol, it is well-suited to sending binary data without any need to extend the protocol with attachments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3512) Upgrade to newer wagon-provider-api
Upgrade to newer wagon-provider-api --- Key: MNG-3512 URL: http://jira.codehaus.org/browse/MNG-3512 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.8, 2.0.7, 2.0.6, 2.0.5 Reporter: Brian Fox Fix For: 2.0.10 Upgrade to the new wagon-provider-api to fix WAGON-80. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3512) Upgrade to newer wagon-provider-api
[ http://jira.codehaus.org/browse/MNG-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-3512: --- Fix Version/s: 2.0.10 Upgrade to newer wagon-provider-api --- Key: MNG-3512 URL: http://jira.codehaus.org/browse/MNG-3512 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.5, 2.0.6, 2.0.7, 2.0.8 Reporter: Brian Fox Fix For: 2.0.10 Upgrade to the new wagon-provider-api to fix WAGON-80. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2012) TestNG 5.8
TestNG 5.8 -- Key: MAVENUPLOAD-2012 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2012 Project: maven-upload-requests Issue Type: Task Reporter: Dan Fabulich Attachments: testng-5.8-bundle.jar TestNG 5.8. I'm not a developer, but I'll happily lend a hand. Created using TestNG's new dist-maven-bundle ant task, but against the 5.8 tag which doesn't include this source. That makes this bundle a one-off, so there may be errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-306) Dependency resolution fails with an NPE for a provided dependency with a fixed version
Dependency resolution fails with an NPE for a provided dependency with a fixed version -- Key: MASSEMBLY-306 URL: http://jira.codehaus.org/browse/MASSEMBLY-306 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-2 Environment: Maven 2.0.8, Java 1.6.0_03-b05 Reporter: Thomas Dudziak Priority: Critical A POM like this: ?xml version=1.0 encoding=UTF-8?project modelVersion4.0.0/modelVersion groupIdmaven-test/groupId artifactIdmaven-test/artifactId namemaven-test/name version1.0-SNAPSHOT/version urlhttp://maven.apache.org/url dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version[1.2.13]/version scopeprovided/scope /dependency /dependencies build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.2-beta-2/version configuration descriptorRefs descriptorRefjar-with-dependencies/descriptorRef /descriptorRefs archive manifest mainClassning.dashboard.DashboardServer/mainClass /manifest /archive /configuration executions execution idmake-assembly/id phasepackage/phase goals goalattached/goal /goals /execution /executions /plugin /plugins /build /project fails with this error: [INFO] Processing DependencySet (output=) [INFO] [ERROR] FATAL ERROR [INFO] [INFO] version was null for log4j:log4j [INFO] [INFO] Trace java.lang.NullPointerException: version was null for log4j:log4j at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) at org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) at org.apache.maven.shared.artifact.filter.ScopeArtifactFilter.include(ScopeArtifactFilter.java:142) at org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:345) at org.apache.maven.plugin.assembly.artifact.DefaultDependencyResolver.resolveDependencies(DefaultDependencyResolver.java:123) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.resolveDependencyArtifacts(AddDependencySetsTask.java:205) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addDependencySet(AddDependencySetsTask.java:132) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.execute(AddDependencySetsTask.java:116) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPhase.execute(DependencySetAssemblyPhase.java:74) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:129) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) 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 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
[jira] Commented: (SCM-349) The includes and excludes parameters appear not to work with a StarTeam scm:checkout
[ http://jira.codehaus.org/browse/SCM-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130318#action_130318 ] Brad Harper commented on SCM-349: - I'm seeing this same behavior apparently for the svn provider. The includes and excludes parameters appear not to work with a StarTeam scm:checkout Key: SCM-349 URL: http://jira.codehaus.org/browse/SCM-349 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-starteam Affects Versions: 1.0 Environment: Windows XP Pro SP2 Reporter: Ken Turner I used this snippet of code: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0/version configuration includesbuild.xml/includes scmVersion0.1.0.54/scmVersion scmVersionTypetag/scmVersionType /configuration /plugin No matter what values I used in the includes (or excludes) parameters, everything was checked out; the version info appeared to be correctly converted into a parameter for the generated STCMD command, but the include/exclude info was not. No error was reported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3510) download with http 403 status code assumed by maven to be OK, then checksum failed error
[
http://jira.codehaus.org/browse/MNG-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130319#action_130319
]
Bruce Chapman commented on MNG-3510:
Milos,
I had configured mevenide to force use the version of 1.0.6 I had downloaded. I
am new to maven and still at the stumbling around stage. I'll attempt to get a
2.1 snapshot for maven and try that at the command line. I was having problems
both in netbeans and command line. I just happened to be be in netbeans when I
realised why it wasn't working. It seems much more likely to be a maven rather
than meveide prob so I'll do further diagnosis on command line. I'll need to
work quick before support guys fix the problem in the firewall.
download with http 403 status code assumed by maven to be OK, then checksum
failed error
Key: MNG-3510
URL: http://jira.codehaus.org/browse/MNG-3510
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.6
Environment: Win xp pro., JDK6, mvn 2.0.6, netbeans 6, mevenide
plugin in netbeans.
Reporter: Bruce Chapman
Priority: Minor
Our firewall/cache is blocking access to
http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.jar becuase it
thinks it has a virus (that's the not the problem)
{{$ wget http://repo1.maven.org/maven2/javax/mail/mail
--14:13:46-- http://repo1.maven.org/maven2/javax/mail/mail
= `mail'
Resolving cache... done.
Connecting to cache[172.30.41.11]:8080... connected.
Proxy request sent, awaiting response... 403 Forbidden
14:13:47 ERROR 403: Forbidden.}}
but the firewall also returns content for the browser
{{
htmlheadMETA HTTP-EQUIV=Expires CONTENT=-1META HTTP-EQUIV=Pragma
CONTENT=no-cacheMETA HTTP-EQUIV=Cache-Control CONTENT=no-cachemeta
http-equiv=Content-Type content=text/html; charset=UTF-8titleSonicWALL
- Blocked by Application Firewall/title/headbody bgcolor=#011B4A
text=#FFbrbrbrbrbrtable align=center cellpadding=5 border=2
width=500 bgcolor=#9CBACEtrtd align=centertable align=center
cellpadding=5 width=450trtd align=centerbrbrfont face=arial
color=00 size=4bThis request is blocked by the SonicWALL Gateway
Anti-Virus Service. Name: WMF.Gen-2
(Exploit)/b/font/td/tr/table/td/tr/table/body/html
}}
The problem is that maven is ignoring the status code, goes ahead and
downloads the file then decides that the checksum for the content does not
match what is expected. This is misleading and makes it more difficult to
diagnose the cause of the failed download.
Here is what maven does
{{
Building Hudson core
task-segment: [install]
Maven Version: 2.0.6
JDK Version: 1.6.0_05 normalized as: 1.6.0-5
OS Info: Arch: x86 Family: windows Name: windows xp Version: 5.1
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.pom
993/993b
993b downloaded
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.jar
696/?
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'e0bb0f663e436cde3a6e1e5b8e8e80be43bde8a3'; remote =
'1aa1579ae5ecd41920c4f355b0a9ef40b68315dd' - RETRYING
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.jar
696/?
}}
Maven should only go on and download the file and compare checksums if the
http status is valid eg 200, in the case of a failing http status code, it
would be much more useful if maven failed earlier with the status code and
text as the error message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-3510) download with http 403 status code assumed by maven to be OK, then checksum failed error
[
http://jira.codehaus.org/browse/MNG-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130320#action_130320
]
Bruce Chapman commented on MNG-3510:
OK,
I presume I can't download a build of maven 2.1 snapshot, so I have checked out
the source and built it. (svn revision 646544)
I have then deleted the corrupt mail-1.4.jar from the local maven repository
(it contains the html error screen).
I have then rerun the hundson builod, and it fails by the same mechanism.
heres the relevant section of the output
[INFO]
[INFO] Building Hudson core
[INFO]
[INFO] Id: org.jvnet.hudson.main:hudson-core:stapler-jar:1.204
[INFO] task-segment: [install]
[INFO]
[INFO] Attempting to resolve a version for plugin:
org.apache.maven.plugins:maven-enforcer-plugin us
ing meta-version: LATEST
[INFO] Using version: 1.0-alpha-3 of plugin:
org.apache.maven.plugins:maven-enforcer-plugin
[INFO] Attempting to resolve a version for plugin:
org.kohsuke.stapler:maven-stapler-plugin using me
ta-version: LATEST
[INFO] Using version: 1.6 of plugin: org.kohsuke.stapler:maven-stapler-plugin
[INFO] [enforcer:display-info]
[INFO] Maven Version: 2.1-SNAPSHOT
[INFO] JDK Version: 1.6.0_05 normalized as: 1.6.0-5
[INFO] OS Info: Arch: x86 Family: windows Name: windows xp Version: 5.1
[INFO] [localizer:generate]
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.pom
993b downloaded
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.jar
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'e0bb0f663e436cde3a6e1e5b8e8e80
be43bde8a3'; remote = '1aa1579ae5ecd41920c4f355b0a9ef40b68315dd' - RETRYING
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.jar
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'e0bb0f663e436cde3a6e1e5b8e8e80
be43bde8a3'; remote = '1aa1579ae5ecd41920c4f355b0a9ef40b68315dd' - IGNORING
Note that there is now a corrupt jar file (actually an html page) in my local
maven repository again. If the dowload had a status of 200 OK and the
checksum failed, maybe thats a good thing, but with a status 403 Forbidden
the jar should not exist in the local repository, and the error message
shouldn't be about checksum failures, but should be about the 403 forbidden
status code.
download with http 403 status code assumed by maven to be OK, then checksum
failed error
Key: MNG-3510
URL: http://jira.codehaus.org/browse/MNG-3510
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.6
Environment: Win xp pro., JDK6, mvn 2.0.6, netbeans 6, mevenide
plugin in netbeans.
Reporter: Bruce Chapman
Priority: Minor
Our firewall/cache is blocking access to
http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.jar becuase it
thinks it has a virus (that's the not the problem)
{{$ wget http://repo1.maven.org/maven2/javax/mail/mail
--14:13:46-- http://repo1.maven.org/maven2/javax/mail/mail
= `mail'
Resolving cache... done.
Connecting to cache[172.30.41.11]:8080... connected.
Proxy request sent, awaiting response... 403 Forbidden
14:13:47 ERROR 403: Forbidden.}}
but the firewall also returns content for the browser
{{
htmlheadMETA HTTP-EQUIV=Expires CONTENT=-1META HTTP-EQUIV=Pragma
CONTENT=no-cacheMETA HTTP-EQUIV=Cache-Control CONTENT=no-cachemeta
http-equiv=Content-Type content=text/html; charset=UTF-8titleSonicWALL
- Blocked by Application Firewall/title/headbody bgcolor=#011B4A
text=#FFbrbrbrbrbrtable align=center cellpadding=5 border=2
width=500 bgcolor=#9CBACEtrtd align=centertable align=center
cellpadding=5 width=450trtd align=centerbrbrfont face=arial
color=00 size=4bThis request is blocked by the SonicWALL Gateway
Anti-Virus Service. Name: WMF.Gen-2
(Exploit)/b/font/td/tr/table/td/tr/table/body/html
}}
The problem is that maven is ignoring the status code, goes ahead and
downloads the file then decides that the checksum for the content does not
match what is expected. This is misleading and makes it more difficult to
diagnose the cause of the failed download.
Here is what maven does
{{
Building Hudson core
task-segment: [install]
Maven Version: 2.0.6
JDK Version: 1.6.0_05 normalized as: 1.6.0-5
OS Info: Arch: x86 Family: windows Name: windows xp Version: 5.1
Downloading: http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.pom
993/993b
993b downloaded
Downloading:
