>From Drew McAuliffe <[EMAIL PROTECTED]>:
> I've been running into a number of problems with building tapestry (RC1).
> The biggest problem I have is that the build structure is completely
> interdependent on HiveMind. While I can understand a need to have access to
> HiveMind, I don't see why I
> >
> > Go ahead, and get involved. For the problems that you mention above, are
> >
> > they active JIRA issues? If not, then please submit the issue request.
> > Maybe a small e-mail to the devel list telling Tapestry committers to
> > please look-up the issues
JIRA issues? If not, then please submit the issue request.
> Maybe a small e-mail to the devel list telling Tapestry committers to
> please look-up the issues - preferably with a fix already investigated,
> would be nice? (I just submitted an e-mail of that kind myself, and it
>
preferably with a fix already investigated,
would be nice? (I just submitted an e-mail of that kind myself, and it
was promptly fixed in the 4.0 branch - thanks Howard!)
As for the temporary build problems, I think Howard moved the target to
a temp directory due to the large amount of code / do
Tapestry is dependent on the *build scripts* used by HiveMind. I wrote
them out of frustration with maven 1.0, but I'm looking into Maven 2
for HiveMind (1.2) and Tapestry (4.1).
Those are problems you've identified; the framework and contrib code
is supposed to be compatible with JDK 1.3. I'll l
I've been running into a number of problems with building tapestry (RC1).
The biggest problem I have is that the build structure is completely
interdependent on HiveMind. While I can understand a need to have access to
HiveMind, I don't see why I should need the source of HiveMind, and it's
build s
an issue related to line endings; if you are on
> > Windows it works, on Unix it fails. Sorry.
> >
> > On 6/16/05, Mark Dillon <[EMAIL PROTECTED]> wrote:
> >
> >> I got around the build problems by editing
> >> "framework/src/scripts/TestUpload
quot; and everything built and tested correctly.
--Chris
On Jun 16, 2005, at 12:41 PM, Howard Lewis Ship wrote:
It appears to be an issue related to line endings; if you are on
Windows it works, on Unix it fails. Sorry.
On 6/16/05, Mark Dillon <[EMAIL PROTECTED]> wrote:
I got around the
It appears to be an issue related to line endings; if you are on
Windows it works, on Unix it fails. Sorry.
On 6/16/05, Mark Dillon <[EMAIL PROTECTED]> wrote:
> I got around the build problems by editing
> "framework/src/scripts/TestUpload.xml" and commenting out 3 blocks
I got around the build problems by editing
"framework/src/scripts/TestUpload.xml" and commenting out 3 blocks
that look like this:
Contents match.
If you're failing in the same place as I was, this should take care of
it for you temporarily.
HTH,
Mark
On 6/15/05, Chris
I wanted to try out the new annotations support in Tapestry 4 but
could not get a cvs checkout from tonight to build because of JUnit
test failures. Is cvs going to be in a buildable state soon? Or am
I better off waiting until alpha-4 is released?
--Chris
-
11 matches
Mail list logo