How about generating the changelog from the PRs themselves?
https://github.com/apache/uima-parent-pom/blob/main/pom.xml#L1002-L1071
-- Richard
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands,
> On 4. Dec 2024, at 07:18, Olivier Lamy wrote:
>
> We fixed 3 issues:
> https://issues.apache.org/jira/projects/MJAVADOC/versions/12355299
The link unfortunately does not work without a Jira account.
This one should work:
https://issues.apache.org/jira/browse/MJAVADOC-823?jql=project%20%3D%
> On 16. Oct 2024, at 13:39, Elliotte Rusty Harold wrote:
>
> Could someone with admin rights on github protect the master branch on
> https://github.com/apache/maven-dependency-plugin and possibly other
> repos?
INFRA doesn't grant admin rights, but you can add a `.asf.yaml` file
to the repo
Hi
> On 14. Oct 2024, at 01:31, Dale Ogilvie wrote:
>
> The trick is, the generated maven-metadata.xml is fine when we use maven
> 3.8.5. This is a very mature build pipeline, and we have just started
> noticing this, after a switch to 3.9.x
>
> I'm taking a look at this off of our build infras
Ran into this also recently (again).
I believe a good way to solve this would be to allow overriding a dependency
inherited from the parent POM with `none` or something like that.
I tried overriding with `provided` but for some reason that
didn't seem to work.
The context was trying that I typi
Please do not make us have to create an empty directory just to please
the build tool...
-- Richard
> On 24. Sep 2024, at 23:06, Tamás Cservenák wrote:
>
> So, essentially, if you have a Maven3 project, and you want to build it
> with Maven4, you MUST have a ".mvn" directory. You must create a
> On 16. Aug 2024, at 10:24, Christoph Läubrich wrote:
>
>> I would hence restrict the use of "sub-something" to inheritance (think
>> "sub-class") and never use it to discussion aggregation. In particular,
>> "submodule" is really redundant, as a module is always below an
>> aggregator by defi
Hi,
> On 13. Apr 2024, at 14:05, Slawomir Jaranowski wrote:
>
> Such organizations must have an awareness that support for their product
> can be impossible - especially for free.
> So it looks like large tech companies don't want to pay for maintenance and
> try to require it from an Open Sourc
> On 21. Mar 2024, at 19:43, Tamás Cservenák wrote:
>
> I mean, I know what those goals do, I am just unsure WHY you needed those.
The current Apache UIMA release guidelines still list them as suggested steps
to perform before a local trial build to ensure locally cached artifacts do
not inter
Hi,
I mostly use the "analyze" (mostly the "analyze-only") and "tree" goals,
but I have also already used "copy/unpack-dependencies", "sources",
"purge-local-repository" and "resolve".
IMHO the "versions" plugin has a few functionalities that feel like could
also belong to the dependencies plugi
Hi,
> On 13. Mar 2024, at 23:58, Slawomir Jaranowski wrote:
>
> It looks as most usable will be to manage release notes also in GitHub at
> least as link to jira public url for release notes.
> Yes I know we don't have (or have old one like maven-changes-plugin)
> perfect tools to help with this
Hi Chris,
there is a quite detailed explanation of what Apache understands as a release:
http://www.apache.org/dev/release.html
Uploading the source JARs to Maven Central is afaik not enough.
What UIMA does is, we set up the build so that as part of the Maven build,
a ZIP of the checked out s
12 matches
Mail list logo
