You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Donald Woods <dr...@yahoo.com> on 2006/10/13 22:43:02 UTC
Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?
Having build problems today and wondering if the below genesis change
yesterday is causing it?
Started with a new trunk checkout directory on a SLES10 x86 machine.
Removed the existing .m2 repo.
bootstrap clean ran fine.
bootstrap specs is failing (also tried mvn -U install from
target/external/specs) because the file version=1.1-20061013.014841-21
is not in the snapshot repo, but version=1.1-20061013.014841-23 is.
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin-support \
-Dversion=1.1-20061013.014841-21 -Dpackaging=jar
-Dfile=/path/to/file
Path to dependency:
1)
org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:1.1-20061013.014841-21
2)
org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-20061013.014841-21
----------
1 required artifact is missing.
for artifact:
org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:1.1-20061013.014841-21
from the specified remote repositories:
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
central (http://repo1.maven.org/maven2),
codehaus (http://repository.codehaus.org),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)
jdillon@apache.org wrote:
> Author: jdillon
> Date: Thu Oct 12 20:54:00 2006
> New Revision: 463555
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=463555
> Log:
> Add tools profile to enable tools-m-p and m-m-p to all projects
>
> Modified:
> geronimo/genesis/trunk/config/project-config/pom.xml
>
> Modified: geronimo/genesis/trunk/config/project-config/pom.xml
> URL: http://svn.apache.org/viewvc/geronimo/genesis/trunk/config/project-config/pom.xml?view=diff&rev=463555&r1=463554&r2=463555
> ==============================================================================
> --- geronimo/genesis/trunk/config/project-config/pom.xml (original)
> +++ geronimo/genesis/trunk/config/project-config/pom.xml Thu Oct 12 20:54:00 2006
> @@ -508,6 +508,24 @@
> <activeByDefault>true</activeByDefault>
> </activation>
> </profile>
> +
> + <profile>
> + <id>tools</id>
> +
> + <build>
> + <plugins>
> + <plugin>
> + <groupId>org.apache.geronimo.genesis.plugins</groupId>
> + <artifactId>tools-maven-plugin</artifactId>
> + </plugin>
> +
> + <plugin>
> + <groupId>org.apache.geronimo.genesis.plugins</groupId>
> + <artifactId>maven-maven-plugin</artifactId>
> + </plugin>
> + </plugins>
> + </build>
> + </profile>
> </profiles>
>
> <reporting>
>
>
>
Re: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Jason Dillon <ja...@planet57.com>.
On Oct 14, 2006, at 6:58 AM, Kenney Westerhof wrote:
> Running mvn with -U -cpu should fix that (or wait 24 hours and try
> again :)).
I don't think this helps... at least not the wait 24 hours. I was up
late and was running a build at 11:50pm and it ran fine, then ran a
build at 12:02am and it puked about missing versions from genesis 1.1-
SNAPSHOT versions... which I had versions in my local repo that were
all newer than any snap that I had deployed.... and I am the only one
who deploys them, so no chance that it as deployed by someone else.
The only way I could fix was to build genesis locally after the
failed 12:02am build. But the crazy part was that I had just done
that at about 11:40pm, did *not deploy* so my local copy was newer,
but maven decided not to resolve to those versions?!?!
I don't think using `mvn -U` helps either, as that negates the use of
caching SNAPSHOTs and will slowdown the build way to much.
> Another solution is to delete the metadata file from the local
> repository.
Nope... this does not work either as the problem shows up quite often
when you removed you local repo and build... ie... no local metadata
at all. So I don't think the problem is there.
If there is a problem with the local metadata it is getting corrupted
while mvn is running, so even removing the local repo cache will not
ensure that the run will succeed.
> Btw, how come the original snapshot versions are removed from the
> remote repository?
> The local metadata file probably contains a reference to the old
> snapshot version,
> but doesn't seem to have it locally, which needs investigation..
Who said anything about removing anything? The genesis 1.1-SNAPSHOTS
have not been altered ore removed from the remote repo. In the
specific problem build 1 - 23 of plugin-support are all available.
> As for the other snapshot errors: Maven 1 legacy repositories don't
> contain metadata files. Updating snapshots from them doesn't seem
> to work. That's another thing that
> should be investigated.
>
> I personally never have problems with snapshot versions, so maybe
> the use of maven 1 repositories
> and the removal of snapshots from the remote repository isn't
> handled correctly by Maven.
I know there are issues with m1 repos... not specific to snapshots...
though unfortunately we can not eliminate them completely from out
build because we have a few dependencies which define m1 repos in
their poms.
But... I think that use of m1 repos is only one of the problems going
on here... something else, which I have yet to understand, is broken.
One thing does look very fishy to me though....
<snip>
1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -
DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin-
support \
-Dversion=1.1-20061013.014841-21 -Dpackaging=jar -Dfile=/
path/to/file
Path to dependency:
1) org.apache.geronimo.genesis.plugins:tools-maven-
plugin:maven-plugin:1.1-20061013.014841-21 2)
org.apache.geronimo.genesis.plugins:plugin-support:jar:
1.1-20061013.014841-21 ----------
1 required artifact is missing.
for artifact:
org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:
1.1-20061013.014841-21 from the specified
</snip>
Notice that the tools-maven-plugin's timestamp-build is
"20061013.014841-21" and this is also the same timestamp-build that
is being used for the plugin-support jar. However the real timestamp
for build 21 of plugins-support is "20061012.062745".
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Jason Dillon <ja...@planet57.com>.
On Oct 14, 2006, at 6:58 AM, Kenney Westerhof wrote:
> Running mvn with -U -cpu should fix that (or wait 24 hours and try
> again :)).
I don't think this helps... at least not the wait 24 hours. I was up
late and was running a build at 11:50pm and it ran fine, then ran a
build at 12:02am and it puked about missing versions from genesis 1.1-
SNAPSHOT versions... which I had versions in my local repo that were
all newer than any snap that I had deployed.... and I am the only one
who deploys them, so no chance that it as deployed by someone else.
The only way I could fix was to build genesis locally after the
failed 12:02am build. But the crazy part was that I had just done
that at about 11:40pm, did *not deploy* so my local copy was newer,
but maven decided not to resolve to those versions?!?!
I don't think using `mvn -U` helps either, as that negates the use of
caching SNAPSHOTs and will slowdown the build way to much.
> Another solution is to delete the metadata file from the local
> repository.
Nope... this does not work either as the problem shows up quite often
when you removed you local repo and build... ie... no local metadata
at all. So I don't think the problem is there.
If there is a problem with the local metadata it is getting corrupted
while mvn is running, so even removing the local repo cache will not
ensure that the run will succeed.
> Btw, how come the original snapshot versions are removed from the
> remote repository?
> The local metadata file probably contains a reference to the old
> snapshot version,
> but doesn't seem to have it locally, which needs investigation..
Who said anything about removing anything? The genesis 1.1-SNAPSHOTS
have not been altered ore removed from the remote repo. In the
specific problem build 1 - 23 of plugin-support are all available.
> As for the other snapshot errors: Maven 1 legacy repositories don't
> contain metadata files. Updating snapshots from them doesn't seem
> to work. That's another thing that
> should be investigated.
>
> I personally never have problems with snapshot versions, so maybe
> the use of maven 1 repositories
> and the removal of snapshots from the remote repository isn't
> handled correctly by Maven.
I know there are issues with m1 repos... not specific to snapshots...
though unfortunately we can not eliminate them completely from out
build because we have a few dependencies which define m1 repos in
their poms.
But... I think that use of m1 repos is only one of the problems going
on here... something else, which I have yet to understand, is broken.
One thing does look very fishy to me though....
<snip>
1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -
DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin-
support \
-Dversion=1.1-20061013.014841-21 -Dpackaging=jar -Dfile=/
path/to/file
Path to dependency:
1) org.apache.geronimo.genesis.plugins:tools-maven-
plugin:maven-plugin:1.1-20061013.014841-21 2)
org.apache.geronimo.genesis.plugins:plugin-support:jar:
1.1-20061013.014841-21 ----------
1 required artifact is missing.
for artifact:
org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:
1.1-20061013.014841-21 from the specified
</snip>
Notice that the tools-maven-plugin's timestamp-build is
"20061013.014841-21" and this is also the same timestamp-build that
is being used for the plugin-support jar. However the real timestamp
for build 21 of plugins-support is "20061012.062745".
--jason
Re: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Jason Dillon <ja...@planet57.com>.
I think I have tracked this down... looks like ${pom.version} is
getting resolved to a timestamp version instead of the value it its
parents <version> element.
Is this expected?
If my parent has 1.1-SNAPSHOT, and an intermediate module defines a
dependency using ${pom.version}, should this resolve to 1.1-SNAPSHOT
or to 1.1-<timestamp>-<build> for the current module?
--jason
On Oct 14, 2006, at 6:58 AM, Kenney Westerhof wrote:
> The problem below seems to indicate that the local repository
> contains an old metadata file.
>
> Running mvn with -U -cpu should fix that (or wait 24 hours and try
> again :)).
>
> Another solution is to delete the metadata file from the local
> repository.
>
> Btw, how come the original snapshot versions are removed from the
> remote repository?
> The local metadata file probably contains a reference to the old
> snapshot version,
> but doesn't seem to have it locally, which needs investigation..
>
> As for the other snapshot errors: Maven 1 legacy repositories don't
> contain metadata files. Updating snapshots from them doesn't seem
> to work. That's another thing that
> should be investigated.
>
> I personally never have problems with snapshot versions, so maybe
> the use of maven 1 repositories
> and the removal of snapshots from the remote repository isn't
> handled correctly by Maven.
>
> -- Kenney
>
> Jason Dillon wrote:
>> Folks... maven's handling of *SNAPSHOT artifacts is killing us.
>> Any idea what is going on... and how we can fix this. Its an
>> ongoing problem, seems like new timestamp mismatch problems are
>> popping up quite often now. I've already removed our direct use
>> of m1 repos to get around some problems resolving artifacts... but
>> something is still very broken with maven's SNAPSHOT mechanism.
>> Any ideas?
>> --jason
>> Begin forwarded message:
>>> From: Jason Dillon <ja...@planet57.com>
>>> Date: October 13, 2006 2:00:50 PM PDT
>>> To: dev@geronimo.apache.org
>>> Cc: Jason van Zyl <ja...@maven.org>
>>> Subject: Maven's snapshot mechanism is horked (Re: Build error -
>>> Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/
>>> project-config/pom.xml?)
>>>
>>> Yes, build genesis locally for now to get around... I'm gonna
>>> need to get the maven peeps to explain wtf is going on... and
>>> hopefully fix maven to not freak out like this.
>>>
>>> The metadata for plugin-support is correct... showing the latest
>>> 1.1-SNAPSHOT is -23:
>>>
>>> <metadata>
>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>> <artifactId>plugin-support</artifactId>
>>> <version>1.1-SNAPSHOT</version>
>>> <versioning>
>>> <snapshot>
>>> <timestamp>20061013.014841</timestamp>
>>> <buildNumber>23</buildNumber>
>>> </snapshot>
>>> <lastUpdated>20061013014947</lastUpdated>
>>> </versioning>
>>> </metadata>
>>>
>>> And -23 is there:
>>>
>>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/
>>> geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
>>> support-1.1-20061013.014841-23.jar
>>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/
>>> geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
>>> support-1.1-20061013.014841-23.pom
>>>
>>> So, Maven *should* be resolving any 1.1-SNAPSHOT of plugin-config
>>> to these files... but...
>>>
>>> --jason
>>>
>>>
>>> On Oct 13, 2006, at 1:50 PM, Joe Bohn wrote:
>>>
>>>> Prasad and I hit the same problem earlier today. There must be
>>>> something strange going on with the version # where "21" is
>>>> being assumed instead of the "23" that is actually in the repo.
>>>> I'm hoping that Jason will know what exactly is going on and how
>>>> to fix it and I suspect it may be related to one of his changes.
>>>>
>>>> To get around the problem for now you can build genesis
>>>> locally. That worked for me.
>>>>
>>>> Joe
>>>>
>>>>
>>>> Donald Woods wrote:
>>>>> Having build problems today and wondering if the below genesis
>>>>> change yesterday is causing it?
>>>>> Started with a new trunk checkout directory on a SLES10 x86
>>>>> machine.
>>>>> Removed the existing .m2 repo.
>>>>> bootstrap clean ran fine.
>>>>> bootstrap specs is failing (also tried mvn -U install from
>>>>> target/external/specs) because the file
>>>>> version=1.1-20061013.014841-21 is not in the snapshot repo, but
>>>>> version=1.1-20061013.014841-23 is.
>>>>> ------------------------------------------------------------------
>>>>> ------
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO]
>>>>> ------------------------------------------------------------------
>>>>> ------
>>>>> [INFO] Failed to resolve artifact.
>>>>> Missing:
>>>>> ----------
>>>>> 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-
>>>>> SNAPSHOT
>>>>> Try downloading the file manually from the project website.
>>>>> Then, install it using the command:
>>>>> mvn install:install-file -
>>>>> DgroupId=org.apache.geronimo.genesis.plugins -
>>>>> DartifactId=plugin-support \
>>>>> -Dversion=1.1-20061013.014841-21 -Dpackaging=jar -
>>>>> Dfile=/path/to/file
>>>>> Path to dependency:
>>>>> 1) org.apache.geronimo.genesis.plugins:tools-maven-
>>>>> plugin:maven-plugin:1.1-20061013.014841-21 2)
>>>>> org.apache.geronimo.genesis.plugins:plugin-support:jar:
>>>>> 1.1-20061013.014841-21 ----------
>>>>> 1 required artifact is missing.
>>>>> for artifact:
>>>>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
>>>>> plugin:1.1-20061013.014841-21 from the specified remote
>>>>> repositories:
>>>>> apache.snapshots (http://people.apache.org/repo/m2-snapshot-
>>>>> repository),
>>>>> codehaus-snapshots (http://snapshots.repository.codehaus.org),
>>>>> central (http://repo1.maven.org/maven2),
>>>>> codehaus (http://repository.codehaus.org),
>>>>> apache-snapshots (http://people.apache.org/repo/m2-snapshot-
>>>>> repository)
>>>>> jdillon@apache.org wrote:
>>>>>> Author: jdillon
>>>>>> Date: Thu Oct 12 20:54:00 2006
>>>>>> New Revision: 463555
>>>>>>
>>>>>> URL: http://svn.apache.org/viewvc?view=rev&rev=463555
>>>>>> Log:
>>>>>> Add tools profile to enable tools-m-p and m-m-p to all projects
>>>>>>
>>>>>> Modified:
>>>>>> geronimo/genesis/trunk/config/project-config/pom.xml
>>>>>>
>>>>>> Modified: geronimo/genesis/trunk/config/project-config/pom.xml
>>>>>> URL: http://svn.apache.org/viewvc/geronimo/genesis/trunk/
>>>>>> config/project-config/pom.xml?
>>>>>> view=diff&rev=463555&r1=463554&r2=463555
>>>>>> =================================================================
>>>>>> =============
>>>>>> --- geronimo/genesis/trunk/config/project-config/pom.xml
>>>>>> (original)
>>>>>> +++ geronimo/genesis/trunk/config/project-config/pom.xml Thu
>>>>>> Oct 12 20:54:00 2006
>>>>>> @@ -508,6 +508,24 @@
>>>>>> <activeByDefault>true</activeByDefault>
>>>>>> </activation>
>>>>>> </profile>
>>>>>> + + <profile>
>>>>>> + <id>tools</id>
>>>>>> +
>>>>>> + <build>
>>>>>> + <plugins>
>>>>>> + <plugin>
>>>>>> +
>>>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>>>> + <artifactId>tools-maven-plugin</
>>>>>> artifactId>
>>>>>> + </plugin>
>>>>>> +
>>>>>> + <plugin>
>>>>>> +
>>>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>>>> + <artifactId>maven-maven-plugin</
>>>>>> artifactId>
>>>>>> + </plugin>
>>>>>> + </plugins>
>>>>>> + </build>
>>>>>> + </profile>
>>>>>> </profiles>
>>>>>> <reporting>
>>>>>>
>>>>>>
>>>>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Jason Dillon <ja...@planet57.com>.
I think I have tracked this down... looks like ${pom.version} is
getting resolved to a timestamp version instead of the value it its
parents <version> element.
Is this expected?
If my parent has 1.1-SNAPSHOT, and an intermediate module defines a
dependency using ${pom.version}, should this resolve to 1.1-SNAPSHOT
or to 1.1-<timestamp>-<build> for the current module?
--jason
On Oct 14, 2006, at 6:58 AM, Kenney Westerhof wrote:
> The problem below seems to indicate that the local repository
> contains an old metadata file.
>
> Running mvn with -U -cpu should fix that (or wait 24 hours and try
> again :)).
>
> Another solution is to delete the metadata file from the local
> repository.
>
> Btw, how come the original snapshot versions are removed from the
> remote repository?
> The local metadata file probably contains a reference to the old
> snapshot version,
> but doesn't seem to have it locally, which needs investigation..
>
> As for the other snapshot errors: Maven 1 legacy repositories don't
> contain metadata files. Updating snapshots from them doesn't seem
> to work. That's another thing that
> should be investigated.
>
> I personally never have problems with snapshot versions, so maybe
> the use of maven 1 repositories
> and the removal of snapshots from the remote repository isn't
> handled correctly by Maven.
>
> -- Kenney
>
> Jason Dillon wrote:
>> Folks... maven's handling of *SNAPSHOT artifacts is killing us.
>> Any idea what is going on... and how we can fix this. Its an
>> ongoing problem, seems like new timestamp mismatch problems are
>> popping up quite often now. I've already removed our direct use
>> of m1 repos to get around some problems resolving artifacts... but
>> something is still very broken with maven's SNAPSHOT mechanism.
>> Any ideas?
>> --jason
>> Begin forwarded message:
>>> From: Jason Dillon <ja...@planet57.com>
>>> Date: October 13, 2006 2:00:50 PM PDT
>>> To: dev@geronimo.apache.org
>>> Cc: Jason van Zyl <ja...@maven.org>
>>> Subject: Maven's snapshot mechanism is horked (Re: Build error -
>>> Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/
>>> project-config/pom.xml?)
>>>
>>> Yes, build genesis locally for now to get around... I'm gonna
>>> need to get the maven peeps to explain wtf is going on... and
>>> hopefully fix maven to not freak out like this.
>>>
>>> The metadata for plugin-support is correct... showing the latest
>>> 1.1-SNAPSHOT is -23:
>>>
>>> <metadata>
>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>> <artifactId>plugin-support</artifactId>
>>> <version>1.1-SNAPSHOT</version>
>>> <versioning>
>>> <snapshot>
>>> <timestamp>20061013.014841</timestamp>
>>> <buildNumber>23</buildNumber>
>>> </snapshot>
>>> <lastUpdated>20061013014947</lastUpdated>
>>> </versioning>
>>> </metadata>
>>>
>>> And -23 is there:
>>>
>>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/
>>> geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
>>> support-1.1-20061013.014841-23.jar
>>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/
>>> geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
>>> support-1.1-20061013.014841-23.pom
>>>
>>> So, Maven *should* be resolving any 1.1-SNAPSHOT of plugin-config
>>> to these files... but...
>>>
>>> --jason
>>>
>>>
>>> On Oct 13, 2006, at 1:50 PM, Joe Bohn wrote:
>>>
>>>> Prasad and I hit the same problem earlier today. There must be
>>>> something strange going on with the version # where "21" is
>>>> being assumed instead of the "23" that is actually in the repo.
>>>> I'm hoping that Jason will know what exactly is going on and how
>>>> to fix it and I suspect it may be related to one of his changes.
>>>>
>>>> To get around the problem for now you can build genesis
>>>> locally. That worked for me.
>>>>
>>>> Joe
>>>>
>>>>
>>>> Donald Woods wrote:
>>>>> Having build problems today and wondering if the below genesis
>>>>> change yesterday is causing it?
>>>>> Started with a new trunk checkout directory on a SLES10 x86
>>>>> machine.
>>>>> Removed the existing .m2 repo.
>>>>> bootstrap clean ran fine.
>>>>> bootstrap specs is failing (also tried mvn -U install from
>>>>> target/external/specs) because the file
>>>>> version=1.1-20061013.014841-21 is not in the snapshot repo, but
>>>>> version=1.1-20061013.014841-23 is.
>>>>> ------------------------------------------------------------------
>>>>> ------
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO]
>>>>> ------------------------------------------------------------------
>>>>> ------
>>>>> [INFO] Failed to resolve artifact.
>>>>> Missing:
>>>>> ----------
>>>>> 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-
>>>>> SNAPSHOT
>>>>> Try downloading the file manually from the project website.
>>>>> Then, install it using the command:
>>>>> mvn install:install-file -
>>>>> DgroupId=org.apache.geronimo.genesis.plugins -
>>>>> DartifactId=plugin-support \
>>>>> -Dversion=1.1-20061013.014841-21 -Dpackaging=jar -
>>>>> Dfile=/path/to/file
>>>>> Path to dependency:
>>>>> 1) org.apache.geronimo.genesis.plugins:tools-maven-
>>>>> plugin:maven-plugin:1.1-20061013.014841-21 2)
>>>>> org.apache.geronimo.genesis.plugins:plugin-support:jar:
>>>>> 1.1-20061013.014841-21 ----------
>>>>> 1 required artifact is missing.
>>>>> for artifact:
>>>>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
>>>>> plugin:1.1-20061013.014841-21 from the specified remote
>>>>> repositories:
>>>>> apache.snapshots (http://people.apache.org/repo/m2-snapshot-
>>>>> repository),
>>>>> codehaus-snapshots (http://snapshots.repository.codehaus.org),
>>>>> central (http://repo1.maven.org/maven2),
>>>>> codehaus (http://repository.codehaus.org),
>>>>> apache-snapshots (http://people.apache.org/repo/m2-snapshot-
>>>>> repository)
>>>>> jdillon@apache.org wrote:
>>>>>> Author: jdillon
>>>>>> Date: Thu Oct 12 20:54:00 2006
>>>>>> New Revision: 463555
>>>>>>
>>>>>> URL: http://svn.apache.org/viewvc?view=rev&rev=463555
>>>>>> Log:
>>>>>> Add tools profile to enable tools-m-p and m-m-p to all projects
>>>>>>
>>>>>> Modified:
>>>>>> geronimo/genesis/trunk/config/project-config/pom.xml
>>>>>>
>>>>>> Modified: geronimo/genesis/trunk/config/project-config/pom.xml
>>>>>> URL: http://svn.apache.org/viewvc/geronimo/genesis/trunk/
>>>>>> config/project-config/pom.xml?
>>>>>> view=diff&rev=463555&r1=463554&r2=463555
>>>>>> =================================================================
>>>>>> =============
>>>>>> --- geronimo/genesis/trunk/config/project-config/pom.xml
>>>>>> (original)
>>>>>> +++ geronimo/genesis/trunk/config/project-config/pom.xml Thu
>>>>>> Oct 12 20:54:00 2006
>>>>>> @@ -508,6 +508,24 @@
>>>>>> <activeByDefault>true</activeByDefault>
>>>>>> </activation>
>>>>>> </profile>
>>>>>> + + <profile>
>>>>>> + <id>tools</id>
>>>>>> +
>>>>>> + <build>
>>>>>> + <plugins>
>>>>>> + <plugin>
>>>>>> +
>>>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>>>> + <artifactId>tools-maven-plugin</
>>>>>> artifactId>
>>>>>> + </plugin>
>>>>>> +
>>>>>> + <plugin>
>>>>>> +
>>>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>>>> + <artifactId>maven-maven-plugin</
>>>>>> artifactId>
>>>>>> + </plugin>
>>>>>> + </plugins>
>>>>>> + </build>
>>>>>> + </profile>
>>>>>> </profiles>
>>>>>> <reporting>
>>>>>>
>>>>>>
>>>>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Re: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Jason Dillon <ja...@planet57.com>.
It is the default, this element is not set on any repos. Is the
default value true? Setting to false should keep it from using
timestamp versions?
What are the implications of this change?
--jason
On Oct 16, 2006, at 11:46 AM, Jörg Schaible wrote:
> Hi Jason,
>
> Jason Dillon wrote:
>
>> I think I have tracked this down... looks like ${pom.version} is
>> getting resolved to a timestamp version instead of the value it its
>> parents <version> element.
>>
>> Is this expected?
>>
>> If my parent has 1.1-SNAPSHOT, and an intermediate module defines a
>> dependency using ${pom.version}, should this resolve to 1.1-SNAPSHOT
>> or to 1.1-<timestamp>-<build> for the current module?
>
> What's you setting for the repo? See "uniqueVersion":
> http://maven.apache.org/ref/current/maven-model/
> maven.html#class_snapshotRepository
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Jörg Schaible <jo...@gmx.de>.
Hi Jason,
Jason Dillon wrote:
> I think I have tracked this down... looks like ${pom.version} is
> getting resolved to a timestamp version instead of the value it its
> parents <version> element.
>
> Is this expected?
>
> If my parent has 1.1-SNAPSHOT, and an intermediate module defines a
> dependency using ${pom.version}, should this resolve to 1.1-SNAPSHOT
> or to 1.1-<timestamp>-<build> for the current module?
What's you setting for the repo? See "uniqueVersion":
http://maven.apache.org/ref/current/maven-model/maven.html#class_snapshotRepository
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Fwd: Maven's snapshot mechanism is horked (Re: Build error - Is it
from svn commit: r463555 -
/geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Kenney Westerhof <ke...@apache.org>.
The problem below seems to indicate that the local repository contains an old metadata file.
Running mvn with -U -cpu should fix that (or wait 24 hours and try again :)).
Another solution is to delete the metadata file from the local repository.
Btw, how come the original snapshot versions are removed from the remote repository?
The local metadata file probably contains a reference to the old snapshot version,
but doesn't seem to have it locally, which needs investigation..
As for the other snapshot errors: Maven 1 legacy repositories don't contain metadata files.
Updating snapshots from them doesn't seem to work. That's another thing that
should be investigated.
I personally never have problems with snapshot versions, so maybe the use of maven 1 repositories
and the removal of snapshots from the remote repository isn't handled correctly by Maven.
-- Kenney
Jason Dillon wrote:
> Folks... maven's handling of *SNAPSHOT artifacts is killing us. Any
> idea what is going on... and how we can fix this. Its an ongoing
> problem, seems like new timestamp mismatch problems are popping up quite
> often now. I've already removed our direct use of m1 repos to get
> around some problems resolving artifacts... but something is still very
> broken with maven's SNAPSHOT mechanism.
>
> Any ideas?
>
> --jason
>
>
> Begin forwarded message:
>
>> From: Jason Dillon <ja...@planet57.com>
>> Date: October 13, 2006 2:00:50 PM PDT
>> To: dev@geronimo.apache.org
>> Cc: Jason van Zyl <ja...@maven.org>
>> Subject: Maven's snapshot mechanism is horked (Re: Build error - Is it
>> from svn commit: r463555 -
>> /geronimo/genesis/trunk/config/project-config/pom.xml?)
>>
>> Yes, build genesis locally for now to get around... I'm gonna need to
>> get the maven peeps to explain wtf is going on... and hopefully fix
>> maven to not freak out like this.
>>
>> The metadata for plugin-support is correct... showing the latest
>> 1.1-SNAPSHOT is -23:
>>
>> <metadata>
>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>> <artifactId>plugin-support</artifactId>
>> <version>1.1-SNAPSHOT</version>
>> <versioning>
>> <snapshot>
>> <timestamp>20061013.014841</timestamp>
>> <buildNumber>23</buildNumber>
>> </snapshot>
>> <lastUpdated>20061013014947</lastUpdated>
>> </versioning>
>> </metadata>
>>
>> And -23 is there:
>>
>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-support-1.1-20061013.014841-23.jar
>>
>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-support-1.1-20061013.014841-23.pom
>>
>>
>> So, Maven *should* be resolving any 1.1-SNAPSHOT of plugin-config to
>> these files... but...
>>
>> --jason
>>
>>
>> On Oct 13, 2006, at 1:50 PM, Joe Bohn wrote:
>>
>>> Prasad and I hit the same problem earlier today. There must be
>>> something strange going on with the version # where "21" is being
>>> assumed instead of the "23" that is actually in the repo. I'm hoping
>>> that Jason will know what exactly is going on and how to fix it and I
>>> suspect it may be related to one of his changes.
>>>
>>> To get around the problem for now you can build genesis locally.
>>> That worked for me.
>>>
>>> Joe
>>>
>>>
>>> Donald Woods wrote:
>>>> Having build problems today and wondering if the below genesis
>>>> change yesterday is causing it?
>>>> Started with a new trunk checkout directory on a SLES10 x86 machine.
>>>> Removed the existing .m2 repo.
>>>> bootstrap clean ran fine.
>>>> bootstrap specs is failing (also tried mvn -U install from
>>>> target/external/specs) because the file
>>>> version=1.1-20061013.014841-21 is not in the snapshot repo, but
>>>> version=1.1-20061013.014841-23 is.
>>>> ------------------------------------------------------------------------
>>>>
>>>> [ERROR] BUILD ERROR
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] Failed to resolve artifact.
>>>> Missing:
>>>> ----------
>>>> 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-SNAPSHOT
>>>> Try downloading the file manually from the project website.
>>>> Then, install it using the command:
>>>> mvn install:install-file
>>>> -DgroupId=org.apache.geronimo.genesis.plugins
>>>> -DartifactId=plugin-support \
>>>> -Dversion=1.1-20061013.014841-21 -Dpackaging=jar
>>>> -Dfile=/path/to/file
>>>> Path to dependency:
>>>> 1)
>>>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:1.1-20061013.014841-21
>>>> 2)
>>>> org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-20061013.014841-21
>>>> ----------
>>>> 1 required artifact is missing.
>>>> for artifact:
>>>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:1.1-20061013.014841-21
>>>> from the specified remote repositories:
>>>> apache.snapshots
>>>> (http://people.apache.org/repo/m2-snapshot-repository),
>>>> codehaus-snapshots (http://snapshots.repository.codehaus.org),
>>>> central (http://repo1.maven.org/maven2),
>>>> codehaus (http://repository.codehaus.org),
>>>> apache-snapshots
>>>> (http://people.apache.org/repo/m2-snapshot-repository)
>>>> jdillon@apache.org wrote:
>>>>> Author: jdillon
>>>>> Date: Thu Oct 12 20:54:00 2006
>>>>> New Revision: 463555
>>>>>
>>>>> URL: http://svn.apache.org/viewvc?view=rev&rev=463555
>>>>> Log:
>>>>> Add tools profile to enable tools-m-p and m-m-p to all projects
>>>>>
>>>>> Modified:
>>>>> geronimo/genesis/trunk/config/project-config/pom.xml
>>>>>
>>>>> Modified: geronimo/genesis/trunk/config/project-config/pom.xml
>>>>> URL:
>>>>> http://svn.apache.org/viewvc/geronimo/genesis/trunk/config/project-config/pom.xml?view=diff&rev=463555&r1=463554&r2=463555
>>>>>
>>>>> ==============================================================================
>>>>>
>>>>> --- geronimo/genesis/trunk/config/project-config/pom.xml (original)
>>>>> +++ geronimo/genesis/trunk/config/project-config/pom.xml Thu Oct 12
>>>>> 20:54:00 2006
>>>>> @@ -508,6 +508,24 @@
>>>>> <activeByDefault>true</activeByDefault>
>>>>> </activation>
>>>>> </profile>
>>>>> + + <profile>
>>>>> + <id>tools</id>
>>>>> +
>>>>> + <build>
>>>>> + <plugins>
>>>>> + <plugin>
>>>>> +
>>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>>> + <artifactId>tools-maven-plugin</artifactId>
>>>>> + </plugin>
>>>>> +
>>>>> + <plugin>
>>>>> +
>>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>>> + <artifactId>maven-maven-plugin</artifactId>
>>>>> + </plugin>
>>>>> + </plugins>
>>>>> + </build>
>>>>> + </profile>
>>>>> </profiles>
>>>>> <reporting>
>>>>>
>>>>>
>>>>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Fwd: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Jason Dillon <ja...@planet57.com>.
Folks... maven's handling of *SNAPSHOT artifacts is killing us. Any
idea what is going on... and how we can fix this. Its an ongoing
problem, seems like new timestamp mismatch problems are popping up
quite often now. I've already removed our direct use of m1 repos to
get around some problems resolving artifacts... but something is
still very broken with maven's SNAPSHOT mechanism.
Any ideas?
--jason
Begin forwarded message:
> From: Jason Dillon <ja...@planet57.com>
> Date: October 13, 2006 2:00:50 PM PDT
> To: dev@geronimo.apache.org
> Cc: Jason van Zyl <ja...@maven.org>
> Subject: Maven's snapshot mechanism is horked (Re: Build error - Is
> it from svn commit: r463555 - /geronimo/genesis/trunk/config/
> project-config/pom.xml?)
>
> Yes, build genesis locally for now to get around... I'm gonna need
> to get the maven peeps to explain wtf is going on... and hopefully
> fix maven to not freak out like this.
>
> The metadata for plugin-support is correct... showing the latest
> 1.1-SNAPSHOT is -23:
>
> <metadata>
> <groupId>org.apache.geronimo.genesis.plugins</groupId>
> <artifactId>plugin-support</artifactId>
> <version>1.1-SNAPSHOT</version>
> <versioning>
> <snapshot>
> <timestamp>20061013.014841</timestamp>
> <buildNumber>23</buildNumber>
> </snapshot>
> <lastUpdated>20061013014947</lastUpdated>
> </versioning>
> </metadata>
>
> And -23 is there:
>
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/
> geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
> support-1.1-20061013.014841-23.jar
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/
> geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
> support-1.1-20061013.014841-23.pom
>
> So, Maven *should* be resolving any 1.1-SNAPSHOT of plugin-config
> to these files... but...
>
> --jason
>
>
> On Oct 13, 2006, at 1:50 PM, Joe Bohn wrote:
>
>> Prasad and I hit the same problem earlier today. There must be
>> something strange going on with the version # where "21" is being
>> assumed instead of the "23" that is actually in the repo. I'm
>> hoping that Jason will know what exactly is going on and how to
>> fix it and I suspect it may be related to one of his changes.
>>
>> To get around the problem for now you can build genesis locally.
>> That worked for me.
>>
>> Joe
>>
>>
>> Donald Woods wrote:
>>> Having build problems today and wondering if the below genesis
>>> change yesterday is causing it?
>>> Started with a new trunk checkout directory on a SLES10 x86 machine.
>>> Removed the existing .m2 repo.
>>> bootstrap clean ran fine.
>>> bootstrap specs is failing (also tried mvn -U install from target/
>>> external/specs) because the file version=1.1-20061013.014841-21
>>> is not in the snapshot repo, but version=1.1-20061013.014841-23 is.
>>> --------------------------------------------------------------------
>>> ----
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> --------------------------------------------------------------------
>>> ----
>>> [INFO] Failed to resolve artifact.
>>> Missing:
>>> ----------
>>> 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-
>>> SNAPSHOT
>>> Try downloading the file manually from the project website.
>>> Then, install it using the command:
>>> mvn install:install-file -
>>> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin-
>>> support \
>>> -Dversion=1.1-20061013.014841-21 -Dpackaging=jar -
>>> Dfile=/path/to/file
>>> Path to dependency:
>>> 1) org.apache.geronimo.genesis.plugins:tools-maven-
>>> plugin:maven-plugin:1.1-20061013.014841-21 2)
>>> org.apache.geronimo.genesis.plugins:plugin-support:jar:
>>> 1.1-20061013.014841-21 ----------
>>> 1 required artifact is missing.
>>> for artifact:
>>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
>>> plugin:1.1-20061013.014841-21 from the specified remote
>>> repositories:
>>> apache.snapshots (http://people.apache.org/repo/m2-snapshot-
>>> repository),
>>> codehaus-snapshots (http://snapshots.repository.codehaus.org),
>>> central (http://repo1.maven.org/maven2),
>>> codehaus (http://repository.codehaus.org),
>>> apache-snapshots (http://people.apache.org/repo/m2-snapshot-
>>> repository)
>>> jdillon@apache.org wrote:
>>>> Author: jdillon
>>>> Date: Thu Oct 12 20:54:00 2006
>>>> New Revision: 463555
>>>>
>>>> URL: http://svn.apache.org/viewvc?view=rev&rev=463555
>>>> Log:
>>>> Add tools profile to enable tools-m-p and m-m-p to all projects
>>>>
>>>> Modified:
>>>> geronimo/genesis/trunk/config/project-config/pom.xml
>>>>
>>>> Modified: geronimo/genesis/trunk/config/project-config/pom.xml
>>>> URL: http://svn.apache.org/viewvc/geronimo/genesis/trunk/config/
>>>> project-config/pom.xml?view=diff&rev=463555&r1=463554&r2=463555
>>>> ===================================================================
>>>> ===========
>>>> --- geronimo/genesis/trunk/config/project-config/pom.xml (original)
>>>> +++ geronimo/genesis/trunk/config/project-config/pom.xml Thu Oct
>>>> 12 20:54:00 2006
>>>> @@ -508,6 +508,24 @@
>>>> <activeByDefault>true</activeByDefault>
>>>> </activation>
>>>> </profile>
>>>> + + <profile>
>>>> + <id>tools</id>
>>>> +
>>>> + <build>
>>>> + <plugins>
>>>> + <plugin>
>>>> +
>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>> + <artifactId>tools-maven-plugin</
>>>> artifactId>
>>>> + </plugin>
>>>> +
>>>> + <plugin>
>>>> +
>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>> + <artifactId>maven-maven-plugin</
>>>> artifactId>
>>>> + </plugin>
>>>> + </plugins>
>>>> + </build>
>>>> + </profile>
>>>> </profiles>
>>>> <reporting>
>>>>
>>>>
>>>>
>
Fwd: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Jason Dillon <ja...@planet57.com>.
Folks... maven's handling of *SNAPSHOT artifacts is killing us. Any
idea what is going on... and how we can fix this. Its an ongoing
problem, seems like new timestamp mismatch problems are popping up
quite often now. I've already removed our direct use of m1 repos to
get around some problems resolving artifacts... but something is
still very broken with maven's SNAPSHOT mechanism.
Any ideas?
--jason
Begin forwarded message:
> From: Jason Dillon <ja...@planet57.com>
> Date: October 13, 2006 2:00:50 PM PDT
> To: dev@geronimo.apache.org
> Cc: Jason van Zyl <ja...@maven.org>
> Subject: Maven's snapshot mechanism is horked (Re: Build error - Is
> it from svn commit: r463555 - /geronimo/genesis/trunk/config/
> project-config/pom.xml?)
>
> Yes, build genesis locally for now to get around... I'm gonna need
> to get the maven peeps to explain wtf is going on... and hopefully
> fix maven to not freak out like this.
>
> The metadata for plugin-support is correct... showing the latest
> 1.1-SNAPSHOT is -23:
>
> <metadata>
> <groupId>org.apache.geronimo.genesis.plugins</groupId>
> <artifactId>plugin-support</artifactId>
> <version>1.1-SNAPSHOT</version>
> <versioning>
> <snapshot>
> <timestamp>20061013.014841</timestamp>
> <buildNumber>23</buildNumber>
> </snapshot>
> <lastUpdated>20061013014947</lastUpdated>
> </versioning>
> </metadata>
>
> And -23 is there:
>
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/
> geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
> support-1.1-20061013.014841-23.jar
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/
> geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
> support-1.1-20061013.014841-23.pom
>
> So, Maven *should* be resolving any 1.1-SNAPSHOT of plugin-config
> to these files... but...
>
> --jason
>
>
> On Oct 13, 2006, at 1:50 PM, Joe Bohn wrote:
>
>> Prasad and I hit the same problem earlier today. There must be
>> something strange going on with the version # where "21" is being
>> assumed instead of the "23" that is actually in the repo. I'm
>> hoping that Jason will know what exactly is going on and how to
>> fix it and I suspect it may be related to one of his changes.
>>
>> To get around the problem for now you can build genesis locally.
>> That worked for me.
>>
>> Joe
>>
>>
>> Donald Woods wrote:
>>> Having build problems today and wondering if the below genesis
>>> change yesterday is causing it?
>>> Started with a new trunk checkout directory on a SLES10 x86 machine.
>>> Removed the existing .m2 repo.
>>> bootstrap clean ran fine.
>>> bootstrap specs is failing (also tried mvn -U install from target/
>>> external/specs) because the file version=1.1-20061013.014841-21
>>> is not in the snapshot repo, but version=1.1-20061013.014841-23 is.
>>> --------------------------------------------------------------------
>>> ----
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> --------------------------------------------------------------------
>>> ----
>>> [INFO] Failed to resolve artifact.
>>> Missing:
>>> ----------
>>> 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-
>>> SNAPSHOT
>>> Try downloading the file manually from the project website.
>>> Then, install it using the command:
>>> mvn install:install-file -
>>> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin-
>>> support \
>>> -Dversion=1.1-20061013.014841-21 -Dpackaging=jar -
>>> Dfile=/path/to/file
>>> Path to dependency:
>>> 1) org.apache.geronimo.genesis.plugins:tools-maven-
>>> plugin:maven-plugin:1.1-20061013.014841-21 2)
>>> org.apache.geronimo.genesis.plugins:plugin-support:jar:
>>> 1.1-20061013.014841-21 ----------
>>> 1 required artifact is missing.
>>> for artifact:
>>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
>>> plugin:1.1-20061013.014841-21 from the specified remote
>>> repositories:
>>> apache.snapshots (http://people.apache.org/repo/m2-snapshot-
>>> repository),
>>> codehaus-snapshots (http://snapshots.repository.codehaus.org),
>>> central (http://repo1.maven.org/maven2),
>>> codehaus (http://repository.codehaus.org),
>>> apache-snapshots (http://people.apache.org/repo/m2-snapshot-
>>> repository)
>>> jdillon@apache.org wrote:
>>>> Author: jdillon
>>>> Date: Thu Oct 12 20:54:00 2006
>>>> New Revision: 463555
>>>>
>>>> URL: http://svn.apache.org/viewvc?view=rev&rev=463555
>>>> Log:
>>>> Add tools profile to enable tools-m-p and m-m-p to all projects
>>>>
>>>> Modified:
>>>> geronimo/genesis/trunk/config/project-config/pom.xml
>>>>
>>>> Modified: geronimo/genesis/trunk/config/project-config/pom.xml
>>>> URL: http://svn.apache.org/viewvc/geronimo/genesis/trunk/config/
>>>> project-config/pom.xml?view=diff&rev=463555&r1=463554&r2=463555
>>>> ===================================================================
>>>> ===========
>>>> --- geronimo/genesis/trunk/config/project-config/pom.xml (original)
>>>> +++ geronimo/genesis/trunk/config/project-config/pom.xml Thu Oct
>>>> 12 20:54:00 2006
>>>> @@ -508,6 +508,24 @@
>>>> <activeByDefault>true</activeByDefault>
>>>> </activation>
>>>> </profile>
>>>> + + <profile>
>>>> + <id>tools</id>
>>>> +
>>>> + <build>
>>>> + <plugins>
>>>> + <plugin>
>>>> +
>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>> + <artifactId>tools-maven-plugin</
>>>> artifactId>
>>>> + </plugin>
>>>> +
>>>> + <plugin>
>>>> +
>>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>>> + <artifactId>maven-maven-plugin</
>>>> artifactId>
>>>> + </plugin>
>>>> + </plugins>
>>>> + </build>
>>>> + </profile>
>>>> </profiles>
>>>> <reporting>
>>>>
>>>>
>>>>
>
Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Posted by Jason Dillon <ja...@planet57.com>.
Yes, build genesis locally for now to get around... I'm gonna need to
get the maven peeps to explain wtf is going on... and hopefully fix
maven to not freak out like this.
The metadata for plugin-support is correct... showing the latest 1.1-
SNAPSHOT is -23:
<metadata>
<groupId>org.apache.geronimo.genesis.plugins</groupId>
<artifactId>plugin-support</artifactId>
<version>1.1-SNAPSHOT</version>
<versioning>
<snapshot>
<timestamp>20061013.014841</timestamp>
<buildNumber>23</buildNumber>
</snapshot>
<lastUpdated>20061013014947</lastUpdated>
</versioning>
</metadata>
And -23 is there:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/
geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
support-1.1-20061013.014841-23.jar
http://people.apache.org/repo/m2-snapshot-repository/org/apache/
geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
support-1.1-20061013.014841-23.pom
So, Maven *should* be resolving any 1.1-SNAPSHOT of plugin-config to
these files... but...
--jason
On Oct 13, 2006, at 1:50 PM, Joe Bohn wrote:
> Prasad and I hit the same problem earlier today. There must be
> something strange going on with the version # where "21" is being
> assumed instead of the "23" that is actually in the repo. I'm
> hoping that Jason will know what exactly is going on and how to fix
> it and I suspect it may be related to one of his changes.
>
> To get around the problem for now you can build genesis locally.
> That worked for me.
>
> Joe
>
>
> Donald Woods wrote:
>> Having build problems today and wondering if the below genesis
>> change yesterday is causing it?
>> Started with a new trunk checkout directory on a SLES10 x86 machine.
>> Removed the existing .m2 repo.
>> bootstrap clean ran fine.
>> bootstrap specs is failing (also tried mvn -U install from target/
>> external/specs) because the file version=1.1-20061013.014841-21 is
>> not in the snapshot repo, but version=1.1-20061013.014841-23 is.
>> ---------------------------------------------------------------------
>> ---
>> [ERROR] BUILD ERROR
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] Failed to resolve artifact.
>> Missing:
>> ----------
>> 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-
>> SNAPSHOT
>> Try downloading the file manually from the project website.
>> Then, install it using the command:
>> mvn install:install-file -
>> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin-
>> support \
>> -Dversion=1.1-20061013.014841-21 -Dpackaging=jar -Dfile=/
>> path/to/file
>> Path to dependency:
>> 1) org.apache.geronimo.genesis.plugins:tools-maven-
>> plugin:maven-plugin:1.1-20061013.014841-21 2)
>> org.apache.geronimo.genesis.plugins:plugin-support:jar:
>> 1.1-20061013.014841-21 ----------
>> 1 required artifact is missing.
>> for artifact:
>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
>> plugin:1.1-20061013.014841-21 from the specified remote repositories:
>> apache.snapshots (http://people.apache.org/repo/m2-snapshot-
>> repository),
>> codehaus-snapshots (http://snapshots.repository.codehaus.org),
>> central (http://repo1.maven.org/maven2),
>> codehaus (http://repository.codehaus.org),
>> apache-snapshots (http://people.apache.org/repo/m2-snapshot-
>> repository)
>> jdillon@apache.org wrote:
>>> Author: jdillon
>>> Date: Thu Oct 12 20:54:00 2006
>>> New Revision: 463555
>>>
>>> URL: http://svn.apache.org/viewvc?view=rev&rev=463555
>>> Log:
>>> Add tools profile to enable tools-m-p and m-m-p to all projects
>>>
>>> Modified:
>>> geronimo/genesis/trunk/config/project-config/pom.xml
>>>
>>> Modified: geronimo/genesis/trunk/config/project-config/pom.xml
>>> URL: http://svn.apache.org/viewvc/geronimo/genesis/trunk/config/
>>> project-config/pom.xml?view=diff&rev=463555&r1=463554&r2=463555
>>> ====================================================================
>>> ==========
>>> --- geronimo/genesis/trunk/config/project-config/pom.xml (original)
>>> +++ geronimo/genesis/trunk/config/project-config/pom.xml Thu Oct
>>> 12 20:54:00 2006
>>> @@ -508,6 +508,24 @@
>>> <activeByDefault>true</activeByDefault>
>>> </activation>
>>> </profile>
>>> + + <profile>
>>> + <id>tools</id>
>>> +
>>> + <build>
>>> + <plugins>
>>> + <plugin>
>>> +
>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>> + <artifactId>tools-maven-plugin</artifactId>
>>> + </plugin>
>>> +
>>> + <plugin>
>>> +
>>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>>> + <artifactId>maven-maven-plugin</artifactId>
>>> + </plugin>
>>> + </plugins>
>>> + </build>
>>> + </profile>
>>> </profiles>
>>> <reporting>
>>>
>>>
>>>
Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?
Posted by Joe Bohn <jo...@earthlink.net>.
Prasad and I hit the same problem earlier today. There must be
something strange going on with the version # where "21" is being
assumed instead of the "23" that is actually in the repo. I'm hoping
that Jason will know what exactly is going on and how to fix it and I
suspect it may be related to one of his changes.
To get around the problem for now you can build genesis locally. That
worked for me.
Joe
Donald Woods wrote:
> Having build problems today and wondering if the below genesis change
> yesterday is causing it?
>
> Started with a new trunk checkout directory on a SLES10 x86 machine.
> Removed the existing .m2 repo.
> bootstrap clean ran fine.
> bootstrap specs is failing (also tried mvn -U install from
> target/external/specs) because the file version=1.1-20061013.014841-21
> is not in the snapshot repo, but version=1.1-20061013.014841-23 is.
>
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file
> -DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin-support \
> -Dversion=1.1-20061013.014841-21 -Dpackaging=jar
> -Dfile=/path/to/file
>
> Path to dependency:
> 1)
> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:1.1-20061013.014841-21
>
> 2)
> org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-20061013.014841-21
>
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
>
> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:1.1-20061013.014841-21
>
>
> from the specified remote repositories:
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
> codehaus-snapshots (http://snapshots.repository.codehaus.org),
> central (http://repo1.maven.org/maven2),
> codehaus (http://repository.codehaus.org),
> apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)
>
>
>
>
> jdillon@apache.org wrote:
>
>> Author: jdillon
>> Date: Thu Oct 12 20:54:00 2006
>> New Revision: 463555
>>
>> URL: http://svn.apache.org/viewvc?view=rev&rev=463555
>> Log:
>> Add tools profile to enable tools-m-p and m-m-p to all projects
>>
>> Modified:
>> geronimo/genesis/trunk/config/project-config/pom.xml
>>
>> Modified: geronimo/genesis/trunk/config/project-config/pom.xml
>> URL:
>> http://svn.apache.org/viewvc/geronimo/genesis/trunk/config/project-config/pom.xml?view=diff&rev=463555&r1=463554&r2=463555
>>
>> ==============================================================================
>>
>> --- geronimo/genesis/trunk/config/project-config/pom.xml (original)
>> +++ geronimo/genesis/trunk/config/project-config/pom.xml Thu Oct 12
>> 20:54:00 2006
>> @@ -508,6 +508,24 @@
>> <activeByDefault>true</activeByDefault>
>> </activation>
>> </profile>
>> + + <profile>
>> + <id>tools</id>
>> +
>> + <build>
>> + <plugins>
>> + <plugin>
>> +
>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>> + <artifactId>tools-maven-plugin</artifactId>
>> + </plugin>
>> +
>> + <plugin>
>> +
>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>> + <artifactId>maven-maven-plugin</artifactId>
>> + </plugin>
>> + </plugins>
>> + </build>
>> + </profile>
>> </profiles>
>> <reporting>
>>
>>
>>
Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?
Posted by Jason Dillon <ja...@planet57.com>.
#$^%! Maven's bunk-ass-snapshot mechanism is broken. These should
be resolved to the latest 1.2-SNAPSHOT, which are all up there, I
published a fresh set yesterday.
Dunno what to do in the short-term to fix this... yet.
--jason
On Oct 13, 2006, at 1:43 PM, Donald Woods wrote:
> Having build problems today and wondering if the below genesis
> change yesterday is causing it?
>
> Started with a new trunk checkout directory on a SLES10 x86 machine.
> Removed the existing .m2 repo.
> bootstrap clean ran fine.
> bootstrap specs is failing (also tried mvn -U install from target/
> external/specs) because the file version=1.1-20061013.014841-21 is
> not in the snapshot repo, but version=1.1-20061013.014841-23 is.
>
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -
> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin-
> support \
> -Dversion=1.1-20061013.014841-21 -Dpackaging=jar -Dfile=/
> path/to/file
>
> Path to dependency:
> 1) org.apache.geronimo.genesis.plugins:tools-maven-
> plugin:maven-plugin:1.1-20061013.014841-21
> 2) org.apache.geronimo.genesis.plugins:plugin-support:jar:
> 1.1-20061013.014841-21
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:
> 1.1-20061013.014841-21
>
> from the specified remote repositories:
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-
> repository),
> codehaus-snapshots (http://snapshots.repository.codehaus.org),
> central (http://repo1.maven.org/maven2),
> codehaus (http://repository.codehaus.org),
> apache-snapshots (http://people.apache.org/repo/m2-snapshot-
> repository)
>
>
>
>
> jdillon@apache.org wrote:
>> Author: jdillon
>> Date: Thu Oct 12 20:54:00 2006
>> New Revision: 463555
>> URL: http://svn.apache.org/viewvc?view=rev&rev=463555
>> Log:
>> Add tools profile to enable tools-m-p and m-m-p to all projects
>> Modified:
>> geronimo/genesis/trunk/config/project-config/pom.xml
>> Modified: geronimo/genesis/trunk/config/project-config/pom.xml
>> URL: http://svn.apache.org/viewvc/geronimo/genesis/trunk/config/
>> project-config/pom.xml?view=diff&rev=463555&r1=463554&r2=463555
>> =====================================================================
>> =========
>> --- geronimo/genesis/trunk/config/project-config/pom.xml (original)
>> +++ geronimo/genesis/trunk/config/project-config/pom.xml Thu Oct
>> 12 20:54:00 2006
>> @@ -508,6 +508,24 @@
>> <activeByDefault>true</activeByDefault>
>> </activation>
>> </profile>
>> + + <profile>
>> + <id>tools</id>
>> +
>> + <build>
>> + <plugins>
>> + <plugin>
>> +
>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>> + <artifactId>tools-maven-plugin</artifactId>
>> + </plugin>
>> +
>> + <plugin>
>> +
>> <groupId>org.apache.geronimo.genesis.plugins</groupId>
>> + <artifactId>maven-maven-plugin</artifactId>
>> + </plugin>
>> + </plugins>
>> + </build>
>> + </profile>
>> </profiles>
>> <reporting>