The following issue has been updated:
Updater: Shinobu Kawai (mailto:[EMAIL PROTECTED])
Date: Mon, 25 Oct 2004 9:33 PM
Comment:
Okay, here's the patch to move the Velocity log cleaning to the xdoc plugin. As for
the maven.clean.include extension, I think a new issue should be file
aheritier2004/10/25 15:45:53
Modified:xdoc plugin.jelly plugin.properties
xdoc/src/plugin-test/test02 maven.xml
xdoc/xdocs changes.xml properties.xml
Added: xdoc/src/plugin-test/test02 project.properties
xdoc/src/plugin-test/test02
Message:
The following issue has been closed.
Resolver: Arnaud HERITIER
Date: Mon, 25 Oct 2004 6:45 PM
A new property is added : maven.xdoc.xml.copy
A comma separated list of patterns to specify xml files to copy from ${maven.docs.src}
to ${maven.docs.dest} without to perform a tr
IF you have a look at jar:deploy, that's exactly what is there :)
Cheers,
Brett
Ryan Schutt wrote:
While searching the maven plugins for a goal to automatically upload a created
artifact to a repository, I ran across the maven artifact plugin. This plugin
seems to have the necessary functionality
While searching the maven plugins for a goal to automatically upload a created
artifact to a repository, I ran across the maven artifact plugin. This plugin
seems to have the necessary functionality needed for automatically uploading
artifacts, and indeed, I can accomplish what I need if I add thi
All the other plugin releases except eclipse are done.
So after the outstanding JIRA issues on the roadmap. Patches welcome :)
Cheers,
Brett
Arnaud HERITIER wrote:
+1 for me.
It's better to turn off this feature.
Brett, do you have an idea when you'll be able to produce the 1.0.1 release ?
Arnaud
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-55
Here is an overview of the issue:
-
Ke
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-54
Here is an overview of the issue:
-
Ke
+1 for me.
It's better to turn off this feature.
Brett, do you have an idea when you'll be able to produce the 1.0.1 release ?
Arnaud
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1 for Brett's proposal
On Mon, 2004-10-25 at 08:32, Brett Porter wrote:
> OTOH, you could do as below and default to off - so the new feature is
> there if needed, but still compatible until a better solution can be found.
>
> What do you think?
-
Yeah, I think it is really important that users can download a new
version and expect things not to break, especially in a "bugfix"
release. We don't exactly have a great track record on that count :)
If it's a breaker, I'd say we leave it out of 1.0.1 - it can be easily
downloaded separately.
MPECLIPSE-53 does need fixing, otherwise we won't be backwards compatible.
If we can wait a day or so, I'll see if I can (or anyone else) can think of
something smart. Otherwise I'll add a switch to turn on and off including
resources, with the default being I guess, on. That will break some
proj
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Mon, 25 Oct 2004 5:18 AM
Body:
Brett does have a valid point. And his point is why I want to supply a generic
maven.clean.includes patternset, versus a hardcoded velocity.log.1 file.
I agree, th
The following comment has been added to this issue:
Author: Shinobu Kawai
Created: Mon, 25 Oct 2004 5:12 AM
Body:
Don't worry, Velocity will only roll one file, so the patch is sufficient in
Velocity's case. B)
I read Brett's comment in http://jira.codehaus.org/browse/MPCLEAN-2,
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Mon, 25 Oct 2004 4:51 AM
Body:
While your patch would work for velocity.log.1, it won't work for velocity.log.2 or
name your extra artifact.
If you are interested, look at how other plugins imp
15 matches
Mail list logo
