You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Scott Wegner (JIRA)" <ji...@apache.org> on 2018/04/18 15:55:00 UTC
[jira] [Assigned] (BEAM-4057) Ensure generated pom don't break
consumers
[ https://issues.apache.org/jira/browse/BEAM-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wegner reassigned BEAM-4057:
----------------------------------
Assignee: (was: Luke Cwik)
> Ensure generated pom don't break consumers
> ------------------------------------------
>
> Key: BEAM-4057
> URL: https://issues.apache.org/jira/browse/BEAM-4057
> Project: Beam
> Issue Type: Sub-task
> Components: build-system
> Reporter: Romain Manni-Bucau
> Priority: Major
>
> Out of my head here are the requirements:
> 1. dependencies are all here (all scopes and well scoped: this means that provided or test dependencies are not in compile scope for instance)
> 2. META-INF should contain the pom.xml and pom.properties as maven generates them (it is consumes by tools and libraries to grab the dependencies or scan some classpath/lib folder)
> 3. ensure the compiler plugin at least is defined with the java version+compiler flags (a usage is to check if -parameters is activated for instance)
> 4. (nice to have) dont put all the boilerplate in all poms (license, etc) but keep it in the parent pom as it was
> 5. (if possible) respect the hierarchy (parents) - this is used sometimes as a shortcut for dependencies analyzis cause it is faster than analyzing the dependencies, probably not the best practise ever but it is efficient in general
> 6. ensure meta used by mainstream tools like mvnrepository are here (description etc, should be a passthrough from gradle)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)