Displaying #maven/2016-11-29.log:

Tue Nov 29 00:30:25 2016  dmlloyd:Joined the channel
Tue Nov 29 00:32:59 2016  mischat:Joined the channel
Tue Nov 29 00:34:38 2016  mischat:Joined the channel
Tue Nov 29 00:58:11 2016  mischat:Joined the channel
Tue Nov 29 00:58:54 2016  mischat:Joined the channel
Tue Nov 29 00:59:45 2016  mischat:Joined the channel
Tue Nov 29 01:00:31 2016  mischat:Joined the channel
Tue Nov 29 01:01:21 2016  mischat:Joined the channel
Tue Nov 29 01:02:11 2016  mischat:Joined the channel
Tue Nov 29 01:02:55 2016  mischat:Joined the channel
Tue Nov 29 01:03:45 2016  mischat:Joined the channel
Tue Nov 29 01:04:31 2016  mischat:Joined the channel
Tue Nov 29 01:05:37 2016  mischat:Joined the channel
Tue Nov 29 02:06:05 2016  mischat:Joined the channel
Tue Nov 29 02:16:43 2016  pokEarl:Joined the channel
Tue Nov 29 02:40:20 2016  hboutemy:Joined the channel
Tue Nov 29 03:06:53 2016  mischat:Joined the channel
Tue Nov 29 03:19:20 2016  lefou:Joined the channel
Tue Nov 29 03:24:50 2016  jdcasey:Joined the channel
Tue Nov 29 04:07:35 2016  mischat:Joined the channel
Tue Nov 29 04:44:30 2016  hboutemy_:Joined the channel
Tue Nov 29 05:08:21 2016  mischat:Joined the channel
Tue Nov 29 05:11:07 2016  lithium:Joined the channel
Tue Nov 29 06:09:07 2016  mischat:Joined the channel
Tue Nov 29 07:06:27 2016  edvorg:Joined the channel
Tue Nov 29 07:09:38 2016  hboutemy:Joined the channel
Tue Nov 29 07:10:06 2016  mischat:Joined the channel
Tue Nov 29 07:30:50 2016  mischat:Joined the channel
Tue Nov 29 07:38:21 2016  jknetl:Joined the channel
Tue Nov 29 08:03:26 2016  Candle:Joined the channel
Tue Nov 29 08:05:31 2016  adac:Joined the channel
Tue Nov 29 08:18:55 2016  mischat:Joined the channel
Tue Nov 29 08:36:38 2016  vtunka:Joined the channel
Tue Nov 29 08:38:00 2016  PeErLesS:Joined the channel
Tue Nov 29 08:52:09 2016  TomyWork:Joined the channel
Tue Nov 29 08:59:32 2016  ppalaga:Joined the channel
Tue Nov 29 08:59:57 2016  vtunka:Joined the channel
Tue Nov 29 09:12:55 2016  lithium:Joined the channel
Tue Nov 29 09:21:54 2016  adac:Joined the channel
Tue Nov 29 09:32:03 2016  mischat:Joined the channel
Tue Nov 29 09:32:55 2016  mischat:Joined the channel
Tue Nov 29 09:34:46 2016  vtunka:Joined the channel
Tue Nov 29 09:48:39 2016  thc202:Joined the channel
Tue Nov 29 09:59:17 2016  vtunka:Joined the channel
Tue Nov 29 10:12:22 2016  metrixx:Joined the channel
Tue Nov 29 10:12:24 2016  metrixx:hi.
Tue Nov 29 10:13:38 2016  metrixx:how can i specify different pom files for local and remote settings?
Tue Nov 29 10:33:14 2016  pokEarl:Joined the channel
Tue Nov 29 11:06:59 2016  vtunka:Joined the channel
Tue Nov 29 11:57:48 2016  pokEarl:Joined the channel
Tue Nov 29 12:55:05 2016  synthroid:Joined the channel
Tue Nov 29 13:02:04 2016  lithium_:Joined the channel
Tue Nov 29 13:16:23 2016  mischat:Joined the channel
Tue Nov 29 13:25:17 2016  sobersocialist:Joined the channel
Tue Nov 29 13:30:15 2016  lefou:Joined the channel
Tue Nov 29 13:53:50 2016  mischat:Joined the channel
Tue Nov 29 14:00:44 2016  conan:Joined the channel
Tue Nov 29 14:00:54 2016  vtunka:Joined the channel
Tue Nov 29 14:30:45 2016  jsightler_:Joined the channel
Tue Nov 29 14:42:19 2016  Maxel:Joined the channel
Tue Nov 29 15:07:29 2016  jieryn:Joined the channel
Tue Nov 29 15:07:30 2016  jieryn:Joined the channel
Tue Nov 29 15:25:15 2016  Maxel:Joined the channel
Tue Nov 29 15:30:45 2016  csanchez:Joined the channel
Tue Nov 29 15:54:57 2016  csanchez:Joined the channel
Tue Nov 29 16:16:39 2016  hboutemy:Joined the channel
Tue Nov 29 16:16:42 2016  mischat:Joined the channel
Tue Nov 29 16:20:39 2016  PeErLesS:Joined the channel
Tue Nov 29 16:55:15 2016  Maxel:Joined the channel
Tue Nov 29 17:08:37 2016  jdcasey:Joined the channel
Tue Nov 29 17:20:20 2016  Maxel:Joined the channel
Tue Nov 29 17:31:42 2016  diogogmt:Joined the channel
Tue Nov 29 18:01:27 2016  sobersocialist1:Joined the channel
Tue Nov 29 18:08:38 2016  Maxel:Joined the channel
Tue Nov 29 18:11:40 2016  hjd:Joined the channel
Tue Nov 29 18:48:06 2016  lithium_:Joined the channel
Tue Nov 29 18:48:59 2016  Maxel:Joined the channel
Tue Nov 29 18:52:59 2016  Sasazuka:Joined the channel
Tue Nov 29 19:06:59 2016  lithium:Joined the channel
Tue Nov 29 19:11:56 2016  jugglinmike:Joined the channel
Tue Nov 29 19:15:36 2016  synthroid:Joined the channel
Tue Nov 29 19:18:21 2016  jdcasey:Joined the channel
Tue Nov 29 19:20:59 2016  jugglinmike:Hello, all
Tue Nov 29 19:21:03 2016  jugglinmike:I'm trying to formalize the dependencies of an existing code base, and I'm running into some problems
Tue Nov 29 19:21:08 2016  jugglinmike:I think I know what the problem is, but I'm new to Maven and would appreciate some verification
Tue Nov 29 19:21:11 2016  jugglinmike:That way, I'll know how to fix it :)
Tue Nov 29 19:21:16 2016  jugglinmike:Anyway, here is a simplified version of the project layout:
Tue Nov 29 19:21:35 2016  jugglinmike:project-A
Tue Nov 29 19:21:35 2016  jugglinmike: - pom.xml (defines a repository, `repo-A`)
Tue Nov 29 19:21:35 2016  jugglinmike: - subproject-1
Tue Nov 29 19:21:35 2016  jugglinmike: - pom.xml (defines a dependency on `project-B` hosted in `repo-A`)
Tue Nov 29 19:21:35 2016  jugglinmike:project-C
Tue Nov 29 19:21:35 2016  jugglinmike: - pom.xml (defines a dependency on `project-A-subproject-1`)
Tue Nov 29 19:21:45 2016  jugglinmike:After deploying `project-A` to a remote repository, I clear my local repository and attempt to build `project-C`
Tue Nov 29 19:21:50 2016  jugglinmike:This build fails because it is unable to locate `project-B`
Tue Nov 29 19:21:55 2016  jugglinmike:I think this is because during this build, Maven does not interpret `subproject-1`'s POM in the context of `project-A`'s POM
Tue Nov 29 19:22:01 2016  jugglinmike:Is that right?
Tue Nov 29 19:35:51 2016  hakvroot:jugglinmike: iirc any repository definitions are not inherited from a parent pom
Tue Nov 29 19:37:13 2016  hakvroot:jugglinmike: and for reference - https://maven.apache.org/pom.html#Inheritance
Tue Nov 29 19:39:58 2016  jugglinmike:Thanks, hakvroot! You're right--"repositories" is definitely not listed there
Tue Nov 29 19:40:32 2016  jugglinmike:so maybe the question I need to be asking is, "Why does `project-A` build at all?"
Tue Nov 29 19:48:20 2016  mischat:Joined the channel
Tue Nov 29 19:48:53 2016  hakvroot:jugglinmike: I'm currently having doubts whether the same rule applies for multi-module builds ;) - any chance there is a cached artifact of project-B in the localrepo on the machine where subproject-1 is built?
Tue Nov 29 19:49:50 2016  jugglinmike:For now, this is all happening on the same machine
Tue Nov 29 19:50:25 2016  jugglinmike:But I am regularly removing my ~/.m2/repository directory to simulate "clean" installation
Tue Nov 29 19:52:32 2016  jugglinmike:Hm.. It looks like the `pom.xml` in `project-A` *also* defines a dependency on `project-B`
Tue Nov 29 19:53:06 2016  hakvroot:is that under <dependencyManagement> by any chance?
Tue Nov 29 19:53:27 2016  hakvroot:jugglinmike: and sounds like you're already approaching stuff the clinical way, so that's good :P
Tue Nov 29 19:53:56 2016  jugglinmike:I haven't been considering dependencyManagement because I thought that only controlled the location assets were deployed to
Tue Nov 29 19:54:35 2016  hakvroot:you might be mixing that up with distributionManagement
Tue Nov 29 19:54:44 2016  jugglinmike:oh, you are correct
Tue Nov 29 19:56:02 2016  hakvroot:do you build your artifacts with `mvn clean package`?
Tue Nov 29 19:56:48 2016  jugglinmike:I've been building `project-A` with `mvn clean deploy`, and `project-C` with `mvn clean test`
Tue Nov 29 19:57:38 2016  jugglinmike:But yes, `project-A`'s pom.xml also defines a dependency on `project-B` in its <dependencyManagement> section
Tue Nov 29 19:58:11 2016  jugglinmike:So it may be that Maven can build `project-A` because it fetches `project-B` to satisfy the top-level POM. When it finds `subproject-1`'s dependency on `project-B`, it doesn't matter that `project-B` has no associated `repository`--Maven is able to locate that dependency locally
Tue Nov 29 19:59:27 2016  jugglinmike:...arg, sorry. I meant, "[...] it doesn't matter than [`subproject-1`] has no associated [...]"
Tue Nov 29 20:00:15 2016  jugglinmike:And it's not until `project-C` attempts to install `subproject-1` directly that this mis-configuration is appreciable
Tue Nov 29 20:01:10 2016  hakvroot:hehe, gotcha :) but I think everything under <dependencyManagement> is left alone until a matching artifact is being resolved ... so my guess would be that the multi-module project works correctly because the repository is inherited in that case (cannot find any doc clarifying that now atm though)
Tue Nov 29 20:03:37 2016  Maxel:Joined the channel
Tue Nov 29 20:03:54 2016  hakvroot:does a `mvn dependency:tree` shine any light on the issue with project-C?
Tue Nov 29 20:05:10 2016  jugglinmike:Nope. It fails with the same error
Tue Nov 29 20:06:13 2016  hakvroot:do you see anything special in the artifact inclusion for project-B in the project-A pom or the subproject-1 pom?
Tue Nov 29 20:06:28 2016  hakvroot:or is it your regular <groupId>/<artifactId>/<version> ?
Tue Nov 29 20:09:53 2016  jugglinmike:In both files, the <version> is defined in terms of a property from project-A's pom.xml
Tue Nov 29 20:10:11 2016  hakvroot:sounds a bit redundant but otherwise fine to me
Tue Nov 29 20:10:47 2016  jugglinmike:yeah--the error from building `project-C` specifies the expected version
Tue Nov 29 20:11:27 2016  hakvroot:either way, the, err, easy answer is probably that it fails because project-C depends on project-B (but just not explicitly)
Tue Nov 29 20:12:32 2016  jugglinmike:I'm not trying to argue semantics here, but I want to make sure I understand:
Tue Nov 29 20:12:56 2016  jugglinmike:I would say, "just not directly" -- the dependency seems explicit to me
Tue Nov 29 20:13:55 2016  Maxel:Joined the channel
Tue Nov 29 20:14:42 2016  hakvroot:yeah, that's probably a better way to describe it
Tue Nov 29 20:14:52 2016  jugglinmike:It's starting to seem like the answer is, "include a reference to `repo-A` in `project-C`'s pom.xml"
Tue Nov 29 20:14:59 2016  hakvroot:it maven lingo those are called transitive dependencies btw
Tue Nov 29 20:15:06 2016  hakvroot:in*
Tue Nov 29 20:15:07 2016  Maxel:Joined the channel
Tue Nov 29 20:15:12 2016  jugglinmike:ah, yeah. I've been reading about that, too
Tue Nov 29 20:15:58 2016  hakvroot:and correct... or alternatively you configure your environment to include that repository
Tue Nov 29 20:16:19 2016  jugglinmike:but that seems like it violates the goal of transitive dependency resolution--as a consumer, I shouldn't have to know anything about the dependencies of my dependencies
Tue Nov 29 20:17:11 2016  jugglinmike:Which I don't say just to criticize Maven. It just makes me think that there might be a better solution
Tue Nov 29 20:18:08 2016  jugglinmike:Just before asking here, I was reading about BOM ("Bill of Material") pom files. But I don't think that pattern applies here because repositories are not inherited
Tue Nov 29 20:20:19 2016  hakvroot:jugglinmike: and you're right that maven has its... quirks ;)
Tue Nov 29 20:20:29 2016  Maxel:Joined the channel
Tue Nov 29 20:21:00 2016  hakvroot:are you running your own repository btw?
Tue Nov 29 20:21:08 2016  jugglinmike:yes. Artifactory
Tue Nov 29 20:21:49 2016  hakvroot:because if I have a situation like that where my own repo is the deployment target I make sure the dependency is resolved from that repo as well
Tue Nov 29 20:21:50 2016  jugglinmike:Hmm, this kind of throws a wrench in our theory: https://maven.apache.org/guides/mini/guide-multiple-repositories.html
Tue Nov 29 20:22:04 2016  jugglinmike:"The repositories element is inherited so you would usually specify the repositories to use for a group of projects by defining a repositories element at the top of your inheritance chain."
Tue Nov 29 20:23:36 2016  hakvroot:(by that I mean I'd add repo-A as a source to your artifactory)
Tue Nov 29 20:24:40 2016  jugglinmike:Oh, interesting. So it mirrors/proxies dependencies available in repo-A
Tue Nov 29 20:24:59 2016  hakvroot:indeed
Tue Nov 29 20:25:05 2016  jugglinmike:Probably "mirror" is what it will do. Still learning about that, too
Tue Nov 29 20:25:38 2016  hakvroot:and as long as you keep your repository the authority of your artifact it makes sense to also be able to provide its dependencies through the same repo
Tue Nov 29 20:27:38 2016  csanchez:Joined the channel
Tue Nov 29 20:30:07 2016  hakvroot:jugglinmike: and seems that that solves that mystery, I wonder why it wasn't listed in the inheritance section though :P
Tue Nov 29 20:31:11 2016  hjd:Left the channel
Tue Nov 29 20:31:50 2016  hakvroot:for artifactory you can add remote repositories as an admin I think and then adjust your virtual repositories accordingly
Tue Nov 29 20:32:52 2016  jugglinmike:hakvroot: It's still a mystery to me. It seems like the documentation I referenced is saying, "jugglinmike's setup should work"
Tue Nov 29 20:33:52 2016  hakvroot:jugglinmike: but project-C doesn't inherit from project-A, correct?
Tue Nov 29 20:35:38 2016  jugglinmike:no, but project-B does inherit from project-A
Tue Nov 29 20:36:19 2016  jugglinmike:so when project-C lists project-B as a dependency, then project-B's dependencies should be interpreted in the context of the repositories inherited from project-A
Tue Nov 29 20:38:08 2016  hakvroot:jugglinmike: for as far as I know a build for project-C will be executed for the context of project-C (as project-A/subproject-1 has already been built)
Tue Nov 29 20:40:27 2016  jugglinmike:Does that mean that a build for project-C should require resolving project-B's dependencies?
Tue Nov 29 20:40:39 2016  jugglinmike:arg scratch that
Tue Nov 29 20:40:42 2016  jugglinmike:let me re-type
Tue Nov 29 20:40:58 2016  jugglinmike:Does that mean that a build for project-C should require resolving subproject-1's dependencies?
Tue Nov 29 20:41:15 2016  jugglinmike:again, I mistyped
Tue Nov 29 20:41:18 2016  jugglinmike:sorry about that
Tue Nov 29 20:41:41 2016  jugglinmike: Does that mean that a build for project-C should **not** require resolving subproject-1's dependencies?
Tue Nov 29 20:42:08 2016  jugglinmike:(that one's good; I double-checked it)
Tue Nov 29 20:42:17 2016  hakvroot:hah
Tue Nov 29 20:42:26 2016  diogogmt:Joined the channel
Tue Nov 29 20:43:14 2016  hakvroot:and err, no
Tue Nov 29 20:43:31 2016  jugglinmike:Okay, so I'm not completely lost
Tue Nov 29 20:43:47 2016  hakvroot:so a build for project-C should require resolving subproject-1's dependencies
Tue Nov 29 20:44:07 2016  jugglinmike:but that can only be reliably done in the context of subproject-1
Tue Nov 29 20:44:54 2016  hakvroot:and that's true
Tue Nov 29 20:45:10 2016  jugglinmike:Okay, so far so good
Tue Nov 29 20:45:41 2016  jugglinmike:Here, "the context of subproject-1" includes "the repositories defined by the parent pom.xml file"
Tue Nov 29 20:46:32 2016  hakvroot:and I also agree with that :P
Tue Nov 29 20:47:08 2016  jugglinmike:hm
Tue Nov 29 20:47:12 2016  jugglinmike:So putting it together
Tue Nov 29 20:47:36 2016  Maxel:Joined the channel
Tue Nov 29 20:47:49 2016  jugglinmike:A build for project-C requires resolving subproject-1's dependencies in the context of the repositories defined in project-A.
Tue Nov 29 20:48:22 2016  hakvroot:well, not per se
Tue Nov 29 20:48:29 2016  jugglinmike:ahah
Tue Nov 29 20:49:22 2016  hakvroot:as the dependencies (project-B) of subproject-1 (which were resolved during the build of subproject-1 with the information by project-A) can also be provided through a different context
Tue Nov 29 20:50:45 2016  mischat:Joined the channel
Tue Nov 29 20:51:10 2016  hakvroot:it might even be that there are some dependencies required during the compilation or test phase - these aren't required when resolving project-B during the build of project-C
Tue Nov 29 20:51:40 2016  jugglinmike:Okay, I think I have been missing something important about the resolution process
Tue Nov 29 20:52:55 2016  jugglinmike:You are saying that subproject-1's dependencies were resolved when that project was built. Is that once-and-for-all? e.g. is the result of the resolution also deployed and later re-used when building project-C?
Tue Nov 29 20:54:49 2016  hakvroot:those results are not reused
Tue Nov 29 20:55:55 2016  hakvroot:so dependency resolution is done again when building a different project
Tue Nov 29 20:57:03 2016  jugglinmike:okay, and there are other variables that might influence the result of that second resolution
Tue Nov 29 20:57:12 2016  hakvroot:yes
Tue Nov 29 20:57:22 2016  hakvroot:like the <dependencyManagement> section =)
Tue Nov 29 20:57:58 2016  jugglinmike:hmm
Tue Nov 29 20:58:09 2016  hakvroot:your dependency might depend on org.acme:anvil:1.0.0 but your own project might depend on org.acme:anvil:2.0.0
Tue Nov 29 20:58:28 2016  jugglinmike:I think I understand, but project-C has no references to project-B
Tue Nov 29 20:58:44 2016  hakvroot:well, only transitively
Tue Nov 29 20:58:48 2016  hakvroot:"only"
Tue Nov 29 20:58:52 2016  jugglinmike:hah, right
Tue Nov 29 20:59:58 2016  hakvroot:for a variety of reasons you want to fetch the transitive dependencies as well
Tue Nov 29 21:01:27 2016  hakvroot:like when packaging (a war, fat jar), running tests
Tue Nov 29 21:01:41 2016  jugglinmike:This is making me look harder at the requests issued by Maven
Tue Nov 29 21:02:13 2016  jugglinmike:Slightly more context here: `project-C` also defines a <repository>
Tue Nov 29 21:02:21 2016  hakvroot:heh
Tue Nov 29 21:02:41 2016  jugglinmike:when attempting to build `project-C`, I can see the requests issued for `project-B`
Tue Nov 29 21:02:46 2016  hakvroot:I usually add tattletale ( http://tattletale.jboss.org/ ) as a plugin and run it when I don't trust stuff
Tue Nov 29 21:03:07 2016  hakvroot:jugglinmike: that sounds about right
Tue Nov 29 21:03:17 2016  jugglinmike:yes, but
Tue Nov 29 21:04:11 2016  jugglinmike:First, Maven is trying the repository of `project-C`, then it is trying the main public Maven repository (repo.maven.apache.org, which I understand comes from the master pom shared by all Maven projects)
Tue Nov 29 21:05:16 2016  jugglinmike:So Maven is interpreting a sub-dependency (`project-B`) in the context of the current build (`project-C`)--*not* in the context of the dependent project (`subproject-1`)
Tue Nov 29 21:06:20 2016  jugglinmike:Maybe that's not actually new information. I just hadn't seen such direct evidence until now
Tue Nov 29 21:06:39 2016  hakvroot:jugglinmike: I was already trying to figure out if I stated the opposite somewhere ;)
Tue Nov 29 21:06:50 2016  hakvroot:everything for a build is done in the context of that build
Tue Nov 29 21:08:58 2016  jugglinmike:Okay, so my hope is that this is not default behavior. In other words, I hope that that there is something about the context of project-C's build that is causing Maven to ignore information that is relevant to resolving subproject-1's dependencies
Tue Nov 29 21:13:32 2016  hakvroot:jugglinmike: well, I'm afraid I can't give you much hope there
Tue Nov 29 21:15:41 2016  jugglinmike:Is that a polite way of saying, "tough luck, this is expected behavior." Or, "there are too many variables for me to help you via irc" ?
Tue Nov 29 21:15:47 2016  hakvroot:hah
Tue Nov 29 21:15:58 2016  hakvroot:tough luck
Tue Nov 29 21:16:10 2016  jugglinmike:Got it
Tue Nov 29 21:17:23 2016  ppalaga:Left the channel
Tue Nov 29 21:17:33 2016  hakvroot:I'm actually used to not including repositories in poms myself btw - but if you're already in that situation it is a bit trickier to solve ofc.
Tue Nov 29 21:18:16 2016  hakvroot:I think I read this once - http://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/ ... probably still relevant today
Tue Nov 29 21:18:19 2016  jugglinmike:I'll concede if you would agree with a criticism of Maven: that this behavior conflicts with the goal of transitive dependency management
Tue Nov 29 21:19:50 2016  jugglinmike:If a more seasoned user such as yourself would agree with that, then I would feel better about having struggled with this for so long
Tue Nov 29 21:20:06 2016  jugglinmike:(reading)
Tue Nov 29 21:21:03 2016  hakvroot:and I wholeheartedly agree
Tue Nov 29 21:21:47 2016  jugglinmike:excellent
Tue Nov 29 21:22:17 2016  jugglinmike:I appreciate that. Though not as much as I appreciate your walking me through all of this
Tue Nov 29 21:22:21 2016  jugglinmike:It's been close to two hours!
Tue Nov 29 21:22:27 2016  jugglinmike:Thank you very much :)
Tue Nov 29 21:23:22 2016  lefou:Joined the channel
Tue Nov 29 21:23:34 2016  hakvroot:and you're welcome! glad I can use my past struggles with maven for some good ;)
Tue Nov 29 21:24:09 2016  hakvroot:(present too, btw)
Tue Nov 29 21:26:54 2016  hakvroot:either way, I'd point you to configuring Artifactory and removing the <repo> declarations from the poms altogether - downside is that you then need to instruct/configure everyone and everything with local maven settings
Tue Nov 29 21:27:29 2016  hakvroot:if you have the freedom to do so of course
Tue Nov 29 21:29:11 2016  hakvroot:eot
Tue Nov 29 21:34:39 2016  jugglinmike:That sounds good to me. I'll see how it goes over with the client
Tue Nov 29 21:43:54 2016  tang^:Joined the channel
Tue Nov 29 21:48:14 2016  csanchez:Joined the channel
Tue Nov 29 21:51:41 2016  mischat:Joined the channel
Tue Nov 29 22:08:12 2016  jdcasey:Joined the channel
Tue Nov 29 22:12:19 2016  diogogmt:Joined the channel
Tue Nov 29 22:20:42 2016  tang^_:Joined the channel
Tue Nov 29 22:21:54 2016  Sasazuka_:Joined the channel
Tue Nov 29 22:28:24 2016  benlue:Joined the channel
Tue Nov 29 22:29:44 2016  benlue:heyas i have some trouble with maven create app :/ http://hastebin.com/uxepawicur.sql
Tue Nov 29 22:29:47 2016  benlue:any ideas?
Tue Nov 29 22:57:38 2016  benlue:[ERROR] No plugin found for prefix 'archetype' in the current project and in the plugin groups
Tue Nov 29 22:57:41 2016  benlue:no ideas?
Tue Nov 29 22:59:59 2016  conan_:Joined the channel
Tue Nov 29 23:04:22 2016  tang^:try running just the mvn archetype:generate line?
Tue Nov 29 23:07:32 2016  benlue:same issue
Tue Nov 29 23:07:34 2016  benlue:[ERROR] No plugin found for prefix 'archetype' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/benlue/.m2/repository), central (https://repo.maven.apache.org/maven2)] -> [Help 1]
Tue Nov 29 23:08:10 2016  tang^:sounds like you have an internet connection issue
Tue Nov 29 23:08:21 2016  benlue:o.O
Tue Nov 29 23:08:22 2016  tang^:if you can't see the central repo
Tue Nov 29 23:09:01 2016  benlue:i can open the repo via webbrowser
Tue Nov 29 23:09:37 2016  tang^:no funky settings in .m2?
Tue Nov 29 23:11:50 2016  benlue:only folder
Tue Nov 29 23:11:57 2016  tang^:version?
Tue Nov 29 23:11:58 2016  benlue:repository
Tue Nov 29 23:12:29 2016  benlue:http://hastebin.com/gojebinaxu.rb
Tue Nov 29 23:12:35 2016  benlue:3.3.9
Tue Nov 29 23:13:25 2016  tang^:I cannot reproduce that error
Tue Nov 29 23:15:14 2016  benlue:hmm im not the first person with the same error :/
Tue Nov 29 23:54:03 2016  mischat:Joined the channel

Comments