[ 
http://jira.magnolia-cms.com/browse/BUILD-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph updated BUILD-47:
--------------------------------

    Description: 
We have a couple of modules where a simple bundle is used (stk, newsletter, 
ldap), and where we have to set the packaging to jar, which is inherently 
wrong: it creates an "empty" jar artifacts (which is attached to the build and 
thus uploaded to repositories). If we set those modules to packaging:pom, the 
assembly still works but is missing the .TXT files from our remote resources.

Additionally, we might want to use {{runOnlyAtExecutionRoot}}, to investigate.

Also check why our parent pom also uses the "bundle" goal.

http://maven.apache.org/plugins/maven-remote-resources-plugin/usage.html

  was:
We have a couple of modules where a simple bundle is used (stk, newsletter, 
ldap), and where we have to set the packaging to jar, which is inherently 
wrong: it creates an "empty" jar artifacts (which is attached to the build and 
thus uploaded to repositories). If we set those modules to packaging:pom, the 
assembly still works but is missing the .TXT files from our remote resources.

Additionally, we might want to use {{runOnlyAtExecutionRoot}}, to investigate.

http://maven.apache.org/plugins/maven-remote-resources-plugin/usage.html


> Investigate why maven-remote-resources-plugin is not used for pom artifacts
> ---------------------------------------------------------------------------
>
>                 Key: BUILD-47
>                 URL: http://jira.magnolia-cms.com/browse/BUILD-47
>             Project: Build
>          Issue Type: Bug
>          Components: poms
>            Reporter: Grégory Joseph
>            Assignee: Grégory Joseph
>             Fix For: POMs 18
>
>
> We have a couple of modules where a simple bundle is used (stk, newsletter, 
> ldap), and where we have to set the packaging to jar, which is inherently 
> wrong: it creates an "empty" jar artifacts (which is attached to the build 
> and thus uploaded to repositories). If we set those modules to packaging:pom, 
> the assembly still works but is missing the .TXT files from our remote 
> resources.
> Additionally, we might want to use {{runOnlyAtExecutionRoot}}, to investigate.
> Also check why our parent pom also uses the "bundle" goal.
> http://maven.apache.org/plugins/maven-remote-resources-plugin/usage.html

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

Reply via email to