Hi,
I need to change the Ant build target for the pde-maven-plugin.
So I checked out the trunk, changed version 2.0.9-SNAPSHOT into 2.0.8 in the
POM
and did a mvn clean install.
The following error came up:
[ERROR] BUILD ERROR
[INFO]
Hi,
i did hit the same problem and found that there is a difference in the
version range handling between maven and eclipse plugins.
My solution was rather ugly i used the maven-eclipse-plugin in the
version 2.4 to create a local repository. because that version of the
plugin ignores the version
Hi!
I work on two projects which utilize Artifactory as build artifact
manager. Both are used as proxies, so we want to make them both replace
central, but not at the same time. I also deploy/release company
internal artifacts to libs-releases/libs-snapshots to companyA's repo
and to
The Maven team is pleased to announce the release of the Maven Eclipse
Plugin, version 2.5
This plugin is used to generate Eclipse IDE files (*.classpath,
*.wtpmodules and the .settings folder) for use with a project.
http://maven.apache.org/plugins/maven-eclipse-plugin/
You can run mvn -up to
+1
Vincent
2008/3/17, Daniel Kulp [EMAIL PROTECTED]:
There is a critical bug in 1.0 where the resulting merged NOTICE files
may not be correct. This release is JUST to fix that issue (thus the
1.0.1 version and not 1.1):
http://jira.codehaus.org/browse/MSHADE-22
Staging area:
+1
Vincent
2008/3/17, Daniel Kulp [EMAIL PROTECTED]:
To comply with the latest requirements discussed on legal-discuss, we
need a new version of the apache-jar-resource-bundle.
The only change is really the result of discussions and testing around:
Late but a merry +1 :)
Vincent
2008/3/14, Arnaud HERITIER [EMAIL PROTECTED]:
Hi,
We solved more than 50 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593styleName=HtmlprojectId=11133
Important changes are :
- Add support for WTP 2.0
- Add support for MyEclipse
The vote has passed:
+1 Dennis, Lukas, Olivier and Vincent
+0 Brian
I'll proceed with the release.
Cheers,
Vincent
2008/3/10, Vincent Siveton [EMAIL PROTECTED]:
Hi,
It s again me :) I would like to release (again) the Maven Plugin
Tools projects:
* maven-plugin-plugin-2.4
*
+1
Vincent
2008/3/17, Daniel Kulp [EMAIL PROTECTED]:
Several projects are sucessfully using remote-resources so it's time pull
it out of beta and do the 1.0 release. :-)
This version provides three new improvements from 1.0-beta-2:
** Improvement
* [MRRESOURCES-22] - Provide
Help...
I started to run the integration tests to work out why my patch breaks
them, and have moved on to trying to work out why my integration tests
work on some of my machines, but not others, to a bit of confusion. My
patch is in r638310
r638310 of 2.0.x,
Hi,
2008/3/15, Lukas Theussl [EMAIL PROTECTED]:
beta-1 is actually ready IMO, the two open issues are minor and can be
postponed.
However, I do not understand why you say that MNG-3402 is dependent on a
doxia release? The aim of MNG-3402 is exactly to make maven independent
of the doxia
On 18/03/2008, at 10:51 PM, Nigel Magnay wrote:
[1] Added bonus : 12 hours ago, these worked for me on the same
machine...
[2] Looking in the IT test directories, this looks like there's a
${maven.repo.local} directory being created which is why things are
getting confused.
This looks
Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if
M2_REPO = /path/to/repo executing the command renders build paths for
dependencies for project as
M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
If I use version 2.4 M2_REPO
Ok - I'll compare to what I get.
It still worries me that you've got failures when
https://ci.sonatype.org/job/Maven-2.0.x-ITs/ is showing a clean bill
of health since Mar 17, 2008 3:32:29 PM..
On Tue, Mar 18, 2008 at 2:24 PM, Brett Porter [EMAIL PROTECTED] wrote:
These are the failures I'm
The larger question is with regards to trunk. It was requested that
scopeimport/scope not be used there and that importing just be the
defined behavior of specifying a pom in a dependencyManagement section.
I think the import scope should _NOT_ be assumed for pom projects. Pom
projects serve
Hi,
I always looked at repo IDs as something local to my machine (take
into account Brian's note: apache.snapshot vs apache.snapshots vs
apache-snapshot etc). How many builds exists with those variants of
the same repo?
Also, you can easily pull in the _same_ repo with different ID into
the
Hi all,
after Nigel words, i tried to play with Nexus and HTTP Proxying and
have tested some solutions with Nexus and HTTP Proxying.
It seems that it is feasible and easily done.
I set my m2 to use Nexus as HTTP Proxy, and made nexus to use the
incoming URL as basis to resolve the repo in
Perhaps Brian or Carlos could have an opinion about it (I think one of
them added it).
I didn't develop it and never played with this goal, thus I have no
idea about it.
Arnaud
On Tue, Mar 18, 2008 at 9:08 PM, Apaar Trivedi
[EMAIL PROTECTED] wrote:
Hell,
We need one thing parameterized on
We have modified our copy locally and verified that what I am describing
can be parameterized and it works.
I can provide a patch for review if that is desired, or any feedback
from Carlos or Brian would also be helpful.
Thanks!
Apaar
-Original Message-
From: Arnaud HERITIER
Make sure you have installed the latest core integration test folder.
I'll redeploy everything, but it's possible it is out of date. The
Hudson at ci.sonatype.org is building the Its locally everytime it
changes.
-Original Message-
From: Nigel Magnay [mailto:[EMAIL PROTECTED]
Sent:
Hi
To get the latest version of maven-source-plugin into our toolchain and
use the recently release maven-plugin-plugin 2.4, I'd
like to release the plugins parent r638340 as version 11.
Source:
https://svn.apache.org/viewvc/maven/plugins/trunk/pom.xml?r1=587343r2=638340diff_format=h
Not I, if it's OSGI, it was probably Carlos.
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 5:59 PM
To: Maven Developers List
Subject: Re: parameter needed in maven-eclipse-plugin
Perhaps Brian or Carlos could have an opinion about it (I
Hi,
the recent release of maven-eclipse-plugin:2.5 brought up
http://jira.codehaus.org/browse/MECLIPSE-404
which is caused by (windows) users specifying drive-relative paths to their
local repos.
Further progress on this issue would require some clarification:
Is Maven supposed to support
You can open an issue and attach your patch.
We see with carlos if your change seems to be interesting to apply (I
think but I'm not an expert).
On Tue, Mar 18, 2008 at 11:02 PM, Apaar Trivedi
[EMAIL PROTECTED] wrote:
We have modified our copy locally and verified that what I am describing
can
+1
Vincent
2008/3/18, Dennis Lundberg [EMAIL PROTECTED]:
Hi
To get the latest version of maven-source-plugin into our toolchain and
use the recently release maven-plugin-plugin 2.4, I'd
like to release the plugins parent r638340 as version 11.
Source:
On 19/03/2008, at 9:04 AM, Brian E. Fox wrote:
Make sure you have installed the latest core integration test folder.
I'll redeploy everything, but it's possible it is out of date. The
Hudson at ci.sonatype.org is building the Its locally everytime it
changes.
That's what I did... I haven't
To get the latest version of maven-source-plugin into our toolchain and
use the recently release maven-plugin-plugin 2.4, I'd
like to release the plugins parent r638340 as version 11.
You could consider to lock down clean-plugin and resources-plugin, too.
Benjamin
Hi Brian,
Don't forget to call the include-site profile to include the site
documentation in the release (MNG-3360)
Cheers,
Vincent
2008/3/18, Brian E. Fox [EMAIL PROTECTED]:
The list of fixes in this release is substantial. See release notes at
the bottom. High level changes are: locking
I think even the minimal (a) would be a great thing (just proxy things
you don't know about), having it able to create them on the fly (or
maybe just 'prepare' them as you suggest ready for an admin to
'approve') would be a killer feature! Nexus sounds like it's shaping
up to be a great tool..
Thank you, I have submitted an issue with a patch.
http://jira.codehaus.org/browse/MECLIPSE-405
Thanks again,
Apaar
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 5:30 PM
To: Maven Developers List
Subject: Re: parameter needed in
i have answered to the issue, included here for reference. If you dont
like the way the to-maven goal works you need to use the
make-artifacts goal, it should do the same but allowing customization
The qualifier is an important part of the version, it's not the same
3.3.0.x than 3.3.0.y so if
Unfortunately the make-artifacts goal does not do the same, it does not
name the artifact id's correctly and does not setup the heirarchy in the
repository correctly, which is why it is deprecated I believe. \
I have responded to the issue and will maintain the rest of my responses
to the issue.
+1 tested on the archetype plugin build.
Raphaël
2008/3/18, Brian E. Fox [EMAIL PROTECTED]:
The list of fixes in this release is substantial. See release notes at
the bottom. High level changes are: locking down the plugins in the
super pom, new import scope, new toolchain support, native
I don't follow what you're actually trying to do. Are you trying to
switch between two artifactories/mirrors or change where you deploy to?
(or both?)
-Original Message-
From: Erik Drolshammer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 3:54 AM
To: Maven Developers List
There are two ways you can run the Its. First is in the maven build
tree, use mvn clean install -Prun-its. This will build and then unpack
the maven and use it to run the Its from a jar. If you do this, make
sure you have already installed the it tree.
The other way is to build and install the
I'd like to contribute a table to the 2.0.9 release under the issues that
may affect build section detailing the defaulted plugins and versions. Can
I just attach it to MNG-3395?
Paul
On Tue, Mar 18, 2008 at 5:42 PM, Vincent Siveton [EMAIL PROTECTED]
wrote:
Hi Brian,
Don't forget to call the
36 matches
Mail list logo
