headers
Mark Michaelis (JIRA | 1 Oct 2010 08:31

[jira] Updated: (MTOMCAT-55) Can't shutdown tomcat started with tomcat:run with fork=true


     [
http://jira.codehaus.org/browse/MTOMCAT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Michaelis updated MTOMCAT-55:
----------------------------------

    Attachment: MTOMCAT-55.patch

Attached the SVN Diff-Version of the patch [^MTOMCAT-55.patch].

> Can't shutdown tomcat started with tomcat:run with fork=true
> ------------------------------------------------------------
>
>                 Key: MTOMCAT-55
>                 URL: http://jira.codehaus.org/browse/MTOMCAT-55
>             Project: Maven 2.x Tomcat Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: ant elder
>         Attachments: 0003-Fix-for-http-jira.codehaus.org-browse-MTOMCAT-55.patch, MTOMCAT-55.patch
>
>
> MTOMCAT-20 added the fork option but there doesn't appear to be any way to shutdown that forked instance.
Doesn't there needs to be something like a shutdown goal and add parameters to both run and fork to
configure the shutdown port and key?

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mark Michaelis (JIRA | 1 Oct 2010 08:35

[jira] Commented: (MTOMCAT-55) Can't shutdown tomcat started with tomcat:run with fork=true


    [
http://jira.codehaus.org/browse/MTOMCAT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237069#action_237069
] 

Mark Michaelis commented on MTOMCAT-55:
---------------------------------------

Oh, please don't hesitate to adjust the Copyright-Statement in EmbeddedRegistry. It of course applies to
the same license you have chosen (Apache, I think).

> Can't shutdown tomcat started with tomcat:run with fork=true
> ------------------------------------------------------------
>
>                 Key: MTOMCAT-55
>                 URL: http://jira.codehaus.org/browse/MTOMCAT-55
>             Project: Maven 2.x Tomcat Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: ant elder
>         Attachments: 0003-Fix-for-http-jira.codehaus.org-browse-MTOMCAT-55.patch, MTOMCAT-55.patch
>
>
> MTOMCAT-20 added the fork option but there doesn't appear to be any way to shutdown that forked instance.
Doesn't there needs to be something like a shutdown goal and add parameters to both run and fork to
configure the shutdown port and key?

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gábor Lipták (JIRA | 1 Oct 2010 09:21

[jira] Created: (MOJO-1574) I cannot specify JVM to run on, and the -server argument is wired into the code. This will fail running on JRE

I cannot specify JVM to run on, and the -server argument is wired into the code. This will fail running on JRE
--------------------------------------------------------------------------------------------------------------

                 Key: MOJO-1574
                 URL: http://jira.codehaus.org/browse/MOJO-1574
             Project: Mojo
          Issue Type: Bug
          Components: chronos
            Reporter: Gábor Lipták
            Assignee: Kent Soelvsten
         Attachments: chronos.patch

My problem is, that I cannot tell in the configuration of the plugin, that wich JVM to run with. As I realized,
the java.exe which is on path is used by the plugin. This is a bad thing if this JVM is a JRE, since in
org.codehaus.mojo.chronos.jmeter.JMeterMojo in method getJavaLauncher it is wired in that
"-server" argument is always present. As an easy workaround I removed it from my version (since I had to
download source to create a non-snapshot version of it locally).

The best solution would be to provide a configuration setting to enable pick JVM for it. Then it could be
handled nicely with using profiles.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:
(Continue reading)

Permalink | Reply | 9 comments |
headers
Gábor Lipták (JIRA | 1 Oct 2010 09:23

[jira] Commented: (MOJO-1574) I cannot specify JVM to run on, and the -server argument is wired into the code. This will fail running on JRE


    [
http://jira.codehaus.org/browse/MOJO-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237071#action_237071
] 

Gábor Lipták commented on MOJO-1574:
------------------------------------

And a comment: this is mainly because JRE do not have -server argument.

> I cannot specify JVM to run on, and the -server argument is wired into the code. This will fail running on JRE
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MOJO-1574
>                 URL: http://jira.codehaus.org/browse/MOJO-1574
>             Project: Mojo
>          Issue Type: Bug
>          Components: chronos
>            Reporter: Gábor Lipták
>            Assignee: Kent Soelvsten
>         Attachments: chronos.patch
>
>
> My problem is, that I cannot tell in the configuration of the plugin, that wich JVM to run with. As I
realized, the java.exe which is on path is used by the plugin. This is a bad thing if this JVM is a JRE, since in
org.codehaus.mojo.chronos.jmeter.JMeterMojo in method getJavaLauncher it is wired in that
"-server" argument is always present. As an easy workaround I removed it from my version (since I had to
download source to create a non-snapshot version of it locally).
> The best solution would be to provide a configuration setting to enable pick JVM for it. Then it could be
handled nicely with using profiles.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gábor Lipták (JIRA | 1 Oct 2010 09:30

[jira] Created: (MOJO-1575) In POM the schema is not specified, and since then code completion dont work in Eclipse for example

In POM the schema is not specified, and since then code completion dont work in Eclipse for example
---------------------------------------------------------------------------------------------------

                 Key: MOJO-1575
                 URL: http://jira.codehaus.org/browse/MOJO-1575
             Project: Mojo
          Issue Type: Bug
          Components: chronos
            Reporter: Gábor Lipták
            Assignee: Kent Soelvsten
            Priority: Minor
         Attachments: chronos2.patch

The correct header is like this:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
...

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:
(Continue reading)

Permalink | Reply | 4 comments |
headers
Geoffrey De Smet (JIRA | 1 Oct 2010 10:22

[jira] Reopened: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies


     [
http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey De Smet reopened MGWT-219:
-----------------------------------

Reopening: In the Eclipse and IntelliJ plugin we can set the order of the entry's in the classpath given to
the gwt compiler process. Having that same ability in the maven gwt plugin will allow us to use this plugin
instead of an ant build (and get rid all the trouble the ant build represents).
Even though you're right that the gwt classpath is a mess (mixing client and server side classpaths and
whatnot), it doesn't look like they'll fix it anytime soon, so please reconsider supporting the same
feature as the Eclipse and IntelliJ plugin to at least have some control over the gwt plugin.
Also note that both the eclipse and the intellij plugin, by default, put the gwt-dev dependency first, not last.

> In gwt:compile the gwt-dev library should be on the classpath before the project dependencies
> ---------------------------------------------------------------------------------------------
>
>                 Key: MGWT-219
>                 URL: http://jira.codehaus.org/browse/MGWT-219
>             Project: Maven 2.x GWT Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Geoffrey De Smet
>            Priority: Critical
>
> When compiling drools-guvnor with gwt:compile I does this:
> ...java -Xmx512m -classpath "/home/ge0ffrey/projects/jboss/drools/drools-guvnor/src/main/java":
> "/home/ge0ffrey/projects/jboss/drools/drools-guvnor/src/main/resources":
> "/home/ge0ffrey/projects/jboss/drools/drools-guvnor/target/classes":
(Continue reading)

Permalink | Reply | 0 comments |
headers
Geoffrey De Smet (JIRA | 1 Oct 2010 10:24

[jira] Issue Comment Edited: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies


    [
http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237075#action_237075
] 

Geoffrey De Smet edited comment on MGWT-219 at 10/1/10 3:22 AM:
----------------------------------------------------------------

Reopening: In the Eclipse and IntelliJ plugin we can set the order of the entry's in the classpath given to
the gwt compiler process. Having that same ability in the maven gwt plugin will allow us to use this plugin
instead of an ant build (and get rid all the trouble the ant build represents).
Even though you're right that the gwt classpath is a mess (mixing client and server side classpaths and
whatnot), it doesn't look like they'll fix it anytime soon, so please reconsider supporting the same
feature as the Eclipse and IntelliJ plugin to at least have some control over the gwt compiler classpath.
Also note that both the eclipse and the intellij plugin, by default, put the gwt-dev dependency first, not last.

      was (Author: ge0ffrey):
    Reopening: In the Eclipse and IntelliJ plugin we can set the order of the entry's in the classpath given to
the gwt compiler process. Having that same ability in the maven gwt plugin will allow us to use this plugin
instead of an ant build (and get rid all the trouble the ant build represents).
Even though you're right that the gwt classpath is a mess (mixing client and server side classpaths and
whatnot), it doesn't look like they'll fix it anytime soon, so please reconsider supporting the same
feature as the Eclipse and IntelliJ plugin to at least have some control over the gwt plugin.
Also note that both the eclipse and the intellij plugin, by default, put the gwt-dev dependency first, not last.

> In gwt:compile the gwt-dev library should be on the classpath before the project dependencies
> ---------------------------------------------------------------------------------------------
>
>                 Key: MGWT-219
>                 URL: http://jira.codehaus.org/browse/MGWT-219
(Continue reading)

Permalink | Reply | 0 comments |
headers
ant elder (JIRA | 1 Oct 2010 10:34

[jira] Commented: (MTOMCAT-55) Can't shutdown tomcat started with tomcat:run with fork=true


    [
http://jira.codehaus.org/browse/MTOMCAT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237080#action_237080
] 

ant elder commented on MTOMCAT-55:
----------------------------------

This is terrific Mark, really looking forward to it getting out in a release.

> Can't shutdown tomcat started with tomcat:run with fork=true
> ------------------------------------------------------------
>
>                 Key: MTOMCAT-55
>                 URL: http://jira.codehaus.org/browse/MTOMCAT-55
>             Project: Maven 2.x Tomcat Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: ant elder
>         Attachments: 0003-Fix-for-http-jira.codehaus.org-browse-MTOMCAT-55.patch, MTOMCAT-55.patch
>
>
> MTOMCAT-20 added the fork option but there doesn't appear to be any way to shutdown that forked instance.
Doesn't there needs to be something like a shutdown goal and add parameters to both run and fork to
configure the shutdown port and key?

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
(Continue reading)

Permalink | Reply | 0 comments |
headers
Olivier Lamy (JIRA | 1 Oct 2010 11:08

[jira] Closed: (MTOMCAT-55) Can't shutdown tomcat started with tomcat:run with fork=true


     [
http://jira.codehaus.org/browse/MTOMCAT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MTOMCAT-55.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1
         Assignee: Olivier Lamy

fixed [rev 12745|http://fisheye.codehaus.org/changelog/mojo/?cs=12745]
As you agreed the license has been changed to ASF.
Thanks for your great patch !!

> Can't shutdown tomcat started with tomcat:run with fork=true
> ------------------------------------------------------------
>
>                 Key: MTOMCAT-55
>                 URL: http://jira.codehaus.org/browse/MTOMCAT-55
>             Project: Maven 2.x Tomcat Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: ant elder
>            Assignee: Olivier Lamy
>             Fix For: 1.1
>
>         Attachments: 0003-Fix-for-http-jira.codehaus.org-browse-MTOMCAT-55.patch, MTOMCAT-55.patch
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Geoffrey De Smet (JIRA | 1 Oct 2010 11:29

[jira] Updated: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies


     [
http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey De Smet updated MGWT-219:
----------------------------------

    Attachment: MGWT-219.patch

Attached patch to set gwt-dev library first on the classpath given to the GWT compiler.
Justification:
- The Eclipse and IntelliJ plugin do this too and the default behavior of the maven plugin, the eclipse and
the IntelliJ plugin should not differ.
- Without this patch, none of the projects that depend on GWT and JDT (directly or indirectly) can be build
with this maven plugin. This includes but is not limited to: drools-guvnor, all projects that depend on
drools-guvnor (this is extended a lot in-house), ...
- This has been a long standing issue with the gwt-maven plugins: http://code.google.com/p/gwt-maven/issues/detail?id=79

> In gwt:compile the gwt-dev library should be on the classpath before the project dependencies
> ---------------------------------------------------------------------------------------------
>
>                 Key: MGWT-219
>                 URL: http://jira.codehaus.org/browse/MGWT-219
>             Project: Maven 2.x GWT Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Geoffrey De Smet
>            Priority: Critical
>         Attachments: MGWT-219.patch
>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane