I'm currently working with the book Better Builds with Maven and doing
some custom maven plugin development. I have a plugin I've created with the
following POM info.
groupIdcom.exist.mvnbook.plugins/groupId
artifactIdmaven-buildinfo-plugin/artifactId
packagingmaven-plugin/packaging
You know
This should be posted to the users@ list - I can answer this there
afterwards.
Thanks,
Brett
On 24/09/2009, at 4:04 AM, Tristan JC Rouse wrote:
I'm currently working with the book Better Builds with Maven and
doing
some custom maven plugin development. I have a plugin I've created
with
Brett Porter wrote:
Any objections to disabling write to the Codehaus MAVEN space and
pointing people to cwiki as described below?
Nope.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
let's go
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Thu, Sep 24, 2009 at 3:07 AM, Brett Porter br...@apache.org wrote:
Changing the subject to get more visibility... Codehaus is upgrading to
Confluence 3.0
Benjamin Bentmann wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-038/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
Benjamin Bentmann wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-039/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
+1
2009/9/24 Arnaud HERITIER aherit...@gmail.com
let's go
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Thu, Sep 24, 2009 at 3:07 AM, Brett Porter br...@apache.org wrote:
Changing the subject to get
+1
2009/9/24 Brett Porter br...@apache.org:
Changing the subject to get more visibility... Codehaus is upgrading to
Confluence 3.0 this weekend which will limit migration options if we make
any further edits over there.
Any objections to disabling write to the Codehaus MAVEN space and
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, Arnaud Héritier, Benjamin Bentmann
+1 (non-binding): Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, Arnaud Héritier, Benjamin Bentmann
+1 (non-binding): Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
The server hosting the zone for repository.apache.org is having some
maintenance issues at the moment so the repository is offline. You can
follow the apache infra twitter for updates on the status:
http://twitter.com/infrabot
-
It can't hurt.
On Wed, Sep 23, 2009 at 6:03 PM, Brett Porter br...@apache.org wrote:
On 24/09/2009, at 7:22 AM, Hervé BOUTEMY wrote:
I also think we should move all the MARTIFACT JIRAs back into MNG.
I don't know how to do the move to MNG Artufact and Repositories
component,
then disable
Issue Subscription
Filter: Design Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Moving over to dev...
So here's a thought - why don't we create a new central repository?
- a new repository with strict acceptance rules regarding POMs,
signatures, ownership, etc.
- if there's a new metadata format needed (recently discussed), this
would use it
- validated artifacts could
On 2009-09-24, at 8:37 PM, Brett Porter wrote:
Moving over to dev...
So here's a thought - why don't we create a new central repository?
- a new repository with strict acceptance rules regarding POMs,
signatures, ownership, etc.
- if there's a new metadata format needed (recently
This has already been done once in history, between M1 and M2 and look
how we still have that mess to deal with all the time. Doing this
again serves no one well, making sure new data coming in is clean is
more productive for everyone. Who would _want_ to deploy their stuff
to the old repo? No
16 matches
Mail list logo
