> On Dec 14, 2014, at 8:29 PM, Jason van Zyl wrote:
>
> What we want is a form of continuous delivery where a version like 3.2.4 is
> the version that we call it to the outside world (some refer to it as the
> marketing version) and the qualifier changes from build to build so we have:
>
> 3
http://blog.sonatype.com/2014/07/ssl_connectivity_for_central/
--Brian (mobile)
> On Jul 28, 2014, at 11:06 PM, Brian Fox wrote:
>
> We are already in the process of making this open for free to
> everyone. Way back in 2012 the CDN situation was different but we just
> renewed the contract and
+1
--Brian (mobile)
On Jan 17, 2013, at 3:17 PM, Olivier Lamy wrote:
> Hi,
> I'd like to release both ASF Parent pom 13 and Maven parent pom 23
>
> ASF Parent pom 13:
> * staging repository:
> https://repository.apache.org/content/repositories/orgapacheapache-142/
> * diff with previous relea
Hi Nicolas, this isn't intentional of course. Let me see what I can dig up
based in your traces.
--Brian (mobile)
On Jul 7, 2012, at 11:45 PM, Niclas Hedhman wrote:
> (I am not subscribed, so please CC me on any responses)
>
> I live in China. I normally have a VPN enabled to circumvent vari
+1 since we moved that way for 2.2 and 3, I think we can safely move all of our
cosebases to 1.6 as needed
--Brian (mobile)
On Dec 28, 2010, at 3:15 PM, Olivier Lamy wrote:
> Hi,
> As we will start a new year, I'd like to move scm to java 1.5.
> Let me know if you have any trouble regarding t
-1 to a, +1 to b
--Brian (mobile)
On Dec 28, 2010, at 1:20 PM, Jason van Zyl wrote:
>
> On Dec 28, 2010, at 10:02 AM, Benjamin Bentmann wrote:
>
>> Brett Porter wrote:
>>
>>> I think the original reason the logic is how it is was because just
>>> "SNAPSHOT" (with no leading version) was va
Do you need @aggregator to make sure the reactorProjects is properly populated?
--Brian (mobile)
On Dec 20, 2010, at 12:18 PM, Benjamin Bentmann
wrote:
> Bernd Vogt wrote:
>
>> when implementing a Mojo (Maven 3), how do I get the MavenProject
>> objects of the modules that were already built
Don't go back to a lower version in the parent unless you change one
if the other coords like the artifactid. This causes sorting issues
when the metadata needs to be rebuilt.
--Brian (mobile)
On May 6, 2010, at 4:29 PM, Hervé BOUTEMY
wrote:
ok
i'll do the svn update and open a Xircle
+1
--Brian (mobile)
On Apr 10, 2010, at 4:40 AM, Jason van Zyl wrote:
Hi,
This was simply to bump the default source/target to 1.5. I don't
want 3.0-beta-1 released requiring people to set these as they
should be defaults now.
Staging repo:
https://repository.apache.org/content/reposi
+1
--Brian (mobile)
On Feb 8, 2010, at 8:06 AM, Olivier Lamy wrote:
Hi,
I'd like to release maven-checkstyle-plugin version 2.5.
It's a small release to make it working with maven 3.
We solved 1 issue:
http://jira.codehaus.org/browse/MCHECKSTYLE-123
Staging repo:
https://repository.apache
All joking aside, 2.0.9 and 2.0.10 have proven to be very stable. We
need to keep the same bar for 2.0.11 especially if we intend this to
be the end of 2.0.x. That means we need lots of participation during
the rc process.
--Brian (mobile)
On Nov 20, 2009, at 4:23 PM, Brett Porter wrote:
re be an apache 7 pom or, how else would we get
this new functionality?
thanks
david jencks
On May 7, 2009, at 8:13 PM, Brian E. Fox wrote:
I just need to finish the ITs.
--Brian (mobile)
On May 7, 2009, at 10:45 PM, Stephane Nicoll > wrote:
On Tue, May 5, 2009 at 3:21 AM, Bret
I just need to finish the ITs.
--Brian (mobile)
On May 7, 2009, at 10:45 PM, Stephane Nicoll
wrote:
On Tue, May 5, 2009 at 3:21 AM, Brett Porter wrote:
On 05/05/2009, at 11:01 AM, Brian Fox wrote:
To make this happen relatively quickly, I'll take finish my patch by
adding tests, and
-1 we need to produce source archives for all releases based on the
recent discussions on some other lists. I'm experimenting with some
ways to make this inherited but for now you can bind the assembly
plugin with the src descriptor to produce the correct zip of the
sources.
--Brian (mobi
I will take a look shortly
--Brian (mobile)
On May 1, 2009, at 4:59 PM, Arnaud HERITIER wrote:
I'm not administrator to verify but perhaps, the job to fix metadata
isn't
scheduled ?
On Fri, May 1, 2009 at 6:09 PM, Nord, James wrote:
Hi all,
The metadata served by nexus for http://repo
+1
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Friday, April 10, 2009 3:59 PM
To: Maven Developers List
Subject: Re: [VOTE] Release mercury-1.0-alpha-6
+1
I didn't see this vote at first because for some reason my email client
thought it was part of the al
mal module dependency?
On Apr 3, 2009, at 10:14 AM, Brian E. Fox wrote:
> It's because a plugin may have a defacto dependency based on something
> in its configuration. Maven won't know about this so if that dep is in
> the same reactor, it may not be ordered correctly. The depen
It's because a plugin may have a defacto dependency based on something
in its configuration. Maven won't know about this so if that dep is in
the same reactor, it may not be ordered correctly. The dependency:copy
is an example of this. There should be a way for a plugin to participate
in the reacto
No, it hasn't changed. This won't happen until 3.x when there is the
ability for a plugin to introspect the build plan pre-execution.
-Original Message-
From: James Carpenter [mailto:nawk...@gmail.com]
Sent: Friday, April 03, 2009 12:11 PM
To: dev@maven.apache.org
Subject: Is it now possi
hanks,
--
Olivier
2009/3/28 Olivier Lamy :
> I can see the artifacts on central now.
>
> Thanks Brian !
>
> --
> Olivier
>
> 2009/3/28 Brian E. Fox :
>> It's in the process of syncing to central now.
>>
>> -Original Message-
>> From: oliver.
All set.
-Original Message-
From: Niall Pemberton [mailto:niall.pember...@gmail.com]
Sent: Saturday, March 28, 2009 5:52 PM
To: Maven Developers List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
The parent pom doesn't seem to have found its way to the public repo
yet, is i
It's in the process of syncing to central now.
-Original Message-
From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of
Olivier Lamy
Sent: Saturday, March 28, 2009 3:42 AM
To: Maven Developers List; scm-...@maven.apache.org
Subject: Re: [RESULT] [VOTE] Release Maven Rele
Ok I just wasn't sure because there was lots of talk about eclipse
plugin fixes in parallel so I lost track.
-Original Message-
From: Barrie Treloar [mailto:baerr...@gmail.com]
Sent: Friday, March 27, 2009 2:52 AM
To: Maven Developers List
Subject: Re: Re : Re : [VOTE] Release Maven eclip
Has this vote been officially cancelled?
-Original Message-
From: Julien HENRY [mailto:henr...@yahoo.fr]
Sent: Tuesday, March 24, 2009 11:27 AM
To: Maven Developers List
Subject: Re : Re : [VOTE] Release Maven eclipse plugin version 2.6
Done:
http://jira.codehaus.org/browse/MECLIPSE-53
It looks like a hardware tracking / provisioning tool not a build system.
Shrug. Not related to Apache Maven at all it appears to me.
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Thursday, March 26, 2009 2:19 AM
To: Maven Developers List
Subject: Maven Enterprise
l you...the
console output you included really isn't much to go on.
Sorry,
-john
Brian E. Fox wrote:
> I tried a build with -N (non recursive) and I get an error with 2.1.0:
>
>
>
> [INFO] Parent pr
List
Subject: Re: Recording build environment
That's true, I can get the OS and Java version from standard properties,
and
then put them in the Manifest or somewhere else. Is there a property
that
contains the current running version of maven?
Brian E. Fox wrote:
> It seems like if th
I tried a build with -N (non recursive) and I get an error with 2.1.0:
[INFO] Parent project loaded from repository.
[INFO]
[ERROR] BUILD ERROR
[INFO]
It seems like if there were some properties available, or known to the
resources plugin, then you could filter these values in anywhere you
wanted them.
-Original Message-
From: Paul Gier [mailto:pg...@redhat.com]
Sent: Wednesday, March 25, 2009 11:54 AM
To: Maven Developers List
Subject:
>don't forget to use the new snapshot repository
>http://repository.zones.apache.org/content/groups/snapshots/
The correct url is http://repository.apache.org/snapshots/
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
The enforcer uses this to hand components over to the rules via a get
Component method (it implements the expressionevaluator interface). I
would probably need to convert all the rules over to actual plexus
components to use injection.
-Original Message-
From: Jason van Zyl [mailto:jvan...
+1 I tested briefly against 2.0.x build with various values of parallel
downloads and everything seems ok.
-Original Message-
From: Arnaud HERITIER [mailto:aherit...@gmail.com]
Sent: Friday, March 20, 2009 2:07 PM
To: Maven Developers List
Subject: Re: [vote] Maven 2.1.0
+1
Arnaud
On Fr
The issue is resolved so you can go ahead and release.
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Wednesday, March 18, 2009 12:36 PM
To: Maven Developers List
Subject: Maven release...in progress
Hi,
I just wanted to let everyone know that I'm currently in
I'll write some docs to cover this for Apache globally, but iirc there
weren't docs before for p.a.o, so the current docs have to be better
than what was there previously.
Each project presumably has their own release docs similar to what we
have for Maven that I've pointed projects to as they mi
David, the process to migrate the process is covered here:
https://issues.apache.org/jira/browse/INFRA-1896
The usage docs for the Maven release process covers everything else once
you are setup:
http://maven.apache.org/developers/release/releasing.html
-Original Message-
From: David Jenc
my-classes/
it/alt-src-output-directori
Yeah, it probably could be done like that. But it seems a little
strange way to
accomplish it.
Also that would put all the output into a single directory, and I would
prefer
to keep the classes separate in the output.
Brian E. Fox wrote:
> Can you do it
com.my.pacakge
--
However it only appears to work if the two
maven-metadata-local.xml
files exist otherwise the short-hand or non-specific-version
invocations fail.
Any thoughts?
thanks in advance.
Kaveh.
Brian E. Fox wrote:
> In order for maven to look in the ri
t
are compiled differently and then output to different locations. For
the main
sources it's not as much of an issue.
Brian E. Fox wrote:
> Why doesn't the buildhelper plugin work for this use case? That lets
you
> attach many source folders.
>
> -Original Mess
Yes, we are fixing it now.
-Original Message-
From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier
Lamy
Sent: Friday, March 13, 2009 5:26 AM
To: Maven Developers List
Subject: Fwd: maven-site-plugin pre 2.0 not in maven-metadata.xml
Hi,
First sorry for cross po
In order for maven to look in the right place for the shorthand lookup,
you need to add a pluginGroup in your settings. By default, maven only
uses org.apache.maven.plugins and org.codehaus.mojo.
-Original Message-
From: Kaveh Goudarzi [mailto:ka...@itkaa.com]
Sent: Friday, March 13, 200
Why doesn't the buildhelper plugin work for this use case? That lets you
attach many source folders.
-Original Message-
From: Paul Gier [mailto:pg...@redhat.com]
Sent: Friday, March 13, 2009 2:58 PM
To: Maven Developers List
Subject: Re: svn commit: r753302 - in
/maven/plugins/trunk/maven
As an addendum to the meetup, we're also going to conduct a keysigning
party. For more information about a key signing party, take a look at
these excellent documents for how the ApacheCon party runs:
http://wiki.apache.org/apachecon/PgpKeySigning
Note, that this requires a tiny bit of preparation
If it's about developing archetypes, otherwise the user list will have
quicker responses.
-Original Message-
From: Derek Chen-Becker [mailto:j...@chen-becker.org]
Sent: Thursday, March 12, 2009 4:38 PM
To: dev@maven.apache.org
Subject: Is this the place for archetype questions?
I have a
You could use the Nexus UI to upload it directly, or if you need to
automate you could use the REST api.
-Original Message-
From: Olivier Billard [mailto:olivier.bill...@gmail.com]
Sent: Thursday, March 12, 2009 7:57 AM
To: dev@maven.apache.org
Subject: [Maven Deploy Plugin] Add consisten
I would change the tag.
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Wednesday, March 11, 2009 8:22 AM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.1.0-RC1
Mistake on my part. I realized it when I started working on the bugfixes
described in
Nope, go ahead. The enforcer applies also.
-Original Message-
From: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu]
Sent: Tuesday, March 10, 2009 3:36 AM
To: Maven Developers List
Subject: Migrate Maven Dependency Plugin to use Invoker Plugin for ITs
Hi,
This is mostly a question t
+1
-Original Message-
From: Lukas Theussl [mailto:ltheu...@apache.org]
Sent: Monday, March 09, 2009 6:31 AM
To: Maven Developers List
Subject: [vote] promote pdf plugin
Hi,
With Doxia 1.1 released, I'd like to promote the pdf plugin out of the sandbox
so
we can release it. Snapshot i
Ibiblio only gets updated once a day starting at 1am CST, so every 2 hours is
overkill. You could wait until 2am CST and then pull your copy.
-Original Message-
From: Mirror-Service [mailto:mirror-serv...@netcologne.de]
Sent: Thursday, March 05, 2009 3:11 AM
To: dev@maven.apache.org
Subj
1:35 PM
To: Maven Developers List
Subject: Re: MPIR 2.3-snapshot
On 05/03/2009, at 1:39 PM, Brian E. Fox wrote:
> No, I mean, why do we need to set the prereq...i understand how it
> works
> ;-)
> Can we work it so a prereq isn't needed is the question.
Agree (and it should be p
Maven Developers List
Subject: Re: MPIR 2.3-snapshot
On 05/03/2009, at 2:29 AM, Brian E. Fox wrote:
> Everytime I build a site, I run into this and I have to go lockdown
> the
> report. This is going to cause massive headaches when this gets
> released. It would be nice if Maven could see
Is there a way to avoid requiring 2.1.0-M2 for the mpir 2.3 snapshot?
[INFO] snapshot
org.apache.maven.plugins:maven-project-info-reports-plugin:2.3-SNAPSHOT:
checking for updates
from central
[INFO]
[ERROR] BUILD ERROR
Ok, The doxia tools are restaged here:
https://repository.apache.org/content/repositories/maven-staging-4cc3f47
d7847b8/
+1 (procedural checking, I didn't test them directly, but I did rebuild
the tools and it was ok)
-Original Message-
From: Brian E. Fox [mailt
-1, the doxia tools release isn't signed:
https://repository.apache.org/content/repositories/maven-staging-4c838f3
8e6b44b/org/apache/maven/doxia/doxia-converter/1.0/
The others looked ok.
-Original Message-
From: vincent.sive...@gmail.com [mailto:vincent.sive...@gmail.com] On
Behalf Of
The more this thread goes on, the less optimistic I feel about this going into
2.1. We already know the 2.1M1 is stable and the point was to get it out in a
release that people can use, ie non-milestone. Making radical changes at the
last minute is not good for stability and not good for the use
>1.1 is NOT under development anymore, it hasn't been for at least over a year.
>All
>we did was small bug fixes and enhancements that came along on the way because
>there was nothing else to do.
I don't follow this logic, if it's been done for over a year, why has it been
discussed for the la
>I'm venting because I'm a little frustrated that this conversation came
>up back in August and here we are talking about it again...and again,
we
>have no released version of Doxia to consume. So, we're in a position
of
>rushing out a release of Doxia so we can push an unproven dependency
>in
Yeah double it up to reduce the overall timeline.
-Original Message-
From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett
Porter
Sent: Monday, March 02, 2009 5:57 AM
To: Maven Developers List
Subject: Re: decision on Doxia for 2.1.0?
On 02/03/2009, at 9:45 PM, Vincent Sive
Seems logical to me. I don't know why there are these special mappings
in the first place. Sources is the other one that comes to mind... if
true you should handle that the same.
-Original Message-
From: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu]
Sent: Sunday, March 01, 2009 9:1
When can we get 1.1? I think 2.1.0 is essentially ready to go now.
-Original Message-
From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Sent: Sunday, March 01, 2009 2:44 PM
To: Maven Developers List
Subject: Re: decision on Doxia for 2.1.0?
We made tests with Vincent today and found lit
Maybe it's waiting for the password?
-Original Message-
From: Stephane Nicoll [mailto:stephane.nic...@gmail.com]
Sent: Sunday, March 01, 2009 10:57 AM
To: Maven Developers List
Subject: stuck on gpg:sign while staging ear plugin
Hey guys,
I am trying to stage EAR plugin 2.3.2 before cal
Plexus is a codehaus component, so Apache would most likely not have these
checks.
-Original Message-
From: Abel Muiño [mailto:amu...@gmail.com]
Sent: Friday, February 27, 2009 1:18 PM
To: dev@maven.apache.org
Subject: Code provenance checks for Plexus components
The Eclipse legal team
7;t need to go into the core, I think a plugin is better.
I was thinking about GUI in the plugin - that way we either go by
-Dsettings-master-password and -Dsettings-server-password or have the
same options available via swing GUI
Thanks,
Oleg
>
> On 26-Feb-09, at 6:22 AM, Brian E. Fox wrot
That doesn't negate the need for an issue and some tracking of these
changes.
-Original Message-
From: Shane Isbell [mailto:shane.isb...@gmail.com]
Sent: Thursday, February 26, 2009 1:57 PM
To: Maven Developers List
Subject: Re: svn commit: r748226 - in
/maven/components/trunk/maven-proje
+1 for no abbreviations. We have enough crazy options to memorize on the
cli as it is. (ie is it maven.tests.skip or maven.skip.tests?)
-Original Message-
From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett
Porter
Sent: Thursday, February 26, 2009 8:52 AM
To: Maven Develope
Results:
Binding: +7 Brian, Jason, Arnaud, Lukas, Vincent, Olivier, Brett
Non binding: +3 Jason Dillon, Oleg, Nicolas
I'll publish the sites and artifacts now.
-Original Message-
From: Brian E. Fox [mailto:bri...@reply.infinity.nu]
Sent: Sunday, February 22, 2009 10:20 PM
To:
Yes, they are ASL.
-Original Message-
From: Abel Muiño [mailto:amu...@gmail.com]
Sent: Tuesday, February 24, 2009 1:58 PM
To: dev@maven.apache.org
Subject: License for maven 3.0 artifacts
I have not been able to get information about these two artifacts (transitive
dependencies of the m
Time to release a beta with a few bug fixes:
Release Notes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14948&styleName
=Html&projectId=11530&Create=Create
Staged site:
http://people.apache.org/~brianf/staging/people.apache.org/www/maven.apa
che.org/enforcer/
Artifacts S
Okay that fixes the issue.
Thanks,
Stéphane
On Sun, Feb 22, 2009 at 6:57 PM, Brian E. Fox wrote:
> We don't yet have an official cert from infra yet (INFRA-1891). So you need
> to install the current cert, see http://repository.apache.org/ssl for
> instructions. The rest of the inf
that file in
repo1 using the nexus index.
talked with tamas some weeks ago to add this feature (the automatic
creation of the catalog in repo1)
WDYT?
Ragards,
Raphaël
2009/2/21 Brian E. Fox
> [WARNING] Error reading archetype catalog http://repo1.maven.org/mav
164123-1.jar
>
> Thanks,
> Stéphane
>
>
>
> On Sun, Feb 22, 2009 at 2:10 AM, Brian E. Fox wrote:
>
>> The Maven project has recently moved to a new repository within the
>> Apache infrastructure. The repository that was previously at:
>> http://people.
The Maven project has recently moved to a new repository within the
Apache infrastructure. The repository that was previously at:
http://people.apache.org/repo/m2-snapshot-repository is deprecated. All
new snapshots are being deployed to
http://repository.apache.org/snapshots . Note that this is a
[WARNING] Error reading archetype catalog http://repo1.maven.org/maven2
org.apache.maven.archetype.source.ArchetypeDataSourceException: Error
parsing ar
chetype catalog.
at
org.apache.maven.archetype.source.CatalogArchetypeDataSource.readCata
log(CatalogArchetypeDataSource.java:202)
is still one feature missing: automatic blame when reports get worse on
> a commit. I didn't find anything like this.
>
> Regards,
>
> Hervé
>
>
> [1] http://wiki.hudson-ci.org/display/HUDSON/Violations
>
> [2] http://wiki.hudson-ci.org/display/HUDSON/Static+Cod
[vote] release asf/maven/maven-plugins/maven-shared poms
Yep, looks fine now
+1
Brian E. Fox wrote:
> Grrr. It's fixed now:
>
https://repository.apache.org/content/repositories/maven-staging-493287f
> 5223d96/org/apache/maven/plugins/maven-plugins/13/
>
> FWIW, the release
Best to wait, I just fixed the issues you found, if you change your
vote, we can release them, it's been 72hrs.
-Original Message-
From: Dennis Lundberg [mailto:denn...@apache.org]
Sent: Friday, February 20, 2009 6:49 PM
To: Maven Developers List
Subject: Release/staging question
Hi
I'm
the same in
the staged POM.
Still -1 I'm afraid
The staged POM for shared also has an section that points to
trunk.
-1
Brian E. Fox wrote:
> Dennis, can you take another look and hopefully update your vote?
>
> -Original Message-
> From: Dennis Lundberg [mailto:denn.
maven-plugins POM after a quick glance.
It still has a SNAPSHOT version on the tag
http://svn.apache.org/viewvc/maven/plugins/tags/maven-plugins-13/pom.xml
?revision=745340&view=markup
Brian E. Fox wrote:
> New parents need to be released with the new distributionManagement
> sections
yle report for the
current artifact.
Brian E. Fox wrote:
> Why don't we just hookup checkstyle to maven?
>
> -Original Message-
> From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
> Sent: Thursday, February 19, 2009 7:08 PM
> To: dev@maven.apache.org
> Subject:
Why don't we just hookup checkstyle to maven?
-Original Message-
From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Sent: Thursday, February 19, 2009 7:08 PM
To: dev@maven.apache.org
Subject: Re: svn commit: r746002 - in /maven/components/trunk:
maven-core/src/main/java/org/apache/maven/
It's fixed now. The problem was I fixed org/hibernate/* before not
/hibernate. Anyone know why these same files exist in both paths?
-Original Message-
From: Brian E. Fox [mailto:bri...@reply.infinity.nu]
Sent: Thursday, February 19, 2009 6:23 PM
To: Maven Developers List
Subjec
artefacts on central repo
which will be launched after each rsync ?
it's a possibility if it's not too long to repair all rigths.
On Thu, Feb 19, 2009 at 11:46 PM, Brian E. Fox
wrote:
> I'll just put a script to fix all the permissions?
>
> -Original Message-
&view=markup
Brian E. Fox wrote:
> New parents need to be released with the new distributionManagement
> sections pointed at repository.apache.org:
>
> Apache Pom Diffs:
>
http://svn.apache.org/viewvc/maven/pom/tags/apache-5/pom.xml?r1=639584&r
> 2=745325&di
I'll just put a script to fix all the permissions?
-Original Message-
From: Arnaud HERITIER [mailto:aherit...@gmail.com]
Sent: Thursday, February 19, 2009 5:33 PM
To: Maven Developers List
Subject: Re: Permission denied to access some artefacts on central repo
Jason,
I reported the issu
Just testing the wrapping problem I seem to have:
http://repository.apache.org/snapshots/org/apache/asyncweb/asyncweb-spri
ng/maven-metadata.xml
-Original Message-
From: Brian E. Fox [mailto:bri...@reply.infinity.nu]
Sent: Wednesday, February 18, 2009 2:37 PM
To: Maven Developers List
Seems to be proxying just fine:
http://repository.apache.org/snapshots/org/apache/asyncweb/asyncweb-spri
ng/maven-metadata.xml
http://repository.apache.org/snapshots/org/apache/maven/maven-project-bu
ilder/3.0-SNAPSHOT/maven-metadata.xml
-Original Message-
From: Brian E. Fox [mailto:bri
As far as I know, I've been using it but haven't cleared my repo. If you
browse it's only going to show stuff that has been proxied, not the entire
contents of p.a.o.
On 2/18/09 10:41 AM, "Brett Porter" wrote:
>
> On 15/02/2009, at 2:05 AM, Brian E. Fox wrote:
New parents need to be released with the new distributionManagement
sections pointed at repository.apache.org:
Apache Pom Diffs:
http://svn.apache.org/viewvc/maven/pom/tags/apache-5/pom.xml?r1=639584&r
2=745325&diff_format=h
Staged at:
https://repository.apache.org/content/repositories/staging-48
Developers List
Subject: Re: [VOTE] Release Maven Doxia version 1.0
Thanks Brian.
I'm reading up on the new repo as we speak.
Brian E. Fox wrote:
> I'll copy the artifacts to a staging repo for you tonight and then you
can
> promote it when the vote is closed.
>
>
> On
gt;
> Brett Porter wrote:
>> So, there seems to be some agreement.
>>
>> However, I've come back from underground and now there are *two*
>> snapshots on trunk. I'm already spending valentine's day alone, so I
>> didn't really need another reason to c
I'll copy the artifacts to a staging repo for you tonight and then you can
promote it when the vote is closed.
On 2/17/09 1:25 PM, "Dennis Lundberg" wrote:
> +1 from me
>
> Dennis Lundberg wrote:
>> Hi,
>>
>> (resending due to SMTP-server problems)
>>
>> The time has finally come to release
alentine's day alone, so I
> didn't really need another reason to curl up in the corner and cry :)
>
> I would really like to pull an M2 release in the next week with the
> stuff that is already there. John, what do you think?
>
> Thanks,
> Brett
>
> On 10/02/200
: Brian E. Fox [mailto:bri...@reply.infinity.nu]
Sent: Monday, February 09, 2009 11:32 PM
To: Maven Developers List
Subject: [vote] release maven 2.0.10
It's finally time after 8 Release Candidates:
Issues fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleN
All set
-Original Message-
From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Sent: Sunday, February 15, 2009 10:47 AM
To: dev@maven.apache.org
Subject: karma on grid.sonatype.org
I used to have karma on ci.sonatype.org to read and modify project
configuration.
Can someone give me karma
What benefits in 2.1 would we get by upgrading?
-Original Message-
From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Sent: Sunday, February 15, 2009 11:15 AM
To: dev@maven.apache.org
Subject: use Modello 1.0 in Maven 2.1.x
Maven 3.x recently upgraded Modello to 1.0 in r743174, and Ben
opers List
Subject: Re: [PROPOSAL] Start using bugtraq in our subversion repository
I wasn't aware that you could use it as a reminder. Would that require
some pre-commit hooks to work?
Brian E. Fox wrote:
> You can regexp the comment to make sure every comment has an issue in
> it, and you
09 at 7:03 AM, Brett Porter wrote:
> ++1
>
> I ran the integration tests as confirmation.
>
> On 10/02/2009, at 12:32 PM, Brian E. Fox wrote:
>
>> It's finally time after 8 Release Candidates:
>>
>>
>>
>> Issues fixed:
>>
>>
http:/
>I do like the hook to get people to actually use the parent POM, but
>at the same time it feels back to front (We probably don't need
>another pom release, but if we did that would then have to be a
>fork...). What about having them use the properties as their distMgmt
>settings for now?
>Isn't modifying the ASF POM premature? I'm not sure if other projects
>are using the POM or not (they should be), but they may not be using
>this system.
There are a few other projects looking to use the new structure and this
would make it easier for them to do. Projects not using the new
+1
-Original Message-
From: Oleg Gusakov [mailto:oleg.subscripti...@gmail.com]
Sent: Wednesday, February 11, 2009 12:58 AM
To: Maven Developers List
Subject: [VOTE] Release mercury-1.0-alpha-5
Hi,
Main reason for this release - bug fixes. A lot of testing done on the
repository side, I
You can regexp the comment to make sure every comment has an issue in
it, and you can tweak the dialog so it has a prompt for the issue.
Otherwise it doesn't do much else that I recall...it's just an
aid/reminder to get the issue in the comment.
-Original Message-
From: Benjamin Bentmann [
1 - 100 of 1530 matches
Mail list logo
