Re: [Maven-Release] Version update issue when a profile activates a module.

Hi Nils, I'll have a look. Right now I have fixed it this way: https://github.com/jvm-repo-rebuild/reproducible-central/pull/200 Note that I'm still curious about my original question regarding the maven release plugin and profiles during the version update. Niels On Sat, Sep 14,

Re: [Maven-Release] Version update issue when a profile activates a module.

Niels Basjes wrote: > The key problem is that 22 has such a limited lifespan that the normal > packages for systems like Ubuntu are not available. Would it be possible to use a third-party repository like the one from Azul (https://docs.azul.com/core/install/debian) to install OpenJDK packages?

Re: [Maven-Release] Version update issue when a profile activates a module.

> need > > a > > >> > different way of activating the profile. > > >> > > > >> > I have been looking if I can activate a profile if a toolchain > version > > >> is > > >> > available but that is not yet a feature. >

Re: [Maven-Release] Version update issue when a profile activates a module.

gt; is > >> > available but that is not yet a feature. > >> > Side question: Being able to activate an optional profile IF a > specific > >> > toolchain is available; Would that be a desirable feature in maven? > >> > > >> > Back to my original q

Re: [Maven-Release] Version update issue when a profile activates a module.

gt; > >> > >> > >> > >> > >> > >> > On Fri, Sep 13, 2024, 19:26 Tamás Cservenák >> wrote: >> > >> > > Howdy, >> > > >> > > I am just shooting in the dark, but why not: >> > &g

Re: [Maven-Release] Version update issue when a profile activates a module.

gt; > > T > > > > > > On Fri, Sep 13, 2024 at 11:41 AM Niels Basjes wrote: > > > > > > > > Hi, > > > > > > > > I have in my project a maven module that is only activated if a > specific > > > > profile is active

Re: [Maven-Release] Version update issue when a profile activates a module.

; > > > > I have in my project a maven module that is only activated if a specific > > > profile is active (by default it is not active). > > > Side note: It is an part that requires Java 22, optional during > > development > > > and I do want to release i

Re: [Maven-Release] Version update issue when a profile activates a module.

odule that is only activated if a specific >> > profile is active (by default it is not active). >> > Side note: It is an part that requires Java 22, optional during >> development >> > and I do want to release it with the maven-release-plugin >> > >> &

Re: [Maven-Release] Version update issue when a profile activates a module.

an part that requires Java 22, optional during > development > > and I do want to release it with the maven-release-plugin > > > > I have put this profile into both the list of profiles that need to be > > active during preparation and release (see sketch below). >

Re: [Maven-Release] Version update issue when a profile activates a module.

st of profiles that need to be > active during preparation and release (see sketch below). > > When I do "mvn release:prepare" it does not update the module2/pom.xml with > the new version. > I found that I need to explicitly activate it on the commandline as

Re: [Maven-Release] Version update issue when a profile activates a module.

ve during preparation and release (see sketch below). > > When I do "mvn release:prepare" it does not update the module2/pom.xml with > the new version. > I found that I need to explicitly activate it on the commandline as well to > activate it there too "mvn rele

[Maven-Release] Version update issue when a profile activates a module.

the list of profiles that need to be active during preparation and release (see sketch below). When I do "mvn release:prepare" it does not update the module2/pom.xml with the new version. I found that I need to explicitly activate it on the commandline as well to activate it ther

Re: Update plexus-archiver to 4.8.0 in maven-archiver

Hi, The release of version 3.6.1 is under voting [1] according to the release procedure [2] will be available publicly in a few days. [1] https://lists.apache.org/thread/p5nb5q4t9m18sn7yx26oby3hlb28v2d3 [2] https://maven.apache.org/developers/release/maven-project-release-procedure.html ni

Re: Update plexus-archiver to 4.8.0 in maven-archiver

Thanks for checking this. I am seeing that https://issues.apache.org/jira/browse/MSHARED-1292 is closed. But I am not able to find maven-archiver, 3.6.1 in mvnrepository yet. On Wed, Aug 9, 2023 at 4:51 PM Slawomir Jaranowski w

Re: Update plexus-archiver to 4.8.0 in maven-archiver

Hi Next version of maven-archiver is ready for release. I can release new version in next week. https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12353169 wt., 8 sie 2023, 14:12 użytkownik Debraj Manna napisał: > Hi > > maven-archiver is getting flagged for CV

Update plexus-archiver to 4.8.0 in maven-archiver

Hi maven-archiver is getting flagged for CVE-2023-37460 in our vulnerability scans. But I am seeing the latest version of maven-archiver (3.6.0) is still using plexus-archiver 4.4.0. Is there any plan to upgrade plexus-archiver to 4.8.0 in maven-a

Re: plugin to update version to patch version

thank you Hervé. To set the version I think there is also versions:set but I haven't found yet how to read to update the version to the next minor or patch, without providing any parameter. I'm just imagining two options illustrate my mind: setPatchVersion and setVersionSu

Re: plugin to update version to patch version

release plugin has an update-versions goal https://maven.apache.org/maven-release/maven-release-plugin/update-versions-mojo.html - Mail original - De: "Stephane Passignat" À: "Maven Users List" Envoyé: Vendredi 24 Juin 2022 21:19:18 Objet: plugin to update vers

plugin to update version to patch version

Hello, I actually create a branch (using scm plugin) from a tag (created by release plugin) to patch a release version of a library. After the branching I need to change the pom version from minor (ex: 1.0.2) to patch (ex: 1.0.2.0-SNAPSHOT). Are there any plugin for that ? I looked at versi

[Enforcer plugin] Snapshot update of currently analyzed module

nload snapshot updates for dependencies, but not for the current module. I have created a minimal reproducible example here : https://github.com/alexismanin/enforcer-test The project uses a single repository with snapshot update policy set to always, and we can see that enforcer always tries to dow

RE: request for documentation update about mirrors

True, it is "just a file". It was actually my first idea, before I emailed this list. But though it's "just a file", it's a file I'd have to keep editing every time I updated maven. It's likewise a file everyone else on the team needs to be taught to

Re: request for documentation update about mirrors

Well, it’s just a file to edit. -- http://bernd.eckenfels.net Von: mark.yagnatin...@barclays.com.INVALID Gesendet: Thursday, December 9, 2021 6:22:46 AM An: users@maven.apache.org Betreff: RE: request for documentation update about mirrors > But if you ins

RE: request for documentation update about mirrors

> But if you insist, I heared you can remove the blocked tag in your maven/conf > settings.. ;) But I can't, right? I'd have edit the global settings file bundled with maven itself. Or no? _

Re: request for documentation update about mirrors

documentation update about mirrors I hope this is the right mailing list; if I not, would appreciate a redirect. In the release notes for maven 3.8.1, here: https://maven.apache.org/docs/3.8.1/release-notes.html There is a helpfully titled section "How to fix when I get a HTTP repository bl

Re: request for documentation update about mirrors

It sounds like you have multiple repositories defined on same nexus instance. This is similar to setup we have. We have repositories for third party libraries we use as well as a mirror of maven central for the stuff we need. Key difference between the setup you have and my setup is we have on

Re: request for documentation update about mirrors

I can't speak to your question about disabling the https requirement, though my guess is that will be impossible and/or unpopular, likely by design. If you could just turn it off, some people would just turn it off, which defeats the purpose. The root of my questions is that if your Nexus is confi

RE: request for documentation update about mirrors

Sorry for broken threading; I wasn't subscribed to the mailing list so I never got your reply; not sure how to fix it now. Now I'm subscribed. Yes, we are using nexus. One of our nexus servers is even using HTTPS. The rest are not. As for why we have "many" ... I'm not entirely sure. It was

Re: request for documentation update about mirrors

d section "How to fix when I get a HTTP > repository blocked?" > > https://maven.apache.org/docs/3.8.1/release-notes.html#how-to-fix-when-i-get-a-http-repository-blocked > It mentions 2 options: > > * Update to a newer version of the artifact you're fetchi

request for documentation update about mirrors

e.org/docs/3.8.1/release-notes.html#how-to-fix-when-i-get-a-http-repository-blocked It mentions 2 options: * Update to a newer version of the artifact you're fetching, which is presumably available over https * Define a mirror in your settings, which links to this page: https://m

Re: Best practice to update dependency versions for *many* projects to the current version

unning the POM per application rather than > > > some global singular POM, since you should retain the ability to > > > update a single application's dependencies without breaking other > > > applications' behavior. I agree that this approach is the more time >

Re: Best practice to update dependency versions for *many* projects to the current version

