headers
Pawel S. Veselov (JIRA | 1 Nov 2007 02:03

[jira] Created: (MOJO-944) javah is not looked up in ${jdk.home}

javah is not looked up in ${jdk.home}
-------------------------------------

                 Key: MOJO-944
                 URL: http://jira.codehaus.org/browse/MOJO-944
             Project: Mojo
          Issue Type: Bug
          Components: native
         Environment: Linux
            Reporter: Pawel S. Veselov

When native:javah is executed, the "javah" path is used for the binary. Only on MacOS, the
${jdk.home}/bin/javah is used.
${java.home} should be used at all times, because:
a) One doesn't have to add JDK bin directory to current PATH
b) The JDK directory in the path may not be the same that is used for Maven
c) the javah binary in the path may not even be JavaH

The trivial fix is to roll up org.codehaus.mojo.natives.javah.JavahMacOSExecutable into org.codehaus.mojo.natives.javah.JavahExecutable.

Anyone knows how to make native pick up the MacOS executable as a workaround ?

-- Pawel.

--

-- 
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
(Continue reading)

Permalink | Reply | 23 comments |
headers
Pawel S. Veselov (JIRA | 1 Nov 2007 02:05

[jira] Commented: (MOJO-944) javah is not looked up in ${jdk.home}


    [
http://jira.codehaus.org/browse/MOJO-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112304
] 

Pawel S. Veselov commented on MOJO-944:
---------------------------------------

The javah binary full path should actually be configurable.

> javah is not looked up in ${jdk.home}
> -------------------------------------
>
>                 Key: MOJO-944
>                 URL: http://jira.codehaus.org/browse/MOJO-944
>             Project: Mojo
>          Issue Type: Bug
>          Components: native
>         Environment: Linux
>            Reporter: Pawel S. Veselov
>
> When native:javah is executed, the "javah" path is used for the binary. Only on MacOS, the
${jdk.home}/bin/javah is used.
> ${java.home} should be used at all times, because:
> a) One doesn't have to add JDK bin directory to current PATH
> b) The JDK directory in the path may not be the same that is used for Maven
> c) the javah binary in the path may not even be JavaH
> The trivial fix is to roll up org.codehaus.mojo.natives.javah.JavahMacOSExecutable into org.codehaus.mojo.natives.javah.JavahExecutable.
> Anyone knows how to make native pick up the MacOS executable as a workaround ?
> -- Pawel.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dan Tran (JIRA | 1 Nov 2007 04:24

[jira] Commented: (MOJO-944) javah is not looked up in ${jdk.home}


    [
http://jira.codehaus.org/browse/MOJO-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112307
] 

Dan Tran commented on MOJO-944:
-------------------------------

how about submitting patch to allow the plugin to override the default javah default location? with test ofcourse

> javah is not looked up in ${jdk.home}
> -------------------------------------
>
>                 Key: MOJO-944
>                 URL: http://jira.codehaus.org/browse/MOJO-944
>             Project: Mojo
>          Issue Type: Bug
>          Components: native
>         Environment: Linux
>            Reporter: Pawel S. Veselov
>
> When native:javah is executed, the "javah" path is used for the binary. Only on MacOS, the
${jdk.home}/bin/javah is used.
> ${java.home} should be used at all times, because:
> a) One doesn't have to add JDK bin directory to current PATH
> b) The JDK directory in the path may not be the same that is used for Maven
> c) the javah binary in the path may not even be JavaH
> The trivial fix is to roll up org.codehaus.mojo.natives.javah.JavahMacOSExecutable into org.codehaus.mojo.natives.javah.JavahExecutable.
> Anyone knows how to make native pick up the MacOS executable as a workaround ?
> -- Pawel.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pawel S. Veselov (JIRA | 1 Nov 2007 07:28

[jira] Commented: (MOJO-944) javah is not looked up in ${jdk.home}


    [
http://jira.codehaus.org/browse/MOJO-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112313
] 

Pawel S. Veselov commented on MOJO-944:
---------------------------------------

ok, hold on a bit

> javah is not looked up in ${jdk.home}
> -------------------------------------
>
>                 Key: MOJO-944
>                 URL: http://jira.codehaus.org/browse/MOJO-944
>             Project: Mojo
>          Issue Type: Bug
>          Components: native
>         Environment: Linux
>            Reporter: Pawel S. Veselov
>
> When native:javah is executed, the "javah" path is used for the binary. Only on MacOS, the
${jdk.home}/bin/javah is used.
> ${java.home} should be used at all times, because:
> a) One doesn't have to add JDK bin directory to current PATH
> b) The JDK directory in the path may not be the same that is used for Maven
> c) the javah binary in the path may not even be JavaH
> The trivial fix is to roll up org.codehaus.mojo.natives.javah.JavahMacOSExecutable into org.codehaus.mojo.natives.javah.JavahExecutable.
> Anyone knows how to make native pick up the MacOS executable as a workaround ?
> -- Pawel.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kevin Stembridge (JIRA | 1 Nov 2007 10:04

[jira] Commented: (MWEBSTART-54) JnlpDownloadServlet does not filter out system and test scope dependencies


    [
http://jira.codehaus.org/browse/MWEBSTART-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112319
] 

Kevin Stembridge commented on MWEBSTART-54:
-------------------------------------------

Can I give this issue a nudge :)

