Page Comparison

...

• Ongoing work on javadocs

  • Any javadocs used by other projects are deployed now under /api

  • Site jobs for both branches converted to build and deploy the aggregate javadoc jar for snapshots

    • Significant variability encountered using the Maven options box vs. the command line box

    • Unable to find a simple way to get Maven to build and deploy just the javadoc, it wants to build all the code and deploy all the jars it built. This means for now the site jobs will actually deploy another snapshot. It doesn’t build all the individual javadocs like the main build profiles do, so the jobs are still pretty fast.

  • Release profile used by nightlies no longer include any javadoc goals, verified docs not being deployed to Nexus nightly anymore

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-2183

  • We should have some fairly self-contained ways to generate hashes needed for inline scripts

  • Straddles the bug/enhancement line vis a vis when/how to release changes, OTOH a minor update is “freeing”

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-392

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-2187

  • A regression but does not break (proper) upgrades (i.e., you know it’s going to bite people)

Tom

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key GEN-333

  
  Problem being bin/install.sh is not being made executable if the sign-snapshots profile is active
  Cause seems to be that Maven plugins are called once with multiple executions
  So activating the sign-snapshots plugin calls make-files-in-bin-executable after the assembly is built
  Workarounds ? maybe use the assembly plugin to change the filemode
  

...