You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Alex Shneyderman <al...@law.columbia.edu> on 2004/01/04 00:43:24 UTC
Dependencies question.
I am new to maven and was going thru the User's Guide, that puzzled me a
bit.
I am not sure how to define dependence on a package as a whole.
Documentation
says that dependence element is constructed by the following pattern:
${repo}/${groupId}/${type}s/${artifactId}-${version}.${type}
Suppose, I am developing a project and I use hibernate to help out
with persistence. Hibernate is versioned and has multiple jars
in its package. Ideally I would only want to say that my project
depends on hibernate version so and so, and not list every single
jar of hibernate as dependence of my project. From what it looks like
from the docs and by trying it is impossible to rely on a versioned
package, or am I missing something? In addition what if the future
versions of hiberante will change the set of jars? It would be a real
pain to switch between versions. Some project are relased every two
weeks or so, for me this means I would have to potentially change or
at least revise my dependencies every two weeks.
If I can somehow rely on the whole package then how would I declare
the exact version of the package that I rely on, since version is
not specified on groupId (I take it as my package identifier) level
but rather on artifactId?
Your suggestions and answers would be greatly appreciated!
Thanks,
Alex.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: XDoclet plugin strange behavior
Posted by Kevin Hagel <kh...@mminternet.com>.
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-673
I filed this back in october, still unresolved.
Are you building from source? The maven plugin source still uses the old
style, which has NEVER worked since I first started building XDoclet about 6
months ago. I changed the /blah/XDocletsource/maven/project.xml file to
contain the following
<dependency>
<id>xdoclet+xdoclet-module</id>
<version>@XDOCLET_VERSION@</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xjavadoc</artifactId>
<version>@XJAVADOC_VERSION@</version>
</dependency>
Without this fix XDoclet's maven plugin will not load.
----- Original Message -----
From: "__matthewHawthorne" <ma...@apache.org>
To: "Maven Users List" <us...@maven.apache.org>
Sent: Sunday, January 04, 2004 10:55 AM
Subject: Re: XDoclet plugin strange behavior
> A week or so ago, I filed this as a bug with the Xdoclet team. The
> plugin looks for the xjavadoc plugin with the groupId "xjavadoc" instead
> of "xdoclet". I haven't heard anything back.
>
> The frustrating part is that the only way I was able to figure out the
> error was by looking at the plugin's project.xml.
>
> To fix it, you must either put the jar into <repo>/xjavadoc/jars or use
> the jar override feature and put it wherever you want. I requested that
> the xjavadoc jar be put into its own directory (not the xdoclet dir) on
> ibiblio, but the request was denied.
>
>
> Aleksandr Shneyderman wrote:
> > Konstantin Priblouda wrote:
> >
> >> Well, if yoyu use gourpid, you have to call your
> >> xjavadoc xdoclet-xjavadoc.whatever.jar
> >>
> >
> > According to the documentation the files are located according to the
> > following pattern:
> >
> > ${repo}/${groupId}/${type}s/${artifactId}-${version}.${type}
> >
> > So if my dependency looks something like the following:
> > <dependency>
> > <artifactId>xjavadoc</artifactId>
> > <groupId>xdoclet</groupId>
> > <version>1.0.2</version>
> > <type>jar</type>
> > </dependency>
> >
> > Should not I expcet maven to find the jar if the file at location
> > ${repo}/xdoclet/jars/xjavadoc-1.0.2.jar does exists?
> >
> > Thanks,
> > Alex.
>
>
> ---------------------------------------------------------------------
> 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: XDoclet plugin strange behavior
Posted by __matthewHawthorne <ma...@apache.org>.
A week or so ago, I filed this as a bug with the Xdoclet team. The
plugin looks for the xjavadoc plugin with the groupId "xjavadoc" instead
of "xdoclet". I haven't heard anything back.
The frustrating part is that the only way I was able to figure out the
error was by looking at the plugin's project.xml.
To fix it, you must either put the jar into <repo>/xjavadoc/jars or use
the jar override feature and put it wherever you want. I requested that
the xjavadoc jar be put into its own directory (not the xdoclet dir) on
ibiblio, but the request was denied.
Aleksandr Shneyderman wrote:
> Konstantin Priblouda wrote:
>
>> Well, if yoyu use gourpid, you have to call your
>> xjavadoc xdoclet-xjavadoc.whatever.jar
>>
>
> According to the documentation the files are located according to the
> following pattern:
>
> ${repo}/${groupId}/${type}s/${artifactId}-${version}.${type}
>
> So if my dependency looks something like the following:
> <dependency>
> <artifactId>xjavadoc</artifactId>
> <groupId>xdoclet</groupId>
> <version>1.0.2</version>
> <type>jar</type>
> </dependency>
>
> Should not I expcet maven to find the jar if the file at location
> ${repo}/xdoclet/jars/xjavadoc-1.0.2.jar does exists?
>
> Thanks,
> Alex.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: XDoclet plugin strange behavior
Posted by Aleksandr Shneyderman <al...@law.columbia.edu>.
Konstantin Priblouda wrote:
>Well, if yoyu use gourpid, you have to call your
>xjavadoc
>xdoclet-xjavadoc.whatever.jar
>
According to the documentation the files are located according to the
following pattern:
${repo}/${groupId}/${type}s/${artifactId}-${version}.${type}
So if my dependency looks something like the following:
<dependency>
<artifactId>xjavadoc</artifactId>
<groupId>xdoclet</groupId>
<version>1.0.2</version>
<type>jar</type>
</dependency>
Should not I expcet maven to find the jar if the file at location
${repo}/xdoclet/jars/xjavadoc-1.0.2.jar does exists?
Thanks,
Alex.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: XDoclet plugin strange behavior
Posted by Konstantin Priblouda <kp...@yahoo.com>.
--- Aleksandr Shneyderman <al...@law.columbia.edu>
wrote:
> As you have probably noticed for the last couple of
> days I was
> struggling with XDoclet plugin.
> What I did is I downloaded their 1.2 version,
> created xdoclet/jars
> directory in my local repository,
> copied over the jars that come with the xdoclet. I
> then copied xdoclet's
> maven-plugin jar to my plugins
> directory.
Well, if yoyu use gourpid, you have to call your
xjavadoc
xdoclet-xjavadoc.whatever.jar
If you do not use groupid, you shall place it in
<maven repo>/xjavadoc/jars/
regards,
=====
----[ Konstantin Pribluda ( ko5tik ) ]----------------
Zu Verst�rkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] f�r die Festanstellung.
Arbeitsort: Mainz
Skills: Programieren, Kentnisse in OpenSource-Bereich
----[ http://www.pribluda.de ]------------------------
__________________________________
Do you Yahoo!?
Find out what made the Top Yahoo! Searches of 2003
http://search.yahoo.com/top2003
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
XDoclet plugin strange behavior
Posted by Aleksandr Shneyderman <al...@law.columbia.edu>.
As you have probably noticed for the last couple of days I was
struggling with XDoclet plugin.
What I did is I downloaded their 1.2 version, created xdoclet/jars
directory in my local repository,
copied over the jars that come with the xdoclet. I then copied xdoclet's
maven-plugin jar to my plugins
directory.
I created project.xml and maven.xml (they are both pasted at the end of
this message). The problem
I am having has something to do with the xjavadoc dependency. Right now
xjavadoc-1.0.2.jar is
in my ${maven.repo.local}/xdoclet/jars/ directory and when I run maven I
am getting an error saying
that xjavadoc-1.0.2 can not be resolved. When I move the jar to
${maven.repo.local}/xjavadoc/jars/
directory I am able to build nicely. Basically it is no big deal I just
hate to keep xjavadoc separately
from xdoclet. Does anyone know where I might need to start looking, to
fix this?
my project.xml
<project default="java:compile">
<id>gls-model</id>
<currentVersion>1.0</currentVersion>
<build>
<sourceDirectory>
${basedir}/src/java
</sourceDirectory>
</build>
<dependencies>
<dependency>
<artifactId>xdoclet-hibernate-module</artifactId>
<groupId>xdoclet</groupId>
<version>1.2</version>
<type>jar</type>
</dependency>
<dependency>
<artifactId>xdoclet</artifactId>
<groupId>xdoclet</groupId>
<version>1.2</version>
<type>jar</type>
</dependency>
<dependency>
<artifactId>xjavadoc</artifactId>
<groupId>xdoclet</groupId>
<version>1.0.2</version>
<type>jar</type>
</dependency>
</dependencies>
</project>
my maven.xml:
<project default="java:compile">
<preGoal name="java:compile">
<attainGoal name="xdoclet:hibernatedoclet"/>
</preGoal>
</project>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Dependencies question.
Posted by Jason van Zyl <jv...@maven.org>.
On Sat, 2004-01-03 at 18:43, Alex Shneyderman wrote:
> I am new to maven and was going thru the User's Guide, that puzzled me a
> bit.
> I am not sure how to define dependence on a package as a whole.
> Documentation
> says that dependence element is constructed by the following pattern:
>
> ${repo}/${groupId}/${type}s/${artifactId}-${version}.${type}
>
> Suppose, I am developing a project and I use hibernate to help out
> with persistence. Hibernate is versioned and has multiple jars
> in its package. Ideally I would only want to say that my project
> depends on hibernate version so and so, and not list every single
> jar of hibernate as dependence of my project. From what it looks like
> from the docs and by trying it is impossible to rely on a versioned
> package, or am I missing something?
Maven doesn't handle transitive dependencies yet but it's planned,
currently you will have to list each of the hibernate JARs. We're aware
of the problem.
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org