You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Geert Schuring (JIRA)" <ji...@apache.org> on 2010/10/16 22:34:40 UTC

[jira] Created: (SM-2002) Maven3 is not happy with poms

Maven3 is not happy with poms
-----------------------------

                 Key: SM-2002
                 URL: https://issues.apache.org/activemq/browse/SM-2002
             Project: ServiceMix
          Issue Type: Bug
          Components: archetypes
    Affects Versions: archetypes-2010.01
            Reporter: Geert Schuring
            Assignee: Jean-Baptiste Onofré
            Priority: Minor
             Fix For: archetypes-2010.02


Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Work started: (SM-2002) Maven3 is not happy with poms

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SM-2002 started by Jean-Baptiste Onofré.

> Maven3 is not happy with poms
> -----------------------------
>
>                 Key: SM-2002
>                 URL: https://issues.apache.org/activemq/browse/SM-2002
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: archetypes-2010.01
>            Reporter: Geert Schuring
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: archetypes-2010.02
>
>         Attachments: SM-2002.patch
>
>
> Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (SM-2002) Maven3 is not happy with poms

Posted by "Geert Schuring (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geert Schuring reopened SM-2002:
--------------------------------


Apparently 1 archetype wasn't included in the patch (servicemix-camel-osgi-bundle), or something went wrong with the commit. I'll attach a patch that fixes this.

> Maven3 is not happy with poms
> -----------------------------
>
>                 Key: SM-2002
>                 URL: https://issues.apache.org/activemq/browse/SM-2002
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: archetypes-2010.01
>            Reporter: Geert Schuring
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: archetypes-2010.02
>
>         Attachments: SM-2002.patch, SM-2002b.patch
>
>
> Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-2002) Maven3 is not happy with poms

Posted by "Geert Schuring (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geert Schuring updated SM-2002:
-------------------------------

    Attachment:     (was: SM-2002.patch)

> Maven3 is not happy with poms
> -----------------------------
>
>                 Key: SM-2002
>                 URL: https://issues.apache.org/activemq/browse/SM-2002
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: archetypes-2010.01
>            Reporter: Geert Schuring
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: archetypes-2010.02
>
>
> Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SM-2002) Maven3 is not happy with poms

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved SM-2002.
--------------------------------------

    Resolution: Fixed

Patch reviewed and commited: revision 1025709.

> Maven3 is not happy with poms
> -----------------------------
>
>                 Key: SM-2002
>                 URL: https://issues.apache.org/activemq/browse/SM-2002
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: archetypes-2010.01
>            Reporter: Geert Schuring
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: archetypes-2010.02
>
>         Attachments: SM-2002.patch
>
>
> Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-2002) Maven3 is not happy with poms

Posted by "Geert Schuring (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geert Schuring updated SM-2002:
-------------------------------

    Attachment: SM-2002b.patch

> Maven3 is not happy with poms
> -----------------------------
>
>                 Key: SM-2002
>                 URL: https://issues.apache.org/activemq/browse/SM-2002
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: archetypes-2010.01
>            Reporter: Geert Schuring
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: archetypes-2010.02
>
>         Attachments: SM-2002.patch, SM-2002b.patch
>
>
> Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-2002) Maven3 is not happy with poms

Posted by "Geert Schuring (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geert Schuring updated SM-2002:
-------------------------------

    Attachment: SM-2002.patch

Patch updated to include <encoding>UTF-8</encoding> for compiler plugin config

> Maven3 is not happy with poms
> -----------------------------
>
>                 Key: SM-2002
>                 URL: https://issues.apache.org/activemq/browse/SM-2002
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: archetypes-2010.01
>            Reporter: Geert Schuring
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: archetypes-2010.02
>
>         Attachments: SM-2002.patch
>
>
> Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SM-2002) Maven3 is not happy with poms

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved SM-2002.
--------------------------------------

    Resolution: Fixed

Revision 1026569.

> Maven3 is not happy with poms
> -----------------------------
>
>                 Key: SM-2002
>                 URL: https://issues.apache.org/activemq/browse/SM-2002
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: archetypes-2010.01
>            Reporter: Geert Schuring
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: archetypes-2010.02
>
>         Attachments: SM-2002.patch, SM-2002b.patch
>
>
> Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-2002) Maven3 is not happy with poms

Posted by "Geert Schuring (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geert Schuring updated SM-2002:
-------------------------------

    Patch Info: [Patch Available]

> Maven3 is not happy with poms
> -----------------------------
>
>                 Key: SM-2002
>                 URL: https://issues.apache.org/activemq/browse/SM-2002
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: archetypes-2010.01
>            Reporter: Geert Schuring
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: archetypes-2010.02
>
>         Attachments: SM-2002.patch
>
>
> Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-2002) Maven3 is not happy with poms

Posted by "Geert Schuring (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geert Schuring updated SM-2002:
-------------------------------

    Attachment: SM-2002.patch

I've attached a patch that solves the issue.

> Maven3 is not happy with poms
> -----------------------------
>
>                 Key: SM-2002
>                 URL: https://issues.apache.org/activemq/browse/SM-2002
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: archetypes-2010.01
>            Reporter: Geert Schuring
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: archetypes-2010.02
>
>         Attachments: SM-2002.patch
>
>
> Maven 3 complains about several issues with the POM files generated by the 2010.01 archetypes. For instance, build plugins have not been given a version number, and ${pom.artifactId} is being used instead of {project.artifactId}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.