+1
On 02/05/2010, at 6:55 AM, Hervé BOUTEMY wrote:
After releasing an alpha of Archetype components and some archetypes, it
becomes clear to me that the actual structure is not ideal.
I think that maven-archertype-bundles with all its modules (ie concrete
archetypes) should be a separate
On 01/05/2010, at 3:19 AM, Benjamin Bentmann wrote:
Hi,
considering the recent fixes to checksums for stuff in central, I was
wondering what's the overall state of (existing) checksums on central these
days?
Probably still not great.
We aren't using these for an
+1
-Lukas
John Casey wrote:
Hi,
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=15050
There are still a couple of issues left in JIRA:
+1
-Lukas
Benjamin Bentmann wrote:
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139version=16416
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11139status=1
Staging repo:
+1
-Lukas
Hervé BOUTEMY wrote:
Hi,
We solved 24 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140styleName=Htmlversion=14419
There are still a couple of issues left in JIRA:
Hi,
somehow related to my previous question about the checksums, what are
our chances to automatically detect and fix bad maven-metadata.xml's
deployed to Central like seen in [0]?
Benjamin
[0] http://jira.codehaus.org/browse/MEV-658
Benjamin Bentmann wrote:
Hi,
considering the recent fixes to checksums for stuff in central, I was
wondering what's the overall state of (existing) checksums on central
these days?
Assuming checksums are correct where present, this should put us in a
good position to introduce a new
On May 3, 2010, at 12:10 PM, Benjamin Bentmann wrote:
Hi,
somehow related to my previous question about the checksums, what are our
chances to automatically detect and fix bad maven-metadata.xml's deployed to
Central like seen in [0]?
While the content of the POMs is not something we
On 03/05/2010, Brett Porter br...@apache.org wrote:
On 01/05/2010, at 3:19 AM, Benjamin Bentmann wrote:
Hi,
considering the recent fixes to checksums for stuff in central, I was
wondering what's the overall state of (existing) checksums on central these
days?
Probably still not
Seems to me that the first step is to prevent any new files being
added to central unless they have valid hashes and signatures to stop
the problem getting worse - or has that already been done?
This is being done. The signatures are checked, but the hashes
currently aren't. That's a trivial
I have a custom plugin which
implements
org.codehaus.plexus.personality.plexus.lifecycle.phase.Contextualizable.
It has been working fine with the older alphas (5 and 6) but with alpha-7
and beta-1 my plugin is no longer being contextualized. The
method contextualize is not being called. Any
Jason van Zyl wrote:
On May 3, 2010, at 12:10 PM, Benjamin Bentmann wrote:
Hi,
somehow related to my previous question about the checksums, what are our
chances to automatically detect and fix bad maven-metadata.xml's deployed to
Central like seen in [0]?
While the content of the
Possibly if we introduce a pom that has the exact internal model maven
generates when it can't find one. This could cause some issues for
people who have their own versions of those poms.
On Mon, May 3, 2010 at 2:05 PM, Paul Gier pg...@redhat.com wrote:
Jason van Zyl wrote:
On May 3, 2010, at
Good point, it's probably a bad idea to add a pom that contains any dependencies
or other information that would affect the build of a project using the
dependency. Although I think it would be safe to add information like project
url, description, and license if those are available since those
14 matches
Mail list logo
