Log for pom.xml

• [maven-release-plugin] prepare release 0.0.4 by Caio 6 years ago
• Bump gula-bom to 0.0.3 by Caio 6 years ago
• [maven-release-plugin] prepare for next development iteration by Caio 6 years ago
• [maven-release-plugin] prepare release 0.0.3 by Caio 6 years ago
• [maven-release-plugin] prepare for next development iteration by Caio 6 years ago
• [maven-release-plugin] prepare release 0.0.2 by Caio 6 years ago
• Bump gula-bom to 0.0.2 by Caio 6 years ago
• [maven-release-plugin] prepare for next development iteration by Caio 6 years ago
• [maven-release-plugin] prepare release 0.0.1 by Caio 6 years ago
• Make the Loader not care about cerberus.properties by Caio 6 years ago
• Use a parent pom so I don't repeat myself too much by Caio 6 years ago
• Make maven plugin versions explicit by Caio 6 years ago
• Configure maven-release-plugin for a git-based release 💬 by Caio 6 years ago

  This, by the way, is the only sane way of using this plugin with git
  in my opinion: I get to keep control of everything, nothing is
  even pushed without my consent.
  

• Package a test jar with a useable Util class by Caio 6 years ago
• Bump dependency versions 💬 by Caio 6 years ago

  Nothing notable in the changelogs.
  

• Cleanup/adapt pom.xml 💬 by Caio 6 years ago

  Drop everything spring-boot, add back what the parent was pulling
  for us automatically.
  

• Update to Tablier 0.2.3 💬 by Caio 6 years ago

  Error pages now look like Index. No more ZeroResults pages.
  
  This patch contains whitespace changes, the `-w` switch should show
  how trivial it actually really is.
  

• Declare mockito dependency explicitly 💬 by Caio 6 years ago

  The spring-boot-starter-test already pulls this dependency in, but now
  that I'm using it outside of the `.boot.` namespace I'd like it
  explicit.
  

• Bump to tablier 0.2.2 💬 by Caio 6 years ago

  Things are a lot simpler now :-)
  

• Drop unused property by Caio 7 years ago
• Revert "Stop using spring-boot-starter-parent as parent" 💬 by Caio 7 years ago

  This reverts commit 0a72f9527905c4ca3af4e0577eaac6761e2894bf.
  
  I've done it and decided to go back. These are the things I had to
  do to make the multi-project setup happen:
  
  1. Move the `co.caio.cerberus.boot` into a separate module (web)
  2. Move the rest into a library module (core)
  3. Create a parent pom with shared dependencies, move the
     non-shared dependencies around so that they belong to their
     respective module
  4. Make the core library ship a test jar (as simple as activating
     the `test-jar` goal from maven-jar-plugin) so that both modules
     have access to the sample recipes and utilities
  5. Change Util.java (test scope) to use .getResourceAsStream() so
     that we can static load it from #3's jar (*shrug* this is so
     poorly documented that I'm not really sure why .getResource()
     wasn't working.
  
  (NOTE that this means there's a little bit of the strong coupling
  I wanted to avoid by moving to multi-modules in the first place-
  At least it is just for tests...)
  
  After that was done I wanted to ship the `core` module separately
  so that the `web` module would only evolve when I released a new
  core version (same way as I'm interacting with `tablier`); This
  led me to start fighting with `mvn release:*` since I doesn't
  like SNAPSHOTS - so my solution would be to not have the `web`
  module as part of the multi-module project, which meant that
  the split was pretty much useless as I wouldn't be sharing things
  from the parent POM unless I started being sillier...
  
  Anyway, while doing all this and questioning my sanity I decided
  that the best way would be to just split the repository and be
  done with it. If I revisit this I'll probably:
  
  1. Split the `boot` package into it's own repository; And
  2. Create a separate project which just ships a parent pom
     in case I really want/need to share the pluginManagement
     section
  
  But that's a story for another day, I've spent time with this for
  no particular gain (besides understanding a bit more about maven,
  so there's that). The result of this saga is in the
  `dropped-multi-module` branch in case I ever need to look back.
  

• Stop using spring-boot-starter-parent as parent 💬 by Caio 7 years ago

  I'll be moving this to a multi-module project and I don't
  want the parent to pull all of this into the core.
  
  I hadn't realized how many things the starter configures
  by default. Damn. Thanks <3
  

• Render recipe URLs with all search parameters 💬 by Caio 7 years ago

  This patch switches from using crawlUrl() to using the /go/
  route and appends all search parameters to said urls following
  the idea outlined in b31fb8d995
  

• Point at the released tablier 0.2.0 by Caio 7 years ago
• Bump to spring-boot 2.1.3 by Caio 7 years ago
• Prepare for tablier 0.2.+ 💬 by Caio 7 years ago

  Type-checked templates makes my life so much easier <3
  

• Build the index via `mvn exec:exec@build-index` 💬 by Caio 7 years ago

  This patch configures an unbound execution (with `build-index` for id)
  to call the Loader. This is a better approach than the previous one
  of using profiles since this avoids the bad interaction when trying
  to do things like `mvn clean compile -Pindex` (which would fail
  the flatbuffers code generation).
  

• Upgrade to lucene 7.7.0 💬 by Caio 7 years ago

  `IndexWriter.numDocs` is now deprecated in favour of `getDocStats`,
  so this patch adjusts our usage.
  

• Default to the EnglishAnalyzer 💬 by Caio 7 years ago

  These IndexConfiguration.* thingers can probably be derived from
  the Indexer, so FIXME maybe.
  

• Bump junit to 5.4.0 by Caio 7 years ago