hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Carey <sc...@richrelevance.com>
Subject Re: getting started building Mavenized hadoop common
Date Mon, 08 Aug 2011 21:59:52 GMT
Also note that if you trigger a profile that changes the repo, it
_replaces_ the other repos, it does not 'merge' them. So if you configure
a profile that defines an internal Maven repo, you have just 'erased' the
other repos from the POV of your build.

You must either: define both your internal repo AND the external ones in
the POM, 
Configure your internal repo to cascade to an external one for things it
does not find.

Generally, the latter is recommended because it gives your organization
more control over what is pulled and from where.

On 8/5/11 9:53 AM, "Alejandro Abdelnur" <tucu@cloudera.com> wrote:

>For using a settings.xml in other location than ~/.m2 use:
>mvn --settings /home/foo/mysettings.xml ....
>For using a local cache in other location than ~/.m2/repository use:
>mvn -Dmaven.repo.local ...
>Hope this helps.
>On Fri, Aug 5, 2011 at 9:43 AM, Rottinghuis, Joep <jrottinghuis@ebay.com>
>> My ~/.m2/settings.xml has an activeProfile defined for an internal
>>Maven repo to be able to resolve 0.22 snapshots internally.
>> When trying the
>> mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
>> step this failed because it tried to resolve 0.23-SNAPSHOT against our
>>internal repo.
>> After first running
>> mvn install -DskipTests
>> the problem was resolved.
>> This makes me wonder if it is possible to pass something like
>>-Dmaven.repo.local or -Dsettings.localRepository on the command-line?
>> It would also be nice if I can specify different active profiles per
>>build through properties.
>> Right now that all seems to come from the same shared
>> Cheers,
>> Joep
>> -----Original Message-----
>> From: Eli Collins [mailto:eli@cloudera.com]
>> Sent: Thursday, August 04, 2011 1:41 PM
>> To: general@hadoop.apache.org
>> Subject: Re: getting started building Mavenized hadoop common
>> On Thu, Aug 4, 2011 at 1:38 PM, Eli Collins <eli@cloudera.com> wrote:
>> > On Tue, Aug 2, 2011 at 5:44 PM, Tom White <tom@cloudera.com> wrote:
>> >> On Tue, Aug 2, 2011 at 3:47 PM, Jeffrey Naisbitt
>><jnaisbit@yahoo-inc.com> wrote:
>> >>> On 8/2/11 5:21 PM, "Alejandro Abdelnur" <tucu@cloudera.com> wrote:
>> >>>> Regarding adding the 'target/generated-src/test/java' dir to the
>>build path.
>> >>>> You are correct, you have to add it manually to your IDE (I use
>> >>>> IntelliJ and it is the same story). But unless you need to debug
>> >>>> through the generated code you don't need to do so (doing a 'mvn
>> >>>> test -DskipTests' will generate/compile the class and the .class
>> >>>> file will be in the IDE project classpath).
>> >>>
>> >>> I like to debug through the code :)  It would be nice if there were
>> >>> an automated way to handle that folder, but in the meantime, it
>> >>> would probably be useful to document that along with the eclipse
>> >>
>> >> I had to do this step too. I've added it to the instructions on
>> >> http://wiki.apache.org/hadoop/EclipseEnvironment, but I agree it
>> >> would be nice to automate this if anyone knows the relevant setting.
>> >>
>> >
>> > Using helios when I follow these instructions, selecting the top-level
>> > Hadoop directory as the root directory, just gives me MapReduceTools
>> > as the only project (no hadoop-annotations, hadoop-assemblies, and
>> > hadoop-common, etc.)   Do these instructions work for anyone else?
>> >
>> Never mind, was missing the mvn eclipse:eclipse step.

View raw message