Re: No compile errors with plexus-compiler-eclipse
Hello Olivier, Am 04.12.2012 um 09:00 schrieb Olivier Lamy : > 2012/12/4 Peter Palmreuther : >> Hello Olivier, >> >> Am 03.12.2012 um 10:52 schrieb Olivier Lamy : >> >>> Thanks for the test project. >>> It's now fixed. >>> You can test the fix with compiler plugin 3.1-SNAPSHOT and with >>> plexus-compiler-eclipse 2.1-SNAPSHOT >> >> Thanks a lot. >> >> I was able to get maven-compiler-plugin:3.1-SNAPSHOT from Apache snapshot >> repository. >> Sadly I can't find plexus-compiler-*:2.1-SNAPSHOT. >> I've set my Nexus to proxy >> https://nexus.codehaus.org/content/repositories/snapshots/, but that seems >> to be the wrong location. >> Can you point me to the correct repository? > > Use: https://oss.sonatype.org/content/repositories/plexus-snapshots Thanks, seems to work. Both, the repository URL and the fix. -- Regards, Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No compile errors with plexus-compiler-eclipse
Hello Olivier, Am 03.12.2012 um 10:52 schrieb Olivier Lamy : > Thanks for the test project. > It's now fixed. > You can test the fix with compiler plugin 3.1-SNAPSHOT and with > plexus-compiler-eclipse 2.1-SNAPSHOT Thanks a lot. I was able to get maven-compiler-plugin:3.1-SNAPSHOT from Apache snapshot repository. Sadly I can't find plexus-compiler-*:2.1-SNAPSHOT. I've set my Nexus to proxy https://nexus.codehaus.org/content/repositories/snapshots/, but that seems to be the wrong location. Can you point me to the correct repository? -- Thanks in advance, and best regards, Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No compile errors with plexus-compiler-eclipse
Hello Martin, Am 02.12.2012 um 15:37 schrieb Martin Gainty : > I downloaded maven-eclipse-compiler version 1.9.2 from maven repo1 and was > able to use the pom.xml to compile and package > here is the pom.xml i implemented: > [...] > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-compiler-eclipse/1.9.2 > does this not compile for your environment? Pardon? My message was not about compiling plexus-comiler-eclipse itself, but using it to compile my very own stuff. As requested by Olivier Lamy I already opened a JIRA issue about my objections, but thanks for your comment. -- Best regards, Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
No compile errors with plexus-compiler-eclipse
Hello, I'm trying to make use of plexus-compiler-eclipse by setting maven-compiler-plugin 3.0 eclipse org.codehaus.plexus plexus-compiler-eclipse 2.0 in pom.xml. mvn compile works, but in fact I still have errors in my code (I'm actually porting an ant and xdoclet based project to maven). But instead of getting errors I see a lot of warnings and build succeeds. The warnings are not only about "Hashtable is a raw type. References to generic type Hashtable should be parameterized" which I'd expect as a warning only, but also "Type mismatch: cannot convert from Object to MyBusinessFacadeRemote" or "MyBusinessServlet cannot be resolved" or "Unreachable catch block for RemoteException. This exception is never thrown from the try statement body" or "The import foo.bar.Bla cannot be resolved" or even whole types (formerly xdoclet generated types I partially need to create manually by myself and haven't done yet). These I'd expect to pop up as an error and fail the build. Instead it's only printed as a warning and build continues. Am I configuring maven-compiler-plugin - and plexus-compile-eclipse - the wrong way? Or is plexus-compiler-eclipse not raising these errors as such at all, which would render it quite a bit useless at the moment? -- Thanks in advance, and best regards, Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No compile errors with plexus-compiler-eclipse
Hello, Am 30.11.2012 um 21:41 schrieb Olivier Lamy : > 2012/11/30 Peter Palmreuther : >> [...] >> Am I configuring maven-compiler-plugin - and plexus-compile-eclipse - the >> wrong way? >> Or is plexus-compiler-eclipse not raising these errors as such at all, which >> would render it quite a bit useless at the moment? > maybe an issue. > Can you raise a jira entry with a sample project ? http://jira.codehaus.org/browse/PLXCOMP-215 -- Regards, Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
No compile errors with plexus-compiler-eclipse
Hello, I'm trying to make use of plexus-compiler-eclipse by setting maven-compiler-plugin 3.0 eclipse org.codehaus.plexus plexus-compiler-eclipse 2.0 in pom.xml. mvn compile works, but in fact I still have errors in my code (I'm actually porting an ant and xdoclet based project to maven). But instead of getting errors I see a lot of warnings and build succeeds. The warnings are not only about "Hashtable is a raw type. References to generic type Hashtable should be parameterized" which I'd expect as a warning only, but also "Type mismatch: cannot convert from Object to MyBusinessFacadeRemote" or "MyBusinessServlet cannot be resolved" or "Unreachable catch block for RemoteException. This exception is never thrown from the try statement body" or "The import foo.bar.Bla cannot be resolved" or even whole types (formerly xdoclet generated types I partially need to create manually by myself and haven't done yet). These I'd expect to pop up as an error and fail the build. Instead it's only printed as a warning and build continues. Am I configuring maven-compiler-plugin - and plexus-compile-eclipse - the wrong way? Or is plexus-compiler-eclipse not raising these errors as such at all, which would render it quite a bit useless at the moment? -- Thanks in advance, and best regards, Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dependency hel(l|p)
Hi, thanks for your response. In fact I just tried 'mvn compile dependency:tree' and it works. Strange. But than: is there something wrong with my project dependencies or with 'maven-dependency-plugin' and 'maven-source-plugin' if their goals 'tree' (or 'list) and 'aggregate' only work when executed in combination with phase 'compile' or 'package'? I stumbled upon this problem when I tried to set up a 'source:aggregate' being executed in my master project on every 'install'. The goal was to be able to 'mvn install' and end up with aggregated sources for the reactor project being available. If as a workaround instead of 'mvn install' I can do 'mvn package install' and have 'source:aggregate' executed automatically I'm fine for now. But I assume this is not primarily "the maven way". Nor do I see the point in doing 'mvn compile dependency:tree' if only I want to see all the dependencies (or generate some graphics from it's output). So any other comments or hints about what's going (wr)on(g)? Best regards, Peter On Wed, Sep 12, 2012 at 3:47 PM, Aliaksei Lahachou wrote: > Hi, > > I've seen this problem. It seems that Maven knows about artifacts from > dependencies only if they were built in the same run. So for example 'mvn > package cargo:deploy' works, because all artifacts were packaged in the > same run, but 'mvn cargo:deploy' doesn't work until artifacts are > installed, even if you ran 'mvn package' before. > > > Regards, > htfv (Aliaksei Lahachou) > > > On Wed, Sep 12, 2012 at 8:11 AM, Peter Palmreuther < > pit.palme+ma...@gmail.com> wrote: > >> Hi, >> >> I hope somebody on this list can help me with - or knows a location to >> find help for - a dependency problem. >> >> I have a bunch of projects: >> >> +master >> + plain >> - java-lib >> - bind-one >> - bind-two >> + jee >> - ejb >> - ear >> >> '+' are 'pom', i.e. reactor-, projects, '-' are 'jar', 'ejb' and 'ear' >> projects. >> 'ejb' depends on all 'plain' projects (provided), so does 'ear' (runtime). >> 'bind-two' depends on 'java-lib' (currently provided, tried compile, >> but makes no difference). >> >> I'm able to 'mvn package' and 'mvn install' without any hassle. >> But 'mvn dependency:tree' or 'mvn source:aggregate' fails, unless I >> had successfully run 'mvn install' for the current version before. >> >> What's wrong here? Are my dependencies creepy, or is there something >> going wrong in dependency and source plugin? >> >> For those interested in inspecting this (and pointing me towards my >> probably obvious mistake by banging my head onto it) I've created a >> minimal example I'm capable to reproduce this behavior with: >> >> http://www.file-upload.net/download-4778941/maven_dep_example.zip.html >> >> Thanks in advance, >> and best regards, >> >> Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dependency hel(l|p)
Hello, I'm sorry for any confusion, but behind the given download link there's on the right side a block with date, file size and comment. Below this block there's a download button. And to it works. It would for sure have been easier to attach the archive, especially as it's only a few K in size. But I assumed this list might block attachments. So the next easy solution to me was to upload it somewhere always accessible. I can only assure I never was nor am trying to trick you to install malware. Regards, Peter On Wed, Sep 12, 2012 at 8:41 AM, Anders Hammar wrote: > It might just be me being an Internet idiot, but I tried downloading > and just got downloads for some download manager or other junk. Please > make it easy for us to help! I'm not even sure this is for real or if > you're someone trying to trick us to install some malware. > > Just wasted time which I could have spent helping you, > /Anders > > On Wed, Sep 12, 2012 at 8:11 AM, Peter Palmreuther > wrote: >> Hi, >> >> I hope somebody on this list can help me with - or knows a location to >> find help for - a dependency problem. >> >> I have a bunch of projects: >> >> +master >> + plain >> - java-lib >> - bind-one >> - bind-two >> + jee >> - ejb >> - ear >> >> '+' are 'pom', i.e. reactor-, projects, '-' are 'jar', 'ejb' and 'ear' >> projects. >> 'ejb' depends on all 'plain' projects (provided), so does 'ear' (runtime). >> 'bind-two' depends on 'java-lib' (currently provided, tried compile, >> but makes no difference). >> >> I'm able to 'mvn package' and 'mvn install' without any hassle. >> But 'mvn dependency:tree' or 'mvn source:aggregate' fails, unless I >> had successfully run 'mvn install' for the current version before. >> >> What's wrong here? Are my dependencies creepy, or is there something >> going wrong in dependency and source plugin? >> >> For those interested in inspecting this (and pointing me towards my >> probably obvious mistake by banging my head onto it) I've created a >> minimal example I'm capable to reproduce this behavior with: >> >> http://www.file-upload.net/download-4778941/maven_dep_example.zip.html >> >> Thanks in advance, >> and best regards, >> >> Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Dependency hel(l|p)
Hi, I hope somebody on this list can help me with - or knows a location to find help for - a dependency problem. I have a bunch of projects: +master + plain - java-lib - bind-one - bind-two + jee - ejb - ear '+' are 'pom', i.e. reactor-, projects, '-' are 'jar', 'ejb' and 'ear' projects. 'ejb' depends on all 'plain' projects (provided), so does 'ear' (runtime). 'bind-two' depends on 'java-lib' (currently provided, tried compile, but makes no difference). I'm able to 'mvn package' and 'mvn install' without any hassle. But 'mvn dependency:tree' or 'mvn source:aggregate' fails, unless I had successfully run 'mvn install' for the current version before. What's wrong here? Are my dependencies creepy, or is there something going wrong in dependency and source plugin? For those interested in inspecting this (and pointing me towards my probably obvious mistake by banging my head onto it) I've created a minimal example I'm capable to reproduce this behavior with: http://www.file-upload.net/download-4778941/maven_dep_example.zip.html Thanks in advance, and best regards, Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: - How to create multiple jar files from one project? - Bayesian Filter detected spam
Hello Alexander, On Sunday, December 3, 2006 at 10:53:57 PM Alexander wrote: > Yea, I agree...I don't see why interfaces should be dependent on > implementations? What's the point? It doesn't. The *Factory* does, and just *this* factory is (should be) shipped with the relevant interface, while the implementation should be shipped separately. Or more precisely: the impl-jar shouldn't be shipped anywhere, just located in the runtime. > I don't see how you would have a circular dependency. I do have. If you don't see it I wasn't able to explain it correctly. > Your factory classes probably produce instances of your interfaces. It does. > Your implementation classes would depend on those interfaces. Exactly. And for the Factory producing instances it depends on the implementation class. Which is in a different project / jar. Which depends on the interface class / jar. Which can't be built due to the fact it needs the impl-jar (as "" set up in "pom.xml"). Which can't be compiled as it needs the interface class. Which *aghh* I'm lost in a recursive explanation!!! ;-) > Life is good! :D Sometimes. Not. :-) > On 12/3/06, William Ferguson <[EMAIL PROTECTED]> wrote: >> >> Peter, >> >> I don't think a Maven solution is what you need. >> I think you need to rethink the packaging and dependencies of your 2 >> projects. >> It sounds like your interface project shouldn't depend on the Factory in >> the implementation project. >> >> You could organise this a couple of different ways: >> 1) The Factory class could ship with interface project. >> 2) Ship a Factory interface with your interface project, and ship the >> Factory impl in the other project. >> >> Hope this helps. >> >> William >> >> -Original Message- >> From: Peter Palmreuther [mailto:[EMAIL PROTECTED] >> Sent: Sunday, 3 December 2006 9:01 PM >> To: Maven Users List >> Subject: [***POSSIBLE SPAM***] - How to create multiple jar files from >> one project? - Bayesian Filter detected spam >> >> Hello, >> >> I'm new to Maven and tried to find an answer on the website, but either >> I'm to dense or it ain't there (yet). So if this question is already >> answered in a public available document I'd be happy to get the link. >> >> I have a project that should be a library to encapsulate the logger >> being used in all other projects. From this project I create two JAR >> files: one containing the interface(s) and a factory, the other one >> containing the implementation classes. >> >> By now I'm trying to switch to use Maven2 for project management and >> dependency tracking, but I'm still unable to get the two jars out of >> Maven build process. >> >> Therefore I've tried to split the project up into two projects to have >> two artifacts. But than I end up in a cyclic dependency: >> >> Interface project depends on implementation project for the factory to >> compile; Implementation project depends on interface project for the >> implementation class to compile (Class implements Interface). A deadlock >> :-( >> >> Anybody out there with an idea how to solve this problem "the Maven2 >> way"? I'd be happy with a hint on >> - either how to influence the packaging process for getting two JARs >> (artifacts?) from one POM >> - or how to tell the two Maven2 projects they belong "somehow >> together" for dependency resolution in a way it's done as if this >> were one project >> >> Thanks a lot in advance, >> -- >> Best regards >> Peter Palmreuther >> >> "Bother," said Pooh as he found he'd used a dirty needle -- Best regards "Peter Palmreuther <[EMAIL PROTECTED]>" (The Bat! v3.86.8 ALPHA (beta) on Windows XP 5.1 Build 2600 Service Pack 2) "There is no statute of limitations on stupidity." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to create multiple jar files from one project?
Hello Tom, On Sunday, December 3, 2006 at 8:31:24 PM Tom wrote: > Maven does not support creating two artifacts from one project and it > does not support circular dependencies between two projects. The only > proper solution is cutting the dependency from interface to > implementation. Thanks a lot for clarifying things up, for me don't need to search further. > One thing you could try is to create an abstract factory that can find > a concrete implementation of itself through reflection (based on a > default implementation, a system property, configuration, ...) Thanks. Already started something similar, while I was awaiting the answer here ... Seems I was on the right track ... > On 12/3/06, Peter Palmreuther <[EMAIL PROTECTED]> wrote: >> Hello, >> >> I'm new to Maven and tried to find an answer on the website, but >> either I'm to dense or it ain't there (yet). So if this question is >> already answered in a public available document I'd be happy to get >> the link. >> >> I have a project that should be a library to encapsulate the logger >> being used in all other projects. From this project I create two JAR >> files: one containing the interface(s) and a factory, the other one >> containing the implementation classes. >> >> By now I'm trying to switch to use Maven2 for project management and >> dependency tracking, but I'm still unable to get the two jars out of >> Maven build process. >> >> Therefore I've tried to split the project up into two projects to have >> two artifacts. But than I end up in a cyclic dependency: >> >> Interface project depends on implementation project for the factory to >> compile; Implementation project depends on interface project for the >> implementation class to compile (Class implements Interface). A >> deadlock :-( >> >> Anybody out there with an idea how to solve this problem "the Maven2 >> way"? I'd be happy with a hint on >> - either how to influence the packaging process for getting two JARs >> (artifacts?) from one POM >> - or how to tell the two Maven2 projects they belong "somehow >> together" for dependency resolution in a way it's done as if this >> were one project >> >> Thanks a lot in advance, >> -- >> Best regards >> Peter Palmreuther >> >> "Bother," said Pooh as he found he'd used a dirty needle -- Best regards "Peter Palmreuther <[EMAIL PROTECTED]>" (The Bat! v3.86.8 ALPHA (beta) on Windows XP 5.1 Build 2600 Service Pack 2) DIODE: What happens to people who don't die young. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: - How to create multiple jar files from one project? - Bayesian Filter detected spam
Hello William, On Sunday, December 3, 2006 at 10:46:37 PM William wrote: > I don't think a Maven solution is what you need. OK. Can live with this. I just wanted to make sure *there is none* before I go the long way and get told later there was a shorter one. > I think you need to rethink the packaging and dependencies of your 2 > projects. In fact I do. I took over this project and started to clean up and introduce Maven ... Rethinking everything is the very first I did ;-) And I'm not quite finished yet ;-) > It sounds like your interface project shouldn't depend on the Factory in > the implementation project. The factory is part of the interface project: Interface-Project: - Custom logger interface - Factory to create such a logger Implementation-Project: - Custom logger - some other stuff (just the relevant parts mentioned) > You could organise this a couple of different ways: > 1) The Factory class could ship with interface project. It does. > 2) Ship a Factory interface with your interface project, and ship the > Factory impl in the other project. *hmm* Good idea, will think about it. But there's still the need create an instance of something that's in the interface-project. And this one needs to know something from the implementation. And this implementation-project needs to know the Interface(s) and this leads me to: "You most probable need reflection when you want to cut the two things up". > Hope this helps. Sure. Somehow. And if it only enforces me to think about all the stuff another time ;-) > -Original Message- > From: Peter Palmreuther [mailto:[EMAIL PROTECTED] > Sent: Sunday, 3 December 2006 9:01 PM > To: Maven Users List > Subject: [***POSSIBLE SPAM***] - How to create multiple jar files from > one project? - Bayesian Filter detected spam > Hello, > I'm new to Maven and tried to find an answer on the website, but either > I'm to dense or it ain't there (yet). So if this question is already > answered in a public available document I'd be happy to get the link. > I have a project that should be a library to encapsulate the logger > being used in all other projects. From this project I create two JAR > files: one containing the interface(s) and a factory, the other one > containing the implementation classes. > By now I'm trying to switch to use Maven2 for project management and > dependency tracking, but I'm still unable to get the two jars out of > Maven build process. > Therefore I've tried to split the project up into two projects to have > two artifacts. But than I end up in a cyclic dependency: > Interface project depends on implementation project for the factory to > compile; Implementation project depends on interface project for the > implementation class to compile (Class implements Interface). A deadlock > :-( > Anybody out there with an idea how to solve this problem "the Maven2 > way"? I'd be happy with a hint on > - either how to influence the packaging process for getting two JARs > (artifacts?) from one POM > - or how to tell the two Maven2 projects they belong "somehow > together" for dependency resolution in a way it's done as if this > were one project > Thanks a lot in advance, > -- > Best regards > Peter Palmreuther > "Bother," said Pooh as he found he'd used a dirty needle -- Best regards "Peter Palmreuther <[EMAIL PROTECTED]>" (The Bat! v3.86.8 ALPHA (beta) on Windows XP 5.1 Build 2600 Service Pack 2) Don't know what I'm after, but the pressure's driving me insane... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to create multiple jar files from one project?
Hello, I'm new to Maven and tried to find an answer on the website, but either I'm to dense or it ain't there (yet). So if this question is already answered in a public available document I'd be happy to get the link. I have a project that should be a library to encapsulate the logger being used in all other projects. From this project I create two JAR files: one containing the interface(s) and a factory, the other one containing the implementation classes. By now I'm trying to switch to use Maven2 for project management and dependency tracking, but I'm still unable to get the two jars out of Maven build process. Therefore I've tried to split the project up into two projects to have two artifacts. But than I end up in a cyclic dependency: Interface project depends on implementation project for the factory to compile; Implementation project depends on interface project for the implementation class to compile (Class implements Interface). A deadlock :-( Anybody out there with an idea how to solve this problem "the Maven2 way"? I'd be happy with a hint on - either how to influence the packaging process for getting two JARs (artifacts?) from one POM - or how to tell the two Maven2 projects they belong "somehow together" for dependency resolution in a way it's done as if this were one project Thanks a lot in advance, -- Best regards Peter Palmreuther "Bother," said Pooh as he found he'd used a dirty needle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to create multiple jar files from one project?
Hello, I'm new to Maven and tried to find an answer on the website, but either I'm to dense or it ain't there (yet). So if this question is already answered in a public available document I'd be happy to get the link. I have a project that should be a library to encapsulate the logger being used in all other projects. From this project I create two JAR files: one containing the interface(s) and a factory, the other one containing the implementation classes. By now I'm trying to switch to use Maven2 for project management and dependency tracking, but I'm still unable to get the two jars out of Maven build process. Therefore I've tried to split the project up into two projects to have two artifacts. But than I end up in a cyclic dependency: Interface project depends on implementation project for the factory to compile; Implementation project depends on interface project for the implementation class to compile (Class implements Interface). A deadlock :-( Anybody out there with an idea how to solve this problem "the Maven2 way"? I'd be happy with a hint on - either how to influence the packaging process for getting two JARs (artifacts?) from one POM - or how to tell the two Maven2 projects they belong "somehow together" for dependency resolution in a way it's done as if this were one project Thanks a lot in advance, -- Best regards Peter Palmreuther "Bother," said Pooh as he found he'd used a dirty needle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
