Hi Guys,
Can you tell me how is setup the build of plugins on hudson @ sonatype ?
JDK version?
Maven version ?
I don't understand this error related to plexus :
I've noticed that dependency reduced pom produced by the shade plugin
contains unnecessary exclusions. Checking the code, in ShadeMojo:825
we have:
//anything two levels deep that is not marked included
//is stuff that was excluded by the original poms, make sure
Hi,
2008/7/14, Brian E. Fox [EMAIL PROTECTED]:
I just went to cut the RC for 2.0.10 and found out that it's failing on
a snapshot dependency of Doxia. I know we were debating to include this
in 2.0.9...is it ready to go or do we have to revert?
According our release plan [1], we are soon to
Just a little bug :
http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.1/project-summary.html
Did you use the 2.1 to generate its own site ?
arnaud
On Tue, Jul 15, 2008 at 12:41 PM, Vincent Siveton [EMAIL PROTECTED]
wrote:
Hi,
We solved around 65 issues:
I'll just give you access and then you can look at the configuration.
On 15-Jul-08, at 4:53 AM, Arnaud HERITIER wrote:
Hi Guys,
Can you tell me how is setup the build of plugins on hudson @
sonatype ?
JDK version?
Maven version ?
I don't understand this error related to plexus :
Thanks.
What is the version of maven 2.0 wich is in : /opt/maven/2.0. Is it a maven
2.0.0 ?
The eclipse plugin requires to be build with at least maven 2.0.8.
I also noticed that the build of plugins is disabled. Any idea why ?
Can we schedule it one or two times per day ?
Arnaud
On Tue, Jul
On 15-Jul-08, at 8:30 AM, Arnaud HERITIER wrote:
Thanks.
What is the version of maven 2.0 wich is in : /opt/maven/2.0. Is it
a maven
2.0.0 ?
Again, all in the configuration for Hudson. It manages many
installations and you can look at the details in the console.
The eclipse plugin
The 2.0 is a symlink to 2.0.9. The plugins were disabled because Hudson
had them as a dependency of itself so it was building in a circle. I
shut it off until I had a moment to upgrade Hudson. I'll do that today.
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent:
There's only 1 issue left in Jira and it didn't seem to be a huge deal.
We've been driving towards the 2.0.10 release for a while now and I
don't think we want to wait another couple of weeks. What are the
ramifications of reverting back the beta? Recall that the original plan
was to release the
On Tue, Jul 15, 2008 at 2:48 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
On 15-Jul-08, at 8:30 AM, Arnaud HERITIER wrote:
Thanks.
What is the version of maven 2.0 wich is in : /opt/maven/2.0. Is it a
maven
2.0.0 ?
Again, all in the configuration for Hudson. It manages many installations
Hi Arnaud,
It is a known issue, see MPIR-88
Cheers,
Vincent
2008/7/15, Arnaud HERITIER [EMAIL PROTECTED]:
Just a little bug :
http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.1/project-summary.html
Did you use the 2.1 to generate its own site ?
arnaud
On Tue,
I will be out of the office starting 12.07.2008 and will not return until
28.07.2008.
I will respond to your message when I return. In urgent cases please refer
to Elena Tonoyan ([EMAIL PROTECTED]) or Daria Ignatieva
([EMAIL PROTECTED])
ok this only for the staging thus +1
Arnaud
On Tue, Jul 15, 2008 at 5:42 PM, Vincent Siveton [EMAIL PROTECTED]
wrote:
Hi Arnaud,
It is a known issue, see MPIR-88
Cheers,
Vincent
2008/7/15, Arnaud HERITIER [EMAIL PROTECTED]:
Just a little bug :
Guys,
I am preparing to cut the first release of the artifact-3.0
Are there any issues that are not resolved anyone knows about? Please
raise them in http://jira.codehaus.org/browse/MNG-3185
Thanks,
Oleg
-
To unsubscribe,
IMO there are several things that will need to change for this update to
be effective. The site plugin still lists a bunch of alpha-10
dependencies, so even with DOXIA-245 fixed (I just committed a fix), it
won't be used until the site plugin is updated (or people add a long
list of updated
Just wanted to let everyone know that we're quickly approaching a stable
build that I feel comfortable cutting as RC-1 so we can start abusing it.
First, however, I've had to revert the patch for MNG-3503, since this
patch (which refined the shaded exclusions to only leave the Xpp3Dom and
Hi,
My plan is after my vacations :-) (middle of next week).
But before I thougth about a change in maven-filtering : using last
plexus-interpolation instead of FileUtils.FilterWrapper.
This will break the current maven-filtering api but this component has
never been released and it's a sandbox
Hi again,
As promised, I've staged the first release candidate for Maven 2.0.10 here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
The issues resolved for this release (so far) are here:
I say start out using the new interpolator apis so we don't have to
consolidate more later.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Olivier Lamy
Sent: Tuesday, July 15, 2008 4:50 PM
To: Maven Developers List
Subject: Re: Releasing maven-filering?
The POM lost its license during the release, suffering from point 1b of
http://maven.apache.org/developers/release/releasing.html
[EMAIL PROTECTED] wrote:
Author: carlos
Date: Tue Jul 15 15:40:55 2008
New Revision: 677075
URL: http://svn.apache.org/viewvc?rev=677075view=rev
Log:
It probably goes without saying, but no objections here :)
On 16/07/2008, at 3:08 AM, Oleg Gusakov wrote:
Guys,
I am preparing to cut the first release of the artifact-3.0
Are there any issues that are not resolved anyone knows about?
Please raise them in
sounds good to me. fire away!
Oleg Gusakov wrote:
Guys,
I am preparing to cut the first release of the artifact-3.0
Are there any issues that are not resolved anyone knows about? Please
raise them in http://jira.codehaus.org/browse/MNG-3185
Thanks,
Oleg
On 16/07/2008, at 7:32 AM, [EMAIL PROTECTED] wrote:
Author: jdcasey
Date: Tue Jul 15 14:32:01 2008
New Revision: 677049
URL: http://svn.apache.org/viewvc?rev=677049view=rev
Log:
rolling back to shade plugin version 1.1.
This will break the setting of the User-Agent header on http requests
On 15/07/2008, at 8:32 PM, Mark Hobson wrote:
I've noticed that dependency reduced pom produced by the shade plugin
contains unnecessary exclusions. Checking the code, in ShadeMojo:825
we have:
//anything two levels deep that is not marked
included
//is stuff
Looks like the 1.1 version of the shade plugin didn't do what I needed
it to WRT avoiding rewriting the Xpp3Dom and/or XmlSerializer classes.
The IT for MNG-3503 is messed up in the RC1 build, so I'll be cutting an
RC2 as soon as I can verify that 1.0 of the shade plugin works (this is
what we
I think 1.0.1 was what would have been used in 2.0.9 (it looks like no
version was given to me though).
Any idea what is wrong in 1.1+?
- Brett
On 16/07/2008, at 10:02 AM, [EMAIL PROTECTED] wrote:
Author: jdcasey
Date: Tue Jul 15 17:02:42 2008
New Revision: 677112
URL:
I think the comment is wrong. If it's two levels deep and included, it was
stuff that was originally excluded and needs to be re-excluded. I doubt
there is a test for it, but it was tested in the OpenEJB project and in CXF.
Dan
mihobson wrote:
I've noticed that dependency reduced
I just checked and if I reverse that logic, I get things like:
dependency
groupIdorg.springframework/groupId
artifactIdspring-core/artifactId
version2.0.8/version
scopecompile/scope
exclusions
exclusion
artifactIdcommons-logging/artifactId
28 matches
Mail list logo
