[
https://issues.apache.org/jira/browse/FLUME-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Wendell updated FLUME-2379:
-----------------------------------
Description:
The pom file in flume 1.4 relies on properties that are not defined outside of
profiles. This is technically an invalid pom format and, while it happens to be
supported by maven, is not supported by other build tools that consume poms.
The issue is with the parent pom:
http://repo1.maven.org/maven2/org/apache/flume/flume-parent/1.4.0/flume-parent-1.4.0.pom
In general, AFIAK, it's not good for projects to rely on profiles for
downstream consumers of build, since technically maven profiles are not
considered during transitive dependency resolution.
To fix this, default values just need to be set for properties such as
`thrift.version` that are defined inside of the profiles.
I reproduced this easily with the following build.sbt file:
{code}
name := "Simple Project"
version := "1.0"
libraryDependencies += "org.apache.flume" % "flume-ng-sdk" % "1.4.0"
{code}
Then you can just run `sbt compile` and it fails.
was:
The pom file in flume 1.4 relies on properties that are not defined outside of
profiles. This is technically an invalid pom format and, while it happens to be
supported by maven, is not supported by other build tools that consume poms.
In general, AFIAK, it's not good for projects to rely on profiles for
downstream consumers of build, since technically maven profiles are not
considered during transitive dependency resolution.
To fix this, default values just need to be set for properties such as
`thrift.version` that are defined inside of the profiles.
I reproduced this easily with the following build.sbt file:
{code}
name := "Simple Project"
version := "1.0"
libraryDependencies += "org.apache.flume" % "flume-ng-sdk" % "1.4.0"
{code}
Then you can just run `sbt compile` and it fails.
> Flume's pom files are invalid and not parseable by non-maven build tools
> ------------------------------------------------------------------------
>
> Key: FLUME-2379
> URL: https://issues.apache.org/jira/browse/FLUME-2379
> Project: Flume
> Issue Type: Bug
> Components: Build
> Affects Versions: v1.4.0
> Reporter: Patrick Wendell
>
> The pom file in flume 1.4 relies on properties that are not defined outside
> of profiles. This is technically an invalid pom format and, while it happens
> to be supported by maven, is not supported by other build tools that consume
> poms.
> The issue is with the parent pom:
> http://repo1.maven.org/maven2/org/apache/flume/flume-parent/1.4.0/flume-parent-1.4.0.pom
> In general, AFIAK, it's not good for projects to rely on profiles for
> downstream consumers of build, since technically maven profiles are not
> considered during transitive dependency resolution.
> To fix this, default values just need to be set for properties such as
> `thrift.version` that are defined inside of the profiles.
> I reproduced this easily with the following build.sbt file:
> {code}
> name := "Simple Project"
> version := "1.0"
> libraryDependencies += "org.apache.flume" % "flume-ng-sdk" % "1.4.0"
> {code}
> Then you can just run `sbt compile` and it fails.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
