Hi Community,
As Jukka mentioned in the graduation release mails, it would be really
great to improve the UI of Manifold.
I looked at the approach Piergiorgio used in CONNECTORS-265 and this
is already a great improvement.
But how about removing all those snippets from the connectors and
build a
Hi Karl,
I checked out the RC1 und did a
mvn clean install
on the root to test the build using the maven integration.
HSQLDB is now included in a new version (2.2.5.6-9-2011) which is not
available in the maven repositories.
So maybe you can add it to the list of additional dependencies for build
Hi,
maybe, I can help you to clarify some maven things.
In a standard maven project, those end-to-end tests would normally run in
the integration-test phase of the resulted webapp project.
Then, you could set up the dependency plugin in the pre-integration-test
phase.
Manifold is primary build us
it was unnecessary.
>
> Thanks,
> Karl
>
> On Mon, Jul 18, 2011 at 10:26 AM, Tobias Rübner wrote:
> > Ahh ok, sorry for that!
> > I run all the tests of a module at once. That leads to confusing results.
> > Now I would also structure the tests in maven to run the derby tests
wrote:
> run-tests-framework only invokes the Derby tests. That's why you are
> not seeing any others.
>
> Karl
>
> On Mon, Jul 18, 2011 at 9:50 AM, Tobias Rübner wrote:
> > Maybe I'm on the wrong track, but there are currently 2 modules (agents |
> > pull-a
ons. This makes perfect sense in that two tests are being
> invoked. So the process model is working as expected under ant.
>
> Do you mind telling us what "side effects" are you seeing?
>
> Karl
>
>
> On Mon, Jul 18, 2011 at 9:12 AM, Tobias Rübner wrote:
> > I
t;
> > On Mon, Jul 18, 2011 at 8:04 AM, Karl Wright wrote:
> >> These tests run fine under ant, but the ant build invokes test files
> >> explicitly. I'm not quite sure what Ant's behavior is here, and how
> >> exactly it differs from Maven's.
>
The unit tests are currently not working.
The first test in a module creates the properties and logging files and
initializes the framework.
All following tests are also creating those files, but because the framework
is already initialized, they are useless.
This depends on the static behaviour o
