Yes i tried using maven-antrun-plugin but i am not able to setup JDK 1.4.2
version in it. I am trying to specify all possible way to apply JDK version
1.4.2 but it's still taking tools.jar or JDK version, Which maven.bat file
is using (jdk 1.5)
I was using following code in MAVEN-ANTRUN-PLUGIN as
Looks to me you're trying to use the wrong plugin. This one seems to fit
more:http://maven.apache.org/plugins/maven-antrun-plugin/ -Robert > Date: Thu,
18 Aug 2011 15:21:49 -0700
> Subject: exec-maven-plugin want to pass maven.dependency.classpath as a
> variable in my EXEC Goal
> From: daivis
Hi,
I want to define property or want to use maven.plugin.classpath and
maven.dependency.classpath in my build.xml.
How can i do it ?
Sample code is as below...
is not working and not able to read the values from
my build.xml so please explain me how can i do it ?
> I guess this has been asked before, but is there any way to gracefully
> handle situations in a multi-level modular project where the artifactId
> does not always correspond to the folder name of the module?
Maven operates under certain conventions. This is not the convention,
thus it is not wel
Hi,
I am not aware of any other solution, but I remember the following
comment by Benjamin, quoted from http://jira.codehaus.org/browse/MNG-5000:
"The cause of the issue was that module-2 has a different artifactId
than its module name. Let me stress that such a layout is a recipe for
troub
On Thu, Aug 18, 2011 at 10:40:23AM -0600, David Hoffer wrote:
> I'm creating a plugin and having trouble getting the container
> (plexus) to configure initial values. I've started with the
> dependency plugin as a basis and see that somehow mojo parameters get
> set with default values...I assume
I'm creating a plugin and having trouble getting the container
(plexus) to configure initial values. I've started with the
dependency plugin as a basis and see that somehow mojo parameters get
set with default values...I assume this is happening by the container
but what's the secret to making thi
Hi,
I guess this has been asked before, but is there any way to gracefully
handle situations in a multi-level modular project where the artifactId
does not always correspond to the folder name of the module?
It's especially about the scm url and connection.
So my folder structure is like this:
Hi,
I would like to let my co-workers publish Maven sites easily. For this I'd
like to define some kind of convention for site locations. I would like this
to work "out-of-the-box", so if I create a new Maven project that uses the
company POM, its site would be deployed to the right location autom
The issue turns out to be that the 'package' statement in the class
was wrong! I have no idea why the compiler, and checkstyle, and PMD,
all allowed this, but javadoc was the only canary to chirp.
On Thu, Aug 18, 2011 at 10:18 AM, Anders Hammar wrote:
> Does it work with command line javadoc tool
Does it work with command line javadoc tool?
/Anders (mobile)
Den 18 aug 2011 16.05 skrev "Benson Margulies" :
> There is exactly one java source file, for a public class, in the
> package cited below. There are no exclusions set up. Anyone have a
> clue?
>
> INFO] [javadoc:javadoc {execution: def
There is exactly one java source file, for a public class, in the
package cited below. There are no exclusions set up. Anyone have a
clue?
INFO] [javadoc:javadoc {execution: default-cli}]
[INFO]
1 error
1 warning
[INFO]
[ERRO
My understanding is that maven-embedder stopped being supported for
Maven 2 at v2.0.4 (there is no 2.0.5, 2.1.x, or 2.2.x for example).
Then it was re-introduced with Maven 3, but I'm guessing that the API
changed completely.
But I could be completely off...
/Anders
On Thu, Aug 18, 2011 at 15:31,
The MavenEmbedder class is gone, the maven-embedder module that still exists in
the source is a misnomer really. Though if you look at the MavenCli class
you'll see how we use some of the components to do some basic things like
execute goals, read settings and the like.
On Aug 18, 2011, at 9:31
Thanks for a link to those examples.
I noticed that that pom has dependencies like:
org.apache.maven
maven-model
3.0.1
This artifact is also a dependency of the maven-embedder artifact. The
statement I linked earlier regarding the maven embedder not being supported;
It is basically the effective pom, but just for properties. So if in your
settings.xml file you have this:
profileId
profileProperty1Value
profileProperty3Value
true
And in the pom you have this:
pomProperty
While you're use case is not quite clear to me ("combined view of
properties defined in pom and in profile..."), you could take a peek
at this:
https://github.com/sonatype/sisu-maven-bridge
It does offer effective pom for example...
Patches, as always, are welcome! :)
Thanks,
~t~
On Wed, Aug
separate modules!
/Anders
On Thu, Aug 18, 2011 at 09:39, Asplund Marko wrote:
> Hi,
>
> I'm using the jaxws-maven-plugin to build a JAX-WS webservice implementation
> (packaged as an EJB jar).
> The service contract and message type definitions are stored in src/wsdl and
> they're packaged in
Hi,
I'm using the jaxws-maven-plugin to build a JAX-WS webservice implementation
(packaged as an EJB jar).
The service contract and message type definitions are stored in src/wsdl and
they're packaged in META-INF/wsdl in a jar.
This is working fine, but now I need generate a Java client API pack
Codehaus have been upgrading servers over the past few weeks.
On Thu, Aug 18, 2011 at 7:51 AM, Siegfried Goeschl
wrote:
> Hi John,
>
> if you mean something like
>
> [INFO] [site:deploy {execution: default-deploy}]
> https://dav.codehaus.org/mojo/webtest-maven-plugin - Session: Opened
> Aug 17, 2
20 matches
Mail list logo