GitHub user aldettinger opened a pull request:
https://github.com/apache/camel/pull/1548
CAMEL-11009: Corrected the generation of the 'spring.schemas' file in
camel-blueprint
This PR proposes a possible fix for
[CAMEL-11009](https://issues.apache.org/jira/browse/CAMEL-11009).
Actually, the file `/META-INF/spring.schemas` is filtered during the
process-resources phase.
However, the `camel.schema.version` property is defined too late (during
the process-classes phase).
I re-sequenced those steps, and now the file `/META-INF/spring.schemas` is
generated as below:
`http\://camel.apache.org/schema/spring=camel-spring.xsd`
`http\://camel.apache.org/schema/spring/v2.19=camel-spring-v2.19.xsd`
The fix needs at least maven 3.0.3, but I'm sure build servers are more
recent ;)
If you are ok with the fix, I would then check this issue in
camel-blueprint and camel-spring-dm (unless deprecated).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aldettinger/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1548.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1548
----
commit 23545491c228997f52cfc482af17c5f48fa83348
Author: aldettinger <[email protected]>
Date: 2017-03-13T20:36:49Z
CAMEL-11000: Issued a simple warning rather than throwing an Exception
commit 649e9cbbed41a6970bc9b5881b53f446531af4ff
Author: aldettinger <[email protected]>
Date: 2017-03-17T16:15:01Z
Merge remote-tracking branch 'upstream/master'
Merging from upstream/master
commit 1e7763d120e38322db17f9a5fbc4d3ff6b3ac183
Author: aldettinger <[email protected]>
Date: 2017-03-17T18:22:30Z
CAMEL-11009: Set the camel.schema.version property earlier
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
