Thank you. I didn't look hard enough before. Here is what works:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.6.0</version>
<executions>
<execution>
<id>Markdownj-Compile</id>
<phase>prepare-package</phase>
<goals>
<goal>exec</goal>
</goals>
<configuration>
<executable>java</executable>
<commandlineArgs>--enable-preview -classpath %classpath
org.markdownj.cli.Main -v:2 -s src/docs/manual -d target/manual
-wr</commandlineArgs>
<workingDirectory></workingDirectory>
<includeProjectDependencies>false</includeProjectDependencies>
<includePluginDependencies>true</includePluginDependencies>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.markdownj</groupId>
<artifactId>markdownj-cli</artifactId>
<version>0.1.15-SNAPSHOT</version>
<type>jar</type>
</dependency>
</dependencies>
</plugin>
It wasn't accessing the jar file, but the 'class' file! I'll upload the
changes.
Thanks again
Brad.
On 8/3/20 5:12 am, Geertjan Wielenga wrote:
Can you do this, please:
1. Right-click the project.
2. Choose "Run".
3. Copy the content of the Output window in response to this e-mail.
Thanks,
Gj
On Sat, Mar 7, 2020 at 10:09 PM Bradley Willcott
<optusprepa...@gmail.com <mailto:optusprepa...@gmail.com>> wrote:
'run' requires the packaged jar file (markdownj-cli-*.jar) that is
produced by this very project. Bootstrapping!
On 8/3/20 5:01 am, Geertjan Wielenga wrote:
So run the project, rather than building it, and all will be
well. That’s because of your settings for ‘run’ action in
nbactions file.
Gj
On Sat, 7 Mar 2020 at 21:59, Bradley Willcott
<optusprepa...@gmail.com <mailto:optusprepa...@gmail.com>> wrote:
There is a reason for that. This is being run in the:
<phase>prepare-package</phase>
At this point, there is no jar file to run. I only have
access to the compiled class files, hence, using the:
<goal>java</goal>
instead of the:
<goal>exec</goal>
This is processing the 'md' files for the src/docs/manual,
storing the 'html' output in the target/manual directory.
All this works perfectly without the use of the /Preview
Features/. I just like to use bleeding-edge technology.
On 8/3/20 4:22 am, Geertjan Wielenga wrote:
See my responses above.
Seems to me that when you do your build, you're not using
the settings you provided in nbactions.
Gj
On Sat, Mar 7, 2020 at 9:21 PM Bradley Willcott
<optusprepa...@gmail.com <mailto:optusprepa...@gmail.com>>
wrote:
Here are the links to the compiled jar files:
BEW Commons Library jar
<https://github.com/bewillcott/bewcommons/releases/tag/1.0.2-SNAPSHOT>
files
Markdownj-core jar
<https://github.com/bewillcott/markdownj/releases/tag/0.5.15-SNAPSHOT>
files
On 8/3/20 3:47 am, Bradley Willcott wrote:
There are two other projects you require. I don't yet
know how to get a compiled package up there for download.
BEW Commons Library
<https://github.com/bewillcott/bewcommons>
Markdownj Core Library
<https://github.com/bewillcott/markdownj/core>
I will look into uploading compiled versions.
On 8/3/20 3:42 am, Geertjan Wielenga wrote:
Trying to reproduce, but this is nowhere to be found:
<dependency>
<groupId>com.bew</groupId>
<artifactId>BEWCommons</artifactId>
<version>1.0.2-SNAPSHOT</version>
</dependency>
Gj
On Sat, Mar 7, 2020 at 8:31 PM Bradley Willcott
<optusprepa...@gmail.com
<mailto:optusprepa...@gmail.com>> wrote:
Thank you for that.
However, I have already plumbed those depths. If
you would take a look at the pom.xml
<https://github.com/bewillcott/markdownj-cli/blob/master/pom.xml>
file. I don't want to put it here as it is rather
long.
I have set the '--enable-preview' option for
'maven-compiler-plugin' and 'maven-surefire-plugin'.
On 8/3/20 3:12 am, Geertjan Wielenga wrote:
Read:
https://netbeans.apache.org/download/nb113/index.html
Gj
On Sat, 7 Mar 2020 at 19:12, Bradley Willcott
<optusprepa...@gmail.com
<mailto:optusprepa...@gmail.com>> wrote:
I have just installed both JDK 14 and NB 11.3.
I am trying to incorporate 14's preview
features into an on-going project: Markdownj
CLI
<https://github.com/bewillcott/markdownj-cli>.
However, part of my POM processing causes an
error:
"java.lang.UnsupportedClassVersionError:
Preview features are not enabled for
org/markdownj/cli/Main (class file version
58.65535). Try running with '--enable-preview'"
The part that is the culprit is:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.6.0</version>
<executions>
<execution>
<id>Markdownj-Compile</id>
<phase>prepare-package</phase>
<goals>
<goal>java</goal>
</goals>
<configuration>
<commandlineArgs>--enable-preview</commandlineArgs>
<workingDirectory>${project.build.directory}</workingDirectory>
<includeProjectDependencies>false</includeProjectDependencies>
<includePluginDependencies>true</includePluginDependencies>
<mainClass>org.markdownj.cli.Main</mainClass>
<arguments>
<argument>-s
src/docs/manual</argument>
<argument>-d
target/manual</argument>
<argument>-rwv:2</argument>
</arguments>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.markdownj</groupId>
<artifactId>markdownj-cli</artifactId>
<version>0.1.15-SNAPSHOT</version>
<type>jar</type>
</dependency>
</dependencies>
</plugin>
If I comment out this entire plugin section,
I can complete the compile. Somewhere,
somehow, I need to tell "exec-maven-plugin"
to use the JDK 14 "java" app with the
"--enable-preview" option.
Any ideas?
Thanks,
Brad.
