[ 
https://issues.apache.org/jira/browse/CAMEL-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830547#comment-13830547
 ] 

Hadrian Zbarcea commented on CAMEL-6777:
----------------------------------------

I checked and there are some tiny, tiny (inconsequential) differences between 
the two source distros. I checked and the code can be successfully built from 
both. I have two solutions, one involves changing the behavior of the release 
plugin during release:perform (cannot be tested with a dryRun and I would like 
to avoid committing a tag and all that just for this). The second solution 
involves messing with the <configuration> of the maven-source-plugin. 
Nevertheless, it can be fixed, but the question is this:

Is there a preference which one we should keep? I would think the apache-camel 
one, not the camel (root) one. Assuming no objections, I'll get it done for the 
2.11.3 which I'll release next. I didn't want to keep 2.12.2 to properly test 
this.

> We are building two different source distributions which should not be the 
> case
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-6777
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6777
>             Project: Camel
>          Issue Type: Improvement
>          Components: build system
>    Affects Versions: 2.11.2, 2.12.1
>            Reporter: Christian Müller
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.11.3, 2.12.3, 2.13.0
>
>
> Because of the 'apache-release' profile in our root 
> [pom.xml|https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=pom.xml;h=9e99be5684cfe5a3e48693ed62a1a5ba03d4bfc2;hb=HEAD],
>  we are building two different source distributions:
> - http://search.maven.org/#artifactdetails|org.apache.camel|camel|2.12.0|pom
> - 
> http://search.maven.org/#artifactdetails|org.apache.camel|apache-camel|2.12.0|pom
> I propose to remove this profile.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to