You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2005/06/22 20:43:52 UTC
[jira] Created: (MNG-507) Add deprecation information to POM
Add deprecation information to POM
----------------------------------
Key: MNG-507
URL: http://jira.codehaus.org/browse/MNG-507
Project: Maven 2
Type: New Feature
Components: maven-model
Reporter: Carlos Sanchez
Priority: Critical
Fix For: 2.0-beta-1
Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-507) Add deprecation information to POM
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=all ]
Brett Porter updated MNG-507:
-----------------------------
Priority: Blocker (was: Critical)
> Add deprecation information to POM
> ----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-507) Add deprecation information to POM
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=comments#action_42914 ]
Carlos Sanchez commented on MNG-507:
------------------------------------
This deprecation info is related to repository management. There are a lot of wrong named groupIds, artifactIds, versions, etc. that we need to provide new ones, but without removing the old ones to avoid breaking builds. e.g. all the javax.* related jars spreaded through different groups.
Especially if we want to migrate to the new groupIds schema (mirroring package names) this is a must, and should be made before going beta.
> Add deprecation information to POM
> ----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-507) Add deprecation information to POM
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=comments#action_42892 ]
John Casey commented on MNG-507:
--------------------------------
After talking with Trygve and Jason more on this, it seems to me that deprecation information as such is not a good idea.
Let's start with the introduction of deprecation information to the project in question. It amounts to republishing the metadata for that project, and (provided the POM isn't a snapshot) will mean that users won't get the updated POM without removing their own local copy first.
Another alternative would be to provide "replaces" information rather than "deprecated" information. This would be in the form of metadata which would be placed alongside the replaced artifact in the repository, and would contain a pointer to the replacement artifact. Since the groupId is assumed to be under the authority of that project, placement of this metadata must be done with the consent of the project owner(s) (whoever publishes to that groupId)...to avoid the case of my project simply claiming to replace yours and thereby declare yours defunct or inferior.
What it really gets back to is the question: What's the purpose of this proposed new feature?
Carlos, can you give an example or two, and especially explain the priority of the issue?
> Add deprecation information to POM
> ----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-507) Implement POM repository relocation
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=all ]
Brett Porter closed MNG-507:
----------------------------
Resolution: Fixed
now, to start moving things in the repository :)
this will have to wait until the beta-2 release, then we can remove the jars from jdbc:jdbc, for example.
> Implement POM repository relocation
> -----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-507) Add deprecation information to POM
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=comments#action_42922 ]
Carlos Sanchez commented on MNG-507:
------------------------------------
I think we shouldn't care. When they try to upgrade a jar to a new version they will see it,
> Add deprecation information to POM
> ----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-507) Implement POM repository relocation
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=all ]
Brett Porter updated MNG-507:
-----------------------------
Description:
Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
was:
Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
Environment:
Summary: Implement POM repository relocation (was: Add deprecation information to POM)
I don't think we should do a deprecation of artifacts, as of the chicken and egg problem, so lets just aim for the supersedes functionality in a later version. We can, however, do pointers which are similar and I think what is intended in the discussion so far: a POM is moved and replaced with a POM that points to the new one with a message. This makes historical builds work with a warning (from a clean repository).
Suggested syntax:
<distributionManagement>
<relocation>
<groupId>...</groupId>
<artifactId>...</artifactId>
<version>...</version>
<message>...</message>
</relocation>
</distributionManagement>
Version would match by default.
> Implement POM repository relocation
> -----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-507) Add deprecation information to POM
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=comments#action_42891 ]
Trygve Laugstol commented on MNG-507:
-------------------------------------
Most Linux distributions have solved this a long time ago so I think we definitely should take a look into how they're doing this. Your suggestion do make sense to me.
> Add deprecation information to POM
> ----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-507) Add deprecation information to POM
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=comments#action_42919 ]
John Casey commented on MNG-507:
--------------------------------
What about the users who have already downloaded these poms? They won't get the deprecation information. Do we care?
> Add deprecation information to POM
> ----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-507) Add deprecation information to POM
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=comments#action_42954 ]
Brett Porter commented on MNG-507:
----------------------------------
there is already an open bug for "replaces" (I called it "supercedes").
I'm not sure what the best here. Carlos is talking about pointers where it is actaully directed elsewhere, which is probably a little different to deprecation too.
It might be better to look at repository level metadata here, which can be updated more frequently, in a similar way to the plugin mappings. 2.1?
> Add deprecation information to POM
> ----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-507) Add deprecation information to POM
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=comments#action_42957 ]
Carlos Sanchez commented on MNG-507:
------------------------------------
Why don't start just with deprecation info in 2.0 and see what happens after. When downloading one of those poms maven only has to print that message
<deprecated>
<reason>Use the right groupId: org.whatever</reason>
</deprecated>
> Add deprecation information to POM
> ----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-507) Add deprecation information to POM
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-507?page=comments#action_42890 ]
John Casey commented on MNG-507:
--------------------------------
I'm adding a section that will look like this:
<deprecated>
<reason>Foo 1.x is no longer actively maintained.</reason>
<alternative>
<groupId>org.myco.stuff</groupId>
<artifactId>foo</artifactId>
<version>2.0</version>
</alternative>
</deprecated>
However, I'm not really in favor of directly adding the suggested alternative as a dependency, since it could get in the way of development where they're not ready to move to the alternative...not to mention changing the dependency information of the project itself to be an inaccurate representation.
The project builder should detect deprecated poms and output warnings along with suggested alternatives.
> Add deprecation information to POM
> ----------------------------------
>
> Key: MNG-507
> URL: http://jira.codehaus.org/browse/MNG-507
> Project: Maven 2
> Type: New Feature
> Components: maven-model
> Reporter: Carlos Sanchez
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> Add deprecation information to POM. Probably just a String explaining why the artifact was deprecated.
> If we'd like to suggest the use of a different artifact we can add a dependency to it and it'll get added through transitive resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org