Ahh, I figured it out. Besides the need for xdoclet-hibernate-module I also need xdoclet and xjavadoc
dependency.


Which, leads me to another question. How do you specify dependency on the whole package
rather than a jar file.


Suppose I use a pcakge that has its own dependencies. Package I use say A (version 1.0). A contains
a-1.0.jar and depends on package B (version 2.0). B contains b-2.0.jar


Suppose now depvelopers of A decide to release A (version 2.0), that is dependent on B (version 3.0)

If I want to try version 2.0 of A on my projet. I would need to know that A developers now depend
on version 3.0 of B pacakge.


It seems a bit awkward to chase the dependencies. I was wondering how would I depend on package
rather than jar files?


Thanks,
Alex.

Aleksandr Shneyderman wrote:



<dependency>
    <artifactId>xdoclet-hibernate-module</artifactId>
    <groupId>xdoclet</groupId>
    <version>1.2b4</version>
    <type>jar</type>
</dependency>

I have:

   <dependencies>
          <dependency>
              <id>xdoclet+hibernate-module</id>
              <version>1.2</version>
       </dependency>
   </dependencies>

I am not quite sure what this means exactly, but I snaged it from some other script and thought it would do the trick.
I tried your suggestion (except 1.2b4 - I have 1.2) but it did not help, I have the same error.


Thakns,
Alex.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to