You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Fabian Christ <fc...@gmx.de> on 2009/10/07 17:48:16 UTC
Injecting custom ConflictResolver using Embedder
Hi,
I'm doing some research on conflict resolving between Java components.
Now I would like to use my own ConflictResolver during a Maven run. I'm
using Maven Embedder in my application and tried several ways on how to
manipulate the Plexus container to use my own ConflictResolver. I used
the "customize" interface that is meant to manipulate the container on
Embedder startup but an "addComponent" did not work as expected.
Can someone give me a hint how to do that? I know the Wiki page at [1]
that suggests to manipulate the POM to configure the ConflictResolver
that should be used. But I'm working with Embedder and I can not change
the POMs. I would like to inject my ConflictResolver as the default
resolver when the Embedder is created. But how?
Thank you,
Fabian
[1] http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Nexus/Hudson/EC2
Posted by Brian Fox <br...@infinity.nu>.
On Thu, Oct 8, 2009 at 12:14 PM, Michael Hüttermann
<mi...@huettermann.net> wrote:
> What could be a practical scenario in the CI context for Clouding ?
I could see it being handy as temporary or sporadic load extension, or
alternative config support. IOW, once a day to run a build on a
different jdk/browser/os/other, driven as a slave from hudson, but not
as the primary system.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Nexus/Hudson/EC2
Posted by Michael Hüttermann <mi...@huettermann.net>.
What could be a practical scenario in the CI context for Clouding ?
Michael
> On Thu, Oct 8, 2009 at 4:52 AM, Anders Hammar <an...@hammar.net> wrote:
>> Yes, I was thinking about that one. Didn't really come to a good
>> conclusion.
>>
>> Pros:
>> * Easy to scale out
>> * Easy to start up (you don't have to buy the hardware etc)
>>
>> Cons:
>> * Security (if you need to retrieve the code and you don't want to have
>> your
>> version management system publicly available)
>> * If the repo manager is locally and the build server is externally,
>> retrieving artifacts will be slower. However, possibly not a big issue
>> unless you need to squeeze out that extra performance (time wise).
>> * Cost (?)
>>
>> What I'm thinking is that it could be an easy way to get started, but as
>> your build server(s) is most likely something you want for a long time
>> and
>> it will be working constantly, I think it might make more sense having
>> it
>> locally on your own hardware. It think it will be far more expensive to
>> have
>> it "in the cloud" compared to this. However, I don't have any figures to
>> back this up, it's just my guess.
>>
>> Anyone else having any thoughts?
>
> I'm thinking along the same lines. The virtual cloud instances are
> good for sporadic use but aren't as cost effective for around the
> clock cpu / disk io that you would see from a CI system. Also a CI
> system puts a heavy load on your repository (push and pull) so it
> needs to be near the repo. Having your repo in the cloud invalidates
> many of the benefits, namely proxying and caching that speeds up your
> builds and provides you the ability to continue working when your
> network is unstable.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Nexus/Hudson/EC2
Posted by Brian Fox <br...@infinity.nu>.
On Thu, Oct 8, 2009 at 4:52 AM, Anders Hammar <an...@hammar.net> wrote:
> Yes, I was thinking about that one. Didn't really come to a good conclusion.
>
> Pros:
> * Easy to scale out
> * Easy to start up (you don't have to buy the hardware etc)
>
> Cons:
> * Security (if you need to retrieve the code and you don't want to have your
> version management system publicly available)
> * If the repo manager is locally and the build server is externally,
> retrieving artifacts will be slower. However, possibly not a big issue
> unless you need to squeeze out that extra performance (time wise).
> * Cost (?)
>
> What I'm thinking is that it could be an easy way to get started, but as
> your build server(s) is most likely something you want for a long time and
> it will be working constantly, I think it might make more sense having it
> locally on your own hardware. It think it will be far more expensive to have
> it "in the cloud" compared to this. However, I don't have any figures to
> back this up, it's just my guess.
>
> Anyone else having any thoughts?
I'm thinking along the same lines. The virtual cloud instances are
good for sporadic use but aren't as cost effective for around the
clock cpu / disk io that you would see from a CI system. Also a CI
system puts a heavy load on your repository (push and pull) so it
needs to be near the repo. Having your repo in the cloud invalidates
many of the benefits, namely proxying and caching that speeds up your
builds and provides you the ability to continue working when your
network is unstable.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Nexus/Hudson/EC2
Posted by Anders Hammar <an...@hammar.net>.
Yes, I was thinking about that one. Didn't really come to a good conclusion.
Pros:
* Easy to scale out
* Easy to start up (you don't have to buy the hardware etc)
Cons:
* Security (if you need to retrieve the code and you don't want to have your
version management system publicly available)
* If the repo manager is locally and the build server is externally,
retrieving artifacts will be slower. However, possibly not a big issue
unless you need to squeeze out that extra performance (time wise).
* Cost (?)
What I'm thinking is that it could be an easy way to get started, but as
your build server(s) is most likely something you want for a long time and
it will be working constantly, I think it might make more sense having it
locally on your own hardware. It think it will be far more expensive to have
it "in the cloud" compared to this. However, I don't have any figures to
back this up, it's just my guess.
Anyone else having any thoughts?
/Anders
On Thu, Oct 8, 2009 at 10:17, Michael Hüttermann <mi...@huettermann.net>wrote:
> that is a good point. What do you think about running a build server in
> the Cloud while having the repo manager locally ?
>
>
> > While seeing the benefits of services and also of using the cloud in
> > general, I'm having a hard time ignoring the fact that I would like to
> > have
> > my repo manager locally. One great benefit of a repo manager is improved
> > speed when downloading artifacts, which I wouldn't get when it's hosted
> > outside of my LAN.
>
>
> Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven/Nexus/Hudson/EC2
Posted by Michael Hüttermann <mi...@huettermann.net>.
that is a good point. What do you think about running a build server in
the Cloud while having the repo manager locally ?
> While seeing the benefits of services and also of using the cloud in
> general, I'm having a hard time ignoring the fact that I would like to
> have
> my repo manager locally. One great benefit of a repo manager is improved
> speed when downloading artifacts, which I wouldn't get when it's hosted
> outside of my LAN.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Nexus/Hudson/EC2
Posted by Anders Hammar <an...@hammar.net>.
There is also Artifactory Online, a repo manager "service".
While seeing the benefits of services and also of using the cloud in
general, I'm having a hard time ignoring the fact that I would like to have
my repo manager locally. One great benefit of a repo manager is improved
speed when downloading artifacts, which I wouldn't get when it's hosted
outside of my LAN.
/Anders
On Wed, Oct 7, 2009 at 19:16, Jason van Zyl <ja...@sonatype.com> wrote:
>
> On 2009-10-07, at 9:38 AM, Michael Hüttermann wrote:
>
> Hello,
>>
>> do you plan to continue the work in the context nexus/hudson/ec2 you
>> kicked off and described here:
>>
>> http://www.sonatype.com/people/2009/06/nexus-open-source-and-hudson-on-ec2/
>>
>>
> That's orthogonal to anything we're doing with Maven.
>
> E.g. are you planning to provide new Maven versions in ec2 continuously,
>> to add more "convenience features", .. or similar things ?
>>
>>
> Maven 3.x builds on the standard Sonatype grid here:
> https://grid.sonatype.org/ci/view/Maven%203.0.x/
>
> It's just a standard VMWare grid. But we do use Hudson extensively.
>
>
>> Thank you.
>>
>> Best regards
>> Michael
>>
>> --
>> michael@huettermann.net
>> http://huettermann.net
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven/Nexus/Hudson/EC2
Posted by Jason van Zyl <ja...@sonatype.com>.
On 2009-10-07, at 9:38 AM, Michael Hüttermann wrote:
> Hello,
>
> do you plan to continue the work in the context nexus/hudson/ec2 you
> kicked off and described here:
> http://www.sonatype.com/people/2009/06/nexus-open-source-and-hudson-on-ec2/
>
That's orthogonal to anything we're doing with Maven.
> E.g. are you planning to provide new Maven versions in ec2
> continuously,
> to add more "convenience features", .. or similar things ?
>
Maven 3.x builds on the standard Sonatype grid here: https://grid.sonatype.org/ci/view/Maven%203.0.x/
It's just a standard VMWare grid. But we do use Hudson extensively.
>
> Thank you.
>
> Best regards
> Michael
>
> --
> michael@huettermann.net
> http://huettermann.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Maven/Nexus/Hudson/EC2
Posted by Michael Hüttermann <mi...@huettermann.net>.
Hello,
do you plan to continue the work in the context nexus/hudson/ec2 you
kicked off and described here:
http://www.sonatype.com/people/2009/06/nexus-open-source-and-hudson-on-ec2/
E.g. are you planning to provide new Maven versions in ec2 continuously,
to add more "convenience features", .. or similar things ?
Thank you.
Best regards
Michael
--
michael@huettermann.net
http://huettermann.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Injecting custom ConflictResolver using Embedder
Posted by Jason van Zyl <ja...@sonatype.com>.
Do not cross post between the user and dev list.
On 2009-10-07, at 8:48 AM, Fabian Christ wrote:
> Hi,
>
> I'm doing some research on conflict resolving between Java components.
> Now I would like to use my own ConflictResolver during a Maven run.
> I'm
> using Maven Embedder in my application and tried several ways on how
> to
> manipulate the Plexus container to use my own ConflictResolver. I used
> the "customize" interface that is meant to manipulate the container on
> Embedder startup but an "addComponent" did not work as expected.
>
> Can someone give me a hint how to do that? I know the Wiki page at [1]
> that suggests to manipulate the POM to configure the ConflictResolver
> that should be used. But I'm working with Embedder and I can not
> change
> the POMs. I would like to inject my ConflictResolver as the default
> resolver when the Embedder is created. But how?
>
> Thank you,
> Fabian
>
> [1] http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org