Browse Source

Replace github.com/vaadin/vaadin with github.com/vaadin/framework (#75)

tags/8.0.0.alpha9
Artur 7 years ago
parent
commit
105ac0b10a

+ 3
- 3
CONTRIBUTING.md View File

@@ -26,13 +26,13 @@ Getting in touch with us early will also help us co-ordinate efforts so that not

# Obtain a current source tree

The Vaadin repository can be cloned using `git clone https://github.com/vaadin/vaadin.git` or using your favorite Git tool.
The Vaadin repository can be cloned using `git clone https://github.com/vaadin/framework.git` or using your favorite Git tool.

Remember to do `git checkout master` and `git pull` to make sure you are creating your commits on top of a recent enough version.

## Set up your development environment

To set up the project to your IDE, follow the instructions in the [README.md](https://github.com/vaadin/vaadin).
To set up the project to your IDE, follow the instructions in the [README.md](https://github.com/vaadin/framework).

# Describe your changes

@@ -72,7 +72,7 @@ When dividing your change into a series of patches, take special care to ensure

# Style-check your changes

Check your patch for basic style violations. If you use eclipse, use the formatting rules preconfigured in the project to make life easier for all involved, and configure save actions as described in [README.md](https://github.com/vaadin/vaadin/blob/master/README.md).
Check your patch for basic style violations. If you use eclipse, use the formatting rules preconfigured in the project to make life easier for all involved, and configure save actions as described in [README.md](https://github.com/vaadin/framework/blob/master/README.md).

Patches causing unnecessary style/whitespace changes are messy and will likely be bounced back.


+ 3
- 3
README.md View File

@@ -4,7 +4,7 @@

For instructions about _using_ Vaadin to develop applications, please refer to [Vaadin tutorial](https://vaadin.com/docs/-/part/framework/tutorial.html) and other [documentation](https://vaadin.com/docs/).

To contribute, first refer to [Contributing Code](https://github.com/vaadin/vaadin/blob/master/CONTRIBUTING.md)
To contribute, first refer to [Contributing Code](https://github.com/vaadin/framework/blob/master/CONTRIBUTING.md)
for general instructions and requirements for contributing code to the Vaadin framework.

Instructions on how to set up a working environment for developing the Vaadin Framework follow below.
@@ -16,7 +16,7 @@ The distribution files can be built by running the standard Maven goal `mvn inst
## Eclipse Quick Setup

1. Run
<code>git clone https://github.com/vaadin/vaadin.git</code>
<code>git clone https://github.com/vaadin/framework.git</code>
command or clone the repository your favorite Git tool.
If using Windows, you might want to add these Git settings: `core.autocrlf=false` and `core.fileMode=false`.
1. Run <code>mvn install</code> in the project root.
@@ -65,7 +65,7 @@ The following preferences need to be set to keep the project consistent. You nee

1. Intall and run IDEA. Ultimate Edition is better but Community Edition should also work.
1. Ensure if Git and Maven plugins are installed, properly configured and enabled.
1. Clone the repository, using menu VCS -> Checkout from Version Control -> Git -> Git Repository URL -> https://github.com/vaadin/vaadin.git.
1. Clone the repository, using menu VCS -> Checkout from Version Control -> Git -> Git Repository URL -> https://github.com/vaadin/framework.git.
When the repository is cloned, do **NOT** open it as a project.
1. Open cloned repository as a maven object. Use File -> Open and choose root _pom.xml_ file
1. Have a coffee break while IDEA is loading dependencies and indexing the project

+ 2
- 2
all/src/main/templates/release-notes.html View File

@@ -71,7 +71,7 @@
<!-- @release-notes-changelog@ -->
<p>
You can find the full list of all changes <a
href="https://github.com/vaadin/vaadin/releases/tag/@version@">in
href="https://github.com/vaadin/framework/releases/tag/@version@">in
GitHub</a>.
</p>

@@ -268,7 +268,7 @@
</p>

<p>
There is a <a href="https://github.com/vaadin/vaadin8-migration-tool/">
There is a <a href="https://github.com/vaadin/framework8-migration-tool/">
migration tool</a> which helps with some of the migration steps.
</p>


+ 3
- 3
pom.xml View File

@@ -80,9 +80,9 @@
</license>
</licenses>
<scm>
<connection>scm:https:https://github.com/vaadin/vaadin.git</connection>
<developerConnection>scm:https:https://github.com/vaadin/vaadin.git</developerConnection>
<url>https://github.com/vaadin/vaadin</url>
<connection>scm:https:https://github.com/vaadin/framework.git</connection>
<developerConnection>scm:https:https://github.com/vaadin/framework.git</developerConnection>
<url>https://github.com/vaadin/framework</url>
</scm>



+ 1
- 1
scripts/GeneratePostPublishReport.py View File

@@ -57,7 +57,7 @@ content += createTableRow("", "Inform marketing and PO about the release")
content += createTableRow("", "<a href=\"http://{}/admin/editProject.html?projectId={}&tab=projectParams\">Update vaadin.version.latest and vaadin.version.next parameters in TeamCity</a>".format(args.teamcityUrl, args.projectId))

# Link to GH release notes
content += createTableRow("", "<a href=\"https://github.com/vaadin/vaadin/releases/new\">Write release notes in GH</a>")
content += createTableRow("", "<a href=\"https://github.com/vaadin/framework/releases/new\">Write release notes in GH</a>")

content += "</table></body></html>"


+ 1
- 1
scripts/GeneratePublishReportPart1.py View File

@@ -53,7 +53,7 @@ metadataOk = True
for url in metadataChecks:
metadataOk = metadataOk and checkUrlContents(url, metadataChecks[url].format(ver=args.version))

tagOk = checkUrlStatus("https://github.com/vaadin/vaadin/releases/tag/{ver}".format(ver=args.version))
tagOk = checkUrlStatus("https://github.com/vaadin/framework/releases/tag/{ver}".format(ver=args.version))

if not prerelease:
downloadPageOk = checkUrlStatus("https://vaadin.com/download/release/{maj}.{min}/{ver}/".format(maj=major, min=minor, ver=args.version))

Loading…
Cancel
Save