crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Micah Whitacre (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-244) Add support for hadoop1 and hadoop2 classifiers to the POM and release artifacts
Date Thu, 25 Jul 2013 13:41:50 GMT


Micah Whitacre commented on CRUNCH-244:

I'm not as well versed in how the projects are released beyond what you have documented here[1].
 When do you activate the second "hadoop2" profile?

I think Matthias is correct in that this would create a conflict.  Using the "hadoop1" profile
it would create a crunch-core-0.7.jar and a crunch-core-0.7-hadoop1.jar.  When the second
profile is activated we'd get crunch-core-0.7.jar again and a crunch-core-0.7-hadoop2-.jar.
 The second time it would fail to deploy because the crunch-core-0.7 already existed.  I also
think that if you use the secondary artifacts to group them all into a single groupId/artifactId/version,
the POM file would only be describing one set of the dependencies and not the appropriate
one for the version of hadoop you are compiling against.

Would it be better if we actually changed the version in each profile?  hadoop1 = 0.7-mrv1
and hadoop2 = 0.7 (or vice versa).

[1] -
> Add support for hadoop1 and hadoop2 classifiers to the POM and release artifacts
> --------------------------------------------------------------------------------
>                 Key: CRUNCH-244
>                 URL:
>             Project: Crunch
>          Issue Type: Bug
>            Reporter: Josh Wills
>         Attachments: CRUNCH-244.patch
> We would like to be able to publish jars and binary release artifacts that are compiled
against both the hadoop1 as well as the hadoop2 APIs as part of doing a release in order to
make the transition easier for clients to use.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message