[
http://jira.magnolia-cms.com/browse/BUILD-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated BUILD-19:
--------------------------------
Fix Version/s: POMs 11
(was: POMs 10)
(was: Build Tools 1.5.2)
Description:
--1) Current build-tools' README depend a lot on the artifact type to determine
what information to put in the README files etc. One of the most visible flaws
is that is the artifact is of type {{pom}}, the README will say this bundle
includes Tomcat, which is not always desirable (i.e STK is *not* bundled with
Tomcat).
We could introduce a {{bundleType}} property to circumvent this; or have these
bundle projects specify extra bundled artifacts (not necessarily visible to the
project model, like with our tomcat bundles, specifically)-- see BUILD-24
2) Assembly descriptor: magnolia-bundle-assembly could (should) be merged in
magnolia-build-tools
3) The default module assembly descriptor should probably not filter everything
under src/bundle, but only txt files ?
--4) poms: we're using deprecated goal and configuration properties of the
assembly plugin (attached vs single, descriptorRefs, ...)-- done with BUILD-15
and BUILD-17
was:
1) Current build-tools' README depend a lot on the artifact type to determine
what information to put in the README files etc. One of the most visible flaws
is that is the artifact is of type {{pom}}, the README will say this bundle
includes Tomcat, which is not always desirable (i.e STK is *not* bundled with
Tomcat).
We could introduce a {{bundleType}} property to circumvent this; or have these
bundle projects specify extra bundled artifacts (not necessarily visible to the
project model, like with our tomcat bundles, specifically)
2) Assembly descriptor: magnolia-bundle-assembly could (should) be merged in
magnolia-build-tools
3) The default module assembly descriptor should probably not filter everything
under src/bundle, but only txt files ?
4) poms: we're using deprecated goal and configuration properties of the
assembly plugin (attached vs single, descriptorRefs, ...)
> Build tools improvements
> ------------------------
>
> Key: BUILD-19
> URL: http://jira.magnolia-cms.com/browse/BUILD-19
> Project: Build
> Issue Type: Improvement
> Reporter: Grégory Joseph
> Assignee: Grégory Joseph
> Fix For: POMs 11
>
>
> --1) Current build-tools' README depend a lot on the artifact type to
> determine what information to put in the README files etc. One of the most
> visible flaws is that is the artifact is of type {{pom}}, the README will say
> this bundle includes Tomcat, which is not always desirable (i.e STK is *not*
> bundled with Tomcat).
> We could introduce a {{bundleType}} property to circumvent this; or have
> these bundle projects specify extra bundled artifacts (not necessarily
> visible to the project model, like with our tomcat bundles, specifically)--
> see BUILD-24
> 2) Assembly descriptor: magnolia-bundle-assembly could (should) be merged in
> magnolia-build-tools
> 3) The default module assembly descriptor should probably not filter
> everything under src/bundle, but only txt files ?
> --4) poms: we're using deprecated goal and configuration properties of the
> assembly plugin (attached vs single, descriptorRefs, ...)-- done with
> BUILD-15 and BUILD-17
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
