You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mykel Alvis <my...@weirdness.com> on 2007/08/07 16:29:56 UTC
maven-ant-tasks-2.0.7 settings file read hangs at install-provider
Hi all,
I'm trying to make an example ant project for one of our teams who currently
uses ant to do their builds.
Relevant sections of build.xml
--------------------------------------------
<target name="init">
<tstamp>
<format property="build.date" pattern="yyyy-MM-dd@hhmmss" />
</tstamp>
<mkdir dir="${target.dir}" />
<mkdir dir="${ target.classes}" />
<mkdir dir="${target.gensrc}" />
<mkdir dir="${target.dist}" />
<mkdir dir="${lib}" />
</target>
<target name="maven-setup" depends="init" description="Setup maven ant
tasks, required for dependency resolution">
<get src="${maven.ant.task.url}" dest="${lib}/${ maven.ant.task.jar}"
usetimestamp="true" />
<path id="maven-ant-tasks.classpath" path="lib/${maven.ant.task.jar}"
/>
<typedef resource="org/apache/maven/artifact/ant/antlib.xml"
uri="urn:maven-artifact-ant" classpathref=" maven-ant-tasks.classpath" />
<artifact:remoteRepository id="remote.public" url="${url.public}" />
<echo message="Installing Provider"/>
<artifact:install-provider artifactId="wagon-webdav" version="
1.0-beta-2" />
<echo message="Provider Installed"/>
</target>
build.properties
-------------------------
custom = true
# Jarfile name of the maven ant tasks. Occasionally updates
maven.ant.task.jar=maven-ant-tasks-2.0.7.jar
# Local file location of maven ant tasks jar
maven.ant.task.url=http://sirdsite/installs/maven-ant-tasks/${maven.ant.task.jar}
# repo username for scp
repository.username=localbuild
# localtion of local private key
repository.privatekey=${user.home}/.ssh/id_dsa
url.public=http://sirdsite/proximity/repository/public
url.codehaus=http://sirdsite/proximity/repository/codehaus
# URL of remote snapshot.
remote.snapshot.url=scp://sirdsite/var/www/html/m2repos
remote.release.url=scp://sirdsite/var/www/html/m2repos/dst/release
target.dir=target
target.gensrc=target/generated-sources
target.dist=target/dist
target.classes=target/classes
lib=lib
src=src/main/java
artifactOne=artifact1.jar
artifactTwo=artifact2.jar
When I execute this command, it seems to hang at reading my long-ish
settings.xml
[mykel@DHBHDTBLDCTRLAH ExampleAntMavenProject]$ ant -v
Apache Ant version 1.6.5 compiled on June 2 2005
Buildfile: build.xml
Detected Java version: 1.5 in: /usr/java/jdk1.5.0_12/jre
Detected OS: Linux
parsing buildfile
/home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml with URI =
file:///home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml
Project base dir set to:
/home/mykel/workspace-tutorial/ExampleAntMavenProject
[property] Loading
/home/mykel/workspace-tutorial/ExampleAntMavenProject/build.properties
Build sequence for target(s) `all' is [init, maven-setup,
resolve-dependencies, compile, package, install, all]
Complete build sequence is [init, maven-setup, resolve-dependencies,
compile, package, install, all, deploy-subordinate, deploy-release, clean,
deploy-snapshot, ]
init:
maven-setup:
[get] Getting:
http://sirdsite/installs/maven-ant-tasks/maven-ant-tasks-2.0.7.jar
[get] To:
/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
ant-tasks-2.0.7.jar
[get] Not modified - so not downloaded
parsing buildfile
jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml with URI =
jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml
[echo] Installing Provider
[artifact:install-provider] Using remote repositories:
- id=central, url=http://repo1.maven.org/maven2, releases=enabled,
snapshots=disabled
[artifact:install-provider] Loading Maven settings file:
/home/mykel/.m2/settings.xml
....and we wait.
I cut the settings.xml down to just the bare minimum (the mirror setting for
our proximity setup which keeps all the proxy/firewall issues away). No
discernible effect.
The wagon-provider is already installed in my local repo from various maven
builds, so the need to d/l it seems off-kilter but this is an ant project so
I dunno what's really supposed to happen here.
Am I doing something wrong?
MANTTASKS-6<http://jira.codehaus.org/browse/MANTTASKS-6>reports some
element of this fixed, although that seems to be unrelated to
an inability to read from my local settings file. I posted this same log as
a comment to the fixed issue.
--
"My friends tell me I have an intimacy problem. But they don't really know
me." -- Garry Shandling
Anyone who has the power to make you believe absurdities has the power to
make you commit injustices. -- Voltaire
Re: maven-ant-tasks-2.0.7 settings file read hangs at install-provider
Posted by Mykel Alvis <my...@weirdness.com>.
Hi Hervé,
That's great (bad) news! :)
I'll check it out as soon as possible, which is likely to be the day after
tomorrow when I get back to the office. Once I can determine that this fix
is working, I'll respond to the issue.
Thanks a lot for your help!
Mykel
On 8/10/07, Hervé BOUTEMY <he...@free.fr> wrote:
>
> Hi Mykel,
>
> Ok, I studied your case more deeply: you've just found a bug! :)
> For remote repositories defined in pom.xml, settings file is taken into
> account but not for remote repositories defined in build.xml...
>
> I filed a Jira issue, with a testcase and fix:
> http://jira.codehaus.org/browse/MANTTASKS-85
>
> You'll find the modified tasks at
> http://codehaus.org/~hboutemy/maven-ant-tasks-2.0.7-MANTTASKS-85.jar
>
> Can you check that it fixes your problem?
> Then it should be released in 2.0.8.
>
> Hervé
>
> Le vendredi 10 août 2007, Mykel Alvis a écrit :
> > Hervé,
> > Sorry it took so long to get back to you about this. I've been out of
> the
> > office and had trouble accessing the systems in question.
> >
> > Attached is my settings.xml that is used by 40+ developers daily with
> this.
> > We do have a local firewall, but it definitely works with maven since we
> > override central with our internal proximity instance. What appears to
> be
> > the case is that the settings.xml isn't getting read prior to the
> attempt
> > to acquire the provider, so it's trying
> > (http://repo1.maven.org/maven2/....) instead of
> > (http://sirdsite/proximity/....), but that's just a guess.
> >
> > Thanks again for your help,
> > Mykel
> >
> > On 8/7/07, Hervé BOUTEMY <he...@free.fr> wrote:
> > > ok, settings.xml has been read, but the task is hanging when trying to
> > > download wagon-provider-api from central http://repo1.maven.org/maven2
> > >
> > > Do you have direct internet access, or through a proxy?
> > > If through a proxy, how was it configured in settings.xml?
> > > Did you try your configuration with full Maven instead of Ant tasks?
> > >
> > > Le mardi 7 août 2007, Mykel Alvis a écrit :
> > > > Hi Hervé,
> > > >
> > > > OK. I lied. It timed out after several minutes. I don't know why
> it
> > > > would delay the 10 minutes it took before, but must recently it
> timed
> > >
> > > out
> > >
> > > > in less than 4.
> > > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
"My friends tell me I have an intimacy problem. But they don't really know
me." -- Garry Shandling
Anyone who has the power to make you believe absurdities has the power to
make you commit injustices. -- Voltaire
Re: maven-ant-tasks-2.0.7 settings file read hangs at install-provider
Posted by Hervé BOUTEMY <he...@free.fr>.
Hi Mykel,
Ok, I studied your case more deeply: you've just found a bug! :)
For remote repositories defined in pom.xml, settings file is taken into
account but not for remote repositories defined in build.xml...
I filed a Jira issue, with a testcase and fix:
http://jira.codehaus.org/browse/MANTTASKS-85
You'll find the modified tasks at
http://codehaus.org/~hboutemy/maven-ant-tasks-2.0.7-MANTTASKS-85.jar
Can you check that it fixes your problem?
Then it should be released in 2.0.8.
Hervé
Le vendredi 10 août 2007, Mykel Alvis a écrit :
> Hervé,
> Sorry it took so long to get back to you about this. I've been out of the
> office and had trouble accessing the systems in question.
>
> Attached is my settings.xml that is used by 40+ developers daily with this.
> We do have a local firewall, but it definitely works with maven since we
> override central with our internal proximity instance. What appears to be
> the case is that the settings.xml isn't getting read prior to the attempt
> to acquire the provider, so it's trying
> (http://repo1.maven.org/maven2/....) instead of
> (http://sirdsite/proximity/....), but that's just a guess.
>
> Thanks again for your help,
> Mykel
>
> On 8/7/07, Hervé BOUTEMY <he...@free.fr> wrote:
> > ok, settings.xml has been read, but the task is hanging when trying to
> > download wagon-provider-api from central http://repo1.maven.org/maven2
> >
> > Do you have direct internet access, or through a proxy?
> > If through a proxy, how was it configured in settings.xml?
> > Did you try your configuration with full Maven instead of Ant tasks?
> >
> > Le mardi 7 août 2007, Mykel Alvis a écrit :
> > > Hi Hervé,
> > >
> > > OK. I lied. It timed out after several minutes. I don't know why it
> > > would delay the 10 minutes it took before, but must recently it timed
> >
> > out
> >
> > > in less than 4.
> > >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Maven 2 documentation portion of the site is horribly broken
Posted by EJ Ciramella <ej...@upromise.com>.
Ugggg - any of the "jump-to-location-on-page" links are similarly
broken.
Thanks for the workaround, I'm looking forward to the real fix.
-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com]
Sent: Friday, August 10, 2007 12:13 PM
To: Maven Users List
Subject: Re: Maven 2 documentation portion of the site is horribly
broken
Looks like the links are broken thanks to a recent update of the site.
Fortunately, they are easy for you to fix in your browser until the
site is updated again (hopefully *very* soon) with proper links.
Let's take the jar plugin as an example:
Current link is:
http://maven.apache.org/plugins/index.html#maven-jar-plugin/
Correct link is: http://maven.apache.org/plugins/maven-jar-plugin/
Just cut out the "index.html#" and you'll get to the documentation for
the jar plugin.
Wayne
On 8/10/07, EJ Ciramella <ej...@upromise.com> wrote:
> Can someone please either enlighten me as to what I'm doing wrong or
fix
> the site? Almost 90% of the links anywhere don't work. Considering
> this is the ONLY source for m2 documentation, this is a huge failure.
>
> http://maven.apache.org/plugins/index.html
>
> None of those links work anymore for me. I'm using the latest firefox
> for what its worth.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven 2 documentation portion of the site is horribly broken
Posted by Wayne Fay <wa...@gmail.com>.
Looks like the links are broken thanks to a recent update of the site.
Fortunately, they are easy for you to fix in your browser until the
site is updated again (hopefully *very* soon) with proper links.
Let's take the jar plugin as an example:
Current link is: http://maven.apache.org/plugins/index.html#maven-jar-plugin/
Correct link is: http://maven.apache.org/plugins/maven-jar-plugin/
Just cut out the "index.html#" and you'll get to the documentation for
the jar plugin.
Wayne
On 8/10/07, EJ Ciramella <ej...@upromise.com> wrote:
> Can someone please either enlighten me as to what I'm doing wrong or fix
> the site? Almost 90% of the links anywhere don't work. Considering
> this is the ONLY source for m2 documentation, this is a huge failure.
>
> http://maven.apache.org/plugins/index.html
>
> None of those links work anymore for me. I'm using the latest firefox
> for what its worth.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven 2 documentation portion of the site is horribly broken
Posted by Wendy Smoak <ws...@gmail.com>.
On 8/10/07, EJ Ciramella <ej...@upromise.com> wrote:
> Can someone please either enlighten me as to what I'm doing wrong or fix
> the site? Almost 90% of the links anywhere don't work. Considering
> this is the ONLY source for m2 documentation, this is a huge failure.
>
> http://maven.apache.org/plugins/index.html
No idea yet what happened, but to work around it, edit the url to
remove "index.html#". For example:
http://maven.apache.org/plugins/index.html#maven-compiler-plugin/
--> http://maven.apache.org/plugins/maven-compiler-plugin/
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Maven 2 documentation portion of the site is horribly broken
Posted by EJ Ciramella <ej...@upromise.com>.
Can someone please either enlighten me as to what I'm doing wrong or fix
the site? Almost 90% of the links anywhere don't work. Considering
this is the ONLY source for m2 documentation, this is a huge failure.
http://maven.apache.org/plugins/index.html
None of those links work anymore for me. I'm using the latest firefox
for what its worth.
Re: maven-ant-tasks-2.0.7 settings file read hangs at install-provider
Posted by Mykel Alvis <my...@weirdness.com>.
Herv�,
Sorry it took so long to get back to you about this. I've been out of the
office and had trouble accessing the systems in question.
Attached is my settings.xml that is used by 40+ developers daily with this.
We do have a local firewall, but it definitely works with maven since we
override central with our internal proximity instance. What appears to be
the case is that the settings.xml isn't getting read prior to the attempt to
acquire the provider, so it's trying (http://repo1.maven.org/maven2/....)
instead of (http://sirdsite/proximity/....), but that's just a guess.
Thanks again for your help,
Mykel
On 8/7/07, Herv� BOUTEMY <he...@free.fr> wrote:
>
> ok, settings.xml has been read, but the task is hanging when trying to
> download wagon-provider-api from central http://repo1.maven.org/maven2
>
> Do you have direct internet access, or through a proxy?
> If through a proxy, how was it configured in settings.xml?
> Did you try your configuration with full Maven instead of Ant tasks?
>
> Le mardi 7 ao�t 2007, Mykel Alvis a �crit :
> > Hi Herv�,
> >
> > OK. I lied. It timed out after several minutes. I don't know why it
> > would delay the 10 minutes it took before, but must recently it timed
> out
> > in less than 4.
> >
> > The log was then:
> > BUILD FAILED
> > /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml:32:
> Error
> > downloading wagon provider from the remote repository: Missing:
> > ----------
> > 1) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
> >
> > Try downloading the file manually from the project website.
> >
> > Then, install it using the command:
> > mvn install:install-file
> > -DgroupId=org.apache.maven.wagon-DartifactId=wagon-provider-api \
> > -Dversion=1.0-beta-2 -Dpackaging=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.wagon-DartifactId=wagon-provider-api \
> > -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \
> > -Durl=[url] -DrepositoryId=[id]
> >
> > Path to dependency:
> > 1) unspecified:unspecified:jar:0.0
> > 2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
> > 3) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
> >
> > ----------
> > 1 required artifact is missing.
> >
> > for artifact:
> > unspecified:unspecified:jar:0.0
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2)
> >
> > at
> > org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
> > InstallWagonProviderTask.java:117)
> > at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(
> > AbstractArtifactTask.java:522)
> > at org.apache.tools.ant.UnknownElement.execute(
> UnknownElement.java
> >
> > :275)
> >
> > at org.apache.tools.ant.Task.perform(Task.java:364)
> > at org.apache.tools.ant.Target.execute(Target.java:341)
> > at org.apache.tools.ant.Target.performTasks(Target.java:369)
> > at org.apache.tools.ant.Project.executeSortedTargets(
> Project.java
> >
> > :1216)
> >
> > at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
> > at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(
> > DefaultExecutor.java:40)
> > at org.apache.tools.ant.Project.executeTargets(Project.java
> :1068)
> > at org.apache.tools.ant.Main.runBuild(Main.java:668)
> > at org.apache.tools.ant.Main.startAnt(Main.java:187)
> > at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
> > at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
> > Caused by:
> > org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException:
> > Missing:
> > ----------
> > 1) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
> >
> > Try downloading the file manually from the project website.
> >
> > Then, install it using the command:
> > mvn install:install-file
> > -DgroupId=org.apache.maven.wagon-DartifactId=wagon-provider-api \
> > -Dversion=1.0-beta-2 -Dpackaging=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.wagon-DartifactId=wagon-provider-api \
> > -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \
> > -Durl=[url] -DrepositoryId=[id]
> >
> > Path to dependency:
> > 1) unspecified:unspecified:jar:0.0
> > 2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
> > 3) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
> >
> > ----------
> > 1 required artifact is missing.
> >
> > for artifact:
> > unspecified:unspecified:jar:0.0
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2)
> >
> > at
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
> >ely (DefaultArtifactResolver.java:305)
> > at
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
> >ely (DefaultArtifactResolver.java:272)
> > at
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
> >ely (DefaultArtifactResolver.java:243)
> > at
> > org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
> > InstallWagonProviderTask.java:111)
> > ... 13 more
> > --- Nested Exception ---
> > org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException:
> > Missing:
> > ----------
> > 1) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
> >
> > Try downloading the file manually from the project website.
> >
> > Then, install it using the command:
> > mvn install:install-file
> > -DgroupId=org.apache.maven.wagon-DartifactId=wagon-provider-api \
> > -Dversion=1.0-beta-2 -Dpackaging=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.wagon-DartifactId=wagon-provider-api \
> > -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \
> > -Durl=[url] -DrepositoryId=[id]
> >
> > Path to dependency:
> > 1) unspecified:unspecified:jar:0.0
> > 2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
> > 3) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
> >
> > ----------
> > 1 required artifact is missing.
> >
> > for artifact:
> > unspecified:unspecified:jar:0.0
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2)
> >
> > at
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
> >ely (DefaultArtifactResolver.java:305)
> > at
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
> >ely (DefaultArtifactResolver.java:272)
> > at
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
> >ely (DefaultArtifactResolver.java:243)
> > at
> > org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
> > InstallWagonProviderTask.java:111)
> > at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(
> > AbstractArtifactTask.java:522)
> > at org.apache.tools.ant.UnknownElement.execute(
> UnknownElement.java
> >
> > :275)
> >
> > at org.apache.tools.ant.Task.perform(Task.java:364)
> > at org.apache.tools.ant.Target.execute(Target.java:341)
> > at org.apache.tools.ant.Target.performTasks(Target.java:369)
> > at org.apache.tools.ant.Project.executeSortedTargets(
> Project.java
> >
> > :1216)
> >
> > at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
> > at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(
> > DefaultExecutor.java:40)
> > at org.apache.tools.ant.Project.executeTargets(Project.java
> :1068)
> > at org.apache.tools.ant.Main.runBuild(Main.java:668)
> > at org.apache.tools.ant.Main.startAnt(Main.java:187)
> > at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
> > at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
> >
> > Total time: 3 minutes 17 seconds
> > -------------------------------- End of log ------
> >
> >
> > The thread dump:
> > Full thread dump Java HotSpot(TM) Client VM (1.5.0_12-b04 mixed mode,
> > sharing):
> >
> > "Low Memory Detector" daemon prio=1 tid=0xb2100b50 nid=0x613a runnable
> > [0x00000000..0x00000000]
> >
> > "CompilerThread0" daemon prio=1 tid=0x0983e918 nid=0x6139 waiting on
> > condition [0x00000000..0xb22ad798]
> >
> > "Signal Dispatcher" daemon prio=1 tid=0x0983d9f0 nid=0x6138 waiting on
> > condition [0x00000000..0x00000000]
> >
> > "Finalizer" daemon prio=1 tid=0x09837c50 nid=0x6137 in Object.wait()
> > [0xb25af000..0xb25b00b0]
> > at java.lang.Object.wait(Native Method)
> > - waiting on <0x88fec588> (a java.lang.ref.ReferenceQueue$Lock)
> > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
> > - locked <0x88fec588> (a java.lang.ref.ReferenceQueue$Lock)
> > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
> > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java
> :159)
> >
> > "Reference Handler" daemon prio=1 tid=0x09835dc8 nid=0x6136 in
> > Object.wait() [0xb2630000..0xb2631030]
> > at java.lang.Object.wait(Native Method)
> > - waiting on <0x88fec608> (a java.lang.ref.Reference$Lock)
> > at java.lang.Object.wait(Object.java:474)
> > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java
> :116)
> > - locked <0x88fec608> (a java.lang.ref.Reference$Lock)
> >
> > "main" prio=1 tid=0x097f69e8 nid=0x6133 runnable
> [0xbfff2000..0xbfff39a8]
> > at java.net.PlainSocketImpl.socketConnect(Native Method)
> > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> > - locked <0x88b52220> (a java.net.PlainSocketImpl)
> > at java.net.PlainSocketImpl.connectToAddress(
> PlainSocketImpl.java
> >
> > :195)
> >
> > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> > at java.net.Socket.connect(Socket.java:519)
> > at java.net.Socket.connect(Socket.java:469)
> > at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
> > at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
> > at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
> > - locked <0x88b521a0> (a sun.net.www.http.HttpClient)
> > at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
> > at sun.net.www.http.HttpClient.New(HttpClient.java:304)
> > at sun.net.www.http.HttpClient.New(HttpClient.java:316)
> > at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(
> > HttpURLConnection.java:813)
> > at sun.net.www.protocol.http.HttpURLConnection.plainConnect(
> > HttpURLConnection.java:765)
> > at sun.net.www.protocol.http.HttpURLConnection.connect(
> > HttpURLConnection.java:690)
> > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(
> > HttpURLConnection.java:934)
> > - locked <0x88b51938> (a
> > sun.net.www.protocol.http.HttpURLConnection )
> > at
> > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData
> (
> > LightweightHttpWagon.java:83)
> > at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68)
> > at
> > org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(
> > DefaultWagonManager.java:462)
> > at
> > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> > (DefaultWagonManager.java:347)
> > at
> > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> > (DefaultWagonManager.java:302)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:185)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:73)
> > at
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
> >ely (DefaultArtifactResolver.java:294)
> > at
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
> >ely (DefaultArtifactResolver.java:272)
> > at
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
> >ely (DefaultArtifactResolver.java:243)
> > at
> > org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
> > InstallWagonProviderTask.java:111)
> > at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(
> > AbstractArtifactTask.java:522)
> > at org.apache.tools.ant.UnknownElement.execute(
> UnknownElement.java
> >
> > :275)
> >
> > at org.apache.tools.ant.Task.perform(Task.java:364)
> > at org.apache.tools.ant.Target.execute(Target.java:341)
> > at org.apache.tools.ant.Target.performTasks(Target.java:369)
> > at org.apache.tools.ant.Project.executeSortedTargets(
> Project.java
> >
> > :1216)
> >
> > at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
> > at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(
> > DefaultExecutor.java:40)
> > at org.apache.tools.ant.Project.executeTargets(Project.java
> :1068)
> > at org.apache.tools.ant.Main.runBuild(Main.java:668)
> > at org.apache.tools.ant.Main.startAnt(Main.java:187)
> > at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
> > at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
> >
> > "VM Thread" prio=1 tid=0x09834950 nid=0x6135 runnable
> >
> > "VM Periodic Task Thread" prio=1 tid=0xb2102108 nid=0x613b waiting on
> > condition
> >
> > ------- End of thread dump
> >
> > What else can I do to help?
> >
> > Mykel
> >
> > On 8/7/07, Herv� BOUTEMY <he...@free.fr> wrote:
> > > Hi Mykel,
> > >
> > > There is something weird happenning: I don't understand why reading a
> > > file would hang. FYI, it's working perfectly in a number of places.
> > >
> > > We'll have to find what is so special in your case.
> > > Can you get a thread dump when ant freezes?
> > > On Linux, it's: kill -SIGQUIT <pid>
> > >
> > > Herv�
> > >
> > > Le mardi 7 ao�t 2007, Mykel Alvis a �crit :
> > > > Hi all,
> > > > I'm trying to make an example ant project for one of our teams who
> > > > currently uses ant to do their builds.
> > > >
> > > > Relevant sections of build.xml
> > > > --------------------------------------------
> > > > <target name="init">
> > > > <tstamp>
> > > > <format property="build.date" pattern="yyyy-MM-dd@hhmmss
> "
> > > > /> </tstamp>
> > > > <mkdir dir="${target.dir}" />
> > > > <mkdir dir="${ target.classes}" />
> > > > <mkdir dir="${target.gensrc}" />
> > > > <mkdir dir="${target.dist}" />
> > > > <mkdir dir="${lib}" />
> > > > </target>
> > > >
> > > > <target name="maven-setup" depends="init" description="Setup
> maven
> > >
> > > ant
> > >
> > > > tasks, required for dependency resolution">
> > > > <get src="${maven.ant.task.url}" dest="${lib}/${
> > > > maven.ant.task.jar}" usetimestamp="true" />
> > > > <path id="maven-ant-tasks.classpath"
> > > > path="lib/${maven.ant.task.jar}" />
> > > > <typedef resource="org/apache/maven/artifact/ant/antlib.xml"
> > > > uri="urn:maven-artifact-ant" classpathref="
> maven-ant-tasks.classpath"
> > >
> > > />
> > >
> > > > <artifact:remoteRepository id="remote.public" url="${
> url.public
> > >
> > > }"
> > >
> > > > /> <echo message="Installing Provider"/>
> > > > <artifact:install-provider artifactId="wagon-webdav"
> version="
> > > > 1.0-beta-2" />
> > > > <echo message="Provider Installed"/>
> > > > </target>
> > > >
> > > >
> > > > build.properties
> > > > -------------------------
> > > > custom = true
> > > > # Jarfile name of the maven ant tasks. Occasionally updates
> > > > maven.ant.task.jar=maven-ant-tasks-2.0.7.jar
> > > > # Local file location of maven ant tasks jar
> > >
> > >
> maven.ant.task.url=http://sirdsite/installs/maven-ant-tasks/${maven.ant.t
> > >as
> > >
> > > >k.jar} # repo username for scp
> > > > repository.username=localbuild
> > > > # localtion of local private key
> > > > repository.privatekey=${user.home}/.ssh/id_dsa
> > > > url.public=http://sirdsite/proximity/repository/public
> > > > url.codehaus=http://sirdsite/proximity/repository/codehaus
> > > > # URL of remote snapshot.
> > > > remote.snapshot.url=scp://sirdsite/var/www/html/m2repos
> > > > remote.release.url=scp://sirdsite/var/www/html/m2repos/dst/release
> > > > target.dir=target
> > > > target.gensrc=target/generated-sources
> > > > target.dist=target/dist
> > > > target.classes=target/classes
> > > > lib=lib
> > > > src=src/main/java
> > > > artifactOne=artifact1.jar
> > > > artifactTwo=artifact2.jar
> > > >
> > > >
> > > > When I execute this command, it seems to hang at reading my long-ish
> > > > settings.xml
> > > > [mykel@DHBHDTBLDCTRLAH ExampleAntMavenProject]$ ant -v
> > > > Apache Ant version 1.6.5 compiled on June 2 2005
> > > > Buildfile: build.xml
> > > > Detected Java version: 1.5 in: /usr/java/jdk1.5.0_12/jre
> > > > Detected OS: Linux
> > > > parsing buildfile
> > > > /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml with
> > > > URI
> > >
> > > =
> > >
> > > >
> file:///home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml
> > > > Project base dir set to:
> > > > /home/mykel/workspace-tutorial/ExampleAntMavenProject
> > > > [property] Loading
> > > >
> /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.properties
> > > > Build sequence for target(s) `all' is [init, maven-setup,
> > > > resolve-dependencies, compile, package, install, all]
> > > > Complete build sequence is [init, maven-setup, resolve-dependencies,
> > > > compile, package, install, all, deploy-subordinate, deploy-release,
> > >
> > > clean,
> > >
> > > > deploy-snapshot, ]
> > > >
> > > > init:
> > > >
> > > > maven-setup:
> > > > [get] Getting:
> > > > http://sirdsite/installs/maven-ant-tasks/maven-ant-tasks-2.0.7.jar
> > > > [get] To:
> > > > /home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> > > > ant-tasks-2.0.7.jar
> > > > [get] Not modified - so not downloaded
> > > > parsing buildfile
> > >
> > >
> jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> > >
> > > > ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml with
> URI
> > > > =
> > >
> > >
> jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> > >
> > > > ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml
> > > > [echo] Installing Provider
> > > > [artifact:install-provider] Using remote repositories:
> > > > - id=central, url=http://repo1.maven.org/maven2, releases=enabled,
> > > > snapshots=disabled
> > > > [artifact:install-provider] Loading Maven settings file:
> > > > /home/mykel/.m2/settings.xml
> > > >
> > > > ....and we wait.
> > > >
> > > > I cut the settings.xml down to just the bare minimum (the mirror
> > > > setting for our proximity setup which keeps all the proxy/firewall
> > > > issues away). No discernible effect.
> > > >
> > > > The wagon-provider is already installed in my local repo from
> various
> > >
> > > maven
> > >
> > > > builds, so the need to d/l it seems off-kilter but this is an ant
> > >
> > > project
> > >
> > > > so I dunno what's really supposed to happen here.
> > > >
> > > > Am I doing something wrong?
> > > > MANTTASKS-6<http://jira.codehaus.org/browse/MANTTASKS-6>reports some
> > > > element of this fixed, although that seems to be unrelated to
> > > > an inability to read from my local settings file. I posted this
> same
> > >
> > > log
> > >
> > > > as a comment to the fixed issue.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
"My friends tell me I have an intimacy problem. But they don't really know
me." -- Garry Shandling
Anyone who has the power to make you believe absurdities has the power to
make you commit injustices. -- Voltaire
Re: maven-ant-tasks-2.0.7 settings file read hangs at install-provider
Posted by Hervé BOUTEMY <he...@free.fr>.
ok, settings.xml has been read, but the task is hanging when trying to
download wagon-provider-api from central http://repo1.maven.org/maven2
Do you have direct internet access, or through a proxy?
If through a proxy, how was it configured in settings.xml?
Did you try your configuration with full Maven instead of Ant tasks?
Le mardi 7 août 2007, Mykel Alvis a écrit :
> Hi Hervé,
>
> OK. I lied. It timed out after several minutes. I don't know why it
> would delay the 10 minutes it took before, but must recently it timed out
> in less than 4.
>
> The log was then:
> BUILD FAILED
> /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml:32: Error
> downloading wagon provider from the remote repository: Missing:
> ----------
> 1) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file
> -DgroupId=org.apache.maven.wagon-DartifactId=wagon-provider-api \
> -Dversion=1.0-beta-2 -Dpackaging=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.wagon-DartifactId=wagon-provider-api \
> -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) unspecified:unspecified:jar:0.0
> 2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
> 3) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> unspecified:unspecified:jar:0.0
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
> at
> org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
> InstallWagonProviderTask.java:117)
> at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(
> AbstractArtifactTask.java:522)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java
>
> :275)
>
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java
>
> :1216)
>
> at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(
> DefaultExecutor.java:40)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
> at org.apache.tools.ant.Main.runBuild(Main.java:668)
> at org.apache.tools.ant.Main.startAnt(Main.java:187)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
> Caused by:
> org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException:
> Missing:
> ----------
> 1) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file
> -DgroupId=org.apache.maven.wagon-DartifactId=wagon-provider-api \
> -Dversion=1.0-beta-2 -Dpackaging=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.wagon-DartifactId=wagon-provider-api \
> -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) unspecified:unspecified:jar:0.0
> 2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
> 3) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> unspecified:unspecified:jar:0.0
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
>ely (DefaultArtifactResolver.java:305)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
>ely (DefaultArtifactResolver.java:272)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
>ely (DefaultArtifactResolver.java:243)
> at
> org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
> InstallWagonProviderTask.java:111)
> ... 13 more
> --- Nested Exception ---
> org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException:
> Missing:
> ----------
> 1) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file
> -DgroupId=org.apache.maven.wagon-DartifactId=wagon-provider-api \
> -Dversion=1.0-beta-2 -Dpackaging=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.wagon-DartifactId=wagon-provider-api \
> -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) unspecified:unspecified:jar:0.0
> 2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
> 3) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> unspecified:unspecified:jar:0.0
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
>ely (DefaultArtifactResolver.java:305)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
>ely (DefaultArtifactResolver.java:272)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
>ely (DefaultArtifactResolver.java:243)
> at
> org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
> InstallWagonProviderTask.java:111)
> at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(
> AbstractArtifactTask.java:522)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java
>
> :275)
>
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java
>
> :1216)
>
> at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(
> DefaultExecutor.java:40)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
> at org.apache.tools.ant.Main.runBuild(Main.java:668)
> at org.apache.tools.ant.Main.startAnt(Main.java:187)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
>
> Total time: 3 minutes 17 seconds
> -------------------------------- End of log ------
>
>
> The thread dump:
> Full thread dump Java HotSpot(TM) Client VM (1.5.0_12-b04 mixed mode,
> sharing):
>
> "Low Memory Detector" daemon prio=1 tid=0xb2100b50 nid=0x613a runnable
> [0x00000000..0x00000000]
>
> "CompilerThread0" daemon prio=1 tid=0x0983e918 nid=0x6139 waiting on
> condition [0x00000000..0xb22ad798]
>
> "Signal Dispatcher" daemon prio=1 tid=0x0983d9f0 nid=0x6138 waiting on
> condition [0x00000000..0x00000000]
>
> "Finalizer" daemon prio=1 tid=0x09837c50 nid=0x6137 in Object.wait()
> [0xb25af000..0xb25b00b0]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x88fec588> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
> - locked <0x88fec588> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
>
> "Reference Handler" daemon prio=1 tid=0x09835dc8 nid=0x6136 in
> Object.wait() [0xb2630000..0xb2631030]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x88fec608> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:474)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
> - locked <0x88fec608> (a java.lang.ref.Reference$Lock)
>
> "main" prio=1 tid=0x097f69e8 nid=0x6133 runnable [0xbfff2000..0xbfff39a8]
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> - locked <0x88b52220> (a java.net.PlainSocketImpl)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java
>
> :195)
>
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> at java.net.Socket.connect(Socket.java:519)
> at java.net.Socket.connect(Socket.java:469)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
> - locked <0x88b521a0> (a sun.net.www.http.HttpClient)
> at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
> at sun.net.www.http.HttpClient.New(HttpClient.java:304)
> at sun.net.www.http.HttpClient.New(HttpClient.java:316)
> at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(
> HttpURLConnection.java:813)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(
> HttpURLConnection.java:765)
> at sun.net.www.protocol.http.HttpURLConnection.connect(
> HttpURLConnection.java:690)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(
> HttpURLConnection.java:934)
> - locked <0x88b51938> (a
> sun.net.www.protocol.http.HttpURLConnection )
> at
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(
> LightweightHttpWagon.java:83)
> at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(
> DefaultWagonManager.java:462)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> (DefaultWagonManager.java:347)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> (DefaultWagonManager.java:302)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:185)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:73)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
>ely (DefaultArtifactResolver.java:294)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
>ely (DefaultArtifactResolver.java:272)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitiv
>ely (DefaultArtifactResolver.java:243)
> at
> org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
> InstallWagonProviderTask.java:111)
> at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(
> AbstractArtifactTask.java:522)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java
>
> :275)
>
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java
>
> :1216)
>
> at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(
> DefaultExecutor.java:40)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
> at org.apache.tools.ant.Main.runBuild(Main.java:668)
> at org.apache.tools.ant.Main.startAnt(Main.java:187)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
>
> "VM Thread" prio=1 tid=0x09834950 nid=0x6135 runnable
>
> "VM Periodic Task Thread" prio=1 tid=0xb2102108 nid=0x613b waiting on
> condition
>
> ------- End of thread dump
>
> What else can I do to help?
>
> Mykel
>
> On 8/7/07, Hervé BOUTEMY <he...@free.fr> wrote:
> > Hi Mykel,
> >
> > There is something weird happenning: I don't understand why reading a
> > file would hang. FYI, it's working perfectly in a number of places.
> >
> > We'll have to find what is so special in your case.
> > Can you get a thread dump when ant freezes?
> > On Linux, it's: kill -SIGQUIT <pid>
> >
> > Hervé
> >
> > Le mardi 7 août 2007, Mykel Alvis a écrit :
> > > Hi all,
> > > I'm trying to make an example ant project for one of our teams who
> > > currently uses ant to do their builds.
> > >
> > > Relevant sections of build.xml
> > > --------------------------------------------
> > > <target name="init">
> > > <tstamp>
> > > <format property="build.date" pattern="yyyy-MM-dd@hhmmss"
> > > /> </tstamp>
> > > <mkdir dir="${target.dir}" />
> > > <mkdir dir="${ target.classes}" />
> > > <mkdir dir="${target.gensrc}" />
> > > <mkdir dir="${target.dist}" />
> > > <mkdir dir="${lib}" />
> > > </target>
> > >
> > > <target name="maven-setup" depends="init" description="Setup maven
> >
> > ant
> >
> > > tasks, required for dependency resolution">
> > > <get src="${maven.ant.task.url}" dest="${lib}/${
> > > maven.ant.task.jar}" usetimestamp="true" />
> > > <path id="maven-ant-tasks.classpath"
> > > path="lib/${maven.ant.task.jar}" />
> > > <typedef resource="org/apache/maven/artifact/ant/antlib.xml"
> > > uri="urn:maven-artifact-ant" classpathref=" maven-ant-tasks.classpath"
> >
> > />
> >
> > > <artifact:remoteRepository id="remote.public" url="${url.public
> >
> > }"
> >
> > > /> <echo message="Installing Provider"/>
> > > <artifact:install-provider artifactId="wagon-webdav" version="
> > > 1.0-beta-2" />
> > > <echo message="Provider Installed"/>
> > > </target>
> > >
> > >
> > > build.properties
> > > -------------------------
> > > custom = true
> > > # Jarfile name of the maven ant tasks. Occasionally updates
> > > maven.ant.task.jar=maven-ant-tasks-2.0.7.jar
> > > # Local file location of maven ant tasks jar
> >
> > maven.ant.task.url=http://sirdsite/installs/maven-ant-tasks/${maven.ant.t
> >as
> >
> > >k.jar} # repo username for scp
> > > repository.username=localbuild
> > > # localtion of local private key
> > > repository.privatekey=${user.home}/.ssh/id_dsa
> > > url.public=http://sirdsite/proximity/repository/public
> > > url.codehaus=http://sirdsite/proximity/repository/codehaus
> > > # URL of remote snapshot.
> > > remote.snapshot.url=scp://sirdsite/var/www/html/m2repos
> > > remote.release.url=scp://sirdsite/var/www/html/m2repos/dst/release
> > > target.dir=target
> > > target.gensrc=target/generated-sources
> > > target.dist=target/dist
> > > target.classes=target/classes
> > > lib=lib
> > > src=src/main/java
> > > artifactOne=artifact1.jar
> > > artifactTwo=artifact2.jar
> > >
> > >
> > > When I execute this command, it seems to hang at reading my long-ish
> > > settings.xml
> > > [mykel@DHBHDTBLDCTRLAH ExampleAntMavenProject]$ ant -v
> > > Apache Ant version 1.6.5 compiled on June 2 2005
> > > Buildfile: build.xml
> > > Detected Java version: 1.5 in: /usr/java/jdk1.5.0_12/jre
> > > Detected OS: Linux
> > > parsing buildfile
> > > /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml with
> > > URI
> >
> > =
> >
> > > file:///home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml
> > > Project base dir set to:
> > > /home/mykel/workspace-tutorial/ExampleAntMavenProject
> > > [property] Loading
> > > /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.properties
> > > Build sequence for target(s) `all' is [init, maven-setup,
> > > resolve-dependencies, compile, package, install, all]
> > > Complete build sequence is [init, maven-setup, resolve-dependencies,
> > > compile, package, install, all, deploy-subordinate, deploy-release,
> >
> > clean,
> >
> > > deploy-snapshot, ]
> > >
> > > init:
> > >
> > > maven-setup:
> > > [get] Getting:
> > > http://sirdsite/installs/maven-ant-tasks/maven-ant-tasks-2.0.7.jar
> > > [get] To:
> > > /home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> > > ant-tasks-2.0.7.jar
> > > [get] Not modified - so not downloaded
> > > parsing buildfile
> >
> > jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> >
> > > ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml with URI
> > > =
> >
> > jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> >
> > > ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml
> > > [echo] Installing Provider
> > > [artifact:install-provider] Using remote repositories:
> > > - id=central, url=http://repo1.maven.org/maven2, releases=enabled,
> > > snapshots=disabled
> > > [artifact:install-provider] Loading Maven settings file:
> > > /home/mykel/.m2/settings.xml
> > >
> > > ....and we wait.
> > >
> > > I cut the settings.xml down to just the bare minimum (the mirror
> > > setting for our proximity setup which keeps all the proxy/firewall
> > > issues away). No discernible effect.
> > >
> > > The wagon-provider is already installed in my local repo from various
> >
> > maven
> >
> > > builds, so the need to d/l it seems off-kilter but this is an ant
> >
> > project
> >
> > > so I dunno what's really supposed to happen here.
> > >
> > > Am I doing something wrong?
> > > MANTTASKS-6<http://jira.codehaus.org/browse/MANTTASKS-6>reports some
> > > element of this fixed, although that seems to be unrelated to
> > > an inability to read from my local settings file. I posted this same
> >
> > log
> >
> > > as a comment to the fixed issue.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-ant-tasks-2.0.7 settings file read hangs at install-provider
Posted by Mykel Alvis <my...@weirdness.com>.
Hi Hervé,
OK. I lied. It timed out after several minutes. I don't know why it
would delay the 10 minutes it took before, but must recently it timed out in
less than 4.
The log was then:
BUILD FAILED
/home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml:32: Error
downloading wagon provider from the remote repository: Missing:
----------
1) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.maven.wagon-DartifactId=wagon-provider-api \
-Dversion=1.0-beta-2 -Dpackaging=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.wagon-DartifactId=wagon-provider-api \
-Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) unspecified:unspecified:jar:0.0
2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
3) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
----------
1 required artifact is missing.
for artifact:
unspecified:unspecified:jar:0.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
InstallWagonProviderTask.java:117)
at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(
AbstractArtifactTask.java:522)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java
:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java
:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(
DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Caused by:
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException:
Missing:
----------
1) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.maven.wagon-DartifactId=wagon-provider-api \
-Dversion=1.0-beta-2 -Dpackaging=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.wagon-DartifactId=wagon-provider-api \
-Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) unspecified:unspecified:jar:0.0
2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
3) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
----------
1 required artifact is missing.
for artifact:
unspecified:unspecified:jar:0.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:305)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:272)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:243)
at org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
InstallWagonProviderTask.java:111)
... 13 more
--- Nested Exception ---
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException:
Missing:
----------
1) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.maven.wagon-DartifactId=wagon-provider-api \
-Dversion=1.0-beta-2 -Dpackaging=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.wagon-DartifactId=wagon-provider-api \
-Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) unspecified:unspecified:jar:0.0
2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
3) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
----------
1 required artifact is missing.
for artifact:
unspecified:unspecified:jar:0.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:305)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:272)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:243)
at org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
InstallWagonProviderTask.java:111)
at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(
AbstractArtifactTask.java:522)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java
:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java
:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(
DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Total time: 3 minutes 17 seconds
-------------------------------- End of log ------
The thread dump:
Full thread dump Java HotSpot(TM) Client VM (1.5.0_12-b04 mixed mode,
sharing):
"Low Memory Detector" daemon prio=1 tid=0xb2100b50 nid=0x613a runnable
[0x00000000..0x00000000]
"CompilerThread0" daemon prio=1 tid=0x0983e918 nid=0x6139 waiting on
condition [0x00000000..0xb22ad798]
"Signal Dispatcher" daemon prio=1 tid=0x0983d9f0 nid=0x6138 waiting on
condition [0x00000000..0x00000000]
"Finalizer" daemon prio=1 tid=0x09837c50 nid=0x6137 in Object.wait()
[0xb25af000..0xb25b00b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x88fec588> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x88fec588> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=1 tid=0x09835dc8 nid=0x6136 in Object.wait()
[0xb2630000..0xb2631030]
at java.lang.Object.wait(Native Method)
- waiting on <0x88fec608> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x88fec608> (a java.lang.ref.Reference$Lock)
"main" prio=1 tid=0x097f69e8 nid=0x6133 runnable [0xbfff2000..0xbfff39a8]
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
- locked <0x88b52220> (a java.net.PlainSocketImpl)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java
:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
- locked <0x88b521a0> (a sun.net.www.http.HttpClient)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
at sun.net.www.http.HttpClient.New(HttpClient.java:304)
at sun.net.www.http.HttpClient.New(HttpClient.java:316)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(
HttpURLConnection.java:813)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(
HttpURLConnection.java:765)
at sun.net.www.protocol.http.HttpURLConnection.connect(
HttpURLConnection.java:690)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(
HttpURLConnection.java:934)
- locked <0x88b51938> (a sun.net.www.protocol.http.HttpURLConnection
)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(
LightweightHttpWagon.java:83)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(
DefaultWagonManager.java:462)
at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
(DefaultWagonManager.java:347)
at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
(DefaultWagonManager.java:302)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:185)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:73)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:294)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:272)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:243)
at org.apache.maven.artifact.ant.InstallWagonProviderTask.doExecute(
InstallWagonProviderTask.java:111)
at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(
AbstractArtifactTask.java:522)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java
:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java
:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(
DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
"VM Thread" prio=1 tid=0x09834950 nid=0x6135 runnable
"VM Periodic Task Thread" prio=1 tid=0xb2102108 nid=0x613b waiting on
condition
------- End of thread dump
What else can I do to help?
Mykel
On 8/7/07, Hervé BOUTEMY <he...@free.fr> wrote:
>
> Hi Mykel,
>
> There is something weird happenning: I don't understand why reading a file
> would hang. FYI, it's working perfectly in a number of places.
>
> We'll have to find what is so special in your case.
> Can you get a thread dump when ant freezes?
> On Linux, it's: kill -SIGQUIT <pid>
>
> Hervé
>
> Le mardi 7 août 2007, Mykel Alvis a écrit :
> > Hi all,
> > I'm trying to make an example ant project for one of our teams who
> > currently uses ant to do their builds.
> >
> > Relevant sections of build.xml
> > --------------------------------------------
> > <target name="init">
> > <tstamp>
> > <format property="build.date" pattern="yyyy-MM-dd@hhmmss" />
> > </tstamp>
> > <mkdir dir="${target.dir}" />
> > <mkdir dir="${ target.classes}" />
> > <mkdir dir="${target.gensrc}" />
> > <mkdir dir="${target.dist}" />
> > <mkdir dir="${lib}" />
> > </target>
> >
> > <target name="maven-setup" depends="init" description="Setup maven
> ant
> > tasks, required for dependency resolution">
> > <get src="${maven.ant.task.url}" dest="${lib}/${
> > maven.ant.task.jar}" usetimestamp="true" />
> > <path id="maven-ant-tasks.classpath"
> > path="lib/${maven.ant.task.jar}" />
> > <typedef resource="org/apache/maven/artifact/ant/antlib.xml"
> > uri="urn:maven-artifact-ant" classpathref=" maven-ant-tasks.classpath"
> />
> > <artifact:remoteRepository id="remote.public" url="${url.public
> }"
> > /> <echo message="Installing Provider"/>
> > <artifact:install-provider artifactId="wagon-webdav" version="
> > 1.0-beta-2" />
> > <echo message="Provider Installed"/>
> > </target>
> >
> >
> > build.properties
> > -------------------------
> > custom = true
> > # Jarfile name of the maven ant tasks. Occasionally updates
> > maven.ant.task.jar=maven-ant-tasks-2.0.7.jar
> > # Local file location of maven ant tasks jar
> >
> maven.ant.task.url=http://sirdsite/installs/maven-ant-tasks/${maven.ant.tas
> >k.jar} # repo username for scp
> > repository.username=localbuild
> > # localtion of local private key
> > repository.privatekey=${user.home}/.ssh/id_dsa
> > url.public=http://sirdsite/proximity/repository/public
> > url.codehaus=http://sirdsite/proximity/repository/codehaus
> > # URL of remote snapshot.
> > remote.snapshot.url=scp://sirdsite/var/www/html/m2repos
> > remote.release.url=scp://sirdsite/var/www/html/m2repos/dst/release
> > target.dir=target
> > target.gensrc=target/generated-sources
> > target.dist=target/dist
> > target.classes=target/classes
> > lib=lib
> > src=src/main/java
> > artifactOne=artifact1.jar
> > artifactTwo=artifact2.jar
> >
> >
> > When I execute this command, it seems to hang at reading my long-ish
> > settings.xml
> > [mykel@DHBHDTBLDCTRLAH ExampleAntMavenProject]$ ant -v
> > Apache Ant version 1.6.5 compiled on June 2 2005
> > Buildfile: build.xml
> > Detected Java version: 1.5 in: /usr/java/jdk1.5.0_12/jre
> > Detected OS: Linux
> > parsing buildfile
> > /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml with URI
> =
> > file:///home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml
> > Project base dir set to:
> > /home/mykel/workspace-tutorial/ExampleAntMavenProject
> > [property] Loading
> > /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.properties
> > Build sequence for target(s) `all' is [init, maven-setup,
> > resolve-dependencies, compile, package, install, all]
> > Complete build sequence is [init, maven-setup, resolve-dependencies,
> > compile, package, install, all, deploy-subordinate, deploy-release,
> clean,
> > deploy-snapshot, ]
> >
> > init:
> >
> > maven-setup:
> > [get] Getting:
> > http://sirdsite/installs/maven-ant-tasks/maven-ant-tasks-2.0.7.jar
> > [get] To:
> > /home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> > ant-tasks-2.0.7.jar
> > [get] Not modified - so not downloaded
> > parsing buildfile
> >
> jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> > ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml with URI =
> >
> jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> > ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml
> > [echo] Installing Provider
> > [artifact:install-provider] Using remote repositories:
> > - id=central, url=http://repo1.maven.org/maven2, releases=enabled,
> > snapshots=disabled
> > [artifact:install-provider] Loading Maven settings file:
> > /home/mykel/.m2/settings.xml
> >
> > ....and we wait.
> >
> > I cut the settings.xml down to just the bare minimum (the mirror setting
> > for our proximity setup which keeps all the proxy/firewall issues away).
> > No discernible effect.
> >
> > The wagon-provider is already installed in my local repo from various
> maven
> > builds, so the need to d/l it seems off-kilter but this is an ant
> project
> > so I dunno what's really supposed to happen here.
> >
> > Am I doing something wrong?
> > MANTTASKS-6<http://jira.codehaus.org/browse/MANTTASKS-6>reports some
> > element of this fixed, although that seems to be unrelated to
> > an inability to read from my local settings file. I posted this same
> log
> > as a comment to the fixed issue.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
"My friends tell me I have an intimacy problem. But they don't really know
me." -- Garry Shandling
Anyone who has the power to make you believe absurdities has the power to
make you commit injustices. -- Voltaire
Re: maven-ant-tasks-2.0.7 settings file read hangs at install-provider
Posted by Hervé BOUTEMY <he...@free.fr>.
Hi Mykel,
There is something weird happenning: I don't understand why reading a file
would hang. FYI, it's working perfectly in a number of places.
We'll have to find what is so special in your case.
Can you get a thread dump when ant freezes?
On Linux, it's: kill -SIGQUIT <pid>
Hervé
Le mardi 7 août 2007, Mykel Alvis a écrit :
> Hi all,
> I'm trying to make an example ant project for one of our teams who
> currently uses ant to do their builds.
>
> Relevant sections of build.xml
> --------------------------------------------
> <target name="init">
> <tstamp>
> <format property="build.date" pattern="yyyy-MM-dd@hhmmss" />
> </tstamp>
> <mkdir dir="${target.dir}" />
> <mkdir dir="${ target.classes}" />
> <mkdir dir="${target.gensrc}" />
> <mkdir dir="${target.dist}" />
> <mkdir dir="${lib}" />
> </target>
>
> <target name="maven-setup" depends="init" description="Setup maven ant
> tasks, required for dependency resolution">
> <get src="${maven.ant.task.url}" dest="${lib}/${
> maven.ant.task.jar}" usetimestamp="true" />
> <path id="maven-ant-tasks.classpath"
> path="lib/${maven.ant.task.jar}" />
> <typedef resource="org/apache/maven/artifact/ant/antlib.xml"
> uri="urn:maven-artifact-ant" classpathref=" maven-ant-tasks.classpath" />
> <artifact:remoteRepository id="remote.public" url="${url.public}"
> /> <echo message="Installing Provider"/>
> <artifact:install-provider artifactId="wagon-webdav" version="
> 1.0-beta-2" />
> <echo message="Provider Installed"/>
> </target>
>
>
> build.properties
> -------------------------
> custom = true
> # Jarfile name of the maven ant tasks. Occasionally updates
> maven.ant.task.jar=maven-ant-tasks-2.0.7.jar
> # Local file location of maven ant tasks jar
> maven.ant.task.url=http://sirdsite/installs/maven-ant-tasks/${maven.ant.tas
>k.jar} # repo username for scp
> repository.username=localbuild
> # localtion of local private key
> repository.privatekey=${user.home}/.ssh/id_dsa
> url.public=http://sirdsite/proximity/repository/public
> url.codehaus=http://sirdsite/proximity/repository/codehaus
> # URL of remote snapshot.
> remote.snapshot.url=scp://sirdsite/var/www/html/m2repos
> remote.release.url=scp://sirdsite/var/www/html/m2repos/dst/release
> target.dir=target
> target.gensrc=target/generated-sources
> target.dist=target/dist
> target.classes=target/classes
> lib=lib
> src=src/main/java
> artifactOne=artifact1.jar
> artifactTwo=artifact2.jar
>
>
> When I execute this command, it seems to hang at reading my long-ish
> settings.xml
> [mykel@DHBHDTBLDCTRLAH ExampleAntMavenProject]$ ant -v
> Apache Ant version 1.6.5 compiled on June 2 2005
> Buildfile: build.xml
> Detected Java version: 1.5 in: /usr/java/jdk1.5.0_12/jre
> Detected OS: Linux
> parsing buildfile
> /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml with URI =
> file:///home/mykel/workspace-tutorial/ExampleAntMavenProject/build.xml
> Project base dir set to:
> /home/mykel/workspace-tutorial/ExampleAntMavenProject
> [property] Loading
> /home/mykel/workspace-tutorial/ExampleAntMavenProject/build.properties
> Build sequence for target(s) `all' is [init, maven-setup,
> resolve-dependencies, compile, package, install, all]
> Complete build sequence is [init, maven-setup, resolve-dependencies,
> compile, package, install, all, deploy-subordinate, deploy-release, clean,
> deploy-snapshot, ]
>
> init:
>
> maven-setup:
> [get] Getting:
> http://sirdsite/installs/maven-ant-tasks/maven-ant-tasks-2.0.7.jar
> [get] To:
> /home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> ant-tasks-2.0.7.jar
> [get] Not modified - so not downloaded
> parsing buildfile
> jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml with URI =
> jar:file:/home/mykel/workspace-tutorial/ExampleAntMavenProject/lib/maven-
> ant-tasks-2.0.7.jar!/org/apache/maven/artifact/ant/antlib.xml
> [echo] Installing Provider
> [artifact:install-provider] Using remote repositories:
> - id=central, url=http://repo1.maven.org/maven2, releases=enabled,
> snapshots=disabled
> [artifact:install-provider] Loading Maven settings file:
> /home/mykel/.m2/settings.xml
>
> ....and we wait.
>
> I cut the settings.xml down to just the bare minimum (the mirror setting
> for our proximity setup which keeps all the proxy/firewall issues away).
> No discernible effect.
>
> The wagon-provider is already installed in my local repo from various maven
> builds, so the need to d/l it seems off-kilter but this is an ant project
> so I dunno what's really supposed to happen here.
>
> Am I doing something wrong?
> MANTTASKS-6<http://jira.codehaus.org/browse/MANTTASKS-6>reports some
> element of this fixed, although that seems to be unrelated to
> an inability to read from my local settings file. I posted this same log
> as a comment to the fixed issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org