; You might be interested in running the POM per application rather than > > some global singular POM, since you should retain the ability to > > update a single application's dependencies without breaking other > > applications' behavior. I agree that this approach is the more

Re: Best practice to update dependency versions for *many* projects to the current version

wrote: > You might be interested in running the POM per application rather than > some global singular POM, since you should retain the ability to > update a single application's dependencies without breaking other > applications' behavior. I agree that this approach is the more t

Re: Best practice to update dependency versions for *many* projects to the current version

Another way of doing this is with automation. There are various tools that update a dependency, run the build and create a PR (or automerge). If you are using Github, you can take a look at dependabot, but if you use standalone tools (like bitbucket and Jenkins) you can look at renovate. With

Re: Best practice to update dependency versions for *many* projects to the current version

You might be interested in running the POM per application rather than some global singular POM, since you should retain the ability to update a single application's dependencies without breaking other applications' behavior. I agree that this approach is the more time consuming than h

Re: Best practice to update dependency versions for *many* projects to the current version

Another option is creating an artifact of type ‘pom’ that consists of just a pom.xml with a section and optionally properties for the versions (so they can easily be overridden when needed), and importing this BOM (bill of materials) artifact in your applications. See spring-boot-dependencies

Re: Best practice to update dependency versions for *many* projects to the current version

Hi Bruno, You can define a property in a project all projects inherit from 3.2.4 Then add a dependencyManagement section that sections the version cglib cglib ${dep.cglib.cglib} And use this plugin to check for updates etc https://www.mojohaus.org/vers

Best practice to update dependency versions for *many* projects to the current version

I have been developing in Java almost from the beginning, but have not used Maven for much more than a few personal test apps. I am now about to migrate nearly 100 applications to Maven and I am a bit concerned about how to manage dependency versions across that many projects in the future. F

Fwd: [versions-maven-plugin] how to update version property in pom.xml?

reactor dependency: com.***.example:submodtest:jar:1.1.1-SNAPSHOT [INFO] Ignoring com.***.example:afeaturemod:jar:[1.3.0] as the version number is too short [INFO] Incremental version changes allowed How to update the property for next snapshots? ref: https://www.mojohaus.org/versions-maven-plugin

Re: Unable to update version for provided transient dependencies

in their way. On Thu, May 28, 2020 at 1:41 PM Mitchell Rathbun (BLOOMBERG/ 731 LEX) < mrathb...@bloomberg.net> wrote: > We are currently using Storm 1.2.3, and we want to update the version of > log4j2 being used. In our Maven file, we specify storm-core with version > 1.2.3 and

Unable to update version for provided transient dependencies

We are currently using Storm 1.2.3, and we want to update the version of log4j2 being used. In our Maven file, we specify storm-core with version 1.2.3 and provided scope. This dependency has dependencies on log4j-api, log4j-core, slf4j-log4j-impl, etc. The provided version of these

Re: mvn versions:display-plugin-updates says I can update from 3 to 2

Thanks! I finally tried looking at this. This works for me. Side note: We use the enforcer plugin only when we enable a certain profile because of MENFORCER-306. We can't downgrade before that defect because of MENFORCER-268. 306 is fixed in 3.0.0-M3, which is not in Maven Central yet. I forgot to

Re: mvn versions:display-plugin-updates says I can update from 3 to 2

Technically you didn't do anything wrong... If you don't configure what version of java and maven your project requires, then versions will tell you about all options available. So that is saying if you want users to build using maven 2.0.1 then the maven-war-plugin needs to be 2.0.2. If you add

mvn versions:display-plugin-updates says I can update from 3 to 2

Did I do something wrong? $ mvn versions:display-plugin-updates ... [INFO] Require Maven 2.0.1 to use the following plugin updates: [INFO] maven-war-plugin ... 3.2.3 -> 2.0.2 -- Jason Young

Update to the new Maven wrapper

Hi all, Just wanted to give you a heads up about the recent Maven wrapper and plugin releases. https://www.simpligility.com/2019/03/recent-maven-wrapper-updates/ Some pretty nice features worth checking out imho. Go update your projects to this latest version! Manfred

Re: Supporting custom "Scopes" and Maven support for "Non-Java" languages (WAS: Re: Any update on "polyglot" Maven?)

I don't have all the details, but on static vs dynamic libs, static libs are classical dependencies from a Maven point of view, ie. downloaded from the repository and added to something like a classpath, where dynamic libs are classically managed by the distribution's package manager: I don't kn

