Another remark: there are two issues open in JIRA that seem to address
the same problem that you have encountered: MPSCM-64 and MPSCM-1. Can
you check if those are resolved by your recent changes?
-Lukas
Fabrizio Giustina wrote:
a big +1, but we absolutely need to also release a new version of the
maven-release-plugin:
pom validation in the pom/plugin plugins now enforces uses of a
correct namespace in project.xml but the scm:prepare-release (which
uses code from the release plugin) doesn't work at all with projects
with a declared namespace.
This is now fixed (I encontered this problem in the recent eclipse and
jira plugin releases), so we should release it together with the
plugin plugin
fabrizio
On 12/6/05, Lukas Theussl <[EMAIL PROTECTED]> wrote:
Hi again,
The plugin-plugin is the second plugin I would like to release after the
arifact-plugin. The biggest change in this release is the introduction
of the validate-xml tag which allows to validate arbitrary xml documents
against schemas, dtds, rngs, etc. It will be used by a number of plugins
to validate their respective input documents (xdoc, faq, pdf, pom,
changes,...).
There are two special points I want to emphasize to make sure people are
aware of it and agree:
- The xml validation routines are fully namespace aware, in particular,
poms without a namespace declaration are considered invalid. Note that
this does not in any way influence the functioning of the
plugin/project, only the pom:validate goal will report an invalid pom.
- The plugin:plugin goal requires the artifact plugin v1.7 and therefore
maven 1.1. That means that maven 1.0 users will not be able to install
and deploy plugins from sources (only plugin:download will work for them).
The future documentation is here:
http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/plugin/
I give it the usual 72 hours and my +1.
-Lukas
===============================================================================
Changes in this version include:
New Features:
o Allow plugin-test directory to be changed. Fixes MPPLUGIN-33.
o Resolve project.xml inheritance when installing plugin. plugin:plugin
goal
now requires at least maven 1.1 and maven-artifact-plugin 1.7. Fixes
MPPLUGIN-3.
o new plugin:validate-xml tag to validate xml documents against a schema.
o new assert:assertPluginAvailable tag to check if a minimal release of a
plugin is present.
Fixed bugs:
o NTLM Proxy Problem. Fixes MPPLUGIN-25. Thanks to Jamie McCrindle, Barrie
Treloar.
o plugin:download didn't redownload SNAPSHOT plugins. Fixes MPPLUGIN-26.
Changes:
o Update dependencies to match ones in maven 1.1 core and to unify them
between plugins. The following dependencies are updated :
commons-jelly-tags-xml v1.0 -> v1.1 commons-logging v1.0.3 -> v1.0.4
jdom v b10 -> v1.0 xercesImpl v 2.4.0 -> v2.6.2 xml-apis v 1.0.b2
-> xmlParserAPIs v2.6.2 Fixes MAVEN-1712.
===============================================================================
To automatically install the plugin, type the following on a single line:
maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/
-DgroupId=maven
-DartifactId=maven-plugin-plugin
-Dversion=1.7-SNAPSHOT
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
______________________________________________________________________________
Lukas Theussl
TRIUMF email: [EMAIL PROTECTED]
4004 Wesbrook Mall tel.: + 1 604 222 1047 ext. 6446
Vancouver, British Columbia http://www.triumf.ca/people/theussl/
Canada V6T 2A3
______________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
