Looking good, very good.
Robert
Op Mon, 04 May 2015 22:16:32 +0200 schreef Baptiste Mathus
:
I just drafted that for informing about the ML terminations:
https://github.com/mojohaus/mojohaus.github.io/wiki/Termination-mail
WDYT?
2015-05-04 21:49 GMT+02:00 Robert Scholte :
some
nyway.
- Announcements List : same as user list. I don't see us keeping it;
WDYT? Do you agree?
2015-05-04 20:38 GMT+02:00 Robert Scholte :
If the google group is fully up and running, then I don't see any reason
for voting.
You could do a (pre-)announcement saying this ML wi
hortcut option. Would you prefer to have a vote for that and
reconsider where we go for the MLs?
2015-05-04 19:41 GMT+02:00 Robert Scholte :
Hi,
I don't think we have a real choice here. Once the Codehaus domain is
gone
including its infra then there are no mailinglists anymore.
The vote
Hi,
I don't think we have a real choice here. Once the Codehaus domain is gone
including its infra then there are no mailinglists anymore.
The vote should be about the move to X and how to register it for Markmail
and Nabble.
Robert
Op Mon, 04 May 2015 15:36:52 +0200 schreef Baptiste Mathu
+1
Op Sun, 03 May 2015 21:48:41 +0200 schreef Baptiste Mathus
:
Hi all,
As a followup to previous threads, I guess it's time for us to try and
move
on.
Indeed, the announcement says services should be shut down the 17 May.
So, to go forward, I'd like to ask Codehaus support to put the S
Paul Hammant(cc) did a Jira export for QDox[1]
IMHO that's complete enough.
If we agree on such approach, Paul can probably help us or give the
instructions how he did it.
thanks,
Robert
[1] http://paul-hammant.github.io/Old_Qdox_Issues/
Op Thu, 09 Apr 2015 17:14:52 +0200 schreef Baptiste M
Hi,
Don't expect http://jira.codehaus.org/browse/HAUS-2412 to be fixed, we're
moving to https://github.com/mojohaus
See the mailinglist for Codehaus EOL.
Robert
Op Wed, 08 Apr 2015 23:32:35 +0200 schreef Jörg Hohwiller
:
Hi there,
I refactored the flatten-maven-plugin and completed the
Title: Message Title
Robert Scholte closed an issue as Fixed
+1 for MojoHaus
Op Wed, 11 Mar 2015 12:06:34 +0100 schreef Brett Okken
:
+1 for MojoHaus
On Mar 11, 2015 4:35 AM, "Stephen Connolly"
wrote:
On 11 March 2015 at 07:54, Hervé BOUTEMY wrote:
then we have a few proposals:
- Mojo Extras
- MojoHaus
- The Mojo Project
I really like MojoH
+1
Op Mon, 02 Mar 2015 08:51:58 +0100 schreef Baptiste Mathus
:
Well, since this didn't seem to trigger counter opinions I'm starting a
formal vote.
That vote is to deprecate the shitty-maven-plugin, and move it to the
mojo's graveyard.
[ ] +1 : deprecate it
[ ] 0 : don't care
[ ] -1: don'
IMHO the Apache Maven team should focus on Maven Core, (java)-build
lifecycle plugins, plugin-development tools, transport (SCM, Wagon) and
project-health tools.
There are probably a couple of Codehaus-Mojo plugins which might be
interesting to move Apache Maven (assuming legal issues will
+1
Op Wed, 25 Feb 2015 18:14:00 +0100 schreef Stephane Nicoll
:
Hi,
This release brings full Java8 compatibility thanks to MANIMALSNIFFER-51
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12070&version=20742
There are still 20 issues left in JIRA:
http://ji
reserved for Apache Maven, we might want to
call it dependable-pom.
WDYT?
Robert
Op Sat, 14 Feb 2015 12:17:45 +0100 schreef Robert Scholte
:
Hi Jörg,
I think your adjustment of rev. 20330 to the
optional-elements-modeMinimum/verify.groovy is incorrect.
This project results in a jar so
Hi Jörg,
I think your adjustment of rev. 20330 to the
optional-elements-modeMinimum/verify.groovy is incorrect.
This project results in a jar so there's no reason to keep
dependencyManagement here: all dependencies should be resolved.
What I'm missing is a project *using* this bom. I seem t
Op Tue, 10 Feb 2015 14:26:57 +0100 schreef Anders Hammar
:
I would recommend that we migrate to the following requirement for all
our
plugins:
1. Minimum Maven version 3.0.4 (i.e. drop support for Maven 2.x)
As discussed (and concluded) somewhere else, we should go with a Maven
3.0
2015-02-07 10:55 GMT+01:00 Robert Scholte :
From a user/community perspective I would go for 3.0 as a minimum.
Testing with a wide range of versions would be good.
So the minimum (3.0) and the latest (3.2.5 if available on Bamboo) would
already cover a lot.
Op Sat, 07 Feb 2015 10:51:50 +0100 sc
,
I took the version defined/used by the Codehaus Bamboo servers for ITs.
I can easily pick another version for more sensible reasons.
Which 3.0.x version is the better one to use?
(I suppose I should adjust the bamboo jobs as well, right?)
2015-02-07 10:29 GMT+01:00 Robert Scholte :
Hi Lennart
Hi Lennart,
Why 3.0.4? This version has a security issue[1] fixed in 3.0.5 (it is
actually the only fix in 3.0.5).
And it is probably easier to say the plugin is Maven3 compatible, which
implies at least Maven 3.0.
Is there a specific interface change in 3.0.4 you depend on?
thanks,
Robert
Title: Message Title
Robert Scholte commented on an issue
Op Sun, 18 Jan 2015 00:01:16 +0100 schreef Jörg Hohwiller
:
Hi there,
I would like to open a discussion about the design of
flatten-maven-plugin.
Important issue is http://jira.codehaus.org/browse/MOJO-2041
Therefore I already applied the old code back onto trunk and did some
rework.
1. I
Title: Message Title
Robert Scholte closed an issue as Duplicate
Title: Message Title
Robert Scholte closed an issue as Fixed
Title: Message Title
Robert Scholte closed an issue as Fixed
Title: Message Title
Robert Scholte closed an issue as Fixed
Title: Message Title
Robert Scholte created an issue
Title: Message Title
Robert Scholte assigned an issue to Robert Scholte
Title: Message Title
Robert Scholte created an issue
Title: Message Title
Robert Scholte created an issue
/MOJO-2042
I would like to finally pull out beta3. Before that I would like to know
if there are any concerns (esp. according to MOJO-2042).
Regards
Jörg
Am 21.10.2014 19:40, schrieb Robert Scholte:
I think reverting is the best option right now.
Robert
Op Mon, 20 Oct 2014 22:53:33 +0200 schr
that prevents core usage of flatten-maven-plugin in some
cases what is rather bad.
Unfortunately SVN is not very strong on feature branches and merging. I
am spoiled by git and other more agile infrastructure now...
Regards
Jörg
Am 19.10.2014 22:34, schrieb Robert Scholte:
I've seen a l
you might consider it as "abusage" - if you keep all
elements then flatten-maven-plugin is not really flattening but can help
you with resolving variables. Do you want to argue that someone should
be forced to use a different plugin for his purpose then?
Regards
Jörg
Am 15.10.2014 2
Hi Jörg,
I don't think this is correct. The whole idea is that:
- pom projects should stay as they are
- non-pom files should be flattened, meaning mainly resolving dependencies.
so parent, modules, properties and reporting are already included for the
first, and should *never* be added to the
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte closed an issue as Not A Bug
Title: Message Title
Robert Scholte closed an issue as Not A Bug
s(
repo.getUrl() ) )
{
if ( !repo.getSnapshots().isEnabled() )
{
return true;
}
}
}
return false;
}
Any ideas what makes the difference? Different maven version using
different super POM with central URL pointing to
Hi,
I still consider Maven as a language independent build management tool.
In case of the enforceBytecodeVersion I think we should add an API so it
can be implemented for other packaging types as well.
Shouldn't be too hard to do so, just needs to be done.
@Stephen, which other rules do you h
Hi,
FYI: I'm having the same issue as Karl-Heinz: the external-parent IT fails.
I've checked out
http://svn.codehaus.org/mojo/tags/flatten-maven-plugin-1.0.0-beta-3/
and executed 'mvn verify'.
Robert
Op Sun, 28 Sep 2014 20:42:28 +0200 schreef Jörg Hohwiller
:
Hi Karl Heinz,
thanks aga
+1
Robert
Op Sat, 20 Sep 2014 09:48:49 +0200 schreef Baptiste Mathus
:
Hi,
I'd like to release version 1.0-beta-3 of the extra-enforcer-rules
project.
That project provides additional rules for the Apache Maven's Enforcer
Plugin.
We solved 3 issues:
http://jira.codehaus.org/browse/MOJ
go ahead,
Robert
Op Wed, 24 Sep 2014 07:57:46 +0200 schreef Hervé BOUTEMY
:
I'd like to release a new mojo-parent version with updated plugins
any objection?
anything someon want to do before the release?
Regards,
Hervé
---
Just quoting the ajdoc-ref[1]
"ajdoc currently requires the tools.jar from J2SE 1.3 to be on the
classpath. Normally the scripts set this up, assuming that your JAVA_HOME
variable points to an appropriate installation of Java. You may need to
provide this jar when using a different version
Current trunk runs fine on my system:
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: D:\apache-maven-3.0.5\bin\..
Java version: 1.7.0_55, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_55\jre
Default locale: nl_NL, plat
painless.
2014-09-08 19:29 GMT+02:00 Robert Scholte :
This is an interesting case, because the compile-time JDK is less then
the
runtime JDK (1.5 and 1.6 in same order). Normally it's the other way
around.
However, to be able to run the integration tests, you will still need
1.6.
So I&
ould be overly
complex.
Unless someone has strong opinions for another approach, I intend
to:
- Remove the bytecode-level enforcement from the a-m-p POM, as
per
the thoughs under 1 above.
- Keep the tools.jar dependency in the a-m-p POM, as per the
thoughts under 3 above.
2014-
Maybe the difference between String and GString[1]
equals should always work
Robert
[1] http://groovy.codehaus.org/Strings+and+GString
Op Thu, 04 Sep 2014 21:59:54 +0200 schreef Jörg Hohwiller
:
Hi there,
I am not a groovy expert and need some help.
An IT of flatten-maven-plugin fails wit
Hi,
If you compare the differences between Apaches PMC and teammembers, then
the difference between a Codehaus despot and teammember is much smaller.
Teammembers already have a lot of rights for the infrastructure[1],
there's no such thing as binding votes. Main difference between a despot
Hi,
read http://www.codehaus.org/customs/licenses.html
The advice is to use ASL2, although MIT is permitted.
I want to hear the facts why "they say" MIT would be better.
Robert
Op Wed, 03 Sep 2014 21:40:48 +0200 schreef Dan Tran :
OK, They are not my plugins, they belong to MOJO@codehaus
th
ely be the same as setting a *maximum* JDK version.
2014-09-02 23:30 GMT+02:00 Robert Scholte :
Hi,
I've added the enforceBytecodeVersion rule to see which jar(s) are
causing
problems.
It seems that aspectjtools can't run with JDK5.
As long as org.aspectj.tools.ajc.Main.Main() is c
a new JVM, preferably with toolchains to manage
the JDK versions. Not sure if it's worth it to implement, though.
For me this is a valid reason to change the required JDK, I'll leave it up
to you.
Robert
Op Tue, 02 Sep 2014 23:00:26 +0200 schreef Robert Scholte
:
Hi,
I&#
Hi,
I've fixed the unittest, next step is to fix the integration tests.
I've added a JDK8 task to the integration tests, so now it will be tested
with the minimum (JDK5) and maximum, both with Maven-2.2.1.
There are only linux bambooo-agents available right now. According to
JIRA[1] there has
Title: Message Title
Robert Scholte edited a comment on an issue
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte edited a comment on an issue
Title: Message Title
Robert Scholte closed an issue as Fixed
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte closed an issue as Fixed
Title: Message Title
Robert Scholte closed an issue as Fixed
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte updated an issue
Title: Message Title
Robert Scholte updated an issue
Title: Message Title
Robert Scholte updated an issue
Title: Message Title
Robert Scholte created an issue
Shouldn't it be 2.5.5 instead of 3.0.0?
Robert
Op Fri, 25 Jul 2014 17:16:17 +0200 schreef :
Revision:
19892
Author:
gleclaire
Date:
2014-07-25 10:16:17 -0500 (Fri, 25 Jul 2014)
Log Message
findbugs-maven-plugin 3.0.0 release
Modified Paths
site/src/site/apt/plugins.apt
Diff
Modified
Op Fri, 25 Jul 2014 17:16:17 +0200 schreef :
Revision:
19892
Author:
gleclaire
Date:
2014-07-25 10:16:17 -0500 (Fri, 25 Jul 2014)
Log Message
findbugs-maven-plugin 3.0.0 release
Modified Paths
site/src/site/apt/plugins.apt
Diff
Modified: site/src/site/apt/plugins.apt (19891 => 19892)
lists help goal (other goals
missing in list)
* [MMOCKRM-11] - Param propertyName should have a default value
* [MMOCKRM-13] - downloading /favicon.ico throws an
emptyStackException
** Improvement
* [MMOCKRM-12] - Expose settings.xml for non-localhost users
Enjoy,
The Mojo tea
The vote has passed with the following result:
+1 : Karl Heinz Marbaise, Robert Scholte
0 :
-1 :
I'll proceed with the release process.
thanks,
Robert
Op Fri, 04 Jul 2014 18:06:52 +0200 schreef Robert Scholte
:
Hi,
I'd like to release version 1.0-beta-2 of the Mock Reposito
+1
Op Fri, 04 Jul 2014 18:06:52 +0200 schreef Robert Scholte
:
Hi,
I'd like to release version 1.0-beta-2 of the Mock Repository Manager
The Mock Repository Manager suite of projects are used to provide mock
or lightweight Maven Repository Managers for use during integration
te
Hi,
I'd like to release version 1.0-beta-2 of the Mock Repository Manager
The Mock Repository Manager suite of projects are used to provide mock or
lightweight Maven Repository Managers for use during integration testing
of Maven plugins.
We solved 4 issues:
http://jira.codehaus.org/secure
cts at work as well ( we adopt maven code style
and
svn).
import-codehaus-certificate is very helpful, try to read the
instructions
from Codehaus and import manually is a pain IMO
Thanks
-Dan
On Mon, Jun 30, 2014 at 2:32 PM, Robert Scholte <
codeh...@sourcegrounds.com> wrote:
Hi
to rename 'prepare-environment' back to
'import-codehaus-certificate' ( rather then removing it) and call it
alpha,
to let ppl know it it very specify MOJO at codehaus development.
Thanks
-Dan
On Sun, Jun 29, 2014 at 12:25 PM, Robert Scholte
wrote:
This is exactly the
ce other project can use it as
well including my internal plugin development. BTW, I have a really need
for this.
What would it take todo so? should we push it as alpha while waiting for
more concrete decision?
-D
On Sun, Jun 29, 2014 at 2:33 AM, Robert Scholte
wrote:
Hi Dan,
I see
prepare-environment, perhaps I should change
it
back to 'import-codehaus-certificates.
Thoughts?
Thanks
-Dan
On Sat, Jun 28, 2014 at 3:08 AM, Robert Scholte
wrote:
I agree with Baptiste here.
I'm also wondering if this project should be pushed to Maven central,
since it
I agree with Baptiste here.
I'm also wondering if this project should be pushed to Maven central,
since it's first of all a codehaus mojo specific plugin.
so -1
Robert
Op Sat, 28 Jun 2014 00:19:47 +0200 schreef Baptiste Mathus
:
I'm not personally worried, actually. I didn't make the
Hi Dan,
just a thought: how about changing the goals to:
* prepare-environment or prepare-system
* prepare-eclipse
* prepare-project
this way it's possible to do additional tasks without creating new goals,
since these tasks should all be done when preparing X.
Based on http://mojo.codehaus.or
+1 for the m-dependency-p
Op Mon, 23 Jun 2014 01:08:09 +0200 schreef Stephen Connolly
:
Ancestors are dependencies, you cannot build a project without its
parent... You just don't reference them in a dependencies section is all!
I think it actually would suit perfectly in dependency:tree (e
IIRC to be compatible with Maven 2.0.6
I think I did this together with Mark.
I'm pretty sure you'll discover it ones you remove it.
Robert
Op Mon, 23 Jun 2014 20:30:08 +0200 schreef Karl Heinz Marbaise
:
Hi,
just a question concerning the SQL Maven Plugin...
can someone give me hint why
It's not mine, it's Lennarts.
This happens when you generate your keys multiple times. For instance, if
you reinstall your machine are have a new one. These keys will then be
merged. That happened to me about 3 times, so mines a bit longer than the
average one.
It shouldn't be an issue, al
ignore, wrong list...
Op Sat, 21 Jun 2014 22:28:05 +0200 schreef Robert Scholte
:
Hi all,
40% of the current open issues are related to QDox-attributes and
QDox-XML.
QDOX-20[1]: Migrate qdox-attributes and qdox-xml to maven 2
QDOX-21[2]: Upload website for qdox-xml and qdox-attributes
Hi all,
40% of the current open issues are related to QDox-attributes and QDox-XML.
QDOX-20[1]: Migrate qdox-attributes and qdox-xml to maven 2
QDOX-21[2]: Upload website for qdox-xml and qdox-attributes
They're open for about 5 years, so to me it looks like there's not enough
interest for it to
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte commented on an issue
Try https://bamboo-ci.codehaus.org/userlogin!default.action
Robert
Op Fri, 30 May 2014 23:52:39 +0200 schreef Dan Tran :
I am not able to login into it.
Can someone confirm?
-D
-- Forwarded message --
From: Codehaus Bamboo
Date: Fri, May 30, 2014 at 10:46 AM
Subject: [Bambo
Op Thu, 29 May 2014 22:54:17 +0200 schreef Jörg Hohwiller
:
Hi,
Hi Jörg,
Hi Robert,
I very much appreciate your support and contribution.
However, your "in the middle of the discussion" commit caused me some
SVN conflict and merge trouble.
I did my best to resolve but as a consequence rem
Op Tue, 27 May 2014 22:37:50 +0200 schreef Jörg Hohwiller
:
Am 26.05.2014 21:03, schrieb Robert Scholte:
Hi Jörg,
Hi Robert,
I very much appreciate your support and contribution.
However, your "in the middle of the discussion" commit caused me some
SVN conflict and merge trouble
Try using https instead of http
Robert
Op Tue, 27 May 2014 16:26:13 +0200 schreef Julien HENRY :
The problem with Nexus is now fixed. I'm now stopped at step:
Update the plugins.apt document to reflect the new release. Redeploy the
mojo site by executing mvn site-deploy and verify that it i
blog.sonatype.com/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/
Op Sun, 25 May 2014 23:27:35 +0200 schreef Jörg Hohwiller
:
Am 24.05.2014 12:03, schrieb Robert Scholte:
Hi,
Hi Robert,
seems like I missed a mail.
no worries...
What I don't understand is why you
Title: Message Title
Robert Scholte closed an issue as Fixed
so specify a path such as
${basedir}/flatten-custom.xml that would be
loaded as file.
Did I get it right? Or do you only want me to put the current config
options into a container element (pomDescriptor) so future Maven
features could help with some magic I can not see yet?
Best regards
Jörg
A
Title: Message Title
Robert Scholte created an issue
Title: Message Title
Robert Scholte commented on an issue
Title: Message Title
Robert Scholte closed an issue as Fixed
Title: Message Title
Robert Scholte assigned an issue to Robert Scholte
Title: Message Title
Robert Scholte created an issue
MD*B*UPGRADE instead of MDPUPGRADE
Op Thu, 15 May 2014 22:29:10 +0200 schreef Dan Tran :
um, what should it be?
Thanks for watching
-D
On Thu, May 15, 2014 at 1:26 PM, Robert Scholte
wrote:
Dan,
https://jira.codehaus.org/browse/HAUS-2379 has the wrong title, which
might result in an
Dan,
https://jira.codehaus.org/browse/HAUS-2379 has the wrong title, which
might result in an unwanted Jira key for the project
Robert
Op Thu, 15 May 2014 21:12:16 +0200 schreef Dan Tran :
Thanks Robert
-Dan
On Thu, May 15, 2014 at 11:57 AM, Robert Scholte
wrote:
These are your
1 - 100 of 1626 matches
Mail list logo