Re: Supporting custom "Scopes" and Maven support for "Non-Java" languages (WAS: Re: Any update on "polyglot" Maven?)

Hi Herve, well I know for example that I have some libraries, that are statically linked and some expect libraries to be installed on the host system. I had the exact same problem with Flex in the past ... here I could also have dynamically linked versions of libraries, then I had to also refere

Re: Supporting custom "Scopes" and Maven support for "Non-Java" languages (WAS: Re: Any update on "polyglot" Maven?)

let's try to dig into your requirements instead of trying to explain generic mechanisms, can you provide some concrete C++ examples, please? Regards, Hervé Le lundi 7 janvier 2019, 14:23:48 CET Christofer Dutz a écrit : > Hi Hervé, > > thanks for that info ... I adjusted the topic to distingu

Supporting custom "Scopes" and Maven support for "Non-Java" languages (WAS: Re: Any update on "polyglot" Maven?)

Hi Hervé, thanks for that info ... I adjusted the topic to distinguish from the other topic :) Well I first ran into problems when taking over the maintenance of the Flexmojos maven plugin, which allowed building Flex applications with maven. A while ago a "bug" was fixed, which that plugin rel

Re: Any update on "polyglot" Maven?

Hi Christofer, I know C/C++ people who used nar-maven-plugin [1] with success: did you have a look? Notice: in Maven, "polyglot" term has always been used for other POM format than XML. Here, it's more on Maven support for non-java languages One key requirement in such multi-languages context

Any update on "polyglot" Maven?

Hi all, after leaving the Flex project I sort of lost the need for supporting alternate dependency strategies. Now in PLC4X we’re currently starting to work on the C and C++ versions of our PLC drivers. This brings the old problem up again that not all programming languages have the same super-

Re: Default update policy for plugin repositories is never?

sed. Best, Laird On Mon, Oct 2, 2017 at 12:19 PM Tom Golden wrote: > Wondering if someone can link me to some explicit documentation around the > update policy for plugin repositories. > > I ran into an issue today with our CI server where one build would use a > particularly old v

Default update policy for plugin repositories is never?

Wondering if someone can link me to some explicit documentation around the update policy for plugin repositories. I ran into an issue today with our CI server where one build would use a particularly old version of the sonar-maven-plugin. I eventually realized after some digging that it was due

Re: Update non-unique snapshots from Artifactory to local repository

Am Tue, 21 Jul 2015 23:00:12 +0300 schrieb Alex Ditu : > I am not sure if it > is a specific artifactory issue, I found this: > https://www.jfrog.com/jira/browse/RTFACT-5404 if it helps Yes, if the repo does not provide the timestamps, then the policy wont work. You can purge your snapshots local

Re: Update non-unique snapshots from Artifactory to local repository

Hello, not sure if you are asking about the general handling or a specific problem with Artifactory. But with mvn you can use the -U switch to force a snapshot update. Otherwise it will use the updatePolicy from your settings.xml (I think "daily" would be the default for snapshots rep

Update non-unique snapshots from Artifactory to local repository

Hello, I am new to maven and do not know how to solve this issue: I decided not to keep timestampped artifacts in Aritfactory but now maven is not downloading newer artifacts from Artifactory, although in metadata the versions differ. I do not want to manually delete my local copy of an artifact

IndexingContext.getSize() update

no method like - update() ?? Only when I create new IndexingContext...the size is updated Has anybody better solution , then closing Indexing context and creating new one again? Thanks MB

AW: AW: Painless way to update a frameworks group id?

hagen [mailto:mfriedenha...@gmail.com] Gesendet: Samstag, 14. Dezember 2013 07:40 An: Maven Users List Betreff: Re: AW: Painless way to update a frameworks group id? Christofer, this depends on your definition of "we" :-). In a company context with an internal repository manager you

Re: AW: Painless way to update a frameworks group id?

