You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Kenney Westerhof (JIRA)" <ji...@codehaus.org> on 2005/08/11 14:43:57 UTC
[jira] Created: (MNG-724) Make distinction between m2 and project plugins, and add --dont-update-snapshots and --dont-update-maven-snapshots
Make distinction between m2 and project plugins, and add --dont-update-snapshots and --dont-update-maven-snapshots
------------------------------------------------------------------------------------------------------------------
Key: MNG-724
URL: http://jira.codehaus.org/browse/MNG-724
Project: Maven 2
Type: Wish
Components: maven-core
Versions: 2.0-beta-1
Reporter: Kenney Westerhof
Priority: Minor
Make a distinction between Maven dependencies and Project dependencies.
Maven core deps are already in the maven dir; everything that those depend on, like plugins and their dependencies,
are 'maven dependencies', needed to build the project.
The project itself also has dependencies, those are the project dependencies (doh!)
I've had almost daily problems here using a bootstrapped snapshot m2, because dependencies
of m2 (like plexus-compiler-*) were updated, and these updates broke the compiler-plugin, requiring
a new bootstrap.
I'd like to be able to tell m2 NOT to update snapshots, be it m2 snapshots, project snapshots, or in general (both).
Offline mode doesn't cover this - it will also not download releases.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-724) Make distinction between m2 and project plugins, and add --dont-update-snapshots and --dont-update-maven-snapshots
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-724?page=all ]
Brett Porter closed MNG-724:
----------------------------
Assign To: Brett Porter
Resolution: Won't Fix
I'm not in favour of this. It's still not a deterministic way to handle this.
The problem is that m2 libs are breaking compatibility. Two things need to happen (or not happen as the case may be):
- stabilise the maven public API, particularly anything used by plugins. Stop breaking them.
- reduce dependence on the m2 APIs and minimise what is exposed to the plugins by separating a known API from the implementations.
To ease the pain while we are still changing the interfaces, plugins can now specify a minimum m2 version to run on which should prevent newer versions being used on an old m2 build.
> Make distinction between m2 and project plugins, and add --dont-update-snapshots and --dont-update-maven-snapshots
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-724
> URL: http://jira.codehaus.org/browse/MNG-724
> Project: Maven 2
> Type: Wish
> Components: maven-core
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: Brett Porter
> Priority: Minor
>
>
> Make a distinction between Maven dependencies and Project dependencies.
> Maven core deps are already in the maven dir; everything that those depend on, like plugins and their dependencies,
> are 'maven dependencies', needed to build the project.
> The project itself also has dependencies, those are the project dependencies (doh!)
> I've had almost daily problems here using a bootstrapped snapshot m2, because dependencies
> of m2 (like plexus-compiler-*) were updated, and these updates broke the compiler-plugin, requiring
> a new bootstrap.
> I'd like to be able to tell m2 NOT to update snapshots, be it m2 snapshots, project snapshots, or in general (both).
> Offline mode doesn't cover this - it will also not download releases.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org