Re: Not a local repository. It is a local repository cache. (was: Fwd: Why Is Maven Ignoring My Local Repo?)
I also think that installing locally is somehow to be seen as a hack. And though I do it myself on a regular basis while developing, I indeed never see it as a sustainable place for my artifacts, only deploy is (and still temporary for non releases). Yes, I think we should rename that tag. And if not we should stop telling people it must not be seen as a repository, but as a cache... Le 15 avr. 2014 11:32, Igor Fedorenko i...@ifedorenko.com a écrit : localRepository currently works as both a cache or artifacts from remote repositories and as a repository of locally installed artifacts. Do you suggest we get rid of locally installed functionality (which I personally very much in favour) or you want to just change the name (which I think will be confusing)? -- Regards, Igor On 2014-04-15, 4:53, Baptiste Mathus wrote: Hi all, Wondering, though not strictly 4.0.0 restricted, shouldn't a decision be made about that vocabulary and reflect this in the docs and settings.xml tags and so on? I mean, I myself often explain it's not really a local repo, more a cache, but the tag names and the docs makes it hard to spread the word. In settings.xml : localRepository could be renamed to localCache or localRepositoryCache ? In the docs, e.g. https://maven.apache.org/pom.html there're many references to a local repository. WDYT? Cheers -- Forwarded message -- From: Stephen Connolly stephen.alan.conno...@gmail.com Date: 2014-04-15 10:12 GMT+02:00 Subject: Re: Why Is Maven Ignoring My Local Repo? To: Maven Users List us...@maven.apache.org It's not a local repository. It is a local repository cache. There are files there that record where the artifacts were cached *from*. If the artifact is there but the cache file is not or indicates a different source from the allowed sources for your build, then Maven will ignore the artifact in your cache and check the remote sources. On 15 April 2014 02:02, Eric Kolotyluk e...@kolotyluk.net wrote: I seem to keep running into this problem regularly for things not in Maven Central [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project csharp-windows-elevate: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.3:site failed: Plugin org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could not be resolved: Could not find artifact net.trajano.wagon:wagon-git:jar:1.0.1-SNAPSHOT in local-nexus (http://localhost:8081/nexus/content/groups/public) - [Help 1] I can see the artifact in my local repo, but maven somehow feels, because it cannot find it in my nexus repository, then it does not exist. The side problem is, even though nexus can see the artifact in its index, it refuses to download it. Why do maven and nexus work so hard at ignoring artifacts? Cheers, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12.1
+1 14. Apr. 2014 23:15 skrev Dennis Lundberg denn...@apache.org følgende: Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=20236styleName=Html There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1020 https://repository.apache.org/service/local/repositories/maven-1020/content/org/apache/maven/plugins/maven-checkstyle-plugin/2.12.1/maven-checkstyle-plugin-2.12.1-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.12.1-source-release.zip sha1: ed95a8b5a13190b1e6095b754365766b1aa3989a Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12.1
+1 On 14 April 2014 22:14, Dennis Lundberg denn...@apache.org wrote: Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=20236styleName=Html There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1020 https://repository.apache.org/service/local/repositories/maven-1020/content/org/apache/maven/plugins/maven-checkstyle-plugin/2.12.1/maven-checkstyle-plugin-2.12.1-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.12.1-source-release.zip sha1: ed95a8b5a13190b1e6095b754365766b1aa3989a Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Not a local repository. It is a local repository cache. (was: Fwd: Why Is Maven Ignoring My Local Repo?)
I don't understand the issue. I regularly use artifacts in my build that are only present in my local repository. Yes, Maven checks my remote repository for these artifacts but it doesn't ignore them if they are not in the remote repo. It also works when building offline without access to my remote repository. Is it treated as a cache, maybe so but it's not clear to me that renaming the tag won't serve to add more confusion to a long-standing behavior... Clearly, removing the ability to install artifacts locally would be a very bad idea since it would make it more difficult for casual users to use Maven for casual builds (e.g., I regularly use it to build sample projects for customers that I never intend to do anything else with once I send it to the customer). Just my two cents, Robert Robert Patrick robert.patr...@oracle.com VP, FMW Platform Architecture Oracle Mobile: +1 469 556 9450 Sent from my iPad On Apr 17, 2014, at 1:54 AM, Baptiste Mathus bmat...@batmat.net wrote: I also think that installing locally is somehow to be seen as a hack. And though I do it myself on a regular basis while developing, I indeed never see it as a sustainable place for my artifacts, only deploy is (and still temporary for non releases). Yes, I think we should rename that tag. And if not we should stop telling people it must not be seen as a repository, but as a cache... Le 15 avr. 2014 11:32, Igor Fedorenko i...@ifedorenko.com a écrit : localRepository currently works as both a cache or artifacts from remote repositories and as a repository of locally installed artifacts. Do you suggest we get rid of locally installed functionality (which I personally very much in favour) or you want to just change the name (which I think will be confusing)? -- Regards, Igor On 2014-04-15, 4:53, Baptiste Mathus wrote: Hi all, Wondering, though not strictly 4.0.0 restricted, shouldn't a decision be made about that vocabulary and reflect this in the docs and settings.xml tags and so on? I mean, I myself often explain it's not really a local repo, more a cache, but the tag names and the docs makes it hard to spread the word. In settings.xml : localRepository could be renamed to localCache or localRepositoryCache ? In the docs, e.g. https://maven.apache.org/pom.html there're many references to a local repository. WDYT? Cheers -- Forwarded message -- From: Stephen Connolly stephen.alan.conno...@gmail.com Date: 2014-04-15 10:12 GMT+02:00 Subject: Re: Why Is Maven Ignoring My Local Repo? To: Maven Users List us...@maven.apache.org It's not a local repository. It is a local repository cache. There are files there that record where the artifacts were cached *from*. If the artifact is there but the cache file is not or indicates a different source from the allowed sources for your build, then Maven will ignore the artifact in your cache and check the remote sources. On 15 April 2014 02:02, Eric Kolotyluk e...@kolotyluk.net wrote: I seem to keep running into this problem regularly for things not in Maven Central [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project csharp-windows-elevate: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.3:site failed: Plugin org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could not be resolved: Could not find artifact net.trajano.wagon:wagon-git:jar:1.0.1-SNAPSHOT in local-nexus (http://localhost:8081/nexus/content/groups/public) - [Help 1] I can see the artifact in my local repo, but maven somehow feels, because it cannot find it in my nexus repository, then it does not exist. The side problem is, even though nexus can see the artifact in its index, it refuses to download it. Why do maven and nexus work so hard at ignoring artifacts? Cheers, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Not a local repository. It is a local repository cache. (was: Fwd: Why Is Maven Ignoring My Local Repo?)
ROBERT PATRICK wrote: I don't understand the issue. I regularly use artifacts in my build that are only present in my local repository. Yes, Maven checks my remote repository for these artifacts but it doesn't ignore them if they are not in the remote repo. It also works when building offline without access to my remote repository. Is it treated as a cache, maybe so but it's not clear to me that renaming the tag won't serve to add more confusion to a long-standing behavior... Clearly, removing the ability to install artifacts locally would be a very bad idea since it would make it more difficult for casual users to use Maven for casual builds (e.g., I regularly use it to build sample projects for customers that I never intend to do anything else with once I send it to the customer). A remote repository is specified with an URL. Nobody prevents you from using a file URL i.e. having a real local repository on your disk. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Not a local repository. It is a local repository cache. (was: Fwd: Why Is Maven Ignoring My Local Repo?)
My problem with current behaviour is that the same location is used as both cache for remote artifacts and repository for locally installed artifacts. I think a cleaner model is to separate the two. It will still be possible to install locally, although I am not sure we'll need separate install phase. -- Regards, Igor On 2014-04-17, 7:13, ROBERT PATRICK wrote: I don't understand the issue. I regularly use artifacts in my build that are only present in my local repository. Yes, Maven checks my remote repository for these artifacts but it doesn't ignore them if they are not in the remote repo. It also works when building offline without access to my remote repository. Is it treated as a cache, maybe so but it's not clear to me that renaming the tag won't serve to add more confusion to a long-standing behavior... Clearly, removing the ability to install artifacts locally would be a very bad idea since it would make it more difficult for casual users to use Maven for casual builds (e.g., I regularly use it to build sample projects for customers that I never intend to do anything else with once I send it to the customer). Just my two cents, Robert Robert Patrick robert.patr...@oracle.com VP, FMW Platform Architecture Oracle Mobile: +1 469 556 9450 Sent from my iPad On Apr 17, 2014, at 1:54 AM, Baptiste Mathus bmat...@batmat.net wrote: I also think that installing locally is somehow to be seen as a hack. And though I do it myself on a regular basis while developing, I indeed never see it as a sustainable place for my artifacts, only deploy is (and still temporary for non releases). Yes, I think we should rename that tag. And if not we should stop telling people it must not be seen as a repository, but as a cache... Le 15 avr. 2014 11:32, Igor Fedorenko i...@ifedorenko.com a écrit : localRepository currently works as both a cache or artifacts from remote repositories and as a repository of locally installed artifacts. Do you suggest we get rid of locally installed functionality (which I personally very much in favour) or you want to just change the name (which I think will be confusing)? -- Regards, Igor On 2014-04-15, 4:53, Baptiste Mathus wrote: Hi all, Wondering, though not strictly 4.0.0 restricted, shouldn't a decision be made about that vocabulary and reflect this in the docs and settings.xml tags and so on? I mean, I myself often explain it's not really a local repo, more a cache, but the tag names and the docs makes it hard to spread the word. In settings.xml : localRepository could be renamed to localCache or localRepositoryCache ? In the docs, e.g. https://maven.apache.org/pom.html there're many references to a local repository. WDYT? Cheers -- Forwarded message -- From: Stephen Connolly stephen.alan.conno...@gmail.com Date: 2014-04-15 10:12 GMT+02:00 Subject: Re: Why Is Maven Ignoring My Local Repo? To: Maven Users List us...@maven.apache.org It's not a local repository. It is a local repository cache. There are files there that record where the artifacts were cached *from*. If the artifact is there but the cache file is not or indicates a different source from the allowed sources for your build, then Maven will ignore the artifact in your cache and check the remote sources. On 15 April 2014 02:02, Eric Kolotyluk e...@kolotyluk.net wrote: I seem to keep running into this problem regularly for things not in Maven Central [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project csharp-windows-elevate: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.3:site failed: Plugin org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could not be resolved: Could not find artifact net.trajano.wagon:wagon-git:jar:1.0.1-SNAPSHOT in local-nexus (http://localhost:8081/nexus/content/groups/public) - [Help 1] I can see the artifact in my local repo, but maven somehow feels, because it cannot find it in my nexus repository, then it does not exist. The side problem is, even though nexus can see the artifact in its index, it refuses to download it. Why do maven and nexus work so hard at ignoring artifacts? Cheers, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:
Re: Intended use of properties in the version element
I'd like to arrange a system in which the automated builds stamp out
releases (in the Maven sense), but that developers can use the usual
IDE and command-line builds when just building on their particular
machine at some particular instant. So I'd like to spare developers
from 'passing in the version always.' The device discussed in your
last paragraph could undoubtedly use some environmental hint to tell
that it's just a dev's machine and either fill in a very unique
qualifier or just use a snapshot.
On Tue, Apr 15, 2014 at 12:09 PM, Jason van Zyl ja...@takari.io wrote:
For the continuous delivery friendly versions I saw an issue in JIRA as well
that tried to use snapshots.
The version is always a release version, not a snapshot. Snapshots are
definitively not CD friendly. In the system I'm working on that currently
uses this feature it is always a Perforce changelist which is the version.
All artifacts get deployed with this version. This is getting close, but we
don't use snapshots or the release plugin which is the way I believe things
will evolve in the Maven ecosystem. This is the generations stuff I've
mentioned and while it is working in production right now, it's not complete
but I'll likely have all the edge cases worked out in a few months.
So the theory is with this mechanism that the release version is passed in
externally always. I have another method I'm working on which is to have
something like x.y.z.qualifier where the magic happens in the
maven-aether-provider to do the necessary transformation based on the system
you're running in: Git, P4, whatever.
What are you trying to do? I can explain more if I know what you're playing
with.
On Apr 15, 2014, at 10:19 AM, Benson Margulies bimargul...@gmail.com wrote:
I've been thinking about how to exploit the 3.2.1 feature of
version${something}/version
My idea is that an ordinary developer would end up with 'something'
defined to be a good, old, -SNAPSHOT, while various automated builds
would define it based on git commits.
Is is intended that a POM could declare
something44-SNAPSHOT/something
and then have the command-line override with -Dsomething=SOMETHING-else?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-
A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.
-- Jakob Burckhardt
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Not a local repository. It is a local repository cache. (was: Fwd: Why Is Maven Ignoring My Local Repo?)
Am Thu, 17 Apr 2014 07:43:13 -0400 schrieb Igor Fedorenko i...@ifedorenko.com: My problem with current behaviour is that the same location is used as both cache for remote artifacts and repository for locally installed artifacts. Actually I agree, it would be good to have a real cache which is 1:1 existing for each defined remote repo, and the default local repo, which only contains stuff you installed in. This would also reduce checksum conflicts, avoids the special from where is it properties and allows to more selectively purge cache content (by deleting for example only the cache of the 'snapshot-repo') (But I guess this would slow down searching/resolution?) Bernd - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Not a local repository. It is a local repository cache. (was: Fwd: Why Is Maven Ignoring My Local Repo?)
Am Thu, 17 Apr 2014 13:40:38 +0200 schrieb Jörg Schaible joerg.schai...@swisspost.com: Clearly, removing the ability to install artifacts locally would be a very bad idea since it would make it more difficult for casual users to use Maven for casual builds (e.g., I regularly use it to build sample projects for customers that I never intend to do anything else with once I send it to the customer). A remote repository is specified with an URL. Nobody prevents you from using a file URL i.e. having a real local repository on your disk. Or using mvn verify and pick up the artifacts in target/ where they are easier to find anyway. (which does of course not work if multiple ad-hoc projects depend on each other) (This is BTW a personal pet peeve, any idea why eclipse e2m offers some default targets but the verfiy (or at least package) goal is none of them.) Gruss Bernd - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12.1
+1 Regards, Hervé Le lundi 14 avril 2014 23:14:33 Dennis Lundberg a écrit : Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=202 36styleName=Html There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127sta tus=1 Staging repo: https://repository.apache.org/content/repositories/maven-1020 https://repository.apache.org/service/local/repositories/maven-1020/content/ org/apache/maven/plugins/maven-checkstyle-plugin/2.12.1/maven-checkstyle-plu gin-2.12.1-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.12.1-source-release.zip sha1: ed95a8b5a13190b1e6095b754365766b1aa3989a Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