safe > side :-( > > Chris > > -Ursprüngliche Nachricht- > Von: Mirko Friedenhagen [mailto:mfriedenha...@gmail.com] > Gesendet: Freitag, 13. Dezember 2013 21:26 > An: Maven Users List > Betreff: Re: Painless way to update a frameworks group id? > > Just a gues

AW: Painless way to update a frameworks group id?

on the safe side :-( Chris -Ursprüngliche Nachricht- Von: Mirko Friedenhagen [mailto:mfriedenha...@gmail.com] Gesendet: Freitag, 13. Dezember 2013 21:26 An: Maven Users List Betreff: Re: Painless way to update a frameworks group id? Just a guess: * Deploy a new relocation pom at the old

Re: Painless way to update a frameworks group id?

>> > >> Chris > >> > >> > >> > >> Von: anders.g.ham...@gmail.com im Auftrag > >> von Anders Hammar > >> Gesendet: Donnerstag, 12. Dezember 2013 11:37 > >> An: Maven Users List

Re: Painless way to update a frameworks group id?

___ >> Von: anders.g.ham...@gmail.com im Auftrag >> von Anders Hammar >> Gesendet: Donnerstag, 12. Dezember 2013 11:37 >> An: Maven Users List >> Betreff: Re: Painless way to update a frameworks group id? >> >> I don&#x

Re: Painless way to update a frameworks group id?

component guiding users on how to > use the plugin) > > Chris > > > > Von: anders.g.ham...@gmail.com im Auftrag von > Anders Hammar > Gesendet: Donnerstag, 12. Dezember 2013 11:37 > An: Maven Users List > Betreff: Re: Painless way to update a frameworks group id?

AW: Painless way to update a frameworks group id?

d really like to implement some validator and "best-practice" validator component guiding users on how to use the plugin) Chris Von: anders.g.ham...@gmail.com im Auftrag von Anders Hammar Gesendet: Donnerstag, 12. Dezember 2013 11:37 An:

Re: Painless way to update a frameworks group id?

ies for the good > artifacts, the "exclude" entries are automatically in place. > > Chris > > > > Von: anders.g.ham...@gmail.com im Auftrag von > Anders Hammar > Gesendet: Donnerstag, 12. Dezember 2013 11:07 > An: Mave

AW: Painless way to update a frameworks group id?

de" entries are automatically in place. Chris Von: anders.g.ham...@gmail.com im Auftrag von Anders Hammar Gesendet: Donnerstag, 12. Dezember 2013 11:07 An: Maven Users List Betreff: Re: Painless way to update a frameworks group id? AFAIK there is

Re: Painless way to update a frameworks group id?

AFAIK there is not painless way to solve this. What you could add to the docs is instructions on how to use an enforcer rule to ensure that no "bad" libs are pulled in by accident (if the miss some exclusion). Use the banned deps [1] rule. /Anders [1] http://maven.apache.org/enforcer/enforcer-ru

Painless way to update a frameworks group id?

Hi, I am the current maintainer of the Flexmojos Maven Plugin and contributor to the Apache Flex Project. Currently I am working on a new Version of Flexmojos which is able to work with Flex SDKs that have a groupId of org.apache.flex instead of the old com.adobe.flex. While building applica

RE: AW: AW: AW: mvn release:prepare does not update parent version

> Date: Sat, 9 Nov 2013 08:31:21 -0500 > Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version > From: gordon.c...@zafin.com > To: users@maven.apache.org > > You may want to upgrade maven itself once more. It is not just maven itself > but the c

Re: AW: AW: AW: mvn release:prepare does not update parent version

a JIRA issue would help. Robert [1] https://jira.codehaus.org/browse/MRELEASE-511 Op Sat, 09 Nov 2013 14:17:57 +0100 schreef Martin Gainty : From: k...@quipsy.de To: users@maven.apache.org Date: Fri, 8 Nov 2013 16:30:30 +0100 Subject: AW: AW: AW: mvn release:prepare does not update par

Re: AW: AW: AW: mvn release:prepare does not update parent version

Message- > From: Robert Scholte [mailto:rfscho...@apache.org] > Sent: Freitag, 8. November 2013 18:52 > To: Maven Users List > Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version > > Op Fri, 08 Nov 2013 16:30:30 +0100 schreef Markus Karg : > > &g

RE: AW: AW: AW: mvn release:prepare does not update parent version

> From: k...@quipsy.de > To: users@maven.apache.org > Date: Fri, 8 Nov 2013 16:30:30 +0100 > Subject: AW: AW: AW: mvn release:prepare does not update parent version > > Martin, > > thank you for your explanations, but as it turned out the problem is fixed > si

RE: AW: AW: AW: mvn release:prepare does not update parent version

