I imagine there have to be a number of projects/companies out there
using Maven artifacts and incurring bandwidth costs to build systems.
Atlassian seems to be recommending the practice to its Bamboo users...
http://confluence.atlassian.com/display/BAMBOO/Populating+your+EBS+volume#PopulatingyourE
there was some talk about it during ApacheCON but there are some costs
associated
- S3 storage of the EBS snapshot
- bandwidth to upload the repo and keep it up to date
- an EC2 machine to do the rsync and scheduled snapshots of the EBS volume
There's an option to "sell" it so users end paying th
Cheers,
After experimenting a bit with EC2, It seems it would be ideal if
there were an EBS volume that had all the Maven central repository
within it. Does anyone know of such a thing?
thanks,
Mark
-
To unsubscribe, e-mail: us
While I read the doc, it didn't seem applicable. Now that you tell me
that there's no special trickery going on that tries to force 1.4 on
mojo projects, I'm off to revisit all the poms to see there's
something I missed.
On Sun, Dec 20, 2009 at 8:51 PM, Barrie Treloar wrote:
>> On Sun, Dec 20, 20
> On Sun, Dec 20, 2009 at 5:26 PM, Barrie Treloar wrote:
>> On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies
>> wrote:
>>> The eclipse plugin forces the compiler source version to 1.4 for maven
>>> plugins. I'm building a maven plugin that I want to require 1.5. Is
>>> there a way to tell the e
I did.
On Sun, Dec 20, 2009 at 5:26 PM, Barrie Treloar wrote:
> On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies
> wrote:
>> The eclipse plugin forces the compiler source version to 1.4 for maven
>> plugins. I'm building a maven plugin that I want to require 1.5. Is
>> there a way to tell the
On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies wrote:
> The eclipse plugin forces the compiler source version to 1.4 for maven
> plugins. I'm building a maven plugin that I want to require 1.5. Is
> there a way to tell the eclipse plugin to stop harassing me?
Did you check the docs?
http://ma
hi!
You catched a very old finesse of reporting plugin configuration (in fact, lots
of Jira issues have been opened for that very topic).
Please read
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
for an example how it should work.
LieGrue,
strub
---
Hello Maven users,
If one installs a snapshot of a plugin (P1) in local repository, and for
other plugin (P2) an IT, run using maven-invoker-plugin configured as
recommended to use isolated local repository for integration tests, is a
project which makes use of P1 snapshot, IT will fail since P1 s
Oh, it looks like this issue was fixed in maven-changelog-plugin version 2.2:
http://jira.codehaus.org/browse/MCHANGELOG-92
But version 2.2 is not in the repository yet...
--
View this message in context:
http://old.nabble.com/No-such-provider%3A-%27git%27-tp26859089p26866688.html
Sent from th
Wayne Fay wrote:
>
> Perhaps try adding it as an extension (google for info here)?
>
Same error with an "" element in the POM, like this:
...
org.apache.maven.scm
maven-scm-provider-gitexe
1.2
...
--
View this message in context:
http:/
> I did try that, but that is illegal syntax, based on the POM 4.0.0 XML
> schema definition (at http://maven.apache.org/maven-v4_0_0.xsd), the
> relevant parts of which I have paraphrased below:
Perhaps try adding it as an extension (google for info here)? I have
zero experience with what you're
This helped me! Thanks a lot!
19 декабря 2009 г. 14:45 пользователь Anders Hammar написал:
> Your plugin binding binds the resources plugin as configured to the Maven
> lifecycle. But you're executing
> mvn resources:copy-resources
> which isn't executing the lifecycle (it justs executed the copy
Wayne Fay wrote:
>
>
> No, you were so close before, did you read what I wrote?
>
> Try this:
>
>
>
>org.apache.maven.plugins
>maven-changelog-plugin
>
>
>
> org.apache.maven.scm
> maven-scm-provider-gitexe
>
>> DepMgmt does not affect reporting plugins in M2. You need to add the
>> dep directly to the plugin in the reporting section.
>>
> I've added the plugin directly to the reporting section, like this:
No, you were so close before, did you read what I wrote?
Try this:
org.apache
15 matches
Mail list logo