Repository navigation
Headlines Feb-March #69
Description
- Eclipse Mars.2
- https://www.eclipse.org/eclipse/news/4.6/M5/
- https://github.com/eclipse/buildship/wiki/Migration-guide-from-STS-Gradle-to-Buildship
Activity
Known limitations of BuildShip Gradle integration:
Bug 471728: BuildShip does not integrate with Eclipse WTP. While projects that use 'war' packaging can be created using our wizards, such projects are not officialy supported and consequently will not be correctly configured by BuildShip. Bug 482315: Running a BuildShip project with "Run As Java Application" or "Run as Spring Boot App", the runtime classpath will be incorrect and contain 'test' dependencies. Note: this is not a problem specific only to "BuildShip". "STS Gradle Integration" is also affected as this issue stems from a limitation of the Gradle Tooling API that both use. Bug 468244: BuildShip lacks a mechanism for third-party tooling providers to participate in configuring a project. STS uses such a mechanism to configure the JDT Annotation Processor when spring-boot-configration-processor is present on a project's classpath. This automatic configuration currently only works with "STS Gradle Integration" but not "BuildShip". If you make use of the '@ConfigurationProperties' annotations in your code, this means that these annotations will not be processed as part of Eclipse workspace builds unless you manually configure JDT APT.http://docs.spring.io/sts/nan/v371/NewAndNoteworthy.html
->
Groovy-Eclipse remains on the dashboard and was fully updated for Eclipse 4.5. It was not updated for Eclipse 4.5.1 so beware that if you install Groovy-Eclipse you will be downgrading your Java compiler and missing all the JDT related fixes that went into 4.5.1.
Paul Verest
January 22, 2015 at 7:13 amIt is too early to judge whether it is good news or bad.
It may turn out that there will be several companies leading under some banner like Eclipse or Apache
or smaller company will lead on, say Gradle.com
But if everybody will be saying that this is bad, so it will be.In any case, it is opened test for a newer G&G and the future is interesting.
Personally I like frameworks that are not being lead by just one big company.
Nexus OSS support npm (private, company's repositories in Nexus open-source version
http://links.sonatype.com/products/nexus/npm -> http://www.sonatype.org/nexus/2015/11/30/the-next-level-of-npm-support-with-nexus-videos/