You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Blevins <da...@visi.com> on 2006/02/15 01:30:52 UTC
Re: Migrating to maven 2 - conversion idea
On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
> Is there an easy way to do this with m1? I'm concerned about
> having two dependency lists: one in the project.xml and one in the
> pom.xml. Is there a tool that can merge the project.xml
> dependencies into a template pom.xml?
If there was a tool we'd probably go from pom.xml to project.xml for
transitive deps reasons rather than the other way around.
But really, I wouldn't worry about having two deps lists. Here is an
idea for keeping things working ...
Why don't we:
- use an non-conflicting groupId like org.apache.geronimo-m2 or
something specifically for conversion
- set it up in our continuum install as another project
- and continuously build *both*
?
The reason for the new groupId is so that the m2 build doesn't
interfere at all with our regular m1 build. We just won't sycn
org.apache.geronimo-m2.
When our m2 build is read, we just drop the "-m2" suffix from the
groupId and delete the old maven.xml and project.xml files.
Thoughts?
-David
Re: Migrating to maven 2 - conversion idea
Posted by David Blevins <da...@visi.com>.
On Feb 15, 2006, at 2:52 PM, Alan D. Cabrera wrote:
> David Blevins wrote, On 2/14/2006 5:29 PM:
>> On Feb 14, 2006, at 5:01 PM, Dain Sundstrom wrote:
>>> I get the impression that people are proposing that we create
>>> parallel builds for modules one at a time, and I just don't see
>>> that working.
>> Both the OpenEJB and ActiveMQ builds were done as parallel
>> builds. I've got ActiveMQ up in continuum building as an M2
>> projects, so we know it stays good. Obviously, the OpenEJB build
>> was done way before we had continuum and it got crufty.
>> ActiveMQ still does releases from m1 as they still don't have all
>> their tests converted over. Other than that their m2 build works.
>> But I'm in the same boat as you, I don't have the bandwidth to
>> work on it aside from helping people get it running in continuum.
>
> I feel the same way as Dain but I am willing to back it up w/ warm
> bodies to help. Continuum will not help, imho. It will only
> remind us how badly the two versions are drifting.
Ok, now *that* is feedback I can use. The whole "i don't think it
will work" with no reasons why is not as useful.
And thanks for the warm bodies.
-David
Re: Migrating to maven 2 - conversion idea
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
David Blevins wrote, On 2/14/2006 5:29 PM:
>
> On Feb 14, 2006, at 5:01 PM, Dain Sundstrom wrote:
>
>> On Feb 14, 2006, at 4:30 PM, David Blevins wrote:
>>
>>>
>>> On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
>>>
>>>> Is there an easy way to do this with m1? I'm concerned about
>>>> having two dependency lists: one in the project.xml and one in the
>>>> pom.xml. Is there a tool that can merge the project.xml
>>>> dependencies into a template pom.xml?
>>>
>>>
>>> If there was a tool we'd probably go from pom.xml to project.xml for
>>> transitive deps reasons rather than the other way around.
>>>
>>> But really, I wouldn't worry about having two deps lists. Here is
>>> an idea for keeping things working ...
>>>
>>> Why don't we:
>>> - use an non-conflicting groupId like org.apache.geronimo-m2 or
>>> something specifically for conversion
>>> - set it up in our continuum install as another project
>>> - and continuously build *both*
>>>
>>> ?
>>>
>>> The reason for the new groupId is so that the m2 build doesn't
>>> interfere at all with our regular m1 build. We just won't sycn
>>> org.apache.geronimo-m2.
>>>
>>> When our m2 build is read, we just drop the "-m2" suffix from the
>>> groupId and delete the old maven.xml and project.xml files.
>>>
>>> Thoughts?
>>
>>
>> Take my comments with a large dose of salt since, I'm not
>> volunteering to do the work.... I would like to see a module
>> completely converted to m2 (one at a time) and stay converted.
>
>
> I think the continuum aspect would be the thing to ensure something
> stays converted. We could even do one at a time too, just that most
> people (and the release process) would continue to rely on m1 till m2
> conversion is completely done.
>
>> I get the impression that people are proposing that we create
>> parallel builds for modules one at a time, and I just don't see that
>> working.
>
>
> Both the OpenEJB and ActiveMQ builds were done as parallel builds.
> I've got ActiveMQ up in continuum building as an M2 projects, so we
> know it stays good. Obviously, the OpenEJB build was done way before we
> had continuum and it got crufty.
>
> ActiveMQ still does releases from m1 as they still don't have all their
> tests converted over. Other than that their m2 build works.
>
> But I'm in the same boat as you, I don't have the bandwidth to work on
> it aside from helping people get it running in continuum.
I feel the same way as Dain but I am willing to back it up w/ warm
bodies to help. Continuum will not help, imho. It will only remind us
how badly the two versions are drifting.
Regards,
Alan
Re: Migrating to maven 2 - conversion idea
Posted by David Blevins <da...@visi.com>.
On Feb 14, 2006, at 5:01 PM, Dain Sundstrom wrote:
> On Feb 14, 2006, at 4:30 PM, David Blevins wrote:
>
>>
>> On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
>>
>>> Is there an easy way to do this with m1? I'm concerned about
>>> having two dependency lists: one in the project.xml and one in
>>> the pom.xml. Is there a tool that can merge the project.xml
>>> dependencies into a template pom.xml?
>>
>> If there was a tool we'd probably go from pom.xml to project.xml
>> for transitive deps reasons rather than the other way around.
>>
>> But really, I wouldn't worry about having two deps lists. Here is
>> an idea for keeping things working ...
>>
>> Why don't we:
>> - use an non-conflicting groupId like org.apache.geronimo-m2 or
>> something specifically for conversion
>> - set it up in our continuum install as another project
>> - and continuously build *both*
>>
>> ?
>>
>> The reason for the new groupId is so that the m2 build doesn't
>> interfere at all with our regular m1 build. We just won't sycn
>> org.apache.geronimo-m2.
>>
>> When our m2 build is read, we just drop the "-m2" suffix from the
>> groupId and delete the old maven.xml and project.xml files.
>>
>> Thoughts?
>
> Take my comments with a large dose of salt since, I'm not
> volunteering to do the work.... I would like to see a module
> completely converted to m2 (one at a time) and stay converted.
I think the continuum aspect would be the thing to ensure something
stays converted. We could even do one at a time too, just that most
people (and the release process) would continue to rely on m1 till m2
conversion is completely done.
> I get the impression that people are proposing that we create
> parallel builds for modules one at a time, and I just don't see
> that working.
Both the OpenEJB and ActiveMQ builds were done as parallel builds.
I've got ActiveMQ up in continuum building as an M2 projects, so we
know it stays good. Obviously, the OpenEJB build was done way before
we had continuum and it got crufty.
ActiveMQ still does releases from m1 as they still don't have all
their tests converted over. Other than that their m2 build works.
But I'm in the same boat as you, I don't have the bandwidth to work
on it aside from helping people get it running in continuum.
-David
Re: Migrating to maven 2 - conversion idea
Posted by Dain Sundstrom <da...@iq80.com>.
On Feb 14, 2006, at 4:30 PM, David Blevins wrote:
>
> On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
>
>> Is there an easy way to do this with m1? I'm concerned about
>> having two dependency lists: one in the project.xml and one in the
>> pom.xml. Is there a tool that can merge the project.xml
>> dependencies into a template pom.xml?
>
> If there was a tool we'd probably go from pom.xml to project.xml
> for transitive deps reasons rather than the other way around.
>
> But really, I wouldn't worry about having two deps lists. Here is
> an idea for keeping things working ...
>
> Why don't we:
> - use an non-conflicting groupId like org.apache.geronimo-m2 or
> something specifically for conversion
> - set it up in our continuum install as another project
> - and continuously build *both*
>
> ?
>
> The reason for the new groupId is so that the m2 build doesn't
> interfere at all with our regular m1 build. We just won't sycn
> org.apache.geronimo-m2.
>
> When our m2 build is read, we just drop the "-m2" suffix from the
> groupId and delete the old maven.xml and project.xml files.
>
> Thoughts?
Take my comments with a large dose of salt since, I'm not
volunteering to do the work.... I would like to see a module
completely converted to m2 (one at a time) and stay converted. I get
the impression that people are proposing that we create parallel
builds for modules one at a time, and I just don't see that working.
Then again, if there is a group of you that want to do the work,
don't let me hold you back. I've been wrong many times before.
-dain
Re: Migrating to maven 2 - conversion idea
Posted by David Blevins <da...@visi.com>.
On Feb 14, 2006, at 5:28 PM, Brett Porter wrote:
> On 2/15/06, David Blevins <da...@visi.com> wrote:
>> Every m2 project i've worked with eventually ended up leveraging
>> maven 1 repositories.
>>
>> We'd likely use the maven-one-plugin which puts jars into a maven 1
>> repo. Also we'd likely still need to list cvs.apache.org in the repo
>> list of our m2 build.
>
> That's because they're all depending on snapshot versions of geronimo
> dependencies :)
>
> You will want to limit the number of snapshot repos you use, and
> eventually remove dependence on m1 repos. I'd suggest mapping out
> "what goes where" first. If all you are using is ibiblio, there is no
> need to use the m1 version, as it is just a mapping over the m2 one.
>
> Isn't the current Geronimo group ID "geronimo", so the new one can be
> "org.apache.geronimo" without a clash?
>
Oh, yea. You're right. We could just use "geronimo" groupId in m1
and "org.apache.geronimo" groupId for m2. For some reason I was
thinking we switched groupIds already.
-David
Re: Migrating to maven 2 - conversion idea
Posted by Anders Hessellund Jensen <ah...@trifork.com>.
Brett Porter wrote:
> Isn't the current Geronimo group ID "geronimo", so the new one can be
> "org.apache.geronimo" without a clash?
Great! The modules i converted to m2 already has groupId set to this in
the m2 build.
Re: Migrating to maven 2 - conversion idea
Posted by Brett Porter <br...@gmail.com>.
On 2/15/06, David Blevins <da...@visi.com> wrote:
> Every m2 project i've worked with eventually ended up leveraging
> maven 1 repositories.
>
> We'd likely use the maven-one-plugin which puts jars into a maven 1
> repo. Also we'd likely still need to list cvs.apache.org in the repo
> list of our m2 build.
That's because they're all depending on snapshot versions of geronimo
dependencies :)
You will want to limit the number of snapshot repos you use, and
eventually remove dependence on m1 repos. I'd suggest mapping out
"what goes where" first. If all you are using is ibiblio, there is no
need to use the m1 version, as it is just a mapping over the m2 one.
Isn't the current Geronimo group ID "geronimo", so the new one can be
"org.apache.geronimo" without a clash?
- Brett
Re: Migrating to maven 2 - conversion idea
Posted by David Blevins <da...@visi.com>.
On Feb 14, 2006, at 4:48 PM, Anders Hessellund Jensen wrote:
> David Blevins wrote:
>> Why don't we:
>> - use an non-conflicting groupId like org.apache.geronimo-m2 or
>> something specifically for conversion
>> - set it up in our continuum install as another project
>> - and continuously build *both*
>> ?
>> The reason for the new groupId is so that the m2 build doesn't
>> interfere at all with our regular m1 build. We just won't sycn
>> org.apache.geronimo-m2.
>
> As I understand it, there should be no problems with interference.
> m1 and m2 uses different repositories. m1 will always get the
> dependencies built by m1, and m2 will always get the dependencies
> built by m2. The two builds should be able to coexist without any
> interference, so there should be no need to change the groupId.
Every m2 project i've worked with eventually ended up leveraging
maven 1 repositories.
We'd likely use the maven-one-plugin which puts jars into a maven 1
repo. Also we'd likely still need to list cvs.apache.org in the repo
list of our m2 build.
-David
Re: Migrating to maven 2 - conversion idea
Posted by Anders Hessellund Jensen <ah...@trifork.com>.
David Blevins wrote:
> Why don't we:
> - use an non-conflicting groupId like org.apache.geronimo-m2 or
> something specifically for conversion
> - set it up in our continuum install as another project
> - and continuously build *both*
>
> ?
>
> The reason for the new groupId is so that the m2 build doesn't
> interfere at all with our regular m1 build. We just won't sycn
> org.apache.geronimo-m2.
As I understand it, there should be no problems with interference. m1
and m2 uses different repositories. m1 will always get the dependencies
built by m1, and m2 will always get the dependencies built by m2. The
two builds should be able to coexist without any interference, so there
should be no need to change the groupId.
I agree that we should set the m2 build up in continuum - the sooner the
better.
Re: Migrating to maven 2 - conversion idea
Posted by Jason Dillon <ja...@planet57.com>.
Please, no -m2 suffix.
--jason
On 2/14/06, David Blevins <da...@visi.com> wrote:
>
> On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
>
> > Is there an easy way to do this with m1? I'm concerned about
> > having two dependency lists: one in the project.xml and one in the
> > pom.xml. Is there a tool that can merge the project.xml
> > dependencies into a template pom.xml?
>
> If there was a tool we'd probably go from pom.xml to project.xml for
> transitive deps reasons rather than the other way around.
>
> But really, I wouldn't worry about having two deps lists. Here is an
> idea for keeping things working ...
>
> Why don't we:
> - use an non-conflicting groupId like org.apache.geronimo-m2 or
> something specifically for conversion
> - set it up in our continuum install as another project
> - and continuously build *both*
>
> ?
>
> The reason for the new groupId is so that the m2 build doesn't
> interfere at all with our regular m1 build. We just won't sycn
> org.apache.geronimo-m2.
>
> When our m2 build is read, we just drop the "-m2" suffix from the
> groupId and delete the old maven.xml and project.xml files.
>
> Thoughts?
>
> -David
>
>
>
>
>
>