spring-cloud / spring-cloud-build Goto Github PK
View Code? Open in Web Editor NEWCommon build concerns, shared plugin configuration, etc. for Spring Cloud modules
License: Apache License 2.0
Common build concerns, shared plugin configuration, etc. for Spring Cloud modules
License: Apache License 2.0
See https://raw.githubusercontent.com/square/okhttp/master/.github/ISSUE_TEMPLATE.md
What kind of issue is this?
- [ ] Question. This issue tracker is not the place for questions. If you want to ask how to do
something, or to understand why something isn't working the way you expect it to, use Stack
Overflow. https://stackoverflow.com/questions/tagged/spring-cloud
- [ ] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests
get fixed. Here’s an example: <todo>
- [ ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose.
See boot commit for inspiration spring-projects/spring-boot@c5d8eec
The project is making use of the org.codehaus.mojo:exec-maven-plugin
maven plugin. Unfortunately M2E does not (yet) support this plugin inside Eclipse.
Why not disabling it in the project top-level pom? This would ease the import of the project inside Eclipse.
Proposition is to add the following inside spring-cloud-build/pom.xml
:
<pluginManagement>
<plugins>
<!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<versionRange>[1.3.2,)</versionRange>
<goals>
<goal>exec</goal>
</goals>
</pluginExecutionFilter>
<action>
<ignore></ignore>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
</plugins>
</pluginManagement>
Or even better, this could be declared inside a separate profile activated only when under Eclipse (this would avoid maven complaining during builds because it could not find the lifecycle-mapping
pseudo plugin that doesn't actually exist):
<profiles>
<profile>
<id>m2e</id>
<activation>
<property>
<name>m2e.version</name>
</property>
</activation>
<build>
<pluginManagement>
....
</pluginManagement>
</build>
</profile>
</profiles>
distributionUrl=https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip
It's very manual and error prone (forget to push tags, promote to maven central, etc...).
Spring-Data follows a similar release train and memory serves @olivergierke has some automation. Oliver can you point me to it?
http://www.mojohaus.org/license-maven-plugin/
So we can see the license of the dependencies and potentially fail when we have a non-good license.
https://github.com/pivotal-cf/spring-cloud-service-broker/pull/5
Similar to how we do all the other servers. Create a sample in scripts.
https://github.com/spring-cloud/spring-cloud-build/blob/master/docs/src/main/asciidoc/ghpages.sh
+ COMMIT_SUCCESSFUL=no
+ git commit -a -m 'Sync docs from v1.1.2.RELEASE to gh-pages'
On branch gh-pages
Your branch is up-to-date with 'origin/gh-pages'.
nothing to commit, working tree clean
+ echo 'Failed to commit changes'
Failed to commit changes
+ [[ no == \y\e\s ]]
+ checkout_previous_branch
+ cd /Users/sgibb/workspace/spring/spring-cloud-consul
+ git checkout v1.1.2.RELEASE
HEAD is now at 5eaf6aa... Update SNAPSHOT to 1.1.2.RELEASE
+ '[' '' '!=' 0 ']'
+ git stash pop
Auto-merging spring-cloud-starter-consul/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-starter-consul/pom.xml
Auto-merging spring-cloud-starter-consul-discovery/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-starter-consul-discovery/pom.xml
Auto-merging spring-cloud-starter-consul-config/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-starter-consul-config/pom.xml
Auto-merging spring-cloud-starter-consul-bus/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-starter-consul-bus/pom.xml
Auto-merging spring-cloud-starter-consul-all/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-starter-consul-all/pom.xml
Auto-merging spring-cloud-consul-sample/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-consul-sample/pom.xml
Auto-merging spring-cloud-consul-discovery/src/test/java/org/springframework/cloud/consul/discovery/ConsulLifecycleCustomizedPropsTests.java
Auto-merging spring-cloud-consul-discovery/src/main/java/org/springframework/cloud/consul/discovery/ConsulLifecycle.java
CONFLICT (content): Merge conflict in spring-cloud-consul-discovery/src/main/java/org/springframework/cloud/consul/discovery/ConsulLifecycle.java
Auto-merging spring-cloud-consul-discovery/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-consul-discovery/pom.xml
Auto-merging spring-cloud-consul-dependencies/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-consul-dependencies/pom.xml
Auto-merging spring-cloud-consul-core/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-consul-core/pom.xml
Auto-merging spring-cloud-consul-config/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-consul-config/pom.xml
Auto-merging spring-cloud-consul-binder/pom.xml
CONFLICT (content): Merge conflict in spring-cloud-consul-binder/pom.xml
Auto-merging pom.xml
CONFLICT (content): Merge conflict in pom.xml
Auto-merging docs/src/main/asciidoc/README.adoc
CONFLICT (content): Merge conflict in docs/src/main/asciidoc/README.adoc
Auto-merging docs/pom.xml
CONFLICT (content): Merge conflict in docs/pom.xml
Auto-merging README.adoc
CONFLICT (content): Merge conflict in README.adoc
related issue spring-cloud/spring-cloud-sleuth#876
Hi,
When will be the approximate release date of spring-cloud-build 2?
This commit
ended up removing these versions via inheritance through spring-boot-dependencies.
Add them into the spring-cloud-build pom.
There maybe an issue with eclipse using the latest maven-jar-plugin version 3.0.x
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#failOnError
This will catch problems where no javadoc is deployed to nexus.
After fixing 58 we have in root pom for the Checkstyle plugin:
<headerLocation>LICENSE.txt</headerLocation>
where it refers to the https://github.com/spring-cloud/spring-cloud-build/blob/master/spring-cloud-build-tools/src/main/resources/LICENSE.txt
But this indeed must be Java class Copyright pattern, something like this:
^\Q/*\E$
^\Q * Copyright \E20\d\d(\-20\d\d)?\Q the original author or authors.\E$
^\Q *\E$
^\Q * Licensed under the Apache License, Version 2.0 (the "License");\E$
^\Q * you may not use this file except in compliance with the License.\E$
^\Q * You may obtain a copy of the License at\E$
^\Q *\E$
^\Q * http://www.apache.org/licenses/LICENSE-2.0\E$
^\Q *\E$
^\Q * Unless required by applicable law or agreed to in writing, software\E$
^\Q * distributed under the License is distributed on an "AS IS" BASIS,\E$
^\Q * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\E$
^\Q * See the License for the specific language governing permissions and\E$
^\Q * limitations under the License.\E$
^\Q */\E$
^$
^.*$
The current state causes this error during build:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (validate) on project spring-cloud-stream-binder-kinesis-parent: Execution validate of goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed: line 83 in
header specification is not a regular expression: Unclosed group near index 65
[ERROR] institute patent litigation against any entity (including a
[ERROR] ^
I am using maven 3.2.2 and running mvn install -s .settings.xml
and that resulted in missing dependencies
ERROR] The project org.springframework.cloud:spring-cloud-config:1.1.0.BUILD-SNAPSHOT (/Users/igopinatha/workspace/git/ilayaperumalg/spring-cloud-config/pom.xml) has 6 errors
[ERROR] Non-resolvable import POM: Failure to find org.springframework:spring-framework-bom:pom:4.2.0.RC2 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @ org.springframework.boot:spring-boot-dependencies:1.3.0.BUILD-SNAPSHOT, /Users/igopinatha/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.0.BUILD-SNAPSHOT/spring-boot-dependencies-1.3.0.BUILD-SNAPSHOT.pom, line 1593, column 16 -> [Help 2]
[ERROR] Non-resolvable import POM: Failure to find org.springframework.data:spring-data-releasetrain:pom:Gosling-M1 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @ org.springframework.boot:spring-boot-dependencies:1.3.0.BUILD-SNAPSHOT, /Users/igopinatha/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.0.BUILD-SNAPSHOT/spring-boot-dependencies-1.3.0.BUILD-SNAPSHOT.pom, line 1666, column 16 -> [Help 2]
[ERROR] Non-resolvable import POM: Failure to find org.springframework.integration:spring-integration-bom:pom:4.2.0.M2 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @ org.springframework.boot:spring-boot-dependencies:1.3.0.BUILD-SNAPSHOT, /Users/igopinatha/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.0.BUILD-SNAPSHOT/spring-boot-dependencies-1.3.0.BUILD-SNAPSHOT.pom, line 1678, column 16 -> [Help 2]
[ERROR] Non-resolvable import POM: Failure to find org.springframework:spring-framework-bom:pom:4.2.0.RC2 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @ org.springframework.boot:spring-boot-dependencies:1.3.0.BUILD-SNAPSHOT, /Users/igopinatha/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.0.BUILD-SNAPSHOT/spring-boot-dependencies-1.3.0.BUILD-SNAPSHOT.pom, line 1593, column 16 -> [Help 2]
[ERROR] Non-resolvable import POM: Failure to find org.springframework.data:spring-data-releasetrain:pom:Gosling-M1 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @ org.springframework.boot:spring-boot-dependencies:1.3.0.BUILD-SNAPSHOT, /Users/igopinatha/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.0.BUILD-SNAPSHOT/spring-boot-dependencies-1.3.0.BUILD-SNAPSHOT.pom, line 1666, column 16 -> [Help 2]
[ERROR] Non-resolvable import POM: Failure to find org.springframework.integration:spring-integration-bom:pom:4.2.0.M2 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @ org.springframework.boot:spring-boot-dependencies:1.3.0.BUILD-SNAPSHOT, /Users/igopinatha/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.0.BUILD-SNAPSHOT/spring-boot-dependencies-1.3.0.BUILD-SNAPSHOT.pom, line 1678, column 16 -> [Help 2]
After upgrading maven to 3.3.3, the build ran successfully
Please note I ran this on spring-cloud-config
project.
Editor Config didn't use to support eclipse and it does now.
Tweet that spawned the issue: https://twitter.com/phillip_webb/status/634106050312953857 thanks @philwebb
The grep check. https://github.com/spring-cloud/spring-cloud-build/blob/master/spring-cloud-build/pom.xml#L284-L317
I re-based my forks of spring-cloud-commons today and it will not compile because of some incompatibility with Spring Boot 1.3.0.BUILD-SNAPSHOT. The snapshots from June 26 from 14:12 onward all have the parent listed as the subject, while the source code still lists 1.2.4.RELEASE as the parent. This is causing the project not to compile. Is there a reason for this change? Is there something else I should be doing to get the project to compile again?
Isn't version missing in spring-core artifact in dependencyManagement section of pom.xml?
I have encountered the problem first when my project was processed by sonar plugin.
Using maven3 I also have a similar error when trying to install the spring-cloud-build project locally:
[ERROR] Internal error: org.apache.maven.artifact.InvalidArtifactRTException: For artifact {org.springframework:spring-core:null:jar}: The version cannot be empty. -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: org.apache.maven.artifact.InvalidArtifactRTException: For artifact {org.springframework:spring-core:null:jar}: The version cannot be empty.
at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: org.apache.maven.artifact.InvalidArtifactRTException: For artifact {org.springframework:spring-core:null:jar}: The version cannot be empty.
at org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:148)
at org.apache.maven.artifact.DefaultArtifact.<init>(DefaultArtifact.java:123)
If I set a version like below it works fine:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
<version>${spring.version}</version>
<exclusions>
<exclusion>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>${lombok.version}</version>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-dependencies</artifactId>
<version>${spring-boot.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
In .mvn/wrapper/maven-wrapper.properties
distributionUrl=https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-bin.zip
For each project.
E.g. see here: spring-projects/spring-boot#10089
Current steps are:
$ ./mvnw deploy
# later
$ ./mvnw deploy -Pcentral
See slack discussion
https://pivotal.slack.com/archives/spring-cloud/p1487362868006845
Possible workaround:
http://stackoverflow.com/questions/635154/multiple-deployments-in-maven#answer-1259799
Would like to have templates for contributions, issues, and PRs.
https://github.com/blog/2111-issue-and-pull-request-templates
I get an IllegalArgumentException when using boot 1.5.11 or 1.5.12 deps. It seems to be fixed by using version 1.16 instead of 1.14.
@spencergibb Sorry for a delay as a bad network....
I'm using spring-cloud-starter-config:1.4.0.RELEASE.
The scope of lombok dependency should be defined as provided
because you comment that it's only needed at compile time. Definitely, the compile
scope will hold all the phases after compile in maven's lifecycle.
Actually, when the scope defined as provided
, the optional element is alternative.
I prefer the logging placeholders {}
and deferred string construction. Since it is part of all spring boot loggers, there is no need worry about not having the slf4j-api
dependency.
This nice little service http://javadoc.io/ could be used to render our javadocs, but there are multiple jars per project. So there are 2 choices:
Option 1 is easier for us, but option 2 is more convenient for users.
It looks like the commit
resulted in us not getting versions specified for javadoc and antrun plugins. There are probably a couple other common ones that would be good to have as well.
This was noticed as we got another older version for antrun and our .zip file for docs in dataflow was not being generated anymore... See spring-cloud/spring-cloud-dataflow@f9fca1a
Spring Cloud Stream Docs are not being aggregated correctly when generating documentation.
http://cloud.spring.io/spring-cloud-static/Camden.SR4/#_spring_cloud_stream
When running ./release_train.sh --version Camden.SR4 --retrieveversions --ghpages
I see
asciidoctor: ERROR: loud-stream-docs/src/main/asciidoc/index.adoc: line 2: invalid part, must have at least one section (e.g., chapter, appendix, etc.)
asciidoctor: ERROR: loud-stream-docs/src/main/asciidoc/index.adoc: line 24: invalid part, must have at least one section (e.g., chapter, appendix, etc.)
asciidoctor: WARNING: loud-stream-docs/src/main/asciidoc/spring-cloud-stream-aggregate.adoc: line 1: include file not found: /Users/ryanjbaxter/git-repos/spring-cloud/scripts/docs/../stream/spring-cloud-stream-docs/core/spring-cloud-stream-core-docs/src/main/asciidoc/spring-cloud-stream-overview.adoc
asciidoctor: ERROR: loud-stream-docs/src/main/asciidoc/spring-cloud-stream-aggregate.adoc: line 3: invalid part, must have at least one section (e.g., chapter, appendix, etc.)
asciidoctor: WARNING: loud-stream-docs/src/main/asciidoc/spring-cloud-stream-aggregate.adoc: line 7: include file not found: /Users/ryanjbaxter/git-repos/spring-cloud/scripts/docs/../stream/spring-cloud-stream-docs/kafka/spring-cloud-stream-binder-kafka-docs/src/main/asciidoc/overview.adoc
asciidoctor: WARNING: loud-stream-docs/src/main/asciidoc/spring-cloud-stream-aggregate.adoc: line 11: include file not found: /Users/ryanjbaxter/git-repos/spring-cloud/scripts/docs/../stream/spring-cloud-stream-docs/rabbit/spring-cloud-stream-binder-rabbit-docs/src/main/asciidoc/overview.adoc
asciidoctor: WARNING: loud-stream-docs/src/main/asciidoc/spring-cloud-stream-aggregate.adoc: line 12: include file not found: /Users/ryanjbaxter/git-repos/spring-cloud/scripts/docs/../stream/spring-cloud-stream-docs/rabbit/spring-cloud-stream-binder-rabbit-docs/src/main/asciidoc/dlq.adoc
Go to the home page of Spring Cloud Task project. In the documentation table on the right, the API links points to the Javadoc for Spring Cloud Task. This is what I would expect.
Yet in most of the other Spring Cloud projects I've seen so far, the API links point to a wrong resource (either the the associated Github repo or the Reference documentation). For example, go to Spring Cloud Security. The API links for releases 1.1.4, 1.1.5 and 1.2.1 point to the Github repo. The API links for 1.2.2 and 1.2.3 point to the Reference documentation.
Similar behavior for (e.g. Spring Cloud Config, Spring Cloud Netflix, Spring Cloud AWS, etc.
The convention for working projects (throughout the Spring ecosystem) seems to be that javadoc is hosted at https://docs.spring.io/, e.g.: https://docs.spring.io/spring-boot, https://docs.spring.io/spring-cloud-task. For the errant sites above, there is no such javadoc, e.g.: https://docs.spring.io/spring-cloud-config, https://docs.spring.io/spring-cloud-netflix, https://docs.spring.io/spring-cloud-aws, etc., all produce 404s.
It would be helpful if all spring projects generated and deployed javadoc to docs.spring.io, with correct links to them on their associated project sites.
Wait until the 1.2.x line.
This is not working for me anymore. If I go back to RC1 it works
mavenBom 'org.springframework.cloud:spring-cloud-versions:1.0.0.BUILD-SNAPSHOT'
Likely a table
I am wondering if its correct documented thaht spring cloud brixton M4 shall be bundled with spring boot 1.3.1. I would expect spring boot 1.3.2 instead.
Is the dependency between spring cloud and spring boot managed? Can i reuse this managed dependency and how?
Cuuret approach is (toegther with spring data) to do it manually
<dependency>
<groupId>org.springframework.data</groupId>
<artifactId>spring-data-releasetrain</artifactId>
<version>${spring.data.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-parent</artifactId>
<version>${spring.cloud.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-dependencies</artifactId>
<version>${spring-boot.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
Since the projects that inherit from this parent pom are libraries, the source and javadoc artifacts should be published in Maven along with the main artifact. This enables developers to pull in the sources and documentations via their IDEs to better work with and debug the libraries.
I'm happy to submit a PR for this but its fairly simple to do:
https://maven.apache.org/plugin-developers/cookbook/attach-source-javadoc-artifacts.html
Hi!
I have some trouble updating to 1.0.0.RELEASE. I'm using my own parent pom and I'm explicitly declaring my dependencyManagement
with spring-cloud-starter-parent
. When updating, maven is having trouble finding the spring-cloud-build
module which is not published on maven central. It works when I install the dependency locally as instructed on the wiki but I'd rather link on an official build.
Also tried to add a spring-cloud-build
dependency with version 1.0.0.RELEASE in my parent pom and adding the https://oss.sonatype.org/service/local/staging/deploy/maven2
repository but from what I can see, the version is not published (yet?) on this repo.
I'm probably missing something obvious...
Thanks
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.