Randy, Adam, Kevin!
Any info on this?
We are now at 95% but I personally would prefer to have the
openjpa-maven-plugin just working out of the box for (almost) all situations.
But I need your input what is still missing...
txs and LieGrue,
strub
--- Mark Struberg <strub...@yahoo.de> schrieb am Mo, 9.3.2009:
> Von: Mark Struberg <strub...@yahoo.de>
> Betreff: Re: OpenJPA Maven Plugin
> An: users@openjpa.apache.org
> Datum: Montag, 9. März 2009, 17:50
>
> Hi!
>
> I'm back from skiing and catching up the current status.
>
> So imho the following things are due to be done:
>
> 1.) add a config property to specify a specific
> persistence.xml location and name.
>
> 2.) add a config property to specify one specific
> PersistenceUnit in the persistence.xml from 1.)
>
> 3.) add a way to also resolve the test scope dependencies.
> Please note that simply adding the test classpath in
> target/test-classes may be not enough since there may be
> missing dependencies left open in this case.
>
> All those functions should get implemented for
> openjpa:enhance, openjpa:sql and openjpa:schema. I already
> know the property for the PCEnhancer but what about the
> respective parameters for the
> org.apache.openjpa.jdbc.meta.MappingTool?
>
>
> txs and LieGrue,
> strub
>
>
> --- Randy Watler <wat...@wispertel.net>
> schrieb am Mi, 4.3.2009:
>
> > Von: Randy Watler <wat...@wispertel.net>
> > Betreff: Re: OpenJPA Maven Plugin
> > An: users@openjpa.apache.org
> > Datum: Mittwoch, 4. März 2009, 18:32
> > Sorry... I meant Mark!
> >
> > Mark, let me know if you want me to submit a patch.
> >
> > Randy
> >
> > Randy Watler wrote:
> > > Adam,
> > >
> > > After rereading Matt's question and your
> original
> > problem report, I believe you are asking how to get
> the
> > target/test-classes directory within a single project
> added
> > to the class path used to invoke the enhancer. By
> default,
> > the existing target/classes directory is included, but
> not
> > target/test-classes.
> > >
> > > I believe that we could add a new tag/mojo list
> member
> > called "additionalClasspathElements". AFAICT, that is
> the
> > conventional approach to this. We could also add a
> mojo
> > member for testClasspathElements and use those if
> > available... i.e. in the process-test-classes phase.
> > >
> > > Matt... do you want me to submit a patch with
> either
> > change, or do you want to handle this?
> > >
> > > Randy
> > >
> > > Randy Watler wrote:
> > >> Adam,
> > >>
> > >> I stand corrected. Let me take a look for
> you.
> > >>
> > >> Randy
> > >>
> > >> Adam Hardy wrote:
> > >>> Randy Watler on 04/03/09 14:28, wrote:
> > >>>> Just to clarify.... this is also
> using
> > version 1.0 of the plugin? I dont think
> <classes> is
> > supported if so. Did you try this?
> > >>>>
> > >>>>
> >
> <includes>${build.testOutputDirectory}/org/permacode/atomic/domain/entity/*.class</includes>
> >
> > >>>>
> > >>>> Just checking before I diagnose for
> you,
> > >>>
> > >>> Yes, I mean 1.1-SNAPSHOT actually.
> > >>>
> > >>> Is this not the correct documentation?
> > >>>
> > >>> http://mojo.codehaus.org/openjpa-maven-plugin/enhance-mojo.html
> > >>>
> > >>>
> > >>
> > >>
> > >
> > >
> >
> >
>
>
>
>
