@darcelle424@SapereVincent@PicturesFoIder It isn't built to hold weight. I'm a garage, you might be carrying something.
If you do something like this, don't let the stairs be held up by the sheer force of two little screws.
I have tried repeatedly over the last week to request a delivery of propane from @SuburbanPropane, only to have no record of the request on my account.
Now I made a request from an email. We'll see if that works.
At the leased tank jacked up prices, they should be salivating.
The maven-plugin-api doesn't actually need it directly. But indirectly, maven-model needs it.
I don't know what the resolution would be, but maybe Maven needs a "private" dependency scope. Or maven-plugin-api shouldn't have the dependency.
I would love to submit a bug to the @TheASF Maven project, but apparently the issue tracker registration is turned off. It says to send a message to the project private mailing list, but that got no response.
Maven v3.9 removed plexus-utils (fine), but v3.9 of the maven-plugin-api still includes it as a dependency. Seems archaic to make all plugin developers that use the dependency to explicitly exclude plexus-utils.
v1.0.3 is out. And it is reasonably solid. Supports standard Javadoc format and tags: param, return, throws, see, author, version, and since. Also inline link tag.
And you can write your comments in markdown and they translate over nicely.
It finds all your Spring annotated and named beans (via Component). And then all the public methods. And grabs the important Javadoc comments and tags. Then writes it out in Git friendly markdown files.
Great for reference when writing processes in APS.
Rich McKnight, Software Systems Architect: "Do not wait for your ideas to be perfect to share them. Bring that good but imperfect idea and allow it to be refined. Too many good ideas never see the light of day because of the fear of rejection." https://t.co/GlltTZfiEX