Bug
Components: Invalid POM
Reporter: J. Matthew Pryor
http://www.ibiblio.org/maven2/commons-jelly/commons-jelly-tags-ant/1.0/commons-jelly-tags-ant-1.0.pom
has an incorrect artifact ID and also maskes reference to a SNAPSHOT version
of commons-jelly which has no POM
4.0.0
commons-jelly-
Wouldn't a folksonomy approach to categories be better? I can't imagine any
'exhaustive' list being right the first time (or the second for that matter
;-)
Systems like delicious seem to do pretty well with people supplying their
own tags?
Matthew
> -Original Message-
> From: Carlos Sanc
[ http://jira.codehaus.org/browse/MNG-576?page=comments#action_42739 ]
J. Matthew Pryor commented on MNG-576:
--
I am pretty sure this is the same basic problem that has frustrated my attempts
to write an M2 plugin to support Eclipse PDE artifacts. The
Kenny thanks for the help, however I am not sure we're on the right track
yet
> You don't need to modify maven-core/META-INF/components.xml. That only
> defines the global lifecycle.
As far as I can tell it also defines other lifecycles such as the
plexus-application lifecycle, which is where I a
sage-
> From: Matthew Pryor [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 5 July 2005 10:44 AM
> To: 'Matthew Pryor'; 'Maven Developers List'
> Subject: RE: help with custom lifecycle
>
> OK so I can define a packaging & lifecycle if I edit maven-core/META-
>
;d love to get this working or sort
out what needs to be changed to enable it
Thanks,
Matthew
> -Original Message-
> From: Matthew Pryor [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 5 July 2005 9:29 AM
> To: 'Maven Developers List'
> Subject: RE: help with custom life
ent: Monday, 4 July 2005 4:11 PM
> To: Maven Developers List
> Subject: Re: help with custom lifecycle
>
> You can see some design docs there :
> http://docs.codehaus.org/display/MAVEN/Lifecycle
>
> Emmanuel
>
>
> Matthew Pryor wrote:
> > I am trying to write/re
I am trying to write/refine the mevenide Eclise PDE builder maven2 plugin.
In essence what this plugin needs to do is to read an XML file (plugin.xml)
and add a bunch of jar files to the classpath prior to compilation or
testing.
I have all the latest source for m2 and am not 100% sure abou
[ http://jira.codehaus.org/browse/MNG-359?page=comments#action_39744 ]
J. Matthew Pryor commented on MNG-359:
--
The requirement is really simple. Eclipse does not allow projects to contain
other projects and I like having my master project POM
I seems to have mucked something up, I get the following:
C:\proj>maven plugin:download -DgroupId=maven
-DartifactId=maven-artifact-plugin -Dversion=1.3
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
Plugin cache wil
10 matches
Mail list logo
