Senaka,
We had to clone commons-vfs into our repo since we had some fixes that need
to go into the commons-vfs. This was done in 3.0.0 release. That is
available in[2]. So the trunk orbit should point to cloned version[2] not
the apache commons-vfs trunk[1].
Rajika
[2] -
https://svn.wso2.org/repo
I have fixed the orbit bundle version in trunk. If you are building with a
clean repo you'll need to build the commons-vfs dependency with test because
commos-vfs building tests for the first time.
Rajika
On Tue, Aug 3, 2010 at 10:57 AM, Amila Jayasekara wrote:
> Hi All,
>I am still facing
WRT to the builds, Orbit depends on the VFS trunk, and the dependencies has
a stale version, which has been deployed onto our Maven repos already. So,
on the builder, we build, [1] as well.
Rajika, can you look into this and come up with a better solution?
[1] https://svn.apache.org/repos/asf/com
Hi All,
I am still facing the issue in $subject. To alleviate this issue, in
a previous build i change orbit/common-vfs/pom.xml dependency versions
to 2.0-wso2v1 (for commons-vfs-sandbox and commons-vfs). Now i took a
fresh copy and try to build again. But still the trunk version of
orbit/
Hi,
$ subject.
I built dependencies/common-vfs (version 2.0-wso2v1)successfully.
Which is the right version?
-Ratha.
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.commons:
