You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Gustavo Pinheiro <gu...@estatcamp.com.br> on 2004/01/21 14:49:33 UTC
Issues building Turbine with maven
Hello,
I get a load of errors when trying to build Turbine 2.3 using Maven.
First, I noticed that some Turbine classes had their names truncated. For
instance:
E:\jakarta-turbine-2.3\src\java\org\apache\turbine\services\assemblerbroker\
AssemblerBrok
I could figure out their names looking at compiling error. I downloaded them
from 3 different sources and they were all like this. I also used different
unpacking utilities (winace, gnu gzip and tar). Anyone noticed this?
Second, after fixing the issues mentioned, I kept getting errors. They were
all in ...services/schedule or ...services/security. I found out looking at
the sources and at maven.xml that some of the classes that should go in
those dirs had to be generated at build time by maven-torque-plugin. And
they were, but in a strange way. BaseJobEntry.java became
${basePrefix}JobEntry.java, for instance. So I figure it is something with
torque-plugin, which must be having trouble setting the var ${basePrefix},
but I couldn't find the place where ${basePrefix} and such are defined.
HELP, HELP, HELP!!!!
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: Issues building Turbine with maven
Posted by Eric Pugh <ep...@upstate.com>.
I understand the desire for fewer jars.. Unfortunantly, up through 2.2,
that was the approach, but it meant adding in more and more jars to support
more and more services. With 2.4, we will be able to have a stripped down
turbine build, and then if you need a specific service, then you add it into
yourself.
Additionally, while the TR.props will continue to remain for the foreseable
future, all the config will move to the ComponentConfiguration.xml, so you
will only have to look there to configure your component data...
ERic
> -----Original Message-----
> From: Gustavo Pinheiro [mailto:gustavo@estatcamp.com.br]
> Sent: Wednesday, January 21, 2004 6:06 PM
> To: 'Turbine Users List'; epugh@upstate.com
> Subject: RES: Issues building Turbine with maven
>
>
> Thanks for the tip, but I managed to build 2.3 alright. My production
> environment on the other hand...it seems that some of the
> jars are making my
> tomcat context invalid God knows why. It makes me wish
> Turbine development
> would have followed the opposite direction and instead of
> decoupling things,
> it could be heading for a unifying approach where there would be fewer
> external packages dependencies, fewer configuration files...
>
>
> -----Mensagem original-----
> De: Eric Pugh [mailto:epugh@upstate.com]
> Enviada em: Wednesday, January 21, 2004 2:53 PM
> Para: 'Turbine Users List'
> Assunto: RE: Issues building Turbine with maven
>
>
> Turbine 2.4 builds MUCH easier. All the Torque stuff is
> broken out into
> it's seperate build, so the build for the main Turbine tree
> is much cleaner.
>
>
> > -----Original Message-----
> > From: Loïc QUERAN [mailto:loic.queran@gicm.fr]
> > Sent: Wednesday, January 21, 2004 3:22 PM
> > To: Turbine Users List
> > Subject: Re: Issues building Turbine with maven
> >
> >
> > I had the same kind of problems a few weeks ago. I later
> installed the
> > latest maven version, erased my local repository and
> > everything was ok.
> >
> > Loïc
> >
> > Gustavo Pinheiro wrote:
> >
> > >Hello,
> > >
> > >I get a load of errors when trying to build Turbine 2.3
> using Maven.
> > >
> > >First, I noticed that some Turbine classes had their names
> > truncated. For
> > >instance:
> > >
> > >E:\jakarta-turbine-2.3\src\java\org\apache\turbine\services\a
> > ssemblerbroker\
> > >AssemblerBrok
> > >
> > >I could figure out their names looking at compiling error. I
> > downloaded them
> > >from 3 different sources and they were all like this. I also
> > used different
> > >unpacking utilities (winace, gnu gzip and tar). Anyone
> noticed this?
> > >
> > >Second, after fixing the issues mentioned, I kept getting
> > errors. They were
> > >all in ...services/schedule or ...services/security. I found
> > out looking at
> > >the sources and at maven.xml that some of the classes that
> > should go in
> > >those dirs had to be generated at build time by
> > maven-torque-plugin. And
> > >they were, but in a strange way. BaseJobEntry.java became
> > >${basePrefix}JobEntry.java, for instance. So I figure it is
> > something with
> > >torque-plugin, which must be having trouble setting the var
> > ${basePrefix},
> > >but I couldn't find the place where ${basePrefix} and such
> > are defined.
> > >
> > >
> > >HELP, HELP, HELP!!!!
> > >
> > >
> >
> >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail:
> turbine-user-help@jakarta.apache.org
> > >
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> turbine-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RES: Issues building Turbine with maven
Posted by Gustavo Pinheiro <gu...@estatcamp.com.br>.
Thanks for the tip, but I managed to build 2.3 alright. My production
environment on the other hand...it seems that some of the jars are making my
tomcat context invalid God knows why. It makes me wish Turbine development
would have followed the opposite direction and instead of decoupling things,
it could be heading for a unifying approach where there would be fewer
external packages dependencies, fewer configuration files...
-----Mensagem original-----
De: Eric Pugh [mailto:epugh@upstate.com]
Enviada em: Wednesday, January 21, 2004 2:53 PM
Para: 'Turbine Users List'
Assunto: RE: Issues building Turbine with maven
Turbine 2.4 builds MUCH easier. All the Torque stuff is broken out into
it's seperate build, so the build for the main Turbine tree is much cleaner.
> -----Original Message-----
> From: Loïc QUERAN [mailto:loic.queran@gicm.fr]
> Sent: Wednesday, January 21, 2004 3:22 PM
> To: Turbine Users List
> Subject: Re: Issues building Turbine with maven
>
>
> I had the same kind of problems a few weeks ago. I later installed the
> latest maven version, erased my local repository and
> everything was ok.
>
> Loïc
>
> Gustavo Pinheiro wrote:
>
> >Hello,
> >
> >I get a load of errors when trying to build Turbine 2.3 using Maven.
> >
> >First, I noticed that some Turbine classes had their names
> truncated. For
> >instance:
> >
> >E:\jakarta-turbine-2.3\src\java\org\apache\turbine\services\a
> ssemblerbroker\
> >AssemblerBrok
> >
> >I could figure out their names looking at compiling error. I
> downloaded them
> >from 3 different sources and they were all like this. I also
> used different
> >unpacking utilities (winace, gnu gzip and tar). Anyone noticed this?
> >
> >Second, after fixing the issues mentioned, I kept getting
> errors. They were
> >all in ...services/schedule or ...services/security. I found
> out looking at
> >the sources and at maven.xml that some of the classes that
> should go in
> >those dirs had to be generated at build time by
> maven-torque-plugin. And
> >they were, but in a strange way. BaseJobEntry.java became
> >${basePrefix}JobEntry.java, for instance. So I figure it is
> something with
> >torque-plugin, which must be having trouble setting the var
> ${basePrefix},
> >but I couldn't find the place where ${basePrefix} and such
> are defined.
> >
> >
> >HELP, HELP, HELP!!!!
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: Issues building Turbine with maven
Posted by Eric Pugh <ep...@upstate.com>.
Turbine 2.4 builds MUCH easier. All the Torque stuff is broken out into
it's seperate build, so the build for the main Turbine tree is much cleaner.
> -----Original Message-----
> From: Loïc QUERAN [mailto:loic.queran@gicm.fr]
> Sent: Wednesday, January 21, 2004 3:22 PM
> To: Turbine Users List
> Subject: Re: Issues building Turbine with maven
>
>
> I had the same kind of problems a few weeks ago. I later
> installed the
> latest maven version, erased my local repository and
> everything was ok.
>
> Loïc
>
> Gustavo Pinheiro wrote:
>
> >Hello,
> >
> >I get a load of errors when trying to build Turbine 2.3 using Maven.
> >
> >First, I noticed that some Turbine classes had their names
> truncated. For
> >instance:
> >
> >E:\jakarta-turbine-2.3\src\java\org\apache\turbine\services\a
> ssemblerbroker\
> >AssemblerBrok
> >
> >I could figure out their names looking at compiling error. I
> downloaded them
> >from 3 different sources and they were all like this. I also
> used different
> >unpacking utilities (winace, gnu gzip and tar). Anyone noticed this?
> >
> >Second, after fixing the issues mentioned, I kept getting
> errors. They were
> >all in ...services/schedule or ...services/security. I found
> out looking at
> >the sources and at maven.xml that some of the classes that
> should go in
> >those dirs had to be generated at build time by
> maven-torque-plugin. And
> >they were, but in a strange way. BaseJobEntry.java became
> >${basePrefix}JobEntry.java, for instance. So I figure it is
> something with
> >torque-plugin, which must be having trouble setting the var
> ${basePrefix},
> >but I couldn't find the place where ${basePrefix} and such
> are defined.
> >
> >
> >HELP, HELP, HELP!!!!
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Issues building Turbine with maven
Posted by Loïc QUERAN <lo...@gicm.fr>.
I had the same kind of problems a few weeks ago. I later installed the
latest maven version, erased my local repository and everything was ok.
Loïc
Gustavo Pinheiro wrote:
>Hello,
>
>I get a load of errors when trying to build Turbine 2.3 using Maven.
>
>First, I noticed that some Turbine classes had their names truncated. For
>instance:
>
>E:\jakarta-turbine-2.3\src\java\org\apache\turbine\services\assemblerbroker\
>AssemblerBrok
>
>I could figure out their names looking at compiling error. I downloaded them
>from 3 different sources and they were all like this. I also used different
>unpacking utilities (winace, gnu gzip and tar). Anyone noticed this?
>
>Second, after fixing the issues mentioned, I kept getting errors. They were
>all in ...services/schedule or ...services/security. I found out looking at
>the sources and at maven.xml that some of the classes that should go in
>those dirs had to be generated at build time by maven-torque-plugin. And
>they were, but in a strange way. BaseJobEntry.java became
>${basePrefix}JobEntry.java, for instance. So I figure it is something with
>torque-plugin, which must be having trouble setting the var ${basePrefix},
>but I couldn't find the place where ${basePrefix} and such are defined.
>
>
>HELP, HELP, HELP!!!!
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Issues building Turbine with maven
Posted by Jeff Painter <pa...@kiasoft.com>.
the basePrefix issues have been documented before.
http://marc.theaimsgroup.com/?l=turbine-user&m=107177483118989&w=2
I would start there and see if you continue to have build troubles
On Wed, 21 Jan 2004, Gustavo Pinheiro wrote:
> Hello,
>
> I get a load of errors when trying to build Turbine 2.3 using Maven.
>
> First, I noticed that some Turbine classes had their names truncated. For
> instance:
>
> E:\jakarta-turbine-2.3\src\java\org\apache\turbine\services\assemblerbroker\
> AssemblerBrok
>
> I could figure out their names looking at compiling error. I downloaded them
> from 3 different sources and they were all like this. I also used different
> unpacking utilities (winace, gnu gzip and tar). Anyone noticed this?
>
> Second, after fixing the issues mentioned, I kept getting errors. They were
> all in ...services/schedule or ...services/security. I found out looking at
> the sources and at maven.xml that some of the classes that should go in
> those dirs had to be generated at build time by maven-torque-plugin. And
> they were, but in a strange way. BaseJobEntry.java became
> ${basePrefix}JobEntry.java, for instance. So I figure it is something with
> torque-plugin, which must be having trouble setting the var ${basePrefix},
> but I couldn't find the place where ${basePrefix} and such are defined.
>
>
> HELP, HELP, HELP!!!!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
--
Regards,
Jeffery Painter
- --
painter@kiasoft.com http://kiasoft.com
PGP FP: 9CE8 83A2 33FA 32B1 0AB1 4E62 E4CB E4DA 5913 EFBC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/qEQE5Mvk2lkT77wRAnMJAJ9vJ6qOkg/mvqqIpz7troCEQJ8bFACglu/U
YNXabx7DZOV2Hd9LwSTmGpY=
=dWiu
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org