Rahul Thakur | 1 Jan 01:04 2007
Picon

[vote] Release Jpox Maven Plugin 1.0.4

The JPOX Maven Plugin has been updated recently to support execution of 
SchemaTool with different modes and pass properties via plugin 
configuration, or override them from commandline.

I would like to call for a vote to release 1.0.4.

Cheers,

Rahul 

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Rahul Thakur | 1 Jan 01:10 2007
Picon

Re: [vote] Release Jpox Maven Plugin 1.0.4

opps forgot my +1

----- Original Message ----- 
From: "Rahul Thakur" <rahul.thakur.xdev <at> gmail.com>
To: <dev <at> mojo.codehaus.org>
Sent: Monday, January 01, 2007 1:04 PM
Subject: [mojo-dev] [vote] Release Jpox Maven Plugin 1.0.4

> The JPOX Maven Plugin has been updated recently to support execution 
> of SchemaTool with different modes and pass properties via plugin 
> configuration, or override them from commandline.
>
> I would like to call for a vote to release 1.0.4.
>
> Cheers,
>
> Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
> 

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

(Continue reading)

Brett Porter | 1 Jan 01:14 2007
Picon

Re: [vote] Release Jpox Maven Plugin 1.0.4

+1, but it should be changed to 1.1 given the feature enhancement.

On 01/01/2007, at 11:10 AM, Rahul Thakur wrote:

> opps forgot my +1
>
>
> ----- Original Message ----- From: "Rahul Thakur"  
> <rahul.thakur.xdev <at> gmail.com>
> To: <dev <at> mojo.codehaus.org>
> Sent: Monday, January 01, 2007 1:04 PM
> Subject: [mojo-dev] [vote] Release Jpox Maven Plugin 1.0.4
>
>
>> The JPOX Maven Plugin has been updated recently to support  
>> execution of SchemaTool with different modes and pass properties  
>> via plugin configuration, or override them from commandline.
>>
>> I would like to call for a vote to release 1.0.4.
>>
>> Cheers,
>>
>> Rahul
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>
>
(Continue reading)

