On 22/08/2013, at 4:37 AM, Phillip Hellewell wrote:
> My idea to solve this was to add support for a
> true in the declaration. Thoughts?
I didn't think we could change the POM schema? Not without some epic major
reasoning ( and if we were to change it, there's plenty of things change… )
Mar
Le mercredi 21 août 2013 19:28:03 Robert Scholte a écrit :
> The problem with newest is that it can *never* be overridden by the active
> project, for whatever reason.
> Instead of newest I'd prefer to use the RequireUpperBoundDependencies
> Enforcer Rule[1] which give you the same result (otherwis
Le mercredi 21 août 2013 10:37:40 Phillip Hellewell a écrit :
> On Wed, Aug 21, 2013 at 3:19 AM, Baptiste Mathus wrote:
> > Wondering: is this strategy still gonna choose the newest version
> > specified
> > even if I specify a version inside my pom? Or is it only gonna be used
> > between depende
The problem with newest is that it can *never* be overridden by the active
project, for whatever reason.
Instead of newest I'd prefer to use the RequireUpperBoundDependencies
Enforcer Rule[1] which give you the same result (otherwise the build will
fail).
Robert
[1]
http://maven.apache.o
yes, good idea
yes, just removing the "apache-resource-bundles" line from extpaths.txt will
let content from the general site.
Notice that it will be useful to define the url in the pom of every module to
point to this page, or the calculated url will point to non-existent page
Regards,
Hervé
On Wed, Aug 21, 2013 at 3:19 AM, Baptiste Mathus wrote:
> Wondering: is this strategy still gonna choose the newest version specified
> even if I specify a version inside my pom? Or is it only gonna be used
> between dependencies?
The behavior we actually need and want most of the time is for it
Looks to be the maven-shade-plugin that is doing the property substitution.
They built with Maven 3.1.0 (I had been worried it was a 2.1.0 or 2.2.0
issue)
On 21 August 2013 14:05, Olivier Lamy wrote:
> On 20 August 2013 22:16, Arnaud Héritier wrote:
> > Transitively it won't be propagated AFAI
That's odd.
In my released poms, I do not have token substitution for the maven
variables:
default-profile
true
${java.home}/../lib/tools.jar
${java.
On 21 August 2013 14:59, Dennis Lundberg wrote:
> Yes, both OSX and Windows jobs are unreliable in their current state. When
> they are more mature we can move them from the "unstable" view to the
> "stable" view.
>
> Let me check with builds@a.o to see if they have the resources to breathe
> so
Yes, both OSX and Windows jobs are unreliable in their current state. When
they are more mature we can move them from the "unstable" view to the
"stable" view.
Let me check with builds@a.o to see if they have the resources to breathe
some life into that OSX box, before setting up something extern
The only thing I've ever knit is a scarf, in grade 5. So if you want a grade 5
quality scarf, no problem. It will only take me a year.
On Aug 21, 2013, at 6:23 AM, Kristian Rosenvold
wrote:
> Maybe you can knit something for my mac mini flowerpot stand, the one
> that runs windows ?
>
> Kris
Maybe you can knit something for my mac mini flowerpot stand, the one
that runs windows ?
Kristian
2013/8/21 Jason van Zyl :
> I agree that it would be nice to have Windows and OSX builds. But looking at
> our grid and that those builds are either disabled or haven't passed in
> months I don'
I agree that it would be nice to have Windows and OSX builds. But looking at
our grid and that those builds are either disabled or haven't passed in months
I don't think one can consider them reliable, or contribute to the notion of
being releasable.
I can put an OSX machine in a rack, and I ca
On 20 August 2013 22:16, Arnaud Héritier wrote:
> Transitively it won't be propagated AFAIK. You want to reuse it by
> inheritance (and from a Pom out of your current project) ?
?? No it's resolved.
Sample:
git clone https://code.google.com/r/alexeagle-guava/ guava
cd guava
guava module has a de
On Aug 21, 2013, at 12:39 AM, Dennis Lundberg wrote:
>>
>> This certainly may not be new but does it make sense to release a bugfix
>> release (3.1.1) using a *milestone* release (Aether 0.9.0.M3)?
>>
>> Thanks,
>> S.
>>
>
> IMO if these criteria are fulfilled, I don't see a problem:
>
> *
Wondering: is this strategy still gonna choose the newest version specified
even if I specify a version inside my pom? Or is it only gonna be used
between dependencies?
If the latter, I may agree it can be of interest.
But with the first I guess it would get crazy not being able to force the
versi
Thanks Hervé
The bundles don't have one site for each bundle, and I don't intend to
create them. The plan is to have all pages in the main site.
With that plan should I remove the "apache-resource-bundles" line from
extpaths.txt and add a corresponding page under /content ?
On Tue, Aug 20, 2013
Currently it's only one page, but I plan on expanding it so I prefer to
have it in the site.
On Tue, Aug 20, 2013 at 5:13 PM, Jason van Zyl wrote:
> How many pages is it. Would it just be easier in the wiki?
>
> On Aug 20, 2013, at 7:38 AM, Dennis Lundberg wrote:
>
> > Anyone?
> > Den 9 aug 20
On Mon, Aug 19, 2013 at 1:43 PM, Stephane Nicoll
wrote:
> Hi,
>
> On Mon, Aug 19, 2013 at 1:38 PM, Jason van Zyl wrote:
>
> > I hope to release the next version in pretty short order, integrating
> > Aether 0.9.0.M3 and fixing a few more bugs. So if you can't do the things
> > you want by tomorro
In order to get a working build of the Core ITs there are a number of steps
that needs to be taken. These include checking out the source for the ITs
and the version of Maven you want to test. Then there are an elaborate
setup of M2_HOME local.repo and some other stuff. There is a shell script
to h
20 matches
Mail list logo
