You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Vincent Siveton <vi...@gmail.com> on 2008/12/14 15:28:51 UTC
Maven XSDs
Hi,
MNG-2636 points that settings-1.0.0.xsd (and also profiles-1.0.0.xsd)
uses the same namespace than Maven. This issue was similar to
MASSEMBLY-296.
So, I fixed the modello files to include new namespaces for settings
and profiles:
http://maven.apache.org/PROFILES/1.0.0
http://maven.apache.org/SETTINGS/1.0.0
I redeployed these files to http://maven.apache.org/xsd/ (need to
sync) and fixed documentation.
Also, I notified that calling mvn site generates several XSD which are
not deployed:
lifecycle-mappings-1.0.0.xsd
paramdoc-1.0.0.xsd
plugin-registry-1.0.0.xsd
repository-metadata-1.0.0.xsd
maven-toolchains-1.0.0.xsd
Is it intentional that these files are not deployed? If yes, why do we
need to generate them?
Cheers,
Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven XSDs
Posted by Barrie Treloar <ba...@gmail.com>.
On Mon, Dec 15, 2008 at 10:33 PM, Vincent Siveton
<vi...@gmail.com> wrote:
>> So am I right in that the namespace for assembly xml files should be
>>
>> <settings xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
>> http://maven.apache.org/xsd/assembly-1.1.0.xsd">
>>
>> If this is right, I can update the examples in the documentation to
>> include namespaces.
>
> Feel free to do it.
Well, I found this workspace lying around at work that I had yet to commit.
I've done that now :)
There was also an outstanding JIRA
http://jira.codehaus.org/browse/MASSEMBLY-380 which only talked about
the documentation side, so I have closed that as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven XSDs
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Barrie,
2008/12/14 Barrie Treloar <ba...@gmail.com>:
> After reading the recent post for "New namespaces for Maven Settings
> and Profiles XSD" I went to update my assembly xml files.
>
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
> doesn't list what version it uses and http://maven.apache.org/xsd/
> lists a choice of two:
> assembly-1.0.0.xsd
> assembly-1.1.0.xsd
Its main page specifies which version you need to use:
http://maven.apache.org/plugins/maven-assembly-plugin/index.html
Section Assembly Descriptor Schemas (XSD)
It speaks of SNAPSHOT so the documentation needs to be updated.
> (MASSEMBLY-296 also lists 1.0.0 as being obsolete)
>
> Having a look at
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin
> and src/main/mdo/descriptor.mdo it uses:
>
> <model xsd.namespace="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"
> xsd.target-namespace="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0">
>
>
> So am I right in that the namespace for assembly xml files should be
>
> <settings xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd">
>
> If this is right, I can update the examples in the documentation to
> include namespaces.
Feel free to do it.
Cheers,
Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven XSDs
Posted by Barrie Treloar <ba...@gmail.com>.
> <settings xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd">
Err... cut-n-paste error: tag should be assemly not settings
<assembly xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
http://maven.apache.org/xsd/assembly-1.1.0.xsd">
(this appears to work in eclipse and provide context help)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven XSDs
Posted by Barrie Treloar <ba...@gmail.com>.
On Mon, Dec 15, 2008 at 12:58 AM, Vincent Siveton
<vi...@gmail.com> wrote:
> Hi,
>
> MNG-2636 points that settings-1.0.0.xsd (and also profiles-1.0.0.xsd)
> uses the same namespace than Maven. This issue was similar to
> MASSEMBLY-296.
> So, I fixed the modello files to include new namespaces for settings
> and profiles:
> http://maven.apache.org/PROFILES/1.0.0
> http://maven.apache.org/SETTINGS/1.0.0
After reading the recent post for "New namespaces for Maven Settings
and Profiles XSD" I went to update my assembly xml files.
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
doesn't list what version it uses and http://maven.apache.org/xsd/
lists a choice of two:
assembly-1.0.0.xsd
assembly-1.1.0.xsd
(MASSEMBLY-296 also lists 1.0.0 as being obsolete)
Having a look at
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin
and src/main/mdo/descriptor.mdo it uses:
<model xsd.namespace="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"
xsd.target-namespace="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0">
So am I right in that the namespace for assembly xml files should be
<settings xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
http://maven.apache.org/xsd/assembly-1.1.0.xsd">
If this is right, I can update the examples in the documentation to
include namespaces.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven XSDs
Posted by Vincent Siveton <vi...@gmail.com>.
done
Vincent
2008/12/14 Olivier Lamy <ol...@apache.org>:
> Hi Vincent,
> Is it possible to send an email to users ml just for information ?
> Due to this change (new schema [1] with namespace change) if I open my
> settings.xml with a xml editor which apply validation it breaks due to
> the namespace change.
>
> Thanks,
> --
> Olivier
>
> [1] http://maven.apache.org/xsd/settings-1.0.0.xsd
>
> 2008/12/14 Vincent Siveton <vi...@gmail.com>:
>> Hi,
>>
>> MNG-2636 points that settings-1.0.0.xsd (and also profiles-1.0.0.xsd)
>> uses the same namespace than Maven. This issue was similar to
>> MASSEMBLY-296.
>> So, I fixed the modello files to include new namespaces for settings
>> and profiles:
>> http://maven.apache.org/PROFILES/1.0.0
>> http://maven.apache.org/SETTINGS/1.0.0
>>
>> I redeployed these files to http://maven.apache.org/xsd/ (need to
>> sync) and fixed documentation.
>>
>> Also, I notified that calling mvn site generates several XSD which are
>> not deployed:
>> lifecycle-mappings-1.0.0.xsd
>> paramdoc-1.0.0.xsd
>> plugin-registry-1.0.0.xsd
>> repository-metadata-1.0.0.xsd
>> maven-toolchains-1.0.0.xsd
>>
>> Is it intentional that these files are not deployed? If yes, why do we
>> need to generate them?
>>
>> Cheers,
>>
>> Vincent
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven XSDs
Posted by Olivier Lamy <ol...@apache.org>.
Hi Vincent,
Is it possible to send an email to users ml just for information ?
Due to this change (new schema [1] with namespace change) if I open my
settings.xml with a xml editor which apply validation it breaks due to
the namespace change.
Thanks,
--
Olivier
[1] http://maven.apache.org/xsd/settings-1.0.0.xsd
2008/12/14 Vincent Siveton <vi...@gmail.com>:
> Hi,
>
> MNG-2636 points that settings-1.0.0.xsd (and also profiles-1.0.0.xsd)
> uses the same namespace than Maven. This issue was similar to
> MASSEMBLY-296.
> So, I fixed the modello files to include new namespaces for settings
> and profiles:
> http://maven.apache.org/PROFILES/1.0.0
> http://maven.apache.org/SETTINGS/1.0.0
>
> I redeployed these files to http://maven.apache.org/xsd/ (need to
> sync) and fixed documentation.
>
> Also, I notified that calling mvn site generates several XSD which are
> not deployed:
> lifecycle-mappings-1.0.0.xsd
> paramdoc-1.0.0.xsd
> plugin-registry-1.0.0.xsd
> repository-metadata-1.0.0.xsd
> maven-toolchains-1.0.0.xsd
>
> Is it intentional that these files are not deployed? If yes, why do we
> need to generate them?
>
> Cheers,
>
> Vincent
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven XSDs
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Wendy,
2008/12/14 Wendy Smoak <ws...@gmail.com>:
> On Sun, Dec 14, 2008 at 7:28 AM, Vincent Siveton
> <vi...@gmail.com> wrote:
>
>> Is it intentional that these files are not deployed? If yes, why do we
>> need to generate them?
>
> They're probably not being deployed because it requires a manual step.
>
> For the Struts site, we have some antrun config [1] that grabs the
> dtds from svn and puts them in the right place for site deployment.
> Since the Maven schemas are generated in different projects and need
> to be published in the top level site, we'd have to do something else.
I agree with you for the main Maven XSD (POM, settings profiles) but I
am wondering if we need to deploy all others XSD?
>
> What about publishing them in the various projects they belong to, and
> adding symlinks in maven.apache.org/xsd?
Sounds good.
Cheers,
Vincent
>
> [1] http://svn.apache.org/repos/asf/struts/site/pom.xml
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven XSDs
Posted by Wendy Smoak <ws...@gmail.com>.
On Sun, Dec 14, 2008 at 7:28 AM, Vincent Siveton
<vi...@gmail.com> wrote:
> Is it intentional that these files are not deployed? If yes, why do we
> need to generate them?
They're probably not being deployed because it requires a manual step.
For the Struts site, we have some antrun config [1] that grabs the
dtds from svn and puts them in the right place for site deployment.
Since the Maven schemas are generated in different projects and need
to be published in the top level site, we'd have to do something else.
What about publishing them in the various projects they belong to, and
adding symlinks in maven.apache.org/xsd?
[1] http://svn.apache.org/repos/asf/struts/site/pom.xml
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org