RE: dependency question
This is fine as long as the dependency is always set to x.y.z-Snapshot and the dependency is always overwritten this way. What if the producer produces x.y.z.1-Snapshot, x.y.z.2-Snapshot, x.y.z.3-Snapshot and I want the dependent build to always get the latest in this case, x.y.z.3-Snapshot ? The difference with this scenario is that the producer will always have a new build number. As for your solution of using the range, do I always have to change the pom file in the dependent build whenever a new build is produced by the producer ? -Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Monday, April 10, 2017 10:39 AM To: Maven Users List Subject: Re: dependency question On Mon, Apr 10, 2017 at 8:18 AM, Magnanao, Hector wrote: > I'm still a little confused about the answers I'm getting. So, if build A is > being updated with a new build number(even for a snapshot), and build B has > it as a dependency in it's pom.file, how does the pom file in Build B need to > look like in the dependency section so that it does get the latest snapshot > build of build A ? This conversation seems to keep mixing up SNAPSHOT version processing with various conventions for using version ranges. If the producer produces x.y.z-SNAPSHOT, and the consumer declares a dependency on x.y.z-SNAPSHOT, every build of the consumer will go out to the repositories to look for the latest snapshot build. Snapshots have risks and do not provide a repeatable build. Then again, neither do ranges. If you don't want to use snapshots, then you write the dependency in the consumer with a range (1.0-2.0] or whatever makes sense. This will cause builds of the consumer to go out to repositories and try to find the newest version within the range. it's up to you to bump the version in the producer, manually or with the maven-release-plugin. > > Scenario: > > Build A has 3 builds in it with names 1-Snapshot, 2-snapshot, 3-snapshot and > they are all being uploaded to a repository. > > What will the pom file in build B look like so that the next time build B is > executed, 3-snapshot for build A will be picked up ? > > -Original Message- > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] > Sent: Friday, April 7, 2017 10:50 AM > To: Maven Users List > Subject: Re: dependency question > > Hi Russlel, > On 07/04/17 17:29, Russell Gold wrote: > >> That’s the way it works: when you specify a snapshot, it takes the latest. > > This is not 100% true, cause it depends on the update policy you have > defined in your settings either explicit or by default the updates will > be checked every 24 hours... > > If you like to force this you can use mvn -U ...or define a different > updatePolicy in your settings.xml for the appropriate repository. > > By using mvn -U you make sure for running this build Maven will check if > there are newer SNAPSHOT version available for dependencies which have > defined a SNAPSHOT version > > This is working for a single module project...but if you have a multi > module build (Project C: A1 build before A2) which takes for example 5 > minutes to build ...this is no longer 100% true... > > Now let us assume you have another project B which dependends on two > different artifacts (A1, A2) of Project C ...this means in consequence > those artifacts are build at two different times... > > This means it could happen that your build of Project B consumes A2 from > build #10 but A1 from build #9 ... > > > In practical it usually works without any issue using the mvn -U ...but > you should be aware of this issue... > > > The only solution which I have found to make 100% sure is to use the > output during the build of the project A and use those parsed > informations about the SNAPSHOT versions and inject them into my current > build ...(https://github.com/khmarbaise/deployment-recorder-extension > not ready yet)... > > Kind regards > Karl Heinz Marbaise > > >> >> There are some corner cases where it won’t. I think it only checks for a new >> snapshot every few hours or so, so if you are putting out a lot you might >> conceivably miss one. You can reset that if you need to >> . >>> On Apr 7, 2017, at 11:27 AM, Magnanao, Hector >>> wrote: >>> >>> If the builds for A are always getting a unique build number as a snapshot >>> build, how am I sure that B will always get the latest snapshot of A ? Is >>> there a way to name the A snapshot builds with a unique build number each >>> time for this scenario. >>> >>> -Original Message- >>> From: Russell Gold [mailto:russell.g...@oracle.com] >>> Sent: Thursday,
RE: dependency question
I'm still a little confused about the answers I'm getting. So, if build A is being updated with a new build number(even for a snapshot), and build B has it as a dependency in it's pom.file, how does the pom file in Build B need to look like in the dependency section so that it does get the latest snapshot build of build A ? Scenario: Build A has 3 builds in it with names 1-Snapshot, 2-snapshot, 3-snapshot and they are all being uploaded to a repository. What will the pom file in build B look like so that the next time build B is executed, 3-snapshot for build A will be picked up ? -Original Message- From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] Sent: Friday, April 7, 2017 10:50 AM To: Maven Users List Subject: Re: dependency question Hi Russlel, On 07/04/17 17:29, Russell Gold wrote: > That’s the way it works: when you specify a snapshot, it takes the latest. This is not 100% true, cause it depends on the update policy you have defined in your settings either explicit or by default the updates will be checked every 24 hours... If you like to force this you can use mvn -U ...or define a different updatePolicy in your settings.xml for the appropriate repository. By using mvn -U you make sure for running this build Maven will check if there are newer SNAPSHOT version available for dependencies which have defined a SNAPSHOT version This is working for a single module project...but if you have a multi module build (Project C: A1 build before A2) which takes for example 5 minutes to build ...this is no longer 100% true... Now let us assume you have another project B which dependends on two different artifacts (A1, A2) of Project C ...this means in consequence those artifacts are build at two different times... This means it could happen that your build of Project B consumes A2 from build #10 but A1 from build #9 ... In practical it usually works without any issue using the mvn -U ...but you should be aware of this issue... The only solution which I have found to make 100% sure is to use the output during the build of the project A and use those parsed informations about the SNAPSHOT versions and inject them into my current build ...(https://github.com/khmarbaise/deployment-recorder-extension not ready yet)... Kind regards Karl Heinz Marbaise > > There are some corner cases where it won’t. I think it only checks for a new > snapshot every few hours or so, so if you are putting out a lot you might > conceivably miss one. You can reset that if you need to > . >> On Apr 7, 2017, at 11:27 AM, Magnanao, Hector >> wrote: >> >> If the builds for A are always getting a unique build number as a snapshot >> build, how am I sure that B will always get the latest snapshot of A ? Is >> there a way to name the A snapshot builds with a unique build number each >> time for this scenario. >> >> -Original Message- >> From: Russell Gold [mailto:russell.g...@oracle.com] >> Sent: Thursday, April 6, 2017 2:27 PM >> To: Maven Users List >> Subject: Re: dependency question >> >> The simplest way is simply to use a snapshot version of A. That way B will >> always use the latest snapshot. When you finally release A, you can have B >> point to the released version instead of the snapshot. >> >>> On Apr 6, 2017, at 2:52 PM, Magnanao, Hector >>> wrote: >>> >>> I have to 2 java projects a and b in maven. The B project uses the A build >>> as a dependency. How do I ensure the whenever the A project has a new >>> build, the B project will always use that latest build in A. A is being >>> built with a unique build number each time it gets built. So is A has >>> build # 10 as the newest build, the B project has to use build #10 of A. >>> >>> >>> Hector Magnanao Jr. >>> SCM Analyst >>> SAP Fieldglass >>> Skype: (331) 702-6142 >>> Mobile: (847) 857-8401 >>> Email: hector.magna...@sap.com >>> >> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: dependency question
Can you give me an example of using a range in the pom file as a dependency ? -Original Message- From: Robert Patrick [mailto:robert.patr...@oracle.com] Sent: Thursday, April 6, 2017 2:34 PM To: Maven Users List Subject: RE: dependency question The other way is to use a version range in your dependency, which gives you a similar behavior as using a snapshot dependency. Both approaches have their advantages and drawbacks... -Original Message- From: Russell Gold Sent: Thursday, April 06, 2017 2:27 PM To: Maven Users List Subject: Re: dependency question The simplest way is simply to use a snapshot version of A. That way B will always use the latest snapshot. When you finally release A, you can have B point to the released version instead of the snapshot. > On Apr 6, 2017, at 2:52 PM, Magnanao, Hector wrote: > > I have to 2 java projects a and b in maven. The B project uses the A build > as a dependency. How do I ensure the whenever the A project has a new build, > the B project will always use that latest build in A. A is being built with > a unique build number each time it gets built. So is A has build # 10 as the > newest build, the B project has to use build #10 of A. > > > Hector Magnanao Jr. > SCM Analyst > SAP Fieldglass > Skype: (331) 702-6142 > Mobile: (847) 857-8401 > Email: hector.magna...@sap.com > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: dependency question
If the builds for A are always getting a unique build number as a snapshot build, how am I sure that B will always get the latest snapshot of A ? Is there a way to name the A snapshot builds with a unique build number each time for this scenario. -Original Message- From: Russell Gold [mailto:russell.g...@oracle.com] Sent: Thursday, April 6, 2017 2:27 PM To: Maven Users List Subject: Re: dependency question The simplest way is simply to use a snapshot version of A. That way B will always use the latest snapshot. When you finally release A, you can have B point to the released version instead of the snapshot. > On Apr 6, 2017, at 2:52 PM, Magnanao, Hector wrote: > > I have to 2 java projects a and b in maven. The B project uses the A build > as a dependency. How do I ensure the whenever the A project has a new build, > the B project will always use that latest build in A. A is being built with > a unique build number each time it gets built. So is A has build # 10 as the > newest build, the B project has to use build #10 of A. > > > Hector Magnanao Jr. > SCM Analyst > SAP Fieldglass > Skype: (331) 702-6142 > Mobile: (847) 857-8401 > Email: hector.magna...@sap.com > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: how to get the latest build for dependency
The problem with just using SNAPSHOT is that, we need to build A with its own unique build number for versioning purpose. In your other comment, if I use the minimum version, do I still have to always update the pom file in the B project so it gets the minimum version of build A ? From: Philip Whitehouse [mailto:phi...@whiuk.com] Sent: Thursday, April 6, 2017 1:41 PM To: Maven Users List ; Magnanao, Hector ; Maven users Subject: Re: how to get the latest build for dependency Unless you're actually releasing the builds, just use SNAPSHOT. Otherwise use [minimumVersion, ) and it will resolve to the latest. On 6 April 2017 19:36:57 BST, hector.magna...@sap.com<mailto:hector.magna...@sap.com> wrote: I have to 2 java projects a and b in maven. The B project uses the A build as a dependency. How do I ensure the whenever the A project has a new build, the B project will always use that latest build in A. A is being built with a unique build number each time it gets built. So is A has build # 10 as the newest build, the B project has to use build #10 of A. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
dependency question
I have to 2 java projects a and b in maven. The B project uses the A build as a dependency. How do I ensure the whenever the A project has a new build, the B project will always use that latest build in A. A is being built with a unique build number each time it gets built. So is A has build # 10 as the newest build, the B project has to use build #10 of A. Hector Magnanao Jr. SCM Analyst SAP Fieldglass Skype: (331) 702-6142 Mobile: (847) 857-8401 Email: hector.magna...@sap.com
Maven/Nexus setting
How do I setup my maven builds to use the nexus repository for dependencies ? Hector Magnanao Jr. SCM Analyst SAP Fieldglass hector.magna...@sap.com
Packaging a directory in Maven
I need to have Maven package a directory in Bitbucket that will eventually be uploaded to Artifactory. How do I do this in Maven ? I'd need to run this in Bamboo. Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
RE: maven jar versus ant jar
Hi Greg, I was able to resolve the problem here with assistance from a developer. The jar was being packaged because it was being placed under my resources folder. So to fix it, I had to put an exclude clause in my pom file. Answering your questions below, I installed it using mvn install and the jar I'm installing is a java jar. I needed to install the jar locally in order for my compile to work. I couldn't find the jar in any maven repository so I installed it locally. Here is the solution that worked for me. When I changed my pom file to do an exclude, I did a mvn clean and the rebuild and now my jar is much smaller than before. src/resources **/resources/aspose.pdf-3.2.jdk16.jar Thanks, Hector -Original Message- From: Greg Trasuk [mailto:tras...@stratuscom.com] Sent: Wednesday, September 02, 2015 10:17 AM To: Maven Users List Subject: Re: maven jar versus ant jar Hi Hector: Could you describe in very precise terms how you “installed it locally”? That might help us understand the problem. And perhaps you’ve already mentioned it, but what kind of jar file are you actually building? What does it get installed into? Cheers, Greg Trasuk > On Sep 2, 2015, at 10:37 AM, Magnanao, Hector wrote: > > I've done "mvn clean" several times and built again. It still keeps getting > packaged in my jar. The only difference with this dependency is that I > installed it locally. My pom just declares it as a dependency. Do I need to > clean up my .m2 directory to start fresh ? > > -Original Message- > From: Wayne Fay [mailto:wayne...@gmail.com] > Sent: Tuesday, September 01, 2015 5:31 PM > To: Maven Users List > Subject: Re: maven jar versus ant jar > > Try "mvn clean" first to be sure you didn't accidentally put the > contents of that jar file in target/ and forget about it. Then build > again. > > If it is still large and includes those files, there must be something > in your pom file that is causing it to occur. Very hard to debug your > build without seeing these details. > > Wayne > > On Tue, Sep 1, 2015 at 4:41 PM, Magnanao, Hector > wrote: >> I found out why my maven jar is much bigger. It looks like it's including a >> dependency jar inside the SNAPSHOT jar. I installed this jar locally so I >> can compile but now it's being included in the build itself. So how do I >> exclude it when I do a mvn package ? >> >> -Original Message- >> From: Tobias Hochgürtel [mailto:tobias.hochguer...@googlemail.com] >> Sent: Tuesday, September 01, 2015 3:35 PM >> To: Maven Users List >> Subject: Re: maven jar versus ant jar >> >> You can unpack the jar files to see what they include. This should help >> you to find out what they makes fat or slimmer as the other one. >> >> HTH >> Tobias >> >> Am 01.09.2015 um 22:29 schrieb Magnanao, Hector: >>> I was finally able to build my snapshot jar using maven after going thru >>> all the missing dependencies. But what I noticed is that the maven jar is >>> much larger than my ant jar. Can anybody tell me why this is so ? Should >>> they be different in sizes after converting the build to maven ? what >>> should I be looking for causes of differences ? >>> >>> Hector Magnanao Jr. >>> SCM Analyst >>> >>> Fieldglass, Inc. >>> O: (331) 702-6142 >>> M: (773) 474-3051 >>> hector.magna...@sap.com >>> www.fieldglass.com >>> >>> Fieldglass is now part of SAP >>> >>> This email contains confidential information. If you are not the intended >>> recipient, do not read, distribute or reproduce this transmission >>> (including any attachments). If you have received this email in error, >>> please notify the sender by email reply. >>> >>> >> >> -- >> Tobias Hochgürtel >> >> >> >> Tobias Hochgürtel >> Alt-Stralau 15 >> 10245 Berlin >> >> Tel. 03029 0493-39 >> Fax 03026 9488-22 >> E-Mail: tobias.hochguer...@googlemail.com >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven jar versus ant jar
I've done "mvn clean" several times and built again. It still keeps getting packaged in my jar. The only difference with this dependency is that I installed it locally. My pom just declares it as a dependency. Do I need to clean up my .m2 directory to start fresh ? -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Tuesday, September 01, 2015 5:31 PM To: Maven Users List Subject: Re: maven jar versus ant jar Try "mvn clean" first to be sure you didn't accidentally put the contents of that jar file in target/ and forget about it. Then build again. If it is still large and includes those files, there must be something in your pom file that is causing it to occur. Very hard to debug your build without seeing these details. Wayne On Tue, Sep 1, 2015 at 4:41 PM, Magnanao, Hector wrote: > I found out why my maven jar is much bigger. It looks like it's including a > dependency jar inside the SNAPSHOT jar. I installed this jar locally so I > can compile but now it's being included in the build itself. So how do I > exclude it when I do a mvn package ? > > -Original Message- > From: Tobias Hochgürtel [mailto:tobias.hochguer...@googlemail.com] > Sent: Tuesday, September 01, 2015 3:35 PM > To: Maven Users List > Subject: Re: maven jar versus ant jar > > You can unpack the jar files to see what they include. This should help > you to find out what they makes fat or slimmer as the other one. > > HTH > Tobias > > Am 01.09.2015 um 22:29 schrieb Magnanao, Hector: >> I was finally able to build my snapshot jar using maven after going thru all >> the missing dependencies. But what I noticed is that the maven jar is much >> larger than my ant jar. Can anybody tell me why this is so ? Should they >> be different in sizes after converting the build to maven ? what should I >> be looking for causes of differences ? >> >> Hector Magnanao Jr. >> SCM Analyst >> >> Fieldglass, Inc. >> O: (331) 702-6142 >> M: (773) 474-3051 >> hector.magna...@sap.com >> www.fieldglass.com >> >> Fieldglass is now part of SAP >> >> This email contains confidential information. If you are not the intended >> recipient, do not read, distribute or reproduce this transmission (including >> any attachments). If you have received this email in error, please notify >> the sender by email reply. >> >> > > -- > Tobias Hochgürtel > > > > Tobias Hochgürtel > Alt-Stralau 15 > 10245 Berlin > > Tel. 03029 0493-39 > Fax 03026 9488-22 > E-Mail: tobias.hochguer...@googlemail.com > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven jar versus ant jar
I found out why my maven jar is much bigger. It looks like it's including a dependency jar inside the SNAPSHOT jar. I installed this jar locally so I can compile but now it's being included in the build itself. So how do I exclude it when I do a mvn package ? -Original Message- From: Tobias Hochgürtel [mailto:tobias.hochguer...@googlemail.com] Sent: Tuesday, September 01, 2015 3:35 PM To: Maven Users List Subject: Re: maven jar versus ant jar You can unpack the jar files to see what they include. This should help you to find out what they makes fat or slimmer as the other one. HTH Tobias Am 01.09.2015 um 22:29 schrieb Magnanao, Hector: > I was finally able to build my snapshot jar using maven after going thru all > the missing dependencies. But what I noticed is that the maven jar is much > larger than my ant jar. Can anybody tell me why this is so ? Should they be > different in sizes after converting the build to maven ? what should I be > looking for causes of differences ? > > Hector Magnanao Jr. > SCM Analyst > > Fieldglass, Inc. > O: (331) 702-6142 > M: (773) 474-3051 > hector.magna...@sap.com > www.fieldglass.com > > Fieldglass is now part of SAP > > This email contains confidential information. If you are not the intended > recipient, do not read, distribute or reproduce this transmission (including > any attachments). If you have received this email in error, please notify the > sender by email reply. > > -- Tobias Hochgürtel Tobias Hochgürtel Alt-Stralau 15 10245 Berlin Tel. 03029 0493-39 Fax 03026 9488-22 E-Mail: tobias.hochguer...@googlemail.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven jar versus ant jar
I was finally able to build my snapshot jar using maven after going thru all the missing dependencies. But what I noticed is that the maven jar is much larger than my ant jar. Can anybody tell me why this is so ? Should they be different in sizes after converting the build to maven ? what should I be looking for causes of differences ? Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
need jar location
Can anyone point me to a repository where I can find this jar dependency ? aspose.pdf-3.2.jdk16 Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
snapshot build size difference
So I was finally able to get a good snapshot jar build from maven. But I noticed that the size of the maven build is bigger than the ant build. Does anyone have any suggestions on how to compare or find out why this is so ? Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
RE: compile error with aspose.pdf
I get this error when I run mvn -X compile: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project foundation: Compilation failure: Compilation failure: [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,23] cannot find symbol [ERROR] symbol: class License [ERROR] location: package aspose.pdf [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,59] cannot find symbol [ERROR] symbol: class License [ERROR] location: package aspose.pdf [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project foundation: Compilation failure at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:858) at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 20 more [ERROR] -Original Message- From: Russell Gold [mailto:russell.g...@oracle.com] Sent: Tuesday, August 25, 2015 2:56 PM To: Maven Users List Subject: Re: compile error with aspose.pdf What happens when you run: mvn -X compile? do you really mean to have a package named aspose.pdf? > On Aug 25, 2015, at 2:59 PM, Magnanao, Hector wrote: > > Can anyone tell me how to resolve this compile error ? I've uploaded the jar > locally and I still get the error. > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) > on project foundation: Compilation failure: Compilation failure: > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,23] > cannot find symbol > [ERROR] symbol: class License > [ERROR] location: package aspose.pdf > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,59] > cannot find symbol > [ERROR] symbol: class License > > Hector Magnanao Jr. > SCM Analyst > > Fieldglass, Inc. > O: (331) 702-6142 > M: (773) 474-3051 > hector.magna...@sap.com > www.fieldglass.com > > Fieldglass is now part of SAP > > This email contains confidential information. If you are not the intended > recipient, do not read, distribute or reproduce this transmission (including > any attachments). If you have received this email in error, please notify the > sender by email reply. > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -
compile error with aspose.pdf
Can anyone tell me how to resolve this compile error ? I've uploaded the jar locally and I still get the error. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project foundation: Compilation failure: Compilation failure: [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,23] cannot find symbol [ERROR] symbol: class License [ERROR] location: package aspose.pdf [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,59] cannot find symbol [ERROR] symbol: class License Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
package com.aspose.cells does not exist
Can anyone point me to where to get the dependency for aspose-cells-7.3.1.jar ? I can't find a good repo in google. Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
RE: how can i upload version 1.1.0.1 of tomcat-jdbc
I don't see version 1.1.0.1 in that link that you sent me. -Original Message- From: Olivier Lamy [mailto:ol...@apache.org] Sent: Monday, August 24, 2015 11:18 PM To: Maven Users List Subject: Re: how can i upload version 1.1.0.1 of tomcat-jdbc Try this one: http://repo.maven.apache.org/maven2/org/apache/tomcat/tomcat-jdbc/ HTH Olivier On 25 August 2015 at 03:18, Magnanao, Hector wrote: > I need to compile with 1.1.0.1. whenever I try to compile with this > version, it says the > [WARNING] The POM for org.apache.tomcat:tomcat-jdbc:jar:1.1.0.1 is > missing, no dependency information available > > Is there another url or group that I can grab this version from ? Or do I > need download this locally ? > > Hector Magnanao Jr. > SCM Analyst > > Fieldglass, Inc. > O: (331) 702-6142 > M: (773) 474-3051 > hector.magna...@sap.com > www.fieldglass.com > > Fieldglass is now part of SAP > > This email contains confidential information. If you are not the intended > recipient, do not read, distribute or reproduce this transmission > (including any attachments). If you have received this email in error, > please notify the sender by email reply. > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
dependency error
Can someone help me with this error ? It can't seem to get to this url. [ERROR] Failed to execute goal on project foundation: Could not resolve dependencies for project com.mycompany.app:foundation:jar:1.0-SNAPSHOT: Failure to find javax.sql:jdbc-stdext:jar:2.0 in http://maven.aspose.com/artifactory/simple/ext-release-local/ was cached in the local repository, resolution will not be reattempted until the update interval of AsposeJavaAPI has elapsed or updates are forc ed -> [Help 1] [ERROR] I have this url setup in my pom file as below: AsposeJavaAPI Aspose Java API http://maven.aspose.com/artifactory/simple/ext-release-local/ Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
how can i upload version 1.1.0.1 of tomcat-jdbc
I need to compile with 1.1.0.1. whenever I try to compile with this version, it says the [WARNING] The POM for org.apache.tomcat:tomcat-jdbc:jar:1.1.0.1 is missing, no dependency information available Is there another url or group that I can grab this version from ? Or do I need download this locally ? Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
error when using log4j dependency
Why does Maven complain with this error when I try to use version 1.2.15 of log4j as a dependency in my pom file ? Is there a different way of uploading this particular version of log4j ? [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.373 s [INFO] Finished at: 2015-08-24T11:20:17-05:00 [INFO] Final Memory: 6M/246M [INFO] [ERROR] Failed to execute goal on project foundation: Could not resolve dependencies for project com.mycompany.app:foundation:jar:1.0-SNAPSHOT: The following artifacts could not be resolved: javax.jms :jms:jar:1.1, com.sun.jdmk:jmxtools:jar:1.2.1, com.sun.jmx:jmxri:jar:1.2.1: Could not transfer artifact javax.jms:jms:jar:1.1 from/to java.net (https://maven-repository.dev.java.net/nonav/repository): Cannot access https://maven-repository.dev.java.net/nonav/repository with type legacy using the available connector factories: BasicRepositoryConnectorFactory: Cannot access https://maven-repository. dev.java.net/nonav/repository with type legacy using the available layout factories: Maven2RepositoryLayoutFactory: Unsupported repository layout legacy -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
build error - could not access repository
Can anyone help on why I'm getting this error ? [ERROR] Failed to execute goal on project foundation: Could not resolve dependencies for project com.mycompany.app:foundation:jar:1.0-SNAPSHOT: The following artifacts could not be resolved: com.sun.jmx:jmxri:jar:1.2.1, javax.sql:jdbc-stdext:jar:2.0, javax.jms:jms:jar:1.1, com.sun.jdmk:jmxtools:jar:1.2.1: Could not transfer artifact com.sun.jmx:jmxri:jar:1.2.1 from/to java.net (https://maven-repository.dev.java.net/nonav/repository): Cannot access https://maven-repository.dev.java.net/nonav/repository with type legacy using the available connector factories: BasicRepositoryConnectorFactory: Ca nnot access https://maven-repository.dev.java.net/nonav/repository with type legacy using the available layout factories: Maven2RepositoryLayoutFactory: Unsupported repository layout legacy -> [Help 1 ] Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
RE: build error on strutsel
Curtis, can you elaborate on this ? if the libraries I uploaded in my pom file are newer, how do I find out what version of those libraries are set of code compatible with ? For instance, in my old ant lib folder, I have a struts and struts-el.jar. should I load those into my own local repository ? Hector -Original Message- From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf Of Curtis Rueden Sent: Friday, July 24, 2015 4:13 PM To: Maven Users List Subject: Re: build error on strutsel Hi Hector, Maybe you are depending on the wrong version of those libraries? API change and evolve; you have to depend on a version compatible with what was originally coded against. -Curtis On Fri, Jul 24, 2015 at 3:04 PM, Magnanao, Hector wrote: > Hi Curtis, > > I have these remaining errors on my compilation. I can't figure out if > this is code or package errors. Can you help me out ? > > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[351,53] > cannot find symbol > symbol: method getName() > location: class foundation.web.taglib.struts.html.FormTagEl > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[352,18] > cannot find symbol > symbol: method setName(java.lang.String) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[360,54] > cannot find symbol > symbol: method getScope() > location: class foundation.web.taglib.struts.html.FormTagEl > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[361,18] > cannot find symbol > symbol: method setScope(java.lang.String) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[375,53] > cannot find symbol > symbol: method getType() > location: class foundation.web.taglib.struts.html.FormTagEl > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[376,18] > cannot find symbol > symbol: method setType(java.lang.String) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,23] > cannot find symbol > symbol: class License > location: package aspose.pdf > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,59] > cannot find symbol > symbol: class License > location: package aspose.pdf > [INFO] 8 errors > > -Original Message- > From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf > Of Curtis Rueden > Sent: Friday, July 24, 2015 1:13 PM > To: Maven Users List > Subject: Re: build error on strutsel > > Hi Hector, > > > package com.aspose.cells does not exist > > Looks like Aspose.Cells is in its own Maven repo from that company: > > > http://www.aspose.com/blogs/aspose-products/aspose-total-product-family/archive/2014/08/12/aspose-for-maven-aspose-cloud-maven-repository.html > > Found by searching Google for "com.aspose.cells maven" > > Repeat these tricks for all packages you need to find. > > -Curtis > > On Fri, Jul 24, 2015 at 12:39 PM, Magnanao, Hector < > hector.magna...@sap.com> > wrote: > > > Hi Curtis, that’s ok, I got past that error. Now I get this one. > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile > > (default-compile) on project foundation: Compilation failure: Compilation > > failure: > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[3,24] > > package com.aspose.cells does not exist > > > > From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf > > Of Curtis Rueden > > Sent: Friday, July 24, 2015 12:35 PM > > To: Maven Users List > > Subject: Re: build error on strutsel > > > > Hi Hector, > > > > > I clicked on the link and it returns nothing. > > > How do I search for it in the repository ? > > > > That's baffling. I see this: > > > > [Inline image 1] > > > > I have no clue why it would be different for you... > > > > Regards, > > Curtis > > > > On Fri, Jul 24, 2015 at 12:31 PM, Magnanao, Hector < > > hector.magna...@sap.com<mailto:hector.magna...@sap.com>> wrote: > > Hi Curtis, > > > > I clicked on the link and it returns nothing. How do I sea
RE: build error on strutsel
Hi Curtis, I have these remaining errors on my compilation. I can't figure out if this is code or package errors. Can you help me out ? [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[351,53] cannot find symbol symbol: method getName() location: class foundation.web.taglib.struts.html.FormTagEl [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[352,18] cannot find symbol symbol: method setName(java.lang.String) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[360,54] cannot find symbol symbol: method getScope() location: class foundation.web.taglib.struts.html.FormTagEl [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[361,18] cannot find symbol symbol: method setScope(java.lang.String) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[375,53] cannot find symbol symbol: method getType() location: class foundation.web.taglib.struts.html.FormTagEl [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[376,18] cannot find symbol symbol: method setType(java.lang.String) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,23] cannot find symbol symbol: class License location: package aspose.pdf [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[35,59] cannot find symbol symbol: class License location: package aspose.pdf [INFO] 8 errors -Original Message- From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf Of Curtis Rueden Sent: Friday, July 24, 2015 1:13 PM To: Maven Users List Subject: Re: build error on strutsel Hi Hector, > package com.aspose.cells does not exist Looks like Aspose.Cells is in its own Maven repo from that company: http://www.aspose.com/blogs/aspose-products/aspose-total-product-family/archive/2014/08/12/aspose-for-maven-aspose-cloud-maven-repository.html Found by searching Google for "com.aspose.cells maven" Repeat these tricks for all packages you need to find. -Curtis On Fri, Jul 24, 2015 at 12:39 PM, Magnanao, Hector wrote: > Hi Curtis, that’s ok, I got past that error. Now I get this one. > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile > (default-compile) on project foundation: Compilation failure: Compilation > failure: > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[3,24] > package com.aspose.cells does not exist > > From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf > Of Curtis Rueden > Sent: Friday, July 24, 2015 12:35 PM > To: Maven Users List > Subject: Re: build error on strutsel > > Hi Hector, > > > I clicked on the link and it returns nothing. > > How do I search for it in the repository ? > > That's baffling. I see this: > > [Inline image 1] > > I have no clue why it would be different for you... > > Regards, > Curtis > > On Fri, Jul 24, 2015 at 12:31 PM, Magnanao, Hector < > hector.magna...@sap.com<mailto:hector.magna...@sap.com>> wrote: > Hi Curtis, > > I clicked on the link and it returns nothing. How do I search for it in > the repository ? > > -Original Message- > From: ctrueden.w...@gmail.com<mailto:ctrueden.w...@gmail.com> [mailto: > ctrueden.w...@gmail.com<mailto:ctrueden.w...@gmail.com>] On Behalf Of > Curtis Rueden > Sent: Friday, July 24, 2015 12:17 PM > To: Maven Users List > Subject: Re: build error on strutsel > > Hi Hector, > > > I can't find it in the maven repository. > > > http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.apache.strutsel.taglib.utils%22 > > -Curtis > > On Fri, Jul 24, 2015 at 12:11 PM, Magnanao, Hector < > hector.magna...@sap.com<mailto:hector.magna...@sap.com>> > wrote: > > > How do I resolve this package error ? I can't find it in the maven > > repository. > > > > ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile > > (default-compile) on project foundation: Compilation failure: Compilation > > failure: > > ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[64,40] > > package org.apache.strutsel.taglib.utils does not exist > > ERROR] > > > /C:/Foundation/foundation/src/main/ja
RE: build error on strutsel
Hi Curtis, that’s ok, I got past that error. Now I get this one. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project foundation: Compilation failure: Compilation failure: [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/cache/LicenseService.java:[3,24] package com.aspose.cells does not exist From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf Of Curtis Rueden Sent: Friday, July 24, 2015 12:35 PM To: Maven Users List Subject: Re: build error on strutsel Hi Hector, > I clicked on the link and it returns nothing. > How do I search for it in the repository ? That's baffling. I see this: [Inline image 1] I have no clue why it would be different for you... Regards, Curtis On Fri, Jul 24, 2015 at 12:31 PM, Magnanao, Hector mailto:hector.magna...@sap.com>> wrote: Hi Curtis, I clicked on the link and it returns nothing. How do I search for it in the repository ? -Original Message- From: ctrueden.w...@gmail.com<mailto:ctrueden.w...@gmail.com> [mailto:ctrueden.w...@gmail.com<mailto:ctrueden.w...@gmail.com>] On Behalf Of Curtis Rueden Sent: Friday, July 24, 2015 12:17 PM To: Maven Users List Subject: Re: build error on strutsel Hi Hector, > I can't find it in the maven repository. http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.apache.strutsel.taglib.utils%22 -Curtis On Fri, Jul 24, 2015 at 12:11 PM, Magnanao, Hector mailto:hector.magna...@sap.com>> wrote: > How do I resolve this package error ? I can't find it in the maven > repository. > > ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile > (default-compile) on project foundation: Compilation failure: Compilation > failure: > ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[64,40] > package org.apache.strutsel.taglib.utils does not exist > ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/bean/MessageTagEl.java:[72,40] > package org.apache.strutsel.taglib.utils does not exist > > Hector Magnanao Jr. > SCM Analyst > > Fieldglass, Inc. > O: (331) 702-6142 > M: (773) 474-3051 > hector.magna...@sap.com<mailto:hector.magna...@sap.com> > www.fieldglass.com<http://www.fieldglass.com> > > Fieldglass is now part of SAP > > This email contains confidential information. If you are not the intended > recipient, do not read, distribute or reproduce this transmission > (including any attachments). If you have received this email in error, > please notify the sender by email reply. > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org<mailto:users-unsubscr...@maven.apache.org> For additional commands, e-mail: users-h...@maven.apache.org<mailto:users-h...@maven.apache.org>
RE: build error on strutsel
Hi Curtis, I clicked on the link and it returns nothing. How do I search for it in the repository ? -Original Message- From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf Of Curtis Rueden Sent: Friday, July 24, 2015 12:17 PM To: Maven Users List Subject: Re: build error on strutsel Hi Hector, > I can't find it in the maven repository. http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.apache.strutsel.taglib.utils%22 -Curtis On Fri, Jul 24, 2015 at 12:11 PM, Magnanao, Hector wrote: > How do I resolve this package error ? I can't find it in the maven > repository. > > ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile > (default-compile) on project foundation: Compilation failure: Compilation > failure: > ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[64,40] > package org.apache.strutsel.taglib.utils does not exist > ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/bean/MessageTagEl.java:[72,40] > package org.apache.strutsel.taglib.utils does not exist > > Hector Magnanao Jr. > SCM Analyst > > Fieldglass, Inc. > O: (331) 702-6142 > M: (773) 474-3051 > hector.magna...@sap.com > www.fieldglass.com > > Fieldglass is now part of SAP > > This email contains confidential information. If you are not the intended > recipient, do not read, distribute or reproduce this transmission > (including any attachments). If you have received this email in error, > please notify the sender by email reply. > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
build error on strutsel
How do I resolve this package error ? I can't find it in the maven repository. ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project foundation: Compilation failure: Compilation failure: ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/html/FormTagEl.java:[64,40] package org.apache.strutsel.taglib.utils does not exist ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/web/taglib/struts/bean/MessageTagEl.java:[72,40] package org.apache.strutsel.taglib.utils does not exist Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
build compile error
How do I resolve these package errors ? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project foundation: Compilation failure: Compilation failure: [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/dev/PropertiesMungerTask.java:[7,28] package org.apache.tools.ant does not exist [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/jdbc/SqlProfiler.java:[14,26] package javax.servlet.http does not exist [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/jdbc/SqlProfiler.java:[15,26] package javax.servlet.http does not exist [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/jdbc/SqlProfiler.java:[189,45] cannot find symbol Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
RE: how do i fix this error
ced at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:231) at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421) ... 30 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Thursday, July 23, 2015 10:30 AM To: Maven Users List Subject: Re: how do i fix this error http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html Use "1.7". /Anders On Thu, Jul 23, 2015 at 5:20 PM, Magnanao, Hector wrote: > Where do I configure the plugin for java 7 ? > > -Original Message- > From: Quentin Caillard [mailto:quentin.caill...@ariadnext.com] > Sent: Wednesday, July 22, 2015 4:25 PM > To: Maven Users List > Subject: Re: how do i fix this error > > Hi, > > you must configure the maven compiler plugin for java 7. It's java 5 by > default. > > On Wed, Jul 22, 2015 at 10:40 PM, Magnanao, Hector < > hector.magna...@sap.com> > wrote: > > > I'm converting my ant build to maven using the ant plugin. When I try to > > compile my source code, I get this similar errors. Can someone help me > > with the resolution ? > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile > > (default-compile) on project foundation: Compilation failure: Compilation > > failure: > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/jdbc/SqlProfiler.java:[333,55] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/jdbc/SqlListeners.java:[109,48] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/validator/ValidatorException.java:[59,42] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/Query.java:[37,66] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/DBTransactionManager.java:[54,60] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/txhistory/TxHistory.java:[132,86] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/DBPool.java:[260,47] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/txhistory/TxTable.java:[44,78] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/threadlocal/ThreadCache.java:[53,56] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/concurrent/AsyncList.java:[17,50] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERROR] > > > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/txhistory/TxHistoryUtils.java:[47,72] > > diamond operator is not supported in -source 1.5 > > [ERROR] (use -source 7 or higher to enable diamond operator) > > [ERRO
RE: how do i fix this error
Where do I configure the plugin for java 7 ? -Original Message- From: Quentin Caillard [mailto:quentin.caill...@ariadnext.com] Sent: Wednesday, July 22, 2015 4:25 PM To: Maven Users List Subject: Re: how do i fix this error Hi, you must configure the maven compiler plugin for java 7. It's java 5 by default. On Wed, Jul 22, 2015 at 10:40 PM, Magnanao, Hector wrote: > I'm converting my ant build to maven using the ant plugin. When I try to > compile my source code, I get this similar errors. Can someone help me > with the resolution ? > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile > (default-compile) on project foundation: Compilation failure: Compilation > failure: > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/jdbc/SqlProfiler.java:[333,55] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/jdbc/SqlListeners.java:[109,48] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/validator/ValidatorException.java:[59,42] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/Query.java:[37,66] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/DBTransactionManager.java:[54,60] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/txhistory/TxHistory.java:[132,86] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/DBPool.java:[260,47] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/txhistory/TxTable.java:[44,78] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/threadlocal/ThreadCache.java:[53,56] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/concurrent/AsyncList.java:[17,50] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/txhistory/TxHistoryUtils.java:[47,72] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/ReplacementBuffer.java:[162,69] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/AppEnv.java:[115,83] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/DBService.java:[457,58] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/service/Standalone.java:[86,13] > try-with-resources is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable try-with-resources) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/service/Standalone.java:[88,52] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/thread/ThreadProperties.java:[22,77] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > [ERROR] > /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/ThreadCacheConfig.java:[40,62] > diamond operator is not supported in -source 1.5 > [ERROR] (use -source 7 or higher to enable diamond operator) > > Hector Magnanao Jr. > SCM Analyst > > Fieldglass, Inc. &g
how do i fix this error
I'm converting my ant build to maven using the ant plugin. When I try to compile my source code, I get this similar errors. Can someone help me with the resolution ? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project foundation: Compilation failure: Compilation failure: [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/jdbc/SqlProfiler.java:[333,55] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/jdbc/SqlListeners.java:[109,48] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/validator/ValidatorException.java:[59,42] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/Query.java:[37,66] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/DBTransactionManager.java:[54,60] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/txhistory/TxHistory.java:[132,86] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/DBPool.java:[260,47] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/txhistory/TxTable.java:[44,78] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/threadlocal/ThreadCache.java:[53,56] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/concurrent/AsyncList.java:[17,50] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/txhistory/TxHistoryUtils.java:[47,72] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/ReplacementBuffer.java:[162,69] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/util/AppEnv.java:[115,83] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/DBService.java:[457,58] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/service/Standalone.java:[86,13] try-with-resources is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable try-with-resources) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/service/Standalone.java:[88,52] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/thread/ThreadProperties.java:[22,77] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) [ERROR] /C:/Foundation/foundation/src/main/java/com/mycompany/app/db/ThreadCacheConfig.java:[40,62] diamond operator is not supported in -source 1.5 [ERROR] (use -source 7 or higher to enable diamond operator) Hector Magnanao Jr. SCM Analyst Fieldglass, Inc. O: (331) 702-6142 M: (773) 474-3051 hector.magna...@sap.com www.fieldglass.com Fieldglass is now part of SAP This email contains confidential information. If you are not the intended recipient, do not read, distribute or reproduce this transmission (including any attachments). If you have received this email in error, please notify the sender by email reply.
