Jason Dillon wrote:
Setting interimDirectory for the jjtree-javacc goal fixes my problems.
I finally got the plugin to register both interimDirectory and
outputDirectory as compile source roots such that IDEA should be happy
with the default values for these directories. As a result, you nee
Jason Dillon wrote:
Looks like JavaCC 4.1 is out, though not yet in central. Any thoughts
on upgrading?
Yes, I noticed that but being a lazy guy I hoped somebody else would
have created the upload bundle ;-) Anyway, since you asked for it, here
we go:
http://jira.codehaus.org/browse/MAVE
Looks like JavaCC 4.1 is out, though not yet in central. Any thoughts
on upgrading?
--jason
On Sep 30, 2008, at 2:27 AM, Benjamin Bentmann wrote:
Jason Dillon wrote:
Okay, so I looked into this a little bit more, and the main reason
why I implemented my own version of the javacc-maven-p
Setting interimDirectory for the jjtree-javacc goal fixes my problems.
--jason
On Oct 1, 2008, at 12:49 PM, Benjamin Bentmann wrote:
Jason Dillon wrote:
Notice the ASTOpaqueString, ASTPlainString and ASTQuotedString,
which are defined in src/main/java/* ? There are also classes of
the s
Jason Dillon wrote:
Notice the ASTOpaqueString, ASTPlainString and ASTQuotedString, which
are defined in src/main/java/* ? There are also classes of the same
name, the generated bits, in the target/generated-sources/jjtree output.
The Mojo plugin is currently collecting the output from both
On Oct 1, 2008, at 3:05 AM, Benjamin Bentmann wrote:
Jason Dillon wrote:
Alrighty, I see a problem now. While my build is fine, my IDE
(Intellij) is not so happy.
How comes the IDE and console builds differ? Doesn't the IDE use the
same source roots as the console build?
No idea atm.
Jason Dillon wrote:
Alrighty, I see a problem now. While my build is fine, my IDE
(Intellij) is not so happy.
How comes the IDE and console builds differ? Doesn't the IDE use the
same source roots as the console build?
It shows a bunch of duplicate classes
Can you give a concrete exampl
Alrighty, I see a problem now. While my build is fine, my IDE
(Intellij) is not so happy. It shows a bunch of duplicate classes,
and fails to properly resolve my custom bits. I'm not sure if your
changes are doing the same thing which my groovy impl of the javacc-
maven-plugin is... speci
Jason Dillon wrote:
I'm gonna start using it
FYI: I was planning to have the 2.5-SNAPSHOT hanging around for a week
or two and then call a vote for its release.
Benjamin
-
To unsubscribe from this list, please visit:
Jason Dillon wrote:
Seems to be working :-)
Cool.
BTW, do you just hack on this plugin or do you actually have javacc
parser syntax guru-ism?
I'm sorry, but I have no clue about all these parser grammars. We have
two (rather simplistic) grammars at my work written by co-workers and I
mer
Seems to be working :-)
BTW, do you just hack on this plugin or do you actually have javacc
parser syntax guru-ism? I could really use some help (by someone) to
make the GShell syntax parser more robust and full of features. I
only dabble in parser generators, enough to make GShell work,
Jason Dillon wrote:
2.5-SNAPSHOT na?
Yep, sorry, I should have mentioned that.
Benjamin
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
2.5-SNAPSHOT na?
--jason
On Sep 30, 2008, at 2:27 AM, Benjamin Bentmann wrote:
Jason Dillon wrote:
Okay, so I looked into this a little bit more, and the main reason
why I implemented my own version of the javacc-maven-plugin, was
that the plugin at the time (and still) does not know to
I will give it a short :-)
--jason
On Sep 30, 2008, at 2:27 AM, Benjamin Bentmann wrote:
Jason Dillon wrote:
Okay, so I looked into this a little bit more, and the main reason
why I implemented my own version of the javacc-maven-plugin, was
that the plugin at the time (and still) does no
Jason Dillon wrote:
Okay, so I looked into this a little bit more, and the main reason why I
implemented my own version of the javacc-maven-plugin, was that the
plugin at the time (and still) does not know to omit classes which
already exist in the src/main/java tree for overridden nodes.
I
Jason Dillon wrote:
Feel free to nab the code (and convert it to java, since its groovy, but
that should be easy enough) and just use what I have to fix this problem.
Yep, will look at this once I got the next free time slice.
(or implement javacc in groovy :-P)
Personally, I am quite happ
Feel free to nab the code (and convert it to java, since its groovy,
but that should be easy enough) and just use what I have to fix this
problem.
(or implement javacc in groovy :-P)
--jason
On Jun 12, 2008, at 3:25 AM, Benjamin Bentmann wrote:
Jason Dillon wrote:
plugin at the time (an
Yup :-) Hope you can fix it... and then I'd be happy to consume the
mojo plugin again :-) Feel free to steal whatever code you can from
my impl, though its groovy, you should still be able to figure out
what its doing with relative ease ;-) And if not ping me.
--jason
On Jun 12, 2008,
Jason Dillon wrote:
plugin at the time (and still) does not know to omit classes which
already exist in the src/main/java tree for overridden nodes.
The FAQ suggest placing those classes next to the grammar, but IMO this
is not really desirable, since they should, IMO, live in the
src/main/j
Okay, so I looked into this a little bit more, and the main reason why
I implemented my own version of the javacc-maven-plugin, was that the
plugin at the time (and still) does not know to omit classes which
already exist in the src/main/java tree for overridden nodes.
The FAQ suggest placi
Sure, I'd rather not need the version in use for gshell actually ;-)
--jason
On Jun 11, 2008, at 12:51 PM, Benjamin Bentmann wrote:
Jason Dillon wrote:
I have not looked at the mojo javacc in a while, but my guess is
there are still some issues with it.
Maybe you could try out the recent
Jason Dillon wrote:
I have not looked at the mojo javacc in a while, but my guess is there
are still some issues with it.
Maybe you could try out the recent version when you have some time and
just report back what is not working for you such that we might be able
to extend/fix the Mojo plug
I have not looked at the mojo javacc in a while, but my guess is there
are still some issues with it.
--jason
On Jun 10, 2008, at 6:38 PM, Benjamin Bentmann wrote:
Hi,
this is basically a question to Jason Dillon:
I noticed there is a javacc-maven-plugin developed over at Geronimo
[0].
23 matches
Mail list logo
