Steven,
It is absolute necessary to sit down and brainstorm.
Thanks for the ideas!
I mean it. :-)
On Tue, Oct 6, 2009 at 3:22 PM, Stephen Connolly
wrote:
> metadata is data about data
> metaanalysis is an analysis of other analyses
> metaworry is worrying about worrying
> metacognition is thinkin
metadata is data about data
metaanalysis is an analysis of other analyses
metaworry is worrying about worrying
metacognition is thinking about thinking
metametadata is therefore data about metadata
the jar is your artifact : data
the pom is data about the artifact : metadata
the metadata.xml is
Hi!
I implemented the fetch vs push URL and did a lot of cleanup stuff for the git
providers. The latest is available at:
http://github.com/struberg/maven-scm-providers-git
(attention: also contains the new pure java jgit provider)
>From the changelog:
*snip*
Implement separate fetch and pus
Steven,
http://lmgtfy.com/?q=maven+metametadata
Found this 1st:
"
So he's talking about me!? Does that make me a maven? Does mavenhood
explain metametametadata? Does it excuse all of its self-referential
posts? Are you sick of them yet? Is this clever? Can I ask anymore
questions? Um, no.
"
>From
The Maven team is pleased to announce the release of the Maven
Repository Plugin, version 2.3
This plugin assists the user in creating archived bundles that are
designed to meet all requirements for upload to the central Maven
repository.
http://maven.apache.org/plugins/maven-repository-plugin/
The Maven team is pleased to announce the release of the Maven Resources
Plugin, version 2.4.1
This plugin filters non-Java resource files, replacing expressions with
values from the POM or any of the filtering properties files you choose
to configure.
http://maven.apache.org/plugins/maven-resou
Albert,
I think you are confusing the metadata.XML files from the pom.XML files
the metadata sonatype are referring to is the metametadata (ie
metadata.xml files) and nit the artifact metadata (ie pom.xml files)
there are places in central where the metametadata is incorrect. let's
get tho
Brian,
This is a Stalemate!
I go to sleep() until that code arrives to you.
If I had the time, I promise I would code it for you.
On Tue, Oct 6, 2009 at 12:30 PM, Albert Kurucz wrote:
> Brian,
>
>> This is why in suggestion 1) I said lets get some code to validate the
>> artifacts.
>
> Reading th
Brian,
> This is why in suggestion 1) I said lets get some code to validate the
> artifacts.
Reading this article I thought you already have that
http://www.think88.com/resources/Maven_white_paper_june_2009.pdf
"
Sonatype maintains a central repository with more than 90,000 artifacts,
consuming
On Tue, Oct 6, 2009 at 9:30 AM, Albert Kurucz wrote:
> Tamas, I cannot predict when, but once it will be done in a "machine
> way" or a mathematical/logical proof will be discovered that it is
> impossible. Agreed, it will not be easy.
>
This is why in suggestion 1) I said lets get some code to v
This vote has passed with the following:
+1 (binding): John, Arnaud, Jason, Brian, Olivier, Stephen, Benjamin
+1 (non-binding): Paul
I'll finish this release and get the appropriate announcements out.
John Casey wrote:
Hi everyone,
This release is meant to fix a couple of the biggest bugs int
This vote has passed with the following:
+1 (binding): John, Benjamin, Arnaud
I'll finish the release and make appropriate announcements.
John Casey wrote:
Hi everyone,
We fixed 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11250&styleName=Text&version=15560
There a
+1, still waiting for infra to create my account :-(
-Stephen
2009/10/6 John Casey
> +1
>
>
> Benjamin Bentmann wrote:
>
>> Hi,
>>
>> We solved 10 issues:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15018&styleName=Html&projectId=11139
>>
>> There are still a couple of issues
+1
Benjamin Bentmann wrote:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15018&styleName=Html&projectId=11139
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11139&status=1
Staging r
+1
2009/10/4 Benjamin Bentmann :
> Hi,
>
> We solved 10 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15018&styleName=Html&projectId=11139
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11139&status=1
>
+1
-Lukas
Benjamin Bentmann wrote:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15018&styleName=Html&projectId=11139
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11139&status=1
Tamas, I cannot predict when, but once it will be done in a "machine
way" or a mathematical/logical proof will be discovered that it is
impossible. Agreed, it will not be easy.
2009/10/6 Tamás Cservenák :
> Not to mention that these below are "formal" requirements only. Their
> _presence_ is requi
Changing the rules is OK. Not publishing the change of rules
(policies) is not OK, because it is like getting "undocumented
features" to the system. We cannot talk about "broken" until we define
good, and I believed once it was defined. If you redefined good,
please publish it.
On Mon, Oct 5, 2009
Hi
I am trying build a plugin template and during the build process, I have
encountered 3 artefacts missing from the maven repository. These are:
1) jta:jta:jar:1.01 - but this file exists jta:jta:jar:1.01b
2) saxon:saxon0noaelfred:jar:6.5.5 - is missing
3) jndi:jndi:jar:1.2.1
Hi developers,
I send you this mail because I'm totally irritated. I tried a few times
to release a component. But it always fails while committing in
release:prepare phase.
Problem:
[INFO]
[INFO] BUILD SUCCE
Not to mention that these below are "formal" requirements only. Their
_presence_ is required, but nothing is said about their _content_.I can
publish a POM that will _have_ dependencies section, but how do we know that
the dependencies section is _correct_?
Also: license in POM. What license "name
21 matches
Mail list logo
