The best way to do it to add Gradle tasks in your build.grade for each
main class (like runApp1, runApp2).
Then open the project properties and configure custom actions for each
application.
Or you might reconfigure run and debug actions to use:
run${input:Application}
or
run${input:Applic
Our gradle project isn’t set up with run configured because we run multiple
applications out of the same project (different main classes). Just wondering
the best way to set this up…custom tasks?
Thanks.
Mike
From: Geertjan Wielenga
Sent: Tuesday, July 2, 2019 3:02 PM
To: Mike Billman
Cc: u
Open the project and click Run.
If the above doesn't work, what's the problem exactly so that we can help
with the problem you're encountering?
Gj
On Tue, Jul 2, 2019 at 9:00 PM Mike Billman
wrote:
> Hey –
>
>
>
> I was wondering if there are any tutorials on using the new gradle support
> int
Hey -
I was wondering if there are any tutorials on using the new gradle support
introduced in 11.0. I would like to try to figure out how to run my
applications, but am not sure how.
Thanks!
Mike Billman
Senior Software Engineer
CPTE
[qclogo]
50 E-Business Way
Suite 300
Cincinnati, OH 4524
Hi,
I’m pretty sure that autoResize is an attribute of the inputTextarea not
inputText and inputNumber
(So the editor is correct)
> On 02 Jul 2019, at 16:46, Cisco505 wrote:
>
> I'm getting this error in the editor view,
>
>
>
> The view is a facelet and the composition is :
>
>
>
> The
I'm getting this error in the editor view,
[image: image.png]
The view is a facelet and the composition is :
[image: image.png]
The same error with inputNumber:
[image: image.png]
The versión of primefaces is 6.1.
Any Suggestions?.
Dear Geertjan and Laszlo,
Thanks both for the help. But the source/binary field was already set to JDK12
(see the screenshot in my email of 12:01 yesterday).
It's very odd. I tried again yesterday after getting Geertjan's email and it
built OK without my changing anything. Then I shut down the
I too searched for a solution in my case with TestNG. I did not want to
contaminate the module.info with test lines that had to be edited out once
testing was passed successfully. Defeats one object of black box
integration testing adding a risk that an inadvertent change crept in.
My solution was
Hi all,
I use NB 11.0 and I work on JPMS module with integrations tests. My folder
structure is like this:
.
|-- pom.xml
`-- src
|-- it
| `-- java
| `-- com
| `-- soebes
| `-- maui
| `-- it
| `-- B
