To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
--
Tim O'Brien: (847) 863-7045
On Feb 4, 2008, at 6:14 PM, Dan Fabulich wrote:
Jan Nielsen wrote:
Finding the definitive help information for a plugin should be
absolutely trivial and built-in; having the CLI option which give
the code-you-are-executing-right-now the ability to answer that
question avoids the issues w
On Feb 4, 2008, at 8:49 PM, Dan Fabulich wrote:
Tim O'Brien wrote:
I'm sorry, hold on... starting stopwatch "mvn help:describe -
Dplugin=nifty -Dmojo=nifty -Dfull" - alright, I type fast, but that
took me 10 seconds. Then I hit enter and a whole *crapload* of
stomizable, but any change introduced
can't break the current model.
But, I'm not optimisitc it is going to happen unless someone just does
it and writes a ranting blog entry about it.
Tim O'Brien
On Feb 10, 2008, at 3:34 AM, nicolas de loof wrote:
Hello,
Maven detracto
t way isn't the fix. The fix is to provide
more than one implementation.
Nico.
2008/2/10, Tim O'Brien <[EMAIL PROTECTED]>:
Nicolas,
I agree that POM verbosity is a problem, but I also think that a lot
of people on this list are not going to want to introduce
revolutiona
different?
Wb
On Feb 10, 2008 11:01 AM, Tim O'Brien <[EMAIL PROTECTED]> wrote:
On Feb 10, 2008, at 10:57 AM, nicolas de loof wrote:
Using attributes in place of XML elements is not revolutionary. I
don't
speak here about writting POMs in groovy !
That's t
Why not further steps towards terseness?
1. Get rid of collection container elements.
Why this:
descriptor
When this wold suffice:
descriptor
This seems like a trivial issue, but when you look at all of the
container elements, dependencies, plugins, exclusio
it more difficult for people
building out tool support, if someone wanted to do something like
create a binary format, there's nothing stopping them.
-john
On Feb 12, 2008, at 10:55 AM, Tim O'Brien wrote:
On Feb 12, 2008, at 9:34 AM, Gilles Scokart wrote:
-Original M
On Feb 12, 2008, at 9:34 AM, Gilles Scokart wrote:
-Original Message-
From: Tim O'Brien [mailto:[EMAIL PROTECTED]
Sent: mardi 12 février 2008 16:03
To: Maven Developers List
Subject: Re: An Attribute Based POM
On Feb 12, 2008, at 3:58 AM, Benjamin Bentmann wrote:
For ex
ms since
01/01/1970 .. so its un non-formated binary type
The equivalent XML element should be something like
23:22:22.003
2008/2/12, Tim O'Brien <[EMAIL PROTECTED]>:
On Feb 12, 2008, at 3:58 AM, Benjamin Bentmann wrote:
For example, we'd can group groupId/artifactId/versi
On Feb 12, 2008, at 3:58 AM, Benjamin Bentmann wrote:
For example, we'd can group groupId/artifactId/version into one
attribute
like this:
Please don't do this. This would require another parsing step after
the XML
parsing and introduces further error sources. Use XML to structure
the
Bill, I'd recommend posting this question to the Flexmojos user list.
Here's a link to:
http://groups.google.com/group/flex-mojos/topics
Tim
On Mon, May 16, 2011 at 10:31 PM, sg057052 wrote:
> I followed an example on a flexmojos site at
> https://docs.sonatype.org/display/FLEXMOJOS/Applicatio
I had to write this process down for the millionth time today. Here it
is: the current procedure for downloading Maven (without using figures).
1. Go to http://maven.apache.org.
2. On the right-hand side of the page, you should see a section with the
title "Get Maven 3.0.3".
3. Click on the first
itor (starter, user,
> > > > developer) instead of summing up all the handy
> > stuff, but that's a real
> > > > challenge. -Robert [1] http://maven.apache.org[2] http://gradle.org
> > > > >> From: vsive...@apache.org
> > > > >> Da
Vincent that seems like a mistake. Why add more specific elements like Wiki
and API. Why make the POM syntax this specific. Why not make it free
from, something like:
Which you could compact down in some groovy syntax to something like
"wiki:"
I see a lot of people using Maven for proje
I think DVCS would benefit Maven doc. Someone (not a commiter) could clone
the site, fix it, contribute it back without having to jump through the JIRA
+ patch + "convince a committer to pay attention" hoop. The main
difference here is that Git makes it really easy to merge in changes and
select
Is there a more straightforward way to add support for a custom
packaging type to the dependency plugin aside from just customizing
the components.xml, forking the plugin, and publishing your own custom
build?I'm assuming the answer is no because I see that there is an
UnArchiver with a "swc" r
FYI, running another mirror is a noble goal, and I'm sure there is a
lot of good that could come of finding innovative ways to index, but I
did want to let you know that there is already a searchable index that
provides a number of tools a way to search by class name, GAV
coordinates, etc.
Maybe i
Here LMGTFY,
http://maven.apache.org/plugins/maven-antrun-plugin/usage.html
On Thu, Aug 6, 2009 at 8:31 AM,
akhileshkukreja wrote:
>
> I am a new developer working in Maven. We have migrate the build scripts for
> our project from Ant to Maven. I want to call all the tasks in my build.xml
> fro
Non-binding +1
Many, many trees will be saved from this simple change.
Tim
On Mon, Apr 12, 2010 at 9:46 AM, John Casey wrote:
> +1
>
> This will save me quite a bit of time and frustration in the future...
>
> On 4/10/10 7:40 AM, Jason van Zyl wrote:
>>
>> Hi,
>>
>> This was simply to bump the
By my tally that's 18 vacation days just this year. I think I'm going
to take tomorrow off. These emails serve as a good reminder for us
all.
On Fri, Apr 16, 2010 at 11:01 PM, Paul Benedict wrote:
> Wayne, great point. Makes me jealous too.
>
> On Fri, Apr 16, 2010 at 10:10 PM, Wayne Fay wrot
Arnaud, I run into situations where one project demands a complete
different settings.xml than another. Assume you have a book project
that deals with a separate repo manager and set of credentials vs. a
tiny codehaus project with a separate repo man vs. an internal
corporate project with differe
Ok, I'm glad we were all prepared for this. I've made sure to update
the Maven FAQ to include this info for others that might be confused:
http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-IsJuliaAntonova%2FTumlareoutoftheoffice%3F
On Fri, Apr 30, 2010 at 2:17 PM, John Casey wrote:
> It
; From: wayne...@gmail.com
>>> To: dev@maven.apache.org
>>>
>>> Tim, this is a great addition to the FAQs! I especially like the
>>> calendar going back a few years. ;-)
>>>
>>> Wayne
>>>
>>> On Fri, Apr 30, 2010 at 2:33 PM, Tim O
structure below.
I think it's just a matter of configuration at this point. So I'll
get started with SCM. Emmanuel - interested?
I'm also calling on Tim O'Brien and Henri Yandell here since I saw
them at JavaOne and they said they'd help out in some way (even if
just applyin
Even though we happen to all be developers, this discussion may be
more appropriate on the users list.
Sebastien, have you looked at the overlay feature of the WAR plugin? http://maven.apache.org/plugins/maven-war-plugin/examples/war-overlay.html
Are you proposing that a similar idea be ge
Developers don't write great documentation. Don't raise the bar so high
that people are discouraged from submitting doco-less patches. Just create
a structure to address documentation deficiency.
1. Create a documentation posse - identify people who will focus solely on
doco, reduce the barrier
Having to choose between publishing the latest and greatest docs and only
the released version is a problem that Maven seems to have created for
itself. Same issue comes up in other projects frequently - Commons has a
problem because some of the sites only publish on a release. Latest and
greates
as
> it seems to me that it would reduce confusion.
>
> -john
>
> Tim O'Brien wrote:
> > Having to choose between publishing the latest and greatest docs and
> only
> > the released version is a problem that Maven seems to have created for
> > itself. Same issu
> willing to trade a bit of the look&feel for that sort of information, as
> it seems to me that it would reduce confusion.
>
> -john
>
> Tim O'Brien wrote:
> > Having to choose between publishing the latest and greatest docs and
> only
> > the released version
missing the continuous integration part to auto deploy site
> everytime it's changed
>
> On 3/8/06, Tim O'Brien <[EMAIL PROTECTED]> wrote:
> > Having to choose between publishing the latest and greatest docs and
> only
> > the released version is a problem
of the core committers
for Maven, had to send out an email entitled "Making the current web site
suck less", is not a good sell for generating sites with Maven.
> >
> >
> > On 3/8/06, John Casey <[EMAIL PROTECTED]> wrote:
> >> +1
> >>
> >> May
On 3/9/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jesse Kuhnert wrote:
> > I think what everyone is saying sounds more or less correct, but what is
> the
> > solution then?
> >
> > If they can't rely on a runtime container to host the site
On 3/9/06, John Casey <[EMAIL PROTECTED]> wrote:
>
>
>
> I agree with you on that point. My point was that physical separation of
> the websites might not be appropriate or necessary, since IMO every ASF
> project that releases a product (not an API) should apply this advice,
> and therefore shou
On 3/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Tim O'Brien wrote:
> > I read your response, clicked on the Geronimo site, and wanted to
> believe
> > that that was possible with Maven. But, if you look at
> > https://svn.apache.org/repos/asf/geronimo/sit
; in a proposal form for how to make specific improvements. ie, for
> everything that you think is wrong, say how you'd make it right, in
> point form so each can be specifically addressed and turned into jira
> tasks.
>
> - Brett
>
> Tim O'Brien wrote:
> > I'm
I helped implement the svn:externals over in commons, and it does seem like it
is working well.
Brett your concern about anon and auth URLs is true. In commons we decided to
optimize for the committer and user https. I would like to see svn:externals
support some mechanism for using the sch
Versions: 2.0
Reporter: Tim O'Brien
Fix For: 2.0
Attachments: assembly-descriptor-patch.txt
This patch adds a description element to everything in the assembly descriptor.
Tried to be as verbose as possible. Which the current documentation, the only
way to figure out what the
Reporter: Tim O'Brien
Fix For: 2.0
Attachments: assembly-intro-path.txt
This patch adds some explanation to the assembly plugin intro. It summarizes
the plugin for newbies and it also defines "assembly". While the developers of
Maven might know what an "assembly" is, i
[ http://jira.codehaus.org/browse/MASSEMBLY-59?page=all ]
Tim O'Brien updated MASSEMBLY-59:
-
Attachment: patch.txt
> Patch to the assembly plug-in introduction APT document
> ---
>
[ http://jira.codehaus.org/browse/MASSEMBLY-58?page=comments#action_55682 ]
Tim O'Brien commented on MASSEMBLY-58:
--
Ick. Annoying. I'm sorry, I just posted a better patch for #59. Apologies.
> Documentation Patch to supply description
[ http://jira.codehaus.org/browse/MASSEMBLY-59?page=comments#action_56352 ]
Tim O'Brien commented on MASSEMBLY-59:
--
So, apply the second patch, it updates the documentation for the assembly
plug-in. Let me know if the patch needs to change.
Small patch for General FAQ and Plugin Overview
---
Key: MNG-543
URL: http://jira.codehaus.org/browse/MNG-543
Project: Maven 2
Type: Task
Components: documentation
Versions: 2.0-alpha-3
Reporter: Tim
: documentation
Versions: 2.0-alpha-3
Reporter: Tim O'Brien
Priority: Minor
Fix For: 2.0-beta-1
Attachments: small-apt-and-plugin-patch.txt
Here is yet another small doc patch to APT and the plug-ins index page.
--
This message is automatically generated by JIRA.
-
If you thi
Improve plugin-overview and fix site.xml
Key: MNG-571
URL: http://jira.codehaus.org/browse/MNG-571
Project: Maven 2
Type: Task
Components: documentation
Versions: 2.0-alpha-3
Reporter: Tim O'Brien
Fi
pha-2
Reporter: Tim O'Brien
Fix For: 1.0-alpha-3
Attachments: plexus.bat
The getting started instruction tell you to start Continuum by running
"bin\plexus.bat" on a Windows machine, but when I tried to run that BAT file
all I got was a message "Usage: plexus.bat ". T
46 matches
Mail list logo
