[
https://issues.apache.org/jira/browse/CAMEL-13142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-13142:
-----------------------------------
Summary: Camel may package artifacts from different version (was: Camel
may package artifacts from differnt version)
> Camel may package artifacts from different version
> --------------------------------------------------
>
> Key: CAMEL-13142
> URL: https://issues.apache.org/jira/browse/CAMEL-13142
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.23.1
> Reporter: Thomas Diesler
> Priority: Major
> Fix For: 3.0.0, 2.23.2
>
>
> When switching from one branch to another there is a (likely) possibility
> that component directories that existed in a previous checkout branch are no
> longer available in the current checkout branch. However, the
> `camel-foo/target` with all the previously generated artifacts are still on
> the file system and cannot be detected by `git status`. Neither will these
> stale target directories be removed by `mvn clean`.
> The camel packager plugin seems to be walking the camel directory structure
> and will package everything it finds. As a result the camel-2.23.2-SNAPSHOT
> catalog may contain a catalog entry that points to
> camel-browse-3.0.0-SNAPSHOT.
> As a workaround, to do something like this
> {code}
> find . -type d -name target | xargs rm -rf
> {code}
> before doing a clean mvn build.
> As a possible solution, it may be necessary for the thing that walks the
> directory structure to require at least one file that is maintained in SCM
> (e.g. pom.xml)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
