Hi,
For the record here's the doc of the Jira issues macro:
http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro
Cheers,
Stéphane
On 9/1/06, Brett Porter [EMAIL PROTECTED] wrote:
On 01/09/2006, at 6:55 AM, Dennis Lundberg wrote:
I'll have some time this weekend, so unless you beat
On 8/31/06, Brett Porter [EMAIL PROTECTED] wrote:
On 01/09/2006, at 12:54 AM, Franz Allan Valencia See wrote:
Good day to you, Brett,
There's lot of things to be done.
- implement triggering of the reports and recording of the results
do we now have designs on what events triggers what
Hi,
I just noticed that the jar plugin uses the property
${jar.forceCreation} as default of the new parameter forceCreation. I
find this choice most unfortunate.
Forcing creation is a very general concept: Almost any plugin could
use it, including compiler, assembly, war, ear, ejb,
On 01/09/2006, at 6:35 PM, Franz Allan Valencia See wrote:
btw, when one navigates to the other artifacts, what should be seen,
the [1] page, or something like [2] or what? ^_^
[1]
Sorry if i have too many questions. I am interested in working with
archiva, but i only know a small amount
IMO, if something is to be general, it should be considered for the
POM (like finalName).
- Brett
On 01/09/2006, at 6:26 PM, Jochen Wiedmann wrote:
Hi,
I just noticed that the jar plugin uses the property $
{jar.forceCreation} as default of the new parameter
forceCreation. I find this
Brett Porter wrote:
IMO, if something is to be general, it should be considered for the POM
(like finalName).
I must admit, that I do not understand what you have in mind?
Jochen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
build
forceCreation /
Or perhaps a well known property instead/in the interim:
properties
forceCreation /
Just a thought.
On 01/09/2006, at 6:50 PM, Jochen Wiedmann wrote:
Brett Porter wrote:
IMO, if something is to be general, it should be considered for
the POM (like finalName).
Brett Porter wrote:
Or perhaps a well known property instead/in the interim:
properties
forceCreation /
The latter point is what I am asking for. In the case of the jar plugin,
the property is jar.forceCreation, which I find unfortunate.
Again, any chance to get this changed? I'd
Just to stick my $0.02 worth in: I would not want a single parameter
that causes everything to change how it works like this. If we have a
single parameter value, then how would I, for example, force the WAR to
be rebuilt without making all of the JARs get rebuilt as well?
-Original
Hi,
We are working on a Maven SCM Provider for Synergy CM. Our customer is
La Poste, and it is planned that all the work will be donated to the
Maven community at the end of the development (10/20/2006).
We would like to obtain help from Telelogic (Synergy CM editor), and it
could be
Brett Porter wrote:
Could this break any existing tests?
Yes, if those tests were wrong. Effectively the difference is that
you no longer have $M2_HOME/core/*.jar in the classpath.
Two scenarios:
- the tests dependended on those libs but didn't declare them as test
dependencies.
This can
On 1 Sep 06, at 4:26 AM 1 Sep 06, Jochen Wiedmann wrote:
Hi,
I just noticed that the jar plugin uses the property $
{jar.forceCreation} as default of the new parameter
forceCreation. I find this choice most unfortunate.
We talked about it on the list and there was well longer then 72
Hi there.
I am converting my Maven 1 environment to Maven 2 am running into an issue
with a plugin I'm trying to update. This plugin basically filters some
template files, replacing placeholder values, places them within
directories under the project on which the plugin is being run. In Maven
On 9/1/06, Jason van Zyl [EMAIL PROTECTED] wrote:
We talked about it on the list and there was well longer then 72
hours this time. The prefix is for command line use and I asked if
the new standard could be used and folks agreed.
Jason, I understand completely, that it's my fault to miss
On 1 Sep 06, at 10:17 AM 1 Sep 06, Jochen Wiedmann wrote:
I do not understand where you see the problem. If all plugins that
support switching off an uptodate check honour the same property
(which of course they wouldn't do now, but AFAIK no plugins have
implemented that yet, so it is still
On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote:
Hi,
For the record here's the doc of the Jira issues macro:
http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro
I'm not sure there is enough in the macros to do what we need. I
asked David Blevins to help me use Swizzle to
Jason van Zyl wrote:
On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote:
Hi,
For the record here's the doc of the Jira issues macro:
http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro
I'm not sure there is enough in the macros to do what we need. I asked
David Blevins to
fogwolf [EMAIL PROTECTED] writes:
Hi there.
I am converting my Maven 1 environment to Maven 2 am running into an issue
with a plugin I'm trying to update. This plugin basically filters some
template files, replacing placeholder values, places them within
directories under the project on
Jason van Zyl wrote:
On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote:
Hi,
For the record here's the doc of the Jira issues macro:
http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro
I'm not sure there is enough in the macros to do what we need. I asked
David Blevins to
Dear Madam/Sir,
I am an MBA student at Oxford Brookes University (http://www.brookes.ac.uk).
The following questions are for my dissertation. The dissertation is about how
the recruitment and selection of human resource management can help the
software development company establish creative
Jason van Zyl wrote:
I'm not sure there is enough in the macros to do what we need. I asked
David Blevins to help me use Swizzle to create a list of all the
outstanding issues for plugins that have votes. I would like to sum the
votes in each plugin project and then sort them in ranked order.
On 1 Sep 06, at 11:33 AM 1 Sep 06, Joakim Erdfelt wrote:
Jason van Zyl wrote:
On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote:
Hi,
For the record here's the doc of the Jira issues macro:
http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro
I'm not sure there is enough
On 1 Sep 06, at 11:48 AM 1 Sep 06, Joakim Erdfelt wrote:
Jason van Zyl wrote:
On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote:
Hi,
For the record here's the doc of the Jira issues macro:
http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro
I'm not sure there is enough
Be careful, you overwrote my changes
On 8/31/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: joakime
Date: Thu Aug 31 19:56:28 2006
New Revision: 439148
URL: http://svn.apache.org/viewvc?rev=439148view=rev
Log:
* Correction various svn properties.
* Correcting jpox/jdo handling for new
24 matches
Mail list logo
