You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by nadias <na...@cisco.com> on 2008/01/26 01:40:32 UTC
update/creation of maven-metadata.xml file
How can I force the maven-metadata.xml file to be updated (or created) when
deploying plugins? I have an instance where the maven-metadata.xml is not
being updated or created when deploying plugins - it seems that deploying
plugins may be different from deploying artifacts.
Any help is appreciated.
Thanks.
--
View this message in context: http://www.nabble.com/update-creation-of-maven-metadata.xml-file-tp15100044s177p15100044.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: update/creation of maven-metadata.xml file
Posted by Jeff MAURY <je...@jeffmaury.com>.
If you deploy a new version, it should be updated as it stores the list of
versions. It will be also updated if you specify the updateReleaseInfo flag
to true. Take care, this flag means the version you are deploying is the
default version of your artifact.
Jeff
On Jan 26, 2008 1:40 AM, nadias <na...@cisco.com> wrote:
>
> How can I force the maven-metadata.xml file to be updated (or created)
> when
> deploying plugins? I have an instance where the maven-metadata.xml is not
> being updated or created when deploying plugins - it seems that deploying
> plugins may be different from deploying artifacts.
>
> Any help is appreciated.
>
> Thanks.
> --
> View this message in context:
> http://www.nabble.com/update-creation-of-maven-metadata.xml-file-tp15100044s177p15100044.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent
Miossec (2006)
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
Re: update/creation of maven-metadata.xml file
Posted by Tom Huybrechts <to...@gmail.com>.
On Jan 29, 2008 5:52 PM, Wendy Smoak <ws...@gmail.com> wrote:
> On Jan 29, 2008 9:44 AM, Tom Huybrechts <to...@gmail.com> wrote:
>
> > If you specify an explicit version in your POM, I would think that Maven
> > always finds it ?
>
> Probably, (and that's definitely a best practice,) but not everything
> uses a pom.
>
> 'mvn archetype:create' comes to mind, for example... as well as 'mvn
> deploy:deploy-file' itself.
>
It's ugly, but mvn
org.apache.maven.plugins:maven-archetype-plugin:<version>:create
would work here too.
Tom
>
> Some corporate environments require approvals and manual deployment of
> every artifact into their internal repos to tightly control what is
> available. I don't see a way to deploy a plugin with the correct
> metadata until MDEPLOY-52 is fixed.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: update/creation of maven-metadata.xml file
Posted by Wendy Smoak <ws...@gmail.com>.
On Jan 29, 2008 9:44 AM, Tom Huybrechts <to...@gmail.com> wrote:
> If you specify an explicit version in your POM, I would think that Maven
> always finds it ?
Probably, (and that's definitely a best practice,) but not everything
uses a pom.
'mvn archetype:create' comes to mind, for example... as well as 'mvn
deploy:deploy-file' itself.
Some corporate environments require approvals and manual deployment of
every artifact into their internal repos to tightly control what is
available. I don't see a way to deploy a plugin with the correct
metadata until MDEPLOY-52 is fixed.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: update/creation of maven-metadata.xml file
Posted by nadias <na...@cisco.com>.
My next question would then be: if we specify the exact version to use in the
pom and deploy a plugin using deploy-file then even though the
maven-metadata.xml file hasn't been updated/created, can I rely on the build
run successfully, using the correct plugin?
TomHuybrechts wrote:
>
> On Jan 29, 2008 5:32 PM, Wendy Smoak <ws...@gmail.com> wrote:
>
>> On Jan 26, 2008 4:20 PM, nadias <na...@cisco.com> wrote:
>> >
>> > Will this work deploy-file or just deploy? I am working with
>> deploy-file but
>> > it is not updating the metadata even if I specify this parameter.
>>
>> The updateReleaseInfo parameter is not listed for the deploy-file goal.
>> *
>> http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
>>
>> Vote for it! http://jira.codehaus.org/browse/MDEPLOY-52 :)
>>
>> This seems to make it impossible to deploy a working plugin with
>> deploy:deploy-file. The 'latest' and 'release' elements seem to be
>> required, or Maven complains that it can't find the plugin at all. :(
>>
>
> If you specify an explicit version in your POM, I would think that Maven
> always finds it ?
>
> Tom
>
>
>>
>> --
>> Wendy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/update-creation-of-maven-metadata.xml-file-tp15100044s177p15172352.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: update/creation of maven-metadata.xml file
Posted by Tom Huybrechts <to...@gmail.com>.
On Jan 29, 2008 5:32 PM, Wendy Smoak <ws...@gmail.com> wrote:
> On Jan 26, 2008 4:20 PM, nadias <na...@cisco.com> wrote:
> >
> > Will this work deploy-file or just deploy? I am working with
> deploy-file but
> > it is not updating the metadata even if I specify this parameter.
>
> The updateReleaseInfo parameter is not listed for the deploy-file goal.
> *
> http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
>
> Vote for it! http://jira.codehaus.org/browse/MDEPLOY-52 :)
>
> This seems to make it impossible to deploy a working plugin with
> deploy:deploy-file. The 'latest' and 'release' elements seem to be
> required, or Maven complains that it can't find the plugin at all. :(
>
If you specify an explicit version in your POM, I would think that Maven
always finds it ?
Tom
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: update/creation of maven-metadata.xml file
Posted by nadias <na...@cisco.com>.
Thanks. I've voted for it and asked for a workaround.
Wendy Smoak-3 wrote:
>
> On Jan 26, 2008 4:20 PM, nadias <na...@cisco.com> wrote:
>>
>> Will this work deploy-file or just deploy? I am working with deploy-file
>> but
>> it is not updating the metadata even if I specify this parameter.
>
> The updateReleaseInfo parameter is not listed for the deploy-file goal.
> *
> http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
>
> Vote for it! http://jira.codehaus.org/browse/MDEPLOY-52 :)
>
> This seems to make it impossible to deploy a working plugin with
> deploy:deploy-file. The 'latest' and 'release' elements seem to be
> required, or Maven complains that it can't find the plugin at all. :(
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/update-creation-of-maven-metadata.xml-file-tp15100044s177p15172451.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: update/creation of maven-metadata.xml file
Posted by Wendy Smoak <ws...@gmail.com>.
On Jan 26, 2008 4:20 PM, nadias <na...@cisco.com> wrote:
>
> Will this work deploy-file or just deploy? I am working with deploy-file but
> it is not updating the metadata even if I specify this parameter.
The updateReleaseInfo parameter is not listed for the deploy-file goal.
* http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
Vote for it! http://jira.codehaus.org/browse/MDEPLOY-52 :)
This seems to make it impossible to deploy a working plugin with
deploy:deploy-file. The 'latest' and 'release' elements seem to be
required, or Maven complains that it can't find the plugin at all. :(
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: update/creation of maven-metadata.xml file
Posted by nadias <na...@cisco.com>.
Will this work deploy-file or just deploy? I am working with deploy-file but
it is not updating the metadata even if I specify this parameter.
Thanks!
TomHuybrechts wrote:
>
> -DupdateReleaseInfo=true
>
>
> On Jan 26, 2008 1:40 AM, nadias <na...@cisco.com> wrote:
>
>>
>> How can I force the maven-metadata.xml file to be updated (or created)
>> when
>> deploying plugins? I have an instance where the maven-metadata.xml is
>> not
>> being updated or created when deploying plugins - it seems that deploying
>> plugins may be different from deploying artifacts.
>>
>> Any help is appreciated.
>>
>> Thanks.
>> --
>> View this message in context:
>> http://www.nabble.com/update-creation-of-maven-metadata.xml-file-tp15100044s177p15100044.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/update-creation-of-maven-metadata.xml-file-tp15100044s177p15113940.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: update/creation of maven-metadata.xml file
Posted by Tom Huybrechts <to...@gmail.com>.
-DupdateReleaseInfo=true
On Jan 26, 2008 1:40 AM, nadias <na...@cisco.com> wrote:
>
> How can I force the maven-metadata.xml file to be updated (or created)
> when
> deploying plugins? I have an instance where the maven-metadata.xml is not
> being updated or created when deploying plugins - it seems that deploying
> plugins may be different from deploying artifacts.
>
> Any help is appreciated.
>
> Thanks.
> --
> View this message in context:
> http://www.nabble.com/update-creation-of-maven-metadata.xml-file-tp15100044s177p15100044.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>