> The first question was redundant - you'd already said you wanted to update
> snapshots and the other option is failure. The second one assumes you'll be
> setting the snapshot to the equivalent release, then automatically to the
> next dev't version. The inflexibility of the first part was poi
The enforcer seems like the logical place to do this. Then it could be
added to a release profile if someone wants it only in a release., but
many would want this all the time.
On Fri, Sep 24, 2010 at 11:32 AM, Nicholas Neuberger
wrote:
> First I want to say, I hope this is not the wrong mailing
Scraping the repo will get you banned. Get a repo manager instead.
Sent from my iPad
On Sep 21, 2010, at 9:52 PM, Fabien Renaud wrote:
> Hi,
>
> Few month ago (in July), I tried to download (for work) the Maven Repository
> with my home PC but after a couple of hours, I was banned!
> Now I need
I'm at JavaOne this week so I didn't see this until know. You're back
in the group now.
On Mon, Sep 20, 2010 at 12:07 PM, Mark Hobson wrote:
> On 20 September 2010 16:43, Wendy Smoak wrote:
>> (If Brian hasn't seen this thread and done it already,) send an email
>> to the PMC list private@ and a
"This is actually happening because of a snapshot version metadata
change that went out with maven 3 beta 3, so if folks used that to
deploy, the metadata will be unreadable by nexus versions 1.7.2 and
earlier.
However, we do have a patch that can be applied. Just drop the
following jar in your (
Stephen has just joined us on the Maven PMC. He is the author of the
very popular versions-maven-plugin at Codehaus and has recently been
doing maintenance of the Surefire plugin at the Maven project.
Welcome Stephen!
--Brian Fox
Maven PMC Chair
Those were some pending changes I had that just never got deployed.
Most of that content was out dated and duplicated. I'm trying to
maintain a single source of all the central related documentation to
keep everything in sync. So far all of the forge docs and now the
Maven guide all point to or com
er.
>
Fine with me. Then lets announce that intention to the user list now
and get the page updated to make it easy for people to find the betas.
> On Sep 2, 2010, at 7:34 PM, Brian Fox wrote:
>
>> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty
>> safely
ht the subject up I don't seem to see any traction or
> replies/discussion come along, is there room to address this somehow?
>
> --
> Pull me down under...
>
> On Fri, Sep 3, 2010 at 11:34 AM, Brian Fox wrote:
>
>> Now that Maven 3 beta 3 is out with Guice and Aether,
> When 3.0 is released, is 2.2 pretty much a dead branch? I have no
> problem with that btw :-)
Isn't it essentially dead now?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@m
On Thu, Sep 2, 2010 at 8:40 PM, Barrie Treloar wrote:
> On Fri, Sep 3, 2010 at 9:04 AM, Brian Fox wrote:
>> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty
>> safely call it feature complete. I'd like to propose a few goals to
>> get some things done
Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty
safely call it feature complete. I'd like to propose a few goals to
get some things done. We have ApacheCon coming up the first week of
November, and it would be great to set that as a target to get Maven
3.0 out the door.
So far
This is a little delayed, but still deserved. A few weeks ago,
Kristian joined us on the Maven PMC. He's been driving a lot of
interesting work in Maven 3 to support parallel builds. If you haven't
tried that out yet, please do and send some feedback.
Welcome Kristian!
--Brian Fox
Plus 1. (just discovered the "plus" key on my board is broken)
On Mon, Aug 30, 2010 at 9:09 AM, Benjamin Bentmann
wrote:
> Hi,
>
> what's a better start for a week than a new fresh release :-) ? So here we
> go!
>
> Apart from another few regression fixes, this release includes Guice and
> Ae
On Thu, Aug 26, 2010 at 12:39 PM, Rex Hoffman wrote:
> Baptiste:
>
> I work in a large organization, where there are differing degrees of
> familiarity with maven.
> Most devs shy away from the release plugin for several reasons. One
> is the use of hudson and nexus.
>
I actually wrote those rul
Yes, these are useful rules, although we have some that sound the
same, but maybe there's a subtle difference?
http://maven.apache.org/enforcer/enforcer-rules/requireReleaseDeps.html
http://maven.apache.org/enforcer/enforcer-rules/requireReleaseVersion.html
On Wed, Aug 25, 2010 at 6:26 PM, Rex Ho
Nexus has REST urls to let you retrieve the latest snapshot from a
deterministic url: http://nexus.sonatype.org/nexus-faq.html#25
On Mon, Aug 16, 2010 at 6:16 AM, ni...@codefresh.com
wrote:
> Hi,
>
> I've noticed that the uniqueVersion attribute of the release plugin is
> effectively ignored for
This was done so that plugins could use their own version of p-u and
not have a class path conflict with the version used in core
Sent from my iPad
On Aug 13, 2010, at 10:35 AM, Martin Gainty wrote:
>
> Good Morning Devs-
>
> I needed to rebuild maven-shared-components which references plexus-u
use http instead of https
On Tue, Aug 10, 2010 at 1:04 PM, Steffen Stundzig wrote:
> hi,
>
> thanks igor. For the second I need a login. Do you have a guest account
> or something else?
>
> regards
>
> Am 10.08.10 18:46, schrieb Igor Fedorenko:
>> You may want to check how we do this in m2eclipse
+1 works great on the projects I tested.
On Sat, Aug 7, 2010 at 7:16 AM, Benjamin Bentmann
wrote:
> Hi,
>
> We solved 28 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=16090
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/
I'm not so concerned about confusing users with a beta2 and then a
beta3, that can be mitigated easily in the announcement. More releases
won't hurt anyone.
Let those working on it decide what to do and when presented with a
vote, I'll test, verify and vote accordingly, regardless of if it's
beta
2010/8/5 Arnaud Héritier :
> Ok,
>
> Thus talking is good but doing is better ( I know I'm talking more than I'm
> doing :-) )
>
> Could we have a consensus if we :
> - release now the trunk as a beta 2 without Guice and Aether. With that
> we'll have a solid base to compare future changes wit
>
> The first thing I would like to happen is that we release 3.0-beta-2
> *without* merging the proposed code. There are two reasons for this.
Lets stage them both, I don't see any harm in having them back to
back, it certainly could help isolate any regressions.
Anyone can vote. The community vote is certainly important, but
official Apache policy requires a minimum of 3 PMC +1's.
On Wed, Aug 4, 2010 at 6:56 PM, Mark Derricutt wrote:
> +1 from me - I assume us joe-shmoe users can vote?
>
> --
> Pull me down under...
>
> On Wed, Aug 4, 2010 at 10:11 PM,
> I find your pronouncement that it won't be here very troubling since you only
> have a single vote just as every other committer does.
>
Knowing you in person, I'll take the above with a grain of salt that
maybe it's not exactly what you meant. However my first reading of
this was alarming.
Pe
>
>
> Our ITs say the codebases behave in an equivalent fashion, but it's the
> Aether/Guice changes that will be with us for the long >haul. I would rather
> wait to integrate those in order to suss out problems that may be a result of
> that integration.
I think you meant you would rather _no
A lot of people seem to have the gpg plugin hang during release
perform. It's never happened to me so I haven't dug into the root
cause, if it's release or gpg...but that's the only thing that
immediately comes to mind.
On Thu, Jul 29, 2010 at 7:01 PM, Brett Porter wrote:
> Several folks seem int
On Tue, Jul 27, 2010 at 12:09 AM, Barrie Treloar wrote:
> On Tue, Jul 27, 2010 at 3:04 AM, Brian Fox wrote:
>> I finally crossed off a todo that was about 12 months old:
>>
>> I synthesized the various docs we had laying around to produce a
>> generic Apache wide re
I assumed we had it deploying via ci, sorry about that.
On Mon, Jul 26, 2010 at 5:10 PM, Dennis Lundberg wrote:
> Please make sure that a SNAPSHOT is released when you start to use it.
> I've deployed maven-parent 17-SNAPSHOT now.
>
> On 2010-07-25 01:07, bri...@apache.org wrote:
>> Author: brian
I finally crossed off a todo that was about 12 months old:
I synthesized the various docs we had laying around to produce a
generic Apache wide release procedure for publishing Maven based
artifacts via the repository, and updated our Maven Project specific
docs at the same time. These new docs ca
Was this a mistake or do you want to go Emeritus?
On Tue, Jun 22, 2010 at 5:23 AM, wrote:
> Author: nicolas
> Date: Tue Jun 22 09:23:13 2010
> New Revision: 956833
>
> URL: http://svn.apache.org/viewvc?rev=956833&view=rev
> Log:
> updated developers list
>
> Modified:
> maven/pom/trunk/maven/
If you're using the nexus api, then this belongs in the
nexus-maven-plugin, not the maven-dependency-plugin.
On Mon, Jun 21, 2010 at 8:39 AM, nicolas de loof
wrote:
> I tried to write an alternate implementation of MDEP-269 using nexus indexer
> API, based on samples found on sonatype blog.
>
> I
repo1.maven.org (aka Maven Central) syncs org.apache.* from
repository.apache.org so all of your releases will be synced to
Central automatically. The sync runs every 4 hours.
On Fri, Jun 18, 2010 at 11:05 PM, Gabriele Columbro wrote:
> Dear Mavens,
> cross-posting this to the Chemistry [1] Dev l
While trying to debug some nexus-maven-plugin issues, I came across
some differences in the help:effective-settings output between 2.2.1
and 3.0-b1. Is this expected? Note that in both cases the properties I
have defined in my settings are not shown.
>From Maven 3:
http://maven.apache.org/POM/4.
Is there some plugin in your build that is forking the whole build?
On Wed, Jun 2, 2010 at 10:29 AM, Alan D. Cabrera wrote:
> I have a root POM that defines are deploy profile that generates source,
> javadoc, and signing.
>
> When I use this profile:
>
> mvn clean install -P deploy
>
> My artif
It's not designed to work that way. It could be changed, but the
effort involved isn't really worth it.
On Wed, Jun 2, 2010 at 8:18 AM, timonik wrote:
>
> I processed mvn clean install and now it works fine.
> But, have I chance use depenedency:tree goal without project installation in
> local re
I moved codehaus over to the more frequent sync but had a typo in
there. It's running every 4 hours now in conjunction with Apache.
On Sun, May 23, 2010 at 4:19 AM, Stephen Connolly
wrote:
> The sync seems not to have happened since at least 1am GMT+1h Saturday ...
> shoud see v-m-p version 1.2 i
.html
--Brian Fox
Maven PMC Chair.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
>
> Actually I am an Apache Tiles PMC member, can I fork it in the sandbox?
Nexus is doing a lot more at Apache than just copying and merging xml
files. It's also doing basic sanity checks on the pom, signatures,
etc. It no longer requires you to care about file based permissions
and lots of other
Sat, Jan 16, 2010 at 1:02 PM, Dan Tran wrote:
>> Hi Brian,
>>
>> Great, i am looking forward to see the snapshots deployed soon.
>>
>> Should I ping you after few days I dont see them?
>>
>> Big Thanks
>>
>> -Dan
>>
>> On Fri, Ja
> MavenProject.getOriginalModel() for the raw model, i.e. as read from the
> mere pom.xml.
The current pom only or with inheritence? The latter would usually be
more handy. In the enforcer I would need to get the original poms, but
having inheritence baked in would save me from walking the tree an
Clearly she doesn't read this list or she would have known by now to
stop doing that. Should we just unsub her?
On Tue, May 4, 2010 at 1:57 PM, Martin Gainty wrote:
>
> i dont know if they have internet there yet but you *might* want to check her
> dacha outside of moscow
>
> Martin Gainty
> ___
Possibly if we introduce a pom that has the exact internal model maven
generates when it can't find one. This could cause some issues for
people who have their own versions of those poms.
On Mon, May 3, 2010 at 2:05 PM, Paul Gier wrote:
> Jason van Zyl wrote:
>> On May 3, 2010, at 12:10 PM, Benja
> Seems to me that the first step is to prevent any new files being
> added to central unless they have valid hashes and signatures to stop
> the problem getting worse - or has that already been done?
This is being done. The signatures are checked, but the hashes
currently aren't. That's a trivial
2010/4/27 Arnaud Héritier :
> It could be better but far from perfect. Few users are reading this file and
> are using it to create their own.
> I think they are often copying it from the page you pointed.
> There are several annoying things about settings from my point of view but
> we won't be ab
I assume you want to make it easier for people to get the correct
settings? Moving it from the super pom could have unexpected side
effects, but what if we put the default "boiler plate"[1]
configuration for that into the default settings.xml commented out? I
think this would solve the main visibil
Use Nexus and run rebuild maven metadata.
On Mon, Apr 26, 2010 at 11:56 AM, sebb wrote:
> What is the recommended procedure for fixing hash files in a Maven
> repo that have the wrong syntax?
>
> For example:
>
> file.tar.gz.sha1:
> file.tar.gz: B886 07FA D17D 06C2 7D67 01D6 E7E6 56BB 52F3
>
Benedict wrote:
> Brian,
>
> Then the current situation should be viewed as acceptable? The ".m2"
> directory, although an artifact of Maven 2, continues to be the home
> directory for Maven 3.
>
> Paul
>
> On Thu, Apr 22, 2010 at 12:04 PM, Brian Fox wrote:
>&
> What ramifications could exist if .m2 is the fallback? It would be an
> easy upgrade path. My point is, it's odd Maven 3 has an "m2" user
> directory -- nothing technically incorrect; just a vestigial of
> progress.
Because now every tool that cares about this folder needs to implement
that same
This sounds easy on the maven side, but what are the ramifications for
all the tools that would have to be updated. Is it worth it?
On Thu, Apr 22, 2010 at 11:14 AM, Paul Benedict wrote:
> 3.0-beta-1 being a beta release, it's getting close to GA. I was
> wondering can MNG-4483 be addressed? I do
Ok I think I understand now. The project.build.plugins are searched so
that they would override the pluginGroup metadata for the prefix...AND
all the default plugins are now in project.build.plugins instead of
pluginManagement. This is the bigger change here but the upshot is
that effective-pom now
Last night I was looking at an irc user's pom for a parsing error:
4.0.0
org.lwjgl
lwjgl-linux-64
2.4.2
newdawnsoftware
http://www.newdawnsoftware.com/maven2
net.java.games
jinput
2.0.1
net.java.games
jinput
Lets move to call the next one a final release or at least a beta. We
have too many alphas floating around
2010/4/20 Raphaël Piéroni :
> +1
>
> Tested using Maven 2.2.0
>
> Many thanks to Hervé
>
> Regards,
>
> Raphaël
>
> 2010/4/18 Hervé BOUTEMY
>
>> Hi,
>>
>> We solved 27 issues:
>>
>> http://j
+1 works ok here.
On Mon, Apr 19, 2010 at 2:34 PM, Stephen Connolly
wrote:
> +1
>
> On 19 April 2010 19:12, Jason van Zyl wrote:
>
>> +1
>>
>> Wee!
>>
>> On Apr 19, 2010, at 10:50 AM, Benjamin Bentmann wrote:
>>
>> > Hi,
>> >
>> > We solved 39 issues:
>> >
>> http://jira.codehaus.org/secure/
What project are you a committer on?
On Fri, Apr 16, 2010 at 10:42 PM, Delos wrote:
> Hi,
>
> I'm trying to set up a staging site with "mvn release:perform". The process
> seems blocked when I saw the message below.
>
> [INFO] [INFO] Generating "Dependency Convergence" report.
> [INFO] [INFO] [si
Use or look at the dependency plugin. The copy/unpack goals manually
resolve things to the repo.
On Wed, Apr 14, 2010 at 11:30 PM, Mirko Jahn wrote:
> Hey there,
>
> I am currently trying to manually install an artifact from a remote
> repository into the local repository to do some file operatio
I've often desired some additional logic here that is related and may
side-step this:
Think about how pluginManagement allows you to define something that
only applies once a child pom "mentions" the plugin. Apply the same
logic to an execution, where you could define one ore more default
executio
Since they aren't linked anywhere, they are essentially invisible and
really only helpful to those few devs around here who know they exist.
(Those who really need them least)
2010/3/23 Barrie Treloar :
> On Wed, Mar 24, 2010 at 10:41 AM, Wendy Smoak wrote:
>>
>> On Tue, Mar 23, 2010 at 6:45 PM,
+1
On Thu, Mar 18, 2010 at 4:20 PM, Hervé BOUTEMY wrote:
> Hi,
>
> second try after fixing table fixed column width issue.
>
> We solved 2 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430&version=14888
>
> There are no issues left in JIRA (true!).
>
> Staging repo:
> htt
Which classpath? The order should be as in your Pom followed by Parent
Pom, Grandparent Pom etc.
On Wed, Mar 10, 2010 at 5:14 PM, Vladimir Jigounov wrote:
>
> I'm using maven 2.2.1.
> Order of libraries on classpath does not match order of dependencies in
> pom.xml
> Is there any way to specify o
+1
On Tue, Mar 9, 2010 at 5:55 PM, Benjamin Bentmann
wrote:
> Hi,
>
> We solved 22 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=16087
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=105
+1
On Thu, Feb 11, 2010 at 9:38 AM, Benjamin Bentmann
wrote:
> Hi,
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11431&version=13290
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=114
Does it make sense to create a plugin specifically for annotation processing?
On Sat, Jan 30, 2010 at 3:06 AM, Milos Kleint wrote:
> can I read silence as lazy consensus to add annotation processing to the
> compiler plugin?
>
> Milos
>
> On Mon, Jan 25, 2010 at 2:48 PM, Milos Kleint wrote:
>
>>
Shoving java code into a war project is an antipattern in Maven. Make
a module for the jar and depend upon that with a war and your life
will be better. Shoving it into the incorrect format is guaranteed to
cause you problems with tools that integrate with maven like ides.
On Tue, Feb 2, 2010 at 4
>
> We should endeavour to leave only the build time related plugins being locked
> down. Things like the IDE generating plugins, the site stuff, and archetype
> stuff should all be removed eventually and decoupled from the core entirely.
> We're just making a bigger mess tying all this stuff to
>
> Will the license and headers be changed over before the donation?
Yes.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Just an update: I was waiting for the code to be released so I could
grab a stable tag to put into the ip process. The Nexus 1.5 release
contains the Nexus Indexer 2.0.4 release so that's the code I'll use
to start the process this week.
On Tue, Jan 12, 2010 at 10:24 PM, Brian Fox wr
If it's in the grid, it would be deployed to repository.sonatype.org
and I have rao proxying that maven-snapshot folder. I figured it's
more bandwidth efficient to proxy requested items than to push every
single snapshot from the grid across.
On Fri, Jan 15, 2010 at 12:10 AM, Brett Porter wrote:
Hi Tony,
We are actually in the process of updating the documentation, but
we've decided not to accept new Rsync requests except for forges. For
individual projects, it's simply too much overhead to handle rsyncs
and it isn't scalable, not to mention there isn't a good way to
enforce quality. Inst
The Maven PMC has voted to move forward with the Indexer code
donation. We will need to move next into the ip clearance phase. We
have also voted to add Brian Demers, Damian Bradicich and Tamas
Cservanak as Maven committers to help support the new code.
--Brian Fox
Maven PMC Char
On Thu, Jan 7
We should definitely fix this, both in the GPG and in Nexus. Currently
it expects all files to be signed and this is the first one we've come
across that wasn't signed. I'll disable the rule now until it's sorted
out and close the repo for you.
Stephen, what ended up being the fix for the rest of
In 2.x the plugins you get from the lifecycle depend on which phase
was executed, and it frankly drove me crazy trying to write the
enforcer plugin rules. I think there are several things a plugin
should be able to get:
1) the original model as parsed from disk with no interpolation or inheritence
Yay for the grid ;-) better now than after a release
On Fri, Jan 8, 2010 at 9:22 AM, Stephen Connolly
wrote:
> To clarify, when building archetype with this release of surefire, the
> build fails, but the build passes with the previous version of
> surefire
>
> 2010/1/8 Stephen Connolly :
>> -1
>
It's really that this goal and the go-offline where some experimental
ones I wrote eons ago. It doesn't find the plugins that are injected
by default lifecycles. I have code now in the enforcer to detect
these, but it hasn't been shared with the dependency plugin yet. So
bug, possibly..more like un
Ok the vote is far past the minimum time and the votes are unanimous.
Welcome to the Maven project Kristian. Your account request has
already been submitted; it can take several days before the account is
created.
--Brian Fox
Maven PMC Chair
On Wed, Jan 6, 2010 at 4:19 AM, Petar Tahchiev wrote
>
> What is your proposal here - did you want to vote those 3 people in as
> committers on the basis of the contribution, or will the existing committers
> apply patches until the rest of us get to know them? (I don't know who they
> are, so we may already). Funnily enough these alternatives hav
On Wed, Jan 6, 2010 at 9:45 PM, Dan Fabulich wrote:
> Kristian Rosenvold wrote:
>
>> The only significant difference between the weave mode and the regular
>> mode is that the complete execution plan is determined up-front. As a
>> consequence of this the ReactorArtifactRepository (line 83) is for
IP is owned by Sonatype and there are only three
active developers that aren't currently Maven Committers, so this
should be pretty easy process wise. Assuming no one has concerns
accepting this code into the project, I'll move forward with the
various formal votes and paperwor
+1
On Wed, Jan 6, 2010 at 9:53 AM, Jason van Zyl wrote:
> +1
>
> On 2010-01-06, at 6:17 AM, Benjamin Bentmann wrote:
>
>> Hi,
>>
>> We solved 29 issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=15996
>>
>> There are still a couple of issues left in JIRA:
>> http
I've updated the metadata:
http://repo1.maven.org/maven2/.meta/repository-metadata.xml
On Mon, Jan 4, 2010 at 2:08 PM, Carlos Sanchez wrote:
> Hi Christian,
>
> Thanks for providing the repo!
> Please subscribe to repo-maintain...@maven.apache.org, that's the list
> for repository matters.
>
> Th
+1
On Mon, Jan 4, 2010 at 2:47 AM, Jason van Zyl wrote:
> Hi,
>
> I have reviewed the patches for the parallel build support and I think they
> are great.
>
> I think we should just give Kristian access to work with Dan and other
> developers who want to support this work.
>
> +1
>
> Thanks,
>
> In detail, I suggest to have Maven core adopt the approach taken by the
> Enforcer Plugin [0] regarding normalization of the version with the
> deviation to consider only the first three numeric parts (assume missing
> parts to be 0) for the comparison. This should make profile activation more
>
The reason the assembly id is a property was to allow a project to
tell it to use their own descriptor instead of the default if needed.
Yes it's harder to turn it off completely, but they have two alternate
choices: redefine the release plugin to activate a different profile,
or introduce their ow
I 100% agree that the pom format is likely the single biggest thing we
need to tackle in the future. What that means for future maven
versions is unclear since I agree that pom changes would justify a
major version bump although I don't think we want to talk about 4.x.
However I definitely think t
Lol, I can't imagine anyone diving into the 2.x resolution code again.
Punt them to 3.x
On Mon, Dec 28, 2009 at 8:22 PM, Jason van Zyl wrote:
> Then anything I see I will just move to 3.x because I honestly don't think
> anyone is going to fix them in 2.x and the code is too different now to
>
Is there anything pressing that calls for a 2.2.2? The 3.0's are
moving along and are quite usable.
On Mon, Dec 28, 2009 at 8:12 PM, Brett Porter wrote:
> John, anything happening here, or reasons not to move forward with releasing?
> I could probably help after 2.0.11 is done.
>
> On 26/12/2009
Yeah lets go for a release on this.
On Wed, Dec 23, 2009 at 5:57 PM, David Jencks wrote:
> Any idea when another try might be feasible? I'm updating a bunch of
> project's builds, having the completely built-in source assembly would be
> pretty handy.
>
> many thanks
> david jencks
>
> On Dec 10
e no versions for plugins. Not
>>> a very good idea and potentially harmful.
>>>
>>> We put it in, deprecate it over 3.0 and it becomes taboo in 3.1. If
>>> it's a bad practice in the majority of cases then we eliminate it.
>>> Over the life of 3.
For all the potential trouble this "enhancement" causes, does it
really have a justifiable performance boost? I mean is copying a pom
really that slow given everything else that has to happen in parallel?
I know if I go to a folder and run mvn install, I expect THOSE EXACT
products from this build
found here:
>
> http://ixnay.biz/maven/
>
> The bundle contents were signed using the same PGP signature we use for our
> releases. The key is available in a public repository.
>
> Any suggestions?
>
I'll take a look. Use the jira to track this going forward, you'll
Hi Peter,
Welcome back.
--Brian
On Mon, Dec 7, 2009 at 9:49 PM, Peter Lynch wrote:
> Hello devs,
>
> A long time ago I was once a committer on Apache Maven. However as time
> passed, life happened elsewhere. Despite this I have been programming in
> Java for the past 10 years or so and on virtua
at 7:59 AM, Greg Brown wrote:
>
>> Thanks Brian. I just took a look at the JIRA ticket - I'll follow the steps
>> you suggested and post any additional questions/comments there.
>> Greg
>>
>> On Dec 5, 2009, at 11:01 PM, Brian Fox wrote:
>>
>>> Gr
Greg, I created the issue and setup the project. See my comments here
regarding the bundles:
https://issues.apache.org/jira/browse/INFRA-2364
On Fri, Dec 4, 2009 at 5:37 PM, Brian Fox wrote:
> Hi Greg, yes I'll take a look. Since it's an apache project, we shou
in anticipation of Pivot's
> graduation. The final artifacts for Pivot 1.4 probably won't be ready for
> another few weeks.)
>
> Thanks again for your help,
> Greg
>
>
> On Dec 3, 2009, at 11:27 AM, Brian Fox wrote:
>
>> Hi Greg, I'll take a lo
On Fri, Dec 4, 2009 at 2:16 AM, Jorg Heymans wrote:
> On Thu, Dec 3, 2009 at 7:44 PM, Brian Fox wrote:
>> Something like duplicate dependencies likely means you have a real
>> problem you didn't know about in your poms. I think failing is
>> appropriate in this case.
&
Something like duplicate dependencies likely means you have a real
problem you didn't know about in your poms. I think failing is
appropriate in this case.
On Thu, Dec 3, 2009 at 5:42 AM, Stephen Connolly
wrote:
> 2009/12/3 Stephen Connolly
>
>>
>>
>> 2009/12/3 Jorg Heymans
>>
>>> On Thu, Dec 3
Hi Greg, I'll take a look later today and ping back on the pivot dev
list with what I find.
On Thu, Dec 3, 2009 at 6:44 AM, Greg Brown wrote:
> Forwarding this message to dev@maven.apache.org in case
> us...@maven.apache.org wasn't the right place. Also, since sending the
> original message, I
On Fri, Nov 27, 2009 at 3:42 PM, Brett Porter wrote:
> Brian,
>
> I'm not sure if you were replying to me or others, but you quoted me and
> snipped my actual point:
>
> "I'm fine with either more or less frequent releases... I'm not fine with
> circumventing review or pushing releases outside t
> I'm also not pushing for duration for "testing" purposes. That's part of it,
> but as Jason said
>automation can reduce the need over time (though it's never going to be 100%
>so there's some value
>in testing). However, it is mostly for an opportunity to review changes. If we
>do "8 releases
oh wait oh wait, but i've got 15 things.
;-)
On Fri, Nov 20, 2009 at 4:23 PM, Brett Porter wrote:
> Yes, it's been tagged a while too. I was planning to start the RC process
> today.
>
> On 21/11/2009, at 8:04 AM, Michael wrote:
>
>> Hi folks,
>>
>> all issues for Maven 2.0.11 have been clo
201 - 300 of 670 matches
Mail list logo
