The problem should be solved in the 1.7.0-snapshot that I deployed yesterday
so the workaround is not necessary. Please try it. /Patrik
Andreas Källberg-2 wrote:
>
> Yes, you can do a quick workaround while waiting for the fix.
> In your web project, go to the file:
> src/main/resources/workflo
Hi Partik,
that's it...Many thanks..for your help.
Yippie...
Kind regards
Karl Heinz Marbaise
--
View this message in context:
http://old.nabble.com/Error-during-build-with-Fornax-oAW-MWE-Maven2-Plugin-V3.0.1-tp27255356s17564p27260454.html
Sent from the Fornax-Platform mailing list archive at
Hi,
i have a project which is using the fornax/opernarchitectureware
repositories
but now i get the message:
[WARNING] POM for
'org.eclipse.m2t.xpand:m2t-xpand-xtend-typesystem-xsd:pom:0.7.2:compile' is
invalid.
Its dependencies (if any) will NOT be available to the current build.
Has so
Hi,
i'm working with Maven 2.2.1 and i got the following failure during the
build on command line as well as in Hudson (1.340)
Java:
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
[INFO] [fornax-oaw-m2
Thanks for reporting. We have fixed the issue,
http://fornax.itemis.de/jira/browse/CSC-467 CSC-467 , and deployed new
snapshot.
/Patrik
--
View this message in context:
http://old.nabble.com/ValueObject-%2B-mutable-%2B-shallowclone-%3D%3D-setid-problems-tp27355964s17564p27358780.html
Sent from
Yes, you can do a quick workaround while waiting for the fix.
In your web project, go to the file:
src/main/resources/workflow-gui.oaw
And enable the the advice execution by just remove the comments that per
default are there. So, it should look like:
Maybe this is helpful for you:
http://blogs.itemis.de/stundzig/archives/563
This is also good (but not your problem):
http://kthoms.wordpress.com/2009/07/20/building-tmf-xtext-projects-with-maven/
/Patrik
Karl Heinz Marbaise wrote:
>
> Hi,
>
> first thanks for your answer...but the workflow
Hi,
first thanks for your answer...but the workflow file looks like this: (ref
http://www.eclipse.org/Xtext/documentation/latest/xtext.html)...
I have tried to change these two entries:
Thank you for the quick response and assurance.
Is this a case in which using the template overrides or property file could
provide a quick and easy workaround to change the setId generator to public?
ie:
notChangeablePropertySetter.visibility=private
to
notChangeablePropertySetter.visibility=
Hi,
It is most definitely a bug.
I'll have a look at it.
.../Andreas
On Thu, Jan 28, 2010 at 2:27 PM, Adam Levine wrote:
> I'm trying to come up to speed with Sculptor, and I'm not sure if the
> problem I'm finding is a bug or operator error:
>
>
>ValueObject Event {
>!im
I'm trying to come up to speed with Sculptor, and I'm not sure if the
problem I'm finding is a bug or operator error:
ValueObject Event {
!immutable
String title
Date scheduled !changeable
}
All compiles fine until it gets to the
I don't think you have to do that in the fornax-oaw-m2-plugin. You can do it
in the workflow.oaw
In case you use workflows that runs other workflows, such in sculptor, you
can override properties.
sculptorworkflow.oaw:
in application project workflow.oaw:
Hi,
I'm trying to configure the Maven 2 plugin in that way to have all the
generated code under target/src-gen folder instead src-genbecause it's
the maven way...
Does anyone has an example how to do so, cause i'm trying that for hours...
Many thanks in advance...
Kind regards
Karl Heinz M
13 matches
Mail list logo
