[...]
> A comparison with other systems:
>
> - NPM puts deprecation indicators in repository metadata.
do you know where these repository metadata are visible?
> - Nuget puts deprecation indicators in repository metadata.
do you know where these repository metadata are visible?
[...]
-
dependabot[bot] opened a new pull request #59:
URL: https://github.com/apache/maven-site-plugin/pull/59
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from
3.3.0 to 3.4.0.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-utils/releases";>
Please respect developers' time. 🙏
Please refrain from sending non dev related mails and
promotional mails to dev lists.
Thanks and Regards,
Janardhan
On Thu, Jul 29, 2021 at 6:55 PM wrote:
> Hi,
> I would invite you to participate in an experiment. It requires no more
> than 20 mins and it's
Hi Chris,
I also see the need for such a feature and would like to support you as
friendly tester.
Some people in this thread pointed out, that there is already the
relocation feature. I think it addresses a different use case. BTW, I
have not been aware of it until today.
Furthermore I th
Hi,
Changing status / metadata of artifacts will break "Release Stability" of
Central Repository
Once artifacts was release should never change ...
https://central.sonatype.org/faq/can-i-change-a-component/
Another case when we don't have source code of an artifact we can do a new
pom with reloca
Hi,
I would invite you to participate in an experiment. It requires no more than 20
mins and it's rewarded with 5$. Follow the link below.
Thank you in advance
https://twitter.com/larissabrazb/status/1420334645191880707
[photo-logo]
Fernando Petrulio
PhD Student University of Zurich UZH
Dep
I think we could begin by working out some constraints for the feature...
First, I think it should be possible to deprecate (or undeprecate) an artifact
without compiling a new version of it.
This is because:
- In some legacy code situations (e.g. when the code was not checked in to
VCS), nobo
Re the Enforcer plugin rule breaking builds that passed before:
Yes, can see the problem there. There would be a couple of ways to address it:
- Add a property on the rule (equivalent to Surefire's -DskipTests) which skips
the deprecation errors, effectively restoring default warning behavior an
I have now updated the PR with batch mode in mind. Please have a look.
Note: the PR is of course in complete because it needs modification in
the Java side.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additi
https://github.com/hboutemy/mcmm-yaml could gain some additional
post-publication meta info :)
10 matches
Mail list logo
