2008/3/19, Wendy Smoak <[EMAIL PROTECTED]>:
> On Wed, Mar 19, 2008 at 7:54 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
>
> > This seems a little weird. Why are we packaging up the entire site and
> > deploying it in the assembly?
>
>
> I don't think it should go inside the Maven distribution, bu
2008/3/19, Brian E. Fox <[EMAIL PROTECTED]>:
> This seems a little weird. Why are we packaging up the entire site and
> deploying it in the assembly?
>
Because users want documentation. The only problem is that we don't
use tag for site.
Cheers,
Vincent
>
> -Original Message-
> From:
2008/3/19, Brian E. Fox <[EMAIL PROTECTED]>:
> I don't follow. What changes?
I don't know but my gutfeeling is changes in the dependencies resolution.
Cheers,
Vincent
>
> -Original Message-
> From: Vincent Siveton [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 19, 2008 8:08 PM
>
I don't follow. What changes?
-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 8:08 PM
To: Maven Developers List
Subject: Re: problem with plugin-plugin 2.4
Hi Brian,
Mmmh. I didn't expect this problem with maven 2.0.8 or below but with
2008/3/19, Brian E. Fox <[EMAIL PROTECTED]>:
> This also seems related to the latest release. Looks like we're going to
> need to respin this stuff pretty quickly:
> http://jira.codehaus.org/browse/MPLUGIN-102
>
I don't think it is related, I will comment.
Cheers,
Vincent
> -Original Mes
Hi Brian,
Mmmh. I didn't expect this problem with maven 2.0.8 or below but with 2.0.9.
Due to changes made in 2.0.9, the plugin now needs doxia-core with
runtime scope (???).
Cheers,
Vincent
2008/3/19, Brian E. Fox <[EMAIL PROTECTED]>:
> Today I'm not able to build the maven-dependency-plugin s
We should fix it, but it has no bearing on the binary that is staged.
-Original Message-
From: Ralph Goers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 6:36 PM
To: Maven Developers List
Subject: Re: 2.0.x bootstrap process is fixed
Brian E. Fox wrote:
> Nope, you can't run
Brian E. Fox wrote:
Nope, you can't run the release plugin from the bootstrap...I just use
whatever maven I happen to have installed, usually the snapshot I last
built for testing.
Does this mean it is OK to release 2.0.9 even though bootstrap.sh
doesn't work? Just curious.
Ah yes I did miss that.I've been seeing a combination of plugins not being
locked down and in other threads people using the 2.0.9 snapshot having
problems with their plugins and didn't see that you had locked them down
specifically. I also just now see in the previous thread why they are being
loc
This also seems related to the latest release. Looks like we're going to
need to respin this stuff pretty quickly:
http://jira.codehaus.org/browse/MPLUGIN-102
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 5:52 PM
To: Maven Developers List
I accidentally had it configured twice in Continuum - fixed. I don't
tend to notice because my POP does a weird thing of grabbing messages
twice occasionally so I just assume it's at fault.
On 20/03/2008, at 8:04 AM, Brian E. Fox wrote:
Anyone know why all the continuum emails come through
Sejal,
You must have missed the previous responses that said that only plug-ins
that affect the build cycle will be locked down. So the list below is
incorrect. Nicolas was making a comment/suggestion, not stating what *is*
locked down.
For the record, this is from the Maven 2.0.9 POM (minus conf
Huh? This wasn't a vote and I restaged it already
-Original Message-
From: Sejal Patel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 5:41 PM
To: Maven Developers List
Cc: Daniel Kulp
Subject: Re: [Pre-Vote] release maven 2.0.9
Not to be a party pooper but given all the di
Today I'm not able to build the maven-dependency-plugin site:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error getting reports from the plugin
'org.
Hi everyone,
As I think I promised last week, I've written up some documentation
for the plugin- and extension-loading refactor I did in trunk last
fall. It's here:
http://docs.codehaus.org/display/MAVEN/Maven+2.1+Plugin+and+Extension
+Loading+Design
I'd really appreciate if people could
Not to be a party pooper but given all the discussions that are cropping up
over and around this release, I feel like a vote of -1 is in order.
On Wed, Mar 19, 2008 at 11:42 AM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:
> >Well, the auto-update of the archetype-plugin certainly has caused a
> LOT
>
Anyone know why all the continuum emails come through twice? I checked
that it's not just me:
http://www.nabble.com/Maven---Notifications-f15574.html
-Original Message-
From: Continuum VMBuild Server [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 3:20 PM
To: [EMAIL PROTECTED]
S
Hi All,
I was wondering who the active developers are on the maven 2 eclipse plugin
(http://maven.apache.org/plugins/maven-eclipse-plugin/index.html)? I am
wondering if there are any plans to support .factorypath generation for
eclipse projects? A .factorypath specifies annotation processor fact
Adjusted the EAR plugin version to 2.3.1
The release is staged at:
http://people.apache.org/~brianf/staging-repository/
The bundles are here:
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/2.0.9/
-Original Message-
From: Brian E. Fox [mailto:[EMA
>Well, the auto-update of the archetype-plugin certainly has caused a
LOT
>of issues lately. Would that be considered one of your "commonly used
>utilities"?
Normally yes, but it's already out there and locking down to alpha-2
probably isn't a good idea as it will block lots of people from get
Based on the comments in the pre-vote for Maven 2.0.9, this needs more
discussion.
I like the idea of off-line docs, but not necessarily bundling them
into the main Maven distribution. Also, this isn't reproducible since
it works from site/trunk and not a tag.
--
Wendy
On Thu, Jan 10, 2008 at
Hi All,
When I was trying to do a workaround with
http://jira.jboss.org/jira/browse/JBIDE-1862 (actually seems to be WTP
2.0.2bug) it appears that maven-eclipse-plugin ignores
application.xml that is generated by maven ear plugin. While this might be
ok with WTP 2.0.2 you will have a problem if yo
Well, the auto-update of the archetype-plugin certainly has caused a LOT
of issues lately. Would that be considered one of your "commonly used
utilities"?
Dan
On Wednesday 19 March 2008, Brian E. Fox wrote:
> Crap. I'll have to fix the ear version. The other stuff I don't think
> needs to be
Crap. I'll have to fix the ear version. The other stuff I don't think
needs to be locked down. The goal was to lock down the most important
plugins, things that directly affect a build as part of the default
lifecycle and commonly used utilities. I don't think we want to start
including every singl
Yes, the default build lifecycle not everything.
On 19-Mar-08, at 8:20 AM, Paul Benedict wrote:
nicolas,
I won't speak for Brian, but I thought his intention was to lock down
plug-ins that only affect the build cycle.
Paul
On Wed, Mar 19, 2008 at 10:18 AM, nicolas de loof <[EMAIL PROTECTED]>
nicolas,
I won't speak for Brian, but I thought his intention was to lock down
plug-ins that only affect the build cycle.
Paul
On Wed, Mar 19, 2008 at 10:18 AM, nicolas de loof <[EMAIL PROTECTED]>
wrote:
> I notice some official maven plugin don't have fixed version in the
> super-POM :
>
> mav
I notice some official maven plugin don't have fixed version in the
super-POM :
maven-archetype-plugin
maven-checkstyle-plugin
maven-eclipse-plugin
maven-idea-plugin
maven-jxr-plugin
maven-invoker-plugin
maven-one-plugin
maven-patch-plugin
maven-pmd-plugin
maven-projecthelp-plugin
maven-remote-res
http://jira.codehaus.org/browse/MNG-3360
If this profile is activated, the entire site gets jammed into the
bundle.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 11:09 AM
To: Maven Developers List
Subject: Re: [Pre-Vote] release maven 2.
On Wed, Mar 19, 2008 at 7:54 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> This seems a little weird. Why are we packaging up the entire site and
> deploying it in the assembly?
I don't think it should go inside the Maven distribution, but a
separate docs assembly would be nice to have.
What is
On 19-Mar-08, at 7:54 AM, Brian E. Fox wrote:
This seems a little weird. Why are we packaging up the entire site and
deploying it in the assembly?
That's not right. Who started doing that?
-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2
Sure, that'd be great.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul Benedict
Sent: Tuesday, March 18, 2008 11:19 PM
To: Maven Developers List
Subject: Re: [Pre-Vote] release maven 2.0.9
I'd like to contribute a table to the 2.0.9 release under the
This seems a little weird. Why are we packaging up the entire site and
deploying it in the assembly?
-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 6:42 PM
To: Maven Developers List
Subject: Re: [Pre-Vote] release maven 2.0.9
Hi Brian,
D
Nope, you can't run the release plugin from the bootstrap...I just use
whatever maven I happen to have installed, usually the snapshot I last
built for testing.
-Original Message-
From: Ralph Goers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 3:14 AM
To: Maven Developers List
Brian E. Fox wrote:
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?)
Both. I want to switch between multiple artifactories and I want the
repos in these to follow the same naming conventions.
Now I'm wondering how the rest of you actually build maven. I checked
out from the 2.0.9 tag and it failed the same way. So I guess
bootstrap.sh isn't actually used to build Maven for a release?
Ralph Goers wrote:
Now it is failing again, albeit differently. I'm getting a
NullPointerException.
Now it is failing again, albeit differently. I'm getting a
NullPointerException. Here is the tail end of the log.
Building project in /projects/maven2/temp/maven-2.0.x/apache-maven
--
Cleaning /projects/maven2/temp/maven-2.0.x/apach
36 matches
Mail list logo
