with much
> newer maven versions locally, leading to some inconsistent dependency
> resolutions.
>
> I was wondering if there was any progress in the last years, so that we can
> switch to a newer Maven version?
>
> On Mon, Nov 7, 2016 at 12:04 AM Stephen Connolly <
> step
On Sat 23 Nov 2019 at 14:53, Enrico Olivelli wrote:
> Stephen
>
> Il sab 2 nov 2019, 11:00 Stephen Connolly >
> ha scritto:
>
> > On Thu 3 Oct 2019 at 16:13, Enrico Olivelli wrote:
> >
> > > Hello,
> > > I am going to propose a new release proc
So I know that Sonatype have or had a feature in nexus that let you approve
what dependencies could be consumed by developers from its hosted Maven
repo. If you used that you could then replicate the nexus storage back-end
to the offline network via sneaker-net (or better a dmz that only has
access
source with a
concrete version.h that gets found first and presto!
On Sat 2 Nov 2019 at 09:59, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
>
> On Thu 3 Oct 2019 at 16:13, Enrico Olivelli wrote:
>
>> Hello,
>> I am going to propose a new release
On Thu 3 Oct 2019 at 16:13, Enrico Olivelli wrote:
> Hello,
> I am going to propose a new release procedure in Apache ZooKeeper project
> in the direction of using the Maven Release Plugin.
> Usually with the Maven Release Plugin you are performing to tasks:
>
> mvn release:prepare -> change vers
So I wrote a blog post on how we use the Maven Release Plugin with Jenkins
to do Continuous Delivery and Continuous Deployment in the DevOptics team
of CloudBees.
If you are interested it's at:
https://www.cloudbees.com/blog/apache-maven-continuous-deliverydeployment-devoptics-teams-approach
The
The Apache Maven team is pleased to announce the release of the Apache
Maven 3.5.4.
Apache Maven is a software project management and comprehension tool. Based
on the concept of a project object model (POM), Maven can manage a
project's build, reporting and documentation from a central piece of
in
The Apache Maven team is pleased to announce the release of the Apache
Maven 3.5.2
You can download the appropriate sources etc. from the download page
Contributors
The Apache Maven team would like to thank the following contributors,
without whom this release would not have been pos
The Apache Maven team is pleased to announce the release of the Apache
Maven 3.5.2
You can download the appropriate sources etc. from the download page
Contributors
The Apache Maven team would like to thank the following contributors,
without whom this release would not have been pos
So you could have scope=compile&optional=true (which means the dep is
non-transitive)
On Wed 27 Dec 2017 at 00:26, Andy Feldman wrote:
> On Dec 26, 2017 11:34, "Stephen Connolly" >
> wrote:
>
> On Sun 24 Dec 2017 at 18:01, Andy Feldman wrote:
>
> > Assumi
On Sun 24 Dec 2017 at 18:01, Andy Feldman wrote:
> Assuming I have a dependency relationship of "my-project -> my-library ->
> upstream-library", with each dependency in compile scope, I know that
> my-project transitively picks up a compile scope dependency on
> upstream-library. Reading the doc
On Fri 17 Nov 2017 at 21:07, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
> On Fri 17 Nov 2017 at 13:57, Eric B wrote:
>
>> Hi Bernd,
>>
>> Thanks for the insight. I understand what you mean, and to be honest, not
>> entirely sure how to
On Fri 17 Nov 2017 at 13:57, Eric B wrote:
> Hi Bernd,
>
> Thanks for the insight. I understand what you mean, and to be honest, not
> entirely sure how to deal with that yet. At the moment, it isn't a huge
> deal for me since my project is fairy self contained. I have an API module
> which I
On Thu 16 Nov 2017 at 21:10, Adam Hardy
wrote:
> On 16/11/17 20:40, Stephen Connolly wrote:
> > I think you’ll want to keep master with a version of at least SNAPSHOT or
> > 1-SNAPSHOT and wholesale replace it with the real build version number on
> > the CI server and just
On Thu 16 Nov 2017 at 13:26, ahardy42 wrote:
> V. interesting, thanks.
>
> I'm using TeamCity so controlling an infinite loop using trigger configs
> should be easy.
>
> However I don't want to use snapshot versioning at all, so the
> maven-release-plugin is essentially not the right tool for the
y people claim Maven doesn’t fit for CD just because they don’t
understand that the release plugin was designed for a workflow that has its
own needs shaped by the release processes of Apache Foundation...
>
> Regards,
>
> Arnaud.
>
>
> 2017-11-08 22:21 GMT+01:00 Stephen Connolly
I recommend that you use invoker for testing plugins.
On 9 November 2017 at 13:07, Francois MAROT
wrote:
> I'm no expert at all, but just to let you know: last time I tried the test
> harness plugin, I also gave up... :(
> I think some advocate to use the maven-invoker-plugin to test in real
> c
On Sun 5 Nov 2017 at 11:31, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
> On Fri 27 Oct 2017 at 23:28, Laird Nelson wrote:
>
>> On Fri, Oct 27, 2017 at 1:58 AM ahardy42
>> wrote:
>>
>> > How can I tell maven to increment the version and
On Fri 3 Nov 2017 at 16:18, MAISONOBE Luc wrote:
>
> Hervé BOUTEMY a écrit :
>
> > yes, really ugly :)
> >
> > usual with Maven when you're trying to do by configuration something
> > that would
> > best be served with a supported feature, that defines the associated
> > convention
> >
> > that'
On Fri 27 Oct 2017 at 23:28, Laird Nelson wrote:
> On Fri, Oct 27, 2017 at 1:58 AM ahardy42
> wrote:
>
> > How can I tell maven to increment the version and commit the edited pom
> > without the CI platform seeing the commit and kicking off again in an
> > infinite loop?
>
>
> Indeed. If you ju
Hervé was looking for suggestions on how we can use Jenkins more
effectively.
I decided to use this as an opportunity to kill several birds with the one
stone.
I’m recording a series of live, unscripted, unedited videos developing
Jenkins plugins and Jenkinsfile shared libraries to provide a much
The Apache Maven team is pleased to announce the release of the Apache
Maven 3.5.2
You can download the appropriate sources etc. from the download page
Contributors
The Apache Maven team would like to thank the following contributors,
without whom this release would not have been pos
On Fri 8 Sep 2017 at 11:22, Baptiste Mathus wrote:
> Le 7 sept. 2017 17:00, "Tushar Kapila" a écrit :
>
> I had to delete a directory once as i had pressed Ctrl-C while it was
> downloading jars and a 0kb jar was created. This was in 2013, maybe it
> downloads to a temp file and then create the
So poll results:
493 votes cast
25% want Java 7,8&9 for Maven 3.6.x
65% want Java 8&9 for Maven 3.6.x
10% want Java 8&9 for Maven 3.6.x and 6 months of backporting to 3.5.x
On Sat 9 Sep 2017 at 11:50, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
https://twitter.com/asfmavenproject/status/906451059966693376
--
Sent from my phone
On 13 June 2017 at 07:47, wuchang <583424...@qq.com> wrote:
> I am using maven to compile apache-hive-2.1.1-src for debug reason ,I use
> -X paremeter to print out the debug information. but finally , the
> compilation failed:
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-as
I think that is a bug that is in scope for 3.5.1 or 3.6.0
On 31 May 2017 at 22:30, Laird Nelson wrote:
> (I've been working with Maven since at least 2004 and I think I *still*
> don't
> get transitive dependencies.)
>
> I have a pom.xml file of type pom that has some compile-scoped dependencies
On Mon 8 May 2017 at 03:58, Eric Benzacar wrote:
> Hi,
>
> Interesting. Would something like this be functional then? It seems to
> work, but I don't know if it is working as expected, or by fluke:
>
> com.soebes.examples.j2ee parent
> ${revision} pom ..
>
> 1.2.1-${buildNumber}
> SNAPSHOT
>
ote:
>
> > Hi Stephen,
> > I took it there. From the initial response, I thought I should bring it
> > here. I hope someone can look into it.
> >
> > Rupinder
> > On 6 May 2017 18:06, "Stephen Connolly" >
> > wrote:
> >
> >> This
This is really an issue for the CXF mailing lists.
I suggest you take your question there.
On Sat 6 May 2017 at 12:26, Rupinder Singh wrote:
> Hi,
> Following the simple tutorial at
> http://www.cse.unsw.edu.au/~cs9322/labs/lab01/ I have created project
> named HelloWorldCXF in my CXF working
On Sat 22 Apr 2017 at 00:21, Curtis Rueden wrote:
> Hi Jörg,
>
> As far as I know, Maven has no notion of "major" vs. "minor" vs. "patch"
> versions in the style of e.g. SemVer.
>
> It simply judges which version is the newest via its algorithm, and uses
> the newest, since it is assumed that a d
e architect - https://loci.wisc.edu/software
> ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden
>
>
> On Tue, Apr 11, 2017 at 2:44 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > On Tue 11 Apr 2017 at 16:02, Curtis Rueden wro
On Tue 11 Apr 2017 at 16:02, Curtis Rueden wrote:
> Hi Hector,
>
> > This is fine as long as the dependency is always set to x.y.z-Snapshot
> > and the dependency is always overwritten this way. What if the
> > producer produces x.y.z.1-Snapshot, x.y.z.2-Snapshot, x.y.z.3-Snapshot
> > and I want
The Apache Maven team would like to announce the release of Apache Maven
3.5.0.
You can download the appropriate sources etc. from the download page
http://maven.apache.org/download.cgi
Notable changes
===
- ANSI colors added to the console output
- Fix various bugs in mvn scripts r
The Apache Maven team would like to announce the release of Maven
3.5.0-beta-1.
http://maven.apache.org/
NOTE: This is an BETA release. There is the potential that features may be
removed between this release and the first GA release in the 3.5.x release
line.
Please consult the Known Issues sect
Can you create an issue against the MNG project in the issue tracker and we
will consider it from there
On 2 March 2017 at 08:24, Andreas Sewe
wrote:
> Hi,
>
> > Any chance the Aether work would somehow enable declaring server
> credentials only once in settings.xml and then reusing them for mul
The Apache Maven team would like to announce the release of Maven
3.5.0-alpha-1.
http://maven.apache.org/
NOTE: This is an ALPHA release. There is the potential that features may be
added/removed between this release and the first GA release in the 3.5.x
release line.
Please consult the Known Iss
After some discussion and debate, the Maven developers have agreed [1] to
replan the next release of Maven.
The original plans for Maven 3.4.0 were that it should consist of
effectively a no-op drop in replacement of Eclipse's Aether project (which
has been retired at the Eclipse Foundation) for t
You do have relativePath set correctly for the separate parent from
aggregator?
On Wed 30 Nov 2016 at 03:28, Benson Margulies wrote:
> My experience is precisely the opposite of yours. The most common
> practice is for the parent to be the aggregator; it's hard to get the
> site plugin, for exam
yes that was the advice I gave on this thread originally. you do have to
fight a bit with the shade plugin to get them shaded in though... which is
why I think we may need to rethink how we do shade
On 6 November 2016 at 22:36, Jörg Schaible wrote:
> Stephen Connolly wrote:
>
> >
e.org/mod_mbox/flink-dev/201512.
> mbox/%3CCANZa%3DGvFA%2B61968DBYoZc%3D8WfEmoF01DJAkmvzUcUH5XycLQ5w
> %40mail.gmail.com%3E
>
>
> On Thu, Dec 10, 2015 at 5:01 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > You need to do this in any module that is prod
There are two solutions.
1. Use Maven < 3.3.0
2. Mark the dependencies that are shaded as optional or provided in the
module doing the shading
In the transition from Maven 3.2.x to Maven 3.3.x the internal model was
made read-only which rendered the hacks that the shade plugin has been
using (to
On Thursday 27 October 2016, Robert Scholte wrote:
> In my opinion it is a good choice to make the MavenProject immutable. This
> way the content of the pom.xml will always match the model, no magic.
> To adjust properties you could use MavenSession.userProperties instead,
> and I would expect th
If you use build helper, IntelliJ picks it up automatically too... as does
netbeans.
On Sunday 23 October 2016, Robert Patrick wrote:
> Agreed, I didn’t intend to start a religious war over IDEs.
>
> It seems like Eclipse requires a plugin to understand a Maven plugin.
> IntelliJ takes the oppos
Short answer: no
On phone, so can't give long answer
On Friday 21 October 2016, Rémy Saissy wrote:
> Hi,
> is there a Maven plugin that allows to automatically append a classifier
> given a groupId?
>
> I would do something like that:
>
>
> org.apache.maven.plugins
> maven
You could create your own safe-batik-bridge which is empty and has both
dependencies and then just ask everyone to use that instead...
Or deploy to your proxy of central a batik-bridge:1.8-yourcompany-1 and use
depMgmt to pin that version
On Thursday 13 October 2016, Curtis Rueden wrote:
> Hi e
For pipeline you want to use the mavenLocalRepo property of the withMaven
step in the
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Maven+Plugin
On 13 October 2016 at 16:41, Benson Margulies wrote:
> So, here's a specific puzzle. I want to enable multiple branches in
> the Jenkins job and
uch simpler to
> configure). Be warned that Maven 3.3 support is still busted for projects
> that use .mvn/maven.config waiting on https://issues.apache.org/
> jira/browse/MNG-5889 to be merged...
>
>
> -Original Message-
> From: Stephen Connolly [mailto:stephen
https://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html
is the message from your friendly neighbourhood Apache Maven PMC member and
Jenkins committer!
Two options:
1. (oldschool) Freestyle Job with a Maven build step
2. (coolkids) Multibranch Pipeline Job with a Jenki
The latest version of maven is compiled top target java 1.7+
If you are using the openjdk class path, it would probably work. As the gnu
class path is only 1.5/1.6 compatible that would certainly not work.
Give it a try... Or investigate tool chains to run maven with openjdk and
fork jamvm for su
https://github.com/mojohaus/build-helper-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/buildhelper/AbstractDefinePropertyMojo.java#L47
would be the recommended way to define a property... I would be interested
to find out if there is an issue in build-helper... one should be able to
cre
Is one project resolving the parent from the reactor and the other removing
from the repository cache?
On Saturday 1 October 2016, Oliver B. Fischer wrote:
> I use the property ${project.parent.basedir} in two projects in different
> assembly descriptors. In one project ${project.parent.basedir}
failsafe itself does not manage the lifecycle of your container.
Maven has a lifecycle with some phases:
pre-integration-test: to be used to start any services required by your
integration tests
integration-test: to be used to run the integration tests
post-integration-test: to be used to stop an
Failsafe does not require jetty. If your integration tests require that
your application be deployed to a servlet container - such as jetty - and
you do not want to have your tests manage the lifecycle of that container,
then you will require failsafe so that you can have maven manage starting
up a
Some of those properties are "magic" ones where if you inherit from parent
and do not override then the child's artifactId will be appended.
I am not 100% certain but IIRC the appending may be controlled by the
parent's url ending or not ending with a trailing / but this may not be
universal and m
The issue is that the artifact is being attached to the build and then
attached again, and some versions of maven complain if you try to attach
multiple artifacts at the same coords
On 5 August 2016 at 17:48, Anders Hammar wrote:
> Executing
> mvn verify deploy
> will execute the build lifecycle
TL;DR don't run `mvn clean verify deploy` run `mvn clean deploy` as
`deploy` is after `verify`
On 5 August 2016 at 18:09, Stephen Connolly wrote:
> So you have asked maven to, in sequence:
>
> 1. Run the clean lifecycle up to the phase `clean`
> 2. Run the default lifecycl
So you have asked maven to, in sequence:
1. Run the clean lifecycle up to the phase `clean`
2. Run the default lifecycle up to the phase `verify`
3. Run the default lifecycle *again* up to the phase `deploy`
That will run everything between `initialize` and `verify` twice...
If that's what you w
Kristian,
Well that's going to bomb out each failing module at the `test` phase in
the lifecycle... which would ordinarily be OK, but most people have abused
the lifecycle and will require the build to at least `package` in all
modules... what you really want for this use case is something like
fa
Can you reproduce this outside of Jenkins by trying to build a plugin in a
directory name that includes a literal %2f in the path?
If the answer is yes then you have a winner and file a JIRA in the Apache
Maven project.
If the answer is no, then likely this is the evil job type and you'll need
to
Welcome to the evil one.
I have a blog post entitled "Maven job type considered evil"
Basically the issue is that Jenkins (via the evil one) is injecting a
remoting channel into your maven execution nd using that channel to both
modify and monitor the build.
One of the plugins that does this is
There will probably be a 3.4 soon-ish once we get some other things sorted
out.
On 11 May 2016 at 19:53, Stephen Connolly
wrote:
> Probably we will wait for JDK 9 to be released so that we can kill off
> support for JDK 7 ;-)
>
> On 11 May 2016 at 19:11, Will Iverson wr
Probably we will wait for JDK 9 to be released so that we can kill off
support for JDK 7 ;-)
On 11 May 2016 at 19:11, Will Iverson wrote:
> Hi -
>
> Aside from this wiki page:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+4.0.0
>
> ...I can't find any information about Maven 4.
so that we know what range to restore, e.g.
pre-release pom has
...
[1.2,2.0)
which would get resolved into the release pom as
...
1.5
so that when we want to un-pin we can then see the original range and
up-lift it so that the development pom becomes
...
[1.5,2.0)
>
>
hat about enhancing the install plugin with a list of the latest installs
> and creating a mojo deploy:deploy-latest-install?
>
> Regards
> Mirko
> --
> Sent from my mobile
> Am 03.05.2016 18:15 schrieb "Stephen Connolly" <
> stephen.alan.conno...@gmail.com >:
&g
Here's an embryonic idea I had for doing Continuous Delivery with Maven
https://www.cloudbees.com/blog/new-way-do-continuous-delivery-maven-and-jenkins-pipeline
Probably needs a little fleshing out.
-Stephen
I think that if your SCM supports the options and your MRM supports staging
then you can get the workflow you want by basically making every build a
release build e.g.
mvn -DreleaseVersion=1.0.0.${BUILD_NUMBER} \
-DdevelopmentVersion=1.0.0.0-SNAPSHOT \
-DsuppressCommitBeforeTag=true \
-Dpush
do debugging I will always end up in the sources of
> the artifact downloaded from the artifact repository and not in the source
> code of project A which I also have checked-out.
>
> Regards,
> Gerrit
>
> -Ursprüngliche Nachricht-
> Von: Stephen Connolly [mailto:stephen.al
If I were doing this myself here is what I would do:
I would use a MRM that has staging support and setup a Jenkins Pipeline
that starts by doing
`mvn release:prepare release:perform -B -DpushChanges=false
-DlocalCheckout=true "-DdevelopmentVersion=dev-SNAPSHOT"
"-DreleaseVersion=${BUILD_ID}" "-Dp
Don't configure your Pom to do this.
Use parameterized tests or JUnit theories.
On Monday 18 April 2016, Maple Wang wrote:
> Hi,
>
>
> We want to execute one test case several times in maven test, each time we
> will give it different input. First thought in my head is using profile to
> handle
I share your concern. We could fix the concern if we created the
transformed pom on disk so that things like GPG signatures were generated
correctly, but AIUI the issue there was that the pom could not be put in
target as that would break relative paths.
I suspect this is also related to the issue
I use local aggregator projects all the time to work on multiple loosely
related projects.
I will typically use ../../foo/bar references
The parent tag will be left unmodufied
I use it also outside of the IDE as that lets me run maven without going as
far as the install phase which pollutes the
the core
On 10 March 2016 at 16:43, Benson Margulies wrote:
> On Thu, Mar 10, 2016 at 3:04 AM, Stephen Connolly
> wrote:
> > Also I suspect this doesn't fully include logic to ensure that the
>
> 'this' = my code, or 'this' = the core imp
Also I suspect this doesn't fully include logic to ensure that the
substitution resolved pom is installed/deployed, so may cause issues for
out-of-reactor consumption as a dependency, or GPG signature validation if
you try to "fix" with a hack
On Thursday 10 March 2016, Stephen
on-basis/auto-version-maven-extension.
> >>
> >> My extension is never called, whether I put it into .mvn or the maven
> >> home lib/ext directory. (Proved by running mvnDebug, setting a
> >> breakpoint, and attaching a debugger).
> >>
> >>
> &g
xpressions in version, but does not provide anything as "source" for
> those.
> >
> > On Wed, Mar 9, 2016 at 2:44 PM Stephen Connolly <
> > stephen.alan.conno...@gmail.com > wrote:
> >
> >> I have no clue... that is a different question we should a
I have no clue... that is a different question we should ask of the person
who implemented this functionality
On 9 March 2016 at 13:40, Benson Margulies wrote:
> On Tue, Mar 8, 2016 at 2:28 PM, Stephen Connolly
> wrote:
> > In the .mvn folder put an extension that contribut
On Tue, Mar 8, 2016 at 11:28 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > In the .mvn folder put an extension that contributes the ${rev} property
> > based on whatever you seem safe
> >
>
> Where does this mystical .mvn folder reside
t 11:18 AM, Eric B > wrote:
> > >
> > > > I personally have a pet-peeve of using system variables to define
> > version
> > > > numbers; I find it is counter productive to the building of maven
> > > > artifacts. There is no traceability to determine the a
only specific properties are permitted for expansion in XPath paths that
match the following regex /project/(parent/)?(groupId|artifactId|version)
On 2 March 2016 at 05:39, Raghu wrote:
> I have a POM with parent node as below:
> com.test pom.parent
> ${test.version}
> ../scripts/pom.xml
> Thi
and how do I differentiate @foo@bar@@ whether that would be equivalent to
either:
${foo}bar${}
or
${foo${bar}}
if using ${ } style delimiters for the start and end?
At least with ${ } style delimiters one can count braces...
how about @foo@bar@manchu@ is that supposed to be ${foo${bar}manch
+1
On Thursday 24 December 2015, Michael Osipov <1983-01...@gmx.net> wrote:
> Hi,
>
> as previously suggested, it makes sense to retire those skins because
> they haven't been updated for a long time and we don't have the resources
> to maintain them properly [1].
>
> Last releases:
> Maven Appli
I doubt it is the compilation that sucks up the time. Try running with test
execution skipped to see the time difference, eg `mvn clean install` vs
`mvn clean install -DskipTests`
If you are using `install` then likely there is no need to rebuild
everything each time and you can use the -pl -am an
va version (we shade hadoop
> and its guava in our project as well)
>
>
>
> On Thu, Dec 10, 2015 at 2:08 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com > wrote:
>
> > Dependency reduced poms require mutation of the model after the build
> > started. Jv
Dependency reduced poms require mutation of the model after the build
started. JvZ is investigating a different packaging type to resolve this...
Workaround for now is to mark all the dependencies that are removed as
true so that they are no longer transitive and that
way the effective reactor Pom
Bind dependency:copy to an execution and just specify all the artifactItems
in the execution.
On Monday 30 November 2015, David Hoffer wrote:
> Yeah that is what I ended up doing but would rather have gotten the files
> from Maven at build time instead of just adding manually to SVN...just
> fee
If you get this working, any chance you could share your work?
On 21 November 2015 at 21:20, Mirko Friedenhagen
wrote:
> Hello,
>
> I want to use to run tests on machine, where Maven is not installed
> and access to a repository is not allowed.
> However I want to (ab-)use the failsafe plugin so
:/// URL then you
need -llr AIUI
On 13 November 2015 at 12:09, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I would have tried the -llr command line option
>
> On 13 November 2015 at 11:58, Jörg Schaible
> wrote:
>
>> Hi folks,
>>
>> we have
I would have tried the -llr command line option
On 13 November 2015 at 11:58, Jörg Schaible
wrote:
> Hi folks,
>
> we have a requirement for a source code escrow
> (https://en.wikipedia.org/wiki/Source_code_escrow). Therefore we intended
> provide our source code with a local Maven repository th
FYI: You should be able to unpack the JDK into a user folder only and point
at that
On 4 November 2015 at 20:09, james pruett wrote:
> thanks.
> I gave up. I don't have admin rights and I read that installing jdk by just
> unpacking a zip file won't work.
> I just donated to the apache foundatio
The new link is
https://www.cloudbees.com/blog/playing-trade-offs-maven *BUT* somebody
managed to completely screw up the XML formatting when migrating from
the old blog hosting to the new blog hosting...
On 26 October 2015 at 17:21, Curtis Rueden wrote:
> Hi Reena,
>
> Stephen Connelly wrote a g
IIRC don't version ranges only work with Major.Minor.Patch-(Qualifier or
Build) formatted version numbers, eg 3.2.1-07
On Friday 2 October 2015, Benson Margulies wrote:
> I've just tried version ranges for the first time, and I hit a pothole.
>
> Step 1: set version in dependency to: 7.14.0.c52.
rested in taking a look at that when it's released.
>
> On Fri, Sep 25, 2015 at 5:20 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com > wrote:
>
> > Aha! This is where
> > https://github.com/jenkinsci/workflow-plugin/tree/master/multibranch
> > and/
Aha! This is where
https://github.com/jenkinsci/workflow-plugin/tree/master/multibranch
and/or https://github.com/jenkinsci/literate-plugin/tree/master come
into play... and shortly too there will be the multi-repo job type
(which (wearing cloudbees hat) we are in the process of open sourcing
(remo
Regression filed and fixed... you are just waiting for the next
release in the 3.3.x line
On 24 September 2015 at 19:40, Denis Golovin wrote:
> I have simple project structure:
>
> test-module
> |-pom.xml
> |-child1
> |-pom.xml
>
> test-module/pom.xml
>
> xsi:schemaLocation="http://mav
I have some ruby scripts that we use to detect all the modules with
changes (i.e. the seed set of modules that need a release) and
computes the release dependency tree for all the pom.xml files.
Then it will start with the first module with changes and release that
(by forking release:prepare rele
So if you have type=jar then dependencies of that artifact are transitive.
What I suspect was intended was to introduce a new packaging type (i.e.
jarjar) that was added to the classpath but does not pull in dependencies
to indicate a jar with its dependencies included...
At least that is what my
I have done it (by accident). It works but is super annoying... Especially
when you end up with and off-by-one version number in a couple of the
modules...
(Happened when some developer wanted to do a point release of one module
and kicked off the über-release so that one went to 1.5.1 and everyth
When you don't specify the value in the POM you are *effectively*[1]
specifying ${demoName}
So what you have done is disabled configuration via the CLI.
[1] I say *effectively* because if you did configure that and the property
was undefined then that explicit configuration would evaluate to the
Well that is if version ranges worked by magic...
How does [2,3) know that it is supposed to prefer the version from your
reactor?
If you are following some semver-like [1] versioning scheme, then you
should be building against 2 and running tests against any random *release*
(or all releases...
1 - 100 of 2426 matches
Mail list logo