Jason van Zyl wrote:
Should be good now.
Thanks Jason, but I still don't see an Edit tab on that page. Am I
doing something wrong?
Ralph
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
In that case I think the warning about a missing POM needs to be
stronger and make people aware of the implications of someone suddenly
uploading one.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, 16 October 2007 8:22 AM
To
i don't agree, the point of not having a pom there is to be able to
add one later with the right info. If you work against something
without pom, hey, it's your decision, but you are aware that it's a
problem, as all the warnings tell you
On 10/15/07, William Ferguson <[EMAIL PROTECTED]> wrote:
>
Isn't the goal here to stop incessant warnings during a build about
trying to downalod a missing POM?
The way to do that is to that is to upload a POM for that artifact to
the repository.
But Nico is right is that the uploaded POM should not break existing
builds. Which means that the POM just ne
On 10/15/07, olivier lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> I have fixed both (thanks for the patch).
> A new maven-war-plugin snapshot have been deployed
> maven-war-plugin-2.1-alpha-1-20071015.195227-3.jar.
> Can you try it ?
Works perfectly, I've tried 5 different projects and didn't find
any
Hi,
I have fixed both (thanks for the patch).
A new maven-war-plugin snapshot have been deployed
maven-war-plugin-2.1-alpha-1-20071015.195227-3.jar.
Can you try it ?
Thanks,
--
Olivier
2007/10/14, Tomasz Pik <[EMAIL PROTECTED]>:
>
> On 10/14/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> > I h
sorry, but that's not the case currently. If it has no metadata it can
be added, that's why you get warnings when the metadata is missing.
On 10/15/07, nicolas de loof <[EMAIL PROTECTED]> wrote:
> I fully agree about collaborating and submitting more artifacts to the repo
> with good meta-datas. T
I fully agree about collaborating and submitting more artifacts to the repo
with good meta-datas. The only issue I can see is about reproductible builds
if those meta-datas change.
The established rule NOT to change meta-datas after publication applies IMHO
also to artifacts without meta-datas. An
I'm getting
ssh [EMAIL PROTECTED]
THIS MACHINE IS NO LONGER THE STAGING MACHINE.
stage.mysql.com has been moved to new hardware. it is accessible
via in the internal network as 'stage'. the external ip has not
yet been shifted.
jimw (2005-7-14)
This account is currently not available.
Connection
On 10/15/07, nicolas de loof <[EMAIL PROTECTED]> wrote:
> I'm not the guy who uploaded castor 1.0 on the maven repo, and I'm also not
> the guy who used it in the project. I came later and have to maintain the
> project now.
that's collaboration ;) if you want to use something that uses castor
and
I'm not the guy who uploaded castor 1.0 on the maven repo, and I'm also not
the guy who used it in the project. I came later and have to maintain the
project now.
Do you think I should contribute an empty POM just to ensure no-one can
latter contribute one with some (maybe) unexpected dependencies
On 10/11/07, nicolas de loof <[EMAIL PROTECTED]> wrote:
> Warning : This could break existing projects !
>
> My project has a dependency on castor-1.0. This one has no POM.
> If you povide one, rebuilding my app will introduce new transitive
> dependencies that were not expected, and my build will
12 matches
Mail list logo
