Hello,
The releases of your companies artifacts can't use snapshot versions
and internally patched versions of the plugins needs to be made
available to all developers.
I solved these issues by writing my own proxy which can rewrite URLs (so
even if someone configures Maven to download
On 12/18/06, Brett Porter [EMAIL PROTECTED] wrote:
Sorry to top reply, but my summarised response is:
- there are valid use cases for plugins in more than one repository
- Maven should always be using the repository with the newest version
available. If it's not, then it's a bug.
If you are
Sorry to top reply, but my summarised response is:
- there are valid use cases for plugins in more than one repository
- Maven should always be using the repository with the newest version
available. If it's not, then it's a bug.
If you are using a version the last release, and the
Hi,
I'm following this setup/process:
- We have the following repository definitions in the root pom of the projects:
* repository central - inherited, for normal non-snapshot artifacts
* pluginRepository central - inherited, for normal non-snapshot plugins
* repository company.repo for
On 12/16/06, Kenney Westerhof [EMAIL PROTECTED] wrote:
Thanks Kenney,
- colleagues will automatically get the snapshot version of the plugin, but due
to a a bug in maven 2.0.4
they could end up with the wrong plugin in the reactor. For instance:
mvn
See http://www.nabble.com/forum/ViewPost.jtp?post=7884079framed=yskin=177
for full discussion.
The problem is that a plugin contains defects that have not yet been
resolved in a release.
The defect may be fixed in a snapshot version or there may be an
unapplied patch available.
The releases of