Also, if you have some spare time, could you deploy another snapshot to the repo? 

> JnlpDownloadServlet does not filter out system and test scope dependencies
> --------------------------------------------------------------------------
>
>                 Key: MWEBSTART-54
>                 URL: http://jira.codehaus.org/browse/MWEBSTART-54
>             Project: Maven 2.x Webstart Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-2
>            Reporter: Kevin Stembridge
>         Attachments: MWEBSTART-54.diff
>
>
> As per the summary.
> I'll get started on a patch.

--

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

Permalink | Reply | 0 comments |
headers
Marat Radchenko (JIRA | 1 Nov 2007 11:10

[jira] Commented: (MOJO-942) Allow for wildcard specification of contexts


    [
http://jira.codehaus.org/browse/MOJO-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112323
] 

Marat Radchenko commented on MOJO-942:
--------------------------------------

Do you want
# Multiple source directories with separate excludes/includes
or
# Multiple source directories with global excludes/includes
or
# Single source directory with single excludes/includes
?

Btw. Currently you point one of the <resource> to a directory and plugin will automatically collect all
*.xml files from it [however, not recursively].

> Allow for wildcard specification of contexts
> --------------------------------------------
>
>                 Key: MOJO-942
>                 URL: http://jira.codehaus.org/browse/MOJO-942
>             Project: Mojo
>          Issue Type: Improvement
>          Components: springbeandoc
>         Environment: N/A
>            Reporter: David J. M. Karlsen
>            Assignee: Marat Radchenko
(Continue reading)

Permalink | Reply | 0 comments |
headers
David J. M. Karlsen (JIRA | 1 Nov 2007 12:12

[jira] Commented: (MOJO-937) org.codehaus.mojo:maven-springbeandoc-plugin fails when generating site-report


    [
http://jira.codehaus.org/browse/MOJO-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112324
] 

David J. M. Karlsen commented on MOJO-937:
------------------------------------------

Got it to work now - was missing some other dependencies (I couldn't reach the net.sf repo).
Thus - this issue can be closed.

> org.codehaus.mojo:maven-springbeandoc-plugin fails when generating site-report
> ------------------------------------------------------------------------------
>
>                 Key: MOJO-937
>                 URL: http://jira.codehaus.org/browse/MOJO-937
>             Project: Mojo
>          Issue Type: Bug
>         Environment: maven 2.0.7/JDK 1.6.0_03
>            Reporter: David J. M. Karlsen
>            Assignee: Marat Radchenko
>            Priority: Critical
>
> The springbeandoc plugin fails during site-generation:
> -----------------------------------------------------
> this realm = app0.child-container[org.codehaus.mojo:maven-springbeandoc-plugin]
> urls[0] = file:/c:/data/.m2/repository/org/codehaus/mojo/maven-springbeandoc-plugin/1.0.8-SNAPSHOT/maven-springbeandoc-p
> lugin-1.0.8-SNAPSHOT.jar
> urls[1] = file:/c:/data/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> Number of imports: 4
(Continue reading)

Permalink | Reply | 0 comments |
headers
David J. M. Karlsen (JIRA | 1 Nov 2007 12:12

[jira] Closed: (MOJO-937) org.codehaus.mojo:maven-springbeandoc-plugin fails when generating site-report


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

David J. M. Karlsen closed MOJO-937.
------------------------------------

    Resolution: Cannot Reproduce

User error.

> org.codehaus.mojo:maven-springbeandoc-plugin fails when generating site-report
> ------------------------------------------------------------------------------
>
>                 Key: MOJO-937
>                 URL: http://jira.codehaus.org/browse/MOJO-937
>             Project: Mojo
>          Issue Type: Bug
>         Environment: maven 2.0.7/JDK 1.6.0_03
>            Reporter: David J. M. Karlsen
>            Assignee: Marat Radchenko
>            Priority: Critical
>
> The springbeandoc plugin fails during site-generation:
> -----------------------------------------------------
> this realm = app0.child-container[org.codehaus.mojo:maven-springbeandoc-plugin]
> urls[0] = file:/c:/data/.m2/repository/org/codehaus/mojo/maven-springbeandoc-plugin/1.0.8-SNAPSHOT/maven-springbeandoc-p
> lugin-1.0.8-SNAPSHOT.jar
> urls[1] = file:/c:/data/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> Number of imports: 4
(Continue reading)

Permalink | Reply | 0 comments |
headers
Eirik Bjørsnøs (JIRA | 1 Nov 2007 13:02

[jira] Assigned: (MOJO-943) Web applications and flexible relsources dependencies support with internet enabling.


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

Eirik Bjørsnøs reassigned MOJO-943:
-----------------------------------

    Assignee: Eirik Bjørsnøs

> Web applications and flexible relsources dependencies support with internet enabling.
> -------------------------------------------------------------------------------------
>
>                 Key: MOJO-943
>                 URL: http://jira.codehaus.org/browse/MOJO-943
>             Project: Mojo
>          Issue Type: Improvement
>          Components: osxappbundle
>            Reporter: Oleksandr Maksymchuk
>            Assignee: Eirik Bjørsnøs
>         Attachments: osxappbundle-maven-plugin.patch
>
>
> I've used plugin you contributed to mojo and modified it greatly to be
> more flexible to package my web application having different structure
> from simple jar applications.
> Generealy I had issues running it and some confusion with version in
> svn and sources in repo, so I needed to change:
> -     *  <at> component
> role="org.codehaus.plexus.velocity.VelocityComponent"
> role-hint="default"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marat Radchenko (JIRA | 1 Nov 2007 13:36

[jira] Commented: (MOJO-942) Allow for wildcard specification of contexts


    [
http://jira.codehaus.org/browse/MOJO-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112329
] 

Marat Radchenko commented on MOJO-942:
--------------------------------------

I've implemented second option. Please test against build 1.0.8-20071101.123449-9 (current latest
snapshot) or later.

> Allow for wildcard specification of contexts
> --------------------------------------------
>
>                 Key: MOJO-942
>                 URL: http://jira.codehaus.org/browse/MOJO-942
>             Project: Mojo
>          Issue Type: Improvement
>          Components: springbeandoc
>         Environment: N/A
>            Reporter: David J. M. Karlsen
>            Assignee: Marat Radchenko
>            Priority: Critical
>
> Allow for wildcard expressions for the context's in the resources/resource section (like
*-context.xml and/or **/*-context.xml).
> This will allow for a more smooth configuration - which automatically can discover new context's without
having to define these explicitly.

--

--
(Continue reading)

Permalink | Reply | 0 comments |

Gmane