You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Sridhar Iyer <sr...@gmail.com> on 2012/01/17 11:12:45 UTC
oozie's maven dep
Hi,
oozie has the following snippet in its pom file:
<groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-enforcer-plugin</artifactId>
> <inherited>false</inherited>
> <configuration>
> <rules>
> <requireMavenVersion>
> <version>[3.0.0,)</version>
This causes the build to fail with maven2(present in lucid repos). After
installing maven3, the setup goes through but is still using maven2 repo.
Is this correct or should this requirement be fixed to use maven 2?
Thanks,
Sridhar
Re: oozie's maven dep
Posted by Bruno Mahé <bm...@apache.org>.
On 01/17/2012 02:12 AM, Sridhar Iyer wrote:
> Hi,
>
> oozie has the following snippet in its pom file:
>
> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-enforcer-plugin</artifactId>
>> <inherited>false</inherited>
>> <configuration>
>> <rules>
>> <requireMavenVersion>
>> <version>[3.0.0,)</version>
>
> This causes the build to fail with maven2(present in lucid repos). After
> installing maven3, the setup goes through but is still using maven2 repo.
> Is this correct or should this requirement be fixed to use maven 2?
>
> Thanks,
> Sridhar
>
Maven3 and 2 use the same format for their repositories.
I just confirmed this with Andrew as well.
So it's not an issue
Re: oozie's maven dep
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
Oozie requires Maven 3.0.0+ to build.
Thanks.
Alejandro
On Tue, Jan 17, 2012 at 2:12 AM, Sridhar Iyer <sr...@gmail.com>wrote:
> Hi,
>
> oozie has the following snippet in its pom file:
>
> <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-enforcer-plugin</artifactId>
> > <inherited>false</inherited>
> > <configuration>
> > <rules>
> > <requireMavenVersion>
> > <version>[3.0.0,)</version>
>
>
> This causes the build to fail with maven2(present in lucid repos). After
> installing maven3, the setup goes through but is still using maven2 repo.
> Is this correct or should this requirement be fixed to use maven 2?
>
> Thanks,
> Sridhar
>