Hello!
I am not the first one with this problem, see
http://jira.codehaus.org/browse/MNG-2289.
We are not using the uniqueVersion feature (we don't want all the versions in
our repository).
We observe the behaviour with all our artifacts in a company maven-proxy. May
be it does not happen aga
I had some uncommitted changes. It should work now.
- Brett
On 3/07/2006 11:09 AM, Antoine Levy-Lambert wrote:
Hello Carlos,
sorry to bother you.
You say that I should add this section to the pom.xml of commons-sandbox :
org.apache
apache
1
and remove the repository par
Hello Carlos,
sorry to bother you.
You say that I should add this section to the pom.xml of commons-sandbox :
org.apache
apache
1
and remove the repository part : it is already commented out.
With these changes in the pom.xml of the commons-sandbox I still cannot
build open
yes, that's the one I was referring to, thanks!
On 3/07/2006 9:35 AM, Wendy Smoak wrote:
On 7/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Unfortunately the SNAPSHOT-feature is broken (at least in 2.0.4): When
you have a copy of a snapshot versioned artifact, the jar is not
updated when
On 7/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Unfortunately the SNAPSHOT-feature is broken (at least in 2.0.4): When you have a
copy of a snapshot versioned artifact, the jar is not updated when a new jar with
same snapshot version is uploaded to the repository. I already filed this a
You are right. It was turned off in the late betas because we were'nt
going to have time to verify the entire repository.
With the availability of tools, I think this could be reinstated for
2.1, but I've since rethought it and would rather do this in a way that
is more predictable (ie, even i
Now, they're referring to when uniqueVersion = false (which is not the
default). That feature has always been broken, it was only discovered
recently though, and when I attempted to fix it for 2.0.4 it caused a
performance degradation and I decided to hold off until it could be more
fully consi
Done - sorry it got missed first time round.
On 3/07/2006 8:43 AM, Mike Perham wrote:
Would someone mind updating me to PMC member in the root Maven POM at
pom/maven/pom.xml or give me permission to do it myself?
-
To unsubscri
Dear Canoo WebTest maven plugin developers!
Do you plan to release next plugin version based on Canoo WebTest 2.0
(http://www.canoo.com/news/webtest20.html)?
Kind regards,
Krystian Nowak
-
To unsubscribe, e-mail: [EMAIL PROT
Would someone mind updating me to PMC member in the root Maven POM at
pom/maven/pom.xml or give me permission to do it myself?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maybe they've been deploying versions using a normal repository element
instead of defining a snapshot repository and -SNAPSHOT version ?
On 7/2/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
YeahEven though in my instance it wasn't what I wanted to happen (not
maven's fault, unrelated local
YeahEven though in my instance it wasn't what I wanted to happen (not
maven's fault, unrelated local patches..), I have seen definite updates of
SNAPSHOT builds with the same version.
You can pretty easily infer why it works by looking at the timestamp
generated poms from them...
On 7/2/06,
I don't know what you're saying, you are the first one complaining
about it. SNAPSHOTS work for me
On 7/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Unfortunately the SNAPSHOT-feature is broken (at least in 2.0.4): When you have a
copy of a snapshot versioned artifact, the jar is not upda
I had the same problem. One quick fix in the mean time is to set
uniqueValue to true in the distributionManagement section of the
project pom.
On 7/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Unfortunately the SNAPSHOT-feature is broken (at least in 2.0.4): When you have a
copy of a snap
Unfortunately the SNAPSHOT-feature is broken (at least in 2.0.4): When you have
a copy of a snapshot versioned artifact, the jar is not updated when a new jar
with same snapshot version is uploaded to the repository. I already filed this
as a bug and hope it will be fixed in 2.0.5. It is annoyin
On Sun, 2 Jul 2006, Carlos Sanchez wrote:
Ah.. Well, it used to work in the beta's.. :)
There was a problem then with manually installed projects who lacked the
status field - it tried to download them from ibiblio which didn't have
them, and then the build failed. But that's a long time ago now.
That's not implemented yet. Maven won't recheck poms right now. It's
just informative
On 7/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
On Sun, 2 Jul 2006, Edwin Punzalan wrote:
That's not entirely true. The distributionManagement section
has a field that get's set on deploy:
http://mave
On Sun, 2 Jul 2006, Edwin Punzalan wrote:
That's not entirely true. The distributionManagement section
has a field that get's set on deploy:
http://maven.apache.org/ref/current/maven-model/maven.html#class_distributionManagement>
Gives the status of this artifact in the remote repository. This m
This is only true for release repositories though, as a snapshot
repository will have an updated version when you re-deploy surely?
Andy
On Sun, 2006-07-02 at 07:01 +0800, Edwin Punzalan wrote:
> May I add, that when maven already downloaded a poor/invalid pom, even
> after fixing the pom in the
19 matches
Mail list logo
