HelloWorld DOJO Sample WebApp build fails when using alternate local maven
repository location
--
Key: TUSCANY-2184
URL: https://issues.apache.org/jira/browse/TUSCANY
Simon Nash wrote:
I did a clean checkout and top-level build today. The build failed in
itest/transaction with the following error. Has anyone else seen this?
I get it consistently from a clean top-level build, but it always seems
to go away when I rebuild just this module.
Simon
With a
Message -
From: Simon Nash [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, February 18, 2008 8:47 AM
Subject: Re: Build fails in transaction itest
Simon Nash wrote:
I did a clean checkout and top-level build today. The build failed in
itest/transaction with the following error
I did a clean checkout and top-level build today. The build failed in
itest/transaction with the following error. Has anyone else seen this?
I get it consistently from a clean top-level build, but it always seems
to go away when I rebuild just this module.
Simon
[INFO]
Hi,
In the trunk, the kernel modules are versioned as 1.0-incubator-SNAPSHOT
while other modules (such as container.javascript) reference the
0.1-pre-spec-SNAPSHOT version of the kernel.
The maven seems to be confused by the mixed versions in the tree. Now I'm
seeing inconsistent results:
Given that extensions are likely to require different versions of
kernel and other libraries, I'm wondering what the value of a top-
down build will provide. For example, is someone likely to be
working across all of the extensions and kernel (this probably won't
even be possible given the
For a while now I've been getting occasional fails when building the Groovy
container, usually it works fine but often it fails with one of the two
exceptions below, then works fine if I immediately rebuild. Does anyone else
see this? Also noticed its using quite an old pre release of Groovy, any
[
https://issues.apache.org/jira/browse/TUSCANY-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-938.
-
Resolution: Fixed
Fixed now
Build fails
---
Key: TUSCANY-938
148 as follows
!--
schemaFile${basedir}/src/main/resources/wsdl/AccountService.wsdl/schemaFile
--
After uncommenting the tag, the build completed successfully.
This pom.xml needs to be corrected in the sources.
- Vijay
Build fails
---
Key
Build fails
---
Key: TUSCANY-938
URL: http://issues.apache.org/jira/browse/TUSCANY-938
Project: Tuscany
Issue Type: Bug
Components: Build System
Environment: Windows XP, cygwin, JDK1.5
Reporter: Vijay
[ http://issues.apache.org/jira/browse/TUSCANY-796?page=all ]
Pete Robbins resolved TUSCANY-796.
--
Fix Version/s: Cpp-M2
(was: Cpp-current)
Resolution: Fixed
SCA C++ build fails on VC++ 6
[ http://issues.apache.org/jira/browse/TUSCANY-796?page=all ]
ant elder updated TUSCANY-796:
--
Fix Version/s: Cpp-current
SCA C++ build fails on VC++ 6
-
Key: TUSCANY-796
URL: http
SCA C++ build fails on VC++ 6
-
Key: TUSCANY-796
URL: http://issues.apache.org/jira/browse/TUSCANY-796
Project: Tuscany
Issue Type: Bug
Components: C++ Build
Affects Versions: Cpp-M1
[ http://issues.apache.org/jira/browse/TUSCANY-796?page=all ]
Pete Robbins reassigned TUSCANY-796:
Assignee: Pete Robbins
SCA C++ build fails on VC++ 6
-
Key: TUSCANY-796
URL: http
restructured the code and developers have been
using VC7.1 projects.
SCA C++ build fails on VC++ 6
-
Key: TUSCANY-796
URL: http://issues.apache.org/jira/browse/TUSCANY-796
Project: Tuscany
Issue Type: Bug
Jim, the point I was making was that following all that discussion about
this before the M1 release there was never any subsequent mail about it
having now been implemented and asking if using -Psourcecheck should now be
a mandatory requirement before doing commits.
...ant
On 8/6/06, Jim
[ http://issues.apache.org/jira/browse/TUSCANY-522?page=all ]
Pete Robbins closed TUSCANY-522.
Fix Version/s: Cpp-M1
Resolution: Fixed
Build fails during copyout - The system cannot find the path specified
Jim, I think the problem may be that AFAIR it has never been made clear on
the mailing list that mvn -Psourcecheck is a required or exactly what it
does or how it works. I can find several mails about doing it and problems
with doing it, but nothing saying something like 'this is the proposal, is
At the risk of throwing stones in a glass house (since I forget to
set svn ignore), *please* remember to run mvn -Psourcecheck prior to
checkins for Java SCA. The Checkstyle audit raises a significant
number of formatting errors that are trivial to avoid by setting
templates in an IDE.
Build fails during copyout - The system cannot find the path specified.
-
Key: TUSCANY-522
URL: http://issues.apache.org/jira/browse/TUSCANY-522
Project: Tuscany
Type: Bug
Components: C++ SDO
[ http://issues.apache.org/jira/browse/TUSCANY-108?page=all ]
Pete Robbins closed TUSCANY-108:
SCA Windows build fails on runtime/test
---
Key: TUSCANY-108
URL: http://issues.apache.org/jira
mvn clean helped. Thanks.
Jeremy Boynes [EMAIL PROTECTED] wrote in
message news:[EMAIL PROTECTED]
Raymond Feng wrote:
--
--
---
Battery:
org.apache.tuscany.model.assembly.tests.SCDLAssemblyLoaderTestCase
SCA Windows build fails on runtime/test
---
Key: TUSCANY-108
URL: http://issues.apache.org/jira/browse/TUSCANY-108
Project: Tuscany
Type: Bug
Components: C++ Build
Reporter: Pete Robbins
The generated wrappers/proxies
[ http://issues.apache.org/jira/browse/TUSCANY-108?page=all ]
Pete Robbins reassigned TUSCANY-108:
Assign To: Pete Robbins
SCA Windows build fails on runtime/test
---
Key: TUSCANY-108
URL
[ http://issues.apache.org/jira/browse/TUSCANY-108?page=all ]
Pete Robbins resolved TUSCANY-108:
--
Resolution: Fixed
fix applied - files re-added to svn
SCA Windows build fails on runtime/test
Raymond Feng wrote:
---
Battery: org.apache.tuscany.model.assembly.tests.SCDLAssemblyLoaderTestCase
---
Tests run: 1, Failures: 0,
26 matches
Mail list logo
