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/06/09 05:57:10 UTC
[jira] Created: (MNG-461) warn, but don't fail, on a missing POM in the repository
warn, but don't fail, on a missing POM in the repository
--------------------------------------------------------
Key: MNG-461
URL: http://jira.codehaus.org/browse/MNG-461
Project: Maven 2
Type: Improvement
Components: maven-artifact
Reporter: Brett Porter
--
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-461) warn, but don't fail, on a missing POM in the repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-461?page=all ]
Brett Porter updated MNG-461:
-----------------------------
Fix Version: 2.0-beta-1
yeah, that's what I was suggesting (some sort of confidence level - eg generated, converted-m1, published-m2). Currently, we can't tell the difference as they get written into the m2 repo automatically anyway, so it is worth attempting to improve on it.
> warn, but don't fail, on a missing POM in the repository
> --------------------------------------------------------
>
> Key: MNG-461
> URL: http://jira.codehaus.org/browse/MNG-461
> Project: Maven 2
> Type: Improvement
> Components: maven-artifact
> Reporter: Brett Porter
> Fix For: 2.0-beta-1
>
>
--
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-461) warn, but don't fail, on a missing POM in the repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-461?page=all ]
Brett Porter updated MNG-461:
-----------------------------
Priority: Blocker (was: Major)
> warn, but don't fail, on a missing POM in the repository
> --------------------------------------------------------
>
> Key: MNG-461
> URL: http://jira.codehaus.org/browse/MNG-461
> Project: Maven 2
> Type: Improvement
> Components: maven-artifact
> Reporter: Brett Porter
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
--
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-461) warn, but don't fail, on a missing POM in the repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-461?page=comments#action_40943 ]
Brett Porter commented on MNG-461:
----------------------------------
on the first statement - currently we create dummy poms in the repo anyway, so this wouldn't be any different.
I don't quite understand the second point. If it is not found, then it would be faked, if it was found it would be used. It's going to be consistent across environments.
The main problem is that it would have to check for it every time, or write a local copy of the fake pom, which would yield the situation you talked about. However, we already have that situation when we fix metadata in the remote repository, so maybe that is ok and we need focus on a way of getting that updated (maybe a confidence level on a POM that dictated whether it got update checks even if it weren't a snapshot), or just encourage a pom flush from the local repo regularly?
> warn, but don't fail, on a missing POM in the repository
> --------------------------------------------------------
>
> Key: MNG-461
> URL: http://jira.codehaus.org/browse/MNG-461
> Project: Maven 2
> Type: Improvement
> Components: maven-artifact
> Reporter: Brett Porter
>
>
--
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-461) warn, but don't fail, on a missing POM in the repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-461?page=all ]
Brett Porter closed MNG-461:
----------------------------
Assign To: Brett Porter (was: John Casey)
Resolution: Fixed
done with a warning. confidence levels will be implemented separately
> warn, but don't fail, on a missing POM in the repository
> --------------------------------------------------------
>
> Key: MNG-461
> URL: http://jira.codehaus.org/browse/MNG-461
> Project: Maven 2
> Type: Improvement
> Components: maven-artifact
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
--
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-461) warn, but don't fail, on a missing POM in the repository
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-461?page=comments#action_40965 ]
Trygve Laugstol commented on MNG-461:
-------------------------------------
Can we have a <generated> flag in the pom do indicate that it's generated because of missing/bad upstream metadata? I would really like the client to always assume that all metadata is available. I fear that not doing so might lead users to not help keeping the metadata up to date.
> warn, but don't fail, on a missing POM in the repository
> --------------------------------------------------------
>
> Key: MNG-461
> URL: http://jira.codehaus.org/browse/MNG-461
> Project: Maven 2
> Type: Improvement
> Components: maven-artifact
> Reporter: Brett Porter
>
>
--
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-461) warn, but don't fail, on a missing POM in the repository
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-461?page=comments#action_40875 ]
Trygve Laugstol commented on MNG-461:
-------------------------------------
Assuming we're talking about the same thing: when will this happen? This was one of the first things we said when we implemented transitive dependencies. We required that the metadata about the artifact would have to be present.
What happens if I do a successful build when the metadata is there (and thus the transitive dependencies from the projects) and then when another user is doing the build and suddenly missing runtime dependencies?
> warn, but don't fail, on a missing POM in the repository
> --------------------------------------------------------
>
> Key: MNG-461
> URL: http://jira.codehaus.org/browse/MNG-461
> Project: Maven 2
> Type: Improvement
> Components: maven-artifact
> Reporter: Brett Porter
>
>
--
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