You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dan Fabulich <da...@fabulich.com> on 2008/08/27 21:02:54 UTC
Using a downloader to test plugin releases
I've always found it to be a hassle to test plugins that don't need to be
wired up in POM files, e.g. the archetype, dependency, scm plugins. I
find that to test them I have to create a dummy POM file with a
<pluginRepositories> section, as described in our guide to testing staged
releases.
http://maven.apache.org/guides/development/guide-testing-releases.html
I thought it would be cool to have a downloader plugin that let you do
this:
mvn downloader:get
-Dartifact=org.apache.maven.plugins:maven-scm-plugin:1.1
-DrepoUrl=http://people.apache.org/~olamy/staging-repo
That would retrieve the plugin into your local repository, so you could
immediately start using it.
mvn org.apache.maven.plugins:maven-scm-plugin:1.1:checkin -Dmessage=foo
I've created a prototype downloader plugin and checked it into the
sandbox; I used it to test the Maven SCM 1.1 release. It was pretty nice.
Does this seem like something worth releasing and documenting as part of
our release testing guide?
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Using a downloader to test plugin releases
Posted by Jason van Zyl <ja...@maven.org>.
The only benefit of the profile is that the plugin is downloaded and
installed as Maven does normally. Updating metadata accordingly and
all that jazz.
On 27-Aug-08, at 1:14 PM, Dan Fabulich wrote:
> Jason van Zyl wrote:
>
>> The method that we've pushed in a couple releases is a simple
>> profile which lists the staging repository where a test plugin has
>> been deployed. The profile can be generated with the release and
>> it's a separate file, so you just erase it when you're done with
>> it. Think the profile might be a bit simpler and we could certainly
>> generate the snippet from the staging plugin.
>
> That could be cool, but frankly, even if a file like that were
> available, I'd still prefer to just use the downloader. There's no
> file to deal with or clean up at all in that case; just copy/paste.
>
> -Dan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Using a downloader to test plugin releases
Posted by Dan Fabulich <da...@fabulich.com>.
Jason van Zyl wrote:
> The method that we've pushed in a couple releases is a simple profile which
> lists the staging repository where a test plugin has been deployed. The
> profile can be generated with the release and it's a separate file, so you
> just erase it when you're done with it. Think the profile might be a bit
> simpler and we could certainly generate the snippet from the staging plugin.
That could be cool, but frankly, even if a file like that were available,
I'd still prefer to just use the downloader. There's no file to deal with
or clean up at all in that case; just copy/paste.
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Using a downloader to test plugin releases
Posted by Jason van Zyl <ja...@maven.org>.
The method that we've pushed in a couple releases is a simple profile
which lists the staging repository where a test plugin has been
deployed. The profile can be generated with the release and it's a
separate file, so you just erase it when you're done with it. Think
the profile might be a bit simpler and we could certainly generate the
snippet from the staging plugin.
On 27-Aug-08, at 12:02 PM, Dan Fabulich wrote:
>
> I've always found it to be a hassle to test plugins that don't need
> to be wired up in POM files, e.g. the archetype, dependency, scm
> plugins. I find that to test them I have to create a dummy POM file
> with a <pluginRepositories> section, as described in our guide to
> testing staged releases.
>
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> I thought it would be cool to have a downloader plugin that let you
> do this:
>
> mvn downloader:get
> -Dartifact=org.apache.maven.plugins:maven-scm-plugin:1.1
> -DrepoUrl=http://people.apache.org/~olamy/staging-repo
>
> That would retrieve the plugin into your local repository, so you
> could immediately start using it.
>
> mvn org.apache.maven.plugins:maven-scm-plugin:1.1:checkin -
> Dmessage=foo
>
> I've created a prototype downloader plugin and checked it into the
> sandbox; I used it to test the Maven SCM 1.1 release. It was pretty
> nice.
>
> Does this seem like something worth releasing and documenting as
> part of our release testing guide?
>
> -Dan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.
-- Eric Hoffer, Reflections on the Human Condition
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Using a downloader to test plugin releases
Posted by Wendy Smoak <ws...@gmail.com>.
On Wed, Aug 27, 2008 at 12:02 PM, Dan Fabulich <da...@fabulich.com> wrote:
> I thought it would be cool to have a downloader plugin that let you do this:
>
> mvn downloader:get
> -Dartifact=org.apache.maven.plugins:maven-scm-plugin:1.1
> -DrepoUrl=http://people.apache.org/~olamy/staging-repo
If it will download anything (not just plugins) how about adding a
goal to the dependency plugin?
Also make sure the repoUrl parameter is consistent with other plugins
that have the same thing (archetype? is repository spelled out? URL or
Url? ). And it might need a repository id param in case it requires
credentials.
(I don't need it for plugin testing, I use a repository manager that
proxies and just add another connector to the staging repo.
Alternately, the plugin repo can go in settings.xml, it doesn't
require a pom.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org