rt Scholte [mailto:rfscho...@apache.org] Sent: Freitag, 8. November 2013 18:52 To: Maven Users List Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version Op Fri, 08 Nov 2013 16:30:30 +0100 schreef Markus Karg : > I wonder why someone fixed it but didn

Re: AW: AW: AW: mvn release:prepare does not update parent version

must first be reproducible. That's why attaching a sample project helps, and a patch with a possible fix even more. In this case it was the log-file which triggered me: first update the version of the plugin and see if it has been already been fixed. It is all about being as complete a

AW: AW: AW: mvn release:prepare does not update parent version

Martin, thank you for your explanations, but as it turned out the problem is fixed simply by using version 2.4.2 of the release plugin. I wonder why someone fixed it but didn't close https://jira.codehaus.org/browse/MRELEASE-837...! Thanks for all -Markus

RE: AW: AW: mvn release:prepare does not update parent version

> From: k...@quipsy.de > To: users@maven.apache.org > Date: Fri, 8 Nov 2013 08:40:56 +0100 > Subject: AW: AW: mvn release:prepare does not update parent version > > Martin, > > thanks for your ideas, but... > > > I agree that the docs do not say anything

AW: AW: mvn release:prepare does not update parent version

Martin, thanks for your ideas, but... >MG the previous email was an attempt to explain prepare-mojo will update >current or children artifacts but not parent artifacts I agree that the docs do not say anything about the parent, but my question is not about the docs, it is about this qu

RE: AW: mvn release:prepare does not update parent version

> From: k...@quipsy.de > To: users@maven.apache.org > Date: Thu, 7 Nov 2013 17:11:32 +0100 > Subject: AW: mvn release:prepare does not update parent version > > Sorry for the really long delay, but there had been several urgent projects > meanwhile. > > I

AW: mvn release:prepare does not update parent version

OM reference to be replaced by 1.0 and later by 1.1-SNAPSHOT, and I said YES (which is the default). But in the end, it still is referenced as 1.0-SNAPSHOT, while it certainly must be 1.1-SNAPSHOT instead! Thanks! -Markus -Ursprüngliche Nachricht- Von: Russell Gold [mailto:r...@gold-family.u

Re: mvn release:prepare does not update parent version

Gesendet: Dienstag, 23. Juli 2013 23:24 > An: users@maven.apache.org > Betreff: RE: mvn release:prepare does not update parent version > > Markus > > > Pa

AW: mvn release:prepare does not update parent version

Gesendet: Dienstag, 23. Juli 2013 23:24 An: users@maven.apache.org Betreff: RE: mvn release:prepare does not update parent version Markus Parent.pom |

RE: mvn release:prepare does not update parent version

--- | | v v Child11.pom Child12.pom can you envision a scenario where release plugin should break inheritance and update Parent instead of child s ? Martin

Re: mvn release:prepare does not update parent version

Greetings, On Tue, Jul 23, 2013 at 7:45 AM, Markus Karg wrote: > But why is release:prepare explicitly asking me whether I want to update that > number and what that number is, when it is intended behaviour that it does > not actually set that number into the POM? I would understand

AW: mvn release:prepare does not update parent version

But why is release:prepare explicitly asking me whether I want to update that number and what that number is, when it is intended behaviour that it does not actually set that number into the POM? I would understand all what you say if the plugin would not ask for the next development version of

AW: mvn release:prepare does not update parent version

You don't get my point. My problem is that the plugin asks me to provide the version to set for the tag, but it actually does not use it. This is what I complain about, solely. I don't want to update anything else. -Ursprüngliche Nachricht- Von: christofer.d...

RE: mvn release:prepare does not update parent version

re.de] Envoyé : mardi 23 juillet 2013 10:10 À : Maven Users List Objet : AW: mvn release:prepare does not update parent version Hi, is there actually a reason why only the artifacts in the build are updated? I would agree that without providing versions for artifacts manually, this could cause pro

Re: mvn release:prepare does not update parent version

also ones not in the reactor), but the release:prepare simply skipped those > not in the build. > I had to create a patched version for this, but it was a pretty unsatisfying > solution. If the plugin would for example update all those versions in the > reactor plus all those I m

AW: mvn release:prepare does not update parent version

, but it was a pretty unsatisfying solution. If the plugin would for example update all those versions in the reactor plus all those I manually provided a version for, might solve Markus' problems. Chris -Ursprüngliche Nachricht- Von: jieryn [mailto:jie...@gmail.com] Gesendet: M

