At this stage would it not be better to move the good content to an ASF
hosted space and just remove the rest?
On 9 December 2013 06:26, Brett Porter br...@apache.org wrote:
The confluence wiki linked from our home page has been inundated with
SPAM. I had been deleting small amounts of it for
Hi Mark.
Yes it is, just define them as dependencies of the maven-release-plugin in
your parent (or otherwise) pom.
-Chris
On Mon, Dec 9, 2013 at 3:23 PM, Mark Derricutt m...@talios.com wrote:
Ok - so this looks to be an issue introduced in Git 1.8.5, from
+1
Am 2013-12-09 09:58, schrieb Stephen Connolly:
At this stage would it not be better to move the good content to an ASF
hosted space and just remove the rest?
On 9 December 2013 06:26, Brett Porter br...@apache.org wrote:
The confluence wiki linked from our home page has been inundated
I am canceling the vote due to some problems with the POM and files
Hervé and me have found. I'll respin the vote today.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
GitHub user kreyssel opened a pull request:
https://github.com/apache/maven-enforcer/pull/6
add a IT case for bannedDependencies in a multi module project
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kreyssel/maven-enforcer
Hi,
Changes since the last release:
http://svn.apache.org/viewvc/maven/skins/tags/maven-skins-8/pom.xml?r1=HEADr2=1377628diff_format=h
Staging repo:
https://repository.apache.org/content/repositories/maven-028/
Can I get some votes here please?
--
Regards,
Igor
On 12/6/2013, 8:11, Igor Fedorenko wrote:
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=18839
There are still a couple of issues left in JIRA:
+1
On Dec 9, 2013, at 10:55 AM, Igor Fedorenko i...@ifedorenko.com wrote:
Can I get some votes here please?
--
Regards,
Igor
On 12/6/2013, 8:11, Igor Fedorenko wrote:
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=18839
There
Igor,
so why did mvn verify work locally with Maven 3.0.5? Is there a test
case missing which triggers the bug?
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Mon, Dec 9,
There are two versions of maven involved during maven-plugin-testing
build -- the version of maven used to run the build and the version of
maven core artifacts maven-plugin-testing depends on. Maven core
dependency version is controlled by maven-plugin-testing pom.xml (see
${mavenVersion}
Hi,
during release preps of 1.3.1 I am constantly failing to build the with
Maven 3.1.1. I do mvn -Preporting site and it dies with
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on
project maven-fluido-skin: Error during site generation:
Have you tried to run it with an extra 'clean'? I've seen this a few times
and IIRC the clean helped.
Robert
Op Mon, 09 Dec 2013 20:47:20 +0100 schreef Michael-O 1983-01...@gmx.net:
Hi,
during release preps of 1.3.1 I am constantly failing to build the with
Maven 3.1.1. I do mvn
Am 2013-12-09 22:23, schrieb Robert Scholte:
Have you tried to run it with an extra 'clean'? I've seen this a few
times and IIRC the clean helped.
No avail. Still the same error. If I leave out the profile reporting it
suddenly works.
Op Mon, 09 Dec 2013 20:47:20 +0100 schreef Michael-O
+1
Regards,
Hervé
Le vendredi 6 décembre 2013 08:11:49 Igor Fedorenko a écrit :
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=188
39
There are still a couple of issues left in JIRA:
AFAIK, this is due to the fact that the skin uses itself, which is a good
thing to show the effective result for people wanting to use it, but it costs
this little problem: the most recent version is the version actually built,
not what is in local repo (at least when working with SNAPSHOT)
so
content${project.build.directory}/staging/${maven.site.path}/content
is not really necessary here, since skins are never multi-module, then no need
to site:stage
that's not a blocking issue, since it will work: just need to do extra
site:stage step, not usually needed
Regards,
Hervé
Le
Am 2013-12-10 00:58, schrieb Hervé BOUTEMY:
content${project.build.directory}/staging/${maven.site.path}/content
is not really necessary here, since skins are never multi-module, then no need
to site:stage
that's not a blocking issue, since it will work: just need to do extra
site:stage step,
Am 2013-12-10 00:54, schrieb Hervé BOUTEMY:
AFAIK, this is due to the fact that the skin uses itself, which is a good
thing to show the effective result for people wanting to use it, but it costs
this little problem: the most recent version is the version actually built,
not what is in local
Le mardi 10 décembre 2013 01:05:30 Michael-O a écrit :
Am 2013-12-10 00:58, schrieb Hervé BOUTEMY:
content${project.build.directory}/staging/${maven.site.path}/content
is not really necessary here, since skins are never multi-module, then no
need to site:stage
that's not a blocking
on my machine, build with Maven 3.1.1 works actually
old 2.4 m-pir-p is used, which doesn't use Aether, so it works both for Maven
3.0.x and 3.1.x
To test a skin, I suppose this old version is sufficient
do you have issues?
Regards,
Hervé
Le mardi 10 décembre 2013 01:12:43 Michael-O a écrit
On 10 December 2013 11:24, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le mardi 10 décembre 2013 01:05:30 Michael-O a écrit :
Am 2013-12-10 00:58, schrieb Hervé BOUTEMY:
content${project.build.directory}/staging/${maven.site.path}/content
is not really necessary here, since skins are never
+1
On 10 December 2013 02:55, Igor Fedorenko i...@ifedorenko.com wrote:
Can I get some votes here please?
--
Regards,
Igor
On 12/6/2013, 8:11, Igor Fedorenko wrote:
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=18839
There are
22 matches
Mail list logo
