build error - look familar?
by John Mazzitelli
Anyone ever see this? I did add something to the GWT interfaces, but there are no errors to indicate anything is wrong with the new code... there isn't anything obviously wrong with my new code that I can see.
Caused by: org.codehaus.mojo.gwt.shell.ForkedProcessExecutionException: Command [[
...the big command line to run the gwt compiler is here...
]] failed with status 1
at org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo$JavaCommand.execute(AbstractGwtShellMojo.java:485)
at org.codehaus.mojo.gwt.shell.CompileMojo.compile(CompileMojo.java:365)
at org.codehaus.mojo.gwt.shell.CompileMojo.doExecute(CompileMojo.java:280)
at org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo.execute(AbstractGwtShellMojo.java:172)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
10 years, 1 month
Some script changes in master
by Jay Shaughnessy
Just a heads up, for RFE 1061311 [1] I've extracted the environment
variables out of our rhq-server/bin scripts and into
rhq-server-env.sh|bat. This is now analogous to the way we use
rhq-agent-env.sh. It applies mainly to rhqctl and installation. Please
let me know if you experience any issues, thanks - Jay
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1061311
10 years, 1 month
Introducing additional plugin descriptor
by Libor Zoubek
Hello,
last week I demoed Canned DynaGroup Expressions provided by plugin [1]. On
IRC we discusses what file format should we use (currently I wrote it
using yaml). It's possible that in future we're going to introduce another
descriptor, so we may want some consistency in file formats.
We have basically 3 possibilities yaml, json and xml.
Short summary of pros and cons:
yaml:
+ human readable
+ can be parsed to objects (similar to jackson)
- no declarative "yaml-schema" validation possible
json:
+ harder to read/write
+ json-schema
- gaYak does not like it :-)
xml:
+ consistency (we already use xml - rhq-plugin.xml)
+ xml-schema
+ easy to write in schema-aware IDE
- not fancy
I'd personally stick with yaml, because it's readable. I don't miss
validation using schema, because structure I am using in
dynagroup-expressions.yaml is simple enough, and I still need to
additionally validate/evaluate (even if schema would have existed) the
expression.
Thanks
[1] http://youtu.be/pB5Qr4Sys2w
--
Libor Zoubek
10 years, 1 month