You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jorg Heymans (JIRA)" <ji...@codehaus.org> on 2005/10/21 23:41:11 UTC
[jira] Created: (MNG-1276) warning too verbose for invalid poms
warning too verbose for invalid poms
------------------------------------
Key: MNG-1276
URL: http://jira.codehaus.org/browse/MNG-1276
Project: Maven 2
Type: Improvement
Versions: 2.0
Reporter: Jorg Heymans
Basically , per module we get about 10-15 of these flying by :
[WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
Reason: Invalid POM (not v4.0.0 modelVersion)
We have 65 modules, i'm sure you get the picture :-)
see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
--
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-1276) warning too verbose for invalid poms
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1276?page=all ]
Edwin Punzalan updated MNG-1276:
--------------------------------
Attachment: MNG-1276-maven-project.patch
The attached patch will make the WARN message to a single line by moving the other lines to DEBUG.
> warning too verbose for invalid poms
> ------------------------------------
>
> Key: MNG-1276
> URL: http://jira.codehaus.org/browse/MNG-1276
> Project: Maven 2
> Type: Improvement
> Versions: 2.0
> Reporter: Jorg Heymans
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1276-maven-project.patch
>
>
> Basically , per module we get about 10-15 of these flying by :
> [WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
> Reason: Invalid POM (not v4.0.0 modelVersion)
> We have 65 modules, i'm sure you get the picture :-)
> see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
--
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-1276) warning too verbose for invalid poms
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1276?page=all ]
John Casey updated MNG-1276:
----------------------------
Description:
Basically , per module we get about 10-15 of these flying by :
[WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
Reason: Invalid POM (not v4.0.0 modelVersion)
We have 65 modules, i'm sure you get the picture :-)
see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
was:
Basically , per module we get about 10-15 of these flying by :
[WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
Reason: Invalid POM (not v4.0.0 modelVersion)
We have 65 modules, i'm sure you get the picture :-)
see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
Remaining Estimate: 10 minutes
Original Estimate: 10 minutes
Environment:
adding time est. for applying patch.
> warning too verbose for invalid poms
> ------------------------------------
>
> Key: MNG-1276
> URL: http://jira.codehaus.org/browse/MNG-1276
> Project: Maven 2
> Type: Improvement
> Versions: 2.0
> Reporter: Jorg Heymans
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1276-maven-project.patch
>
> Original Estimate: 10 minutes
> Remaining: 10 minutes
>
> Basically , per module we get about 10-15 of these flying by :
> [WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
> Reason: Invalid POM (not v4.0.0 modelVersion)
> We have 65 modules, i'm sure you get the picture :-)
> see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
--
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-1276) warning too verbose for invalid poms
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1276?page=all ]
John Casey closed MNG-1276:
---------------------------
Resolution: Fixed
Patch applied, with some modifications. Added reason to the end of the warning line, to give a hint at why it's failing. This will make it a bit more verbose, but it's important to know. Also, revised all the messages/formatting involved with this to be a bit more terse.
> warning too verbose for invalid poms
> ------------------------------------
>
> Key: MNG-1276
> URL: http://jira.codehaus.org/browse/MNG-1276
> Project: Maven 2
> Type: Improvement
> Versions: 2.0
> Reporter: Jorg Heymans
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1276-maven-project.patch
>
> Original Estimate: 10 minutes
> Time Spent: 10 minutes
> Remaining: 0 minutes
>
> Basically , per module we get about 10-15 of these flying by :
> [WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
> Reason: Invalid POM (not v4.0.0 modelVersion)
> We have 65 modules, i'm sure you get the picture :-)
> see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
--
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-1276) warning too verbose for invalid poms
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1276?page=comments#action_49220 ]
Edwin Punzalan commented on MNG-1276:
-------------------------------------
What could be a good substitute?
The log level is WARNING... should this be changed to ERROR ?
Or should this be summarized ?
> warning too verbose for invalid poms
> ------------------------------------
>
> Key: MNG-1276
> URL: http://jira.codehaus.org/browse/MNG-1276
> Project: Maven 2
> Type: Improvement
> Versions: 2.0
> Reporter: Jorg Heymans
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
>
>
> Basically , per module we get about 10-15 of these flying by :
> [WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
> Reason: Invalid POM (not v4.0.0 modelVersion)
> We have 65 modules, i'm sure you get the picture :-)
> see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
--
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-1276) warning too verbose for invalid poms
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1276?page=all ]
Brett Porter updated MNG-1276:
------------------------------
Fix Version: 2.0.1
> warning too verbose for invalid poms
> ------------------------------------
>
> Key: MNG-1276
> URL: http://jira.codehaus.org/browse/MNG-1276
> Project: Maven 2
> Type: Improvement
> Versions: 2.0
> Reporter: Jorg Heymans
> Fix For: 2.0.1
>
>
> Basically , per module we get about 10-15 of these flying by :
> [WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
> Reason: Invalid POM (not v4.0.0 modelVersion)
> We have 65 modules, i'm sure you get the picture :-)
> see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
--
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-1276) warning too verbose for invalid poms
Posted by "Jorg Heymans (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1276?page=comments#action_49889 ]
Jorg Heymans commented on MNG-1276:
-----------------------------------
minor nitpick -> "does not appear to be valid" could be shortened to "is invalid"
I don't know why you insist on the newlines here :
getLogger().debug( "\n\nReason: " + e.getMessage() + "\n\n" );
thanks for looking into this.
> warning too verbose for invalid poms
> ------------------------------------
>
> Key: MNG-1276
> URL: http://jira.codehaus.org/browse/MNG-1276
> Project: Maven 2
> Type: Improvement
> Versions: 2.0
> Reporter: Jorg Heymans
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1276-maven-project.patch
>
>
> Basically , per module we get about 10-15 of these flying by :
> [WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
> Reason: Invalid POM (not v4.0.0 modelVersion)
> We have 65 modules, i'm sure you get the picture :-)
> see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
--
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-1276) warning too verbose for invalid poms
Posted by "Jorg Heymans (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1276?page=comments#action_49221 ]
Jorg Heymans commented on MNG-1276:
-----------------------------------
I'ld be happy with a -DWarnInvalidPoms=false of some sort. Alternatively, you could create a separate logging category for this and redirect it to invalidpoms.log, that way people can more easily report them by just sending you guys this file.
> warning too verbose for invalid poms
> ------------------------------------
>
> Key: MNG-1276
> URL: http://jira.codehaus.org/browse/MNG-1276
> Project: Maven 2
> Type: Improvement
> Versions: 2.0
> Reporter: Jorg Heymans
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
>
>
> Basically , per module we get about 10-15 of these flying by :
> [WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to be valid. Its will be ignored for artifact resolution.
> Reason: Invalid POM (not v4.0.0 modelVersion)
> We have 65 modules, i'm sure you get the picture :-)
> see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826
--
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