Svnsubpub is just ridiculously inefficient and we need to do something
about it...
(insert mandatory rant about how this would be a piece of cake with git
here ->.<- )
Would it be possible to use svn copy to clone some initial structure and
then just synchronize with the generated site ??
Kristi
Absolutely, positively, only source-releases. Those are the only
things that the Foundation sees as 'releases' and wants on /dist.
I've started to cook up some python code to grab them all from nexus;
so far I can tell you that all the source-releases of all the plugins
amount to 65728461 bytes of
> I always execute the maven-failsafe-plugin as well as the
> corresponding report (defined in the parent pom). This project however
> does not have any integration-tests run by failsafe, maybe that is the
> problem?
It's a slight change in behaviour combined by the removal of an empty
catch block
On 22/12/2012, at 9:46 AM, Olivier Lamy wrote:
> 2012/12/21 Benson Margulies :
>> Dear fellow community members,
>>
>> Discussions today have made it clear, to me at least, that we're
>> missing a step in the release procedures for plugins and component
>> (indeed, for everything except 'core'
2012/12/21 Benson Margulies :
> Dear fellow community members,
>
> Discussions today have made it clear, to me at least, that we're
> missing a step in the release procedures for plugins and component
> (indeed, for everything except 'core' releases).
>
> The step is to copy the official release pa
Adding "-DskipITs=true" let's the build succeed.
Regards Mirko
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I put the complete log into a gist: https://gist.github.com/4355893
Regards Mirko
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hello Kristian,
forgot to include maven info:
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /usr/local/Cellar/maven/3.0.4/libexec
Java version: 1.7.0_10, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_10.jdk/Contents/Home/jre
Default locale:
Hello Kristian,
I tried this with two of my pet-projects (one is
https://github.com/1and1/testlink-junit).
I tried mvn-3.0.4 as well as an (unofficial) mvn-3.1.0 version.
While running:
"mvn clean verify"
ran successfully, I got a problem when building the site:
"mvn304 -e -Dapache-pre=maven-06
Brian, can you point me to any thread of that discussion?
I'm not going to pick up the conversational gambit of what the policy
*should* be; I'm already neck deep in that on another thread and I
don't think it will help anyone to start a mirror image of it here.
On Fri, Dec 21, 2012 at 1:19 PM,
On Fri, 21 Dec 2012 20:31:35 +0100
Kristian Rosenvold wrote:
+1 (nonebinding)
works fine to me.
thanks,
tony.
> Hi,
>
> This is the "coconut under christmas tree" edition;
> http://twitpic.com/bnygiy/full .
>
> We solved 26 issues with a thriving community engagement:
> https://jira.codehau
Further to that, no one will ever consume maven plugins from a random dist
folder anyway, so a policy that requires this is a paper policy only and
would have no basis in the reality of how these particular projects are
consumed.
On Fri, Dec 21, 2012 at 1:18 PM, Brian Fox wrote:
> The last disc
The last discussion of this required the production of proper source
bundles for voting, which we created at that time. I don't recall there
being any requirement that everything go onto dist.
On Fri, Dec 21, 2012 at 10:57 AM, Benson Margulies wrote:
> Dear fellow community members,
>
> The curr
Dear fellow community members,
The current official documentation for Apache releases calls for all
releases to be copied to the 'dist' area.
We don't do that for poms and plugins. We just push a source release
zip to repository.apache.org.
Can anyone here help me out by finding a historical thr
it complains if redeploy is not enabled.
On Dec 21, 2012, at 8:32 AM, Anders Hammar wrote:
No, not adding any metadata. But it could always deploy the attached
artifact, without updating the pom. Don't think Nexus will complain about
that.
/Anders
On Fri, Dec 21, 2012 at 12:50 PM, Benson Marg
No, not adding any metadata. But it could always deploy the attached
artifact, without updating the pom. Don't think Nexus will complain about
that.
/Anders
On Fri, Dec 21, 2012 at 12:50 PM, Benson Margulies wrote:
> On Fri, Dec 21, 2012 at 12:54 AM, Anders Hammar wrote:
> >
> >> However, you
On Fri, Dec 21, 2012 at 12:54 AM, Anders Hammar wrote:
>
>> However, you really cannot retroactively deploy an attached artifact
>> for a project, ...
>
>
> I think you can, but could differ between mrm. If it's a good thing is a
> different topic.
I don't see how it can work well. There's only o
On Fri, Dec 21, 2012 at 2:18 AM, Anders Hammar wrote:
> You're looking at the wrong place. The xml stuff is listed early in the
> build output (before any plugin execution), but what you're looking for is
> listed in the beginning of the execution of the plugin in question.
Sure enough. It turns
The Maven team is pleased to announce the release of the Maven Verifier,
version 1.4
This is a shared library for use in testing various Maven components. It
allows the user to execute Maven builds as part of the testing process,
with methods supporting test preparation and assertion of results.
19 matches
Mail list logo
