aboutsummaryrefslogtreecommitdiff
path: root/value/pom.xml
AgeCommit message (Collapse)Author
2020-07-08Set version number for auto-value-parent to 1.7.4.upstream/auto-value-1.7.4upstream-auto-value-1.7.4Éamonn McManus
2020-04-15Update versions of Truth and Compile-testing.Sean Sullivan
Closes https://github.com/google/auto/pull/831 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=306447364
2020-04-10Release the SerializableAutoValue extension.alvinlao
RELNOTES=Release the SerializableAutoValue extension. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=304211473
2019-11-08Be more explicit about which Java versions AutoValue supports. The compiler ↵emcmanus
must be at least Java 8, but it can generate code for Java 7. Also update gwtserializer/pom.xml to specify Java 7 rather than Java 6. Compiling with -source 6 is no longer supported in recent Java versions. Fixes https://github.com/google/auto/issues/771. Closes https://github.com/google/auto/pull/524. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=279157033
2019-10-04Update dependencies:cpovirk
- mvn versions:use-latest-releases - mvn versions:update-properties The immediate motivation is that we just broke Caliper's build by updating Dagger, which requires a newer version of JavaPoet than the one currently used by AutoValue (which, sadly, is the version selected by Maven). ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=272889328
2019-06-06Update to Truth 0.45, and address deprecations.cpovirk
Renames may include: - containsAllOf => containsAtLeast - containsAllIn => containsAtLeastElementsIn - isSameAs => isSameInstanceAs - isOrdered => isInOrder - isStrictlyOrdered => isInStrictOrder The other major change is to change custom subjects to extend raw Subject instead of supplying type parameters. The type parameters are being removed from Subject. This CL will temporarily produce rawtypes warnings, which will go away when I remove the type parameters (as soon as this batch of CLs is submitted). Some CLs in this batch also migrate calls away from actualAsString(). Its literal replacement is `"<" + actual + ">"` (unless an object overrides actualCustomStringRepresentation()), but usually I've made a larger change, such as switching from an old-style "Not true that..." failure message to one generated with the Fact API. In that case, the new code usually contains a direct reference to this.actual (a field that I occasionally had to create). Another larger change I sometimes made is to switch from a manual check-and-fail approach to instead use check(...). And sometimes I just remove a withMessage() call that's no longer necessary now that the code uses check(...), or I introduce a check(...) call. (An assertion made with check(...) automatically includes the actual value from the original subject, so there's no need to set it again with withMessage().) Finally, there's one CL in this batch in which I migrate a Correspondence subclass to instead use Correspondence.from. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=251495286
2019-05-05Stop using auto-parent.cpovirk
It's released separately from all its children, so any updates we make there don't take effect until we make a release and update the child projects to use that. This requires pushing various configuration down into the child projects. Doing so makes the recent attempted update to Truth 0.44 actually take effect. Also, update Compile-Testing to the newly released version, which actually works with Truth 0.44. That upgrade exposes that AutoValue was relying on a transitive dependency on Truth8, which was removed in the latest Compile-Testing, so I've added explicit deps. https://github.com/google/compile-testing/commit/43a513ab14a5b4ab5810a13e14d8cb763546ab5d Also, I removed an explicit version for compile-testing in the AutoValue functional tests. That explicit version may or may not have been needed before, but it shouldn't be now. Likely it would make sense to remove more versions explicitly specified elsewhere. (Additional possible future work: Put deps on other Auto projects (like when AutoService depends on AutoCommon) into <dependencyManagement>.) Finally, I added some <url> values, since Maven has been generating bogus ones all along (by appending the subproject name to the parent URL, producing URLs something like "https://github.com/google/auto/auto-value"). ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=245779060
2019-04-29Update copyrights to say Google LLC instead of Google Inc.emcmanus
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=244250754
2018-12-03Update to auto-parent 7 to get the latest version of Guavaronshapiro
Along the way, also clean up some explicit versions that are set in auto-parent Fixes https://github.com/google/auto/issues/683 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=223540267
2018-03-19Make AutoValue releasable againronshapiro
- Give each pom a parent so all versions can be set accordingly with mvn versions:set - Add the src/it/* modules to the parent pom modules list - But don't release them, just build them - Mark auto-service as provided scope - Fix some javadoc that is causing Maven to barf RELNOTES=n/a ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=189393305
2018-03-12Create an auto-value-annotations artifact separate from the processorronshapiro
Fixes https://github.com/google/auto/issues/268 I followed the instructions in https://maven.apache.org/guides/mini/guide-using-one-source-directory.html because it seemed like the easiest way forward without moving around any files. RELNOTES=`@AutoValue`, `@AutoAnnotation`, `@AutoOneOf`, and `@Memoized` are now in a separate artifact, `auto-value-annotations`. This allows users to specify the annotations in compile scope and the processor in an annotation processing scope, without leaking the processor to a release binary. To upgrade to this version of auto-value, you'll need to add this new artifact as a dependency. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=188505001
2018-01-25Don't include AutoValue's sources in its Maven jar. It looks as if they have ↵emcmanus
always been present, as a side-effect of the <resources> clause. That clause is only there so that the *.vm files are present. A new test ensures that there are no *.java files any more. I believe this is the reason for the "Implicitly compiled files were not subject to annotation processing" warning that has been causing tests to fail on Travis occasionally. The compiler finds com/google/auto/value/AutoValue.java in the autovalue jar. If the timestamp of that entry is not older than the com/google/auto/value/AutoValue.class alongside it, the compiler recompiles it, and by default outputs the warning. RELNOTES=Don't include sources in autovalue.jar. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=183130194
2018-01-24Use latest versions of auto-common (0.10) and auto-service (1.0-rc4).dpb
RELNOTES=n/a ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=182924975
2018-01-18Update references to auto-parent 6.dpb
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=182218347
2017-12-14Update version of auto-common to 0.9.dpb
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=178808754
2017-12-04Use dependency and plugin management from auto-parent v5. Use latest ↵dpb
dependencies and plugins for the functional test poms (which don't use auto-parent). ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=177592315
2017-11-15Replace truth.FailureStrategy with truth.FailureMetadata in custom Subjects.jijiang
Also changed truth.SubjectFactory to truth.Subject.Factory (plain renaming) and use method reference instead of anonymous class to create the factory when applicable. FailureMetadata, an opaque object to its users, is introduced to replace FailureStrategy in in custom Subject in order to resolve some existing flaws of FailureStrategy as well as enable new features to be added to Truth. New API is available in Truth-0.36, if there is a build/pom.xml, it's also updated to use this version. RELNOTES=n/a ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=175302659
2017-10-18Avoid including javax/annotation/* in the shipped AutoValue jar. Add a ↵emcmanus
Google-internal test that checks for stray unshaded entries like those in the jar. Fixes https://github.com/google/auto/issues/537. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=172528313
2017-09-28Update the AutoValue snapshot version from 1.5-SNAPSHOT to 1.6-SNAPSHOT. ↵emcmanus
This should have been done when 1.5 was released. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=169493872
2017-08-22Update the AutoValue pom.xml with latest versions.emcmanus
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=165389482
2017-08-03Migrate TestVerb.withFailureMessage to use withMessage instead and update ↵jijiang
truth dependency version to 0.34. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=162407532
2017-04-21Update AutoValueProcessor to use Java 8 constructs now that we can.emcmanus
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=153774612
2017-04-20Update AutoValue's Maven dependencies to latest versions. We were staying on ↵emcmanus
earlier versions while we were preserving the ability to build on Java 7, but now that that's gone we should update. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=152392370
2017-04-06Delete the asm dependency. It was needed for a hack to work around an ↵emcmanus
Eclipse method-order bug. That hack has been deleted. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=152284475
2017-03-22Update AutoValue snapshot version now that 1.4 has been released.emcmanus
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=150397728
2016-12-21Tweak AutoValue's Maven configuration so it can work with Java 7 builds, by ↵emcmanus
choosing an older version in that case and excluding tests that require the newest version. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=142697281
2016-12-21Remove the exclusion of Truth from the dependencies of Compile Testing in ↵emcmanus
the AutoValue POM. We do in fact want to use the later of AutoValue's and Compile Testing's versions of Truth. Otherwise we can (and in fact did) get hard-to-debug linkage errors. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=142595335
2016-12-20Fix AutoValueProcessor so it works even if an old version of @AutoValue is ↵emcmanus
in the -classpath. Add a test for this configuration. Also fix a place where we were incorrectly comparing TypeMirrors using .equals, which is explicitly specified as being unreliable. Fixes https://github.com/google/auto/issues/414. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=142496146
2016-11-09Suppress javadoc doclint in maven, when running on java8 which both ↵cgruber
introduces the doclint, and also introduces the flag to turn it off. Done in a profile so it doesn't break pre-java8 javadoc commands which don't have this option. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=136389313
2016-11-09Upgrade auto-value to use the released auto-common.cgruber
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=136367746
2016-10-12Update ASM usages for Java 8:cushon
1. Set the API level to `ASM5`. ASM requires that all visitors set the `ASM5` API level when visiting Java 8 bytecode. Failing to do so will result in an error when encountering any Java 8 bytecode features. 2. Change any `visitMethodInsn` methods to implement the newly added overload [of that name][1]. The new overload is called by ASM after the API level change; the old one is ignored. [1]: http://asm.ow2.org/asm50/javadoc/user/org/objectweb/asm/MethodVisitor.html#visitMethodInsn-int-java.lang.String-java.lang.String-java.lang.String-boolean- ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=135170390
2016-09-21Replace the use of Elements.overrides in ↵emcmanus
MoreElements.getLocalAndInheritedMethods with a reimplementation that should work with Eclipse. Fixes https://github.com/google/auto/issues/372. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=133716523
2016-09-08Add @Memoized to the open-source AutoValue project.dpb
Extracted MemoizedMethodSubject and MemoizedMethodSubjectFactory in order for the Maven tests to work. ¯\_(ツ)_/¯ ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=132325012
2016-08-29Change the AutoValue version from 1.3-SNAPSHOT to 1.4-SNAPSHOT now that 1.3 ↵emcmanus
has been released. Also change AutoValue's dependency on AutoCommon to 0.6 rather than 1.0-SNAPSHOT. If AutoValue later needs to pick up changes from a more recent AutoCommon, we should make an AutoCommon 0.7 at that point. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=131653094
2016-08-29Update the integration test pom.xml files to use a version of ↵cgruber
maven-jar-plugin that isn't broken on ubuntu, causing multi-minute jar times. And while here, bump them all to 2.6 (2.5+ is fine, but may as well, and may as well be consistent.) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=131537002
2016-05-10Add logic to AutoValue to detect the confusing case where you think you are ↵emcmanus
using JavaBeans conventions (like getFoo()) but you aren't because at least one method isn't. Then a Builder setter like setFoo will be rejected because it would have had to be called setGetFoo. This change detects that this might have happened and shows a list of the methods that prevented the JavaBeans conventions from being applied. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=119569372
2016-03-21Bump auto-value development version to 1.3-SNAPSHOTcgruber
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=117743106
2016-03-21Rely on Guava 19.0 and use CharMatcher.whitespace() since ↵cgdecker
CharMatcher.WHITESPACE is now soft-deprecated and will be removed in a future version of Guava (improves performance on android - not relevant to auto-value, but still nicer). ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=116549017
2016-01-10Package com.google.* classes under autovalue.shaded.com.google.*ronshapiro
Previously, com.google.common classes would end up in autovalue.shaded.com.google.common.common ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=108560677
2015-10-21Use a maven property to harmonize guava versions.cgruber
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=104453482
2015-09-11As suggested by @jbgi, change the Maven build for AutoValue to use the ↵cgruber
org.immutables.tools version of the Maven Shade Plugin, which supports prefixing the simple names of shaded classes with $. This means that people can safely use the AutoValue with their IDEs, without having code completion ever show the shaded classes. ------------- Created by MOE: https://github.com/google/moe ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=102089611
2015-08-05Bump dependency versions.cgruber
2015-08-04Switch AutoValueProcessor over to using the EscapeVelocity subset of Apache ↵emcmanus
Velocity instead of Velocity itself. ------------- Created by MOE: http://code.google.com/p/moe-java MOE_MIGRATED_REVID=95217882
2015-05-19[release] Restore snapshot development version.Christian Edward Gruber
2015-05-19[release] Prepare to release AutoValue 1.1.Christian Edward Gruber
Bump release version in pom.xml, and update snapshot dependencies to released dependencies.
2015-04-24Bump projects to use the new parent pom, and (therefore) the sonatype ↵Christian Edward Gruber
release profile.
2015-03-17Change Maven shading for AutoValue so that org.apache.commons is shaded.Éamonn McManus
I previously believed this was not possible due to classes being loaded by name, but it turns out that it is, provided we avoid tickling a bug in shading related to string constants.
2015-02-03Change the version of AutoValue from 1.0-SNAPSHOT to 1.1-SNAPSHOT.Éamonn McManus
2015-01-21Make AutoValue depend on AutoCommon 1.0-SNAPSHOT until we make a new release.Eamonn McManus
2015-01-21Use Guava 18 so FluentIterable.join(Joiner) can be used, and bump jar ↵Christian Edward Gruber
plugins to 2.5 to be faster on ubuntu
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-08 15:05:49 +0000