Julien HENRY (JIRA | 2 Jan 09:33 2007

[jira] Commented: (MEXEC-13) Need way to add a source folder to the project

    [ http://jira.codehaus.org/browse/MEXEC-13?page=comments#action_83783 ] 

Julien HENRY commented on MEXEC-13:
-----------------------------------

I'm using sourceRoot, and it works fine, thanks. 

I don't use testSourceRoot in my project, but I think it should work too.

> Need way to add a source folder to the project
> ----------------------------------------------
>
>                 Key: MEXEC-13
>                 URL: http://jira.codehaus.org/browse/MEXEC-13
>             Project: Mojo Exec Plugin
>          Issue Type: New Feature
>    Affects Versions: 1.0.2
>            Reporter: Julien HENRY
>         Assigned To: Jerome Lacoste
>            Priority: Minor
>             Fix For: 1.1
>
>
> Like the antrun plugin, the exec plugin can be used to generate new sources files. It may be usefull to have a
new parameter (sourceRoot, testSourceRoot) with the same behavior.

--

-- 
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)

Jurgen De Landsheer (JIRA | 2 Jan 10:22 2007

[jira] Commented: (MOJO-212) Maven 2 Spring BeanDoc plugin & site report (simple wrapper)

    [ http://jira.codehaus.org/browse/MOJO-212?page=comments#action_83787 ] 

Jurgen De Landsheer commented on MOJO-212:
------------------------------------------

you can safely remove this dependency (sneaked in)

<dependency>
<groupId>be.ugent.dict</groupId>
<artifactId>maven-plugins-common</artifactId>
<version>1.0.0-beta-1</version>
</dependency>

> Maven 2 Spring BeanDoc plugin & site report (simple wrapper)
> ------------------------------------------------------------
>
>                 Key: MOJO-212
>                 URL: http://jira.codehaus.org/browse/MOJO-212
>             Project: Mojo
>          Issue Type: New Feature
>          Components: Plugin Submission
>            Reporter: Jurgen De Landsheer
>         Attachments: maven2-spring-beans-plugin.zip, maven2-spring-beans-plugin.zip, maven2-spring-beans-plugin.zip
>
>
> new plugin: creates report from spring xml bean configurations
> for examples see http://springframework.sourceforge.net/beandoc/

--

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

Jerome Lacoste (JIRA | 2 Jan 11:22 2007

[jira] Closed: (MWEBSTART-8) support native libraries

     [ http://jira.codehaus.org/browse/MWEBSTART-8?page=all ]

Jerome Lacoste closed MWEBSTART-8.
----------------------------------

         Assignee: Jerome Lacoste
       Resolution: Incomplete
    Fix Version/s: 1.0-alpha-2

After thinking about it, I don't want to touch this until I get a more complete use case. Minimal support can
be added quickly (along the lines of the incomplete patch I provided), but we probably want to support at
least <resources> attributes such as os or arch.

If someone comes with a real life test case, then I will look into it.

A good test case might be to try to support jdic (https://jdic.dev.java.net/documentation/deployment.html).

> support native libraries
> ------------------------
>
>                 Key: MWEBSTART-8
>                 URL: http://jira.codehaus.org/browse/MWEBSTART-8
>             Project: Maven 2.x Webstart Plugin
>          Issue Type: New Feature
>            Reporter: Jerome Lacoste
>         Assigned To: Jerome Lacoste
>             Fix For: 1.0-alpha-2
>
>         Attachments: MWEBSTART-8.diff
>
(Continue reading)

Jerome Lacoste (JIRA | 2 Jan 11:58 2007

[jira] Closed: (MWEBSTART-11) Support generation of JNLP components

     [ http://jira.codehaus.org/browse/MWEBSTART-11?page=all ]

Jerome Lacoste closed MWEBSTART-11.
-----------------------------------

         Assignee: Jerome Lacoste
       Resolution: Incomplete
    Fix Version/s: 1.0-alpha-2

The patch is incomplete. Except if I am mistaken, one can provide support by having your own template:

In your template use, replace

 <application-desc main-class="${config.jnlp.mainClass}">

by what you need.

> Support generation of JNLP components
> -------------------------------------
>
>                 Key: MWEBSTART-11
>                 URL: http://jira.codehaus.org/browse/MWEBSTART-11
>             Project: Maven 2.x Webstart Plugin
>          Issue Type: New Feature
>            Reporter: Turadg Aleahmad
>         Assigned To: Jerome Lacoste
>             Fix For: 1.0-alpha-2
>
>         Attachments: JnlpConfig.java.diff
>
(Continue reading)

Jerome Lacoste (JIRA | 2 Jan 16:32 2007

[jira] Updated: (MWEBSTART-13) support running the webstart:jnlp plugin alongside a normal pom, without having to use multiprojects

     [ http://jira.codehaus.org/browse/MWEBSTART-13?page=all ]

Jerome Lacoste updated MWEBSTART-13:
------------------------------------

    Attachment: MWEBSTART-13.diff

I would like to fix this and would appreciate your input.

Here's a very rough/untested patch that tries to address the issue.

I modelled the change after the current design of the assembly plugin.

The assembly plugin seems to need to have 3 mojos defined to cover various cases. E.g. for the directory
goal: directory, directory-inline, directory-single. The third one differs from the first by removing
the specified  <at> phase and using the project instead of executedProject instead.
The second one differs from the third by removing the  <at> aggregator tag.

http://maven.apache.org/plugins/maven-assembly-plugin/

So if I want to support something similar in jnlp, we can try the following attached patch.

2 words of caution:

- not sure if I need to move the workDirectory definition out of the abstract class (because the default
value comes from project.build.... and I am not sure this one is defined in the jnlp:jnlp mojo (that now
uses executedProject instead of project)
- I've added  <at> aggregator to the default jnlp mojo. I am not sure if that one will have an impact or not on your
builds. Is so you may need to use the jnlp-inline instead

(Continue reading)

Jerome Lacoste (JIRA | 2 Jan 16:32 2007

[jira] Updated: (MWEBSTART-1) [webstart] deal with already signed jars

     [ http://jira.codehaus.org/browse/MWEBSTART-1?page=all ]

Jerome Lacoste updated MWEBSTART-1:
-----------------------------------

    Summary: [webstart] deal with already signed jars  (was: [webstart] deal with unsigned jars)

Fixed summary

> [webstart] deal with already signed jars
> ----------------------------------------
>
>                 Key: MWEBSTART-1
>                 URL: http://jira.codehaus.org/browse/MWEBSTART-1
>             Project: Maven 2.x Webstart Plugin
>          Issue Type: New Feature
>            Reporter: Jerome Lacoste
>         Assigned To: Jerome Lacoste
>         Attachments: MWEBSTART-1-test.sh
>
>
> There are potential issues when dealing with including such already signed jars in a webstart application.
> In particular see:
> http://jira.codehaus.org/browse/MOJO-7#action_49160
> and the relevant m1 jnlp issues:
> http://jira.codehaus.org/browse/MPJNLP-20
> http://jira.codehaus.org/browse/MPJNLP-28
> According to the feedback I got on the maven user list, I think that, in order to satisfy everybody, we need to:
> - handle already signed jars (MPJNLP-28)
>   - primarily we need the possibility to unsign a jar. That will probably go to jar:unsign.
(Continue reading)

Jerome Lacoste (JIRA | 2 Jan 16:32 2007

[jira] Assigned: (MWEBSTART-13) support running the webstart:jnlp plugin alongside a normal pom, without having to use multiprojects

     [ http://jira.codehaus.org/browse/MWEBSTART-13?page=all ]

Jerome Lacoste reassigned MWEBSTART-13:
---------------------------------------

    Assignee: Jerome Lacoste

> support running the webstart:jnlp plugin alongside a normal pom, without having to use multiprojects
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MWEBSTART-13
>                 URL: http://jira.codehaus.org/browse/MWEBSTART-13
>             Project: Maven 2.x Webstart Plugin
>          Issue Type: New Feature
>            Reporter: Jerome Lacoste
>         Assigned To: Jerome Lacoste
>            Priority: Minor
>         Attachments: MWEBSTART-13.diff
>
>
> Today, you cannot do something like
> mvn install webstart:jnlp
> hoping that your freshly installed artifact gets packaged into your jnlp artifact. The reason, I didn't
think it was necessary because of the one artifact one module rule. If you feel otherwise, please vote on
this issue.

--

-- 
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)


Gmane