You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Viv Kapadekar <vi...@peoplepowerco.com> on 2010/03/18 20:48:16 UTC
how to download historical builds
Hi All,
I am newbie to Continuum and have set up standalone Continuum and it
works great with my Maven2 project. I can check historical builds, its
results, date etc. I can download the latest build artifacts. But how
do I download the historical build artifacts (wars, jars )?
Thanks
Viv Kapadekar
vivek@peoplepowerco.com
Re: how to download historical builds
Posted by Brett Porter <br...@apache.org>.
It's normal to copy to the local repository (this happens at the install step), but this should always be under the single identifier "SNAPSHOT", rather than keeping a copy of each timestamped artifact. I'm not sure why you'd be experiencing that.
On 21/03/2010, at 9:57 AM, Viv Kapadekar wrote:
> Hi Brett,
>
> So, I see the builds now getting copied to the repository specified in distributionManagement and it keeps a copy of all previous builds too, which is great. But it seems to also copy it to my own local repository ( under .m2 ). Thats not what I expected. I thought my local repository would just have the latest artifact and not get piled up with builds everytime I do a mvn deploy. Am I missing something?
>
> Thanks
>
> --Viv
> On Mar 18, 2010, at 5:10 PM, Brett Porter wrote:
>
>> If you're using the configuration as stated below, each build should use a timestamp and build number. IT would only overwrite if for some reason you added <uniqueVersion>false</uniqueVersion> to the repository element.
>>
>> What does your repository look like?
>>
>> On 19/03/2010, at 10:45 AM, Viv Kapadekar wrote:
>>
>>> Thanks Brett. Currently I had it as 1.0-SNAPSHOT in the parent pom but not in module pom.xml. I made the change and now its deploying. But every time I run mvn deploy, it overwrites the previous snapshot build. How can I get a historical builds? I have to generate version numbers dynamically?
>>>
>>> Thanks
>>>
>>> --Viv
>>> On Mar 18, 2010, at 4:13 PM, Brett Porter wrote:
>>>
>>>>
>>>> On 19/03/2010, at 9:39 AM, Viv Kapadekar wrote:
>>>>
>>>>> Thanks for your prompt response. I have set up distribtionManagement in pom.xml like this:
>>>>>
>>>>>
>>>>> <distributionManagement>
>>>>> <snapshotRepository>
>>>>> <id>internal.repo</id>
>>>>> <name>My local Internal Repository of builds</name>
>>>>> <url>file:///Users/vivekkapadekar/workspace/deploy/</url>
>>>>> </snapshotRepository>
>>>>> </distributionManagement>
>>>>
>>>> Note that at some point you'll need <repository> for your release as well (even if it is the same). If the <version> being deployed does not end in -SNAPSHOT this would be the problem.
>>>>
>>>> Otherwise, what version of Maven are you using?
>>>>
>>>> - Brett
>>>>
>>>> --
>>>> Brett Porter
>>>> brett@apache.org
>>>> http://brettporter.wordpress.com/
>>>>
>>>>
>>>>
>>>>
>>>
>>> Viv Kapadekar
>>> vivek@peoplepowerco.com
>>>
>>>
>>>
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>>
>>
>>
>>
>
> Viv Kapadekar
> vivek@peoplepowerco.com
>
>
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: how to download historical builds
Posted by Viv Kapadekar <vi...@peoplepowerco.com>.
Hi Brett,
So, I see the builds now getting copied to the repository specified in
distributionManagement and it keeps a copy of all previous builds too,
which is great. But it seems to also copy it to my own local
repository ( under .m2 ). Thats not what I expected. I thought my
local repository would just have the latest artifact and not get
piled up with builds everytime I do a mvn deploy. Am I missing
something?
Thanks
--Viv
On Mar 18, 2010, at 5:10 PM, Brett Porter wrote:
> If you're using the configuration as stated below, each build should
> use a timestamp and build number. IT would only overwrite if for
> some reason you added <uniqueVersion>false</uniqueVersion> to the
> repository element.
>
> What does your repository look like?
>
> On 19/03/2010, at 10:45 AM, Viv Kapadekar wrote:
>
>> Thanks Brett. Currently I had it as 1.0-SNAPSHOT in the parent pom
>> but not in module pom.xml. I made the change and now its
>> deploying. But every time I run mvn deploy, it overwrites the
>> previous snapshot build. How can I get a historical builds? I have
>> to generate version numbers dynamically?
>>
>> Thanks
>>
>> --Viv
>> On Mar 18, 2010, at 4:13 PM, Brett Porter wrote:
>>
>>>
>>> On 19/03/2010, at 9:39 AM, Viv Kapadekar wrote:
>>>
>>>> Thanks for your prompt response. I have set up
>>>> distribtionManagement in pom.xml like this:
>>>>
>>>>
>>>> <distributionManagement>
>>>> <snapshotRepository>
>>>> <id>internal.repo</id>
>>>> <name>My local Internal Repository of builds</name>
>>>> <url>file:///Users/vivekkapadekar/workspace/deploy/</url>
>>>> </snapshotRepository>
>>>> </distributionManagement>
>>>
>>> Note that at some point you'll need <repository> for your release
>>> as well (even if it is the same). If the <version> being deployed
>>> does not end in -SNAPSHOT this would be the problem.
>>>
>>> Otherwise, what version of Maven are you using?
>>>
>>> - Brett
>>>
>>> --
>>> Brett Porter
>>> brett@apache.org
>>> http://brettporter.wordpress.com/
>>>
>>>
>>>
>>>
>>
>> Viv Kapadekar
>> vivek@peoplepowerco.com
>>
>>
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
>
>
>
>
Viv Kapadekar
vivek@peoplepowerco.com
Re: how to download historical builds
Posted by Viv Kapadekar <vi...@peoplepowerco.com>.
My bad, I was looking at wrong repository. I earlier had repository
url as: file://Users/vivekkapadekar/workspace/deploy
I changed it to: file:///Users/vivekkapadekar/workspace/deploy and
now its where I want.
Works like a charm.
Thanks a lot
--Viv
On Mar 18, 2010, at 5:10 PM, Brett Porter wrote:
> If you're using the configuration as stated below, each build should
> use a timestamp and build number. IT would only overwrite if for
> some reason you added <uniqueVersion>false</uniqueVersion> to the
> repository element.
>
> What does your repository look like?
>
> On 19/03/2010, at 10:45 AM, Viv Kapadekar wrote:
>
>> Thanks Brett. Currently I had it as 1.0-SNAPSHOT in the parent pom
>> but not in module pom.xml. I made the change and now its
>> deploying. But every time I run mvn deploy, it overwrites the
>> previous snapshot build. How can I get a historical builds? I have
>> to generate version numbers dynamically?
>>
>> Thanks
>>
>> --Viv
>> On Mar 18, 2010, at 4:13 PM, Brett Porter wrote:
>>
>>>
>>> On 19/03/2010, at 9:39 AM, Viv Kapadekar wrote:
>>>
>>>> Thanks for your prompt response. I have set up
>>>> distribtionManagement in pom.xml like this:
>>>>
>>>>
>>>> <distributionManagement>
>>>> <snapshotRepository>
>>>> <id>internal.repo</id>
>>>> <name>My local Internal Repository of builds</name>
>>>> <url>file:///Users/vivekkapadekar/workspace/deploy/</url>
>>>> </snapshotRepository>
>>>> </distributionManagement>
>>>
>>> Note that at some point you'll need <repository> for your release
>>> as well (even if it is the same). If the <version> being deployed
>>> does not end in -SNAPSHOT this would be the problem.
>>>
>>> Otherwise, what version of Maven are you using?
>>>
>>> - Brett
>>>
>>> --
>>> Brett Porter
>>> brett@apache.org
>>> http://brettporter.wordpress.com/
>>>
>>>
>>>
>>>
>>
>> Viv Kapadekar
>> vivek@peoplepowerco.com
>>
>>
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
>
>
>
>
Viv Kapadekar
vivek@peoplepowerco.com
Re: how to download historical builds
Posted by Brett Porter <br...@apache.org>.
If you're using the configuration as stated below, each build should use a timestamp and build number. IT would only overwrite if for some reason you added <uniqueVersion>false</uniqueVersion> to the repository element.
What does your repository look like?
On 19/03/2010, at 10:45 AM, Viv Kapadekar wrote:
> Thanks Brett. Currently I had it as 1.0-SNAPSHOT in the parent pom but not in module pom.xml. I made the change and now its deploying. But every time I run mvn deploy, it overwrites the previous snapshot build. How can I get a historical builds? I have to generate version numbers dynamically?
>
> Thanks
>
> --Viv
> On Mar 18, 2010, at 4:13 PM, Brett Porter wrote:
>
>>
>> On 19/03/2010, at 9:39 AM, Viv Kapadekar wrote:
>>
>>> Thanks for your prompt response. I have set up distribtionManagement in pom.xml like this:
>>>
>>>
>>> <distributionManagement>
>>> <snapshotRepository>
>>> <id>internal.repo</id>
>>> <name>My local Internal Repository of builds</name>
>>> <url>file:///Users/vivekkapadekar/workspace/deploy/</url>
>>> </snapshotRepository>
>>> </distributionManagement>
>>
>> Note that at some point you'll need <repository> for your release as well (even if it is the same). If the <version> being deployed does not end in -SNAPSHOT this would be the problem.
>>
>> Otherwise, what version of Maven are you using?
>>
>> - Brett
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>>
>>
>>
>>
>
> Viv Kapadekar
> vivek@peoplepowerco.com
>
>
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: how to download historical builds
Posted by Viv Kapadekar <vi...@peoplepowerco.com>.
Thanks Brett. Currently I had it as 1.0-SNAPSHOT in the parent pom
but not in module pom.xml. I made the change and now its deploying.
But every time I run mvn deploy, it overwrites the previous snapshot
build. How can I get a historical builds? I have to generate version
numbers dynamically?
Thanks
--Viv
On Mar 18, 2010, at 4:13 PM, Brett Porter wrote:
>
> On 19/03/2010, at 9:39 AM, Viv Kapadekar wrote:
>
>> Thanks for your prompt response. I have set up
>> distribtionManagement in pom.xml like this:
>>
>>
>> <distributionManagement>
>> <snapshotRepository>
>> <id>internal.repo</id>
>> <name>My local Internal Repository of builds</name>
>> <url>file:///Users/vivekkapadekar/workspace/deploy/</url>
>> </snapshotRepository>
>> </distributionManagement>
>
> Note that at some point you'll need <repository> for your release as
> well (even if it is the same). If the <version> being deployed does
> not end in -SNAPSHOT this would be the problem.
>
> Otherwise, what version of Maven are you using?
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
>
>
>
>
Viv Kapadekar
vivek@peoplepowerco.com
Re: how to download historical builds
Posted by Brett Porter <br...@apache.org>.
On 19/03/2010, at 9:39 AM, Viv Kapadekar wrote:
> Thanks for your prompt response. I have set up distribtionManagement in pom.xml like this:
>
>
> <distributionManagement>
> <snapshotRepository>
> <id>internal.repo</id>
> <name>My local Internal Repository of builds</name>
> <url>file:///Users/vivekkapadekar/workspace/deploy/</url>
> </snapshotRepository>
> </distributionManagement>
Note that at some point you'll need <repository> for your release as well (even if it is the same). If the <version> being deployed does not end in -SNAPSHOT this would be the problem.
Otherwise, what version of Maven are you using?
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: how to download historical builds
Posted by Viv Kapadekar <vi...@peoplepowerco.com>.
Thanks for your prompt response. I have set up distribtionManagement
in pom.xml like this:
<distributionManagement>
<snapshotRepository>
<id>internal.repo</id>
<name>My local Internal Repository of builds</name>
<url>file:///Users/vivekkapadekar/workspace/deploy/</url>
</snapshotRepository>
</distributionManagement>
But I get this error when I run mvn deploy
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-deploy-plugin:2.4
check that the following section of the pom.xml is present and correct:
<distributionManagement>
<!-- use the following if you're not using a snapshot version. -->
<repository>
<id>repo</id>
<name>Repository Name</name>
<url>scp://host/path/to/repo</url>
</repository>
<!-- use the following if you ARE using a snapshot version. -->
<snapshotRepository>
<id>repo</id>
<name>Repository Name</name>
<url>scp://host/path/to/repo</url>
</snapshotRepository>
</distributionManagement>
Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository'
cannot be instantiated
On Mar 18, 2010, at 1:06 PM, Wendy Smoak wrote:
> On Thu, Mar 18, 2010 at 3:48 PM, Viv Kapadekar <vivek@peoplepowerco.com
> > wrote:
>> I am newbie to Continuum and have set up standalone Continuum and
>> it works
>> great with my Maven2 project. I can check historical builds, its
>> results,
>> date etc. I can download the latest build artifacts. But how do I
>> download
>> the historical build artifacts (wars, jars )?
>
> Continuum does not store old build artifacts. Since you are using
> Maven 2, you'll probably want to set up an artifact repository such as
> Apache Archiva to store these. (To get started, change the build
> definition to 'clean deploy' and configure distributionManagement in
> your pom.)
>
> You can also try configuring the 'deployment repository' directory if
> it still exists. I never used it, but based on the log messages it
> always looked like Continuum was trying to deploy to that directory
> even if you didn't have 'deploy' in the maven command.
>
> --
> Wendy
Viv Kapadekar
vivek@peoplepowerco.com
Re: how to download historical builds
Posted by Wendy Smoak <ws...@gmail.com>.
On Thu, Mar 18, 2010 at 3:48 PM, Viv Kapadekar <vi...@peoplepowerco.com> wrote:
> I am newbie to Continuum and have set up standalone Continuum and it works
> great with my Maven2 project. I can check historical builds, its results,
> date etc. I can download the latest build artifacts. But how do I download
> the historical build artifacts (wars, jars )?
Continuum does not store old build artifacts. Since you are using
Maven 2, you'll probably want to set up an artifact repository such as
Apache Archiva to store these. (To get started, change the build
definition to 'clean deploy' and configure distributionManagement in
your pom.)
You can also try configuring the 'deployment repository' directory if
it still exists. I never used it, but based on the log messages it
always looked like Continuum was trying to deploy to that directory
even if you didn't have 'deploy' in the maven command.
--
Wendy