You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by kroekle <kr...@gmail.com> on 2009/07/15 07:52:32 UTC
IvyDE not attaching source/java doc
I think I have something wrong with my ivy.xml file. We are using the most
current releases of IvyDE & ivy (2.0.0.final & 2.1.0-rc1). According to
this post
(http://www.nabble.com/IvyDE---Is-it-possible-to-have-it-download-sources---javadocs--td22318492.html)
and attached JIRA I believe that the current version should work fine.
Our project ivy.xml file looks like this:
<?xml version="1.0" encoding="ISO-8859-1"?>
<ivy-module version="1.0">
<info
organisation="com.test"
module="test"
status="integration"
revision="integration">
</info>
<configurations>
<conf name="compile"/>
<conf name="provided"/>
<conf name="local" extends="compile"/>
<conf name="test" extends="compile"/>
<conf name="runlocal" extends="compile"/>
<conf name="rundev" extends="compile" />
<conf name="runprod" extends="compile"/>
</configurations>
<publications>
<artifact conf="compile"/>
</publications>
<dependencies>
<dependency org="org.apache.wicket" name="wicket-jmx" rev="1.4-rc6"
conf="compile->default"/>
</dependencies>
</ivy-module>
We have our own repository that we keep dependencies in and use the install
ant task to load it. The relevant parts of the ivy file for wicket-jmx
looks like this:
<ivy-module version="1.0" xmlns:m="http://ant.apache.org/ivy/maven">
<info organisation="org.apache.wicket"
module="wicket-jmx"
revision="1.4-rc6"
status="release"
publication="20090703102812"
namespace="maven2"
>
...
</info>
<configurations>
<conf name="default" visibility="public" description="runtime dependencies
and master artifact can be used with this conf" extends="runtime,master"/>
<conf name="master" visibility="public" description="contains only the
artifact published by this module itself, with no transitive dependencies"/>
<conf name="compile" visibility="public" description="this is the default
scope, used if none is specified. Compile dependencies are available in all
classpaths."/>
<conf name="provided" visibility="public" description="this is much like
compile, but indicates you expect the JDK or a container to provide it. It
is only available on the compilation classpath, and is not transitive."/>
<conf name="runtime" visibility="public" description="this scope indicates
that the dependency is not required for compilation, but is for execution.
It is in the runtime and test classpaths, but not the compile classpath."
extends="compile"/>
<conf name="test" visibility="private" description="this scope indicates
that the dependency is not required for normal use of the application, and
is only available for the test compilation and execution phases."
extends="runtime"/>
<conf name="system" visibility="public" description="this scope is similar
to provided except that you have to provide the JAR which contains it
explicitly. The artifact is always available and is not looked up in a
repository."/>
<conf name="sources" visibility="public" description="this configuration
contains the source artifact of this module, if any."/>
<conf name="javadoc" visibility="public" description="this configuration
contains the javadoc artifact of this module, if any."/>
<conf name="optional" visibility="public" description="contains all
optional dependencies"/>
</configurations>
<publications>
<artifact name="wicket-jmx" type="jar" ext="jar" conf="master"/>
<artifact name="wicket-jmx" type="source" ext="jar" conf="sources"
m:classifier="sources"/>
<artifact name="wicket-jmx" type="javadoc" ext="jar" conf="javadoc"
m:classifier="javadoc"/>
</publications>
<dependencies>
<dependency org="org.apache.wicket" name="wicket" rev="1.4-rc6"
force="true" conf="compile->compile(*),master(*);runtime->runtime(*)"/>
<dependency org="org.junit" name="junit" rev="3.8.1" force="true"
conf="provided->compile(*),provided(*),runtime(*),master(*)"/>
<dependency org="javax.servlet" name="servlet-api" rev="2.3" force="true"
conf="provided->compile(*),provided(*),runtime(*),master(*)"/>
<dependency org="org.slf4j" name="slf4j-api" rev="1.4.2" force="true"
conf="compile->compile(*),master(*);runtime->runtime(*)"/>
<dependency org="org.slf4j" name="slf4j-log4j12" rev="1.4.2" force="true"
conf="test->runtime(*),master(*)"/>
...
ton of overrides
...
</dependencies>
</ivy-module>
I am seeing the correct dependencies brought in, but no source/javadoc (yes,
they exist in our repo) for any of the dependencies.
I am also seeing the following messages in the ivy console:
[Eclipse Workspace resolver - skipping non-project artifact]
org.apache.wicket#wicket-jmx#775;1.4-rc6!wicket-jmx.jar(source)
[Eclipse Workspace resolver - skipping non-project artifact]
org.apache.wicket#wicket-jmx#775;1.4-rc6!wicket-jmx.jar(javadoc)
[Eclipse Workspace resolver - skipping non-project artifact]
org.apache.wicket#wicket#775;1.4-rc6!wicket.jar(source)
[Eclipse Workspace resolver - skipping non-project artifact]
org.apache.wicket#wicket#775;1.4-rc6!wicket.jar(javadoc)
I also checked my local cache and the source & javadoc is not being
downloaded to my machine.
Any suggestions would be greatly appreciated.
--
View this message in context: http://www.nabble.com/IvyDE-not-attaching-source-java-doc-tp24492331p24492331.html
Sent from the ivy-user mailing list archive at Nabble.com.
Re: IvyDE not attaching source/java doc
Posted by kroekle <kr...@gmail.com>.
https://issues.apache.org/jira/browse/IVYDE-192
--
View this message in context: http://www.nabble.com/IvyDE-not-attaching-source-java-doc-tp24492331p24619463.html
Sent from the ivy-user mailing list archive at Nabble.com.
Re: IvyDE not attaching source/java doc
Posted by stephenh <st...@exigencecorp.com>.
Nicolas Lalevée wrote:
>
> Then it is weird to see "Eclipse Workspace resolver" trying to
> download javadocs and sources. Could open a bug in jira please.
> As a work around try to disable the workspace resolver.
>
FWIW, I'm seeing this behavior too. Same versions. Sources aren't attached
when using workspace resolution (which is very handy, btw), but if I disable
workspace resolution then sources for dependencies work great.
Thanks,
Stephen
--
View this message in context: http://www.nabble.com/IvyDE-not-attaching-source-java-doc-tp24492331p24612618.html
Sent from the ivy-user mailing list archive at Nabble.com.
Re: IvyDE not attaching source/java doc
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 15 juil. 09 à 07:52, kroekle a écrit :
>
> I think I have something wrong with my ivy.xml file. We are using
> the most
> current releases of IvyDE & ivy (2.0.0.final & 2.1.0-rc1).
> According to
> this post
> (http://www.nabble.com/IvyDE---Is-it-possible-to-have-it-download-sources---javadocs--td22318492.html
> )
> and attached JIRA I believe that the current version should work fine.
>
> Our project ivy.xml file looks like this:
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <ivy-module version="1.0">
> <info
> organisation="com.test"
> module="test"
> status="integration"
> revision="integration">
> </info>
> <configurations>
> <conf name="compile"/>
> <conf name="provided"/>
> <conf name="local" extends="compile"/>
> <conf name="test" extends="compile"/>
> <conf name="runlocal" extends="compile"/>
> <conf name="rundev" extends="compile" />
> <conf name="runprod" extends="compile"/>
> </configurations>
> <publications>
> <artifact conf="compile"/>
> </publications>
> <dependencies>
> <dependency org="org.apache.wicket" name="wicket-jmx" rev="1.4-rc6"
> conf="compile->default"/>
> </dependencies>
> </ivy-module>
>
> We have our own repository that we keep dependencies in and use the
> install
> ant task to load it. The relevant parts of the ivy file for wicket-
> jmx
> looks like this:
>
> <ivy-module version="1.0" xmlns:m="http://ant.apache.org/ivy/maven">
> <info organisation="org.apache.wicket"
> module="wicket-jmx"
> revision="1.4-rc6"
> status="release"
> publication="20090703102812"
> namespace="maven2"
> >
> ...
> </info>
> <configurations>
> <conf name="default" visibility="public" description="runtime
> dependencies
> and master artifact can be used with this conf"
> extends="runtime,master"/>
> <conf name="master" visibility="public" description="contains only
> the
> artifact published by this module itself, with no transitive
> dependencies"/>
> <conf name="compile" visibility="public" description="this is the
> default
> scope, used if none is specified. Compile dependencies are available
> in all
> classpaths."/>
> <conf name="provided" visibility="public" description="this is
> much like
> compile, but indicates you expect the JDK or a container to provide
> it. It
> is only available on the compilation classpath, and is not
> transitive."/>
> <conf name="runtime" visibility="public" description="this scope
> indicates
> that the dependency is not required for compilation, but is for
> execution.
> It is in the runtime and test classpaths, but not the compile
> classpath."
> extends="compile"/>
> <conf name="test" visibility="private" description="this scope
> indicates
> that the dependency is not required for normal use of the
> application, and
> is only available for the test compilation and execution phases."
> extends="runtime"/>
> <conf name="system" visibility="public" description="this scope is
> similar
> to provided except that you have to provide the JAR which contains it
> explicitly. The artifact is always available and is not looked up in a
> repository."/>
> <conf name="sources" visibility="public" description="this
> configuration
> contains the source artifact of this module, if any."/>
> <conf name="javadoc" visibility="public" description="this
> configuration
> contains the javadoc artifact of this module, if any."/>
> <conf name="optional" visibility="public" description="contains all
> optional dependencies"/>
> </configurations>
> <publications>
> <artifact name="wicket-jmx" type="jar" ext="jar" conf="master"/>
> <artifact name="wicket-jmx" type="source" ext="jar" conf="sources"
> m:classifier="sources"/>
> <artifact name="wicket-jmx" type="javadoc" ext="jar" conf="javadoc"
> m:classifier="javadoc"/>
> </publications>
> <dependencies>
> <dependency org="org.apache.wicket" name="wicket" rev="1.4-rc6"
> force="true" conf="compile->compile(*),master(*);runtime-
> >runtime(*)"/>
> <dependency org="org.junit" name="junit" rev="3.8.1" force="true"
> conf="provided->compile(*),provided(*),runtime(*),master(*)"/>
> <dependency org="javax.servlet" name="servlet-api" rev="2.3"
> force="true"
> conf="provided->compile(*),provided(*),runtime(*),master(*)"/>
> <dependency org="org.slf4j" name="slf4j-api" rev="1.4.2"
> force="true"
> conf="compile->compile(*),master(*);runtime->runtime(*)"/>
> <dependency org="org.slf4j" name="slf4j-log4j12" rev="1.4.2"
> force="true"
> conf="test->runtime(*),master(*)"/>
> ...
> ton of overrides
> ...
> </dependencies>
> </ivy-module>
>
> I am seeing the correct dependencies brought in, but no source/
> javadoc (yes,
> they exist in our repo) for any of the dependencies.
>
> I am also seeing the following messages in the ivy console:
>
> [Eclipse Workspace resolver - skipping non-project artifact]
> org.apache.wicket#wicket-jmx#775;1.4-rc6!wicket-jmx.jar(source)
> [Eclipse Workspace resolver - skipping non-project artifact]
> org.apache.wicket#wicket-jmx#775;1.4-rc6!wicket-jmx.jar(javadoc)
> [Eclipse Workspace resolver - skipping non-project artifact]
> org.apache.wicket#wicket#775;1.4-rc6!wicket.jar(source)
> [Eclipse Workspace resolver - skipping non-project artifact]
> org.apache.wicket#wicket#775;1.4-rc6!wicket.jar(javadoc)
>
> I also checked my local cache and the source & javadoc is not being
> downloaded to my machine.
>
> Any suggestions would be greatly appreciated.
From your log I assume you are using the workspace resolver in your
project. I also assume that you don't have that wicket-jmx project in
your workspace as you expect to have javadoc attached to its jar in
IvyDE's classpath container.
Then it is weird to see "Eclipse Workspace resolver" trying to
download javadocs and sources. Could open a bug in jira please.
As a work around try to disable the workspace resolver.
Nicolas
> --
> View this message in context: http://www.nabble.com/IvyDE-not-attaching-source-java-doc-tp24492331p24492331.html
> Sent from the ivy-user mailing list archive at Nabble.com.
>