This is really a Maven question, not a Maven on Eclipse (M2E) question, and
probably better asked on us...@maven.apache.org
However, the reason is simply that Maven defaults to JDK 1.5. To change it,
you'll want something like the following in your pom.xml ...
org.apach
> costs savings "IT department of a large bank" might get by sticking to
> an old java version.
Also, remember that we're only talking about the JRE of the compilation
tool; I assume there would be absolutely no requirement to enforce JRE7 on
the compiled projects, simply that JRE7 must be used to
y for the project. Perhaps detecting M2E and simply copying the
> web.xml to jspweb.xml if the build is running from eclipse.
>
> -Eric
>
>
> On 05/06/2013 01:19 PM, Greg Thomas wrote:
>
> Firstly, be aware, if you're not already, that a plugin for
> JSPC compilat
Firstly, be aware, if you're not already, that a plugin for
JSPC compilation already exists; http://mojo.codehaus.org/jspc/index.html /
http://mojo.codehaus.org/jspc/jspc-maven-plugin/usage.html
The current release, 2.0-alpha-3, despite the alpha label is stable and
runs fine; it works with Tomcat
On 20 November 2012 11:31, Shumail Arshad wrote:
>
> And thanks for pointing out that I am doing something wrong. Can you please
> point me to some study material or anything which explains me standard way of
> using maven. I am unable to understand how will I be able to package the
> release i
On 1 November 2012 16:21, Jeff wrote:
> It's not Maven that can't find it. I'm building and running the app in our
> CD pipeline and in ... netbeans. It is only an issue when
> attempting to run/debug within the eclipse environment.
If you've got m2e installed, then if Maven knows where the cor
On 1 November 2012 16:05, Jeff wrote:
> Does anyone use Eclipse Indigo + Maven and Enunciate? If so, are you able
> to run/debug the web app?
>
> I recently retrofitted Enunciate into a project and Eclipse doesn't seem to
> recognize the web.xml file that Enunciate generates as part of the Maven
On 5 September 2012 08:35, wrote:
> Hi,
>
> My team is also facing the same issue. How do I identify the proxy settings
> in my profile.Actually the jar file is already present in the local
> repository.Any help.
Which version of the plugin are you using? I did see this previously,
but the pro
On 3 September 2012 13:50, Seref Arikan wrote:
> Thanks a lot for your help, I think I got it now, just trying to understand
> what I'm losing with not having workspace dependency on :)
With workspace resolution, if project A depends on project B, I can
make changes to project B and project A wil
On 29 August 2012 11:27, Fred Bricon wrote:
> On Wed, Aug 29, 2012 at 12:15 PM, Igor Fedorenko wrote:
>>
>> Umm. Sure. I've uploaded new build last night. Do you still see the
>> problem with a fresh/clean install from m2e milestones 1.2 repo?
>
> New build fixes it. Thanks!!!
It also fixes the
On 20 August 2012 13:12, Fred Bricon wrote:
> Also can you show us how you defined your mirrors in your settings?
>
>
> On Mon, Aug 20, 2012 at 2:06 PM, Fred Bricon wrote:
>>
>> Do you have a more complete stacktrace?
>> Is the archetype defined in a remote archetype catalog or found in your
>> n
On 16 August 2012 23:16, Fred Bricon wrote:
> The latest 1.2 build (few minutes old) contain fixes wrt remote archetype
> resolution. If you had troubles using remote archetypes behind proxies or
> mirrors, I'm interested in knowing if this works for you now.
I just tried 1.2.0.20120819-2129 with
On 24 July 2012 13:10, Markus Karg wrote:
> Well, „canBeEdited“ is the Unit Test itself, so it cannot be the source, as
> it runs well in mvn (and, BTW, it does nothing but simply creating an
> instance of a class).
By default, de.quipsy.entities.ProjectAPQPCompliance.canBeEdited is
not a class t
For whatever reason, an in-place upgrade doesn't seem to work when
moving to Indigo/m2e-1.x.
The easiest way I've found to resolve it is to simply delete the
project from your Eclipse workspace (without deleting the underlying
files), deleting the Eclipse-related files (.settings\, project, ,
.cla
I do however think there would be a benefit in moving to Maven and using a
pom.xml file with only a few dependencies. Once you've got started, you can
chip away at moving files from your web-inf/lib folder to dependencies. It
will be worth it in the long term, and you've got to start somewhere ...
On 26 September 2011 15:05, Fred Bricon wrote:
> What happens if you :
> - delete the projects from the workspace, delete all their eclipse config
> files and import them back as maven projects?
Now that did sort it! I'd tried deleting and re-importing the
projects, but not tried deleting the Ecl
I think I've found a bug with the "Workspace Resolution" functionality
within me2/m2e-wtp (I'm not sure which ...)
I've got project-a, a simple m2e project whose output is a JAR file.
I've got a project-b, which is a m2e-wtp project that depends on project-a.
With workspace resolution enabled, I
On 15 September 2011 20:23, Fred Bricon wrote:
> You can use the m2e activated profile like :
>
>
> m2e
>
>
> m2e.version
>
>
> ...
>
Excellent, many thanks I'm all sorted, now. FWIW, I found I also had
to use the reverse syntax, !m2e.versio
On 15 September 2011 17:28, Greg Thomas wrote:
>> Have you tried using profiles? Project properties > Maven > Activate Maven
>> Profiles allows you to activate a specific profile when building the project
>> under eclipse.
...
> That certainly looks like a potential res
> Have you tried using profiles? Project properties > Maven > Activate Maven
> Profiles allows you to activate a specific profile when building the project
> under eclipse.
> This way you can have distinct maven-war-plugin configurations for
> distribution and development builds.
I haven't, thanks
.org
Thanks,
Greg
On 4 September 2011 19:53, Greg Thomas wrote:
> Hi,
>
> I'm using the jspc-maven-plugin compiler to pre-compile my JSPs when I
> package my project in to a WAR file. Part of that process is to
> generate a web.xml file that is a combination of the one based on
Hi,
I'm using the jspc-maven-plugin compiler to pre-compile my JSPs when I
package my project in to a WAR file. Part of that process is to
generate a web.xml file that is a combination of the one based on the
hand-crafted ${basedir}/src/main/webapp/WEB-INF/web.xml in the
project, and the result of
> I formerly use the maven 2.0.8 and have no problem by using the wsgen goal in
> pom.xml. Now
> I change to maven 3.0.3 and got problem after I import the project into the
> eclipse. I got error
> message as follow:
> "Plugin execution not covered by lifecycle configuration:
> org.codehaus.mojo:
On 22 August 2011 22:46, Fred Bricon wrote:
> Le 22 août 2011 05:46, "Greg Thomas" a écrit :
>>
>> When the project is published to the Eclipse version of Tomcat it gets
>> renamed to jspweb.xml
>
> First time I here about that issue.
> Can you post the
I often get those sort of errors; I find stopping the server, selecting
'Clean' (right click on the server in the servers tab), and restarting the
server sorts it.
Greg
On Tuesday, 23 August 2011, Hugi Thordarson wrote:
> Hi Fred.
> Thanks for pointing me to the .log file. I had a stack trace th
Hi all,
I'm using m2eand m2e-wtp. I'm not sure exactly which versions (Eclipse
doesn't make it easy to check), but it's the latest from the Eclipse
Marketplace.
It's all working brilliantly, and makes development much easier. So
many thanks for that.
However, I've one small niggle. My web projec
26 matches
Mail list logo
