That's probably a good practice moving forward. . .
In this case, this is a temporary solution anyhow. We're currently
trying to support the testsuite for both the old tiles architecture and
the new one. Once the container is implemented and the majority of tests
are working, the second test app will go away and the first will be
updated to reflect the new architecture - this will probably be sometime
today, so I wouldn't waste any time on it.
David
James Mitchell wrote:
While, I can appreciate not having duplicate files
(IncludingServlet.java), I think we shouldn't use svn:externals except
at the root to pull in other trunks. They can be abused quite easily as
evidenced by the recent thread on the infrastructure list....and what
happened to you.
The way to get around this for our case would be to move the source to a
separate project and add a dependency on it from both projects instead
of pulling in it's source, even if it is just 1 file.
Your thoughts?
--
James Mitchell
678.910.8017
On Nov 3, 2006, at 8:07 AM, Antonio Petrelli wrote:
Antonio Petrelli ha scritto:
I receive a strange error:
U ****/tiles2
Updating external location at:
****/tiles2/tiles-container-test/src/main/java
RA layer request failed
svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
svn: REPORT of '/repos/asf/!svn/vcc/default': 400 Bad Request
(http://svn.apache.org)
Ok fixed the error myself, the svn:externals in
/tiles-container-test/src/main missed a "https" instead of "http"
Ciao
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
