Re: Check scm/ urls?
I'm not aware of one, but I'd love to have one if it were available - it's somewhere on my to do list to see if I can do it, but I don't see doing it any time soon. On Thu, Apr 29, 2010 at 9:08 AM, Benson Margulies bimargul...@gmail.comwrote: Is there any plugin which will check the consistency of the scm URLs, at least for svn, with the actual status of the tree?
Re: Always download dependencies with classifier
We see that message when we have a jar in the repository that doesn't actually have a POM file. It realizes the JAR is in your local repository, so it doesn't try to download that. But it always tries to download the POM to find out if the artifact has any dependencies (and POMs don't have classifiers) but it's trying to find out if it has any dependencies. It does that on every build. However, my output always shows an INFO message Unable to find resource 'groupX:artifactY:pom:versionZ' for each one as well. Might be interesting if Maven provided a way to indicate in your dependency declaration that you just want the JAR w/o looking at the POM. On Thu, Mar 4, 2010 at 4:52 AM, Thunder Farmer thunder.far...@gmail.comwrote: Thanks for all of your responses. I tried with version 2.2.1. Still the same issue. Is it my luck? find a bug for Maven,:)~ D:\temp\my-appmvn -version Apache Maven 2.2.1 (r801777; 2009-08-07 03:16:01+0800) Java version: 1.6.0_10-rc Thanks, Thunder On Thu, Mar 4, 2010 at 3:22 PM, Anders Hammar and...@hammar.net wrote: Did you try any of the latest recommended versions of Maven, like 2.2.1? Maven 2.1.0 is generally a version to stay away from as it has issues... /Anders On Thu, Mar 4, 2010 at 07:03, Thunder Farmer thunder.far...@gmail.com wrote: Hi, Thanks for your quick response. Here I provide more information. I can reproduce the issue by creating a simple project and adding a dependency with classifier to it. I create the project by mvn archetype:create command. In the pom, I add a dependency: dependency groupIdcom.informix/groupId artifactIdifxjdbc/artifactId version3.50/version classifierJC3/classifier scopecompile/scope /dependency The informix JDBC jar and it's pom file are already in our local repo, and I have local repo in my setting.xml Every time when I run mvn compile, I get below output in the console [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repo1.maven.org/maven2/com/informix/ifxjdbc/3.50/ifxjdbc-3.50.pom [INFO] [compiler:compile] Seems it always tries to download the artifact. Though it doesn't really download the jar file, it consume significant time to connect remote repo for a large project. Is it expected behavior of Maven? The project is attached. Thanks, Thunder On Thu, Mar 4, 2010 at 10:51 AM, Wendy Smoak wsm...@gmail.com wrote: On Wed, Mar 3, 2010 at 9:44 PM, Thunder Farmer thunder.far...@gmail.com wrote: My problems is that seems Maven always download dependencies with classifier even I specify the version. Is it the expected behavior or some thing goes wrong? Maven version: 2.1.0-M1 Java version: 1.5.0_06 This is the right place, but we need more information. Can you post a snippet of the build output or error message that you're seeing, and maybe the relevant portion of your pom.xml file (the problematic dependency)? You might also try the build with the latest recommended stable Maven version from http://maven.apache.org/download.html and see if it's still a problem. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Listen to Your Heart Follow Your Heart - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Listen to Your Heart Follow Your Heart
Re: 401 error with Maven Release Plugin
This is Maven 2.2.1 with release plugin 2.0-beta-8. On Fri, Dec 11, 2009 at 2:26 AM, Anders Hammar and...@hammar.net wrote: You've tried different version of Maven? 2.2.1? 3.0-alpha-5? /Anders On Thu, Dec 10, 2009 at 21:49, Brendan Sibre bren...@sibre.net wrote: A previous poster wrote: Thanks for your response, this fixed the problem! However, another issue comes up - *release*:*perform* almost worked out except at the very end it failed to upload the artifact to the repo, and the error is [INFO] [INFO] Error deploying artifact: Failed to transfer file: .. Return code is: *401* I believe this is a permission related issue. But I've got the correct server username/password pairs in settings.xml and running the deploy goal in the lifecycle has no problem having the artifact deployed, it's just the *release*:*perform* that gets stuck with the permission problem. Anyone knows why this happens please? This is with an https url and, like the previous poster, I can do a maven deploy without any issues. Anyone have any ideas?
401 error with Maven Release Plugin
A previous poster wrote: Thanks for your response, this fixed the problem! However, another issue comes up - *release*:*perform* almost worked out except at the very end it failed to upload the artifact to the repo, and the error is [INFO] [INFO] Error deploying artifact: Failed to transfer file: .. Return code is: *401* I believe this is a permission related issue. But I've got the correct server username/password pairs in settings.xml and running the deploy goal in the lifecycle has no problem having the artifact deployed, it's just the *release*:*perform* that gets stuck with the permission problem. Anyone knows why this happens please? This is with an https url and, like the previous poster, I can do a maven deploy without any issues. Anyone have any ideas?
Re: 401 error with Maven Release Plugin
Actually, using Artifactory 2.1.0. And it is configured to mirror everything. So far I'm guessing that it's one of two problems: 1) I don't have things mapped properly between my ~/.m2/settings.xml and $MAVEN_HOME/conf/settings.xml where the shared configuration defines the distributionManagement and my settings defines server credentials. 2) I have some very vague recollection of there being a problem with Maven passing the MAVEN_HOME value to the forked maven when MAVEN_HOME points to a symlink. Although I've tried changing MAVEN_HOME to the actual directory as well as passing in the -DmavenHome parameter. On Thu, Dec 10, 2009 at 5:20 PM, Matt Milliss matt.mill...@gmail.comwrote: are you using Archiva as your repo? On 11/12/2009 7:49 AM, Brendan Sibre wrote: A previous poster wrote: Thanks for your response, this fixed the problem! However, another issue comes up - *release*:*perform* almost worked out except at the very end it failed to upload the artifactto the repo, and the error is [INFO] [INFO] Error deploying artifact: Failed to transfer file: .. Return code is: *401* I believe this is a permission related issue. But I've got the correct server username/password pairs in settings.xml and running the deploy goal in the lifecycle has no problemhaving the artifact deployed, it's just the *release*:*perform* that gets stuck with the permission problem. Anyone knows why this happens please? This is with an https url and, like the previous poster, I can do a maven deploy without any issues. Anyone have any ideas?
Re: Problem with Maven deploy (Error writing to server)
If you're running Apache 2.2, take a look at
http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslrenegbuffersize
Essentially, it might not really be the size, it might be the size in
combination with
opening a new connection. If there is already an active SSL connection it
won't need
to be renegotiated during the post of the file. If it needs to create a new
connection
then it might fail for larger files.
Tomcat has a similar setting, maxPostSize you can set on the connector so
you might need to
set both.
This has bitten me with other similar things and it's really frustrating.
I'm not quite sure why the
client can't wait for the renegotiation to complete before sending the file.
On Thu, Dec 10, 2009 at 8:17 PM, K J gomm...@gmail.com wrote:
I have a very strange problem when I try to deploy artifacts. For
certain artifacts, the deployment fails with the message 'Error
deploying artifact: Error transferring file...Error writing to server'
(I included the stacktrace below). It appears to be related to the
size of the artifact, but here's the kicker -- the size restriction
isn't consistent acrosss artifact types. I can deploy an 11M WAR, but
can't deploy a 30M WAR. I can deploy a 96K JAR, but can't deploy a
128K JAR. (Sorry for the broad size range, I haven't had enough time
to narrow it down further).
I don't know if it's related, but I also noticed an oddity when I was
trying to narrow down the 'breaking point' for the size. I set up a
test project which deploys a jar and added images as resources to
build up the size. After passing the size threshold (which caused the
deploy to fail), I would remove the newest image and try to rebuild,
but now the deploy would fail with a 'connection reset' or 'connection
reset by peer: socket write error' message. Without making any
changes, I rerun 'mvn clean deploy' or 'mvn deploy. Most of the time
everything deploys fine; although sometimes it takes two tries before
it succeeds. For clarity, I outlined those steps below:
1.) Add image. Build and deploy fine. Size 96K.
2.) Add another image. Build fine, deploy breaks: Error writing to
server. Size 128K.
3.) Remove last image. Build fine, deploy breaks: Connection reset. Size
96K.
4.) No changes. Build and deploy fine. Size 96K.
Some additional information:
* I experience this problem using both Maven 2.0.9 and 2.2.1.
* Our repository is managed by Nexus (deployed to Tomcat with SSL from
apache). Nexus might be part of the problem, but I've checked some of
the logs, but I can't find any indication of errors on that side of
things.
* Our network uses a socks proxy (v5).
Lastly, here is the stack trace (and a bit of the Maven output):
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' --
[DEBUG] (f) artifact = com.cdmtech.icodes.ciw:test:jar:0.0.1-SNAPSHOT
[DEBUG] (f) attachedArtifacts = []
[DEBUG] (f) deploymentRepository =
Repository[snapshots|
https://hudson149/nexus/content/repositories/snapshots]
[DEBUG] (s) localRepository = Repository[local|file://C:\Documents
and Settings\kj\.m2\repository]
[DEBUG] (f) packaging = jar
[DEBUG] (f) pomFile =
C:\eclipse\eclipse-workspaces\eclipse-jee-ganymede-3.4.2\m2eclipse\ciw\test\pom.xml
[DEBUG] (f) skip = false
[DEBUG] (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from snapshots
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] Connecting to repository: 'snapshots' with url:
'https://hudson149/nexus/content/repositories/snapshots'.
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] not adding permissions to wagon connection
Uploading:
https://hudson149/nexus/content/repositories/snapshots/ciw/test/0.0.1-SNAPSHOT/test-0.0.1-20091210.183044-14.jar
4/128Khttps://hudson149/nexus/content/repositories/snapshots/ciw/test/0.0.1-SNAPSHOT/test-0.0.1-20091210.183044-14.jar%0A4/128K
...
128/128K
[DEBUG] Error writing to server
java.io.IOException: Error writing to server
at
sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:438)
at
sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:450)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1002)
at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
at
