On Mon, 23 Jun 2008 14:18:24 Ralph Goers wrote:
> > 2) because and i might be wrong but dependencyManagement messes with the
> > version defined up the chain when what I want is a localised enforcement,
> > its important to isolate the dependency and apply exclusions and version
> > restrictions to
Michael McCallum wrote:
On Mon, 23 Jun 2008 11:20:40 Ralph Goers wrote:
Why aren't you using dependencyManagement instead of the technique shown
below?
Good question, please refute/correct/flame if/where possible
1) there was no way to use dependencyManagement with deps when I adopt
On Mon, 23 Jun 2008 11:20:40 Ralph Goers wrote:
> Why aren't you using dependencyManagement instead of the technique shown
> below?
Good question, please refute/correct/flame if/where possible
1) there was no way to use dependencyManagement with deps when I adopted the
technique. This works now
Why aren't you using dependencyManagement instead of the technique shown
below?
Michael McCallum wrote:
On Sun, 22 Jun 2008 18:16:37 Ralph Goers wrote:
This is one of the problems that has bothered me for a while. It makes
no sense for a project to say I'm compatible with 3.8.x. How in the
Hi,
We solved 19 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139&styleName=Html&version=14166
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11139&status=1
Staging repo:
http://people.apache.org/~denni
On Sun, 22 Jun 2008 18:16:37 Ralph Goers wrote:
> This is one of the problems that has bothered me for a while. It makes
> no sense for a project to say I'm compatible with 3.8.x. How in the
> world could they know that? The dependent project might release a new
> 3.8.x release that isn't compatibl
On Sun, Jun 22, 2008 at 1:18 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> I need a release of plugin-tools 2.4.2 before I can release the next version
> of the Site plugin, because of MPLUGIN-107.
...
> If not, I can do the actual release unless someone else wants to.
Thanks, Dennis. This is
Le dimanche 22 juin 2008, Benjamin Bentmann a écrit :
> Dennis Lundberg wrote:
> > Do you have any more patches lying around?
>
> As for me, nope.
>
> > If not, I can do the actual release unless someone else wants to.
>
> Thanks Dennis, that would be awesome!
+1
>
>
> Benjamin
>
> ---
Dennis Lundberg wrote:
Do you have any more patches lying around?
As for me, nope.
If not, I can do the actual release unless someone else wants to.
Thanks Dennis, that would be awesome!
Benjamin
-
To unsubscribe, e-mai
Hi
I need a release of plugin-tools 2.4.2 before I can release the next
version of the Site plugin, because of MPLUGIN-107.
Looking at the road map [1] in JIRA, shows that it's Benjamin and Herve
that has been doing all the work. Do you have any more patches lying around?
If not, I can do t
You know someone is going to also desire not just the timestamp, but only
the time, or just the date. If you're doing the work now, might as well
throw in the other 2.
Paul
On Sun, Jun 22, 2008 at 1:46 AM, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi John,
>
> The document doesn't exactly explai
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11250&styleName=Html&version=12548
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11250&status=1
Staging repo:
http://people.apache.org/~dennis
On Sun, Jun 22, 2008 at 8:44 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 22-Jun-08, at 11:37 AM, Milos Kleint wrote:
>
>> On Sun, Jun 22, 2008 at 8:18 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>>>
>>> Milos,
>>>
>>> Do you need anything other then the standard embedder that's produced by
On 22-Jun-08, at 11:37 AM, Milos Kleint wrote:
On Sun, Jun 22, 2008 at 8:18 PM, Jason van Zyl <[EMAIL PROTECTED]>
wrote:
Milos,
Do you need anything other then the standard embedder that's
produced by the
build to run your automated tests?
I don't really have any automated tests. The wi
On Sun, Jun 22, 2008 at 8:18 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> Milos,
>
> Do you need anything other then the standard embedder that's produced by the
> build to run your automated tests?
I don't really have any automated tests. The wide variety of problems
I've encountered so far sor
Milos,
Do you need anything other then the standard embedder that's produced
by the build to run your automated tests?
I'm trying to hook the standard output to m2e, and I wanted to try and
do the same with the Netbeans integration so that we can get more
feedback on changes in the trunk
On 22-Jun-08, at 7:48 AM, Brett Porter wrote:
On 22/06/2008, at 10:35 PM, Jason van Zyl wrote:
Hudson is now failing, but the last people to sign off at least on
trunk will be Eugene/Igor, and Milos because even slight changes
affect embedding. We can't take any chances with the IDE
i
On 22/06/2008, at 10:35 PM, Jason van Zyl wrote:
Hudson is now failing, but the last people to sign off at least on
trunk will be Eugene/Igor, and Milos because even slight changes
affect embedding. We can't take any chances with the IDE integration
at this point.
Um... Hudson is passi
On 22-Jun-08, at 12:41 AM, Ralph Goers wrote:
Jason van Zyl wrote:
In the world where there is some rigour in that the said project
doesn't change the API within a major release they know very well.
In Eclipse a great deal of care is taken to make sure that APIs
don't change within a majo
On 22-Jun-08, at 6:44 AM, Brett Porter wrote:
Hi,
I have gone ahead and upgraded wagon to the newer release on 2.0.x
having done some testing to ensure that it worked with previous
extension declarations. This facilitates a large number of bugfixes,
two very visible ones being the proper
Hi,
I have gone ahead and upgraded wagon to the newer release on 2.0.x
having done some testing to ensure that it worked with previous
extension declarations. This facilitates a large number of bugfixes,
two very visible ones being the proper handling of proxies from
settings.xml and the
Jason van Zyl wrote:
Frankly, even if version ranges worked as above I'd still probably
not use them during a build simply because I want to specify exactly
what is used in the build. However, it would be great to know that
multiple projects have dependencies on incompatible versions of th
Jason van Zyl wrote:
In the world where there is some rigour in that the said project
doesn't change the API within a major release they know very well. In
Eclipse a great deal of care is taken to make sure that APIs don't
change within a major release of the platform and ranges in
dependencie
On 21-Jun-08, at 9:37 PM, Brett Porter wrote:
Hi Oleg, all,
I haven't dug into any of the code yet, but I've read through the
document you were working on. It seems positive and makes sense. I
did get a bit lost on the meaning of the "Tree Builder" section as
it doesn't seem to describe
On 22-Jun-08, at 12:03 AM, Oleg Gusakov wrote:
Ralph Goers wrote:
See below
Brett Porter wrote:
Hi Oleg, all,
I haven't dug into any of the code yet, but I've read through the
document you were working on. It seems positive and makes sense. I
did get a bit lost on the meaning of the "
On 21-Jun-08, at 11:16 PM, Ralph Goers wrote:
See below
Brett Porter wrote:
Hi Oleg, all,
I haven't dug into any of the code yet, but I've read through the
document you were working on. It seems positive and makes sense. I
did get a bit lost on the meaning of the "Tree Builder" section a
Ralph Goers wrote:
See below
Brett Porter wrote:
Hi Oleg, all,
I haven't dug into any of the code yet, but I've read through the
document you were working on. It seems positive and makes sense. I
did get a bit lost on the meaning of the "Tree Builder" section as it
doesn't seem to describ
27 matches
Mail list logo
