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
On Wed, Aug 27, 2008 at 12:02 PM, Dan Fabulich <[EMAIL PROTECTED]> 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
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
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
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
section, as described in our guide to testing staged
releases.
http://maven.apach
