[
https://issues.apache.org/jira/browse/MAHOUT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isabel Drost updated MAHOUT-171:
--------------------------------
Attachment: MAHOUT-171.patch
I moved the stuff in the buildtools directory over to our "maven" module. I
think we have few enough configuration files to bundle all the
maven/eclipse/intellij/checkstyle stuff in one module. I added javadoc and
source-jar download and a line to enable the checkstyle config for the eclipse
plugin. However so far the checkstyle config itself seems rather rudimentary to
me - can disable it, if that is not cleaned up yet.
I deleted the NOTICE and LICENSE files that obviously were copied over from
another project to buildtools/src/main/resources/META-INF.
I converted the NOTICE and LICENSE file generation to use the maven remote
resources plugin as recommended in the Apache parent pom. (Thanks to Jukka for
clarifying on how to include a custom NOTICE file)
I added sublemental entries that describe our dependencies so besides license
and notice there is a DEPENDENCIES file being generated with information on
project, license, project url and the like for all (transitive) dependencies of
Mahout.
I think this patch requires a review of the changes and the generated artifacts
to make sure everything is still where it belongs to after the changes.
> Move deployment to repository.apache.org
> ----------------------------------------
>
> Key: MAHOUT-171
> URL: https://issues.apache.org/jira/browse/MAHOUT-171
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.1
> Reporter: Isabel Drost
> Assignee: Isabel Drost
> Fix For: 0.2
>
> Attachments: MAHOUT-171.patch
>
>
> Opening a JIRA task to collect what has to be done for moving over to using
> apache version 5 parent pom (see also
> http://markmail.org/thread/ld26m3xxzoztqsk6 ).
> * Link Apache parent pom into our pom.
> * Update hudson to build via maven ( ? ).
> * File subtask at INFRA-1896 to include mahout in repository.apache.org
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
