Eugene Silinov skrev:
Hi David,
I started coding Maven Plug-in for ATG Dynamo http://www.atg.com. It
will be something similar to was-maven-plugin, but specifically for
ATG Dynamo. It will be possible to assemble ATG Module defined in POM,
deploy the module, etc. This plug-in is not going to be
[
http://jira.codehaus.org/browse/MOJO-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann closed MOJO-1108.
-
Resolution: Fixed
Thanks for the hint. I took this as an opportunity to finally move the plugins
source
I don't use ATG Dynamo myself but I'm certain that I would appreciate
such a plugin if/when I am in a position to use it. And I have to
imagine there are other people using Maven who would benefit from such
a plugin.
+1 for me
Wayne
On 4/27/08, Eugene Silinov <[EMAIL PROTECTED]> wrote:
> Hi Davi
Hi David,
I started coding Maven Plug-in for ATG Dynamo http://www.atg.com. It
will be something similar to was-maven-plugin, but specifically for
ATG Dynamo. It will be possible to assemble ATG Module defined in POM,
deploy the module, etc. This plug-in is not going to be a wrapper for
Ant tasks.
Just to have a new thread for this.
Dan Tran wrote:
also we should remove all the modules element, i dont see a need for it.
Quite funny, the same discussion happened over at [EMAIL PROTECTED] [0]. Over there,
I was originally in favor of leaving the section in the POM such
that once you wa
+1 for b)
as if we choose a, what will be named the wrapper module containing
the parent and the [EMAIL PROTECTED]
Raphaêl
2008/4/27, Dan Tran <[EMAIL PROTECTED]>:
> +1 for the move and keep same artifactId ie "mojo"
>
>
> -D
>
>
> On Sun, Apr 27, 2008 at 11:16 AM, Benjamin Bentmann
> <[EMAI
+1 for the move and keep same artifactId ie "mojo"
-D
On Sun, Apr 27, 2008 at 11:16 AM, Benjamin Bentmann
<[EMAIL PROTECTED]> wrote:
> Greetings,
>
> My experiences with the release of the Mojo Parent POM 17 make me propose
> to move the parent stuff into a dedicated directory like illustrated
Dan Tran wrote:
may be we should move the root pom to its own folder same level with the
rest.
also we should remove all the modules element, i dont see a need for it.
OK, you were some minutes faster than me ;-), I just tried to propose the
same thing. But I guess having a separate thread f
Greetings,
My experiences with the release of the Mojo Parent POM 17 make me propose to
move the parent stuff into a dedicated directory like illustrated below:
trunk/
mojo/
mojo-parent/ <- Parent POM in here, please
antlr3-maven-plugin/
...
xslt-maven-plugin/
may be we should move the root pom to its own folder same level with the rest.
also we should remove all the modules element, i dont see a need for it.
-D
On Sun, Apr 27, 2008 at 10:45 AM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Benjamin Bentmann wrote:
>
> > Dan Tran wrote:
> >
> > > how d
Benjamin Bentmann wrote:
Dan Tran wrote:
how do you release the pom only?
mvn release:prepare -N ?
I watched Dennis doing a release for the maven-plugins parent POM ;-) He
ran into MRELEASE-123 which proposes to use
mvn release:prepare -N -Darguments=-N
as a workaround and seems to work.
Dan Tran wrote:
how do you release the pom only?
mvn release:prepare -N ?
I watched Dennis doing a release for the maven-plugins parent POM ;-) He ran
into MRELEASE-123 which proposes to use
mvn release:prepare -N -Darguments=-N
as a workaround and seems to work.
Benjamin
--
how do you release the pom only?
mvn release:prepare -N ?
-D
On Sun, Apr 27, 2008 at 10:11 AM, Benjamin Bentmann
<[EMAIL PROTECTED]> wrote:
>
> > now that we have the taglist-maven-plugin:2.2 in the parent POM, there is
> new hope that we can get version 17 of the Mojo parent released ;-)
> >
>
now that we have the taglist-maven-plugin:2.2 in the parent POM, there is
new hope that we can get version 17 of the Mojo parent released ;-)
This vote has passed:
+1: B. Bentmann, F. Giustina, D. J. M. Karlsen, J. Lacoste, D. Lundberg
I will proceed with the release, thanks to everybody who r
+1
fabrizio
On Thu, Apr 24, 2008 at 5:49 PM, Benjamin Bentmann <
[EMAIL PROTECTED]> wrote:
> Hi,
>
> now that we have the taglist-maven-plugin:2.2 in the parent POM, there is
> new hope that we can get version 17 of the Mojo parent released ;-)
>
> The vote is open for 72 hours and will succeed
+1
Benjamin Bentmann wrote:
Hi,
now that we have the taglist-maven-plugin:2.2 in the parent POM, there
is new hope that we can get version 17 of the Mojo parent released ;-)
The vote is open for 72 hours and will succeed by lazy consensus if no
objections are reported but I hope all of the
Benjamin Bentmann skrev:
Hi,
now that we have the taglist-maven-plugin:2.2 in the parent POM, there
is new hope that we can get version 17 of the Mojo parent released ;-)
The vote is open for 72 hours and will succeed by lazy consensus if no
objections are reported but I hope all of the orig
[
http://jira.codehaus.org/browse/MNBMODULE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milos Kleint closed MNBMODULE-29.
-
Resolution: Fixed
Fix Version/s: 2.7
patch applied, with one minor change. instead of explicit
[
http://jira.codehaus.org/browse/MNBMODULE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132777#action_132777
]
Milos Kleint commented on MNBMODULE-29:
---
since the goal was using the netbeans.org originated
19 matches
Mail list logo
