Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12344661&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-1623/
https://repository.apache.org/content/repositories/maven-1623/org/apache/maven/shared/mave
Hi,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345175&styleName=Text&projectId=12317922&styleName=Text
** Improvement
* [MSHARED-879] - make build Reproducible
** Dependency upgrade
* [MSHARED-944] - Set minimum Maven version to 3.1.1
There are s
Understood, and so I try to make all Apaches understand that we could have a
subdomain apache.oss.sonatype.org with dedicated infrastructure, just as the
Eclipse Foundation has with jakarta.oss.sonatype.org, to get rid of these
troubles. :-)
-Markus
-Ursprüngliche Nachricht-
Von: Matth
https://maven.apache.org/maven-logging.html needs to be updated,
but also some plugins where changes were already made.
This was from slack: https://issues.apache.org/jira/browse/MNG-6931
And plugins pulling in slf4j directly happen all the time:
https://github.com/apache/maven-artifact-plugin/pu
Markus,
> which is just one of several ways onto Maven Central
The only way for OSS developers not part of big infrastructures.
> As we all do open source and OSSRH is free, maybe we should simply accept
that free stuff might just have some outages currently.
I am not blaming Sonatype at all, on
Mojo scope is clearly the abstraction, no doubt here.
I think extension too by design as explained but guess we never discuss it.
Personally I'd rather generalize the abstraction since we reimpl slf4j -
even if fork is trivial - anyway so maybe we should finally shout something
which never matched
It is not only an extension case.
For example I can write Mojo like:
@Mojo(name = "example")
public class ExampleMojo extends AbstractMojo {
@Inject
private MyService myService;
@Override
public void execute() {
}
}
and
@Named
public class MyService {
@Inject
priv
If you follow the official twitter channel then you will learn that the problem
is simply the internal load of the free OSSRH service, which is just one of
several ways onto Maven Central. At the Eclipse Foundation for example, we have
our own Sonatype-powered instance with separate workload lim
Maven deploy plugin works but nexus one automates some stages (like closing
the staging and releasing it without having to do iy manually after the
upload).
Le ven. 22 janv. 2021 à 18:36, Matthieu Brouillard
a écrit :
> Hi Romain,
>
> Thanks for the hint, I do not use the 'maven-deploy-plugin' t
Hi Romain,
Thanks for the hint, I do not use the 'maven-deploy-plugin' to reach
central but I use 'nexus-staging-maven-plugin' as described on
central/sonatype documentation [1].
The issues are not coming from uploads but from internal
publication/staging inside the OSSRH infrastructure as far as
Hi
AFAIK maven enables to configure the "uploader" and even to switch it
(through wagon) so you can use any retry mecanism...but will not solve a
broken server issue, will just fail later from my experience.
Le ven. 22 janv. 2021 à 15:47, Matthieu Brouillard
a écrit :
> Hi Brian & list,
>
> Sor
Hi Brian & list,
Sorry but I have to insist on the fact that again yesterday and today OSSRH
is mostly unavailable.
I again tried, like others, to deploy artifacts and it failed.
After pinging on twitter, the OPs have provided again a feedback that
deployments have pilled [1] explaining the timeou
Do it means if we represent our classloading structure, all loaders on top
of mojo use slf4j and others our maven abstraction.
Sounds ok to me except for extensions which are not in maven land so
subject to slf4j api breaking changes and undefined/ambiguous context -
which is never true for maven c
I'm not so sure about this, it probably depends on the context.
I think we should assume that JSR330 component are not aware of their context.
They should not require a Maven context, hence in such case it makes sense to
use SLF4J API, while the application selects the logger implementation.
Thi
I agree that we should advice that Maven Plugins should use the provided
logging API.
I can't find the ticket anymore, but I've created one where it should be
possible to scope the debug-logging for a specific goal.
Most of the time you're interested in the debug logging of the last failed goal
awesome! I'll focus on maven-shared-utils and see if we can do a release soon.
thanks,
Robert
On 21-1-2021 18:37:03, Guillaume Nodet wrote:
Hi everyone
Yesterday, I've released Jansi 2.2.0 which incorporates a few bug fixes /
enhancements.
I pushed a few PRs to enhance the terminal support in Ma
elharo merged pull request #55:
URL: https://github.com/apache/maven-doxia/pull/55
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to t
17 matches
Mail list logo
