ok, some link to know better the best practices of J2ee, thanks!
On 13 November 2012 19:39, Wayne Fay wrote:
> > directory, try to create it. The Archetype you used is perhaps broken
> > or doesn't behave as you wanted. Add your dir manually.
>
> It isn't broken. J2EE best practices tell you mak
> There is a way to "force" the JDK (i.e. 1.6) used by the AXIS2 plugin inside
> Maven (without changing environment)? (I would like to have a code
> generation independent from the environment)
Sounds like you need to use toolchains:
http://maven.apache.org/guides/mini/guide-using-toolchains.html
Hi,
I'm using *Maven 3.0.4* and *Axis2 1.5.1* plugin. I've a problem with the
generation of a stub class using AXIS2 plugin on Maven.
Depending on the JDK currently configured on the build environment, AXIS2
plugin generates a different stub class source code. I've tried the
generation using *JDK
> directory, try to create it. The Archetype you used is perhaps broken
> or doesn't behave as you wanted. Add your dir manually.
It isn't broken. J2EE best practices tell you make a Jar project
(module) with your Java source code, and bring it into your War
project as a dependency. So the archety
On 13 November 2012 20:26, daniel echalar wrote:
> Hi,
>
> II have created a maven project using a webapp archetype, the result is
> that in my generated directory structure, there is not the src/main/java
> directory, (there is where I want to put my servlets), so ,how can I do
> that?
Depending
Hi Chad et. al,
> It seems that lots of things in the maven world make the assumption
> that the aggregator pom and the parent pom are one and the same.
Indeed, there are some issues with it. For example:
http://jira.codehaus.org/browse/MNG-4687
Regards,
Curtis
On Tue, Nov 13, 2012 at 12:1
> > Concerning the empty "relativePath" element, this will typically be
> > empty when you can't guarantee that the parent is in the parent
> > directory. it's a common practice to separate the responsibilities of
> > the aggregator pom from the parent pom. When that is the case, if you
> > don'
Have you tried with the git windows port rather than Cygwin git.
That works for me on windows with the release plugin.
Mixing windows and DOS paths / tools is never a good combination in my
experience.
/James
-Original Message-
From: Martin Lichtin [mailto:lich...@yahoo.com]
Sent: 13 N
Thank you for your replied, but I messaged before that I replied to the wrong
thread. (where the subject was similar to this one).
I am not having an issue in regards to correct version of the maven release
plugin.
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
No, pluginManagement. dependencyManagement does not effect plugins.
On Tue, Nov 13, 2012 at 11:06 AM, Ron Wheeler
wrote:
> On 13/11/2012 10:43 AM, Ken O'Connell wrote:
>>
>> I put this version in my parent pom after you first suggested it, but it
>> seems like it not using that version, as you po
On 13/11/2012 10:43 AM, Ken O'Connell wrote:
I put this version in my parent pom after you first suggested it, but it seems
like it not using that version, as you pointed out.
Did you put it in the dependencyManagement section? That controls which
version the children get to use.
As a dependen
Same with version 2.3.2 (many thanks of course for pointing out the old version
I was trying with).
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
[INFO] Working directory: C:\users\mli\nuc\core\master\main\inuc
[INFO] Executing: cmd.exe /X /C "git status
I apologize, I replied to the wrong message. Pls disregard.
-Original Message-
From: Ken O'Connell [mailto:koconn...@casenetllc.com]
Sent: Tuesday, November 13, 2012 10:44 AM
To: Maven Users List
Subject: RE: mvn release:prepare cannot git-commit the pom.xml change
I put this version in
I put this version in my parent pom after you first suggested it, but it seems
like it not using that version, as you pointed out.
-Original Message-
From: Robert Scholte [mailto:rfscho...@apache.org]
Sent: Tuesday, November 13, 2012 9:56 AM
To: Maven Users List
Subject: Re: mvn release:p
The Maven team is pleased to announce the release of the Maven Invoker,
version 2.1.1
With this component it is possible to programmatically invoke Maven.
http://maven.apache.org/shared/maven-invoker/
To use the Maven Invoker, add the following dependency to your project:
org.apache.m
The logging says:
"org.apache.maven.plugins:maven-release-plugin:2.0:prepare"
This means you're using a pretty old version of the maven-release-plugin.
Try to lock the version on 2.3.2 first.
Robert
Op Tue, 13 Nov 2012 15:17:33 +0100 schreef Martin Lichtin
:
Hi
As a first-time user of th
The Maven team is pleased to announce the release of the Maven Plugin
Plugin, version 3.2.
The Maven Plugin Plugin is used to create a Maven plugin descriptor
for any Mojo's found in the source tree, to include in the JAR. It is
also used to generate report files for the Mojos as well as for
updat
Hi
As a first-time user of the "release" plugin, I'm running into the following
problem:
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
[INFO] Working directory: C:\Users\mli\nuc\core\master\main\inuc
[INFO] Executing: cmd.exe /X /C "git status"
[INFO] Wo
Hi,
This has been done in trunk (version 2.10-SNAPSHOT)
We just need to release that.
Feel free to try SNAPSHOT and give us some feedbacks if you have any issues.
2012/11/13 Brett Walker :
> Hi All,
>
>
> I'm using the Maven Checkstyle plugin in a new Java 7 project.
>
>
>
> The latest version of
2012/11/13 Brett Walker :
> Hi Thomas,
>
>>> I tried building the plugin myself with an updated dependency. It did not
>>> work.
>>
>>Have you tried overriding the plugin dependency with checkstyle:5.6?
>>
>>
>> maven-checkstyle-plugin
>> 2.9.1
>>
>>
>> com.puppycrawl.tools
>>
Just FYI, this has been fixed on trunk:
http://jira.codehaus.org/browse/MCHECKSTYLE-181
So if you can't wait, you could always build your internal release.
/Anders
On Tue, Nov 13, 2012 at 10:07 AM, Brett Walker
wrote:
> Hi Thomas,
>
> >> I tried building the plugin myself with an updated depen
Hi Thomas,
>> I tried building the plugin myself with an updated dependency. It did not
>> work.
>
>Have you tried overriding the plugin dependency with checkstyle:5.6?
>
>
> maven-checkstyle-plugin
> 2.9.1
>
>
> com.puppycrawl.tools
> checkstyle
> 5.6
>
On Tue, Nov 13, 2012 at 12:50 AM, Brett Walker
wrote:
> Hi All,
>
> I'm using the Maven Checkstyle plugin in a new Java 7 project.
>
> The latest version of the plugin (v2.9.1) has a dependency of Checkstyle
> v5.5. This has been fine until I tried using the new Java 7
> try-with-resource; when
Hi All,
I'm using the Maven Checkstyle plugin in a new Java 7 project.
The latest version of the plugin (v2.9.1) has a dependency of Checkstyle v5.5.
This has been fine until I tried using the new Java 7 try-with-resource; when
it reported an inner assignment warning.
I have found that th
24 matches
Mail list logo
