[GitHub] camel pull request #1146: CAMEL-10255 - Make it easy to configure property p...

[DariusX]

GitHub user DariusX opened a pull request:

https://github.com/apache/camel/pull/1146

CAMEL-10255 - Make it easy to configure property placeholder

I added a setPropertyPlaceholderLocations() method to Main, as suggested by 
the ticket: 
https://issues.apache.org/jira/browse/CAMEL-10255

I also made a change to the test class "MainExample" and added a test file 
example.properties.
Not sure if a test is worth having in this case, but added it, just in case.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/DariusX/camel 
CAMEL-10255-Property-File-on-Main

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1146.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 #1146


commit 38cb20834dd90b2a485f77d676d15e3a1f0232f3
Author: Darius 
Date:   2016-08-28T18:11:47Z

CAMEL-10255 - Make it easy to configure property placeholder




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Getting ready for Apache Camel 2.18 Release

[Claus Ibsen]

Hi

Hope everybody had good summer vacation. I had my vacation in parts
and have next week as PTO.

We should get started to close down on the upcoming Camel 2.18 release.


There is some outstanding work (in no particular order)

1)
Finish the spring boot stuff with the starter components.
Nicola comes back from PTO and will work on this.

2)
rest-dsl to support calling REST services. I am working on this and
have some outstanding work still around binding and other
improvements.

3)
Tidy up the log4j v2 upgrade. Some of the examples do not start with
the jetty plugin.

4)
Migrate the last wiki pages to adoc files. There is not so many pages
left and you can find a report when running camel-catalog build that
output what is missing.

This will help us with a base-line for maintaining the documentation
going forward in the source code adoc files instead of wiki, and we
can then generate a new website and documentation for the following
release (2.19 or 3.0) etc. But this is a discussion we should IMHO
take post 2.18.

5)
camel-test-karaf module. This module is in the works but could use
some review and finishing so its easier to use for end users.

Notice the existing camel-test-blueprint is still favored for doing
unit tests which you can run fast and easily debug. The new
camel-test-karaf is for running integration tests in a running karaf
instance.

6)
We should look at the JIRA tickets that are assigned to 2.18.0 and try
to fix / implement them, or move them to 2.18.1 or 2.19.0 for next
releases.

7)
Keep an eye on the CI server to make sure the tests are green.
https://builds.apache.org/view/A-D/view/Camel/


If all goes well then hopefully in 2-3 weeks we are ready to cut the 2.18.0 RC.




-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2