John,
Won't that break for 2.0.x when running the ITs against them? I think
110 totally would irrelevant for 2.1, in which case the version could
just be (,2.1-SNAPSHOT) for the test.
But aside from that - why were plugin repositories deprecated? I don't
recall any discussion, proposal or
"...but anything that i share with other developers has a
release version. Each of our artifacts that in active development will get
released at least once a day."
That strikes me as working against the grain of agile development. Our
developers work across components and need to link in that
On Tue, 08 Jan 2008 14:25:06 dhoffer wrote:
> Regarding 1: Well that's not normal maven operation. You apparently have
> created a 'work-around' that works for you...I prefer to fix the bug so it
> works as it is specified.
>
> There are lots of reasons to deploy snapshots. Normal maven behavior
Regarding 1: Well that's not normal maven operation. You apparently have
created a 'work-around' that works for you...I prefer to fix the bug so it
works as it is specified.
There are lots of reasons to deploy snapshots. Normal maven behavior is
that everything, in development, is always a sn
We just avoid that being an issue in three ways...
1) I slap anyone around who deploys a snapshot to a remote repository unless
they have a _very_ good excuse. My method is to increment the major version
if there is a breaking change and release early to avoid the need for
snapshots. Ideally th
Which maven release/build is this in?
Based on my understanding I don't think this is sufficient to resolve this
issue. It needs to exclude 1.0.4-SNAPSHOT as well, let me try to explain.
If I specify a version range of [1.0,2.0) for a dependency, what I am saying
is that I will accept any RELEA
Sorry, can you provide a little more information on when this is
failing, how you're running Maven, and what the error is? I'm having
trouble replicating the problem using the integration tests in the
assembly plugin itself, using a fresh build of maven trunk.
Thanks,
-john
On Dec 21, 200
FYI a release seemed to be eminent a while ago [1], but it never
materialized somehow :-(
Jorg (another eager archetypeNG customer)
[1] http://thread.gmane.org/gmane.comp.jakarta.turbine.maven.devel/82488
On Jan 4, 2008 1:04 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> The archetypeNG plugin
Hi,
The vote has passed with the following result :
+1 (binding) : Dennis, Stephane, Arnaud
+1 (non binding) : Olivier
I will move the artifacts to the central repo and publish the new site.
Thanks,
--
Olivier
-
To unsubscribe,
of course :)
On 07/01/2008, at 5:09 PM, Rahul Thakur wrote:
Are more than one nominations allowed per person?
Rahul
Brett Porter wrote:
So the poll for progressing seems in favour.
Before we continue to vote on a proposal to send to the board, we
need to decide on a description for the p
+1
Arnaud
On Jan 7, 2008 9:23 AM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> No more PMC to push a +1 ?
>
> Thanks,
> --
> Olivier
>
> 2008/1/3, Olivier Lamy <[EMAIL PROTECTED]>:
> > Hi,
> > In preparation of Maven Jar Plugin release, I'd like to release Maven
> > Archiver 2.3.
> > As this
Hi,
No more PMC to push a +1 ?
Thanks,
--
Olivier
2008/1/3, Olivier Lamy <[EMAIL PROTECTED]>:
> Hi,
> In preparation of Maven Jar Plugin release, I'd like to release Maven
> Archiver 2.3.
> As this component doesn't have his own jira project, we have added a
> changes report which is available he
12 matches
Mail list logo
