Skip to content
This repository has been archived by the owner on Aug 4, 2022. It is now read-only.

[REEF-90]: Migrate REEF website code from a private repo to REEF repo #66

Closed
wants to merge 1 commit into from

Conversation

joshuaseol
Copy link
Contributor

  • Modified the pom.xml file of $REEF_HOME to exclude README.* files in all directories when using mvn apache-rat:check
  • Added a directory labelled website which contains the source code for the REEF website
  • Added license headers to all website/src/* files except README.md
  • Added the parent artifact and groupID and artifactID for REEF inside the website project's pom.xml file
  • The javadocs for the 0.10-incubating release needs to be created using a script which is a separate issue recorded in REEF-91 and thus the javadocs link will not work until the script is created and functional.
  • The current Apache REEF logo (website/src/site/resources/REEFLogo.png) is a temporary placeholder because the real logo is under development in REEF-14.

JIRA: REEF-90

This addressed the issue by
 * Modifying the pom.xml file of $REEF_HOME to exclude README.* files in all directories when using `mvn apache-rat:check`
 * Adding a directory labelled `website` which contains the source code for the REEF website
 * Adding license headers to all website/src/* files except README.md
 * Adding the parent artifact and groupID and artifactID for REEF inside the website project's pom.xml file

JIRA: [REEF-90](https://issues.apache.org/jira/browse/REEF-90)
@johnyangk
Copy link
Contributor

I'll create a pointer at https://issues.apache.org/jira/browse/REEF-90 for you.

@johnyangk
Copy link
Contributor

Never mind, I didn't know non-committers could also create one.

@asfbot
Copy link

asfbot commented Feb 4, 2015

Reef-pull-request-ubuntu #233 SUCCESS
This pull request looks good

@asfbot
Copy link

asfbot commented Feb 4, 2015

Reef-pull-request-windows #66 UNSTABLE
Looks like there's a problem with this pull request

@markusweimer
Copy link
Contributor

I'll merge this.

@markusweimer
Copy link
Contributor

Uhm, turns our that I won't merge this :-). When I run mvn clean site:site, I get the following error:

[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project  (D:\src\reef\website\pom.xml) has 1 error
[ERROR]     Non-parseable POM D:\src\reef\website\pom.xml: end tag name </version> must match start tag name <name> from line 22 (position: TEXT seen ...<name>REEF Website</version>... @22:33)  @ line 22, column 33 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/ModelParseException

@markusweimer
Copy link
Contributor

Nevermind, I fixed the issue on my end and will merge the fixed version.

@asfgit asfgit closed this in fa77cc6 Feb 5, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
4 participants