I had created a hack of the clirr plugin at a prior employer to compute the
next version number a few years ago (rejected by the mojo project, as
the owners didn't want to start breaking builds with clirr)
We had 50-60 jars and 20+ developers with a range of skill/java knowledge,
some
On Jul 23, 2012, at 1:52 AM, Mark Derricutt m...@talios.com wrote:
On 16/07/12 4:10 PM, Rex Hoffman wrote:
Losing most of my time to cucumber-jvm maven plugins (most of today), and to
the project in general...
Don't think maven land (proper) will see much love until I nail down
:
On Thu, Jul 12, 2012 at 6:54 PM, Barrie Treloar baerr...@gmail.com wrote:
On Thu, Jul 12, 2012 at 2:12 PM, Rex Hoffman r...@e-hoffman.org wrote:
Just a quick mention that there is an annoying bit of logging that is
showing up now in the dependencyConvergence enforcer rule, since the last
release
Just a quick mention that there is an annoying bit of logging that is
showing up now in the dependencyConvergence enforcer rule, since the last
release...
I haven't looked up if I initially added it or not, I suspect if came in
with the Upper bound dependency checker, but don't really have the
That's correct, but you'll then have to query the content handler object for
it's currently running port.
I'm going to keep pimping out this solution I built for some clients and
open sourced a while back.
In one project I have an api for starting up a jetty application server
either off of the
On peripherally maven-dev related, but as thought leaders, I hope you guys
would take interest.
So I've been aggravated that I've had to start a web app up before running a
test in eclipse, given the way we typically run apps with things like the
jetty-maven-plugin (the startup/shutdown pre/post
, at 3:11 PM, Rex Hoffman wrote:
On peripherally maven-dev related, but as thought leaders, I hope you
guys
would take interest.
So I've been aggravated that I've had to start a web app up before
running a
test in eclipse, given the way we typically run apps with things like
Depends on what your running them with. Testng test groups?
I modify them with an @Listener, it servers multiple purposes for us. First
it makes sure there are no misspelled groups,
then if eclipse-testng jar is on the classpath, it runs all groups, ignoring
the group configuration.
We also us
*you're
On Mon, Jul 11, 2011 at 9:01 AM, Rex Hoffman r...@e-hoffman.org wrote:
Depends on what your running them with. Testng test groups?
I modify them with an @Listener, it servers multiple purposes for us.
First it makes sure there are no misspelled groups,
then if eclipse-testng jar
like it has too much in it though, and a good number of implementation
class. Which limits it's ability to be decouple parts of maven
Rex
On Fri, Nov 19, 2010 at 9:15 AM, Jesse Glick jesse.gl...@oracle.com wrote:
On 11/18/2010 07:20 PM, Rex Hoffman wrote:
it's pretty straight forward if you
I have a slight concern.
It goes into testing portability (running in maven, or eclipse, idea,
netbeans, or via command line)
In short, the smarter we make maven about running tests, the less easy it is
for a developer to run that same test via IDE or something similar.
I'll give two common
providers here at apache, with various forks popping up for less-is-more
or more-is-more at github. I kind of like that kind of ecosystem, which
would give a freedom of choice that is not available currently.
Kristian
fr., 19.11.2010 kl. 12.13 -0800, skrev Rex Hoffman:
I have a slight
it's pretty straight forward if you use some code provided by the
dependencies library (part of the maven-dependencies-plugin)
I wrote some code that uses it for the dependency convergence enforcer rule:
Sweet. Very much what I was looking for. May also create a set of java 5
annotations mirroring these.
Rex
On Tue, Nov 9, 2010 at 8:51 AM, Mark Hobson markhob...@gmail.com wrote:
On 9 November 2010 16:30, Rex Hoffman r...@e-hoffman.org wrote:
My thoughts exactly on the annotation ie. hosted
or implements and
decides which segment of the version number to increment based on that.
might be useful...
david jencks
On Nov 9, 2010, at 4:58 AM, Jesse Glick wrote:
On 11/08/2010 02:21 AM, Rex Hoffman wrote:
project: java-version-delta
By the way, you should look at https
...@oracle.com wrote:
On 11/09/2010 02:21 PM, Rex Hoffman wrote:
http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf
Take note of the distinction made on pp. 5-6 between interface and
package. Without some special annotations, it is not possible for a tool
to mechanically decide
a default annotation?
Weighing options, Looking for feedback, ideas to make it better, etc
Thanks,
Rex
On Fri, Nov 5, 2010 at 2:07 PM, Rex Hoffman r...@e-hoffman.org wrote:
Really, this is a question of how apache maven wants to approach the apache
version standard. I'm begin to believe
that happens to use clirr, rather
than a clirr plugin that happens to enforce the apache version standard.
Rex
On Fri, Nov 5, 2010 at 3:32 AM, Mark Hobson markhob...@gmail.com wrote:
On 4 November 2010 18:28, Rex Hoffman r...@e-hoffman.org wrote:
Seems reasonable, build a helper library to run clirr
are providing a clean patch which uses a helper method to
delegate to DefaultArtifactVersion, then I cannot see why this will
not be applied
-Stephen
On 5 November 2010 18:53, Rex Hoffman r...@e-hoffman.org wrote:
Hmm... good point about the phase i'll have to think on that. We can
always
Seems reasonable, build a helper library to run clirr and analyze it's
results, allow the clirr plugin to use it in it's existing manner, or by an
enforcer rule.
That fact that it's clirr under the hood of that enforcer rule will be
completely abstracted. This will be a rule to enforce apache
On Thu, Nov 4, 2010 at 11:28 AM, Rex Hoffman r...@e-hoffman.org wrote:
Seems reasonable, build a helper library to run clirr and analyze it's
results, allow the clirr plugin to use it in it's existing manner, or by an
enforcer rule.
That fact that it's clirr under the hood of that enforcer
, 2010 4:26 PM, Brian Fox bri...@infinity.nu wrote:
Nah, i'll just release it again.
On Thu, Nov 4, 2010 at 2:31 PM, Rex Hoffman r...@e-hoffman.org wrote:
On Thu, Nov 4, 2010 at 11:...
...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Rex Hoffman
(415) 273-9438
415-2REXGET
http://www.e-hoffman.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands
, 2010 at 3:53 PM, Rex Hoffman r...@e-hoffman.org wrote:
I just created a JIRA issue against a standard rule, with a patch:
http://jira.codehaus.org/browse/MENFORCER-109
Obviously I am not an apache member, but I contributed
dependency-convergence enforcer rule (probably with this bug in place
So I have a desire to have maven check prior versions of an artifact
and determine if the apache version standard is being followed.
I had implemented a patch against the clirr plugin in the mojo project
to do this.
http://jira.codehaus.org/browse/MCLIRR-33
It's been several months and this
...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Rex Hoffman
(415) 273-9438
415-2REXGET
http://www.e-hoffman.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
to this thread when they're raised then
I'll track it from there.
Thanks and happy time off!
Mark
On 8 September 2010 18:41, Rex Hoffman r...@e-hoffman.org wrote:
I haven't opened it yet as I still have to separate out functionality,
and write up some info for the site report. Already have
I haven't opened it yet as I still have to separate out functionality,
and write up some info for the site report. Already have the
integration test done.
I just quit my job and have two weeks off until I start my next, last
day, yay! So really good news for you!
I expect to have this split
transitive dependency conflicts are displayed when the rules
detects that it has been violated.
Seems like 2 and 3 are unique enough to make it in as rules?
Rex
On Thu, Aug 26, 2010 at 12:52 AM, Baptiste MATHUS m...@batmat.net wrote:
2010/8/25 Rex Hoffman r...@e-hoffman.org
So I felt
20:00, Rex Hoffman r...@e-hoffman.org wrote:
So I felt there are few gaps in the maven release process (and
enforcing a project or a reactor project is releasable).
Perceived gaps:
1) Maven should fail a build if it is building a release version
number and any of it's dependencies (including
30 matches
Mail list logo
