[
https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229886#comment-14229886
]
Karl Wright commented on CONNECTORS-1105:
-----------------------------------------
Ok, after consulting a maven expert, I found out that the parent pom allows the
definition of the source assembly to be overwritten, using the following
property:
{code}
<sourceReleaseAssemblyDescriptor>assembly_name</sourceReleaseAssemblyDescriptor>
{code}
Unfortunately, there still does not seem to be any way to *define* the assembly
name in a way that the parent pom allows access to it. The following does NOT
work:
{code}
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.5.2</version>
<configuration>
<descriptors>
<descriptor>src/main/assembly/src.xml</descriptor>
</descriptors>
<!-- tarLongFileMode>gnu</tarLongFileMode -->
</configuration>
</plugin>
{code}
In this case, if src.xml defines the ID 'mcfsrc', and the property above also
says 'mcfsrc', it nonetheless gives an error that it can't find assembly ID
'mcfsrc'. Hmm.
I also determined that there is no way to completely disable the source
generation without changing the parent pom.
> Add maven delivery targets to poms
> ----------------------------------
>
> Key: CONNECTORS-1105
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1105
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Build
> Affects Versions: ManifoldCF 1.8
> Reporter: Karl Wright
> Assignee: Maurizio Pillitu
> Fix For: ManifoldCF 2.0
>
>
> We've been asked to deliver mcf jars and wars to maven central repository by
> some developers. This ticket represents that work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
