forked from tvaughan77/opower-parent
-
Notifications
You must be signed in to change notification settings - Fork 0
/
release_notes.txt
95 lines (74 loc) · 4.62 KB
/
release_notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
What's new in 2.3.1
Updates maven-checkstyle-plugin to 2.15
What's new in 2.3.0
Updating oss-parent to version 9 (from 7).
Replacing the inline "-P" to activate a profile with the provided "releaseProfiles" attribute in the maven-release-plugin [RE-1704]
What's new in 2.2.0
Manage curator and zookeeper versions. [DS-2053]
What's new in 2.1.2
Exposing the maven project base directory as a systemProperty available to unit and int tests. [RE-2007]
What's new in 2.1.1
Bad release (sonatype gateway timeouts in the middle of the perform; unsure of the state of that release)
What's new in 2.1.0
Adding maven failsafe plugin configuration & default plugin inclusion to opower-parent
Setting surefire configuration (e.g. Unit tests) to run in reverse-alphabetical order every other hour
Upgrading maven.resources.plugin from 2.5 to 2.6 in order to use skip parameter. [ARCH-68]
Adding plugin management for Docker plugin. [ARCH-68]
Promoting exhaustive profile up from pose-parent so that it can be used by archmage as well. [ARCH-68]
What's new in 2.0.7
Managing codahale's metrics v3.0.1
What's new in 2.0.6
Enables maven-enforcer-plugin requireReleaseDeps to verify there are no SNAPSHOT dependencies for release builds.
Updating the managed dependency for the maven-deploy-plugin from 2.7 to 2.8.1
Managing apache's commons-math3 artifact at v3.2
Updating maven-assembly-plugin from 2.2-beta2 to 2.4.1 [OPA-3736]
What's new in 2.0.5
Added the buildnumber-maven-plugin to our build and filtered any file under "./version/" with buildnumber information
Indenting 4 spaces in our maven-release-plugin
Direct descendants of 2.0.5 won't have their src/main/resources directory included in resulting artifacts. The workaround is to include the following in your POM:
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
</resource>
</resources>
</build>
What's new in 2.0.4
Removed support for cobertura plugins
Added support for JaCoCo plugins
What's new in 2.0.3
In support of sonatype's transition to Aether in the maven-3.1.1 world (see https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound):
Managed maven-enforcer-plugin to 1.3
Managed maven-shade-plugin to 2.2
Managed maven-site-plugin to 3.3
Added maven-project-info-reports-plugin plugin and managed it to 2.7
What's new in 2.0.2
Managing maven-dependency-plugin to version 2.8
Managing maven-checkstyle-plugin to version 2.11
Managing com.mchange C3P0 connection pool and supporting commons-java library
Updated POM to not use default behavior of looking for the parent POM file in ../pom.xml and instead to always use the repositories
Managing maven-release-plugin to 2.5 to get the benefits of this fix: http://jira.codehaus.org/browse/MRELEASE-812
What's new in 2.0.1
Upgrading from jetty 8.1.8.v20121106 to jetty 8.1.14.v20131031
What's new in 2.0.0
Moving from opower private nexus to sonatype public nexus. RE-1510
What's new in 1.2.4
Fixed our maven-release-plugin configuration to invoke the profile that skips tests when doing the mvn release:perform step. RE-1665
Added explicit plugin declarations for the javadoc-plugin and deploy-plugin to supress release warnings.
What's new in 1.2.3
Fixed our maven-release-plugin configuration to make it guess the released version as our tag name. RE-1661
What's new in 1.2.2
Updated maven-pmd-plugin to set targetJdk to 1.7 to avoid annoying compile-time warnings. See RE-1650
Moving pose-parent's default opower.checkstyle.checks properties up to opower-parent because archmage uses those defaults too. See NAN-239
What's new in 1.2.1
Removing the animal sniffer plugin now that we're up on Java 7. Don't need to slow *every* build down with that sanity check.
Consolidating the version.java.source and version.java.target under just plain old "version.java". We have no plans to cross-compile for a looooong time
Adding jetty to dependencyManagement and jetty-maven-plugin to pluginManagement (centralizing Jetty version in opower-parent across pose-parent and archmage)
What's new in 1.2.0
Java compiler source bumped to Java 7. Source and Target now synchronized on Java 7.
What's new in 1.1.0
Java compiler target bumped to Java 7. Source stays at Java 6 until next iteration
What's new in 1.0.1
Removed the profile that changes the compiler source and target values based on the compile-time detection of the JDK
What's new in 1.0.0
Consolidated Opower's corporate maven plugin versions in a new "opower-parent" pom