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: dev-h...@maven.apac
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 the
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 request
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
(https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=5964567)
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
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
@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
--
@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":
"https://api.nuget.org/v3/registration3/nuget.protocol
@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 thi
use this version or
> artifact anymore.
>
> I can imaging situations where you simply would like to deprecate the
> latest version of an artifact for some reason, for example for security
> reasons, without having a plan to release any newer version.
>
> Oliver
>
>
>
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
)
Regards,
Chris Kilding
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
14 matches
Mail list logo
