You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/05/02 10:57:14 UTC

[jira] [Created] (FLUME-2379) Flume's pom files are invalid and not parseable by non-maven build tools

Patrick Wendell created FLUME-2379:
--------------------------------------

             Summary: 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.

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)