On 10/16/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Hi Dennis,
Dennis Lundberg wrote:
[snip]
==
>> --- maven/plugins/trunk/maven-clean-plugin/pom.xml (original) +++
>> maven/plugins/trunk/maven-clean-plugin/pom.xml Mo
Hi Dennis,
Dennis Lundberg wrote:
[snip]
==
>> --- maven/plugins/trunk/maven-clean-plugin/pom.xml (original) +++
>> maven/plugins/trunk/maven-clean-plugin/pom.xml Mon Oct 16 10:55:07 2006
>> @@ -9,7 +9,7 @@
>>maven-cl
I wouldn't make a feature-freeze just yet (I'm biased, as I have a
feature planned that is very minimal-impact. :) but I wouldn't wnat to
wait to release until the new year. I think momentum is an important
thing, and the change to group handling, the ui changes, plus the rbac
stuff makes continu
I agree with Emmanuel that since 1.1 as it currently stands is not
backwards compatible (I think) with the old database we ought to just
add in what we need now...But doing this will definitely move out a
1.1 release into the new year...and is that something we want to do?
I guess best to res
no, I changed it
On 10/17/06, Dan Tran <[EMAIL PROTECTED]> wrote:
is it a bug in release plugin?
-D
On 10/16/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>
> thanks for pointing, fixed!
>
> On 10/16/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] wrote:
> > > Author: car
is it a bug in release plugin?
-D
On 10/16/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
thanks for pointing, fixed!
On 10/16/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Author: carlos
> > Date: Mon Oct 16 10:55:07 2006
> > New Revision: 464589
> >
> > URL:
Hi,
I have been noticing an intialization error with database whenever the
Continuum webapp restarts. And then jetty freezes after encountering
that error. And it is making it hard to make any sort of even minor
changes to Continuum webapp resources (working on cleaning up some CSS
styles for
thanks for pointing, fixed!
On 10/16/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> Author: carlos
> Date: Mon Oct 16 10:55:07 2006
> New Revision: 464589
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=464589
> Log:
> [maven-release-plugin] prepare for next develop
sorry for the late vote, but I'm +1 as well! :-)
-john
On 10/15/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
Wendy you now have access to the site:
http://svn.apache.org/repos/asf/maven/site/trunk/
And I've sent you instructions for getting access to main Confluence
Wiki.
Jason.
On 1
[EMAIL PROTECTED] wrote:
Author: carlos
Date: Mon Oct 16 10:55:07 2006
New Revision: 464589
URL: http://svn.apache.org/viewvc?view=rev&rev=464589
Log:
[maven-release-plugin] prepare for next development iteration
Modified:
maven/plugins/trunk/maven-clean-plugin/pom.xml
Modified: maven/plug
Holly crap... by not using ${pom.version} that means we are forced to
put all of our modules into the dependencyManagement section of our
top-level pom... which is crazy. Geronimo's server/trunk has like 130
+ modules and growing. Keeping that dependencyManagement section up
to date is goi
I wouldn't like to push a release for more features, they can be
released whenever we want as 1.2.
Re backwards compatibility we should run some tool like clirr and minimize it.
We absolutely need a database migration tool, and will be useful in
next versions too.
I've heard about ActiveMapper,
Yes this is a known "don't do that." I got burned by it recently. See
here: http://jira.codehaus.org/browse/MNG-2486
-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Monday, October 16, 2006 2:27 PM
To: Maven Developers List
Cc: dev@geronimo.
So we have ...
1) Profiles (should call this build-profile)
This is a way to pre-define an environment type to execute the build
under.
Example of build-profile against a maven 2 java project:
* Choose the JDK to run with.
* Choose the Maven version to run with.
Example of bu
It is the default, this element is not set on any repos. Is the
default value true? Setting to false should keep it from using
timestamp versions?
What are the implications of this change?
--jason
On Oct 16, 2006, at 11:46 AM, Jörg Schaible wrote:
Hi Jason,
Jason Dillon wrote:
I thi
Hi Jason,
Jason Dillon wrote:
> I think I have tracked this down... looks like ${pom.version} is
> getting resolved to a timestamp version instead of the value it its
> parents element.
>
> Is this expected?
>
> If my parent has 1.1-SNAPSHOT, and an intermediate module defines a
> dependency u
I was going to try and wrap my head about what needed to get wrapped
up for a 1.1 release of continuum this week when I got to talking to
emmanuel this morning.
I had been under the impression that we were getting near a point that
we might want to polish things up and cut a 1.1 release but emm w
I think I have tracked this down... looks like ${pom.version} is
getting resolved to a timestamp version instead of the value it its
parents element.
Is this expected?
If my parent has 1.1-SNAPSHOT, and an intermediate module defines a
dependency using ${pom.version}, should this resolve
Hi,
If I don't want all my external dependencies bundled in the resulting war
artifact, how do I configure this in my project's pom? Basically I want the
functionality that was provided in Maven 1.x by adding the war.bundle
property to the dependencies I do want to include in the WEB-INF/lib
dire
Result:
+1 evenisse, vsiveton, jerdfelt, jdcasey, Brian E. Fox
Proceeding with the release
On 10/12/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
+1
Emmanuel
Carlos Sanchez a écrit :
> Last release was in February, and last change from august, can we
> release this?
>
> Changelog:
>
http:
I think that i have the same problem as Clover plugin as described in JIRA:
http://jira.codehaus.org/browse/MNG-2184
No ?
dvicente wrote:
>
> i have writed in my class DashBoardReportMojo :
> */**
> * A small tutorial that shows how to create a report.
> * @goal dashboard
> * @execute phas
On 16 Oct 06, at 9:43 AM 16 Oct 06, Brian E. Fox wrote:
I agree that promoting the actual built artifacts is the best way, but
what about projects that have filtered the build number into the
artifact somehow? (we use a property file that is filtered)
I'm sure we could arrive at a number tha
I agree that promoting the actual built artifacts is the best way, but
what about projects that have filtered the build number into the
artifact somehow? (we use a property file that is filtered)
-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sen
Kenney Westerhof wrote:
[snip - much discussion]
Hm. This only describes a major release.
I think that branches should be created off tags, and that a developer
should
do that, not a release plugin.
The above process looks ok for major releases (with reservations), but
we probably don't wa
i have writed in my class DashBoardReportMojo :
*/**
* A small tutorial that shows how to create a report.
* @goal dashboard
* @execute phase="post-site" lifecycle="site"
*/
public class DashBoardReportMojo extends DashBoardMojo implements
MavenReport {
and i have this error :
[INFO] Preparin
Hi David,
2006/10/16, dvicente <[EMAIL PROTECTED]>:
Hi,
i try what you write below but it doesn't work but i have missed something.
I have my first class like this :
/**
* A small tutorial that shows how to create a report.
* @goal generate
* @phase post-site
*/
public class DashBoardMoj
Hi,
i try what you write below but it doesn't work but i have missed something.
I have my first class like this :
/**
* A small tutorial that shows how to create a report.
* @goal generate
* @phase post-site
*/
public class DashBoardMojo extends AbstractMojo
after, i have my mojo report li
I think this is related to build numbers. You'll have 1.0 build
numbers 1001, 1002,... and you vote on the specific build number.
Maven would automatically use the build number in the manifest.
On 10/16/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Ya... the build would need to use the release num
[EMAIL PROTECTED] wrote on Monday, October 16, 2006 9:05 AM:
> Joakim Erdfelt <[EMAIL PROTECTED]> schrieb am 13.10.2006 20:06:51:
>
>>
> ==
> =
>> == LICENSE FILE / HEADER
>>
>> The LICENSE file is a unique monster in t
Joakim Erdfelt <[EMAIL PROTECTED]> schrieb am 13.10.2006 20:06:51:
>
===
> == LICENSE FILE / HEADER
>
> The LICENSE file is a unique monster in the world of apache.
> It will always be Apache v2.0.
Thank you. But please
30 matches
Mail list logo
