You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (Created) (JIRA)" <ji...@apache.org> on 2011/10/22 12:16:31 UTC
[jira] [Created] (FELIX-3182) Update to use parent POM 2.1
Update to use parent POM 2.1
----------------------------
Key: FELIX-3182
URL: https://issues.apache.org/jira/browse/FELIX-3182
Project: Felix
Issue Type: Task
Components: Metatype Service
Affects Versions: metatype-1.0.4
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: metatype-1.0.6
Make use of the 2.1 parent POM to leverage new plugins and remote resources for the legal files
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (FELIX-3182) Update to use parent POM 2.1
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-3182.
------------------------------------
Close after release
> Update to use parent POM 2.1
> ----------------------------
>
> Key: FELIX-3182
> URL: https://issues.apache.org/jira/browse/FELIX-3182
> Project: Felix
> Issue Type: Task
> Components: Metatype Service
> Affects Versions: metatype-1.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: metatype-1.0.6
>
>
> Make use of the 2.1 parent POM to leverage new plugins and remote resources for the legal files
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3182) Update to use parent POM 2.1
Posted by "Felix Meschberger (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-3182.
--------------------------------------
Resolution: Fixed
Done in Rev. 1187702:
Use parent POM 2.1
- remove old legal files in root folder
- create replacements (based on old files) in src/main/appended-resources
- use bundle plugin referred to by parent POM
- depend on official R4 OSGi libraries
> Update to use parent POM 2.1
> ----------------------------
>
> Key: FELIX-3182
> URL: https://issues.apache.org/jira/browse/FELIX-3182
> Project: Felix
> Issue Type: Task
> Components: Metatype Service
> Affects Versions: metatype-1.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: metatype-1.0.6
>
>
> Make use of the 2.1 parent POM to leverage new plugins and remote resources for the legal files
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3182) Update to use parent POM 2.1
Posted by "David Jencks (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133413#comment-13133413 ]
David Jencks commented on FELIX-3182:
-------------------------------------
I'm worried by the removal of all LICENSE and NOTICE files from the metatype root. Expected scm checkout points and the buildable source archives that are the official voted-on apache artifacts need to have LICENSE and NOTICE files at their root correct for their contents. Since metatype is released by itself I think it's an expected scm checkout and needs these. They don't need to reference kxml since there is no kxml source in the metatype scm, but they do need to be present. The appended-resources and m-r-r-p are good for constructing the (different) legal files that are needed in binary artifacts.
> Update to use parent POM 2.1
> ----------------------------
>
> Key: FELIX-3182
> URL: https://issues.apache.org/jira/browse/FELIX-3182
> Project: Felix
> Issue Type: Task
> Components: Metatype Service
> Affects Versions: metatype-1.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: metatype-1.0.6
>
>
> Make use of the 2.1 parent POM to leverage new plugins and remote resources for the legal files
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3182) Update to use parent POM 2.1
Posted by "Felix Meschberger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133441#comment-13133441 ]
Felix Meschberger commented on FELIX-3182:
------------------------------------------
Nothing to worry about. This setup is quite custom in Java-based project. As long as the required files exist in the final build - source and binary.
If you build with the apache-release profile,which is the case for a release build, the source distro is created with the correct files.
> Update to use parent POM 2.1
> ----------------------------
>
> Key: FELIX-3182
> URL: https://issues.apache.org/jira/browse/FELIX-3182
> Project: Felix
> Issue Type: Task
> Components: Metatype Service
> Affects Versions: metatype-1.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: metatype-1.0.6
>
>
> Make use of the 2.1 parent POM to leverage new plugins and remote resources for the legal files
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira