It's not a hack, the plugin asks maven core to resolve the artifacts and the
objects it gets back have file handles. In reactor builds with sibling
dependencies, those handles point to the sibling target folder. If you do a
compile reactor build, those handles will point to the /target/classes
fold
+1
On Thu, Mar 31, 2011 at 3:55 PM, Brian Demers wrote:
> Hi,
>
> We solved 9 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112&version=17270
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-056/
>
> Guide to testing staged releases:
> http://m
On Mon, Mar 21, 2011 at 6:06 AM, Benjamin Bentmann
wrote:
> David Jencks wrote:
>
>> Any advice?
>
> Provide a standalone example project that allows others to reproduce/analyze
> the problem.
People that can't browse source without approval likely can't post
code with out approval either ;-/
--
I didn't write the page.
2011/3/16 Arnaud Héritier :
> Brian,
>
> No link or reference to Apache ? :(
>
> Arnaud
>
> On Tue, Mar 15, 2011 at 3:43 PM, Brian Fox wrote:
>> Page is updated.
>>
>> On Tue, Mar 15, 2011 at 10:18 AM, Brian Fox wro
Page is updated.
On Tue, Mar 15, 2011 at 10:18 AM, Brian Fox wrote:
> It should read something like either :
>
> bringing M2eclipse to eclipse...
>
> or
>
> bringing Maven support to eclipse...
>
> That's the intent here if you read the context. I've passed
It should read something like either :
bringing M2eclipse to eclipse...
or
bringing Maven support to eclipse...
That's the intent here if you read the context. I've passed on the
request to update the text.
On Tue, Mar 15, 2011 at 9:57 AM, Jesse McConnell
wrote:
>> I think they _might_ be tal
The ip change is part of some networking and hosting upgrades that
we've undertaken to ensure the stability of the repository. We
actually have 4 systems now that could be serving Central at any given
time. There are 2 hosts in the UK and two virtual machines in the US
(served from a 6 node cluster
mvn -N site-deploy
On Tue, Mar 1, 2011 at 4:50 PM, Brian Ferris wrote:
> I have a large multi-module project that I wish to build a site for using
> Maven's site functionality. The trick is that I'd like to avoid building
> the sub-module sites as well. Building the individuals sites for each
>
The Maven team is pleased to announce the 2.2 release of the Maven
Dependency Plugin:
http://maven.apache.org/plugins/maven-dependency-plugin
Release Notes - Maven 2.x Dependency Plugin - Version 2.2
** Bug
* [MDEP-138] - unpack of tar files fail with ArchiverException:
chmod exit code was
Vote passed at +4
On Sat, Feb 19, 2011 at 10:28 AM, Hervé BOUTEMY wrote:
> +1
>
> Hervé
>
> Le mardi 15 février 2011, Brian Fox a écrit :
>> Plugin is staged at:
>> https://repository.apache.org/content/repositories/maven-009
>>
>> This release is depen
Ok vote passed at +4
On Sat, Feb 19, 2011 at 10:27 AM, Hervé BOUTEMY wrote:
> +1
>
> Hervé
>
> Le vendredi 11 février 2011, Brian Fox a écrit :
>> Staging repo: https://repository.apache.org/content/repositories/maven-055/
>>
>> This release fixes MDEP-143, MDEP
you can also use the dependency plugin to copy/fetch files and strip
off the version.
On Wed, Feb 16, 2011 at 3:37 AM, Marc Rohlfs wrote:
> Another idea might be:
> 1. In Your Maven project, create a text file with the following content:
> http://your-nexus/your-nexus-repo/${project.artifactId}-$
Plugin is staged at:
https://repository.apache.org/content/repositories/maven-009
This release is dependent upon the maven-dependency-analyzer vote and
staged artifacts.
We fixed a boat load of issues:
Release Notes - Maven 2.x Dependency Plugin - Version 2.2
** Bug
* [MDEP-138] - unpack o
[
http://jira.codehaus.org/browse/MDEP-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MDEP-265:
---
Fix Version/s: (was: 2.2)
2.3
> Add classifier option for dependency:
[
http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MDEP-145:
---
Fix Version/s: (was: 2.2)
2.3
> Outputting dependency resolution/tree in a well kn
[
http://jira.codehaus.org/browse/MDEP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MDEP-124:
---
Fix Version/s: (was: 2.2)
2.3
> Dependency incorrectly reported as "Unused
[
http://jira.codehaus.org/browse/MDEP-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MDEP-166:
---
Fix Version/s: (was: 2.2)
2.3
> runtime-scoped dependencies should be specially hand
[
http://jira.codehaus.org/browse/MDEP-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MDEP-231:
---
Fix Version/s: (was: 2.2)
2.3
> Create a single dependency resolution plu
Ok I'll call this vote passed at +5 and promote them.
On Mon, Feb 14, 2011 at 2:57 PM, Dennis Lundberg wrote:
> On 2011-02-14 18:13, Brian Fox wrote:
>> On Mon, Feb 14, 2011 at 12:01 PM, Lukas Theussl wrote:
>>>
>>>
>>> Brian Fox wrote:
>>>>
On Mon, Feb 14, 2011 at 12:01 PM, Lukas Theussl wrote:
>
>
> Brian Fox wrote:
>>
>> On Mon, Feb 14, 2011 at 2:13 AM, Dennis Lundberg
>> wrote:
>>>
>>> On 2011-02-14 01:51, Brian Fox wrote:
>>>>
>>>> Based on the initial discus
On Mon, Feb 14, 2011 at 2:13 AM, Dennis Lundberg wrote:
> On 2011-02-14 01:51, Brian Fox wrote:
>> Based on the initial discussion, I'm going to cancel this vote and
>> restage the ASF one with source/target at 1.5 and roll back the site
>> plugin to the 2.0.x version u
n-dependency-plugin?
>
> -Dan
>
> On Fri, Feb 11, 2011 at 2:41 PM, Lukas Theussl wrote:
>>
>> +1
>>
>> -Lukas
>>
>>
>> Brian Fox wrote:
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories
Based on the initial discussion, I'm going to cancel this vote and
restage the ASF one with source/target at 1.5 and roll back the site
plugin to the 2.0.x version unless there are objections.
On Sun, Feb 13, 2011 at 4:56 PM, Dennis Lundberg wrote:
> +1
>
> On 2011-02-11 02:05, B
We are working on this already
--mobile
On Feb 11, 2011, at 8:34 PM, Benson Margulies wrote:
> I am hoping that some person who works at Sonatype will have pity on me.
>
> People who work for Oracle seem to have strong feeling that they are
> only supposed to deliver things to the java.net repo
What new features specifically?
On Fri, Feb 11, 2011 at 10:56 AM, Benson Margulies
wrote:
> Would there be any sympathy for a JIRA asking for a maven 2.2.x change
> so that the new features of settings.xml (e.g. mirrors) would be
> tolerated by maven 2? Since you all didn't change the conventiona
My key hasn't changed in at least 1.5 years so it should be out there.
It's also in the KEYs file in svn.
On Fri, Feb 11, 2011 at 9:05 AM, Jason van Zyl wrote:
> All the key servers were whacked a couple days ago, maybe they still are. I
> couldn't find anything either a couple days ago but I th
On Fri, Feb 11, 2011 at 9:07 AM, Jason van Zyl wrote:
>
> On Feb 11, 2011, at 7:54 AM, Jesse Farinacci wrote:
>
>> Greetings,
>>
>> On Fri, Feb 11, 2011 at 6:15 AM, Benjamin Bentmann
>> wrote:
>>>
>>> This parent POM like any other parent POM provides default values, i.e.
>>> something that proje
On Fri, Feb 11, 2011 at 3:00 AM, Lukas Theussl wrote:
>
> Brian,
>
> I am happy about this :) however site-plugin-2.2 uses doxia-1.1 and has a
> prereq of maven 2.2, I seem to remember some resistance last time to use it
> by default. Is this no issue anymore?
>
I didn't bump it to 2.2, Olivier d
ogether. It is easier to test that way.
>>
>> -Dan
>>
>> On Thu, Feb 10, 2011 at 5:08 PM, Brian Fox wrote:
>>> Staging repo: https://repository.apache.org/content/repositories/maven-055/
>>>
>>> This release fixes MDEP-143, MDEP-149, MDEP-262 and
Staging repo: https://repository.apache.org/content/repositories/maven-055/
This release fixes MDEP-143, MDEP-149, MDEP-262 and is required by the
Maven Dependency Plugin 2.2
Vote is open for 72 hours
-
To unsubscribe, e-mail: d
Each parent has a bunch of changes, but mostly the changes fall into 2
categories:
1) mundane updating of new plugin versions to use
2) preparations to make Maven3 builds use the correct site plugin
ASF Parent:
http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?r1=1036993&r2=1069623&diff_f
[
https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993143#comment-12993143
]
Brian Fox commented on MPOM-1:
--
A little history on this setup:
It was moved to the ASF
[
https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox reassigned MPOM-1:
Assignee: Brian Fox (was: Olivier Lamy)
> apache-release does unwanted things in the prepare g
Here's a workaround in the meantime:
http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?p2=%2Fmaven%2Fpom%2Ftrunk%2Fasf%2Fpom.xml&p1=%2Fmaven%2Fpom%2Ftrunk%2Fasf%2Fpom.xml&r1=1065778&r2=1065777&view=diff&pathrev=1065778
On Wed, Feb 9, 2011 at 9:12 AM, John Patrick wrote:
> Hi,
>
> I believe
tice the maven
site isn't part of the maven pom for the same reasons). This would be
a better option than what is in place imo, but my gut is that the CMS
is best.
>
> On Tue, Feb 8, 2011 at 9:34 PM, Brian Fox wrote:
>> I see now what you've done. If you need these values fo
f pom project needs to be JUST the pom so that nothing
inherited screws with anyone else's projects.
On Tue, Feb 8, 2011 at 9:29 PM, Brian Fox wrote:
> same comment as the url, i don't think we want to be polluting the
> inheritence tree with specifics about the ASF wide pom project.
&g
same comment as the url, i don't think we want to be polluting the
inheritence tree with specifics about the ASF wide pom project.
On Sat, Feb 5, 2011 at 3:47 PM, wrote:
> Author: olamy
> Date: Sat Feb 5 20:47:25 2011
> New Revision: 1067520
>
> URL: http://svn.apache.org/viewvc?rev=1067520&vie
You realize that this may cause everyone to inherit the wrong url now?
We should have the default url pointed at the apache site, not the pom
site.
On Sat, Feb 5, 2011 at 3:51 PM, wrote:
> Author: olamy
> Date: Sat Feb 5 20:51:25 2011
> New Revision: 1067521
>
> URL: http://svn.apache.org/viewv
btw, thanks for the documentation on the parent...if nothing else
comes from this at least we got that ;-)
On Tue, Feb 8, 2011 at 9:13 PM, Benson Margulies wrote:
> Unfortunately for the coherence of this discussion, it was months and
> months ago that I filed the original version of this JIRA. T
In my experience these problems are more often caused by bad test
infrastructure or handle leaks in production or test code. I had to
spend a lot of time for example rewriting how the maven-indexer tests
worked because it randomly failed for me on Win7. After isolating the
files into temp folder, t
e patch sticks I need to make a patch to the site doc that I
> wrote for the POM, since it describes the presence of the profile :-)
>
> --benson
>
>
>
>
> On Tue, Feb 8, 2011 at 8:25 PM, Brian Fox wrote:
>> Olivier, I think this still needs some discussion. What
[
https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox reopened MPOM-1:
--
This needs a different approach. If people don't want to use the profile by
default, then lets put the pr
Olivier, I think this still needs some discussion. What's the problem
with the activation of the release profile by default? Many Apache
projects depend up on this updated profile and if we just gank it out
to the Maven pom, it will break them all. I think perhaps we can make
it a property to make
fyi, I'll try to cut the release this weekend.
On Thu, Feb 3, 2011 at 2:31 PM, Wayne Fay wrote:
>> Good news. I delved into this last week and came up with an even
>> better patch, and the developer Brian Fox just applied it!
>
> Great job, Phillip. We need more
Hi Craig, there's also release-disc...@apache.org to talk about
release processes specific to Apache.
On Tue, Feb 1, 2011 at 5:54 PM, Craig L Russell
wrote:
> Thanks Kalle, looks like the right level for me to master before I ask more
> detailed questions.
>
> Craig
>
> On Feb 1, 2011, at 2:48 PM
will be posted on the developer section of our site soon.
2) The license of Aether and Sisu have been updated to EPL/ASL.
Thanks,
Brian Fox
Apache Maven PMC Chair
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.or
The projectbuilder comes to mind.
On Wed, Feb 2, 2011 at 11:29 AM, Moser, Christian wrote:
> I'm currently developing a custom enforcer rule.
>
>
>
> How can I get object references to all modules of a parent pom ?
>
>
>
> final List modulesRelativePath = parentProject.getModules();
>
>
>
> deliv
You could simply add a flag or alternate mojo to the dependency plugin
to allow it to fail. IIRC the analyze goal already does this. IOW it's
not a requirement that every mojo that fails a build be rolled into
the enforcer plugin. Failing that, you'd have to pull all the logic
out into a shared com
[
http://jira.codehaus.org/browse/MDEP-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MDEP-225.
--
Resolution: Fixed
patch applied, thanks.
> Dependency plugin seems to unpack archive even, if it is already unpac
[
http://jira.codehaus.org/browse/MDEP-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MDEP-225:
---
Fix Version/s: 2.2
> Dependency plugin seems to unpack archive even, if it is already unpac
t require a CLA form? Does the answer depend on the amount
> of work being submitted? We decided on a patch but I don't have any
> clear-cut guidance. What are your opinions?
>
> Paul
>
> On Fri, Jan 28, 2011 at 3:56 PM, Brian Fox wrote:
>
>> Sounds fine, in g
Sounds fine, in general you can ask questions to the list
dev@maven.apache.org (cc'd)
On Fri, Jan 28, 2011 at 12:12 PM, Amanda Lynn wrote:
> Hello,
>
> I want to translate 'Frequently Asked Technical Questions'
> (http://maven.apache.org/general.html) to Belorussian language, which is my
> mother
o embody that policy in a POM that isn't the one advertised
>> >> >>> to the complete Apache community.
>> >> >>
>> >> >> ...which is why I said in another branch of this thread, that I'm
>> okay
>> >> with
>> >
If the Land Of Maven
> wants a policy of running a full build on prepare, I'd respectfully
> ask you to embody that policy in a POM that isn't the one advertised
> to the complete Apache community.
>
> On Thu, Jan 27, 2011 at 3:58 PM, Lukas Theussl wrote:
>>
>>
>
>
> FWIW, if the code-signing step fails due to some POM misconfiguration, and
> only runs in the perform step, then you've got to rollback the release and
> try it again...either that, or muck around with manually shifting the tag in
> the SCM, which is probably as ugly.
>
> I'm not as concerned a
Lets end the debate on this pending the ongoing PMC discussions. There
isn't a release pending that I'm aware of that needs this change to be
committed urgently, so there's no need to rush to judgement on
anything, or to further debate what can and can't be done with
licenses at Apache. The policy
AIRN is requiring that Contegix renumber our machines in the UK so
tonight one of them will change and tomorrow the other will change. As
always, you should address them using http://uk.maven.org to allow
failover but I know occasionally people have to poke holes in their
firewalls based on ip.
--
AIRN is requiring that Contegix renumber our machines in the UK so
tonight one of them will change and tomorrow the other will change. As
always, you should address them using http://uk.maven.org to allow
failover but I know occasionally people have to poke holes in their
firewalls based on ip.
--
i don't think the classpath is filtered based on those values in this
goal, it just dumps the actual classpath that would match the desired
scope.
On Mon, Jan 17, 2011 at 10:52 AM, John Anderson wrote:
> I am trying to use dependency:build-classpath. If I run "mvn
> dependency:analyze" all seems
The 500 is an internal error on the Nexus side. We'll need to see your
Nexus logs to see what happened. You should send those to the nexus
user list for a quicker answer.
On Fri, Jan 14, 2011 at 9:01 AM, martib wrote:
>
> I'm facing a problem under M3.0.2 or 3.0.1 with Nexus Repository
> mvn dep
mentation since he's so good at answering questions ;-)
Welcome Wayne!
--Brian Fox
Apache Maven PMC Chair
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
mentation since he's so good at answering questions ;-)
Welcome Wayne!
--Brian Fox
Apache Maven PMC Chair
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
+1
On Wed, Jan 12, 2011 at 9:04 AM, Benjamin Bentmann
wrote:
> Brian Demers wrote:
>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-016/
>
> +1
>
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev-unsu
i would prefer ci rather than failing in the release process
On Wed, Jan 12, 2011 at 7:09 PM, Brett Porter wrote:
> I have the RAT configuration in the indexer already, and could put it in the
> release profile. Another alternative is to put it in maven parent itself.
> There's two drawbacks:
>
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MAVENUPLOAD-2810.
--
Resolution: Won't Fix
Please see
https://docs.sonatype.org/display/Repository/Uploadin
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MAVENUPLOAD-2811.
--
Resolution: Won't Fix
Please
see:https://docs.sonatype.org/display/Repository/Uploadin
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MAVENUPLOAD-2806.
--
Resolution: Won't Fix
Please see
here:https://docs.sonatype.org/display/Repository/Uplo
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MAVENUPLOAD-2807.
--
Resolution: Won't Fix
Please see
https://docs.sonatype.org/display/Repository/Uploadin
+1
On Tue, Jan 11, 2011 at 6:50 AM, Olivier Lamy wrote:
> +1
>
> 2011/1/9 Benjamin Bentmann :
>> Hi,
>>
>> We solved 25 issues since 3.0.1:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=16952
>>
>> There are still a couple of issues left in JIRA:
>> http://jira.codeh
am not a committer) can we set things up so I can
> stage... I don't need to promote unless the Cassandra PMC are happy letting
> me promote.
> Thanks,
> -Stephen
> Note: I have included dev@cassandra.apache.org to keep people in the loop
>
> On 13 December 2010 2
--mobile
On Dec 28, 2010, at 6:50 PM, Jason van Zyl wrote:
>
> On Dec 28, 2010, at 6:06 PM, Benjamin Bentmann wrote:
>
>> Brian E. Fox wrote:
>>
>>> -1 to a, +1 to b
>>
>> Just to be clear, I meant a) AND b), not either or. a) is concerned about
>> the actual version interpretation, b) about gu
[
https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972914#action_12972914
]
Brian Fox commented on AVRO-663:
The content of the jar doesn't matter, the nam
Don't use RELEASE or LATEST.
On Fri, Dec 17, 2010 at 7:43 AM, Asmann, Roland wrote:
> Hi all,
>
> I'm writing an enforcer-rule, that should check if my parent is the
> LATEST version. How can I get the actual version for 'LATEST'?
>
> Thanks!
>
> --
> Roland Asmann
> Senior Software Engineer
>
>
That page is garbage and should be dumped. The official list is
maintained in the repo itself:
http://repo1.maven.org/maven2/.meta/repository-metadata.xml
On Wed, Dec 15, 2010 at 3:32 PM, Jörg Hohwiller wrote:
> Hi there,
>
> some people recommend to use a mirror for maven. Others are required t
[
https://issues.apache.org/jira/browse/IVY-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated IVY-1255:
---
Attachment: ivy.log.gz
> Possible bug in Ivy's maven resolver is causing massive amounts of r
: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.1.0
Reporter: Brian Fox
We were investigating suspicious download trends of groovy as reported by the
central statistics, and I found some odd behavior from Ivy. I see from many ips
mass
If x-SNAPSHOT.release() = x then SNAPSHOT.release()= npe or divide by
zero, take your pick :)
I always made sure to point out this anti-pattern during all the maven
training classes I did.
--mobile
On Dec 13, 2010, at 6:42 AM, Benjamin Bentmann
wrote:
> Brett Porter wrote:
>
>> [...] "SNAPSHOT
We'll take a pass and see which are applicable and flag them in some
way. Moving them all will be a needless pita, imo.
On Tue, Dec 7, 2010 at 1:21 PM, Brett Porter wrote:
>
> On 07/12/2010, at 3:20 AM, Jesse Glick wrote:
>
>> On 12/03/2010 10:09 AM, Brett Porter wrote:
>>> I went ahead and creat
You shouldn't mix unique and non-unique versions of the same snapshot artifact
--mobile
On Dec 6, 2010, at 5:22 PM, "KARR, DAVID (ATTSI)" wrote:
> If I have an artifact with version "n.n.n-SNAPSHOT" in my "user" repo
> and the same artifact with version "n.n.n-SNAPSHOT" in the "local" nexus
> r
You can also use prerequisites in the pom, this is the one and only
use case it was intended for.
--mobile
On Dec 6, 2010, at 3:21 PM, Peter Niederwieser wrote:
> Because my plugin (spock-maven) doesn't work with Maven 3, I'd like to fail
> the build if it used with Maven 3. (Otherwise it will
Take a look at the enforcer plugin and the enforcemavenversion rule
--mobile
On Dec 6, 2010, at 3:21 PM, Peter Niederwieser wrote:
> Because my plugin (spock-maven) doesn't work with Maven 3, I'd like to fail
> the build if it used with Maven 3. (Otherwise it will be very hard for users
> to
dependency:copy-dependencies sounds like what you want.
On Fri, Dec 3, 2010 at 7:41 AM, amaresh mourya wrote:
> Hi,
>
>
>
>
>
> ${project.groupId}
> maven-utils
> ${project.version}
>
>
>
>
> log4j
> log4j
> 1.2.14
>
Repository.apache.org exposes nexus' rest interface
--mobile
On Dec 2, 2010, at 4:44 PM, Russ Tremain wrote:
> anyone know of a web-service interface to any of the public maven artifact
> lookup services?
>
> tia,
> -russ
>
>
Soon. I resolved a ton of issues at ApacheCon and just ran out of time
to wrap it up. I'll be getting back to it in the next week or so.
On Wed, Dec 1, 2010 at 10:19 PM, Dan Tran wrote:
> me too :-)
>
> On Wed, Dec 1, 2010 at 10:04 AM, Jim McCaskey
> wrote:
>> Hello all,
>>
>> I ran across a pro
We do a little bit of sleuthing when resolving these types of issues
to make sure the file hasn't been changed, which is why automatic
correction isn't implemented. We are working on process to ensure that
no new things come in this way. It can only happen today via the old
rsync mechanisms and tho
FYI
-- Forwarded message --
From: Brian Demers
Date: Mon, Nov 29, 2010 at 4:12 PM
Subject: [ANN] Apache parent 8, Maven Parent 18,
apache-source-release-assembly-descriptor 1.0.3 Released
To: annou...@maven.apache.org, us...@maven.apache.org
Cc: d...@maven.apache.org
The Maven
+1
On Sun, Nov 28, 2010 at 7:03 AM, Mark Struberg wrote:
> +1
>
> LieGrue,
> strub
>
> --- On Sun, 11/28/10, Olivier Lamy wrote:
>
>> From: Olivier Lamy
>> Subject: Re: [VOTE] Release Apache parent 8, Maven Parent 18,
>> apache-source-release-assembly-descriptor 1.0.3
>> To: "Maven Developers
+1
On Sat, Nov 27, 2010 at 2:21 PM, Benjamin Bentmann
wrote:
> Brian Demers wrote:
>
>> Staging
>> repo:*https://repository.apache.org/content/groups/maven_promotion-010/*
>
> +1
>
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev
[
http://jira.codehaus.org/browse/MDEP-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245691#action_245691
]
Brian Fox commented on MDEP-294:
Can you add a test?
> copy-dependencies goal doesn
Lets look at this closely:
On Mon, Nov 29, 2010 at 8:36 AM, Jon Strayer wrote:
> On the 24th of November my reports build failed. The failure message is:
> Unable to read local copy of metadata: Cannot read metadata from
> 'e:\repo\org\apache\maven\skins\maven-default-skin\maven-metadata-java.ne
On Tue, Nov 23, 2010 at 10:27 AM, Ralph Goers
wrote:
> Thanks, but I'm still not sure I'll change anything in VFS. I prefer having
> both the source and binary archives built in the same project. With the
> change to the Apache pom the source archive is built in the parent and the
> binary is b
Ralph,
We made the change to easily allow projects to select the tar.gz & zip
source distribution now and it's being staged for a vote today:
http://svn.apache.org/viewvc?view=revision&revision=1038139
Once this is released and you update to the new Apache pom, you can
select the tar.gz assembly s
[
http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243252#action_243252
]
Brian Fox commented on MDEP-273:
We usually add a small section to the usage page describing the
We'll try to cut this release this week. M2e needs an updated indexer
component to go through the PR process and we'd like to make the flip
to the maven one sooner.
On Wed, Nov 3, 2010 at 6:57 PM, Brian Fox wrote:
> The indexer code drop is complete. We're already converting Ne
mvn dependency:sources and/or mvn dependency:resolve
-Dclassifier=sources or -Dclassifier=javadoc
if you use m2eclipse, then it will get the sources/javadocs
automatically as needed.
On Sun, Nov 14, 2010 at 12:26 PM, piloupy GOTTAPIL wrote:
> Hi,
>
> I've search for nearly half a day, and I did
[
http://jira.codehaus.org/browse/MNG-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242791#action_242791
]
Brian Fox commented on MNG-4893:
I think we should stick with the x.y.z-SNAPSHOT form for
We've just discovered a Google App Engine app called pomyard abusing
several repos. Based on the behavior and name of the service, I have
reason to believe they may be attempting to scrape public all maven
repos not just central, ignoring robots.txt. If you have a public
repo, I suggest you block t
The Maven team is pleased to announce the release of the Maven
Enforcer Plugin, version 1.0
Maven Enforcer Plugin - The Loving Iron Fist of Maven™ The Enforcer
plugin provides goals to control certain environmental constraints
such as Maven version, JDK version and OS family along with many more
s
The Maven team is pleased to announce the release of the Maven
Enforcer Plugin, version 1.0
Maven Enforcer Plugin - The Loving Iron Fist of Maven™ The Enforcer
plugin provides goals to control certain environmental constraints
such as Maven version, JDK version and OS family along with many more
s
On Mon, Nov 8, 2010 at 9:43 AM, Jochen Wiedmann
wrote:
> Henning,
>
> it isn't as simple as you believe. See, for example, this thread:
>
> http://marc.info/?t=12825660982&r=1&w=2
>
> The conclusion was, as I read it at the time, that you should expect
> that users still have to edit their re
301 - 400 of 2834 matches
Mail list logo
