I talked with Jason last month about moving and renaming maven-shared-model,
as the component is completely general. It allows people to handle
inheritance, interpolation and transforms on any model in any format. Jason
pinged me before the move and I was in favor of it. It's much clearer to
people
On 15/12/2008, at 6:51 AM, jvan...@apache.org wrote:
Modified: maven/components/trunk/maven-core/pom.xml
URL:
http://svn.apache.org/viewvc/maven/components/trunk/maven-core/pom.xml?rev=726521&r1=726520&r2=726521&view=diff
=
=
=
=
=
=
=
=
On 12/12/2008, at 5:47 PM, Jason van Zyl wrote:
Sent from my iPhone
On Dec 12, 2008, at 7:02 AM, Brett Porter wrote:
Hi,
I was looking at applying the patch for this one, but wasn't happy
with it and looked for a better solution, which I'm also not happy
with :)
Basically, in the r
On 12/12/2008, at 6:57 AM, Barrie Treloar wrote:
On Fri, Dec 12, 2008 at 3:51 AM, Brian E. Fox > wrote:
I think most of these ideas are already covered in the lifecycle
proposal out there that john wrote.
Can you paste the link in please?
http://docs.codehaus.org/display/MAVEN/Deterministic
2.0.10 builds the site just fine. So it sounds like we have a 2.1.0-M2
issue on our hands.
Paul
On Sun, Dec 14, 2008 at 7:51 PM, Brett Porter wrote:
> Have you tried with 2.0.10 RC's? It'd be good to know if the change was
> introduced in that portion of what was in 2.1.0.
>
> It'd be helpful to
>> Is there someone taking ownership of getting a working CI on p.a.o?
>
> It's a bit more than that, since two of the snapshots are from codehaus and
> wouldn't be deployed there anyway. A better thing to do is not depend on
> snapshots for so long :)
Agreed. I was hoping to make a quick change w
On 15/12/2008, at 2:41 PM, Barrie Treloar wrote:
On Mon, Dec 15, 2008 at 12:35 PM, Brian E. Fox > wrote:
The grid is only deploying to the snapshot repo hosted on nexus at
repository.sonatype.org. It's not possible with the current security
setup for us to deploy to p.a.o. Nor is it really desi
On Mon, Dec 15, 2008 at 12:35 PM, Brian E. Fox wrote:
> The grid is only deploying to the snapshot repo hosted on nexus at
> repository.sonatype.org. It's not possible with the current security
> setup for us to deploy to p.a.o. Nor is it really desired because
> there's no automated cleanup there
The grid is only deploying to the snapshot repo hosted on nexus at
repository.sonatype.org. It's not possible with the current security
setup for us to deploy to p.a.o. Nor is it really desired because
there's no automated cleanup there. Nexus is handling that for us. I
wish there was a better way,
On 15/12/2008, at 11:31 AM, Jason van Zyl wrote:
Not sure what you mean there are no Maven jobs on the old Sonatype:
http://ci.sonatype.org/
And why would notifications get spammed if it's going to a list of
people?
My mistake, it's the one on the Apache Hudson zone that needs to be
fi
Have you tried with 2.0.10 RC's? It'd be good to know if the change
was introduced in that portion of what was in 2.1.0.
It'd be helpful to check if we have a bug tracking this already for
2.1.0-M2 regardless.
- Brett
On 15/12/2008, at 11:27 AM, Paul Benedict wrote:
When I generated our
On Mon, Dec 15, 2008 at 10:49 AM, Barrie Treloar wrote:
> On Mon, Dec 15, 2008 at 10:47 AM, Barrie Treloar wrote:
>> I just tried to build maven-assembly-plugin from trunk and I can't
>> because of all the snapshot dependencies that are not available on the
>> snapshot repo.
The its also fail be
Not sure what you mean there are no Maven jobs on the old Sonatype:
http://ci.sonatype.org/
And why would notifications get spammed if it's going to a list of
people?
On 14-Dec-08, at 6:31 PM, Brett Porter wrote:
Could you fix the notifications please?
"Sending e-mails to: ja...@maven.org
When I generated our last Struts website with 2.1.0, it turned out
that some urls were really messed up. If you want to reproduce this,
just stage the S1 website on your locale machine to see the links
messed up. In particular, (a) the Releases link on the left-hand side
and (b) the Struts 1 link i
On Mon, Dec 15, 2008 at 10:47 AM, Barrie Treloar wrote:
> I just tried to build maven-assembly-plugin from trunk and I can't
> because of all the snapshot dependencies that are not available on the
> snapshot repo.
I am using the following profiles:
apache
pe
I just tried to build maven-assembly-plugin from trunk and I can't
because of all the snapshot dependencies that are not available on the
snapshot repo.
Is this something that grid is meant to be doing?
I think I've seen emails that grid is replacing the CI servers.
This would help me avoid chasi
Do we need to bump this out to 2.0.11? It seems to still be reopened
for 2.0.10 waiting on a comment from John.
- Brett
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
Could you fix the notifications please?
"Sending e-mails to: ja...@maven.org shane.isb...@gmail.com oleg.gusa...@gmail.com
"
notificati...@maven is just getting spammed by the old Sonatype CI
that is failing.
- Brett
On 15/12/2008, at 7:27 AM, Jason van Zyl wrote:
I'm getting close to el
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
Err... cut-n-past
On Mon, Dec 15, 2008 at 12:58 AM, Vincent Siveton
wrote:
> Hi,
>
> MNG-2636 points that settings-1.0.0.xsd (and also profiles-1.0.0.xsd)
> uses the same namespace than Maven. This issue was similar to
> MASSEMBLY-296.
> So, I fixed the modello files to include new namespaces for settings
> and pro
Hi Wendy,
2008/12/14 Wendy Smoak :
> On Sun, Dec 14, 2008 at 7:28 AM, Vincent Siveton
> wrote:
>
>> Is it intentional that these files are not deployed? If yes, why do we
>> need to generate them?
>
> They're probably not being deployed because it requires a manual step.
>
> For the Struts site,
done
Vincent
2008/12/14 Olivier Lamy :
> Hi Vincent,
> Is it possible to send an email to users ml just for information ?
> Due to this change (new schema [1] with namespace change) if I open my
> settings.xml with a xml editor which apply validation it breaks due to
> the namespace change.
>
> T
I'm getting close to eliminating the last of the problems, but the
grid build is working for and we'll start adding more OS's but things
are fine for Ubuntu and Windows.
https://grid.sonatype.org/ci/view/Maven%203.0.x/job/maven-3.0.x-bootstrap/
Almost there.
Thanks,
Jason
On Fri, 12 Dec 2008 09:59:33 Chris Maki wrote:
When you say you get unstable builds you mean untested right? Because
appropriate use of ranges will prevent you
from assembling (war, ear, etc) artifacts that conflict.
Ultimately the goal is stable software... right?
In which case you want to use
On Sun, Dec 14, 2008 at 7:28 AM, Vincent Siveton
wrote:
> Is it intentional that these files are not deployed? If yes, why do we
> need to generate them?
They're probably not being deployed because it requires a manual step.
For the Struts site, we have some antrun config [1] that grabs the
dtd
Hi Vincent,
Is it possible to send an email to users ml just for information ?
Due to this change (new schema [1] with namespace change) if I open my
settings.xml with a xml editor which apply validation it breaks due to
the namespace change.
Thanks,
--
Olivier
[1] http://maven.apache.org/xsd/set
Hi,
MNG-2636 points that settings-1.0.0.xsd (and also profiles-1.0.0.xsd)
uses the same namespace than Maven. This issue was similar to
MASSEMBLY-296.
So, I fixed the modello files to include new namespaces for settings
and profiles:
http://maven.apache.org/PROFILES/1.0.0
http://maven.apache.org/S
On 14/12/2008, at 5:24 PM, jvan...@apache.org wrote:
Author: jvanzyl
Date: Sat Dec 13 22:24:01 2008
New Revision: 726383
URL: http://svn.apache.org/viewvc?rev=726383&view=rev
Log:
MNG-3905 First pass at collecting all the repository related code
and started to decouple from maven-artifact
Hi Dennis,
> 2. Rename
> http://svn.eu.apache.org/repos/asf/maven/doxia/doxia-sitetools/branches/doxia-sitetools-1.0-alpha-x/
> to
> http://svn.eu.apache.org/repos/asf/maven/doxia/doxia-sitetools/branches/doxia-sitetools-1.0.x/
I didn't remember this branch... Thanks to refresh my memory :)
So,
Off the top of my head I can't think of circumstances that would cause
this, but some possibilities:
* if the later stage is in part of a "forked" lifecycle the project
may have been altered
* if the enforcer rule or another plugin is modifying/cloning the
project
Do you have a small repr
30 matches
Mail list logo
