Created: (MANT-59) Add support for generating build files when <packaging>bundle</bundle>

Add support for generating build files when <packaging>bundle</bundle>
----------------------------------------------------------------------

                 Key: MANT-59
                 URL: http://jira.codehaus.org/browse/MANT-59
             Project: Maven 2.x Ant Plugin
          Issue Type: New Feature
            Reporter: Alexander Kurtakov


When packaging is set to bundle ant:ant task generates an empty package target containting the following message "No Ant task exists for the packaging 'bundle'. You could overrided the Ant package target in your build.xml."
It would be good if packaging bundle is handled the same way as packaging jar. This will allow generating build.xml good enough for building a jar though it not be an OSGi bundle but this is good enough for bootstrapping purposes.
It would be even better if a parameter for setting the MANIFEST.MF is present, e.g being able to use `ant -Dmaven.bundle.manifest=./MANIFEST.MF package`


--
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

       

     [ http://jira.codehaus.org/browse/MANT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated MANT-59:
--------------------------

         Assignee: Paul Gier
    Fix Version/s: 2.2.1

> Add support for generating build files when <packaging>bundle</bundle>
> ----------------------------------------------------------------------
>
>                 Key: MANT-59
>                 URL: http://jira.codehaus.org/browse/MANT-59
>             Project: Maven 2.x Ant Plugin
>          Issue Type: New Feature
>            Reporter: Alexander Kurtakov
>            Assignee: Paul Gier
>             Fix For: 2.2.1
>
>
> When packaging is set to bundle ant:ant task generates an empty package target containting the following message "No Ant task exists for the packaging 'bundle'. You could overrided the Ant package target in your build.xml."
> It would be good if packaging bundle is handled the same way as packaging jar. This will allow generating build.xml good enough for building a jar though it not be an OSGi bundle but this is good enough for bootstrapping purposes.
> It would be even better if a parameter for setting the MANIFEST.MF is present, e.g being able to use `ant -Dmaven.bundle.manifest=./MANIFEST.MF package`

--
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

       

     [ http://jira.codehaus.org/browse/MANT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier closed MANT-59.
-------------------------

    Resolution: Fixed

This is fixed in [r811464|http://svn.apache.org/viewvc?view=rev&revision=811464].
I couldn't find a good way to create a property for the manifest file, without breaking the plugin's behaviour when there is no manifest file.
So instead you'll probably just have to update the manifest in the external build.xml file.

> Add support for generating build files when <packaging>bundle</bundle>
> ----------------------------------------------------------------------
>
>                 Key: MANT-59
>                 URL: http://jira.codehaus.org/browse/MANT-59
>             Project: Maven 2.x Ant Plugin
>          Issue Type: New Feature
>            Reporter: Alexander Kurtakov
>            Assignee: Paul Gier
>             Fix For: 2.2.1
>
>
> When packaging is set to bundle ant:ant task generates an empty package target containting the following message "No Ant task exists for the packaging 'bundle'. You could overrided the Ant package target in your build.xml."
> It would be good if packaging bundle is handled the same way as packaging jar. This will allow generating build.xml good enough for building a jar though it not be an OSGi bundle but this is good enough for bootstrapping purposes.
> It would be even better if a parameter for setting the MANIFEST.MF is present, e.g being able to use `ant -Dmaven.bundle.manifest=./MANIFEST.MF package`

--
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

       

     [ http://jira.codehaus.org/browse/MANT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MANT-59:
----------------------------------

    Affects Version/s: 2.2

> Add support for generating build files when <packaging>bundle</bundle>
> ----------------------------------------------------------------------
>
>                 Key: MANT-59
>                 URL: http://jira.codehaus.org/browse/MANT-59
>             Project: Maven 2.x Ant Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.2
>            Reporter: Alexander Kurtakov
>            Assignee: Paul Gier
>             Fix For: 2.2.1
>
>
> When packaging is set to bundle ant:ant task generates an empty package target containting the following message "No Ant task exists for the packaging 'bundle'. You could overrided the Ant package target in your build.xml."
> It would be good if packaging bundle is handled the same way as packaging jar. This will allow generating build.xml good enough for building a jar though it not be an OSGi bundle but this is good enough for bootstrapping purposes.
> It would be even better if a parameter for setting the MANIFEST.MF is present, e.g being able to use `ant -Dmaven.bundle.manifest=./MANIFEST.MF package`

--
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