well, when you look at it like that...
ok, I'll do that this weekend and try and get a home for those poor 61
lonely issues :)
jesse
On 11/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
I think breaking out the tools and notifiers is a good idea. They are
actually the *easiest* ones for people
I have every intention of documenting and releasing this for use in plugin
integration-testing. I'm not sure why we'd put this in the testing harness,
as it's a very different type of testing that this enables. As for mangling
the pom, I'm only doing at most two things:
1. changing the version to
I think breaking out the tools and notifiers is a good idea. They are
actually the *easiest* ones for people to hit because they know which
specific one they are using.
How about breaking up core system into scheduling, etc? Also, is
there anything in those 61 no components that should be a
John,
There's a lot of stuff there. Can you write a doc for how to use it?
I can't really grok what all the local repository shuffling etc is
meant for. And mangling POMs for testing sounds like a bad thing :)
Also, should it be part of the existing testing harness?
A lot of this code also
well thats a little more verbose then I was looking for, I was
thinking we could shove all the tool integration stuff together, and
all the notifiers together. I was envisioning
Core system 80
Database 16
Documentation 12
Tool Integration
Notification 5
SCM 18
Web UI 89
W
Breaking apart the notifiers are a good idea.
However, due to natural language sort, they are not grouped very
efficiently.
How about "Notifier ___" instead?
So, expanding your ideas to a the eventual list, we wind up with ...
Core system 80
Database 16
Documentation 12
Integration M
The current components in jira are (with current # of categoried issues):
AOL Notifier 1
Core system 80
Database16
Documentation 12
IRC Notifier3
Jabber Notifier 3
Mail Notifier 14
MSN Notifier2
Notification5
Project Grouping1
SCM 18
Web interfac
artifactId is taken from jar name
On 11/10/06, Nicolas DE LOOF <[EMAIL PROTECTED]> wrote:
Hello,
I'd like to add some artifacts from WSAD in my private repo, and I'm
looking at repo1.maven.org/eclipse to follow "conventions" about
eclipse/ibm artifacts.
Any artifact gets the full eclipse plug
Hello,
I try to develop a maven-script-ant plugin.
The idea is to migrate my project from an existing ant into a maven2
(2.0.4).
So my first step was to generalize my exising ANT targets and create
Seperate Maven2 plugins. I do this reading the Guide:
http://maven.apache.org/guides/plugin/guide-
Hello,
I'd like to add some artifacts from WSAD in my private repo, and I'm
looking at repo1.maven.org/eclipse to follow "conventions" about
eclipse/ibm artifacts.
Any artifact gets the full eclipse plugin name. Is there so many
duplicates that makes this a requirement ?
Nico.
This m
10 matches
Mail list logo
