Hi,
We are in progress with switching issues from Jira to GitHub,
Current status is reported on page [1]
We should try to work with the new issue system, even if some of the
projects still use jira we should think about GitHub issues.
There is a GitHub Conventions [2] - please read it (especial
Good morning,
The vote has passed with the following result:
+1: Sylwester Lachiewicz, Slawomir Jaranowski, Hervé Boutemy, Matthias
Bünger
PMC quorum: reached
I will promote the source release zip file to the Apache distribution
area and the artifacts to the central repo.
---
Matthias
Hi,
We use in Maven projects default tag name for release as:
{project.artifactId}-{project.version}
Such format will be ok for project releasing from one svn repository
... but now we use separate git for each project.
What do you think about changing it to something like: v{project.version}?
I
-1. Maven is complex enough (really too complex) already. Anything
that makes it more so feels unwise. I doubt this feature would carry
its weight at this late point in time.
I'm also extremely skeptical of efforts to build new language level
features like a separation between API and implementati
+1
On Wed, Mar 5, 2025 at 12:17 PM Guillaume Nodet wrote:
>
> We solved 108 issues since rc-2.
> https://issues.apache.org/jira/projects/MNG/versions/12355493
>
> Staging repositories:
> https://repository.apache.org/content/repositories/maven-2278/
> https://dist.apache.org/repos/dist/dev/
Hi all,
While I do like the simple rules of Maven 3 scopes[1], I often lack the
flexibility that Gradle's `api` and `implementation`[2] configurations
provide.
With the separation of build and consumer POMs it should be probably be
easy to have some `compile` dependencies in the build POM be
+1 (nb)
Many thanks for this one :)
Tony.
Le ven. 7 mars 2025 à 9:08, Slawomir Jaranowski
a écrit :
+1
On Wed, 5 Mar 2025 at 12:17, Guillaume Nodet
wrote:
We solved 108 issues since rc-2.
https://issues.apache.org/jira/projects/MNG/versions/12355493
Staging repositories:
https:/
+1
On Wed, 5 Mar 2025 at 12:17, Guillaume Nodet wrote:
>
> We solved 108 issues since rc-2.
> https://issues.apache.org/jira/projects/MNG/versions/12355493
>
> Staging repositories:
> https://repository.apache.org/content/repositories/maven-2278/
> https://dist.apache.org/repos/dist/dev/mav
Howdy,
not a "solution" but just to throw another bone:
Takari Lifecycle had (somewhat similar) support for this since 2010s:
http://takari.io/book/40-lifecycle.html#enforcing-dependency-usage-during-compilation
But instead of forcing this onto publishers (to specify is something
"api" or "implem
+1
Delany
On Wed, 5 Mar 2025 at 13:17, Guillaume Nodet wrote:
> We solved 108 issues since rc-2.
> https://issues.apache.org/jira/projects/MNG/versions/12355493
>
> Staging repositories:
> https://repository.apache.org/content/repositories/maven-2278/
> https://dist.apache.org/repos/dist
Hi,
Think with the scope rework in maven 4 the feature is there, it is just not
yet consumed.
How it will look like will mainly depend on the integration (script in
gradle land) so not sure anything is missing except an opiniated scope
definition with its sibling extension.
Romain Manni-Bucau
@rm
+1
We will need to adjust plugins to changes in API
Sylwester
pt., 7 mar 2025 o 15:12 Tamás Cservenák napisał(a):
> +1
>
> On Wed, Mar 5, 2025 at 12:17 PM Guillaume Nodet wrote:
> >
> > We solved 108 issues since rc-2.
> > https://issues.apache.org/jira/projects/MNG/versions/12355493
> >
>
+1
Arnaud Héritier
GitHub/ASF/... : aheritier
On Wed, Mar 5, 2025 at 12:15 Guillaume Nodet wrote:
> We solved 108 issues since rc-2.
> https://issues.apache.org/jira/projects/MNG/versions/12355493
>
> Staging repositories:
> https://repository.apache.org/content/repositories/maven-2278/
>
13 matches
Mail list logo
