+1
--
Olivier
-Message d'origine-
De : Dennis Lundberg [mailto:[EMAIL PROTECTED]
Envoyé : samedi 29 septembre 2007 00:25
À : dev@maven.apache.org
Objet : [VOTE] Release maven-plugins parent pom version 9
Hi
In preparation for the release of maven-site-plugin I'd like to release the
p
Raphael and I have been doing a lot of work on ArchetypeNG and I
would like to release a series of alphas before we do the official
switch over. I think it's working nicely now but still needs a lot of
work but I want to start getting feedback.
It will remain using the "archetypeng" moniker
Scratch this as it should be 2.0-alpha-1 as it's the next version.
This can't be released as 1.0.
On 28 Sep 07, at 7:07 PM 28 Sep 07, Jason van Zyl wrote:
Raphael and have been doing a lot of work on ArchetypeNG and I
would like to release a series of alphas before we do the official
switc
I followed the instructions here:
http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins
.html
And copied the default-site.vm to my skin, but when velocity is
processing, my site.vm is completely ignored. What's missing?
--Brian
Raphael and have been doing a lot of work on ArchetypeNG and I would
like to release a series of alphas before we do the official switch
over. I think it's working nicely now but still needs a lot of work
but I want to start getting feedback.
It will remain using the "archetypeng" moniker u
+1
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Friday, September 28, 2007 6:25 PM
To: dev@maven.apache.org
Subject: [VOTE] Release maven-plugins parent pom version 9
Hi
In preparation for the release of maven-site-plugin I'd like to release
the plugin paren
Hi
In preparation for the release of maven-site-plugin I'd like to release
the plugin parent pom r575842 as version 9.
Source:
https://svn.apache.org/viewvc/maven/plugins/trunk/pom.xml?revision=575842&content-type=text%2Fplain
The vote will be open for 72 hours.
+1 from me
--
Dennis Lundbe
We have 3 +1 votes from PMC folks (jvanzyl, brianf, aheritier) and my
non-PMC +1 vote. No -1 or 0 votes. Thus, this vote passes.
Releasing now.
Thanks!
Dan
On Monday 24 September 2007, Daniel Kulp wrote:
> All but one bug for GPG plugin is now fixed (and that bug is really a
> bug in th
If there won't be a pre/post-site phase in maven core, then this sounds
like a way solve it. I don't think that it's necessary to beta-6 though.
Vincent Siveton wrote:
Hi,
Just a thought about the site plugin and the default lifecycle:
Actually, there is no goal binding for pre/post site.
So,
I made some experiment to refactor BidirectionalRepositoryLayout so
that toArtifactReference return a set of possible ArtifactReference.
This has many impacts, and sometime breaks archiva logic :
for example, what should be done in MetadataUpdaterConsumer ? We can't
create phantom metadatas just be
On 28 Sep 07, at 10:17 AM 28 Sep 07, Rollo, Dan wrote:
Sorry to reply to this listing, but I saw some messages about the
enforcer now enforcing no repo data in the pom and then read the link
below:
MNG-2381improved control over the repositories in the POM
http://jira.codehaus.o
Sorry to reply to this listing, but I saw some messages about the
enforcer now enforcing no repo data in the pom and then read the link
below:
MNG-2381improved control over the repositories in the POM
http://jira.codehaus.org/browse/MNG-2381
and I got worried. I've commented that
The situation with the lack of a release is compounded by the latest snapshot
of 1.2 from 20070213 missing two class files and the components.xml, so it
does not, in fact, seem to fix http://jira.codehaus.org/browse/MANTRUN-44
So please either put out another snapshot build, or actually release t
I am trying to run mvn release:perform. By default maven is looking at the
current directory as the working directory and the relase fails. My maven
consists of multiple modules. Is there a way I can tell maven release plugin
to tell where the working directory is?
I tried the following configura
"Dan Tran" <[EMAIL PROTECTED]> wrote on 09/28/2007 10:20:43 AM:
> On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
> >
> >
> > Also, when playing with scm:starteam checkout I noticed that it
deletes the
> > checkout area first. I did not see any code that did this in the
Starteam
> > so
On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Greetings all
>
> I have decided to implement my own scm provider, named custom. My connect
> url would therefore look like scm:custom:.
>
> So, my question is, what next? Or more specifically, what are the
> classes/interfaces neede
it's a dynamic discovery.
In your provider, you need a class that extends AbstractScmProvider. This class
must have in javadoc this line:
* @plexus.component role="org.apache.maven.scm.provider.ScmProvider"
role-hint="custom"
And you must add this plugin in your pom:
org.code
Greetings all
I have decided to implement my own scm provider, named custom. My connect
url would therefore look like scm:custom:.
So, my question is, what next? Or more specifically, what are the
classes/interfaces needed to make this happen? Do I "register" with the
scm framework in som
Post-site goal binding will be necessary for the linkcheck plugin to
work, and also, I think, for a dashboard plugin, so +1 from me in
principle. However, I don't think that it *must* go into beta-6 still.
-Lukas
Vincent Siveton wrote:
Hi,
Just a thought about the site plugin and the defaul
On 28 Sep 07, at 1:10 AM 28 Sep 07, Kevin Jackson wrote:
Hi,
The Java sources, xml reader/writer (for various tools like xpp3,
jdom), XSD, and documentation. All comes from the same model.
From the same xml file (maven.mdo)?
Yes.
Because searching for an io
package, or any xpp3 referenc
Hi,
> The Java sources, xml reader/writer (for various tools like xpp3,
> jdom), XSD, and documentation. All comes from the same model.
>From the same xml file (maven.mdo)? Because searching for an io
package, or any xpp3 reference fails (eyeballing or running text
search tools).
I'm missing som
On 28 Sep 07, at 12:38 AM 28 Sep 07, Kevin Jackson wrote:
Hi,
I'm trying to wrap my head around how mvn 2.0.x is built and I'm a
little confused by the maven.mdo file.
It seems as if the entire org.apache.maven.model package is
auto-generated by reading an xml model and spitting out java (why
Hi,
I'm trying to wrap my head around how mvn 2.0.x is built and I'm a
little confused by the maven.mdo file.
It seems as if the entire org.apache.maven.model package is
auto-generated by reading an xml model and spitting out java (why?)
However in the actual model description, I can find no ref
23 matches
Mail list logo
