Hi,
I'd like to release version 1.1.1 of the Appassembler.
Appassembler generates bin and Java Service Wrapper scripts for Java
applications.
We solved 2 small issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11780&version=16887
Staging Repositories:
General: https://nexus.co
[
http://jira.codehaus.org/browse/MOJO-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252751#action_252751
]
Patrick Moore commented on MOJO-1413:
-
As a friend of mine, smart guy, works at google, said this:
+1 to move it to apache tomcat, it is better on the right expertise.
-D
On Mon, Jan 24, 2011 at 5:55 PM, Wayne Fay wrote:
> My +1 for the same reasons.
>
> Wayne
>
> On Mon, Jan 24, 2011 at 3:31 PM, Robert Scholte
> wrote:
>> Any other name wouldn't make sense and if the Tomcat team is willing
My +1 for the same reasons.
Wayne
On Mon, Jan 24, 2011 at 3:31 PM, Robert Scholte wrote:
> Any other name wouldn't make sense and if the Tomcat team is willing
> to maintain the Maven plugin for their own product, I can only agree.
> +1
>
> -Robert
>
>
> From: th
[
http://jira.codehaus.org/browse/MOJO-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252708#action_252708
]
Jochen Wiedmann commented on MOJO-1413:
---
I am sorry, but I can't follow you. The documentation o
Any other name wouldn't make sense and if the Tomcat team is willing to
maintain the Maven plugin for their own product, I can only agree.
+1
-Robert
From: thra...@gmx.net
Date: Mon, 24 Jan 2011 21:56:38 +0100
To: dev@mojo.codehaus.org
Subject: Re: [mojo-dev] [VOTE] move tomcat-maven-plugin
Hello,
as this means laying the plugin in the hands of the experts regarding Tomcat
7 migration I think this solution would help the Tomcat Maven Plugin to
survive. It's currently tightly bound to Tomcat in its very inner and I see
a chance that Tomcat experts will be able to untangle the threads.
> Is this closed as "fixed" to end the discussion? I still agree with you,
> Julien.
Yes it is.
> But if you can set a read-only field, something else is wrong...
>
The field was marked as readonly but has been removed since then as it was just
a shortcut to target/
Cheers
--
http://izpa
I don't know of any plans to move the jboss or jboss-packaging maven
plugins. Unless some new problem comes up, they will stay at Codehaus.
On 01/24/2011 11:39 AM, Robert Scholte wrote:
> No vote from me yet, but some additional questions.
>
> Will this be the beginning of the end for maven plu
Is this closed as "fixed" to end the discussion? I still agree with you,
Julien.
But if you can set a read-only field, something else is wrong...
-Robert
> Date: Mon, 24 Jan 2011 09:47:58 -0600
> From: j...@codehaus.org
> To: dev@mojo.codehaus.org
> Subject: [mojo-dev] [jira] Closed: (MLATEX
Olivier Lamy wrote:
Concerning auto detecting, yes it won't works anymore if users doesn't
add some in their settings.
But it's only a documentation material to add (and maybe something to
think solving on Maven side : don't how now)
Declaring the plugin in the POM's section will also work.
Hello,
I don't know for companies who own this names (JBoss, Weblogic).
But here the concerns is more about Apache related names.
Personnaly, I prefer this mojo having the Apache Tomcat Maven Plugin
name rather than something like thecat-maven-plugin :-).
And having more Tomcat core contributor int
No vote from me yet, but some additional questions.
Will this be the beginning of the end for maven plugins for any
application-server or or any product-specific plugin?
For Tomcat this will look pretty easy since some mojo-developers are also
involved in the Tomcat-project.
But what about JBo
+1
LieGrue,
strub
--- On Mon, 1/24/11, Arnaud Héritier wrote:
> From: Arnaud Héritier
> Subject: Re: [mojo-dev] [VOTE] move tomcat-maven-plugin from codehaus to the
> Apache Tomcat project
> To: dev@mojo.codehaus.org
> Date: Monday, January 24, 2011, 2:27 PM
> +1
>
> On Mon, Jan 24, 2011 at
[
http://jira.codehaus.org/browse/MOJO-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Rimbaud closed MOJO-1510.
Resolution: Fixed
see last comment
> transform fails after a 404 error even if a catalog file is given
>
[
http://jira.codehaus.org/browse/MOJO-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252666#action_252666
]
Julien Rimbaud commented on MOJO-1510:
--
I noted that the catalog file included a DOCTYPE - this
[
http://jira.codehaus.org/browse/MOJO-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Rimbaud updated MOJO-1510:
-
Attachment: test_mvn_xsl.zip
By making a test project, I just cannot transform without network, even wit
[
http://jira.codehaus.org/browse/MASPECTJ-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252660#action_252660
]
Timo Meinen commented on MASPECTJ-90:
-
Hi Robert,
thank you for your answer. Do you think the wr
[
http://jira.codehaus.org/browse/MLATEX-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Ponge closed MLATEX-7.
-
Resolution: Fixed
> buildDir is not documented in plugin site
> -
>
>
[
http://jira.codehaus.org/browse/MLATEX-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Ponge closed MLATEX-5.
-
Resolution: Fixed
Fix Version/s: 1.1
Fixed, LaTeX changes are now scanned.
> Conditional processing will
On Mon, 24 Jan 2011 09:00:06 -0600
Paul Gier wrote:
> Normally a plugin gets it's own jira project the 1.0 release [1].
> Let's try to complete the merge this week, and then next week we can
> call for a 1.0 release and a new jira project. Does that sound good?
Perfect to me :)
There is I think
[
http://jira.codehaus.org/browse/MLATEX-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Ponge closed MLATEX-4.
-
Resolution: Fixed
Fix Version/s: 1.1
Fixed by removing .svn folders. A general exclusion mechanism is wron
[
http://jira.codehaus.org/browse/MLATEX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Ponge closed MLATEX-8.
-
Resolution: Fixed
Fix Version/s: 1.1
I am closing the issue as Maven already provides useful mechanisms fo
I'm having trouble fully understanding the legal description at [1]
regarding this. Just changing the plugin name to "Maven Plugin for the
Apache Tomcat" isn't sufficient?
Or is the actual trouble the "tomcat-maven-plugin" string?
Anyways, I'm 0.
/Anders
[1] http://tomcat.apache.org/legal.html
On 01/23/2011 01:16 PM, chemit wrote:
> Hi,
>
> Yesterday I made a commit on the license-m-p and I never saw the commit
> on the scm mailing list (rev 13433).
>
> Note that just after I do a commit on the ci-aggregator and this commit
> was send to the scm mailing list (rev 13434).
>
> Paul made
[
http://jira.codehaus.org/browse/MFINDBUGS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252644#action_252644
]
Geoffrey De Smet edited comment on MFINDBUGS-129 at 1/24/11 8:36 AM:
---
[
http://jira.codehaus.org/browse/MFINDBUGS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252644#action_252644
]
Geoffrey De Smet commented on MFINDBUGS-129:
+1 to get findbugs 2.3.2 release as soon
+1
On Mon, Jan 24, 2011 at 3:23 PM, John Casey wrote:
> +1
>
> On 1/24/11 8:50 AM, Olivier Lamy wrote:
>>
>> Hi Folks,
>>
>> In order to resolve some trademarks issues with the mojo name, I'd
>> like to move the tomcat-maven-plugin to Apache Tomcat project.
>> The second reason is : IMHO it's pro
+1
On 24 January 2011 13:50, Olivier Lamy wrote:
> Hi Folks,
>
> In order to resolve some trademarks issues with the mojo name, I'd
> like to move the tomcat-maven-plugin to Apache Tomcat project.
> The second reason is : IMHO it's probably the best and more natural
> place for this to be hosted.
+1
On 1/24/11 8:50 AM, Olivier Lamy wrote:
Hi Folks,
In order to resolve some trademarks issues with the mojo name, I'd
like to move the tomcat-maven-plugin to Apache Tomcat project.
The second reason is : IMHO it's probably the best and more natural
place for this to be hosted.
If not moving t
Hi Folks,
In order to resolve some trademarks issues with the mojo name, I'd
like to move the tomcat-maven-plugin to Apache Tomcat project.
The second reason is : IMHO it's probably the best and more natural
place for this to be hosted.
If not moving this, we will have to think about renaming the
[
http://jira.codehaus.org/browse/MOJO-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252615#action_252615
]
Robert Munteanu commented on MOJO-1413:
---
I second that. I honestly gave up, as the article linke
[
http://jira.codehaus.org/browse/MOJO-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252614#action_252614
]
Patrick Moore commented on MOJO-1413:
-
(addendum: unclear documentation that makes the user figure
[
http://jira.codehaus.org/browse/MOJO-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252612#action_252612
]
Patrick Moore commented on MOJO-1413:
-
Delightful. RTFM.
It would make this plugin more useful f
34 matches
Mail list logo
