You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2007/04/12 21:06:46 UTC
[jira] Created: (MNG-2945) plugin to facilitate downloads of
snapshot plugins and dependencies for each insertion into internal
repository.
plugin to facilitate downloads of snapshot plugins and dependencies for each insertion into internal repository.
----------------------------------------------------------------------------------------------------------------
Key: MNG-2945
URL: http://jira.codehaus.org/browse/MNG-2945
Project: Maven 2
Issue Type: New Feature
Components: Plugin Requests
Reporter: Brian Fox
Priority: Minor
Discussed here.
http://www.nabble.com/Re%3A-Remove-auto-resolution-of-plugin-versions-from-Maven-2.1-p9965795s177.html
>
> Here's how I deal with instances where I need a snapshot plugin in my
> corp build:
> 1. Checkout the code for the snapshot.
> 2. Build it, changing the version to something like
> 2.0-[companyname]-svnrev 3. If I have to patch the source at all, I
> take the whole thing and put it in my svn. If not, then the svnrev in
> the release points me back to where I got it in case I need it later.
> 4. Deploy it to my repos.
> 5. Use this now "internally released" version in my builds.
>
I've done this, and also with smaller external snapshots I've downloaded them and just adjusted the metadata (and filename) before deploying to my local repos.
What would be really, really, really useful would be a plugin that you could call that would download a snapshot of a project and its (transient,
snapshot) dependencies, re-label it as a fixed internal version. There's occasions where you just can't wait for an external project to release (and of course this problem is recursive!), and rebuilding everything yourself is a bit drag on the person doing a release.
something like
mvn artifact:freeze-snapshot org.apache.myfaces myfaces-all 1.1.6-SNAPSHOT 1.1.6-mycorp
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MSANDBOX-42) plugin to facilitate downloads of
snapshot plugins and dependencies for each insertion into internal
repository.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSANDBOX-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-2945 to MSANDBOX-42:
-------------------------------------------
Fix Version/s: (was: Reviewed Pending Version Assignment)
Component/s: (was: Plugin Requests)
Key: MSANDBOX-42 (was: MNG-2945)
Project: Maven 2.x Sandbox (was: Maven 2)
> plugin to facilitate downloads of snapshot plugins and dependencies for each insertion into internal repository.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MSANDBOX-42
> URL: http://jira.codehaus.org/browse/MSANDBOX-42
> Project: Maven 2.x Sandbox
> Issue Type: New Feature
> Reporter: Brian Fox
> Priority: Minor
>
> Discussed here.
> http://www.nabble.com/Re%3A-Remove-auto-resolution-of-plugin-versions-from-Maven-2.1-p9965795s177.html
> >
> > Here's how I deal with instances where I need a snapshot plugin in my
> > corp build:
> > 1. Checkout the code for the snapshot.
> > 2. Build it, changing the version to something like
> > 2.0-[companyname]-svnrev 3. If I have to patch the source at all, I
> > take the whole thing and put it in my svn. If not, then the svnrev in
> > the release points me back to where I got it in case I need it later.
> > 4. Deploy it to my repos.
> > 5. Use this now "internally released" version in my builds.
> >
> I've done this, and also with smaller external snapshots I've downloaded them and just adjusted the metadata (and filename) before deploying to my local repos.
> What would be really, really, really useful would be a plugin that you could call that would download a snapshot of a project and its (transient,
> snapshot) dependencies, re-label it as a fixed internal version. There's occasions where you just can't wait for an external project to release (and of course this problem is recursive!), and rebuilding everything yourself is a bit drag on the person doing a release.
> something like
> mvn artifact:freeze-snapshot org.apache.myfaces myfaces-all 1.1.6-SNAPSHOT 1.1.6-mycorp
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2945) plugin to facilitate downloads of
snapshot plugins and dependencies for each insertion into internal
repository.
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-2945:
-------------------------------
Patch Submitted: (was: [Yes])
> plugin to facilitate downloads of snapshot plugins and dependencies for each insertion into internal repository.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2945
> URL: http://jira.codehaus.org/browse/MNG-2945
> Project: Maven 2
> Issue Type: New Feature
> Components: Plugin Requests
> Reporter: Brian Fox
> Priority: Minor
>
> Discussed here.
> http://www.nabble.com/Re%3A-Remove-auto-resolution-of-plugin-versions-from-Maven-2.1-p9965795s177.html
> >
> > Here's how I deal with instances where I need a snapshot plugin in my
> > corp build:
> > 1. Checkout the code for the snapshot.
> > 2. Build it, changing the version to something like
> > 2.0-[companyname]-svnrev 3. If I have to patch the source at all, I
> > take the whole thing and put it in my svn. If not, then the svnrev in
> > the release points me back to where I got it in case I need it later.
> > 4. Deploy it to my repos.
> > 5. Use this now "internally released" version in my builds.
> >
> I've done this, and also with smaller external snapshots I've downloaded them and just adjusted the metadata (and filename) before deploying to my local repos.
> What would be really, really, really useful would be a plugin that you could call that would download a snapshot of a project and its (transient,
> snapshot) dependencies, re-label it as a fixed internal version. There's occasions where you just can't wait for an external project to release (and of course this problem is recursive!), and rebuilding everything yourself is a bit drag on the person doing a release.
> something like
> mvn artifact:freeze-snapshot org.apache.myfaces myfaces-all 1.1.6-SNAPSHOT 1.1.6-mycorp
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira