Re: Did you see dependabot?

[Martijn Dashorst]

Now there's a LEGAL ticket for that:

https://issues.apache.org/jira/browse/LEGAL-491

With a comment from Mark Thomas that this is no different than a
committer running a local tool, reviewing the commit and pushing it.

Read his comment on the ticket for more information and advice.

Martijn

On Sat, Oct 19, 2019 at 8:51 PM Enrico Olivelli  wrote:
>
> I see value in it.
> But from a legal point of viewthere is no human who sends the PR, so in
> theory we cannot accept such patches, can we?
>
> Enrico
>
> Il sab 19 ott 2019, 20:26 Tibor Digana  ha scritto:
>
> > The dependabot looks interesting, cli has more possibilities than a pure
> > button on GUI.
> > >> does anyone enabled it
> > I am all the ear how it can be enabled.
> >
> > On Fri, Oct 18, 2019 at 3:32 PM Enrico Olivelli 
> > wrote:
> >
> > > Hey guys,
> > > Did you see dependabot on our repos?
> > >
> > > Like this automatic PR
> > >
> > >
> > https://github.com/apache/maven-plugins/pull/147#pullrequestreview-303889692
> > >
> > > I feel this is very useful, but... does anyone enabled it?
> > >
> > > Do we have to set a policy, this suggestions are security related fixes,
> > we
> > > could give them some kind of high priority?
> > >
> > > Enrico
> > >
> >



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Did you see dependabot?

[Martijn Dashorst]

The conclusion of the paper itself is 3 pages (no paragraphs, so it
might be written by an AI ;-).

- Dutch (and international) copyright law don't require a copyright
holder to be human
- so the work itself needs to be evaluated, two criteria that factor
into this; requirement of reflecting an original expression and the
carrying of a personal imprint
- original expression is feasible for AIs (according to author)

The author lost me at the reasoning for "personal imprint".

Martijn

On Tue, Oct 29, 2019 at 11:18 AM Paul Hammant  wrote:
>
> Summary ?



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Did you see dependabot?

[Martijn Dashorst]

On Sat, Oct 19, 2019 at 8:51 PM Enrico Olivelli  wrote:
>
> I see value in it.
> But from a legal point of viewthere is no human who sends the PR, so in
> theory we cannot accept such patches, can we?

I'm not a lawyer, nor a scientist, but this paper sounds like a
compelling read on this subject:

http://arno.uvt.nl/show.cgi?fid=145318

Martijn

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Maven incremental build for BIG-sized projects with local and remote caching

[Martijn Dashorst]

On Thu, Sep 19, 2019 at 7:48 AM Alexander Ashitkin
 wrote:
> Configuration:
> * verify -T4 -P default,all-shapshots-repos
> * my project config (might be suboptimal for wicket)
> * scala tests disabled in 2 modules (caused bytecode version conflict on my 
> machine)
>
> Results
> Clean state (cache disabled):   15:58 min
> Second run, target up to date (cache disabled):  10:20 min
> Fully cached (no changes):  17.507 s
> wicketstuff-jwicket-tooltip-wtooltips changed:  34.936 s
> wicketstuff-rest-utils changed: 54.040 s
>
> If you want to try other modules - please let me know.

Nice results!

> regarding ide - it's a usual maven installation, so any ide with maven 
> integration should benefit from cache them maven action invoked

My instinct says that an IDE as Eclipse won't benefit much from it, as
it has its own build lifecycle. Only when you invoke a commandline
Maven action (such as generate-sources) one might have a benefit.

So in the day-to-day life the caching might not be as beneficial for
developers, but commandline builds happen often enough to make this
matter.

Martijn

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Maven incremental build for BIG-sized projects with local and remote caching

[Martijn Dashorst]

This seems like it would benefit a lot of projects (at least it would ours).

How would this work in coordination with IDE's? m2e has (afaict, but
haven't looked closely) its own lifecycle management to bridge eclipse and
maven. AFIAK only Netbeans uses maven directly?

If you want to benchmark a public big repo, you can use Wicket Stuff Core (
https://github.com/wicketstuff/core). It has 237 modules, and the build
takes quite a while to compile and package. The project levels are not
deep, but there's some nesting.

Martijn


On Fri, Sep 13, 2019 at 10:46 PM Maximilian Novikov <
maximilian.novi...@db.com> wrote:

> Hi All,
>
>
>
> *We want to create upstream change to Maven* to support true incremental
> build for big-sized projects.
>
> To raise a pull request we have to pass long chain of Deutsche Bank’s
> internal procedures. So, *before starting the process we would like to
> get your feedback regarding this feature*.
>
>
>
> *Motivation:*
>
>
>
> Our project is hosted in mono-repo and contains ~600 modules. All modules
> has the same SNAPSHOT version.
>
> There are lot of test automation around this, everything is tested before
> merge into release branch.
>
>
>
> Current setup helps us to simplify build/release/dependency management for
> 10+ teams those contribute into codebase. We can release everything in
> 1-click.
>
> The major drawback of such approach is build time: *full local build took
> 45-60 min (*-T8)*, CI build ~25min(*-T16*)*.
>
>
>
> To speed-up our build we needed 2 features: incremental build and shared
> cache.
>
> Initially we started to think about migration to Gradle or Bazel. As
> migration costs for the mentioned tools were too high, we decided to add
> similar functionality into Maven.
>
>
>
> Current results we get: *1-2 mins for local build(*-T8*)* if build was
> cached by CI*, CI build ~5 mins (*-T16*).*
>
>
>
> *Feature description:*
>
>
>
> The idea is to calculate checksum for inputs and save outputs in cache.
>
> [image: image2019-8-27_20-0-14.png]
>
> Each node checksum calculated with:
>
>
>
> · Effective POM hash
>
> · Sources hash
>
> · Dependencies hash (dependencies within multi-module project)
>
>
>
> Project sources inputs are searched inside project + all paths from
> plugins configuration:
>
> [image: image2019-8-30_10-28-56.png]
>
> How does it work in practice:
>
>
>
> 1.   CI: runs builds and stores outputs in shared cache
>
> 2.   CI: reuse outputs for same inputs, so time is decreasing
>
> 3.   Locally: when I checkout branch and run ‘install’ for whole
> project, I get all actual snapshots from remote cache for this branch
>
> 4.   Locally: if I change multiple modules in tree, only changed
> subtree is rebuilt
>
>
>
> Impact on current Maven codebase is very localized (MojoExecutor, where we
> injected cache controller).
>
> Caching can be activated/deactivated by property, so current maven flow
> will work as is.
>
>
>
> And the big plus is that you don’t need to re-work your current project.
> Caching should work out of box, just need to add config in .mvn folder.
>
>
>
> Please let us know what do you think. We are ready to invest in this
> feature and address any further feedback.
>
>
>
> Kind regards,
>
> Max
>
>
>
>
> ---
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and delete this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
>
> Please refer to https://www.db.com/disclosures for additional EU
> corporate and regulatory disclosures and to
> http://www.db.com/unitedkingdom/content/privacy.htm for information about
> privacy.
>


-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

Re: Summary of meeting about Maven performance improvements

[Martijn Dashorst]

There's this umbrella of projects called Wicket Stuff at github.

https://github.com/wicketstuff/core

It has a typical long build time, but not a very complicated setup
(e.g. the depth of nested projects is about 3 max)

You might consider using this as a public benchmark.

Looking forward to improvements in build times.

Martijn

On Wed, Apr 24, 2019 at 8:30 PM Arnaud Héritier  wrote:
>
> Great findings then!
> It’s not easy to catch and my experience is that such big projects are
> often in corporate environments which aren’t open at all and not really
> working with oss projects thus it’s not surprising to have this surfacing
> on Gradle support side.
>
> Le mer. 24 avr. 2019 à 19:09, Karl Heinz Marbaise  a
> écrit :
>
> > Hi,
> >
> > On 24.04.19 17:52, Robert Scholte wrote:
> > > On Wed, 24 Apr 2019 12:45:42 +0200, Arnaud Héritier
> > >  wrote:
> > >
> > >> Just for my knowledge, is it a regression in a recent version or it is
> > >> like
> > >> this for ages ?
> > >
> > > It is like this for ages. AFAIK nobody of the team monitored memory
> > > consumption, focus was on correct + "readable" code.
> >
> > I had done some investigations a longer time ago...related to MNG-6030
> > https://github.com/khmarbaise/maven-test-project-generator
> >
> > and yes it's not a regression...
> >
> > Kind regards
> > Karl Heinz
> >
> > >
> > > Robert
> > >
> > >>
> > >>
> > >> Le mer. 24 avr. 2019 à 10:56, Benedikt Ritter  a
> > >> écrit :
> > >>
> > >>> Am Mi., 24. Apr. 2019 um 10:50 Uhr schrieb Benedikt Ritter <
> > >>> brit...@apache.org>:
> > >>>
> > >>> > Hello,
> > >>> >
> > >>> > this is a summary of a video conference call that happened yesterday
> > >>> > (April 24).
> > >>> >
> > >>>
> > >>> Sorry, actually yesterday was April 23... :o)
> > >>>
> > >>>
> > >>> >
> > >>> > Topic:
> > >>> > Discussion about performance improvements that have been proposed by
> > >>> > Stefan Oehme, namely:
> > >>> >
> > >>> > - [MNG-6638] - Prevent reparsing POMs in MavenMetadataSource (
> > >>> > https://github.com/apache/maven/pull/244)
> > >>> > - [MNG-6633] - Reduce memory usage of excludes (
> > >>> > https://github.com/apache/maven/pull/243) - Speed up project
> > >>> discovery (
> > >>> > https://github.com/apache/maven/pull/242) - Make location handling
> > >>> more
> > >>> > memory efficient (https://github.com/codehaus-plexus/modello/pull/31
> > )
> > >>> >
> > >>> > The goal of this call was to give some more insights into how Stefan
> > >>> found
> > >>> > the improvements and to better understand what is missing before
> > these
> > >>> > changes be merged.
> > >>> >
> > >>> > Attendees of the call:
> > >>> > - Benedikt Ritter (Gradle Inc.)
> > >>> > - Stefan Oehme (Gradle Inc.)
> > >>> > - Robert Scholte (Apache Maven Team)
> > >>> > - Hervé Boutemy (Apache Maven Team; joined about half an hour after
> > >>> the
> > >>> > call started)
> > >>> >
> > >>> > Summary:
> > >>> >
> > >>> > Stefan gave some insights into how he discovered bottlenecks in
> > Maven:
> > >>> >
> > >>> >-
> > >>> >
> > >>> >One of our customers has a huge Maven build:
> > >>> >-
> > >>> >
> > >>> >   Lots of sub projects (2000)
> > >>> >   -
> > >>> >
> > >>> >   Lots of entries in dependency management (4000)
> > >>> >   -
> > >>> >
> > >>> >   Results in a lot of garbage collection
> > >>> >   -
> > >>> >
> > >>> >Problems discovered in that build:
> > >>> >-
> > >>> >
> > >>> >   Re-parsing project POMs during dependency resolution
> > >>> >   -
> > >>> >
> > >>> >   Model objects are too large because of location tracking
> > >>> >   -
> > >>> >
> > >>> >   Low-level bottlenecks in project discovery (especially version
> > >>> >   parsing)
> > >>> >   -
> > >>> >
> > >>> >Customer now has a Maven fork with the proposed changes included:
> > >>> >-
> > >>> >
> > >>> >   1h 50min, 12GB RAM without changes
> > >>> >   -
> > >>> >
> > >>> >   45min, 8GB RAM with changes
> > >>> >
> > >>> >
> > >>> > Robert:
> > >>> >
> > >>> >-
> > >>> >
> > >>> >How to ensure that improvements are not broken?
> > >>> >-
> > >>> >
> > >>> >No answer to how to test this
> > >>> >
> > >>> >
> > >>> > Stefan gave some insights into how performance testing works in the
> > >>> Gradle
> > >>> > project:
> > >>> >
> > >>> >-
> > >>> >
> > >>> >Build has a project generator
> > >>> >-
> > >>> >
> > >>> >Create different projects in different shapes (e.g. lots of
> > >>> >subprojects, deeply nested projects) during the build
> > >>> >-
> > >>> >
> > >>> >Download old Gradle version and run the build on generated
> > projects
> > >>> >-
> > >>> >
> > >>> >Run build again with current Gradle version
> > >>> >-
> > >>> >
> > >>> >Compare results
> > >>> >-
> > >>> >
> > >>> >use statistic methods to filter out variance
> > >>> >-
> > >>> >
> > >>> >Downside to this approach is that it requires a lot of

Re: Build vs Consumer POM study

[Martijn Dashorst]

Just to throw this out there:

The consumer POM should only contain the non-dynamic bits that can
change outside the scope of the artifacts that are described by the
POM.

The consumer POM should consist of only the invariant parts of the
released artifacts: coordinates, dependencies, license, There should
never be a reason to modify a released POM due to a project moving
from one location to another (e.g. codehaus to github, self-hosted
build to travis, self-hosted nexus to apache).

Next to the consumer POM the Maven build should also deploy the full
POM, e.g. pom-build.xml or pom-original.xml. This allows for
researchers and others to continue to analyse the original file(s).

If you're going to keep the CI, Issue tracker, etc information in the
consumer POM, why change at all?

Just my 2 cents.

Martijn


On Wed, Mar 14, 2018 at 11:38 PM, Hervé BOUTEMY  wrote:
> Le mercredi 14 mars 2018, 09:10:20 CET Robert Scholte a écrit :
>> The more I think about this, the more I believe we should approach this a
>> little bit different.
>>
>> There are discussions which parts should be part and which shouldn't. But
>> is this up to us/Maven?
> I don't get the intend here
>
>> How about removing those bits that are useless, i.e build and reporting
>> and I tend to agree on distributionmanagement. These are all instructions
>> specifically for building, reporting and its distribution and does not add
>> value once deployed.
>> If there are additional elements that users want to remove, they can
>> decide to use the flatten-maven-plugin.
> what is hard here is to really define the consumer features, for example on
> profiles or dependencyManagement or repositories. But for the few pure
> descriptive fields that are discussed (like ciManagement), there is no long
> discussion: we'll keep them in the consumer POM, they don't really hurt common
> understanding
>
>>
>> There is another proposal, the pdt-  or project dependency trees-file[1],
>> which will the ultimate and optimized consumer-file.
> yes, in the future, when consumer poms are a reality and we get all the
> implications, we can eventually create a completely new format, why not.
> IMHO, this first step of consumer vs build POM as consumer = subset of POMv4
> and build POM is full POMV4 and newer is a crucial step before discussing more
> disruptive evolution
>
> Regards,
>
> Hervé
>
>>
>> I also have demands about the implementation, but I'll put that in a
>> separate mail. It requires a detailed story and maybe some drawings to
>> fully understyand it.
>>
>> thanks,
>> Robert
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/MAVEN/Project+Dependency+Trees+s
>> chema
>>
>>
>> On Sun, 11 Mar 2018 18:03:07 +0100, Hervé BOUTEMY 
>>
>> wrote:
>> > Hi,
>> >
>> > I wrote a Proposal in the Wiki about Build vs Consumer POM [1] and coded
>> > a
>> > simplified model for the Consumer POM [2]
>> > As written in the proposal, this would permit us to create new POM
>> > versions
>> > that change everything but not the Consumer POM part without breaking any
>> > compatibility with existing Central repository users: build element is
>> > the
>> > main element that could be changed, adding new build
>> > features/configuration
>> > without affecting consumers.
>> >
>> > In addition to reviewing choices proposed for majority of POM elements,
>> > there
>> > are 4 elements that require more discussion:
>> > - contributors
>> > - mailingLists
>> > - repositories
>> > - profiles/activation
>> >
>> > Any thoughts?
>> >
>> > On the code, IMHO, the only missing part is a test of
>> > flatten-maven-plugin to
>> > check that everything works as expected in any situation.
>> > And I suppose a discussion on what we do for the xsd
>> >
>> > Then we should be able to use this strategy for our own artifacts, before
>> > updating POM model version in any newer Maven version starting with 3.6
>> > (yay!)
>> >
>> > Regards,
>> >
>> > Hervé
>> >
>> >
>> > [1]
>> > https://cwiki.apache.org/confluence/display/MAVEN/Build+vs+Consumer+POM
>> >
>> > [2] http://maven.apache.org/studies/consumer-pom/maven-consumer.html
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Redesign website

[Martijn Dashorst]

It's been a while that this thread was active, but I'd like to share
the design contest (or whatever it is) on opensourcedesign.net for the
Maven website.

https://discourse.opensourcedesign.net/t/jobs-redesign-maven-website/394/13

It contains mostly my proposal, but pointing folks at it might give
the discussion about a new site design new energy, and Maven does need
a new web site design.

Martijn


On Fri, Jul 21, 2017 at 7:49 PM, Paul Hammant  wrote:
> I would move to plain markdown in git with one of Hugo or Hexo as the
> static site generators, if I were the decider for this (I am not of course).
>
> https://trunkbaseddevelopment.com is Hugo (Go-based) and took me about a
> month from start to launch, and after/before regular work. I've another in
> Hexo (Node-based) but it's far from ready to share yet. Jekyll is too slow
> these days.
>
> The absolute thing *you must have* is an edit-this-page link for each page,
> and these days that doesn't mean a wiki, it means a link to the VCS's
> edit-a-resource UI. For example, the bottom of
> https://trunkbaseddevelopment.com/branch-for-release/ has a Contribute to
> this page
> 
> link
> that you can harmless click right now to see where that ends up :)
>
> On Fri, Jul 21, 2017 at 12:28 PM, Anton Tanasenko 
> wrote:
>
>> What happened to the last attempt and the shotgun owl? :-D
>>
>> On Fri, 21 Jul 2017, 18:22 Robert Scholte,  wrote:
>>
>> > Hi,
>> >
>> > I'd like to start an attempt to redesign our website.
>> > At ApacheCon Europe Hervé and I got in touch with Open Source Design[1].
>> > Any objections to contact them and to see if we can help each other?
>> > Or are there other suggestions?
>> >
>> > thanks,
>> > Robert
>> >
>> > [1] http://opensourcedesign.net
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>> >
>>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Parent Version maybe not needed in child POM

[Martijn Dashorst]

On Mon, Dec 12, 2016 at 8:22 PM, Christian Schulte  wrote:
> Am 12/12/16 um 10:16 schrieb Tibor Digana:
>> Is it really necessary to specify version of parent artifact in ?
>
> It must be possible to checkout a single module and build that in
> isolation. A parent without a version cannot be resolved from a
> repository. Supporting that means you need to checkout the whole project
> (can be very huge) just to be able to find the parent on disk.
> Installing/deploying an artifact without version is impossible -
> incomplete coordinates. So there needs to be a version as soon as an
> artifact is to be installed or deployed.

But is it really a requirement that the version MUST be there always?
I never encountered your specific requirement, but I can imagine it be
necessary some times. But I can give you enough examples where your
requirement isn't necessary and the version can be omitted.

So, if you need need to checkout a submodule stand alone, then one
should include the version, but if that is not a use case, one can
omit the version and instead rely on the parent's module's version.

Martijn

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: POM Model version 4.1.0 in 3.4.0-SNAPSHOTs

[Martijn Dashorst]

On Wed, Aug 24, 2016 at 8:41 AM, Fred Cooke  wrote:
> Fair call re embedded pom, however it's quite convenient to just browse to
> it and read.

I'd like to vent another opinion: the build pom makes it hard to grok
the information I need as a consumer of a library. I really don't need
to wade through 20 pages of plugin configuration that doesn't affect
me.

I would even posit that issueManagement, scm, and url should not be
part of the consumer POM as these are external to the artifact and
live separate lives. I'd rather see a different file that lists that
particular information that can be updated when someone switches from
JIRA to github issues, or from svn to git on bitbucket to git on
github to a project specific git.project.io. Look what happened with
codehaus or googlecode going away, or all projects moving from sf.net
to github. Having the external information that doesn't relate to the
particular version be external to the POM would make that much better.

I really like the idea of consumer and producer POMs. Strip the
consumer POM of everything  and  related.

Martijn

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Eclipse Plugin Final Release ?

[Martijn Dashorst]

Would be cool if the site was updated wit the new location of jira
issues as well.

Martijn

On Thu, Apr 30, 2015 at 10:25 PM, Karl Heinz Marbaise  wrote:
> Hi,
>
> i would like to know if there are any objections to make a final release of
> the maven-eclipse-plugin ?
>
> The reason is simply because it is the last plugin on the list which misses
> the Maven 2.2.1 minimum
>
> This could make our release map complete here...
>
> as you can see here:
>
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html
>
>
> If there will be no objections until 8. May 2015 i will start a release on
> weekend afterwards...
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Jekyll experiment

[Martijn Dashorst]

While I use jekyll for lots of stuff (blogs and wicket website), I'd
urge to use asciidoc[tor] as the markup format. Markdown is great, but
rather limited for technical documentation. There is some asciidoctor
integration for jekyll available [1], but I haven't used it in anger.

Just my 2 cts.

Martijn

[1] https://google.com/search?q=jekyll%20asciidoctor


On Thu, Mar 19, 2015 at 4:32 AM, Jason van Zyl  wrote:
> Anyone interested in trying a Jekyll experiment for our website? Extract the 
> useful documentation we believe there is and try to make working on the site 
> a pleasurable experience that is easy for users to contribute to?
>
> I'd like to try this because after this last release I'm frankly tired of 
> looking at our pretty awful website. It's ugly, noisy, unmaintained, hard to 
> navigate and personally just makes me not want to write anything. I would 
> like to like writing documentation again and I think a more standard tool 
> like Jekyll will help. I honestly dislike doing core releases because I have 
> to use the site plugin. I created it, I can hate it and I do hate it.
>
> Even if no one answers I'll try this experiment because I think there's only 
> 10-15 useful documents in the whole site so it likely won't take long.
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> -
>
> There's no sense in being precise when you don't even know what you're 
> talking about.
>
>  -- John von Neumann
>
>
>
>
>
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [DISCUSS] To SemVer or not to SemVer, that is the question

[Martijn Dashorst]

On Sun, Feb 22, 2015 at 10:42 PM, Fred Cooke  wrote:
> I'd also love to hear that no one is trying to release 200 artifacts in a
> single reactor.

At Wicket Stuff (https://github.com/wicketstuff) we do just that. It
is a pain, but
it is quite a lot less pain than trying to release each project by itself.

> That makes no sense at all, to me. The chances are on a big
> corporate project you've only changed <25% of them per top level release
> anyway. So to run a top level MVN release against the entire tree would
> produce 75% duplicate (by code, not number) artifacts. Or did I
> misunderstand?

You understand correctly, but in Wicket Stuff's particular case we assume that
while not everything was modified, it is a much bigger benefit of having all
version of all sub modules align, such that we can ensure that one particular
version of Wicket works with one particular version of any Wicket Stuff project.

For a release manager it is actually hard to figure out which projects should
be released, releases of submodules linger long etc. The benefits for the
community with regular, full releases are tremendous. No more trying to figure
out which versions will work with your version of Wicket.

Martijn

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"

[Martijn Dashorst]

B

Martijn

On Mon, Dec 15, 2014 at 2:27 PM, David Hoffer  wrote:
> B
>
> -Dave
>
> On Mon, Dec 15, 2014 at 6:22 AM,  wrote:
>>
>> B
>>
>> Cody Fyler
>> Lending Grid Build Team
>> G=Lending Grid Builds
>> (515) – 441 - 0814
>>
>> -Original Message-
>> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
>> Sent: Monday, December 15, 2014 4:39 AM
>> To: Maven Users List; Maven Developers List
>> Subject: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"
>>
>> After the run-off round, we are left with two names standing.
>>
>> This second vote will be a straight and simple majority wins.
>>
>> The vote will be open for at least 72 hours (with the potential of an
>> extension until I send a message saying that the polls are closed)
>>
>> There will be no discussion in this thread, we have talked it all enough
>> already. If you want to discuss something, please use a different thread.
>>
>> Vote:
>>
>> [A]: Shotgun
>> [B]: The Maven Owl
>>
>> Thank you very much for your time
>>
>> -Stephen
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Scripting a release, incl. vote message

[Martijn Dashorst]

With the help of the nexus plugin and some grep fu I was able to
retrieve the repository id from nexus, albeit not very stable:

stagingrepoid=$(mvn
org.sonatype.plugins:nexus-staging-maven-plugin:LATEST:rc-list
-DnexusUrl=https://repository.apache.org
-DserverId=apache.releases.https |grep -Eo "(orgapachewicket-\d+)";)

I've also added closing the staging repository and other niceties.

Martijn

(see the line in context:
https://github.com/apache/wicket/blob/wicket-6.x/release-dashorst.sh#L243)


On Mon, Aug 25, 2014 at 6:03 PM, Martijn Dashorst
 wrote:
> All,
>
> I have almost fully automated the release process for Wicket,
> including branching, automatic version updates, git archiving,
> uploading of source distributions to svn (dist.a.o), etc.
>
> I'm looking to automate one of the final things I have to do manually:
> crafting the vote message.
>
> Most things I can include easily (like version numbers, and a change
> log), but where can I find to which staging repository are the Maven
> binary artefacts uploaded?
>
> I've included a sample vote message below.
>
> Thanks,
>
> Martijn
>
> -
>
> This is a vote to release Apache Wicket 7.0.0-M3
>
> Please download the source distributions found in our staging area
> linked below.
>
> I have included the signatures for both the source archives. This vote
> lasts for 72 hours minimum.
>
> [ ] Yes, release Apache Wicket 7.0.0-M3
> [ ] No, don't release Apache Wicket 7.0.0-M3, because ...
>
> Distributions, changelog, keys and signatures can be found at:
>
> https://dist.apache.org/repos/dist/dev/wicket/7.0.0-M3
>
> Staging repository:
>
> https://repository.apache.org/content/repositories/orgapachewicket-1024/
>
> The binaries are available in the above link, as are a staging
> repository for Maven. Typically the vote is on the source, but should
> you find a problem with one of the binaries, please let me know, I can
> re-roll them some way or the other.
>
> 
>
> The signatures for the source release artefacts:
>
> apache-wicket-7.0.0-M3.tar.gz
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> Comment: GPGTools - https://gpgtools.org
>
> iEYEABECAAYFAlP7UV4ACgkQJBX8W/xy/UW7JQCgp8aTTy5PKZGhbgmA8224t5zz
> 8HUAoMYUBZKZHZzvuedJiywqELFlkVDv
> =13H6
> -END PGP SIGNATURE-
>
> apache-wicket-7.0.0-M3.zip
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> Comment: GPGTools - https://gpgtools.org
>
> iEYEABECAAYFAlP7UV4ACgkQJBX8W/xy/UVHFQCg0lmCIyHUAnfoEJpxCzjeZyWV
> OWsAoNLXwzNdXIqH5spqGovDYkmmXOSu
> =PIr4
> -END PGP SIGNATURE-
>
> 
>
> Release Notes - Wicket - Version 7.0.0-M3
>
> ** Sub-task
>
> * [WICKET-5633] - Make JavaScriptFilteredIntoFooterHeaderResponse
> non-final to be able to create custom filters
>
> ** Bug
>
> * [WICKET-5241] - RequestLogger's server duration does not include
> 'detach duration'
> * [WICKET-5371] - IllegalArgumentException: Argument 'page' may not be
> null. - when sending event from asynchronous process
> * [WICKET-5564] - AjaxRequestTarget.focusComponent() does not work
> when two Ajax responses arrive next to each other
> * [WICKET-5578] - Stateless/Statefull pages - incorrect behaviour
> * [WICKET-5603] - OnChangeAjaxBehavior attached to DropDownChoice
> produces two Ajax requests in Chrome v35
> * [WICKET-5607] - Wicket Ajax fires calls scheduled by
> AbstractAjaxTimerBehavior even after unload of the page
> * [WICKET-5609] - AutoCompleteTextField can only complete text that is
> visible on screen browser screen
> * [WICKET-5615] - UploadProgressBar does not show up if no
> FileUploadField is given
> * [WICKET-5616] - CLONE - ModalWindow is not visible in Safari when
> opened from a link at the bottom of a large page
> * [WICKET-5619] - ConcurrentModificationException may occur when
> calling EventBus.post()
> * [WICKET-5624] - Do not throw when WebSocket is not supported
> * [WICKET-5626] - ConcatBundleResource#reportError() doesn't print the
> resource attributes
> * [WICKET-5630] - Fix last button translation germany of wizard to 'Letzter'
> * [WICKET-5631] - Allow submitting with POST method for PhantomJS
> * [WICKET-5636] - Update StatelessForm's and AbstractRepeater's
> javadoc that FormComponents should be repeated only with RepeatingView
> * [WICKET-5637] - Fix the encoding of the Chinese tran

Scripting a release, incl. vote message

[Martijn Dashorst]

All,

I have almost fully automated the release process for Wicket,
including branching, automatic version updates, git archiving,
uploading of source distributions to svn (dist.a.o), etc.

I'm looking to automate one of the final things I have to do manually:
crafting the vote message.

Most things I can include easily (like version numbers, and a change
log), but where can I find to which staging repository are the Maven
binary artefacts uploaded?

I've included a sample vote message below.

Thanks,

Martijn

-

This is a vote to release Apache Wicket 7.0.0-M3

Please download the source distributions found in our staging area
linked below.

I have included the signatures for both the source archives. This vote
lasts for 72 hours minimum.

[ ] Yes, release Apache Wicket 7.0.0-M3
[ ] No, don't release Apache Wicket 7.0.0-M3, because ...

Distributions, changelog, keys and signatures can be found at:

https://dist.apache.org/repos/dist/dev/wicket/7.0.0-M3

Staging repository:

https://repository.apache.org/content/repositories/orgapachewicket-1024/

The binaries are available in the above link, as are a staging
repository for Maven. Typically the vote is on the source, but should
you find a problem with one of the binaries, please let me know, I can
re-roll them some way or the other.



The signatures for the source release artefacts:

apache-wicket-7.0.0-M3.tar.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iEYEABECAAYFAlP7UV4ACgkQJBX8W/xy/UW7JQCgp8aTTy5PKZGhbgmA8224t5zz
8HUAoMYUBZKZHZzvuedJiywqELFlkVDv
=13H6
-END PGP SIGNATURE-

apache-wicket-7.0.0-M3.zip

-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iEYEABECAAYFAlP7UV4ACgkQJBX8W/xy/UVHFQCg0lmCIyHUAnfoEJpxCzjeZyWV
OWsAoNLXwzNdXIqH5spqGovDYkmmXOSu
=PIr4
-END PGP SIGNATURE-



Release Notes - Wicket - Version 7.0.0-M3

** Sub-task

* [WICKET-5633] - Make JavaScriptFilteredIntoFooterHeaderResponse
non-final to be able to create custom filters

** Bug

* [WICKET-5241] - RequestLogger's server duration does not include
'detach duration'
* [WICKET-5371] - IllegalArgumentException: Argument 'page' may not be
null. - when sending event from asynchronous process
* [WICKET-5564] - AjaxRequestTarget.focusComponent() does not work
when two Ajax responses arrive next to each other
* [WICKET-5578] - Stateless/Statefull pages - incorrect behaviour
* [WICKET-5603] - OnChangeAjaxBehavior attached to DropDownChoice
produces two Ajax requests in Chrome v35
* [WICKET-5607] - Wicket Ajax fires calls scheduled by
AbstractAjaxTimerBehavior even after unload of the page
* [WICKET-5609] - AutoCompleteTextField can only complete text that is
visible on screen browser screen
* [WICKET-5615] - UploadProgressBar does not show up if no
FileUploadField is given
* [WICKET-5616] - CLONE - ModalWindow is not visible in Safari when
opened from a link at the bottom of a large page
* [WICKET-5619] - ConcurrentModificationException may occur when
calling EventBus.post()
* [WICKET-5624] - Do not throw when WebSocket is not supported
* [WICKET-5626] - ConcatBundleResource#reportError() doesn't print the
resource attributes
* [WICKET-5630] - Fix last button translation germany of wizard to 'Letzter'
* [WICKET-5631] - Allow submitting with POST method for PhantomJS
* [WICKET-5636] - Update StatelessForm's and AbstractRepeater's
javadoc that FormComponents should be repeated only with RepeatingView
* [WICKET-5637] - Fix the encoding of the Chinese translations for
Wizard component
* [WICKET-5639] - ResourceResponse does not write headers when status
code is set
* [WICKET-5643] - WebPageRenderer should bind a Session if redirect is
required and the session is temporary.
* [WICKET-5644] - AjaxWizardButtonBar broken since ARA#preventDefault is false
* [WICKET-5647] - missing generic cast causes compile error on OS X / jdk 8
* [WICKET-5655] - Problem with setting of IComponentInheritedModel and
FLAG_INHERITABLE_MODEL
* [WICKET-5656] - PropertyResolver does not scan for NotNull in annotation tree
* [WICKET-5657] - wicket-autocomplete may fail after preceeding Ajax request
* [WICKET-5662] - @SpringBean(name="something", required=false) still
throws org.springframework.beans.factory.NoSuchBeanDefinitionException:
No bean named 'something' is defined
* [WICKET-5670] - org.apache.wicket.protocol.ws.api.registry.IKey
should be Serializable (IClusterable)
* [WICKET-5679] - RenderStrategy REDIRECT_TO_RENDER lets fail test
with BaseWicketTester#startComponentInPage
* [WICKET-5680] - AjaxEditableLabel keeps raw input after cancel
following a validation failure

** Improvement

* [WICKET-4344] - Implement onVa

Re: Permissions change on cwiki?

[Martijn Dashorst]

A couple of weeks ago infra disabled editing for all accounts due to an
excessive spam influx. IIRC any admin can restore edit privileges.

Martijn


On Sun, Apr 6, 2014 at 9:17 PM, Jason van Zyl  wrote:

> Can anyone else edit that page. Just checking to make sure it's just me
> before I ask infra to look.
>
> On Apr 6, 2014, at 9:41 AM, Jason van Zyl  wrote:
>
> > I can no longer see the edit button on a page I created:
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+4.0.0
> >
> > Anyone else having permissions issues on cwiki?
> >
> > Thanks,
> >
> > Jason
> >
> > --
> > Jason van Zyl
> > Founder,  Apache Maven
> > http://twitter.com/jvanzyl
> > http://twitter.com/takari_io
> > -
> >
> > Selfish deeds are the shortest path to self destruction.
> >
> > -- The Seven Samuari, Akira Kurosawa
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> -
>
> Our achievements speak for themselves. What we have to keep track
> of are our failures, discouragements and doubts. We tend to forget
> the past difficulties, the many false starts, and the painful
> groping. We see our past achievements as the end result of a
> clean forward thrust, and our present difficulties as
> signs of decline and decay.
>
>  -- Eric Hoffer, Reflections on the Human Condition
>
>
>
>
>
>
>
>
>
>


-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

Re: Model Version 5.0.0

[Martijn Dashorst]

On Mon, Mar 24, 2014 at 8:06 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> I see the checksums then as being another potential side artifact... No
> need for modelVersion 5.0.0
>

I see it differently: the checksum validates the GAV coordinates. "I mean
'com.example.foo:foo:1.0', specifically verify that it matches this
signature 'sha1:1234567890abcdef'.

For example, this enables me to check if a different version of an artefact
was uploaded to the same GAV than I expected (and reportedly the original
author too).

A plugin right now could capture them and deploy to repo, and you could
> have same plugin verify the resolved dependencies against the same file.
>

This assumes the whole chain of parties is to be trusted. That nobody will
try to side-load a version from a different repository.

I find the idea of adding a checksum to a dependency interesting. While I
don't care for the extra fields in the POM, it opens a better venue of
vetting the dependencies.

Martijn

Re: Model Version 5.0.0

[Martijn Dashorst]

On Mon, Mar 24, 2014 at 7:29 PM, Robert Scholte wrote:

> I have to admit I have never used it, but aren't the -c / -C Maven
> commandline options meant for this?
>

Only if you trust the repository where you get the checksums from. The idea
advocated by Baptiste is that as a project owner you specify not only which
GAV you require but also the checksum of a dependency: this way you can
retrieve the checksum from the original project and make sure everybody
gets the 'official' version. This also ensures that nobody can tamper with
uploading a new version to a repository under the same GAV.

Now probably this will not be very practical to introduce on a large
project (try to find the correct signatures for each dependency in for
example a standard Maven build for a hello world application), but for some
venues this might actually make sense-where security and accountability is
paramount.

Martijn

Re: Fixed: Unable to upload release artifacts to Apache's nexus

[Martijn Dashorst]

My biggest gripes with Maven in this situation are two fold:

1. an error message that can be much more descriptive as the exception
appears to be SSLPeerUnverifiedException. The message that is logged
by Maven:

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy
(default-deploy) on project wicket-parent: Failed to deploy artifacts:
Could not transfer artifact org.apache.wicket:wicket-parent:pom:6.12.0
from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
peer not authenticated -> [Help 1]

does not convey this information. Information has been lost!

2. The excessive logging generated by Maven obscures the actual
message, making it hard to find what exactly went wrong. Maven should
*end* the log with the exception message (possibly including the type
of the exception). See the following log vomit and try to discern what
went wrong and how to fix it:


[INFO] [INFO] --- maven-site-plugin:3.1:attach-descriptor
(attach-descriptor) @ wicket-parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.4:sign (default) @ wicket-parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install)
@ wicket-parent ---
[INFO] [INFO] Installing
/Workspaces/wicket/wicket-6.x/wicket/target/checkout/pom.xml to
/Users/dashorst/.m2.wicket/repository/org/apache/wicket/wicket-parent/6.12.0/wicket-parent-6.12.0.pom
[INFO] [INFO] Installing
/Workspaces/wicket/wicket-6.x/wicket/target/checkout/target/wicket-parent-6.12.0-source-release.zip
to 
/Users/dashorst/.m2.wicket/repository/org/apache/wicket/wicket-parent/6.12.0/wicket-parent-6.12.0-source-release.zip
[INFO] [INFO] Installing
/Workspaces/wicket/wicket-6.x/wicket/target/checkout/target/wicket-parent-6.12.0.pom.asc
to 
/Users/dashorst/.m2.wicket/repository/org/apache/wicket/wicket-parent/6.12.0/wicket-parent-6.12.0.pom.asc
[INFO] [INFO] Installing
/Workspaces/wicket/wicket-6.x/wicket/target/checkout/target/wicket-parent-6.12.0-source-release.zip.asc
to 
/Users/dashorst/.m2.wicket/repository/org/apache/wicket/wicket-parent/6.12.0/wicket-parent-6.12.0-source-release.zip.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.4:sign (sign-artifacts) @ wicket-parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @
wicket-parent ---
[INFO] Uploading:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/wicket/wicket-parent/6.12.0/wicket-parent-6.12.0.pom
[INFO]
[INFO] [INFO] 

[INFO] [INFO] Reactor Summary:
[INFO] [INFO]
[INFO] [INFO] Wicket Parent .
FAILURE [14.694s]
[INFO] [INFO] Wicket Util ... SKIPPED
[INFO] [INFO] Wicket Request  SKIPPED
[INFO] [INFO] Wicket Core ... SKIPPED
[INFO] [INFO] Wicket  SKIPPED
[INFO] [INFO] Wicket Date/Time .. SKIPPED
[INFO] [INFO] Wicket Extensions . SKIPPED
[INFO] [INFO] Wicket Development Utilities .. SKIPPED
[INFO] [INFO] Wicket IoC common code  SKIPPED
[INFO] [INFO] Wicket CDI Integration  SKIPPED
[INFO] [INFO] Wicket Spring Integration . SKIPPED
[INFO] [INFO] Wicket Velocity ... SKIPPED
[INFO] [INFO] Wicket Auth Roles . SKIPPED
[INFO] [INFO] Wicket Guice Integration .. SKIPPED
[INFO] [INFO] Wicket JMX  SKIPPED
[INFO] [INFO] Wicket Objects Sizeof Agent ... SKIPPED
[INFO] [INFO] Wicket-Experimental ... SKIPPED
[INFO] [INFO] Wicket-Atmosphere . SKIPPED
[INFO] [INFO] Wicket Bean Validation  SKIPPED
[INFO] [INFO] Wicket Examples ... SKIPPED
[INFO] [INFO] Wicket Native WebSocket Parent  SKIPPED
[INFO] [INFO] Wicket Native WebSocket Core .. SKIPPED
[INFO] [INFO] Wicket Native WebSocket Jetty . SKIPPED
[INFO] [INFO] Wicket Native WebSocket Jetty 9 ... SKIPPED
[INFO] [INFO] Wicket Native WebSocket Tomcat 7.x  SKIPPED
[INFO] [INFO] Wicket Bootstrap .. SKIPPED
[INFO] [INFO] Wicket Examples Parent  SKIPPED
[INFO] [INFO] Wicket Examples Jar ... SKIPPED
[INFO] [INFO] Wicket Examples War ... SKIPPED
[INFO] [INFO] Wicket Quickstart Archetype ... SKIPPED
[INFO] [INFO] Wicket Common Tests ... SKIPPED
[INFO] [INFO] 
--

Fixed: Unable to upload release artifacts to Apache's nexus

[Martijn Dashorst]

It appears that I was unable to upload a pending release to the
repository.apache.org nexus while I am able to log in to the web
interface using my credentials.

The log of maven gives as reason:

"Peer not authenticated"

While it is probably completely clear what this descriptive message
means to a core Maven developer, it caused me some griefs (i.e. a
whole morning) to fix this issue. In order to help others that might
run into this particular problem here's what fixed it for me:

It appears that upgrading my lingering Java 6 version on  OS X to
1.6.0_65 has fixed this issue. While not 100% sure, I suspect the
updated Java has newer certificates that make the upload process work
again.

I'd like to see the error handling of Maven to be improved to make
clear that the HTTPS connection could not be established rather than
just "peer not authenticated" due to bad certificates or such.

Martijn Dashorst

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Commits rejected to Subversion

[Martijn Dashorst]

Switch your checkout to https instead of http

Martijn

On Mon, May 20, 2013 at 5:56 PM, Michael-O <1983-01...@gmx.net> wrote:
> Hi folks,
>
> it seems like I do not have full access to the Maven directory in the
> Subversion repository.
> See
>
> commit -m "REOPENED - issue MSKINS-72: Add copyright notice position option"
> D:/Projekte/maven-fluido-skin-trunk/src/site/apt/index.apt.vm
> D:/Projekte/maven-fluido-skin-trunk/src/main/resources/META-INF/maven/site.vm
> svn: E170001: Commit failed (details follow):
> svn: E170001: Commit failed (details follow):
> svn: E170001: MKACTIVITY of
> '/repos/asf/!svn/act/d53b51c2-3e01-0010-901f-c1e0ff6c4ca4': 403 Forbidden
> (http://svn.apache.org)
>
> Is anyone able to check the error and correct permissions?
>
> My username is michaelo
>
> Thanks,
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: EOL of 1.5 as minimum

[Martijn Dashorst]

+1

There is no reason to have *NEW* development of Maven be hampered by
obsolete technology. If anyone can't upgrade their Java runtime for
whatever reason, they probably won't upgrade to a new Maven version as
well. 3.0.4 works rather well and anyone should really be tying down
their plugin versions as well.

I'd even suggest upping the minimum required version of Maven 4 to be
Java 7. A build system really can benefit from try with resources,
NIO2 etc.

Having build times be chopped down half would benefit the whole world:
less time waiting, and less energy used for building.

Martijn

On Wed, Feb 6, 2013 at 9:37 PM, Olivier Lamy  wrote:
> Hi,
> As we are now in 2013, it's probably time to think about that (again).
>
> Reading [1], even 1.6 won't be anymore updated after feb 2013.
>
> Can we say we are safe to go to 1.6 as minimum required ?
>
> NOTE: That will probably need a vote. So depending on how the thread
> move, I will start a vote (or not).
>
> Thanks
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> [1] http://www.oracle.com/technetwork/java/eol-135779.html
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Creating a maven integration test

[Martijn Dashorst]

Is this the canonical URL for supplying a IT with a patch?

http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test

So when I have gone through the moves of creating the IT, and creating
a patch for a maven plugin, I can just zip the IT project and attach
it to the plugin's JIRA?

Martijn

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [MECLIPSE] minimize logging of missing -source/-javadoc jars

[Martijn Dashorst]

Hi Barrie,

Could you also take a look at
http://jira.codehaus.org/browse/MECLIPSE-668, this will cut down on
logging output for OS X users considerably.

Thanks for taking a look into MECLIPSE-669!

Martijn

On Tue, Sep 7, 2010 at 7:03 AM, Barrie Treloar  wrote:
> On Mon, Sep 6, 2010 at 7:24 PM, Martijn Dashorst
>  wrote:
>> When running mvn eclipse:eclipse on our projects, we cringe with the
>> amount of unnecessary output the plugin generates.
>
> Fair enough.
>
> Patch applied.
>
> My build environment is broken at the moment (all the ITs fail)
> Will double check in a few days.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[MECLIPSE] minimize logging of missing -source/-javadoc jars

[Martijn Dashorst]

When running mvn eclipse:eclipse on our projects, we cringe with the
amount of unnecessary output the plugin generates.

We use source dependencies in our IDE which provide the javadocs, so
we have disabled downloading of Javadoc files. Unfortunately, MECLIPSE
finds it necessary to report all dependencies for which it hasn't
downloaded the javadoc resource jars.

I'm trying to come up with a good patch for this and suggest that the
plugin remains silent for both missing source and javadoc jars when
either option is disabled. It strikes me as odd that when you disable
an option, the plugin starts to tell you that things haven't been
downloaded, even when you explicitly told it not to download.

The main reason I'm asking here is to see if there's a specific need
for reporting those missing -javadoc jars, even when their downloading
is explicitly disabled.

To make things concrete: I'm proposing the following patch (also
attached to http://jira.codehaus.org/browse/MECLIPSE-669).

Index: src/main/java/org/apache/maven/plugin/ide/AbstractIdeSupportMojo.java
===
--- src/main/java/org/apache/maven/plugin/ide/AbstractIdeSupportMojo.java   
(revision
992964)
+++ src/main/java/org/apache/maven/plugin/ide/AbstractIdeSupportMojo.java   
(working
copy)
@@ -1040,16 +1040,9 @@
 {
 StringBuffer msg = new StringBuffer();

-if ( !missingSourceDependencies.isEmpty() )
+if ( getDownloadSources() && !missingSourceDependencies.isEmpty() )
 {
-if ( getDownloadSources() )
-{
-msg.append( Messages.getString(
"AbstractIdeSupportMojo.sourcesnotavailable" ) ); //$NON-NLS-1$
-}
-else
-{
-msg.append( Messages.getString(
"AbstractIdeSupportMojo.sourcesnotdownloaded" ) ); //$NON-NLS-1$
-}
+msg.append( Messages.getString(
"AbstractIdeSupportMojo.sourcesnotavailable" ) ); //$NON-NLS-1$

 for ( Iterator it = missingSourceDependencies.iterator();
it.hasNext(); )
 {
@@ -1059,16 +1052,9 @@
 msg.append( "\n" ); //$NON-NLS-1$
 }

-if ( !missingJavadocDependencies.isEmpty() )
+if ( getDownloadJavadocs() && !missingJavadocDependencies.isEmpty() )
 {
-if ( getDownloadJavadocs() )
-{
-msg.append( Messages.getString(
"AbstractIdeSupportMojo.javadocnotavailable" ) ); //$NON-NLS-1$
-}
-else
-{
-msg.append( Messages.getString(
"AbstractIdeSupportMojo.javadocnotdownloaded" ) ); //$NON-NLS-1$
-}
+msg.append( Messages.getString(
"AbstractIdeSupportMojo.javadocnotavailable" ) ); //$NON-NLS-1$

 for ( Iterator it =
missingJavadocDependencies.iterator(); it.hasNext(); )
 {

Martijn

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Improving the apache parent pom

[Martijn Dashorst]

I think this is a great idea. You could even put the new apache wide
repository and staging area in the release profile. Would make doing a
release a snap IMO.

Martijn

On Tue, Apr 14, 2009 at 9:18 PM, Brian Fox  wrote:
> We currently have some expectations about what artifacts are created for
> apache builds, such as javadocs and source jars, and specifically artifact
> signatures. Currently each project must configure the current release
> profile in their own top level pom. This raises the bar of entry for new
> projects and creates more work for us to help them get it sorted out.
>
> I'd like to take the maven release profile and release plugin config and
> push it up to the apache pom to make it consistent and easy for all apache
> projects to produce proper releases.  I think to do it and avoid conflicts
> with any existing profiles, I would change the profile name from "release"
> to "apache-release" and activate that by default. Does anyone see any
> downsides to this?
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Re : Re : [VOTE] Release Maven eclipse plugin version 2.6

[Martijn Dashorst]

On Fri, Mar 27, 2009 at 5:45 AM, Barrie Treloar  wrote:
> There is definitely a defect introduced with setting inclusions to
> **/*.java (MECLIPSE-443 added inclusions) for Apsect developers (see
> MECLIPSE-538).
>
> But that shouldn't stop the release.

I'd rather had it would've stopped the release. This costed our devs a
whole morning to figure out why our application wouldn't start up
anymore due to missing .properties and other configuration and
non-java files (it's a Wicket project). This 'fix' will cause major
headaches for anyone developing Wicket applications, using Maven and
Eclipse. AFIAK that is about 70% of all Wicket developers out there.

I don't see a vote thread for maven-eclipse-plugin-1.6.1 happening,
which is something that should be done fast IMO.

Martijn

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Notes from Build Tools BOF at ApacheCon US 2008

[Martijn Dashorst]

On Sat, Nov 15, 2008 at 2:35 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> Wendy Smoak wrote:
>> Unit tests run slower in Maven than in Ant
>>
>> Surefire fills up /tmp with directories
>
> Are there bugs filed for this?  Do we think that the /tmp directories are
> the cause of our perf troubles?

These are separate issues.

Martijn

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: An Attribute Based POM

[Martijn Dashorst]

On 2/12/08, Michael McCallum <[EMAIL PROTECTED]> wrote:
>
> You can change the tool to make a bad pom look good but at the end of the
> day
> there is something wrong if your declared dependency list looks like
> that...
>

How come? To get reproducible builds, you need to specify the versions of
all your dependencies, including the transitive ones (e.g. to resolve
version conflicts). This makes the list of dependencies huge.
Martijn


-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.1 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.1

Re: Re: Re: Re: Please sync Wicket repo from http://wicketframework.org/maven2

[Martijn Dashorst]

Oh, and one last thing: I don't mind having to wait a couple of days
before a sync happens. That's all in the game for having a central
repository and you guys providing the gateway service for it.

I really appreciate the repo sync, it saves me (and you I suppose) a
lot of work.

Martijn

On 11/3/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:

I'm complaining because of this comment:

On 11/3/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> I pulled Wicket out of the automated sync

If we were not auto-sync'd, then how could we be pulled out of it? I
know we were not in auto-sync, so this came across on me that our
script was completely removed.

I appreciate the sync though. Thanks!

Martijn

On 11/3/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> Martijn, it has never been automatically synced. Nothing has changed
> for you, so I don't know why you are complaining.
> I've synced it manually this time.
>
> On 11/3/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> > On 11/3/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> > > I pulled Wicket out of the automated sync because it required Carlos'
> > > password which means it can't be run by cron. If you want so sort
> > > this out subscribe to the repository list: repository-
> > > [EMAIL PROTECTED]
> >
> > Nice to be notified of this at a more convenient time. There is enough
> > information available for contacting the person that does the releases
> > if/when you do something like this.
> >
> > Martijn
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
>  -- The Princess Bride
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
http://www.thebeststuffintheworld.com/vote_for/wicket";>Vote
for http://www.thebeststuffintheworld.com/stuff/wicket";>Wicket
at the http://www.thebeststuffintheworld.com/";>Best Stuff in
the World!




--
http://www.thebeststuffintheworld.com/vote_for/wicket";>Vote
for http://www.thebeststuffintheworld.com/stuff/wicket";>Wicket
at the http://www.thebeststuffintheworld.com/";>Best Stuff in
the World!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Please sync Wicket repo from http://wicketframework.org/maven2

[Martijn Dashorst]

I'm complaining because of this comment:

On 11/3/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:

I pulled Wicket out of the automated sync


If we were not auto-sync'd, then how could we be pulled out of it? I
know we were not in auto-sync, so this came across on me that our
script was completely removed.

I appreciate the sync though. Thanks!

Martijn

On 11/3/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:

Martijn, it has never been automatically synced. Nothing has changed
for you, so I don't know why you are complaining.
I've synced it manually this time.

On 11/3/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> On 11/3/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> > I pulled Wicket out of the automated sync because it required Carlos'
> > password which means it can't be run by cron. If you want so sort
> > this out subscribe to the repository list: repository-
> > [EMAIL PROTECTED]
>
> Nice to be notified of this at a more convenient time. There is enough
> information available for contacting the person that does the releases
> if/when you do something like this.
>
> Martijn
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
 -- The Princess Bride

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
http://www.thebeststuffintheworld.com/vote_for/wicket";>Vote
for http://www.thebeststuffintheworld.com/stuff/wicket";>Wicket
at the http://www.thebeststuffintheworld.com/";>Best Stuff in
the World!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Please sync Wicket repo from http://wicketframework.org/maven2

[Martijn Dashorst]

On 11/3/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:

I pulled Wicket out of the automated sync because it required Carlos'
password which means it can't be run by cron. If you want so sort
this out subscribe to the repository list: repository-
[EMAIL PROTECTED]


Nice to be notified of this at a more convenient time. There is enough
information available for contacting the person that does the releases
if/when you do something like this.

Martijn

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Please sync Wicket repo from http://wicketframework.org/maven2

[Martijn Dashorst]

Dear Maven guru's,

could you please sync the wicket repository to Ibiblio. We've just
released Wicket 1.2.3 and are anxious to feed the maven 2 repository.

The scripts are already in place.

Thanks a million!

Martijn Dashorst

--
Download Wicket 1.2.3 now!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MAVENUPLOAD-706) Upload wicket-1.1.1-bundle.jar and wicket-extensions-1.1.1-bundle.jar

[Martijn Dashorst (JIRA)]

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-706?page=comments#action_57400 ] 

Martijn Dashorst commented on MAVENUPLOAD-706:
--

This build is still using maven 1. Not everyone is using maven 2.

Please upload these jars. I get a lot of requests on our user list.



> Upload wicket-1.1.1-bundle.jar and wicket-extensions-1.1.1-bundle.jar
> -
>
>  Key: MAVENUPLOAD-706
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-706
>  Project: maven-upload-requests
> Type: Task

> Reporter: Martijn Dashorst

>
>
> http://wicket.sf.net/downloads/wicket-1.1.1-bundle.jar
> http://wicket.sf.net/downloads/wicket-extensions-1.1.1-bundle.jar
> http://wicket.sf.net
> http://wicket.sf.net/team-list.html
> Wicket is a Java web application framework that takes simplicity, separation 
> of concerns and ease of development to a whole new level. Wicket pages can be 
> mocked up, previewed and later revised using standard WYSIWYG HTML design 
> tools. Dynamic content processing and form handling is all handled in Java 
> code using a first-class component model backed by POJO data beans that can 
> easily be persisted using your favourite technology.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MAVENUPLOAD-706) Upload wicket-1.1.1-bundle.jar and wicket-extensions-1.1.1-bundle.jar

[Martijn Dashorst (JIRA)]

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-706?page=comments#action_57290 ] 

Martijn Dashorst commented on MAVENUPLOAD-706:
--

The default for these jar files is that they are production-type jar files, I 
don't want my production system running with all java code in it. If you need 
the sources, go to the project itself and download the source distribution.

> Upload wicket-1.1.1-bundle.jar and wicket-extensions-1.1.1-bundle.jar
> -
>
>  Key: MAVENUPLOAD-706
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-706
>  Project: maven-upload-requests
> Type: Task

>     Reporter: Martijn Dashorst

>
>
> http://wicket.sf.net/downloads/wicket-1.1.1-bundle.jar
> http://wicket.sf.net/downloads/wicket-extensions-1.1.1-bundle.jar
> http://wicket.sf.net
> http://wicket.sf.net/team-list.html
> Wicket is a Java web application framework that takes simplicity, separation 
> of concerns and ease of development to a whole new level. Wicket pages can be 
> mocked up, previewed and later revised using standard WYSIWYG HTML design 
> tools. Dynamic content processing and form handling is all handled in Java 
> code using a first-class component model backed by POJO data beans that can 
> easily be persisted using your favourite technology.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-706) Upload wicket-1.1.1-bundle.jar and wicket-extensions-1.1.1-bundle.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.1.1-bundle.jar and wicket-extensions-1.1.1-bundle.jar
-

 Key: MAVENUPLOAD-706
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-706
 Project: maven-upload-requests
Type: Task

Reporter: Martijn Dashorst


http://wicket.sf.net/downloads/wicket-1.1.1-bundle.jar
http://wicket.sf.net/downloads/wicket-extensions-1.1.1-bundle.jar

http://wicket.sf.net
http://wicket.sf.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-581) Upload wicket-1.1-bundle.jar and wicket-extensions-1.1-bundle.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.1-bundle.jar and wicket-extensions-1.1-bundle.jar
-

 Key: MAVENUPLOAD-581
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-581
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sf.net/downloads/wicket-1.1-bundle.jar
http://wicket.sf.net/downloads/wicket-extensions-1.1-bundle.jar

http://wicket.sf.net
http://wicket.sf.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-540) Upload wicket-1.1-rc2-bundle.jar, wicket-extensions-1.1-rc2-bundle.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.1-rc2-bundle.jar, wicket-extensions-1.1-rc2-bundle.jar
--

 Key: MAVENUPLOAD-540
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-540
 Project: maven-upload-requests
Type: Task
 Reporter: Martijn Dashorst


http://wicket.sf.net/downloads/wicket-1.1-rc2-bundle.jar 
http://wicket.sf.net/downloads/wicket-extensions-1.1-rc2-bundle.jar

http://wicket.sf.net
http://wicket.sf.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVEN-1705) Maven 1.1-beta2 unable to parse POM

[Martijn Dashorst (JIRA)]

Maven 1.1-beta2 unable to parse POM
---

 Key: MAVEN-1705
 URL: http://jira.codehaus.org/browse/MAVEN-1705
 Project: Maven
Type: Bug
  Components: core  
Versions: 1.1-beta-2
 Environment: Windows XP SP2, 

java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)

 Reporter: Martijn Dashorst
 Attachments: project.zip

The project.xml is written by the standard Eclipse WTP 0.7 xml editor. It is 
saved as unicode UTF-8. Maven 1.0 parsed these files without problems.

 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.1-beta-2

org.apache.maven.MavenException: Unknown error reading project
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:146)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:99)
at 
org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:232)
at org.apache.maven.MavenSession.initialize(MavenSession.java:172)
at org.apache.maven.cli.App.doMain(App.java:498)
at org.apache.maven.cli.App.main(App.java:1258)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
--- Nested Exception ---
org.apache.maven.MavenException: Error parsing project.xml 
'D:\workspace\finan\ing\finan-persistency-dbmanager\project.x
ml'
at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:189)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:120)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:99)
at 
org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:232)
at org.apache.maven.MavenSession.initialize(MavenSession.java:172)
at org.apache.maven.cli.App.doMain(App.java:498)
at org.apache.maven.cli.App.main(App.java:1258)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
--- Nested Exception ---
org.codehaus.plexus.util.xml.pull.XmlPullParserException: only whitespace 
content allowed before start tag and not \uef
(position: START_DOCUMENT seen \uef... @1:1)
at 
org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1515)
at 
org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1391)
at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1089)
at 
org.apache.maven.project.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:1018)
at 
org.apache.maven.project.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:1782)
at org.apache.maven.project.Project.(Project.java:122)
at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:185)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:120)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:99)
at 
org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:232)
at org.apache.maven.MavenSession.initialize(MavenSession.java:172)
at org.apache.maven.cli.App.doMain(App.java:498)
at org.apache.maven.cli.App.main(App.java:1258)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)

You have encountered an unknown error running Maven.
Please help us to correct this problem by following these simple steps:
- read the Maven FAQ at http://maven.apache.org/faq.html
- run the same command again with the '-e' parameter, eg 'maven -e jar'
- search the maven-user archives for the error at 
http://www.mail-archive.com/users@maven.apache.org
- post the output of maven -e to JIRA at ???issueTrackingUrl??? (you must sign 
up first)
- run 'maven --info' and post the output as the environment to the bug above

T

[jira] Created: (MAVENUPLOAD-510) Upload wicket and wicket-extensions 1.1-rc1

[Martijn Dashorst (JIRA)]

Upload wicket and wicket-extensions 1.1-rc1 


 Key: MAVENUPLOAD-510
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-510
 Project: maven-upload-requests
Type: Task
 Reporter: Martijn Dashorst


http://wicket.sf.net/downloads/wicket-1.1-rc1-bundle.jar
http://wicket.sf.net/downloads/wicket-extensions-1.1-rc1-bundle.jar

http://wicket.sf.net/team-list.html
http://wicket.sf.net/

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

Please upload!

With regards,

Martijn Dashorst

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven 1.0 branch

[Martijn Dashorst]

It all depends on when 1.1 is expected to become final. And how long/much 
effort it takes to craft a 1.0.3.

I would download and try 1.0.3 instantly, and crafting my builds 
accordingly, as it would make transitioning to 1.1 easier.

I'm +1, but only if it doesn't take (too much) time off of 1.1

Martijn


On 9/8/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> 
> I've contemplated this myself recently given that 1.1 is not moving
> along as fast as I'd hoped. My main concern was confusion with yet
> another release, and that because uptake is often quite slow on minor
> revisions it would not be picked up before 1.1 was out anyway.
> 
> I'm interested to hear what others think.
> 
> - Brett
> 
> Henning P. Schmiedehausen wrote:
> 
> >Hi,
> >
> >due to some questions related to plugin changes on another mailing
> >list, I wondered what changes have been done to the maven-1.0 branch
> >(
> http://svn.apache.org/repos/asf/maven/maven-1/core/branches/MAVEN-1_0-BRANCH
> )
> >post the maven-1.0.2 release
> >(http://svn.apache.org/repos/asf/maven/maven-1/core/tags/MAVEN_1_0_2).
> >
> >A diff came up with "no changes".
> >
> >As maven 1.0.x has proven to be stable, there are many users out
> >there that probably cannot upgrade to a beta version and are forced to
> >use a maven 1.0 version for building.
> >
> >The 1.0.2 release is now ~nine months old and a number of plugins
> >included with 1.0.2 have been significantly upgraded (e.g. Subversion
> >support in Changelog or the xdoc plugin (which still shows 1.9 on the
> >download page BTW) or the jar/artifact deploy code (which even uses a
> >different syntax for describing the upload repositories now).
> >
> >So, wouldn't it make sense to cut a maven 1.0.3 release with the core
> >unchanged and just the upgraded plugins bundled? This would also bring
> >the 1.0.x plugins more in line with the documentation on the web site.
> >
> >(e.g. if you download maven 1.0.2, you get maven-jar-plugin 1.6.1. The
> >docs on the web site are for 1.7 and simply not working for
> >1.6.1. There is not documentation for maven-jar-plugin anywhere to
> >find on the maven web site (or I was not able to find it)).
> >
> > Best regards
> > Henning
> >
> >
> >
> >
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

[jira] Commented: (MAVENUPLOAD-500) Upload http://wicket.sourceforge.net/downloads/wicket-1.1-b4-bundle.jar and http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b4-bundle.jar

[Martijn Dashorst (JIRA)]

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-500?page=comments#action_45963 ] 

Martijn Dashorst commented on MAVENUPLOAD-500:
--

Use the URL's in the description. The bundle URL field apparently has a comma 
attached to the end.

Martijn

> Upload http://wicket.sourceforge.net/downloads/wicket-1.1-b4-bundle.jar and 
> http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b4-bundle.jar
> ---
>
>  Key: MAVENUPLOAD-500
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-500
>  Project: maven-upload-requests
>     Type: Task
> Reporter: Martijn Dashorst

>
>
> http://wicket.sourceforge.net/downloads/wicket-1.1-b4-bundle.jar
> http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b4-bundle.jar
> http://wicket.sf.net
> http://wicket.sf.net/team-list.html
> Wicket is a Java web application framework that takes simplicity, separation 
> of concerns and ease of development to a whole new level. Wicket pages can be 
> mocked up, previewed and later revised using standard WYSIWYG HTML design 
> tools. Dynamic content processing and form handling is all handled in Java 
> code using a first-class component model backed by POJO data beans that can 
> easily be persisted using your favourite technology.
> Thanks for uploading!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven community was: [ANN] Maven XDoc Plug-in 1.9.2 released

[Martijn Dashorst]

> 
> Are there any committers/observers who feel left out? Please speak up!


I don't feel left out, I tend to only respond to things I feel I can 
contribute on, or have an opinion about. I think the community is pretty 
solid and considering the number of messages I recieve on a daily basis 
(excluding the JIRA spam ;-)), I think the community is thriving.

Voting is sometimes artificial IMO. When someone is recommended for 
inclusion in the core project for instance, I've yet to see one -1 vote. It 
feels more like ceremony than real practical value. When voting for plugin 
releases, I think the current process is ok. If someone is monitoring the 
mailinglists, he/she can pull the breaks when he/she feels that a release of 
a plugin is too soon. When the most important and recent players on a 
particular plugin have voted +1, I'd say release.

The only 'gripe' I have is that it takes too long for 1.1 to become final, 
I'd liked it when more development effort had been put into releasing
1.1somewhere in june, but I don't think that is a huge problem though.
1.0.2 is still working wonders for me.

Go team!

Martijn

[jira] Created: (MAVENUPLOAD-500) Upload http://wicket.sourceforge.net/downloads/wicket-1.1-b4-bundle.jar and http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b4-bundle.jar

[Martijn Dashorst (JIRA)]

Upload http://wicket.sourceforge.net/downloads/wicket-1.1-b4-bundle.jar and 
http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b4-bundle.jar
---

 Key: MAVENUPLOAD-500
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-500
 Project: maven-upload-requests
Type: Task
 Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-1.1-b4-bundle.jar
http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b4-bundle.jar

http://wicket.sf.net
http://wicket.sf.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

Thanks for uploading!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-496) Upload wicket-1.0.3-bundle.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.0.3-bundle.jar
--

 Key: MAVENUPLOAD-496
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-496
 Project: maven-upload-requests
Type: Task
 Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-1.0.3-bundle.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MAVENUPLOAD-490) Upload wicket-1.0.2-bundle.jar, wicket-1.1-b3-bundle.jar, wicket-extensions-1.1-b3-bundle.jar

[Martijn Dashorst (JIRA)]

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-490?page=comments#action_45080 ] 

Martijn Dashorst commented on MAVENUPLOAD-490:
--

http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b3-bundle.jar

should work (sorry bout that)

> Upload wicket-1.0.2-bundle.jar, wicket-1.1-b3-bundle.jar, 
> wicket-extensions-1.1-b3-bundle.jar
> -
>
>  Key: MAVENUPLOAD-490
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-490
>  Project: maven-upload-requests
> Type: Task
> Reporter: Martijn Dashorst
> Assignee: Carlos Sanchez

>
>
> http://wicket.sf.net/downloads/wicket-1.0.2-bundle.jar 
> http://wicket.sf.net/downloads/wicket-1.1-b3-bundle.jar 
> http://wicket.sf.net/downloads/wicket-extensions-1.1-b3.jar
> http://wicket.sf.net
> http://wicket.sf.net/team-list.html
> Wicket is a Java web application framework that takes simplicity, separation 
> of concerns and ease of development to a whole new level. Wicket pages can be 
> mocked up, previewed and later revised using standard WYSIWYG HTML design 
> tools. Dynamic content processing and form handling is all handled in Java 
> code using a first-class component model backed by POJO data beans that can 
> easily be persisted using your favourite technology.
> Please upload.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Automate testing

[Martijn Dashorst]

jWebUnit is a nice htmlunit like wrapper around httpunit. When testing 
web apps, I only used jwebunit sofar.


What kind of javascript support are you using? the latest rhino library 
doesn't seem to play nice with xmlhttprequest library dojo. :-(


Martijn

Brett Porter wrote:


Steve Loughran wrote:

 


I think httpunit has a better reputation in the past for
quality/features; it even handles things like javascript.
   



Yes - I always read them interchangably unfortunately, but I definitely
prefer httpunit.

- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-490) Upload wicket-1.0.2-bundle.jar, wicket-1.1-b3-bundle.jar, wicket-extensions-1.1-b3-bundle.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.0.2-bundle.jar, wicket-1.1-b3-bundle.jar, 
wicket-extensions-1.1-b3-bundle.jar
-

 Key: MAVENUPLOAD-490
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-490
 Project: maven-upload-requests
Type: Task
 Reporter: Martijn Dashorst


http://wicket.sf.net/downloads/wicket-1.0.2-bundle.jar 
http://wicket.sf.net/downloads/wicket-1.1-b3-bundle.jar 
http://wicket.sf.net/downloads/wicket-extensions-1.1-b3.jar

http://wicket.sf.net
http://wicket.sf.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

Please upload.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Splitting commit messages and dev messages

[Martijn Dashorst]

Mark Hobson wrote:


+1 to splitting the lists - I've currently set up gmail to filter svn,
repoclean and continuum emails straight to trash ;)
 


Dito here.

Just for the record and to show that it is not totally unheard of, on 
the Wicket project we have also split the lists:

- user
- developer
- autocvs
- builds

The potential for autocvs and builds messages to flood the developer 
list is quite high, so we decided to seperate them into their own lists.



I'm interested in the development discussions, but I'm not a maven developer.
 


So am I.

Martijn

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MAVENUPLOAD-464) Upload wicket-1.1-b2-bundle.jar and wicket-extensions-1.1-b2-bundle.jar

[Martijn Dashorst (JIRA)]

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-464?page=comments#action_43878 ] 

Martijn Dashorst commented on MAVENUPLOAD-464:
--

the missing bundle has been uploaded. Sorry for the inconvenience (I have to 
stop creating releases at 12:00 am :-)

Thanks for your help and patience!

Martijn


> Upload wicket-1.1-b2-bundle.jar and wicket-extensions-1.1-b2-bundle.jar
> ---
>
>  Key: MAVENUPLOAD-464
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-464
>  Project: maven-upload-requests
> Type: Task
> Reporter: Martijn Dashorst

>
>
> http://wicket.sf.net/downloads/wicket-1.1-b2-bundle.jar
> http://wicket.sf.net/downloads/wicket-extensions-1.1-b2-bundle.jar
> http://wicket.sf.net/team-list.html
> http://wicket.sf.net
> Wicket is an open source, Apache 2 licensed, Java. component based web 
> application framework. Please upload.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-464) Upload wicket-1.1-b2-bundle.jar and wicket-extensions-1.1-b2-bundle.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.1-b2-bundle.jar and wicket-extensions-1.1-b2-bundle.jar
---

 Key: MAVENUPLOAD-464
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-464
 Project: maven-upload-requests
Type: Task
 Reporter: Martijn Dashorst


http://wicket.sf.net/downloads/wicket-1.1-b2-bundle.jar
http://wicket.sf.net/downloads/wicket-extensions-1.1-b2-bundle.jar

http://wicket.sf.net/team-list.html
http://wicket.sf.net

Wicket is an open source, Apache 2 licensed, Java. component based web 
application framework. Please upload.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MAVENUPLOAD-448) Upload wicket-1.1-b1-bundle.jar and wicket-extensions-1.1-b1-bundle.jar

[Martijn Dashorst (JIRA)]

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-448?page=comments#action_43345 ] 

Martijn Dashorst commented on MAVENUPLOAD-448:
--

The correct urls are:

http://wicket.sourceforge.net/downloads/wicket-1.1-b1-bundle.jar
http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b1-bundle.jar

Sorry for the mess.

Martijn


> Upload wicket-1.1-b1-bundle.jar and wicket-extensions-1.1-b1-bundle.jar
> ---
>
>  Key: MAVENUPLOAD-448
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-448
>  Project: maven-upload-requests
> Type: Task
> Reporter: Martijn Dashorst

>
>
> http://wicket.sourceforge.net/downloads/wicket-1.1-b1-bundle.jar
> http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b1.jar
> http://wicket.sourceforge.net
> http://wicket.sourceforge.net/team-list.html
> Please note: this upload contains two (2) uploads.
> Wicket is an open source, component based web application framework. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-448) Upload wicket-1.1-b1-bundle.jar and wicket-extensions-1.1-b1-bundle.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.1-b1-bundle.jar and wicket-extensions-1.1-b1-bundle.jar
---

 Key: MAVENUPLOAD-448
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-448
 Project: maven-upload-requests
Type: Task
 Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-1.1-b1-bundle.jar
http://wicket.sourceforge.net/downloads/wicket-extensions-1.1-b1.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Please note: this upload contains two (2) uploads.

Wicket is an open source, component based web application framework. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-443) upload wicket-extensions-1.0.1

[Martijn Dashorst (JIRA)]

upload wicket-extensions-1.0.1
--

 Key: MAVENUPLOAD-443
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-443
 Project: maven-upload-requests
Type: Task
 Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-extensions-1.0.1-bundle.jar

http://wicket.sourceforge.net/team-list.html
http://wicket.sourceforge.net

Wicket is a java, open source, component based web application framework.

Please upload.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-439) upload wicket-1.0.1

[Martijn Dashorst (JIRA)]

upload wicket-1.0.1
---

 Key: MAVENUPLOAD-439
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-439
 Project: maven-upload-requests
Type: Task
 Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-1.0.1-bundle.jar
http://wicket.sourceforge.net/downloads/wicket-extensions-1.0.1-bundle.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-400) Upload wicket-1.0-bundle.jar and wicket-extensions-1.0-bundle.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.0-bundle.jar and wicket-extensions-1.0-bundle.jar
-

 Key: MAVENUPLOAD-400
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-400
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sf.net/downloads/wicket-1.0-bundle.jar
http://wicket.sf.net/downloads/wicket-extensions-1.0-bundle.jar

http://wicket.sf.net
http://wicket.sf.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-393) Upload wicket-extensions-1.0.0-rc3

[Martijn Dashorst (JIRA)]

Upload wicket-extensions-1.0.0-rc3
--

 Key: MAVENUPLOAD-393
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-393
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-extensions-1.0.0-rc3-bundle.jar

http://wicket.sourceforge.net/
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

Please upload!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-392) Upload wicket-1.0.0-rc3

[Martijn Dashorst (JIRA)]

Upload wicket-1.0.0-rc3
---

 Key: MAVENUPLOAD-392
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-392
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-1.0.0-rc3-bundle.jar

http://wicket.sourceforge.net/
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

Please upload!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Continuum 1.0 Technology Preview Available

[Martijn Dashorst]

Also, downloading the continuum zip file directly from the site using
firefox 1.0.3 (and perhaps some download extension) doesn't go to the
mirror page, but opens a "save as" dialog, which falsely saves the
mirror page as a zip file.

Martijn

Martijn Dashorst wrote:

>On the frontpage of the continuum site, the link to maven2 points to the
>maven1 site.
>
>Martijn
>
>Jason van Zyl wrote:
>
>  
>
>>The Maven team is pleased to announce our Technology Preview
>>for the Continuum 1.0 release. Continuum is the Maven project's
>>Continuous integration tool. This release offers users both an advance
>>look at what's in Continuum 1.0 and a head start in helping to shape the
>>final Continuum release (currently slated for early August).
>>
>>Continuum 1.0 features includes:
>>
>>o Tight integration Maven 2.x
>>o Support for Maven 1.x
>>o Support for Ant
>>o Support for shell scripts
>>o Easy to use web interface
>>o An XML-RPC interface for integration, automation and remoting
>>o Easy to use command line shell interface using Python and the XML-RPC
>>interface
>>o Pluggable project registrars
>>o Pluggable project build triggers
>>o Pluggable notification schemes
>>
>>Please note, as a Technology Preview, this release is not intended for
>>production use.
>>
>>We plan to have 2-3 alphas and 1-2 betas prior to posting the release
>>candidates, which will be followed by the final release. We welcome any
>>and all feedback and look forward to your comments!
>>
>>http://maven.apache.org/continuum
>>http://maven.apache.org/continuum/download.html
>>
>>
>> 
>>
>>
>>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>  
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Continuum 1.0 Technology Preview Available

[Martijn Dashorst]

On the frontpage of the continuum site, the link to maven2 points to the
maven1 site.

Martijn

Jason van Zyl wrote:

>The Maven team is pleased to announce our Technology Preview
>for the Continuum 1.0 release. Continuum is the Maven project's
>Continuous integration tool. This release offers users both an advance
>look at what's in Continuum 1.0 and a head start in helping to shape the
>final Continuum release (currently slated for early August).
>
>Continuum 1.0 features includes:
>
>o Tight integration Maven 2.x
>o Support for Maven 1.x
>o Support for Ant
>o Support for shell scripts
>o Easy to use web interface
>o An XML-RPC interface for integration, automation and remoting
>o Easy to use command line shell interface using Python and the XML-RPC
>interface
>o Pluggable project registrars
>o Pluggable project build triggers
>o Pluggable notification schemes
>
>Please note, as a Technology Preview, this release is not intended for
>production use.
>
>We plan to have 2-3 alphas and 1-2 betas prior to posting the release
>candidates, which will be followed by the final release. We welcome any
>and all feedback and look forward to your comments!
>
>http://maven.apache.org/continuum
>http://maven.apache.org/continuum/download.html
>
>
>  
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-362) Upload wicket-1.0.0-rc2.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.0.0-rc2.jar
---

 Key: MAVENUPLOAD-362
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-362
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-1.0.0-rc2-bundle.jar
  
http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html
  
Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-363) Upload wicket-extensions-1.0.0-rc2.jar

[Martijn Dashorst (JIRA)]

Upload wicket-extensions-1.0.0-rc2.jar
--

 Key: MAVENUPLOAD-363
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-363
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-extensions-1.0.0-rc2-bundle.jar
  
http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html
  
Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ibiblio upload requests waiting

[Martijn Dashorst]

Hi,

I have created upload requests for two jar files of my projects. I have
seen more projects being stalled in JIRA since 1 april. Has the
procedure to upload libraries to ibiblio changed?

On another note, how can you become a synchronizer with Ibiblio, just as
mortbay, codehaus, etc.? What does it take to have our jars
automatically synchronized with ibiblio?

With regards,

Martijn Dashorst


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-352) Upload wicket-1.0.0-rc1.jar

[Martijn Dashorst (JIRA)]

Upload wicket-1.0.0-rc1.jar
---

 Key: MAVENUPLOAD-352
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-352
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-1.0.0-rc1-bundle.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-353) Upload wicket-extensions-1.0.0-rc1.jar

[Martijn Dashorst (JIRA)]

Upload wicket-extensions-1.0.0-rc1.jar
--

 Key: MAVENUPLOAD-353
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-353
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-extensions-1.0.0-rc1-bundle.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted using your favourite technology.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MPMULTIPROJECT-51) Mixing different maven.build.dir settings in multiproject fails

[Martijn Dashorst (JIRA)]

Mixing different maven.build.dir settings in multiproject fails
---

 Key: MPMULTIPROJECT-51
 URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-51
 Project: maven-multiproject-plugin
Type: Bug
Versions: 1.3
Reporter: Martijn Dashorst
 Assigned to: dion gillard 


If two projects have different maven.build.dir settings, the multiproject will 
assume that the artifacts of project A are actually in the maven.build.dir 
directory of project B (or vice versa).


Project A, project.properties

maven.build.dir=build

Project B, project.properties

maven.build.dir=target

Project B depends on Project A

Using the multiproject plugin for say multiproject:install will fail.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-314) http://wicket.sourceforge.net/downloads/wicket-0.9.19-beta-bundle.jar

[Martijn Dashorst (JIRA)]

http://wicket.sourceforge.net/downloads/wicket-0.9.19-beta-bundle.jar
-

 Key: MAVENUPLOAD-314
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-314
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-0.9.19-beta-bundle.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted with Hibernate.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-315) http://wicket.sourceforge.net/downloads/wicket-contrib-0.9.19-beta-bundle.jar

[Martijn Dashorst (JIRA)]

http://wicket.sourceforge.net/downloads/wicket-contrib-0.9.19-beta-bundle.jar
-

 Key: MAVENUPLOAD-315
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-315
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-contrib-0.9.19-beta-bundle.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted with Hibernate.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVENUPLOAD-316) http://wicket.sourceforge.net/downloads/wicket-extensions-0.9.19-beta-bundle.jar

[Martijn Dashorst (JIRA)]

http://wicket.sourceforge.net/downloads/wicket-extensions-0.9.19-beta-bundle.jar


 Key: MAVENUPLOAD-316
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-316
 Project: maven-upload-requests
Type: Task
Reporter: Martijn Dashorst


http://wicket.sourceforge.net/downloads/wicket-extensions-0.9.19-beta-bundle.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Dynamic content processing and form handling is all handled in Java code 
using a first-class component model backed by POJO data beans that can easily 
be persisted with Hibernate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jars on Ibiblio that shouldn't be?

[Martijn Dashorst]

Vincent Siveton wrote:
Hi,
Already discussed:
http://www.mail-archive.com/dev@maven.apache.org/msg08836.html
 

Reading the thread, I don't see any resolve. Just people claiming not to 
be a lawyer. ;-). I saw the JIRA issue closed as a 'NO FIX', so my guess 
is the jars have to be removed.

Lets update this property:
maven.repo.remote=http://mirrors.sunsite.dk/maven,http://www.ibiblio.org/maven
 

Why should this be done? This has nothing to do with the issue at hand, 
as sunsite is a _mirror_ of ibiblio, nothing more, nothing less.

Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jars on Ibiblio that shouldn't be?

[Martijn Dashorst]

Eric Pugh wrote:
Hi,
I was just testing commons-email which depends on javamail and
activiation jars, and via a Maven build it work!  It downloaded the
javamail and activation jars from ibiblio.  However, should those jars
be there?  Aren't there redistribution issues with Sun that prevent
them?
 

I was also wondering about this when I was attempting to write an 
article on using Maven in the context of the http://wicket.sf.net";>Wicket project. I stated that some jars 
couldn't be downloaded from the central repo, and was just checking 
which those were. I found them to my suprise, and had to alter the 
article. :-)

I wanted to ask the list, but thought about 'waking sleeping dogs' ;-)
Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Remote repository mirror mirrors.sunsite.dk/maven has invalid content?

[Martijn Dashorst]

OK
Thanks. All the other mirrors still work, but they are really slow ;-)
Just installed maven-proxy to fix the ibiblio slowness. Seems to work 
greatly, but could do better on the documentation and getting an 
official 1.0.

Martijn
Brett Porter wrote:
I will contact the mirror hosts. I'm not aware of any arrangement we 
had with them to do this, and assumed they were a pure ibiblio mirror.

They do have:
http://mirrors.sunsite.dk/apache/dist/java-repository/, which is a 
mirror of Apache releases.

- Brett
Martijn Dashorst wrote:
Hi,
I posted a message yesterday concerning this very annoying problem to 
the users list, but did not get an anwser. So I'm trying the dev list 
instead and hope to hear *if* this is an apache problem, or a sunsite 
problem.

The mirror now shows the distribution of maven instead of the remote 
repository contents. Can someone please look at this, because in 
Europe it is not feasable to use ibiblio as it is across the ocean 
and it gets quite cramped sometimes.

With regards,
Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Remote repository mirror mirrors.sunsite.dk/maven has invalid content?

[Martijn Dashorst]

Hi,
I posted a message yesterday concerning this very annoying problem to 
the users list, but did not get an anwser. So I'm trying the dev list 
instead and hope to hear *if* this is an apache problem, or a sunsite 
problem.

The mirror now shows the distribution of maven instead of the remote 
repository contents. Can someone please look at this, because in Europe 
it is not feasable to use ibiblio as it is across the ocean and it gets 
quite cramped sometimes.

With regards,
Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

New plugin? maven-news plugin

[Martijn Dashorst]

Hi!
I was wondering whether anybody was interested in a new plugin, which is 
like the changes plugin, but is used for generating news instead of 
release notes.

What is different from the changes contents? Well, a new committer, 
receiving funds, joining another project, etc. These are things you 
don't put in the changes.xml.

Features:
- generate RSS feed
- generate News page
- ability to submit news items to sourceforge.net
- ability to mail news items to (announcement) mailinglist
If anybody has an objection to such a plugin, please be gentle :-). 
Seriously, if you have better ideas, please let me know.

With regards,
Martijn Dashorst
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Maven 1.1 & upgrade to ant 1.6.2

[Martijn Dashorst]

Hi,
I saw an issue in JIRA for upgrading maven to use ant 1.6.2. I was 
wondering if this is done, or that I can provide any help on the matter. 
I constantly run into problems with the maven test plugin (more 
specifically the dependency on the ant 1.5.3 junit task).

Any thoughts on the release date of maven 1.1?
With regards,
Martijn Dashorst
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]