You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Anton Bakanovsky <An...@gemini-systems.ru> on 2012/04/10 15:26:16 UTC

ODE 1.4 building

Hi!

I've tried to build ODE 1.4. from trunk and met some problem.
It is more convenient for me to build ODE by maven then Apache Buildr. But 
maven cannot find some dependencies (artifactId: ode-dao-hibernate) as 
xjavadoc-1.1-j5.
So, will it be right to change  xdoclet-maven-plugin to 
maven2-xdoclet2-plugin? Because maven2-xdoclet2-plugin exits in central 
maven repository.


I can send changes for pom.xml and java classes adopted for 
maven2-xdoclet2-plugin.

Re: ODE 1.4 building

Posted by Tammo van Lessen <tv...@gmail.com>.
Hi Anton,

Buildr is the primary build system. When using it in conjunction with
JRuby it works flawlessly for me.

You could try the following dependency, which is closer to 1.1 (I don't
know about the differences between xdoclet 1.x and 2.0) and which is in
the repository.

 <dependency>
    <groupId>xdoclet</groupId>
    <artifactId>xdoclet-xjavadoc</artifactId>
    <version>1.2b2</version>
 </dependency>

Also, there are a couple of non-central repositories that mirror this
artifact, e.g.
http://people.apache.org/~rr/saxon-repo/xdoclet/xjavadoc/1.1-j5/ So it
is probably easier to just fetch it from there.

HTH,
  Tammo

On 10.04.2012 15:26, Anton Bakanovsky wrote:
> Hi!
> 
> I've tried to build ODE 1.4. from trunk and met some problem.
> It is more convenient for me to build ODE by maven then Apache Buildr. But 
> maven cannot find some dependencies (artifactId: ode-dao-hibernate) as 
> xjavadoc-1.1-j5.
> So, will it be right to change  xdoclet-maven-plugin to 
> maven2-xdoclet2-plugin? Because maven2-xdoclet2-plugin exits in central 
> maven repository.
> 
> 
> I can send changes for pom.xml and java classes adopted for 
> maven2-xdoclet2-plugin.

-- 
Tammo van Lessen - http://www.taval.de