I have now created a Jira issue to move this forward:
https://issues.apache.org/jira/browse/MNG-7238
Regards,
Chris
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
I'd like to try out some options for this feature by modifying Maven source. I
could use some help knowing which parts of Maven would need to be modified...
## maven core
I assume any new deprecation property would need to be added to
maven-repository-metadata/src/main/mdo/metadata.mdo, and
I have uploaded the feature proposal to GitHub for now at the following
location:
https://github.com/p4em/maven-enhancement-proposals/tree/main/proposals/artifact-deprecation
This is to encourage feedback from the community, since all you need is a
GitHub account to comment or make pull
I have written up a proposal document. All things being equal it would be
easier to have these things on GitHub, but if we follow 'the Apache way' I
believe the right place for this is in the Proposals section of the wiki
Hi Chris,
I created an Github organisation with one repository:
https://github.com/p4em
The repository is currently empty. For the beginning, it should be
enough to start with a freestyle document with a similar structure like
the JEP Template for Jenkins. If the process itself will work,
My GitHub user is @chriskilding
Chris
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi Chris,
I am not aware of it and I am even do not know if such an approach
causes any conflicts with the way the Maven PMC runs the project. So
please, if someone here knows any reason not to setup such repository,
please object.
@Chris: I will set it up today. Do you have a GH handle?
It looks like OGA Maven plugin has some overlap, but isn't quite the same as
the proposed feature...
In my view, deprecation is largely orthogonal to alternatives:
- Alternatives exist at all stages of an artifact's lifecycle, not just during
deprecation.
- Some artifacts are one-of-a-kind and
Isn't this exactly what the Old GroupIds Alerter - Maven Plugin[1] is doing?
Only instead of adding metadata to Central it keeps a list [2] of
replaced/deprecated artifacts.
[1] https://github.com/jonathanlermitage/oga-maven-plugin
[2]
@Oliver:
Yes, a GitHub repo to write some kind of spec for this feature would be great.
Is there an existing Maven enhancement proposals repo we can use (along the
lines of what the Jenkins project does in https://github.com/jenkinsci/jep), or
is a new one needed?
Chris
Hi,
I was previously just lurking here but following the discussion with
interest. Here are my 2 cents:
Chris Kilding wrote:
> 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
Hi all,
I would like to suggest to write a small specification of the feature
you brought up. I have somethink in mind similar to the JEP process for
Java.
I could create a repo at Github, so that we can work there on the
feature description and ask other people to review it or to
@Hervé:
The NPM `deprecated` property exists in NPM registry package metadata. (Some of
this is derived from package.json, but it is not the same as package.json.)
It is described here:
https://github.com/npm/registry/blob/master/docs/responses/package-metadata.md
The library which NPM itself
@Hervé:
The NuGet `deprecation` object exists in the NuGet package metadata.
It is described here:
https://docs.microsoft.com/en-us/nuget/api/registration-base-url-resource#package-deprecation
Example snippet from the docs:
{
"@id":
Hi Chris,
working for some clients in the last years, I saw nearly all of them
struggling with their dependency management. Sad, but true.
I see various use cases for the feature you propose, not only in the
public space. This feature could be also very interessting for
companies, if they
@Sławomir:
I know the POM and the contents of the artifact itself don't change after
publication (at least on Central). This is one reason I suggested putting
deprecation indicators in something like maven-metadata.xml instead. Are you
saying that maven-metadata.xml is immutable as well?
I
Hi,
@Oliver:
Glad of the help :) My definition of 'deprecated' would be roughly 'this
artifact is not actively developed and should not be used any more'.
One example I have in mind for deprecation is Joda Time - a library which was
superseded years ago by java.time in Java 8 and Android API
[...]
> 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?
[...]
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
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
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),
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
https://github.com/hboutemy/mcmm-yaml could gain some additional
post-publication meta info :)
> There are definitely several good questions to be answered about what
> exactly the feature would look like, so questions and comments are welcome
> :)
sure, many questions...
here are my first thoughts:
- we have relocation, which is far from well known and easy to use, but that
is probably
Hello,
I would like to propose a new Maven feature: dependency deprecation indicators.
In a nutshell, the idea is to let maintainers set a 'deprecated' metadata
indicator on a Maven artifact in a repository. This will indicate to users that
the artifact should no longer be used.
The Maven CLI
25 matches
Mail list logo
