You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/04/06 08:19:45 UTC
[jira] Created: (MNG-257) issues to resolve on the packaging vs type mismatch
issues to resolve on the packaging vs type mismatch
---------------------------------------------------
Key: MNG-257
URL: http://jira.codehaus.org/browse/MNG-257
Project: m2
Type: Task
Components: design
Reporter: Brett Porter
Fix For: 1.0-alpha-2
ok, so we have packaging which specifies how the artifact will be packaged, and there is only one of those per POM. type is used in a dependency, and will always get the same POM, but might get a different artifact from the repository (eg, the javadocs, sources, ejb-client, tld, or a certain type of distribution).
For released versions this is fine, but there can be problems when it comes to snapshots.
The version assigned is per POM, rather than per file - so unless they are all deployed together, this will be a problem where getting the latest vesrion may find something missing. This was originally the intention (eg for ejb-clients), but some things will not be published every time.
Possibly we could have one metadata file per artifact, but this doesn't feel as nice to me.
We should definitely have:
- any deployment of a distribution, etc MUST deploy main artifact too and they can all share a version
Currently we have:
- any later deployment of just a JAR doesn't deploy things like distributions as they are not attached to it
The dependencies on distributions for that snapshot will break - which seems fair, as they wouldn't actually be the same as the JAR anyway. You wouldn't want to get old sources, so if you are going to commit to deploying sources - deploy them every time! If not, then maybe it is reasonable not to ever make them available for snapshots.
I think this is all reasonable. Is this ok?
Are there any other issues besides this with the mismatch?
--
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
-
If you want more information on JIRA, or have a bug to report 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-257) issues to resolve on the packaging vs type mismatch
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-257?page=all ]
Brett Porter updated MNG-257:
-----------------------------
Fix Version: (was: 2.0-alpha-2)
2.0-alpha-3
> issues to resolve on the packaging vs type mismatch
> ---------------------------------------------------
>
> Key: MNG-257
> URL: http://jira.codehaus.org/browse/MNG-257
> Project: m2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0-alpha-3
>
>
> ok, so we have packaging which specifies how the artifact will be packaged, and there is only one of those per POM. type is used in a dependency, and will always get the same POM, but might get a different artifact from the repository (eg, the javadocs, sources, ejb-client, tld, or a certain type of distribution).
> For released versions this is fine, but there can be problems when it comes to snapshots.
> The version assigned is per POM, rather than per file - so unless they are all deployed together, this will be a problem where getting the latest vesrion may find something missing. This was originally the intention (eg for ejb-clients), but some things will not be published every time.
> Possibly we could have one metadata file per artifact, but this doesn't feel as nice to me.
> We should definitely have:
> - any deployment of a distribution, etc MUST deploy main artifact too and they can all share a version
> Currently we have:
> - any later deployment of just a JAR doesn't deploy things like distributions as they are not attached to it
> The dependencies on distributions for that snapshot will break - which seems fair, as they wouldn't actually be the same as the JAR anyway. You wouldn't want to get old sources, so if you are going to commit to deploying sources - deploy them every time! If not, then maybe it is reasonable not to ever make them available for snapshots.
> I think this is all reasonable. Is this ok?
> Are there any other issues besides this with the mismatch?
--
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] Work stopped: (MNG-257) issues to resolve on the packaging vs type mismatch
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-257?page=history ]
Work on MNG-257 stopped by Brett Porter
> issues to resolve on the packaging vs type mismatch
> ---------------------------------------------------
>
> Key: MNG-257
> URL: http://jira.codehaus.org/browse/MNG-257
> Project: m2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0-alpha-2
>
>
> ok, so we have packaging which specifies how the artifact will be packaged, and there is only one of those per POM. type is used in a dependency, and will always get the same POM, but might get a different artifact from the repository (eg, the javadocs, sources, ejb-client, tld, or a certain type of distribution).
> For released versions this is fine, but there can be problems when it comes to snapshots.
> The version assigned is per POM, rather than per file - so unless they are all deployed together, this will be a problem where getting the latest vesrion may find something missing. This was originally the intention (eg for ejb-clients), but some things will not be published every time.
> Possibly we could have one metadata file per artifact, but this doesn't feel as nice to me.
> We should definitely have:
> - any deployment of a distribution, etc MUST deploy main artifact too and they can all share a version
> Currently we have:
> - any later deployment of just a JAR doesn't deploy things like distributions as they are not attached to it
> The dependencies on distributions for that snapshot will break - which seems fair, as they wouldn't actually be the same as the JAR anyway. You wouldn't want to get old sources, so if you are going to commit to deploying sources - deploy them every time! If not, then maybe it is reasonable not to ever make them available for snapshots.
> I think this is all reasonable. Is this ok?
> Are there any other issues besides this with the mismatch?
--
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
-
If you want more information on JIRA, or have a bug to report 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] Work started: (MNG-257) issues to resolve on the packaging vs type mismatch
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-257?page=history ]
Work on MNG-257 started by Brett Porter
> issues to resolve on the packaging vs type mismatch
> ---------------------------------------------------
>
> Key: MNG-257
> URL: http://jira.codehaus.org/browse/MNG-257
> Project: m2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0-alpha-2
>
>
> ok, so we have packaging which specifies how the artifact will be packaged, and there is only one of those per POM. type is used in a dependency, and will always get the same POM, but might get a different artifact from the repository (eg, the javadocs, sources, ejb-client, tld, or a certain type of distribution).
> For released versions this is fine, but there can be problems when it comes to snapshots.
> The version assigned is per POM, rather than per file - so unless they are all deployed together, this will be a problem where getting the latest vesrion may find something missing. This was originally the intention (eg for ejb-clients), but some things will not be published every time.
> Possibly we could have one metadata file per artifact, but this doesn't feel as nice to me.
> We should definitely have:
> - any deployment of a distribution, etc MUST deploy main artifact too and they can all share a version
> Currently we have:
> - any later deployment of just a JAR doesn't deploy things like distributions as they are not attached to it
> The dependencies on distributions for that snapshot will break - which seems fair, as they wouldn't actually be the same as the JAR anyway. You wouldn't want to get old sources, so if you are going to commit to deploying sources - deploy them every time! If not, then maybe it is reasonable not to ever make them available for snapshots.
> I think this is all reasonable. Is this ok?
> Are there any other issues besides this with the mismatch?
--
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
-
If you want more information on JIRA, or have a bug to report 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-257) issues to resolve on the packaging vs type mismatch
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-257?page=comments#action_39280 ]
Brett Porter commented on MNG-257:
----------------------------------
other things to note:
- the repository tool takes the classifier into account, so creates a dummy pom for these, which it shouldn't
- the main pom may not be correct for the purposes of transitive deps on a secondary artifact: eg assemblies already bundle the dependencies. How to specify which are deps for the primary, and which are deps of others?
> issues to resolve on the packaging vs type mismatch
> ---------------------------------------------------
>
> Key: MNG-257
> URL: http://jira.codehaus.org/browse/MNG-257
> Project: m2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0-alpha-3
>
>
> ok, so we have packaging which specifies how the artifact will be packaged, and there is only one of those per POM. type is used in a dependency, and will always get the same POM, but might get a different artifact from the repository (eg, the javadocs, sources, ejb-client, tld, or a certain type of distribution).
> For released versions this is fine, but there can be problems when it comes to snapshots.
> The version assigned is per POM, rather than per file - so unless they are all deployed together, this will be a problem where getting the latest vesrion may find something missing. This was originally the intention (eg for ejb-clients), but some things will not be published every time.
> Possibly we could have one metadata file per artifact, but this doesn't feel as nice to me.
> We should definitely have:
> - any deployment of a distribution, etc MUST deploy main artifact too and they can all share a version
> Currently we have:
> - any later deployment of just a JAR doesn't deploy things like distributions as they are not attached to it
> The dependencies on distributions for that snapshot will break - which seems fair, as they wouldn't actually be the same as the JAR anyway. You wouldn't want to get old sources, so if you are going to commit to deploying sources - deploy them every time! If not, then maybe it is reasonable not to ever make them available for snapshots.
> I think this is all reasonable. Is this ok?
> Are there any other issues besides this with the mismatch?
--
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-257) issues to resolve on the packaging vs type mismatch
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-257?page=all ]
Brett Porter closed MNG-257:
----------------------------
Resolution: Fixed
> issues to resolve on the packaging vs type mismatch
> ---------------------------------------------------
>
> Key: MNG-257
> URL: http://jira.codehaus.org/browse/MNG-257
> Project: Maven 2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0-alpha-3
>
>
> ok, so we have packaging which specifies how the artifact will be packaged, and there is only one of those per POM. type is used in a dependency, and will always get the same POM, but might get a different artifact from the repository (eg, the javadocs, sources, ejb-client, tld, or a certain type of distribution).
> For released versions this is fine, but there can be problems when it comes to snapshots.
> The version assigned is per POM, rather than per file - so unless they are all deployed together, this will be a problem where getting the latest vesrion may find something missing. This was originally the intention (eg for ejb-clients), but some things will not be published every time.
> Possibly we could have one metadata file per artifact, but this doesn't feel as nice to me.
> We should definitely have:
> - any deployment of a distribution, etc MUST deploy main artifact too and they can all share a version
> Currently we have:
> - any later deployment of just a JAR doesn't deploy things like distributions as they are not attached to it
> The dependencies on distributions for that snapshot will break - which seems fair, as they wouldn't actually be the same as the JAR anyway. You wouldn't want to get old sources, so if you are going to commit to deploying sources - deploy them every time! If not, then maybe it is reasonable not to ever make them available for snapshots.
> I think this is all reasonable. Is this ok?
> Are there any other issues besides this with the mismatch?
--
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-257) issues to resolve on the packaging vs type mismatch
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-257?page=comments#action_37919 ]
Brett Porter commented on MNG-257:
----------------------------------
this plus the addition of the source plugin would be a nice to have for alpha-2, must have for alpha-3
> issues to resolve on the packaging vs type mismatch
> ---------------------------------------------------
>
> Key: MNG-257
> URL: http://jira.codehaus.org/browse/MNG-257
> Project: m2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0-alpha-2
>
>
> ok, so we have packaging which specifies how the artifact will be packaged, and there is only one of those per POM. type is used in a dependency, and will always get the same POM, but might get a different artifact from the repository (eg, the javadocs, sources, ejb-client, tld, or a certain type of distribution).
> For released versions this is fine, but there can be problems when it comes to snapshots.
> The version assigned is per POM, rather than per file - so unless they are all deployed together, this will be a problem where getting the latest vesrion may find something missing. This was originally the intention (eg for ejb-clients), but some things will not be published every time.
> Possibly we could have one metadata file per artifact, but this doesn't feel as nice to me.
> We should definitely have:
> - any deployment of a distribution, etc MUST deploy main artifact too and they can all share a version
> Currently we have:
> - any later deployment of just a JAR doesn't deploy things like distributions as they are not attached to it
> The dependencies on distributions for that snapshot will break - which seems fair, as they wouldn't actually be the same as the JAR anyway. You wouldn't want to get old sources, so if you are going to commit to deploying sources - deploy them every time! If not, then maybe it is reasonable not to ever make them available for snapshots.
> I think this is all reasonable. Is this ok?
> Are there any other issues besides this with the mismatch?
--
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