This content has been marked as final.
Show 8 replies
-
1. Re: Putting MC artifacts to our maven repo
adrian.brock Mar 29, 2008 11:13 AM (in response to alesj)"alesj" wrote:
The thing is that I've done that, but than later on modified those files. :-(
Don't ask me why. :-)
But now I cannot run that again. Some mvn complain again.
Surprisingly enough. :-)
You can't modify the files AFTERwards, the build/artifacts wouldn't be reproducable.
If you want to start again, delete the tag from SVN. -
2. Re: Putting MC artifacts to our maven repo
alesj Mar 29, 2008 11:26 AM (in response to alesj)"adrian@jboss.org" wrote:
You can't modify the files AFTERwards, the build/artifacts wouldn't be reproducable.
If you want to start again, delete the tag from SVN.
What about if I push the one's that are in my local repo?
Since all the right versions are there. -
3. Re: Putting MC artifacts to our maven repo
adrian.brock Mar 29, 2008 11:50 AM (in response to alesj)"alesj" wrote:
"adrian@jboss.org" wrote:
You can't modify the files AFTERwards, the build/artifacts wouldn't be reproducable.
If you want to start again, delete the tag from SVN.
What about if I push the one's that are in my local repo?
Since all the right versions are there.
If you can reproduce them I don't have a problem. They're not GA releases
so its not like we'll have to support them for very long. :-) -
4. Re: Putting MC artifacts to our maven repo
alesj Mar 29, 2008 12:06 PM (in response to alesj)"adrian@jboss.org" wrote:
If you can reproduce them I don't have a problem. They're not GA releases
so its not like we'll have to support them for very long. :-)
What about those maven-metadata.xml* files?
Are they crucial for things to be in-synch? -
5. Re: Putting MC artifacts to our maven repo
adrian.brock Mar 29, 2008 12:13 PM (in response to alesj)"alesj" wrote:
"adrian@jboss.org" wrote:
If you can reproduce them I don't have a problem. They're not GA releases
so its not like we'll have to support them for very long. :-)
What about those maven-metadata.xml* files?
Are they crucial for things to be in-synch?
No they just list what is in the repository and which is the current version.
If you edit them and don't know how to regenerate the checksums then
just delete the check sum file(s).
Its the binaries/poms that are important. -
6. Re: Putting MC artifacts to our maven repo
dimitris Mar 31, 2008 6:33 AM (in response to alesj)Somewhat related, looking into https://svn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/jboss-common-core/maven-metadata.xml
a) I can see version 2.2.3.GA missing. Given this one was used by other components, I conclude the maven-metadata.xml is not necessary?
b) Anyone knows if ordering is important?
c) What's the meaning of v2.0.5.GA as it is recorded below?
After a quick search, I didn't much about the maven-metadata schema.<?xml version="1.0" encoding="UTF-8" ?> <metadata> <groupId>org.jboss</groupId> <artifactId>jboss-common-core</artifactId> <version>2.0.5.GA</version> <versioning> <release>2.2.4.GA</release> <versions> <version>2.0.5.GA</version> <version>2.2.2.GA</version> <version>2.2.1.GA</version> <version>2.2.4.GA</version> </versions> <lastUpdated>20080328111223</lastUpdated> </versioning> </metadata>
Another problem I noticed is the moment you are doing the 'mvn release:perform' you need to have checked all the versions of a component, in-order to get access to the maven-metadata.xml, so the new version is correctly added. That means a lot of garbage in your local filesystem, just to do a simple release. -
7. Re: Putting MC artifacts to our maven repo
adrian.brock Mar 31, 2008 7:34 AM (in response to alesj)Dimitris,
Why are you asking questions about maven/build system on the MC forum? :-) -
8. Re: Putting MC artifacts to our maven repo
dimitris Mar 31, 2008 8:41 AM (in response to alesj)I know, I piggybacked on the last answer, sorry :)
Moved here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140104#4140104