oo.de]
> Sent: Tuesday, October 13, 2009 11:52 AM
> To: Maven Users List
> Subject: Re: Running Jar file created by Maven
>
> I'd use the maven-shade-plugin because a) it's a maven-core-plugin and as
> such it's pretty well maintained b) it can also 'shade&#
Always nice to have choices.
Now, which one is better, the onejar-maven-plugin or fatjar?
On Tue, Oct 13, 2009 at 7:15 AM, Stevo Slavić wrote:
> http://code.google.com/p/onejar-maven-plugin/
>
> http://anydoby.com/fatjar/
>
> Regards,
> Stevo.
>
> On Tue, Oct 13, 2009 at 2:03 PM, Marcin Kwapisz w
> Then make your own repository. See how useful that is.
Jason, you are probably right.
http://xircles.codehaus.org/projects/pinin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: user
indexUpdateUrl, // index update url or null if derived from repositoryUrl
false, false);
}
What should be the CONDITION?
On Tue, Sep 29, 2009 at 12:02 PM, Albert Kurucz wrote:
> For some start-ups, this could mean a business opportunity!
> Nobody said, that the quality info should be
It looks like some of the stuff is outdated on that "best practice" document.
Maybe it was OK with Maven1.
Use it only if insane
(this is property of:
http://repo2.maven.org/maven2/org/apache/derby/derby-project/10.5.3.0/derby-project-10.5.3.0.pom)
On Tue, Sep 29, 2009 at 4:18 PM, paulv wrote:
For some start-ups, this could mean a business opportunity!
Nobody said, that the quality info should be given away free.
On Tue, Sep 29, 2009 at 7:21 AM, Albert Kurucz wrote:
>> Do you really mean that you would like to enforce such -source-release.zip
>> artefacts to be publishe
wrote:
> Le samedi 26 septembre 2009, Albert Kurucz a écrit :
>> For the additional requirement, getting into the pure Maven repo (The
>> best), I really meant: build-able.
>>
>> Me too, I don't really care what tool you use to build it as long as
>> the too
Tamas, could explain "MRMs + grouping + mirrorOf" or send a link?
2009/9/28 Tamás Cservenák :
> Sorry for thread hijack, but was not able to resist...
>
> Another thing to think about, since it's adoption:
>
> On Mon, Sep 28, 2009 at 5:34 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> w
p 28, 2009 at 9:02 AM, Albert Kurucz
> wrote:
>> Any other flaws?
>>
>>> A build then becomes dependent on the certlist in order for it to function.
>> The project's build will not become dependent of the certlist.
>> If it was able to build with certlist
e
> "settings.xml" or at the "pom.xml" level.
>
> If you need a specific certlist in order to build correctly, then I do not
> think we should allow your new artifacts into central... and now certlists
> are a dead duck
>
> Just my opinion,
>
> Stephen
>
>
Filtering is already used for another Maven feature.
To avoid ambiguity, we should better call the one what I defined:
repository-skinning or repository-certification.
Do you think this new feature would hurt the repo or any Maven user?
On Sun, Sep 27, 2009 at 11:27 PM, Albert Kurucz wrote:
>
It is not necessary to create a new repo and it is not necessary to
modify anything on Central or the policies how it is managed. Mess
could be cleaned up virtually if I could attach a filter.
In the ~/.m2/settings.xml for example, I should be able to add a list
of repository addresses and for eac
he 3 maintained repo will be used.
On Sat, Sep 26, 2009 at 1:41 PM, Stephen Connolly
wrote:
>
>
> Sent from my [rhymes with tryPod] ;-)
>
> On 26 Sep 2009, at 18:58, Albert Kurucz wrote:
>
>> Very nice idea to measure the quality.
>> But sorry Tamas, 50% corr
Very nice idea to measure the quality.
But sorry Tamas, 50% corrupt or 90% corrupt does not make a difference for me.
Especially not, when I have feeling that it is possible to maintain a
100% clean repo with the right automation tools.
If Sonatype's goal is to sell these tools only for paying cust
/opensolaris-discuss/2005-February/002170.html
On Fri, Sep 25, 2009 at 4:31 PM, Brian Fox wrote:
> On Fri, Sep 25, 2009 at 12:44 PM, Albert Kurucz
> wrote:
>> Technically it is possible to manage 3 different OSS Maven repos.
>>
>> 1. The good enough
>> This is the cur
lly
wrote:
> 2009/9/25 Hervé BOUTEMY :
>> Le vendredi 25 septembre 2009, Stephen Connolly a écrit :
>>> 2009/9/25 Albert Kurucz :
>>> > The pure Maven repo should say:
>>> > We honestly don't care which Maven plugin the people build with, as
>>
ments.
Finally this could be achieved.
(OK it won't come to Maven Central)
Anyone care about having Maven Pure?
On Fri, Sep 25, 2009 at 8:36 AM, Albert Kurucz wrote:
> "We just need a high-quality POM, correct metadata, javadocs, sources,
> and signatures."
> It is debat
are about build ability or not!
On Thu, Sep 24, 2009 at 10:56 PM, Jason van Zyl wrote:
>
> On 2009-09-24, at 7:52 PM, Albert Kurucz wrote:
>
>> Jason and Brian, thanks for the explanations.
>> Understood, the policy of not removing anything from Maven Central
>> ser
use from and supply to this one instead of the big and
ugly.
On Thu, Sep 24, 2009 at 6:44 PM, Brian Fox wrote:
> On Thu, Sep 24, 2009 at 3:16 PM, Albert Kurucz
> wrote:
>> Requirements for the POMs are defined as:
>> http://maven.apache.org/guides/mini/guide-central-repositor
Garbage collection?
Identify corrupted ones and remove.
On Thu, Sep 24, 2009 at 4:41 PM, Brian Fox wrote:
> On Thu, Sep 24, 2009 at 12:04 PM, Albert Kurucz
> wrote:
>> Brian,
>> Probably no one ever suggested that the corrupt artifacts should be
>> fixed, because fix
Central, because the guard
was sleeping.
Rules are enforced or here comes the anarchy...
The severity of the damage?
The Central should be an example of good practice. Otherwise...
On Thu, Sep 24, 2009 at 4:41 PM, Brian Fox wrote:
> On Thu, Sep 24, 2009 at 12:04 PM, Albert Kurucz
> wrote:
&g
inly focus on
> stopping the garbage from getting in there in the first place.
>
> On Thu, Sep 24, 2009 at 7:40 AM, Albert Kurucz
> wrote:
>> According to http://www.think88.com/resources/Maven_white_paper_june_2009.pdf
>>
>> "
>> Sonatype maintains a centra
ser's builds to change in subtle ways.
>
> There are plans to get some of this cleaned up and mainly focus on
> stopping the garbage from getting in there in the first place.
>
> On Thu, Sep 24, 2009 at 7:40 AM, Albert Kurucz
> wrote:
>> According to http://www.think88.c
;
> Either way, in my opinion it's definitely the single most
> annoying thing with maven: the "" field is interpreted
> in different ways for every instance (sometimes it allows
> variables, sometimes it doesn't: sometimes it allows ranges,
> sometimes it doesn
Is property substitution really forbidden in
/project/parent/(groupId|artifactId|version)?
If yes, how is it possible to see that on this Maven Central project?
http://repo2.maven.org/maven2/org/apache/derby/derby/10.5.3.0/derby-10.5.3.0.pom
Is property substitution really forbidden in
/project/(g
According to http://www.think88.com/resources/Maven_white_paper_june_2009.pdf
"
Sonatype maintains a central repository with more than 90,000 artifacts,
consuming more than 60 GB of storage. In addition to the artifacts
themselves, the
Maven Central Repository also contains a POM-file for each of
e pom
> before the sync is turned on or the jars are loaded.
>
> On Thu, Sep 17, 2009 at 10:13 AM, Albert Kurucz
> wrote:
>> Hi,
>>
>> I have a project with builds with Maven.
>> My goal is to see my project on Central.
>>
>> There is a nice guide at
&
Hi,
I have a project with builds with Maven.
My goal is to see my project on Central.
There is a nice guide at
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
which tells me the requirements.
Is there any Report plugin out there, which would check all the
requirements fo
28 matches
Mail list logo