RE: mvn release:prepare does not update parent version

Thanks for picking this up. Please find answers inlined. :-) > > When I do mvn release:prepare, Maven asks whether I want to update > all > > SNAPSHOT version referenced in the POM. > > I don't think the language says that at all. I ran a quick build and > I'

RE: mvn release:prepare does not update parent version

e...: > > > > When I do mvn release:prepare, Maven asks whether I want to update > all > > SNAPSHOT version referenced in the POM. > > I say "yes" and confirm all suggested replacement versions unchanged. > > When Maven is done, I check the POM.xml. > &

Re: mvn release:prepare does not update parent version

Greetings, On Mon, Jul 22, 2013 at 8:25 AM, Markus Karg wrote: > When I do mvn release:prepare, Maven asks whether I want to update all > SNAPSHOT version referenced in the POM. I don't think the language says that at all. I ran a quick build and I'm not seeing where it say

Re: mvn release:prepare does not update parent version

Hi, which version of Maven and Maven-Release-Plugin are you using? On Mon, Jul 22, 2013 at 9:25 AM, Markus Karg wrote: > I'm driving nuts with mvn release:prepare...: > > When I do mvn release:prepare, Maven asks whether I want to update all > SNAPSHOT version referenced in

mvn release:prepare does not update parent version

I'm driving nuts with mvn release:prepare...: When I do mvn release:prepare, Maven asks whether I want to update all SNAPSHOT version referenced in the POM. I say "yes" and confirm all suggested replacement versions unchanged. When Maven is done, I check the POM.xml. It is correctl

Antwort: mvn release:prepare does not update parent version

Hi Markus using "mvn release:prepare -DautoVersionSubmodules=true" should solve your problem. Greetz, Sandra Von:"Markus Karg" An: , Datum: 22.07.2013 09:47 Betreff:mvn release:prepare does not update parent version I'm driving nuts

mvn release:prepare does not update parent version

I'm driving nuts with mvn release:prepare...: When I do mvn release:prepare, Maven asks whether I want to update all SNAPSHOT version referenced in the POM. I say "yes" and confirm all suggested replacement versions unchanged. When Maven is done, I check the POM.xml.

Maven Deploy Plugin and Nexus Meta Data update of LATEST failing

Hi all, I've upgraded to the latest maven deploy plugin and hte latest nexus OSS version. I hoped that between the two that the updating of the LATEST meta-data would work when doing a relase (See http://stackoverflow.com/questions/4878808/maven-metadata-xml-is-not-updated-when-deploying-to-nexus

Re: Maven versions plugin: update property to specific value possible?

in a profile you could define the configuration for the plugin and specify the `properties` (see http://mojo.codehaus.org/versions-maven-plugin/update-properties-mojo.html#properties) and then reference another property to define the range of valid values. really rather hacky if you ask me

Maven versions plugin: update property to specific value possible?

Hi, I have found the mvn versions:update-properties target. mvn versions:update-properties -DincludeProperties={dependency1.version} However, the value being set is the last version for the specific dependency. Is it possible to specify the value for that property? i.e. something like the foll

Re: org.codehaus.mojo:versions-maven-plugin:2.0:update-properties

On 8 May 2013 22:27, Stephen Connolly wrote: > On 8 May 2013 20:28, Thomas Sundberg wrote: > >> On 8 May 2013 21:13, Wayne Fay wrote: >> >> It works well for artifacts in Nexus that was deployed from Maven. >> >> Unfortunately, we have some artifacts that consist of zip files and >> >> has been

Re: org.codehaus.mojo:versions-maven-plugin:2.0:update-properties

On 8 May 2013 21:50, Wayne Fay wrote: >> The files are uploaded to the Nexus server and are expected to be >> downloaded from it as well. If the maven-metadata is updated properly >> or not is something I need to check. > > OK... but HOW is that happening? "mvn deploy:deploy-file" or another > sim

Re: org.codehaus.mojo:versions-maven-plugin:2.0:update-properties

On 8 May 2013 20:28, Thomas Sundberg wrote: > On 8 May 2013 21:13, Wayne Fay wrote: > >> It works well for artifacts in Nexus that was deployed from Maven. > >> Unfortunately, we have some artifacts that consist of zip files and > >> has been generated from an Ant build. > > > > I assume the plu

  1   2   3   4   5   6   7   >