Re: java.lang.OutOfMemoryError: Java heap space in Wagon
M2Eclipse doesn't launch the external Maven with mvn.bat. You can set the heap options in the "JRE" tab of the Maven launch configuration. Rich On May 19, 2010, at 10:14 AM, Ron Wheeler wrote: > I am trying to build a shared library containing the CXF package and the > upload is running out of heap space. > > The jar is built and is 25Mb. > > I have added this to every mvn.bat in sight. > set MAVEN_OPTS=-Xmx1024M > > This is running under the latest STS version of Eclipse which is started by > this shortcut. > "C:\Program Files\SpringSource\sts-2.3.2.RELEASE\STS.exe" -vmargs > -XX:PermSize=256M -XX:MaxPermSize=1024M > > The Eclipse preference for Maven points to my 2.2.1 version of maven > > If I try the same pom on another PC with STS using its embedded Maven it also > fails with a slightly different stack. It fails on the read side. > BufferedInputStream.fill runs out of Java Heap Space. > > What do I have to do get this file uploaded by wagon? > > > > Uploading: > http://xxx.artifact-software.com/nexus/content/repositories/releases/com/artifact_software/lms/lms-pom-cxf/1.8.2/lms-pom-cxf-1.8.2-jar-with-dependencies.jar > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] Java heap space > [INFO] > > [INFO] Trace > java.lang.OutOfMemoryError: Java heap space >at java.util.Arrays.copyOf(Arrays.java:2786) >at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) >at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61) >at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:492) >at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:457) >at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:411) >at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392) >at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365) >at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163) >at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317) >at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227) >at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107) >at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:190) >at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) >at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) >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 org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Error reading archetype catalog http://repo1.maven.org/maven2
This is relevant if you are (will be fixed in 2.0.5-alpha6):
http://jira.codehaus.org/browse/ARCHETYPE-202
Rich
On Jun 9, 2010, at 1:59 AM, Anders Hammar wrote:
> Are you behind a corp web proxy and haven't configured Maven for this?
>
> /Anders
>
> On Wed, Jun 9, 2010 at 01:02, Shyamsunder R Mutcha wrote:
>
>> When I try to execute the following command
>>
>> mvn -e archetype:generate -B -DarchetypeGroupId=org.appfuse.arch
>> etypes -DarchetypeArtifactId=appfuse-basic-spring-archetype
>> -DarchetypeVersion=2
>> .1.0-M1 -DgroupId=com.mycompany -DartifactId=myproject
>>
>> I receive error message "[WARNING] Error reading archetype catalog
>> http://repo1.maven.org/maven2
>> org.apache.maven.wagon.authorization.AuthorizationException: Access denied
>> to: h
>> ttp://repo1.maven.org/maven2"
>>
>> http://repo1.maven.org/maven2is redirected to
>> http://repo2.maven.org/maven2/ in the browser.
>>
>> Is there a way to configure Maven 2.2.1 to contact repo2 instead of repo1.
>>
>> Here is the full trace...
>>
>> C:\Shyam\Source>mvn -e archetype:generate -B
>> -DarchetypeGroupId=org.appfuse.arch
>> etypes -DarchetypeArtifactId=appfuse-basic-spring-archetype
>> -DarchetypeVersion=2
>> .1.0-M1 -DgroupId=com.mycompany -DartifactId=myproject
>> + Error stacktraces are turned on.
>> [INFO] Scanning for projects...
>> [INFO] Searching repository for plugin with prefix: 'archetype'.
>> [INFO]
>>
>> [INFO] Building Maven Default Project
>> [INFO]task-segment: [archetype:generate] (aggregator-style)
>> [INFO]
>>
>> [INFO] Preparing archetype:generate
>> [INFO] No goals needed for project - skipping
>> [INFO] [archetype:generate {execution: default-cli}]
>> [INFO] Generating project in Batch mode
>> [WARNING] Error reading archetype catalog http://repo1.maven.org/maven2
>> org.apache.maven.wagon.authorization.AuthorizationException: Access denied
>> to: h
>> ttp://repo1.maven.org/maven2
>> at
>> org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputD
>> ata(LightweightHttpWagon.java:119)
>> at
>> org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:11
>> 6)
>> at
>> org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
>> at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
>> at
>> org.apache.maven.archetype.source.RemoteCatalogArchetypeDataSource.ge
>> tArchetypeCatalog(RemoteCatalogArchetypeDataSource.java:97)
>> at
>> org.apache.maven.archetype.DefaultArchetypeManager.getRemoteCatalog(D
>> efaultArchetypeManager.java:195)
>> at
>> org.apache.maven.archetype.DefaultArchetypeManager.getRemoteCatalog(D
>> efaultArchetypeManager.java:184)
>> at
>> org.apache.maven.archetype.ui.DefaultArchetypeSelector.getArchetypesB
>> yCatalog(DefaultArchetypeSelector.java:278)
>> at
>> org.apache.maven.archetype.ui.DefaultArchetypeSelector.selectArchetyp
>> e(DefaultArchetypeSelector.java:69)
>> at
>> org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execu
>> te(CreateProjectFromArchetypeMojo.java:186)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> nManager.java:490)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> ultLifecycleExecutor.java:694)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
>> Goal(DefaultLifecycleExecutor.java:569)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> ltLifecycleExecutor.java:539)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> dleFailures(DefaultLifecycleExecutor.java:387)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> ts(DefaultLifecycleExecutor.java:284)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> fecycleExecutor.java:180)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> at
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
>> 0)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> sorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>
>> at org.codehaus.classworlds.Launcher.main(Launch
Re: Checksum Failed using deploy-file
This is a known issue with Maven 2.2.0. Upgrading to 2.2.1 will fix this. Rich On Jul 7, 2010, at 12:21 PM, Victor Calvello wrote: > Hi guys, > > I'm using maven-deploy-plugin:deploy-file to upload an artifact to my Nexus > repository. > The upload process works fine but the metadata is not regenerated. > > So when I download the artifact I get a Checksum Failed error. > Regenerating metadata via Nexus fix the problem. (of course I don't want to > do this every time :) > > Any ideas?? > > btw, I'm using maven 2.2.0 and the last deploy-plugin release. > > Thanks, > Vic - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Our IP Was blocked
File an issue at https://issues.sonatype.org under the "Community Support - Maven Central" to get removed from the blacklist. Rich On Jan 5, 2011, at 8:05 AM, Ron Wheeler wrote: > If you have Nexus installed, you can find any dependency available in any > repository that you configure either by looking at the full list or by > searching for it . > That is the right way to manage dependencies. > It is a really big help in making your management of dependencies much less > painful and provides a sound foundation for managing your own artifacts. > > > Nexus will not get you banned. > > I gather that you will get banned again if you run your program. > > Ron > > On 05/01/2011 5:34 AM, Faruk Can Kaya wrote: >> >> Hello; >> >> I was working on a project for our custom needs about dependency management. >> I have written a program that traverses the repo1.maven.org and list all the >> available artifacts. Unfortunately I'm not able access repo1.maven.org any >> more. Our company uses maven in many projects for build scripting. Hence it >> is essential for our company. I'm sorry for causing any problems. Can anyone >> restore our ip address or addresses. >> >> Our IP addresses are below: >> >> 95.9.74.92 >> 88.249.20.72 >> 78.187.132.76 >> >> Thank You >> Best Regards. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Settings properties not resolved when used in repository element.
If I recall correctly, property definitions within a settings.xml profile can't
be interpolated outside the profile within the settings.xml. And the
rationale for this was that profile elements are a subset of pom files, not
settings.xml files.
See here for the comment accompanying the original implementation, which says
that this was explicitly disallowed:
http://jira.codehaus.org/browse/MNG-2577?focusedCommentId=100862&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-100862
Rich
On Feb 14, 2013, at 5:14 PM, Tonio Caputo wrote:
> Hi Wayne,
>
> Thanks for your answer,
>
> I'll try the _ version tomorrow, and let you know how it worked.
>
>
> Regarding your question
>
>>
>>company.repo
>>Archiva Managed Internal Repository
>>${company.maven.repo}
>>
>
>>> What's the reason that you can't simply specify the url here, and
>>> instead are using this property approach?
>
> You are right, it doesn't make sense in this single sample I've sent, but if
> you read my previous email the idea was to define this property
> *company.maven.repo *in the *settings.xml*.
>
> This way you can customize the repo URL for example if you are working
> in the office (local NETWORK) or at home (with a public URL), or easy
> to change if URL changes, or whatever. :-)
>
> Using properties, instead of definining the full repository entry
> helps in a couple of ways:
>
> - if you need to define the same repository in different profiles
> (to make sure the order in which repositories are searched)
>
> - Some times repository and distributionManagement (which you cannot define
> in the settings profile) uses the same URL.
>
> But of course may be I'm not following a good approach
>
> Thanks again
> tonio
>
>
>
>
>
>
> On Thu, Feb 14, 2013 at 6:23 PM, Wayne Fay wrote:
>
>>>
>>>http://maven:8080/repo/
>>>
>>
>> Try company_maven_repo instead. I know at one point, there was an
>> issue with dotted properties, but that was a while back.
>>
>>>
>>>company.repo
>>>Archiva Managed Internal Repository
>>>${company.maven.repo}
>>>
>>
>> What's the reason that you can't simply specify the url here, and
>> instead are using this property approach?
>>
>> Wayne
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: No SCM support for m2eclipse?
Click on "open catalog" under window/preferences/maven/discovery in Eclipse. BTW, there is a mailing list at Eclipse which is more appropriate place to ask questions about M2E. Look under http://eclipse.org/m2e/support. Regards, Rich On Aug 15, 2011, at 1:13 PM, motes motes wrote: > m2eclipse 1.0.0 has been moved to: > > http://eclipse.org/m2e/ > > but where is the m2eclipse extras (eg. scm support using subclipse) > for version 1.0.0? > > Installing core+extras version 0.12 from : > > http://m2eclipse.sonatype.org/installing-m2eclipse.html > > works but are there any plans on adding scm support for m2eclipse 1.0.0? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [nexus-user] Checksum issue with webdav deploy
This is actually a maven wagon issue:
http://jira.codehaus.org/browse/MNG-4301
Try using the extension specified in that issue, it seems to solve it for me:
org.apache.maven.wagon
wagon-webdav
1.0-beta-2
Rich
On Dec 7, 2011, at 3:59 AM, Julien HENRY wrote:
> Hi,
>
> I was bitten by bug OutOfMemory when deploying big files
> (http://jira.codehaus.org/browse/WAGON-272) so I decided to switch to dav
> protocol. In my pom I have added "dav:" in front of URL in
> distributionManagement section, and also added webdav wagon this way:
>
>
>
> org.apache.maven.plugins
> maven-deploy-plugin
> 2.7
>
>
>org.apache.maven.wagon
>wagon-webdav-jackrabbit
>2.1
>
>
>
> ...
>
>
> Then I tried to deploy on our Nexus repo using Maven 2.2.1, and the result
> was corrupted md5 checksum for all files (pom, metadata.xml, ...). My feeling
> was that it was not the correct wagon that was used (I suppose the one
> included in Maven 2.2.1 takes priority over the one declared as dependency of
> m-deploy-p). So I tried to switch to an extension:
>
>
> org.apache.maven.wagon
> wagon-webdav-jackrabbit
> 2.1
>
>
>
> But then my build failed with the following error:
> [INFO] [deploy:deploy {execution: default-deploy}]
> [INFO] Retrieving previous build number from macif-snapshots-repo
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> ...
> [ERROR] BUILD ERROR
> ...
> Caused by: java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
> at org.slf4j.LoggerFactory.getSingleton(LoggerFactory.java:230)
> at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:112)
> at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:275)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:248)
> at
> org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155)
> at
> org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:131)
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:685)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.(MultiThreadedHttpConnectionManager.java:70)
> at
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.(AbstractHttpClientWagon.java:181)
> at
> org.apache.maven.wagon.providers.webdav.WebDavWagon.(WebDavWagon.java:64)
> ...
>
>
> Any suggestion?
>
> My need is to be able to deploy big files with Maven 2.2.1 and/or Maven
> 3.0.3. I can do any modification in our corporate pom but I don't want to
> rely on anything in settings.xml as I can't be sure users will do the
> modification and I don't want to corrupt my repository.
>
> Thanks
>
> Julien
