On Thu, Dec 4, 2008 at 2:27 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> The thing about that script is it generates a "default" pom which means it
> would have no dependency information, no license information, no pointers to
> qpids website, etc.That's probably not what you want at all.
On Thursday 04 December 2008 8:39:07 am Rafael Schloming wrote:
> Aidan Skinner wrote:
> > On Wed, Dec 3, 2008 at 8:08 PM, Rafael Schloming <[EMAIL PROTECTED]>
wrote:
> >> Aidan Skinner wrote:
> >>> There's a shell script sitting on my blog i've been meaning to
> >>> integrate that should be a goo
On Thu, Dec 4, 2008 at 1:39 PM, Rafael Schloming <[EMAIL PROTECTED]> wrote:
> Great, thanks. I think this takes care of the last issue. I'll possibly
> massage the script a bit and check it in somewhere before removing the maven
> poms.
Does it generate the dependency information properly? I reme
Aidan Skinner wrote:
On Wed, Dec 3, 2008 at 8:08 PM, Rafael Schloming <[EMAIL PROTECTED]> wrote:
Aidan Skinner wrote:
There's a shell script sitting on my blog i've been meaning to
integrate that should be a good starting point for this. It's on the
M3 announcement i think.
Can you post a lin
On Wed, Dec 3, 2008 at 8:08 PM, Rafael Schloming <[EMAIL PROTECTED]> wrote:
> Aidan Skinner wrote:
>>
>> There's a shell script sitting on my blog i've been meaning to
>> integrate that should be a good starting point for this. It's on the
>> M3 announcement i think.
>
> Can you post a link to thi
Aidan Skinner wrote:
There's a shell script sitting on my blog i've been meaning to
integrate that should be a good starting point for this. It's on the
M3 announcement i think.
Can you post a link to this? I wasn't able to google it.
--Rafael
Martin Ritchie wrote:
2008/12/3 Rajith Attapattu <[EMAIL PROTECTED]>:
+1 on removing the pom files.
But as Martin pointed out, we need to create poms (auto generated or hand
written) for client and common modules.
This will help other projects who are trying to integrate Qpid into their
projects
On Wed, Dec 3, 2008 at 11:17 AM, Martin Ritchie <[EMAIL PROTECTED]> wrote:
> 2008/12/3 Rajith Attapattu <[EMAIL PROTECTED]>:
> > +1 on removing the pom files.
> > But as Martin pointed out, we need to create poms (auto generated or hand
> > written) for client and common modules.
> > This will hel
2008/12/3 Rajith Attapattu <[EMAIL PROTECTED]>:
> +1 on removing the pom files.
> But as Martin pointed out, we need to create poms (auto generated or hand
> written) for client and common modules.
> This will help other projects who are trying to integrate Qpid into their
> projects.
> As for the
+1 on removing the pom files.
But as Martin pointed out, we need to create poms (auto generated or hand
written) for client and common modules.
This will help other projects who are trying to integrate Qpid into their
projects.
As for the perftest scripts, I thought Senka had something going with t
There's a shell script sitting on my blog i've been meaning to
integrate that should be a good starting point for this. It's on the
M3 announcement i think. The other thing that the ant files don't do
that they need too is generate the perf test scripts. Other than that,
i am +1^lots for getting ri
Martin Ritchie wrote:
2008/12/2 Rafael Schloming <[EMAIL PROTECTED]>:
Martin Ritchie wrote:
2008/12/2 Rafael Schloming <[EMAIL PROTECTED]>:
It's been noted in several different threads now that the maven poms
currently checked into SVN are out of date, don't work, and are confusing
people new
2008/12/2 Rafael Schloming <[EMAIL PROTECTED]>:
> Martin Ritchie wrote:
>>
>> 2008/12/2 Rafael Schloming <[EMAIL PROTECTED]>:
>>>
>>> It's been noted in several different threads now that the maven poms
>>> currently checked into SVN are out of date, don't work, and are confusing
>>> people new to
Martin Ritchie wrote:
2008/12/2 Rafael Schloming <[EMAIL PROTECTED]>:
It's been noted in several different threads now that the maven poms
currently checked into SVN are out of date, don't work, and are confusing
people new to the project.
So far the only reason given for retaining them is the
2008/12/2 Rafael Schloming <[EMAIL PROTECTED]>:
> It's been noted in several different threads now that the maven poms
> currently checked into SVN are out of date, don't work, and are confusing
> people new to the project.
>
> So far the only reason given for retaining them is the convenience of b
It's been noted in several different threads now that the maven poms
currently checked into SVN are out of date, don't work, and are
confusing people new to the project.
So far the only reason given for retaining them is the convenience of
being able to use them to generate IDEA/Eclipse projec
16 matches
Mail list logo
