You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by Thomas Vandahl <tv...@apache.org> on 2007/10/13 16:35:59 UTC
Re: torque 3.3 schedule
Thomas Fischer wrote:
> how do you plan to integrate village anyway ? Into the runtime or as
> separate jar ? (Personally I'd prefer a separate jar.)
My preference was to integrate it directly into the runtime jar with the
option of building it as a separate artifact, if someone so desires.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: torque 3.3 schedule
Posted by Jeffrey Brekke <ek...@gmail.com>.
I agree on waiting until after 3.3. We've successfully had m2 deploy
to m1 repos. We do it internally at work...
On 10/17/07, Thomas Fischer <fi...@seitenbau.net> wrote:
> I'd think twice before switching the build process now to m2. The
> "official", tested, proven build is still the m1 build. I do believe that
> the m2 build produces correct jars but I'm not so sure about testing, site
> etc.
> I agree wholeheartedly that we should tackle this after 3.3 but I'd rather
> not touch this now. Building a release is complicated enough.
>
> Also, I'm not sure whether m2 can deploy in a m1 repo (never done this
> before). This will need some research.
>
> I'd leave this to Thomas V to decide (he has all the hassle building the
> stuff) but personally I'd get 3.3 out of the door and clean up afterwards.
>
> Thomas
>
> "Jeffrey Brekke" <ek...@gmail.com> schrieb am 17.10.2007 17:17:44:
>
> > Eeeww. m2 can obtain artifacts from an m1 repo, but I think the
> > issues come into deployment of the m2 plugin into/from an m1 repo (
> > and maybe vice-versa ). If the plugins are separate projects,
> > installed into their respective repos, shouldn't the non-plugin
> > artifacts (jars) just be deployed into one place with once
> > group/artifactid? Even if this is a m1 repo? Then we could just use
> > an m2 build for everything but the m1 plugin?
> >
> > On 10/17/07, Thomas Fischer <fi...@seitenbau.net> wrote:
> > > a) we cannot use a m2 build only because the m1 plurgin needs an m1
> build.
> > > And we cannot use a m1 build only because the m2 plugin needs a m2
> build.
> > > So we have to use two types of repository at the moment and we cannot
> do
> > > anything against it.
> > > b) The m1:org.apache.torque is the long term goal. I'd not switch the
> group
> > > id in an rc. Also, having the two goup ids separates the two builds:
> group
> > > id "torque" are the m1 built files, group id "org.apache.torque" are
> the m2
> > > built files. So I'd prefer to keept he the m1:torque,
> > > m2:org.apache.torque solution for 3.3. This does not mean I'm -1 on the
> > > other solution, it is just my personal preference.
> > >
> > > Thomas
> > >
> > > Thomas Vandahl <tv...@apache.org> schrieb am 16.10.2007 22:24:52:
> > >
> > > > Thomas Fischer wrote:
> > > > >> - I'd propose to put the resulting jar into the Maven repository
> in
> > > the
> > > > >> "torque" group or "org.apache.torque" respectively. What do
> others
> > > > >> say?
> > > > >
> > > > > m1:torque, m2:org.apache.torque is good.
> > > >
> > > > The repository people are bugging everybody to settle on one type of
> > > > repository only. Shouldn't we try to use one group only for Torque? I
> > > > propose to deploy the artifacts to the m2-repo only and use
> > > > 'org.apache.torque' for this. Would that create big obstacles for the
> > > > two maven plugins?
> > > >
> > > > Bye, Thomas.
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> > > > For additional commands, e-mail: torque-dev-help@db.apache.org
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> > > For additional commands, e-mail: torque-dev-help@db.apache.org
> > >
> >
> >
> > --
> > Jeffrey D. Brekke
> > Wisconsin, USA
> >
> > brekke at apache dot org
> > ekkerbj at gmail dot com
> > jbrekke at wi dot rr dot com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-dev-help@db.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
--
Jeffrey D. Brekke
Wisconsin, USA
brekke at apache dot org
ekkerbj at gmail dot com
jbrekke at wi dot rr dot com
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: torque 3.3 schedule
Posted by Thomas Fischer <fi...@seitenbau.net>.
I'd think twice before switching the build process now to m2. The
"official", tested, proven build is still the m1 build. I do believe that
the m2 build produces correct jars but I'm not so sure about testing, site
etc.
I agree wholeheartedly that we should tackle this after 3.3 but I'd rather
not touch this now. Building a release is complicated enough.
Also, I'm not sure whether m2 can deploy in a m1 repo (never done this
before). This will need some research.
I'd leave this to Thomas V to decide (he has all the hassle building the
stuff) but personally I'd get 3.3 out of the door and clean up afterwards.
Thomas
"Jeffrey Brekke" <ek...@gmail.com> schrieb am 17.10.2007 17:17:44:
> Eeeww. m2 can obtain artifacts from an m1 repo, but I think the
> issues come into deployment of the m2 plugin into/from an m1 repo (
> and maybe vice-versa ). If the plugins are separate projects,
> installed into their respective repos, shouldn't the non-plugin
> artifacts (jars) just be deployed into one place with once
> group/artifactid? Even if this is a m1 repo? Then we could just use
> an m2 build for everything but the m1 plugin?
>
> On 10/17/07, Thomas Fischer <fi...@seitenbau.net> wrote:
> > a) we cannot use a m2 build only because the m1 plurgin needs an m1
build.
> > And we cannot use a m1 build only because the m2 plugin needs a m2
build.
> > So we have to use two types of repository at the moment and we cannot
do
> > anything against it.
> > b) The m1:org.apache.torque is the long term goal. I'd not switch the
group
> > id in an rc. Also, having the two goup ids separates the two builds:
group
> > id "torque" are the m1 built files, group id "org.apache.torque" are
the m2
> > built files. So I'd prefer to keept he the m1:torque,
> > m2:org.apache.torque solution for 3.3. This does not mean I'm -1 on the
> > other solution, it is just my personal preference.
> >
> > Thomas
> >
> > Thomas Vandahl <tv...@apache.org> schrieb am 16.10.2007 22:24:52:
> >
> > > Thomas Fischer wrote:
> > > >> - I'd propose to put the resulting jar into the Maven repository
in
> > the
> > > >> "torque" group or "org.apache.torque" respectively. What do
others
> > > >> say?
> > > >
> > > > m1:torque, m2:org.apache.torque is good.
> > >
> > > The repository people are bugging everybody to settle on one type of
> > > repository only. Shouldn't we try to use one group only for Torque? I
> > > propose to deploy the artifacts to the m2-repo only and use
> > > 'org.apache.torque' for this. Would that create big obstacles for the
> > > two maven plugins?
> > >
> > > Bye, Thomas.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> > > For additional commands, e-mail: torque-dev-help@db.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-dev-help@db.apache.org
> >
>
>
> --
> Jeffrey D. Brekke
> Wisconsin, USA
>
> brekke at apache dot org
> ekkerbj at gmail dot com
> jbrekke at wi dot rr dot com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: torque 3.3 schedule
Posted by Jeffrey Brekke <ek...@gmail.com>.
Eeeww. m2 can obtain artifacts from an m1 repo, but I think the
issues come into deployment of the m2 plugin into/from an m1 repo (
and maybe vice-versa ). If the plugins are separate projects,
installed into their respective repos, shouldn't the non-plugin
artifacts (jars) just be deployed into one place with once
group/artifactid? Even if this is a m1 repo? Then we could just use
an m2 build for everything but the m1 plugin?
On 10/17/07, Thomas Fischer <fi...@seitenbau.net> wrote:
> a) we cannot use a m2 build only because the m1 plurgin needs an m1 build.
> And we cannot use a m1 build only because the m2 plugin needs a m2 build.
> So we have to use two types of repository at the moment and we cannot do
> anything against it.
> b) The m1:org.apache.torque is the long term goal. I'd not switch the group
> id in an rc. Also, having the two goup ids separates the two builds: group
> id "torque" are the m1 built files, group id "org.apache.torque" are the m2
> built files. So I'd prefer to keept he the m1:torque,
> m2:org.apache.torque solution for 3.3. This does not mean I'm -1 on the
> other solution, it is just my personal preference.
>
> Thomas
>
> Thomas Vandahl <tv...@apache.org> schrieb am 16.10.2007 22:24:52:
>
> > Thomas Fischer wrote:
> > >> - I'd propose to put the resulting jar into the Maven repository in
> the
> > >> "torque" group or "org.apache.torque" respectively. What do others
> > >> say?
> > >
> > > m1:torque, m2:org.apache.torque is good.
> >
> > The repository people are bugging everybody to settle on one type of
> > repository only. Shouldn't we try to use one group only for Torque? I
> > propose to deploy the artifacts to the m2-repo only and use
> > 'org.apache.torque' for this. Would that create big obstacles for the
> > two maven plugins?
> >
> > Bye, Thomas.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-dev-help@db.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
--
Jeffrey D. Brekke
Wisconsin, USA
brekke at apache dot org
ekkerbj at gmail dot com
jbrekke at wi dot rr dot com
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: torque 3.3 schedule
Posted by Thomas Fischer <fi...@seitenbau.net>.
a) we cannot use a m2 build only because the m1 plurgin needs an m1 build.
And we cannot use a m1 build only because the m2 plugin needs a m2 build.
So we have to use two types of repository at the moment and we cannot do
anything against it.
b) The m1:org.apache.torque is the long term goal. I'd not switch the group
id in an rc. Also, having the two goup ids separates the two builds: group
id "torque" are the m1 built files, group id "org.apache.torque" are the m2
built files. So I'd prefer to keept he the m1:torque,
m2:org.apache.torque solution for 3.3. This does not mean I'm -1 on the
other solution, it is just my personal preference.
Thomas
Thomas Vandahl <tv...@apache.org> schrieb am 16.10.2007 22:24:52:
> Thomas Fischer wrote:
> >> - I'd propose to put the resulting jar into the Maven repository in
the
> >> "torque" group or "org.apache.torque" respectively. What do others
> >> say?
> >
> > m1:torque, m2:org.apache.torque is good.
>
> The repository people are bugging everybody to settle on one type of
> repository only. Shouldn't we try to use one group only for Torque? I
> propose to deploy the artifacts to the m2-repo only and use
> 'org.apache.torque' for this. Would that create big obstacles for the
> two maven plugins?
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: torque 3.3 schedule
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Fischer wrote:
>> - I'd propose to put the resulting jar into the Maven repository in the
>> "torque" group or "org.apache.torque" respectively. What do others
>> say?
>
> m1:torque, m2:org.apache.torque is good.
The repository people are bugging everybody to settle on one type of
repository only. Shouldn't we try to use one group only for Torque? I
propose to deploy the artifacts to the m2-repo only and use
'org.apache.torque' for this. Would that create big obstacles for the
two maven plugins?
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: torque 3.3 schedule
Posted by Thomas Fischer <fi...@seitenbau.net>.
Thomas Vandahl <th...@tewisoft.de> schrieb am 16.10.2007 09:11:45:
> Two questions remain (probably more will surface later):
> - What version should we give to the "integrated" Village? 2.0? 3.3?
I'd prefer 3.3 here.
> - I'd propose to put the resulting jar into the Maven repository in the
> "torque" group or "org.apache.torque" respectively. What do others
> say?
m1:torque, m2:org.apache.torque is good.
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: torque 3.3 schedule
Posted by Thomas Vandahl <th...@tewisoft.de>.
Greg Monroe wrote:
> IHMO, it seems much cleaner to keep it as a separate jar
> until it's totally re-packaged into the org.apache.torque
> (or some such) package. Doing this would require a lot
> of testing.
Ok, I see your point. Because Village already uses Maven to build, it
would probably be even easier to integrate as a separate module on the
same level as runtime, generator etc. The most difficult part remains
the integration of documentation into the site, anyway.
Two questions remain (probably more will surface later):
- What version should we give to the "integrated" Village? 2.0? 3.3?
- I'd propose to put the resulting jar into the Maven repository in the
"torque" group or "org.apache.torque" respectively. What do others
say?
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: torque 3.3 schedule
Posted by Brendan Miller <bm...@dotster.com>.
On Mon, Oct 15, 2007 at 10:27:07AM -0400, Greg Monroe wrote:
> FWIW, I'm -0.25 on integrating it into the Runtime jar
> for this version.
>
> Mostly because of possible support issues around having
> an old version of Village in the classpath with new code
> in the Torque jar. This probably won't be a developer
> problem because Maven, et al, handle the dependencies.
> But I can see it happening on established production
> servers where removing old jars are often forgotten.
Allow a humble user to chime in on this--our process is ant-driven
(not maven) and uses build.xml to copy the correct jars from our own
repository of jars against we have tested our application to the correct
production location. Obviously, we would intend to remove village.jar
once it was part of the torque runtime, but we could forget, the script
could go whack, a server could get missed, etc.
So good point.
Brendan
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
RE: torque 3.3 schedule
Posted by Greg Monroe <Gr...@DukeCE.com>.
FWIW, I'm -0.25 on integrating it into the Runtime jar
for this version.
Mostly because of possible support issues around having
an old version of Village in the classpath with new code
in the Torque jar. This probably won't be a developer
problem because Maven, et al, handle the dependencies.
But I can see it happening on established production
servers where removing old jars are often forgotten.
Now that we "own" the code, we're going to be able to put
in misc "patches" for various problems. So I can see
issues coming up due to jar miss-matches with classes in
two places.
IHMO, it seems much cleaner to keep it as a separate jar
until it's totally re-packaged into the org.apache.torque
(or some such) package. Doing this would require a lot
of testing.
> -----Original Message-----
> From: Thomas Vandahl [mailto:tv@apache.org]
> Sent: Saturday, October 13, 2007 10:36 AM
> To: Apache Torque Developers List
> Subject: Re: torque 3.3 schedule
>
> Thomas Fischer wrote:
> > how do you plan to integrate village anyway ? Into the
> runtime or as
> > separate jar ? (Personally I'd prefer a separate jar.)
>
> My preference was to integrate it directly into the runtime
> jar with the option of building it as a separate artifact, if
> someone so desires.
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
>
DukeCE Privacy Statement:
Please be advised that this e-mail and any files transmitted with
it are confidential communication or may otherwise be privileged or
confidential and are intended solely for the individual or entity
to whom they are addressed. If you are not the intended recipient
you may not rely on the contents of this email or any attachments,
and we ask that you please not read, copy or retransmit this
communication, but reply to the sender and destroy the email, its
contents, and all copies thereof immediately. Any unauthorized
dissemination, distribution or copying of this communication is
strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org