I already responded to this here: http://www.nabble.com/Re%3A-local-
repositories-%28was%3A-http%3A--jira.codehaus.org-browse-MNG-3151%29-
p12286344s177.html
Cheers,
Brett
On 29/08/2007, at 4:49 PM, Nigel Magnay wrote:
If you are knowingly doing this then I would say different settings
via
>
> If you are knowingly doing this then I would say different settings
> via a build plan to prevent corruption or the CI mechanism serializes
> the builds.
>
How can one do this and still make use of all 8 cores to build on a
desktop machine (or all 16 on our CI server)? m2 builds could run
real
Where are we with this?
The thread went a bit off the rails for some other stuff, and the
only other suggestion I saw was:
On 23/08/2007, at 3:32 AM, Jason van Zyl wrote:
But the case that Atlassian wants solved would be very simple with
something like Proximity even today. One simple acce
>Raphaël has access now, so as I understand it the steps are as follows:
>1) create a tarball of the code, and checksum
Done. http://people.apache.org/~brianf/archetypeng.tar.gz
>2) check that it in to the sandbox for historical purposes
Skipped this step. If needed, I can add the file.
>3) e
Hi All,
One consequence of Cenqua's acquisition by Atlassian is that we now
have the resources to continue development of the Maven Clover plugin
ourselves. It will remain open source under the Apache licence, and
the source will be hosted in Atlassian's public svn repository.
Many thanks
ok, i'm going to release alpha 6 and delete the alpha 5
+1: Brett, Stephane, Milos, myself
On 8/28/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> Sorry, I read "push" as "delete" :)
>
> On 28/08/2007, at 8:49 PM, Carlos Sanchez wrote:
>
> > I understand that, but then what confuses me was your pr
Sorry, I read "push" as "delete" :)
On 28/08/2007, at 8:49 PM, Carlos Sanchez wrote:
I understand that, but then what confuses me was your previous
answer ;)
On 8/24/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Sounds like the right thing to do.
On 24/08/2007, at 5:47 PM, Carlos Sanchez wro
Hi Lukas,
I don't think that it is confusing: the parent is only used to build
all modules and we deploy artifacts on snapshot repository.
FYI, the "promote-ready" concept is also used in sandbox/trunk/plugins.
I think you could revert them.
Cheers,
Vincent
2007/8/27, Lukas Theussl <[EMAIL PRO
I understand that, but then what confuses me was your previous answer ;)
On 8/24/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> Sounds like the right thing to do.
>
> On 24/08/2007, at 5:47 PM, Carlos Sanchez wrote:
>
> > there must be any problem with the staging settings, I checked that
> > the f
Hi all,
I have a question about documentation generation. We have a lot of
documentation in the apt format (and some in docbook), used to generate
a maven site. A customer has the requirement to have this documentation
in an offline format, PDF would be nice.
I've browsed around a lot and ex
as I understand it, it was never officially endorsed (though if it
works, I'm happy for my vote to remain binding and just get the new
one out ASAP).
- Brett
On 28/08/2007, at 6:36 PM, Carlos Sanchez wrote:
should it? it works
On 8/28/07, Brett Porter <[EMAIL PROTECTED]> wrote:
+1
will
should it? it works
On 8/28/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> +1
>
> will alpha-5 be removed from the sync repository on Apache/central?
>
> Cheers,
> Brett
>
> On 25/08/2007, at 5:36 AM, Carlos Sanchez wrote:
>
> > Milos was right and ARCHETYPE-38 was not properly fixed, and after the
As long as everything is done through the doxia site tools and
reporting implementation modules, and not the doxia sink api and
reporting api modules, then it will be compatible across Maven versions.
- Brett
On 28/08/2007, at 6:17 PM, dvicente wrote:
yes, i think that all internal proces
+1
will alpha-5 be removed from the sync repository on Apache/central?
Cheers,
Brett
On 25/08/2007, at 5:36 AM, Carlos Sanchez wrote:
Milos was right and ARCHETYPE-38 was not properly fixed, and after the
messed up alpha-5 release I'd like to release alpha-6
Issues fixed
ARCHETYPE-38The
yes, i think that all internal process in
org.apache.maven.plugins.site.AbstractSiteRenderingMojo class to configure
the model and the renderer must be pushed in doxia.
With this, when Maven set the siteRenderer component in the report Mojo, the
sink object used by the report is well configured.
You're right - sorry, I was misremembering. I did add enough to bring
in the default skin, but not to read site.xml.
What really needs to happen is for more of the site plugin to be
pushed into the doxia-sitetools, so that they can then be used from
the reporting implementation (as you say)
16 matches
Mail list logo
