Sounds like the right thing to do.
On 24/08/2007, at 5:47 PM, Carlos Sanchez wrote:
there must be any problem with the staging settings, I checked that
the first deployed correctly to staging but seems that the other ones
didn't
The only solution would be to push this release completely, and then
review the problems, maybe making an alpha-6 inmediately
On 8/24/07, Tim Kettler <[EMAIL PROTECTED]> wrote:
Hi,
why is this version already available in central [1]? If this is
intentional the corresponding paren pom needs to be deployed too.
A user already ran into this [2]
-Tim
[1]
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-
archetype-plugin/1.0-alpha-5/
[2]
http://www.nabble.com/Having-Problem-in-creating-new-project-in-
Maven-tf4321938s177.html
Carlos Sanchez schrieb:
Issues fixed
ARCHETYPE-78 Dependencies listed as version ${project.version} in
maven-archetype prevent the use of archetypes
ARCHETYPE-60 Archetype Documentation Incorrect
ARCHETYPE-38 The archetype is using user.dir which prohibits
clean embedding
Change log
http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&pid=11095&fixfor=12413
The release is staged at
http://people.apache.org/~carlos/staging-repo/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
