Hi,
Good to know you're helping the JavaCC guys :-)!
Maybe you can adapt the pom.xml file whenever they release the V8,0
version. It would be great having JavaCC v8,0 uploaded to Maven Central.
Kind regards,
Antonio
El 03/06/2018 a las 10:57, Peter Nabbefeld escribió:
Hi Antonio,
I got to fix the pom.xml and sent them to JavaCC support (which seems to
be maintained by one of the original authors), but he seems not to be
interested: "I'm not sure if you are aware, but I'm completely revamping
the code generator (see the branch csharp_codegen) and calling it V8,0.
So all the old stuff should just be archived asap. I don't mind the
maven/pom.xml as long as the ant build can co-exist with it.".
I've primarily been interested in JavaCC, because it started as a
project sponsored by Sun. But currently I'm not satisfied with it for
different reasons, e.g. documentation, so I'll not use it.
Kind regards
Peter
Am 01.06.2018 um 21:04 schrieb Antonio:
Hi,
Can you run a plain Maven build in the command line? Is this a
Maven/pom.xml problem or a NetBeans problem?
If your objective is to build JavaCC from source, I don't think
messing with the pom.xml (as retrieved from github's master branch) is
a good idea.
I imagine the JavaCC people have a proper "pom.xml" file in their
master branch. Just clone the repo and import it in NetBeans, then
"Clean & Build" should do the job for you.
Cheers,
Antonio
On 01/06/18 19:20, Peter Nabbefeld wrote:
Hello,
I cloned JavaCC from "https://github.com/javacc/javacc.git"; and tried
to build it with NB 9.0 RC1. Of course, I first set the source/target
versions to 1.8.
[1] The source hierarchy looks a bit suspicious, most probably
because of several entries like the following in pom.xml:
<sourceDirectory>src</sourceDirectory>
As I've never used those (to be honest, most changes I do in the
POM are just adding copied dependencies), I don't know how to fix
these. As I'm seeing Eclipse project files, I'd guess, that it
handles them differently.
[2] As a result of the mal-configured hierarchy, packages are
incorrectly interpreted by NB.
Usually, I'd guess the build file is correct, but IMHO maven should
be able to build the project then without worrying, if NB interpretes
the files correctly. So, could anybody tell me how to fix the build
problems?
Kind regards
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
