Glen,

Could it be that you have v3.0.0 POM(s) for some of the XDoclet
dependencies left over from some of your previous tries? I am almost
certain that your xdoclet POM in your local repo is a v3.0 POM, since
that is the case when I was having problems with not having
nanocontainer/picocontainer JARs in the classpath when the plugin was
run.  I'd delete the xdoclet, xdoclet-plugin, generama, etc. dirs from
 the repo, and try again.  Your repo setup is what I have as well.

Shash

On 2/5/06, Glen <[EMAIL PROTECTED]> wrote:
> Thanks for the help...  Unfortunately I am still getting the same error...
>
> Attached is my POM.  Note it reflects my last attempt at having a
> default and legacy layout repo and plugin repo...
>
>
>
> Grégory Joseph wrote:
> > Glen,
> >
> >
> >>That was it I was missing the <layout>legacy</layout> tag for my
> >>repository.
> >
> >
> > No were not missing that tag for the existing repository you'd
> > declared. To try and put it more clearly this time, you need to
> > declare the same repo *two times*, once with layout:default and once
> > with layout:legacy.
> >
> > The thing is the m2 plugin of xd2 is obviously deployed with m2, so
> > it's stored using the m2 repository layout, while the xd2 plugins
> > themselves are still built and deployed with m1, hence they're stored
> > in a "legacy" layout. I hope this makes the error messages you got
> > clearer now.
> >
> > ... but I'm surprised, as I thought the m2 plugin's repositories would
> > be used, so I'm not sure you need to declare the legacy once
> > yourself... Could you send me your complete pom? Are you really
> > declaring the dependency on the xdoclet-hibernate-plugin you use *in*
> > the build/plugins/plugin/dependencies section, or in your project's
> > main dependencies ?
> >
> > Cheers
> >
> > g
>
>
>
>

Reply via email to