You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Laszlo Kishalmi (JIRA)" <ji...@apache.org> on 2018/04/20 23:44:00 UTC
[jira] [Commented] (NETBEANS-42) Netbeans Maven:Java Application
when run several times creates multiple instances (once for each time run),
resulting in a port confilct
[ https://issues.apache.org/jira/browse/NETBEANS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446510#comment-16446510 ]
Laszlo Kishalmi commented on NETBEANS-42:
-----------------------------------------
Well, knowing how Maven project works this is not necessary a trivial change.
Could you please provide at least the Maven archetype you are using or a sample maven project to test?
> Netbeans Maven:Java Application when run several times creates multiple instances (once for each time run), resulting in a port confilct
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NETBEANS-42
> URL: https://issues.apache.org/jira/browse/NETBEANS-42
> Project: NetBeans
> Issue Type: New Feature
> Components: apisupport - Project
> Affects Versions: 8.2
> Environment: Ubuntu Linux 17.04
> Reporter: Ken McWilliams
> Priority: Minor
>
> I generally use JEE and Glassfish to create web applications, however I've created a web application using Jetty which does not require a container. However each time I run the application I have to manually stop the currently running instance. This doesn't take long but it is a bit of a pain. I would like a smoother development cycle, I'm sure it can be automated at the command line and will do so, but I think it should be a pretty common issue.
> I'm creating my project using NB 8.2. File -> New Project -> Under Categories selecting "Maven", Under Projects "Java Application"
> Each time the project is run, a new running instance is deployed, such that after 5 runs there are 5 running programs (well that would normally be the case for this type of application but because of a port conflict I must stop the previous instance).
> Any of the following would be a viable solution:
> Ideally, if their is a running instance of the program it is compiled and relaunched on save, don't know if this is possible outside of a container like Glassfish.
> The application kills any previous deployment and compiles and runs a new instance when "Run Project" button is pressed (F6).
> Anything else that meets this intention.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists