[jira] Created: (MACR-2) Initial documentation
Initial documentation - Key: MACR-2 URL: http://jira.codehaus.org/browse/MACR-2 Project: Maven ACR Plugin Issue Type: Improvement Affects Versions: 1.0 Reporter: Stephane Nicoll Create a simple documentation for the plugin. -- 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
[jira] Work started: (MACR-2) Initial documentation
[ http://jira.codehaus.org/browse/MACR-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MACR-2 started by Stephane Nicoll. > Initial documentation > - > > Key: MACR-2 > URL: http://jira.codehaus.org/browse/MACR-2 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 1.0 >Reporter: Stephane Nicoll >Assignee: Stephane Nicoll > > Create a simple documentation for the plugin. -- 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
[jira] Resolved: (MACR-2) Initial documentation
[ http://jira.codehaus.org/browse/MACR-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll resolved MACR-2. Resolution: Fixed Fix Version/s: 1.0 > Initial documentation > - > > Key: MACR-2 > URL: http://jira.codehaus.org/browse/MACR-2 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 1.0 >Reporter: Stephane Nicoll >Assignee: Stephane Nicoll > Fix For: 1.0 > > > Create a simple documentation for the plugin. -- 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
[jira] Created: (MPLUGINTESTING-18) maven-plugin-testing-harness has file descriptors leaks
maven-plugin-testing-harness has file descriptors leaks --- Key: MPLUGINTESTING-18 URL: http://jira.codehaus.org/browse/MPLUGINTESTING-18 Project: Maven 2.x Plugin Testing Issue Type: Bug Reporter: Herve Boutemy this causes bugs on Windows platform when readers/writers or input/outputstreams are not closed -- 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
[jira] Closed: (MPLUGINTESTING-18) maven-plugin-testing-harness has file descriptors leaks
[ http://jira.codehaus.org/browse/MPLUGINTESTING-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGINTESTING-18. --- Resolution: Fixed Fix Version/s: 1.3 Assignee: Herve Boutemy fixed in [r1085807|http://svn.apache.org/viewvc?rev=1085803&view=rev] > maven-plugin-testing-harness has file descriptors leaks > --- > > Key: MPLUGINTESTING-18 > URL: http://jira.codehaus.org/browse/MPLUGINTESTING-18 > Project: Maven 2.x Plugin Testing > Issue Type: Bug >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 1.3 > > > this causes bugs on Windows platform when readers/writers or > input/outputstreams are not closed -- 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
[jira] Updated: (MPLUGINTESTING-17) Add Property to the execution of Maven in ProjectTool
[
http://jira.codehaus.org/browse/MPLUGINTESTING-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGINTESTING-17:
Description:
{{BuildTool}} fails during integration test prepararion when the {{help-mojo}}
of {{maven-plugin-plugin}} is executed. The guys from the Eclipse Plugin found
a workaround by disabling it. But so the plugin under test can't be built from
scratch any more. So they used a profile to run the integration tests and
disable {{help-mojo}} execution. If the {{BuildTool}} would set a property, a
separate profile could be used for different behaviour during integration
testing. A proper profile could then look like that
{code:xml}
failsafe-runnung-it
src/test/resources
**/*
org.apache.maven.plugins
maven-compiler-plugin
true
org.apache.maven.plugins
maven-plugin-plugin
2.4.3
help-mojo
org.codehaus.mojo
failsafe-maven-plugin
2.4.3-alpha-1
true
maven-plugin-testing-tools:ProjectTool:packageProjectArtifact
{code}
I used a working version of that in
[https://code.google.com/p/code-cop-code/wiki/MackerMavenPlugin].
was:
{{{BuildTool}}} fails during integration test prepararion when the
{{{help-mojo}}} of {{{maven-plugin-plugin} is executed. The guys from the
Eclipse Plugin found a workaround by disabling it. But so the plugin under test
can't be built from scratch any more. So they used a profile to run the
integration tests and disable {{{help-mojo}}} execution. If the {{{BuildTool}}}
would set a property, a separate profile could be used for different behaviour
during integration testing. A proper profile could then look like that
{{{
failsafe-runnung-it
src/test/resources
**/*
org.apache.maven.plugins
maven-compiler-plugin
true
org.apache.maven.plugins
maven-plugin-plugin
2.4.3
help-mojo
org.codehaus.mojo
failsafe-maven-plugin
2.4.3-alpha-1
true
maven-plugin-testing-tools:ProjectTool:packageProjectArtifact
}}}
I used a working version of that in
[https://code.google.com/p/code-cop-code/wiki/MackerMavenPlugin].
> Add Property to the execution of Maven in ProjectTool
> -
>
> Key: MPLUGINTESTING-17
> URL: http://jira.codehaus.org/browse/MPLUGINTESTING-17
> Project: Maven 2.x Plugin Testing
> Issue Type: Improvement
> Components: plugin-testing-tools
>Affects Versions: 1.2
>Reporter: Peter Kofler
>Priority: Minor
> Attachments: maven-plugin-testing-tools_property_patch.txt
>
>
> {{BuildTool}} fails during integration test prepararion when the
> {{help-mojo}} of {{maven-plugin-plugin}} is executed. The guys from the
> Eclipse Plugin found a workaround by disabling it. But so the plugin under
> test can't be built from scratch any more. So they used a profile to run the
> integration tests and disable {{help-mojo}} execution. If the {{BuildTool}}
> would set a property, a separate profile could be used for different
> behaviour during integration testing. A proper profile could then look like
> that
> {code:xml}
>
>
> failsafe-runnung-it
>
>
>
>
> src/test/resources
>
> **/*
>
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
[jira] Work started: (MEAR-137) Support for JEE Application Clients
[ http://jira.codehaus.org/browse/MEAR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MEAR-137 started by Stephane Nicoll. > Support for JEE Application Clients > --- > > Key: MEAR-137 > URL: http://jira.codehaus.org/browse/MEAR-137 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature > Environment: any >Reporter: Pablo Rodriguez >Assignee: Stephane Nicoll > Fix For: 2.6 > > Attachments: maven-ear-plugin > > > Currently the maven ear plugin only supports JEE application clients by > defining them as jarmodules with true. This > is a bit to hacky as Applicaiton client modules are first class EAR citizens > as ejb, war and rar modules. > The patch provided here is half of my attempt to upgrade this application > client modules to be maven ear first citizens. > I have created a maven-car-plugin defining a packaging type 'car' (in same > manner as war, ejb or rar). > http://code.google.com/p/maven-car-plugin/ > The patch provided here, adds support to maven-ear-plugin to recognize the > 'car' packaging type, include the artifact in the root of the ear and adds > the corresponding entry to application.xml > Note that i would like this to be temporary and would prefer to see the car > packaging type, the maven-car-plugin be core maven plugins with gorupid > org.maven.plugins as there is no reason for application clients not having > same support as war, ejb or rar modules. > I feel this extra module, packaging type and plugin are needed as confusion > has been arising around application clients > http://jira.codehaus.org/browse/MEAR-46 > http://jira.codehaus.org/browse/MEAR-40 > Pablo -- 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
[jira] Commented: (MEAR-137) Support for JEE Application Clients
[ http://jira.codehaus.org/browse/MEAR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261604#action_261604 ] Stephane Nicoll commented on MEAR-137: -- A candidate change has been added and a 2.6-SNAPSHOT has been deployed on the repository. Only make sense if you have the acr plugin as well (a release vote is ongoing) > Support for JEE Application Clients > --- > > Key: MEAR-137 > URL: http://jira.codehaus.org/browse/MEAR-137 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature > Environment: any >Reporter: Pablo Rodriguez >Assignee: Stephane Nicoll > Fix For: 2.6 > > Attachments: maven-ear-plugin > > > Currently the maven ear plugin only supports JEE application clients by > defining them as jarmodules with true. This > is a bit to hacky as Applicaiton client modules are first class EAR citizens > as ejb, war and rar modules. > The patch provided here is half of my attempt to upgrade this application > client modules to be maven ear first citizens. > I have created a maven-car-plugin defining a packaging type 'car' (in same > manner as war, ejb or rar). > http://code.google.com/p/maven-car-plugin/ > The patch provided here, adds support to maven-ear-plugin to recognize the > 'car' packaging type, include the artifact in the root of the ear and adds > the corresponding entry to application.xml > Note that i would like this to be temporary and would prefer to see the car > packaging type, the maven-car-plugin be core maven plugins with gorupid > org.maven.plugins as there is no reason for application clients not having > same support as war, ejb or rar modules. > I feel this extra module, packaging type and plugin are needed as confusion > has been arising around application clients > http://jira.codehaus.org/browse/MEAR-46 > http://jira.codehaus.org/browse/MEAR-40 > Pablo -- 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
